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 11:39:28 +0200 (CEST) From: David Miller <davem@...emloft.net> To: Jason@...c4.com Cc: wireguard@...ts.zx2c4.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: WireGuard to port to existing Crypto API From: "Jason A. Donenfeld" <Jason@...c4.com> Date: Wed, 25 Sep 2019 10:29:45 +0200 > His viewpoint has recently solidified: in order to go upstream, > WireGuard must port to the existing crypto API, and handle the Zinc > project separately. I didn't say "must" anything, I suggested this as a more smoothe and efficient way forward. 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 just spoken about this amongst ourselves only 20 minutes ago. Please proceed in a more smoothe and considerate manner for all parties involved. Thank you.
Powered by blists - more mailing lists