From: David Miller <davem@davemloft.net>
To: davejwatson@fb.com
Cc: netdev@vger.kernel.org, vakul.garg@nxp.com, borisp@mellanox.com,
aviadye@mellanox.com, john.fastabend@gmail.com,
daniel@iogearbox.net
Subject: Re: [PATCH net-next v2 0/5] net: tls: TLS 1.3 support
Date: Fri, 01 Feb 2019 15:01:35 -0800 (PST) [thread overview]
Message-ID: <20190201.150135.2232426583404883022.davem@davemloft.net> (raw)
In-Reply-To: <20190130215757.f4hagzixalffnzte@davejwatson-mba.local>
From: Dave Watson <davejwatson@fb.com>
Date: Wed, 30 Jan 2019 21:57:58 +0000
> 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.
Series applied, thanks Dave.
I'll push this out to net-next once my build testing completes.
Thanks again.
prev parent reply other threads:[~2019-02-01 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 21:57 [PATCH net-next v2 0/5] net: tls: TLS 1.3 support Dave Watson
2019-02-01 23:01 ` David Miller [this message]
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=20190201.150135.2232426583404883022.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vakul.garg@nxp.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