From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Sascha Grunert <saschagrunert@icloud.com>, sopium@mysterious.site
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Working on a Rust implementation, and request for test vectors
Date: Tue, 21 Feb 2017 12:14:42 +0100 [thread overview]
Message-ID: <CAHmME9oTCuOV+EB-aCjnKBBZ0sKzU55LndxkVBPr2CTnJ7PqYg@mail.gmail.com> (raw)
In-Reply-To: <2A1F92D5-90A4-4105-A764-897ADFF15D1D@icloud.com>
Hey Sopium,
Sascha and I are all set up. Let me know if you'd like to get in on
the effort too. As well, if you'd like to have a NoiseIK-specific
library or something of that sort, I'd be happy to host that on the
same infra/organization all together. Let me know what you'd like to
do.
Regards,
Jason
prev parent reply other threads:[~2017-02-21 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 6:07 sopium
2017-02-21 10:07 ` Sascha Grunert
2017-02-21 10:48 ` Jason A. Donenfeld
2017-02-21 11:14 ` Jason A. Donenfeld [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=CAHmME9oTCuOV+EB-aCjnKBBZ0sKzU55LndxkVBPr2CTnJ7PqYg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=saschagrunert@icloud.com \
--cc=sopium@mysterious.site \
--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).