From: Vadim Fedorenko <vfedorenko@novek.ru>
To: Jakub Kicinski <kuba@kernel.org>,
Boris Pismenny <borisp@nvidia.com>,
Aviad Yehezkel <aviadye@nvidia.com>
Cc: Vadim Fedorenko <vfedorenko@novek.ru>, netdev@vger.kernel.org
Subject: [net-next 0/5] Add CHACHA20-POLY1305 cipher to Kernel TLS
Date: Sun, 22 Nov 2020 04:57:40 +0300 [thread overview]
Message-ID: <1606010265-30471-1-git-send-email-vfedorenko@novek.ru> (raw)
RFC 7905 defines usage of ChaCha20-Poly1305 in TLS connections. This
cipher is widely used nowadays and it's good to have a support for it
in TLS connections in kernel
Vadim Fedorenko (5):
net/tls: make inline helpers protocol-aware
net/tls: add CHACHA20-POLY1305 specific defines and structures
net/tls: add CHACHA20-POLY1305 specific behavior
net/tls: add CHACHA20-POLY1305 configuration
selftests/tls: add CHACHA20-POLY1305 to tls selftests
include/net/tls.h | 32 ++++++++++++++++---------------
include/uapi/linux/tls.h | 15 +++++++++++++++
net/tls/tls_device.c | 2 +-
net/tls/tls_device_fallback.c | 13 +++++++------
net/tls/tls_main.c | 3 +++
net/tls/tls_sw.c | 36 ++++++++++++++++++++++++++---------
tools/testing/selftests/net/tls.c | 40 ++++++++++++++++++++++++++++++++-------
7 files changed, 103 insertions(+), 38 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-11-22 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 1:57 Vadim Fedorenko [this message]
2020-11-22 1:57 ` [net-next 1/5] net/tls: make inline helpers protocol-aware Vadim Fedorenko
2020-11-22 1:57 ` [net-next 2/5] net/tls: add CHACHA20-POLY1305 specific defines and structures Vadim Fedorenko
2020-11-22 1:57 ` [net-next 3/5] net/tls: add CHACHA20-POLY1305 specific behavior Vadim Fedorenko
2020-11-22 1:57 ` [net-next 4/5] net/tls: add CHACHA20-POLY1305 configuration Vadim Fedorenko
2020-11-24 2:12 ` Jakub Kicinski
2020-11-22 1:57 ` [net-next 5/5] selftests/tls: add CHACHA20-POLY1305 to tls selftests Vadim Fedorenko
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=1606010265-30471-1-git-send-email-vfedorenko@novek.ru \
--to=vfedorenko@novek.ru \
--cc=aviadye@nvidia.com \
--cc=borisp@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.