From: Matt Avery <matthewaveryusa@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Is udp data corruption over wireguard possible?
Date: Sat, 22 Dec 2018 22:37:35 -0500 [thread overview]
Message-ID: <CAJp+990eMsXR1hVwY9Vdtjtz+6d=1SrR8iPHof=9-XaKj9ZZXg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 348 bytes --]
It dawned to me today that if I write an application that sends udp
datagrams through the wireguard interface that corruption of the data
within the datagram is not possible even if I decide to zero-out my
datagram checksums (assuming the datagram doesn't get intentionally
corrupted within the kernel.)
Is that assumption correct?
Thanks,
-Matt
[-- Attachment #1.2: Type: text/html, Size: 694 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-01-02 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 3:37 Matt Avery [this message]
2019-01-02 19:46 ` Is udp data corruption over wireguard possible? David Anderson
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='CAJp+990eMsXR1hVwY9Vdtjtz+6d=1SrR8iPHof=9-XaKj9ZZXg@mail.gmail.com' \
--to=matthewaveryusa@gmail.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).