From: Taehee Yoo <ap420073@gmail.com>
To: 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
Cc: ap420073@gmail.com
Subject: [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm
Date: Mon, 4 Jul 2022 09:42:47 +0000 [thread overview]
Message-ID: <20220704094250.4265-1-ap420073@gmail.com> (raw)
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.
It is tested in x86 and MIPS with the tcrypt module.
The first patch is an implementation of ARIA algorithm.
The second patch adds tests for ARIA.
The third patch adds ARIA-kTLS feature.
ARIA128-kTLS Benchmark results:
openssl-3.0-dev and iperf-ssl are used.
TLS
[ 3] 0.0- 1.0 sec 185 MBytes 1.55 Gbits/sec
[ 3] 1.0- 2.0 sec 186 MBytes 1.56 Gbits/sec
[ 3] 2.0- 3.0 sec 186 MBytes 1.56 Gbits/sec
[ 3] 3.0- 4.0 sec 186 MBytes 1.56 Gbits/sec
[ 3] 4.0- 5.0 sec 186 MBytes 1.56 Gbits/sec
[ 3] 0.0- 5.0 sec 927 MBytes 1.56 Gbits/sec
kTLS
[ 3] 0.0- 1.0 sec 198 MBytes 1.66 Gbits/sec
[ 3] 1.0- 2.0 sec 194 MBytes 1.62 Gbits/sec
[ 3] 2.0- 3.0 sec 194 MBytes 1.63 Gbits/sec
[ 3] 3.0- 4.0 sec 194 MBytes 1.63 Gbits/sec
[ 3] 4.0- 5.0 sec 194 MBytes 1.62 Gbits/sec
[ 3] 0.0- 5.0 sec 974 MBytes 1.63 Gbits/sec
The previous patch version[2].
[1] https://datatracker.ietf.org/doc/html/rfc6209
[2] https://www.spinics.net/lists/linux-crypto/msg64704.html
v2:
- Add ARIA-kTLS feature.
Taehee Yoo (3):
crypto: Implement ARIA symmetric cipher algorithm
crypto: add ARIA testmgr tests
net: tls: Add ARIA-GCM algorithm
crypto/Kconfig | 15 +
crypto/Makefile | 1 +
crypto/aria.c | 288 ++++
crypto/tcrypt.c | 38 +-
crypto/testmgr.c | 31 +
crypto/testmgr.h | 2860 ++++++++++++++++++++++++++++++++++++++
include/crypto/aria.h | 461 ++++++
include/uapi/linux/tls.h | 30 +
net/tls/tls_main.c | 62 +
net/tls/tls_sw.c | 34 +
10 files changed, 3819 insertions(+), 1 deletion(-)
create mode 100644 crypto/aria.c
create mode 100644 include/crypto/aria.h
--
2.17.1
next reply other threads:[~2022-07-04 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:42 Taehee Yoo [this message]
2022-07-04 9:42 ` [PATCH v2 1/3] crypto: Implement ARIA symmetric cipher algorithm 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 ` [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=20220704094250.4265-1-ap420073@gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).