Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Frank Beuth <seclists@boxdan.com>
To: "Fredrik Strömberg" <stromberg@mullvad.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Rohde & Schwarz Adds Emerging WireGuard VPN Protocol to its Deep Packet Inspection (DPI) Software Library, R&S(R) PACE 2
Date: Tue, 19 Feb 2019 20:37:49 +0700	[thread overview]
Message-ID: <20190219133749.cjcisv6g2kmwg3li@web.local> (raw)
In-Reply-To: <CANTUoecQ71BaE-38-qk4CQRXPRTabEEedmsybQb==Y9jaa6epg@mail.gmail.com>

On Thu, Jan 24, 2019 at 12:01:54PM +0100, Fredrik Strömberg wrote:
>It will however be a problem for those blocked by this equipment. Like
>all technology, this DPI equipment is a double-edged sword. Will it be
>sold to a government so they can block privacy-seeking dissidents from
>using WireGuard, or will it be sold to an organization that has a more
>legitimate need to block WireGuard traffic?
>
>The solution is to use an obfuscation protocol that encapsulates
>WireGuard, just like Tor users in censored countries do.

Are there any WireGuard-compatible obfuscation protocols that could be 
considered production ready for use with WireGuard?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-02-21  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  9:18 Rohde & Schwarz Adds Emerging WireGuard VPN Protocol to its Deep Packet Inspection (DPI) Software Library, R&S® " Henrique Carrega
2019-01-24 11:01 ` Rohde & Schwarz Adds Emerging WireGuard VPN Protocol to its Deep Packet Inspection (DPI) Software Library, R&S(R) " Fredrik Strömberg
2019-02-19 13:37   ` Frank Beuth [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=20190219133749.cjcisv6g2kmwg3li@web.local \
    --to=seclists@boxdan.com \
    --cc=stromberg@mullvad.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).