From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg KH <greg@kroah.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Formally Verified Cryptographic Primitive Implementations
Date: Fri, 19 Jan 2018 14:26:07 +0100 [thread overview]
Message-ID: <CAHmME9oTZn2sB+6HL2UR3NGSnEw5ywXZYs3hJOGgVSq8BE8Q+g@mail.gmail.com> (raw)
In-Reply-To: <20180119082957.GB14517@kroah.com>
On Fri, Jan 19, 2018 at 9:29 AM, Greg KH <greg@kroah.com> wrote:
> No questions, just a general, "Wow, this is great work!"
>
> It's wonderful to see this happen, thanks so much for pushing this
> forward.
Glad you like it. The real work, of course, will be parlaying this
work into kernel crypto api 2.0...
Jason
next prev parent reply other threads:[~2018-01-19 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 15:42 Jason A. Donenfeld
2018-01-19 8:29 ` Greg KH
2018-01-19 13:26 ` Jason A. Donenfeld [this message]
2018-01-20 22:14 ` Jose Marinez
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=CAHmME9oTZn2sB+6HL2UR3NGSnEw5ywXZYs3hJOGgVSq8BE8Q+g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=greg@kroah.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).