From: ST <smntov@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: SFTP-based VPN bootstrapping with automatic collision-free IPs assignment/peers' public data sharing
Date: Wed, 18 Apr 2018 13:38:34 +0300 [thread overview]
Message-ID: <1524047914.9423.5.camel@gmail.com> (raw)
In-Reply-To: <CAHmME9qy5mNRNHM4qJc-kBVu1+5ryO8fY5sZfCLiXRvc+b9vmw@mail.gmail.com>
What uses unauthenticated TCP - your demo.wireguard.com script or DHCP?
On Wed, 2018-04-18 at 06:04 +0200, Jason A. Donenfeld wrote:
> The problem is that it uses unauthenticated TCP.
prev parent reply other threads:[~2018-04-18 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 17:49 SFTP-based VPN bootstrapping with automatic collision-free IPs assignment/peers' public data sharing ST
2018-04-15 22:37 ` Jason A. Donenfeld
2018-04-16 8:08 ` ST
2018-04-17 20:07 ` ST
2018-04-18 4:04 ` Jason A. Donenfeld
2018-04-18 10:38 ` ST [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=1524047914.9423.5.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Jason@zx2c4.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