wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard to port to existing Crypto API
Date: Tue, 19 Nov 2019 16:25:57 +0100	[thread overview]
Message-ID: <CAHmME9pPDQxVO5m1gRzWkDn5GfRn7yDdNa3_hy7QC-1RmE0H=A@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pmfZAp5zd9BDLFc2fWUhtzZcjYZc2atTPTyNFFmEdHLg@mail.gmail.com>

Hey folks,

Small update on this thread: it turns out that at the same time as I
was stepping toward compromising and using the old crypto API here
with this thread, other kernel developers were interested in
compromising to upstream some aspects of Zinc. The result is that
everybody took constructive steps toward each other, and the first
part of Zinc has been merged:

https://lore.kernel.org/linux-crypto/CAHmME9rxGp439vNYECm85bgibkVyrN7Qc+5v3r8QBmBXPZM=Dg@mail.gmail.com/

It's not called "Zinc" any more, and some of the design decisions I
liked aren't there, but I think the lion's share of what we were after
is there, and a few other pieces should be possible to upstream one at
a time.

These steps forward should unlock WireGuard upstreaming, which I
expect to get rolling again soon. WireGuard is probably mostly okay,
but I still do anticipate review with lots of feedback to incorporate,
since now there's more impetus for people to take the patch submission
seriously. I'll keep this list updated as we move forward.

Regards,
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2019-11-19 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25  8:29 WireGuard to port to existing Crypto API Jason A. Donenfeld
2019-09-25  8:46 ` Toke Høiland-Jørgensen
2019-09-25  9:17 ` Bruno Wolff III
2019-09-25  9:40   ` David Miller
2019-09-25  9:39 ` David Miller
2019-09-25 10:14   ` Jason A. Donenfeld
2019-11-19 15:25 ` Jason A. Donenfeld [this message]
2019-11-19 16:07   ` Toke Høiland-Jørgensen

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='CAHmME9pPDQxVO5m1gRzWkDn5GfRn7yDdNa3_hy7QC-1RmE0H=A@mail.gmail.com' \
    --to=jason@zx2c4.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).