From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: David Miller <davem@davemloft.net>
Cc: Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: WireGuard secure network tunnel
Date: Mon, 9 Dec 2019 11:07:16 +0100 [thread overview]
Message-ID: <CAHmME9pXLEhe1gJm84EzXCRONMH-VfBh6UsKQ_DLq1NyOSS+_Q@mail.gmail.com> (raw)
In-Reply-To: <20191208.175209.1415607162791536317.davem@davemloft.net>
On Mon, Dec 9, 2019 at 2:52 AM David Miller <davem@davemloft.net> wrote:
>
> From: "Jason A. Donenfeld" <Jason@zx2c4.com>
> Date: Mon, 9 Dec 2019 00:27:34 +0100
>
> > WireGuard is a layer 3 secure networking tunnel made specifically for
> > the kernel, that aims to be much simpler and easier to audit than IPsec.
> > Extensive documentation and description of the protocol and
> > considerations, along with formal proofs of the cryptography, are
> > available at:
> >
> > * https://www.wireguard.com/
> > * https://www.wireguard.com/papers/wireguard.pdf
> ...
>
> Applied, thanks Jason.
Thank you, Dave!
next prev parent reply other threads:[~2019-12-09 10:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 23:27 [PATCH net-next v2] net: WireGuard secure network tunnel Jason A. Donenfeld
2019-12-09 1:52 ` David Miller
2019-12-09 10:07 ` Jason A. Donenfeld [this message]
2019-12-18 10:12 ` Dmitry Vyukov
2019-12-18 10:57 ` Jason A. Donenfeld
2019-12-18 11:37 ` Dmitry Vyukov
2019-12-18 11:50 ` Jason A. Donenfeld
2019-12-19 9:35 ` Dmitry Vyukov
2019-12-19 10:07 ` Jason A. Donenfeld
2019-12-19 10:11 ` Jason A. Donenfeld
2019-12-19 10:49 ` Dmitry Vyukov
2019-12-19 10:53 ` Jason A. Donenfeld
2019-12-19 11:18 ` Dmitry Vyukov
2019-12-19 11:38 ` Jason A. Donenfeld
2019-12-19 14:30 ` Dmitry Vyukov
2019-12-19 10:42 ` Dmitry Vyukov
2019-12-19 10:50 ` 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=CAHmME9pXLEhe1gJm84EzXCRONMH-VfBh6UsKQ_DLq1NyOSS+_Q@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).