netdev - Re: WireGuard to port to existing Crypto API

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190925.114031.379108392028630817.davem@davemloft.net>
Date:   Wed, 25 Sep 2019 11:40:31 +0200 (CEST)
From:   David Miller <davem@...emloft.net>
To:     bruno@...ff.to
Cc:     Jason@...c4.com, wireguard@...ts.zx2c4.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: WireGuard to port to existing Crypto API

From: Bruno Wolff III <bruno@...ff.to>
Date: Wed, 25 Sep 2019 04:17:00 -0500

> Are there going to be two branches, one for using the current API and
> one using Zinc?

This is inapproprate to even discuss at this point.

Let's see what the crypto based stuff looks like, evaluate it,
and then decide how to proceed forward.

Thank you.