From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jason A. Donenfeld" Subject: Re: [PATCH net-next v3 02/17] zinc: introduce minimal cryptography library Date: Tue, 11 Sep 2018 22:29:34 -0600 Message-ID: References: <20180911010838.8818-1-Jason@zx2c4.com> <20180911010838.8818-3-Jason@zx2c4.com> <20180911145624.GA21635@kroah.com> <20180911214737.GA81235@gmail.com> <49BAF465-B3DC-4155-BFF9-DB6C386C1878@amacapital.net> <2E01FBB6-030A-40AB-8BEE-F8F271A57568@amacapital.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: Greg Kroah-Hartman , Ard Biesheuvel , LKML , Netdev , David Miller , Andrew Lutomirski , Samuel Neves , Jean-Philippe Aumasson , Linux Crypto Mailing List To: Andy Lutomirski , Eric Biggers Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi Eric, Andy, > On Tue, Sep 11, 2018 at 5:01 PM Andy Lutomirski wro= te: > > I think Ard=E2=80=99s point is valid: in the long run we don=E2=80=99t = want two competing software implementations of each primitive. It clearly *= should* be possible to make crypto API call into zinc for synchronous softw= are operations, but a demonstration of how this actually works and that the= re isn=E2=80=99t some change to zinc to make it would well would be in orde= r, I think. > > > > IMO the right approach is do one conversion right away and save the res= t for later. It turned out to be fairly straight forward and quick to do. I'm on a transatlantic plane so the connection is super spotty, but you can check out the three commits added to: -- the two "crypto:" commits and the one "random:" commit. Alternatively, you can look directly at and . I'll be refining and checking these over the next week or so, but the basics were super easy to do. Jason