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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 25 Sep 2019 12:14:40 +0200 From: "Jason A. Donenfeld" <Jason@...c4.com> To: David Miller <davem@...emloft.net> Cc: WireGuard mailing list <wireguard@...ts.zx2c4.com>, Netdev <netdev@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: WireGuard to port to existing Crypto API Hi Dave, On Wed, Sep 25, 2019 at 12:03 PM David Miller <davem@...emloft.net> wrote: > I didn't say "must" anything, I suggested this as a more smoothe > and efficient way forward. s/must/should/g? However it's characterized, I think your jugements and opinions are generally sound, and I intend to put them into action. > I'm also a bit disappointed that you felt the need to so quickly > make such an explosive posting to the mailing list when we've Explosive? That's certainly not the intent here. The project is changing direction in a big way. Collaborating with others on the crypto API will be an important part of that. Announcing the change in direction, those intentions, a rationale on why it will be okay, and inviting collaboration is a responsible thing to do at the earliest opportunity. Better to announce intent early rather than surprise people or deter potential collaborators by keeping plans secret. Jason
Powered by blists - more mailing lists