wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Claude Richoux <crichoux@janestreet.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard-rs implementation
Date: Sun, 25 Aug 2019 09:49:37 -0600	[thread overview]
Message-ID: <CAHmME9qEoKtVVQLpuQ1MPrFvspcG+V03o-ZEzuaCQS19JuXwMw@mail.gmail.com> (raw)
In-Reply-To: <CAKZtF0rY6AZzyjwyAo5wtTqcS2GoOGPaUA1XVgGOaG_ZZ=rSbg@mail.gmail.com>

On Sun, Aug 25, 2019 at 9:47 AM Claude Richoux <crichoux@janestreet.com> wrote:
>
> 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?

Mathias is hard at work on wireguard-rs, so there are likely all sorts
of broken or unfinished things in there. The good news is that its
development finally has some great momentum. The not as good news is
that you'll have to wait a tad bit longer for it to be complete.

https://www.wireguard.com/repositories/ has the status of each of our
projects, by the way.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-08-25 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 20:30 Wireguard-rs implementation Claude Richoux
2019-08-25 15:49 ` 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=CAHmME9qEoKtVVQLpuQ1MPrFvspcG+V03o-ZEzuaCQS19JuXwMw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=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).