netdev - Re: [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm

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: <20220704201009.34fb8aa8@kernel.org>
Date:   Mon, 4 Jul 2022 20:10:09 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Taehee Yoo <ap420073@...il.com>
Cc:     linux-crypto@...r.kernel.org, herbert@...dor.apana.org.au,
        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,  4 Jul 2022 09:42:50 +0000 Taehee Yoo wrote:
> RFC 6209 describes ARIA for TLS 1.2.
> ARIA-128-GCM and ARIA-256-GCM are defined in RFC 6209.
> 
> This patch would offer performance increment and an opportunity for
> hardware offload.

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?