linux-kernel - WireGuard for 5.5?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHmME9oqT_BncUFaJRpj0xtL1MPcE=g5WQG_qE7oC231USQCPA@mail.gmail.com>
Date:   Wed, 27 Nov 2019 11:11:20 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: WireGuard for 5.5?

Hey Dave,

It looks like Frankenzinc has landed in Herbert's crypto-2.6.git tree,
and he'll be pushing to Linus quite soon. The fact that there are two
separate trees means that I've missed your net-next cut this Monday,
due to waiting for these pieces to be in place. But I was wondering if
we could do some juggling so that WireGuard doesn't take ~135 days
from now to be released in 5.6, but rather sooner in 5.5. I suspect
this would entail: Herbert pushes to Linus, you pull from Linus, I
submit on top of your tree, you push back to Linus. I realize that
this isn't the ordinary procedure, and if you prefer to do things in
the ordinary way, that's fine and I understand. But in case you're as
excited as I am about getting WireGuard out the door at long last,
maybe we can try to handle this cross-tree situation with
crypto-2.6.git?

Jason