From: patchwork-bot+netdevbpf@kernel.org
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, vfedorenko@novek.ru, fkrenzel@redhat.com,
kuba@kernel.org, kuniyu@amazon.com, apoorvko@amazon.com,
borisp@nvidia.com, john.fastabend@gmail.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, gal@nvidia.com,
marcel@holtmann.org, horms@kernel.org,
Parthiban.Veerasooran@microchip.com
Subject: Re: [PATCH net-next v5 0/6] tls: implement key updates for TLS1.3
Date: Mon, 16 Dec 2024 12:50:31 +0000 [thread overview]
Message-ID: <173435343108.197327.447831770899898017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1734013874.git.sd@queasysnail.net>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 12 Dec 2024 16:36:03 +0100 you wrote:
> This adds support for receiving KeyUpdate messages (RFC 8446, 4.6.3
> [1]). A sender transmits a KeyUpdate message and then changes its TX
> key. The receiver should react by updating its RX key before
> processing the next message.
>
> This patchset implements key updates by:
> 1. pausing decryption when a KeyUpdate message is received, to avoid
> attempting to use the old key to decrypt a record encrypted with
> the new key
> 2. returning -EKEYEXPIRED to syscalls that cannot receive the
> KeyUpdate message, until the rekey has been performed by userspace
> 3. passing the KeyUpdate message to userspace as a control message
> 4. allowing updates of the crypto_info via the TLS_TX/TLS_RX
> setsockopts
>
> [...]
Here is the summary with links:
- [net-next,v5,1/6] tls: block decryption when a rekey is pending
https://git.kernel.org/netdev/net-next/c/0471b1093e3a
- [net-next,v5,2/6] tls: implement rekey for TLS1.3
https://git.kernel.org/netdev/net-next/c/47069594e67e
- [net-next,v5,3/6] tls: add counters for rekey
https://git.kernel.org/netdev/net-next/c/510128b30f2d
- [net-next,v5,4/6] docs: tls: document TLS1.3 key updates
https://git.kernel.org/netdev/net-next/c/5aa97a43d042
- [net-next,v5,5/6] selftests: tls: add key_generation argument to tls_crypto_info_init
https://git.kernel.org/netdev/net-next/c/b2e584aa3c71
- [net-next,v5,6/6] selftests: tls: add rekey tests
https://git.kernel.org/netdev/net-next/c/555f0edb9ff0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-12-16 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 15:36 [PATCH net-next v5 0/6] tls: implement key updates for TLS1.3 Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 1/6] tls: block decryption when a rekey is pending Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 2/6] tls: implement rekey for TLS1.3 Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 3/6] tls: add counters for rekey Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 4/6] docs: tls: document TLS1.3 key updates Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 5/6] selftests: tls: add key_generation argument to tls_crypto_info_init Sabrina Dubroca
2024-12-12 15:36 ` [PATCH net-next v5 6/6] selftests: tls: add rekey tests Sabrina Dubroca
2024-12-16 12:50 ` patchwork-bot+netdevbpf [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=173435343108.197327.447831770899898017.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=apoorvko@amazon.com \
--cc=borisp@nvidia.com \
--cc=fkrenzel@redhat.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=shuah@kernel.org \
--cc=vfedorenko@novek.ru \
/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).