[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190130215757.f4hagzixalffnzte@davejwatson-mba.local>
Date: Wed, 30 Jan 2019 21:57:58 +0000
From: Dave Watson <davejwatson@...com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Dave Miller <davem@...emloft.net>
CC: Vakul Garg <vakul.garg@....com>,
Boris Pismenny <borisp@...lanox.com>,
Aviad Yehezkel <aviadye@...lanox.com>,
John Fastabend <john.fastabend@...il.com>,
Daniel Borkmann <daniel@...earbox.net>
Subject: [PATCH net-next v2 0/5] net: tls: TLS 1.3 support
This patchset adds 256bit keys and TLS1.3 support to the kernel TLS
socket.
TLS 1.3 is requested by passing TLS_1_3_VERSION in the setsockopt
call, which changes the framing as required for TLS1.3.
256bit keys are requested by passing TLS_CIPHER_AES_GCM_256 in the
sockopt. This is a fairly straightforward passthrough to the crypto
framework.
256bit keys work with both TLS 1.2 and TLS 1.3
TLS 1.3 requires a different AAD layout, necessitating some minor
refactoring. It also moves the message type byte to the encrypted
portion of the message, instead of the cleartext header as it was in
TLS1.2. This requires moving the control message handling to after
decryption, but is otherwise similar.
V1 -> V2
The first two patches were dropped, and sent separately, one as a
bugfix to the net tree.
Dave Watson (5):
net: tls: Support 256 bit keys
net: tls: Refactor tls aad space size calculation
net: tls: Refactor control message handling on recv
net: tls: Add tls 1.3 support
net: tls: Add tests for TLS 1.3
include/net/tls.h | 72 ++++++---
include/uapi/linux/tls.h | 19 +++
net/tls/tls_device.c | 5 +-
net/tls/tls_device_fallback.c | 3 +-
net/tls/tls_main.c | 36 ++++-
net/tls/tls_sw.c | 244 +++++++++++++++++++++---------
tools/testing/selftests/net/tls.c | 138 ++++++++++++++++-
7 files changed, 417 insertions(+), 100 deletions(-)
--
2.17.1
Powered by blists - more mailing lists