From: Bruno Wolff III <bruno@wolff.to>
To: Roman Mamedov <rm@romanrm.net>
Cc: Nico Schottelius <nico.schottelius@ungleich.ch>,
el3xyz <el3xyz@protonmail.com>,
wireguard@lists.zx2c4.com
Subject: Re: WireGuard with obfuscation support
Date: Mon, 27 Sep 2021 04:14:35 -0500 [thread overview]
Message-ID: <20210927091435.GA10234@wolff.to> (raw)
In-Reply-To: <20210927123439.7a551913@nvm>
On Mon, Sep 27, 2021 at 12:34:39 +0500,
Roman Mamedov <rm@romanrm.net> wrote:
>On Mon, 27 Sep 2021 02:11:30 -0500
>
>Don't over-estimate the resources available to DPIs, if there aren't easy
>ways to block, it might be almost as good as unblockable.
>
>And it is far from all cases that hiding traffic would result in bad
>consequences. Just hiding it enough so it evades the dumb automated filter,
>many people will thank you.
If someone is having their Wireguard traffic blogged, there is a good
chance that they will be negative consequences to trying to evade the
block. Just getting detected will often be enough to trigger these
consequences, even if the traffic is getting through.
This isn't a simple problem. The assumption is that someone is seeing
your network traffic and blocking it. They are still going to see it
even if you disguise it. So you are going to need to disquise it as
something that whoever is watching isn't going to care about. That
is going to vary a lot depending on who is watching. You may also need
to hide who you are communicating with. In some cases that will be even
more important.
There are going to be a number of ways to detect Wireguard traffic and
it is pretty unlikely that the bar for detection can be raised enough to
be relevant with a few simple changes to the protocol.
This suggest that Wireguard is not the correct place to be doing these
things. As suggested in another followup, this fits a lot closer to
tor's mission and that would probably be a better place to look for
help.
next prev parent reply other threads:[~2021-09-27 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 12:09 el3xyz
2021-09-27 0:53 ` Nico Schottelius
2021-09-27 7:11 ` Bruno Wolff III
2021-09-27 7:34 ` Roman Mamedov
2021-09-27 9:14 ` Bruno Wolff III [this message]
2021-09-27 9:36 ` Roman Mamedov
2021-09-27 10:21 ` Bruno Wolff III
2021-09-27 13:01 ` Konstantin Ryabitsev
2021-09-27 13:48 ` Lonnie Abelbeck
2021-09-27 15:28 ` StarBrilliant
2021-09-27 15:59 ` Nico Schottelius
2021-09-27 16:37 ` StarBrilliant
2021-09-27 7:44 ` Nico Schottelius
2021-09-27 8:17 ` Fredrik Strömberg
2021-09-27 16:21 ` 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=20210927091435.GA10234@wolff.to \
--to=bruno@wolff.to \
--cc=el3xyz@protonmail.com \
--cc=nico.schottelius@ungleich.ch \
--cc=rm@romanrm.net \
--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).