From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Jason E. Aten" <j.e.aten@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: nat traversal / userspace impl
Date: Mon, 17 Apr 2017 23:30:53 +0200 [thread overview]
Message-ID: <CAHmME9rTkyj-K0xi4Kt2Jf9sp2ibF1byXkCN+rZ-CMk7RNHCvg@mail.gmail.com> (raw)
In-Reply-To: <CAPNEFAZZziFPm7mDxBA8WDYROBaBP-fv8RsYjGtTLDDd46+0Xw@mail.gmail.com>
On Mon, Apr 17, 2017 at 11:28 PM, Jason E. Aten <j.e.aten@gmail.com> wrote:
> The "number of security problems" with the approach mentioned in passing in
> the 2016-August message would need enumeration and addressing. Is anybody
> thinking about those? Is this on the roadmap for future plans?
If you're referring to the proof of concept example code for hole
punching... it's just PoC/example code. If you'd like to develop it
into something production worthy, you're more than welcome. It's
licensed under the GPLv2.
Jason
next prev parent reply other threads:[~2017-04-17 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 17:45 Jason E. Aten
2017-04-17 17:55 ` Jason A. Donenfeld
2017-04-17 21:28 ` Jason E. Aten
2017-04-17 21:30 ` Jason A. Donenfeld [this message]
2017-04-17 21:36 ` Jason E. Aten
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=CAHmME9rTkyj-K0xi4Kt2Jf9sp2ibF1byXkCN+rZ-CMk7RNHCvg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=j.e.aten@gmail.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).