From: Claude Richoux <crichoux@janestreet.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard-rs implementation
Date: Mon, 19 Aug 2019 16:30:50 -0400 [thread overview]
Message-ID: <CAKZtF0rY6AZzyjwyAo5wtTqcS2GoOGPaUA1XVgGOaG_ZZ=rSbg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]
Hi there,
I am reimplementing the noise protocol, and I decided to test against
wireguard-rs to check my KDFs. After some confusion, I noticed that the
Blake2s HMAC function is incorrect (it disagrees with pycryptodome,
openssl, and Cloudflare's BoringTun implementation). I guess I'm just
wondering what the status is on wireguard-rs? I saw it on git, so I assumed
it was working, but maybe not?
Thanks!
Claude Richoux
[-- Attachment #1.2: Type: text/html, Size: 480 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-08-25 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 20:30 Claude Richoux [this message]
2019-08-25 15:49 ` 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='CAKZtF0rY6AZzyjwyAo5wtTqcS2GoOGPaUA1XVgGOaG_ZZ=rSbg@mail.gmail.com' \
--to=crichoux@janestreet.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).