Re: [PATCH net-next v9 00/19] WireGuard: Secure Network Tunnel

From
Herbert Xu <herbert@gondor.apana.org.au>
Date
2019-03-25 11:52:09
Also in
linux-crypto, lkml
Reply to
Jason A. Donenfeld, 2019-03-22
Jason A. Donenfeld [off-list ref] wrote:
Changes v8->v9, along with who suggested it.
--------------------------------------------
- [EVERYBODY] Zinc no longer ships generated assembly code. Rather, we now
 bundle in the original perlasm generator for it. This is ongoing joint work
 with Andy Polyakov upstream, so that the same .pl files can live in our tree
 as well as in the CRYPTOGAMS tree. I personally find that the code required
 to share this in both repositories to be a tiny bit ugly. I think there would
 be some degree of an advantage to removing that and making the .pl
 kernel-only, and then carefully tracking Andy's changes (as we already
 do). Previous opinions on the list, though, were that there's also
 significant advantage to being able to share the exact same code in both.
 And I think there's a decent amount of wisdom in that too. Since that
 appeared to be the prevailing view, and since it also has good reasons
 arguments, we'll go with that for now.
Thanks for the update.
 
quoted hunk ↗ jump to hunk
- Following the Adiantum merge, the two commits that port the old crypto API
 over to use Zinc have been removed from this series. We can certainly add
 them back in at some point, but I thought it'd be favorable to at least
 begin to receive some sign-offs on the Zinc-specific commits, now that
 (hopefully all of) the previous feedback has been taken care of. The two
 commits porting it over are fairly standalone as well, so that shouldn't
 impact the ability to review this. For now those are living in the
 jd/with-cryptoapi-port branch of kernel.org's zx2c4/linux.git tree. This
 also allows us to move this all forward a little bit.
Sorry but adding new implementations of chacha20/poly1305 without
removing the existing ones is not acceptable.  I really think
we ought to separate the zinc interface from these new crypto
implementations.  They have nothing to do with each other.

As we've been stuck on this point for so long, let's get the
ball rolling by first merging just the zinc interface itself
with the existing chacha20/poly1305 code.  Then we can replace
these implementations with your implementations without getting
bogged down by all these other discussions.

AFAICS once we resolve Thomas's concerns with regards to the simd
patch, then we can merge the zinc interface right away and go from
there.

Cheers,
-- 
Email: Herbert Xu [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Thread (32 messages) 32 messages, 6 authors, last reply 2019-03-31
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help