From: James Cloos <cloos@jhcloos.com>
To: wireguard@lists.zx2c4.com
Cc: Brian Candler <b.candler@pobox.com>
Subject: Re: Let's talk about obfuscation again
Date: Thu, 06 Sep 2018 17:16:28 -0400 [thread overview]
Message-ID: <m3pnxquy1f.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <2c0808aa-47da-9d1a-1c35-1aec3d0c9acc@pobox.com> (Brian Candler's message of "Thu, 6 Sep 2018 16:24:00 +0100")
>>>>> "BC" == Brian Candler <b.candler@pobox.com> writes:
BC> OK, so what about changing wireguard to use TCP and TLS on port 443?
Using udp/443 for one end could allow making it look like quic.
You'd need non-wg traffic on the port to reply like a quic server would.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2018-09-06 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1542.1536245115.2201.wireguard@lists.zx2c4.com>
2018-09-06 15:24 ` Let's talk about obfuscation again Brian Candler
2018-09-06 21:16 ` James Cloos [this message]
2018-09-06 0:06 StarBrilliant
2018-09-06 8:43 ` Dennis Jackson
2018-09-06 14:45 ` George Walker
2018-09-06 15:19 ` Fredrik Strömberg
2018-09-07 8:49 ` StarBrilliant
2018-09-06 15:34 ` Dennis Jackson
2018-09-06 16:10 ` 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=m3pnxquy1f.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=b.candler@pobox.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).