From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Sascha Grunert <saschagrunert@icloud.com>,
Michael Gerlach <n3ph@terminal21.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Rust Version
Date: Wed, 15 Feb 2017 16:40:05 -0500 [thread overview]
Message-ID: <87bmu3jfpm.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <94F76D79-1813-49E1-AA25-0CE27B3A460D@icloud.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Wed 2017-02-15 13:29:55 -0500, Sascha Grunert wrote:
> The DPI could do a simple classification of the stream which could
> others use within network blocking scenarios. The content should be
> safe, but with obfuscation or maybe tor support it would be even
> „Whisle blower safe“.
Hm, Tor is TCP-only, and WireGuard uses UDP. These systems aren't going
to mix well.
WireGuard cannot and will not obscure the source or destination
addresses of the packets that flow over it.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-02-16 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 17:47 Sascha Grunert
2017-02-15 18:25 ` Michael Gerlach
2017-02-15 18:29 ` Sascha Grunert
2017-02-15 21:40 ` Daniel Kahn Gillmor [this message]
2017-02-17 13:38 ` Jason A. Donenfeld
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=87bmu3jfpm.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=n3ph@terminal21.de \
--cc=saschagrunert@icloud.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).