From: Eric Biggers <ebiggers@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, borisp@nvidia.com, john.fastabend@gmail.com,
daniel@iogearbox.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm
Date: Sat, 9 Jul 2022 15:32:20 -0700 [thread overview]
Message-ID: <YsoB9LBXOLEdV/2e@sol.localdomain> (raw)
In-Reply-To: <20220704094250.4265-1-ap420073@gmail.com>
On Mon, Jul 04, 2022 at 09:42:47AM +0000, Taehee Yoo wrote:
> This patchset adds a new ARIA(RFC 5794) symmetric cipher algorithm.
>
> Like SEED, the ARIA is a standard cipher algorithm in South Korea.
> Especially Government and Banking industry have been using this algorithm.
> So the implementation of ARIA will be useful for them and network vendors.
>
> Usecases of this algorithm are TLS[1], and IPSec.
Is this actually going to be used in the real world, or is this just a PhD
thesis sort of thing? There are already way too many random crypto algorithms
that are supported in the kernel, and many have been removed due to lack of
users -- implying that they should never have been accepted in the first place.
- Eric
next prev parent reply other threads:[~2022-07-09 22:32 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
2022-07-09 22:32 ` Eric Biggers [this message]
2022-07-10 8:08 ` [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm 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=YsoB9LBXOLEdV/2e@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ap420073@gmail.com \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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