From: Bzzzz <lazyvirus@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Preshared Key Rework Coming Soon
Date: Fri, 12 May 2017 00:42:11 +0200 [thread overview]
Message-ID: <20170512004211.215058fe@msi.defcon1> (raw)
In-Reply-To: <CAHmME9r1XFZsvMskbBD8N-_+9NU7GJn+weDLwCsNrpsGPcMqDA@mail.gmail.com>
On Thu, 11 May 2017 22:32:23 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> Hey lazylist,
>=20
> Since the last discussion of preshared key mode in WireGuard, we've
> made some substantial progress. Trevor and I have been working out the
> cryptodetails [1], and Kevin and I have been tweaking our formal
> verification model. Everything is coming together quite nicely on that
> front.
It is time, I was about to wait!
May be that's because you do not work enough (nor does Trevor)=E2=80=A6
JY
*<;-{D
prev parent reply other threads:[~2017-05-11 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 20:32 Jason A. Donenfeld
2017-05-11 21:25 ` Fredrik Strömberg
2017-05-11 22:42 ` Bzzzz [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=20170512004211.215058fe@msi.defcon1 \
--to=lazyvirus@gmx.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).