public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: Taehee Yoo <ap420073@gmail•com>,
	linux-crypto@vger•kernel.org, davem@davemloft•net,
	borisp@nvidia•com, john.fastabend@gmail•com,
	daniel@iogearbox•net, edumazet@google•com, pabeni@redhat•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm
Date: Tue, 5 Jul 2022 11:31:02 -0700	[thread overview]
Message-ID: <20220705113102.1862660a@kernel.org> (raw)
In-Reply-To: <YsO+DmGe7LdGUmUE@gondor.apana.org.au>

On Tue, 5 Jul 2022 12:29:02 +0800 Herbert Xu wrote:
> 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.

GTK, I thought maybe using crypto sockets is enough of a reason.

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

Yup, can confirm. I haven't heard of this algo before but the IETF
RFC looks legit so we'll take the TLS part.

  reply	other threads:[~2022-07-05 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  9:42 [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm Taehee Yoo
2022-07-04  9:42 ` [PATCH v2 1/3] crypto: Implement " Taehee Yoo
2022-07-04  9:42 ` [PATCH v2 2/3] crypto: add ARIA testmgr tests Taehee Yoo
2022-07-04  9:42 ` [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm Taehee Yoo
2022-07-05  3:10   ` Jakub Kicinski
2022-07-05  4:29     ` Herbert Xu
2022-07-05 18:31       ` Jakub Kicinski [this message]
2022-07-09 22:32 ` [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm Eric Biggers
2022-07-10  8:08   ` Taehee Yoo
2022-07-15  8:46 ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220705113102.1862660a@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=ap420073@gmail$(echo .)com \
    --cc=borisp@nvidia$(echo .)com \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox