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]
Date:   Tue, 5 Jul 2022 12:29:02 +0800
From:   Herbert Xu <herbert@...dor.apana.org.au>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Taehee Yoo <ap420073@...il.com>, linux-crypto@...r.kernel.org,
        davem@...emloft.net, borisp@...dia.com, john.fastabend@...il.com,
        daniel@...earbox.net, edumazet@...gle.com, pabeni@...hat.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm

On Mon, Jul 04, 2022 at 08:10:09PM -0700, Jakub Kicinski wrote:
>
> Is it okay if you send the crypto patches now and the TLS support after
> the merge window? They go via different trees and we can't take the TLS
> patches until we get the crypto stuff in net-next. We could work
> something out and create a stable branch that both Herbert and us would
> pull but we're getting close to the merge window, perhaps we can just
> wait?

I need to know that you guys will take the network part of the
patch in order to accept the crypto part.  We don't add algorithms
with no in-kernel users.

As long as you are happy to take the TLS part later, we can add
the crypto parts right now.

Thanks,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Powered by blists - more mailing lists