From: Matthias Urlichs <matthias@urlichs.de>
To: Gianluca Gabrielli <tuxmealux@protonmail.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: TCP Wireguard with socat
Date: Tue, 13 Mar 2018 14:43:48 +0100 [thread overview]
Message-ID: <eedf9f8d-ec6a-0c64-37df-a59c15e26e26@urlichs.de> (raw)
In-Reply-To: <2LLzGYJnMQQE8ZVLLI49kcqDj8mQIdytgKD08XsZHwPaBjfN8f3WkcJZA3j4XFXW6sS1UnXfCY2GyS2PIUSGJOfPUZweZQa-tnWcUcPKzFM=@protonmail.com>
On 13.03.2018 10:19, Gianluca Gabrielli wrote:
> I'm wondering why we should prepend a length to each datagram. On the d=
atagram's header the payload length is already present, should not be eno=
ugh to reconstruct the original datagram after the stream has been unwrap=
ped?
Not really, because the datagram's payload length doesn't have to
correspond to the frame length. Think malicious malformed packets, or
networks with a minimum packet length, or protocols other than wireguard
=E2=80=93 you shouldn't assume that no other data is transmitted on that =
link.
Even if all that were true, or if you enfore that on the sending side,
you'd still need a specialized unpacker on the receiving end. Easier to
just use a tool that doesn't have any of these problems.
--=20
-- Matthias Urlichs
prev parent reply other threads:[~2018-03-13 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 16:41 Gianluca Gabrielli
2018-03-09 21:45 ` Matthias Urlichs
2018-03-12 9:15 ` Gianluca Gabrielli
2018-03-12 11:30 ` Matthias Urlichs
2018-03-12 14:37 ` Gianluca Gabrielli
2018-03-12 15:14 ` Gianluca Gabrielli
2018-03-12 15:44 ` Tim Sedlmeyer
2018-03-12 16:45 ` Gianluca Gabrielli
2018-03-12 17:05 ` Matthias Urlichs
2018-03-12 18:47 ` Matthias Urlichs
2018-03-13 9:19 ` Gianluca Gabrielli
2018-03-13 13:43 ` Matthias Urlichs [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eedf9f8d-ec6a-0c64-37df-a59c15e26e26@urlichs.de \
--to=matthias@urlichs.de \
--cc=tuxmealux@protonmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).