[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230119090016.381eb61b@kernel.org>
Date: Thu, 19 Jan 2023 09:00:16 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Sabrina Dubroca <sd@...asysnail.net>
Cc: netdev@...r.kernel.org, Frantisek Krenzelok <fkrenzel@...hat.com>,
Gal Pressman <gal@...dia.com>,
Apoorv Kothari <apoorvko@...zon.com>
Subject: Re: [PATCH net-next 0/5] tls: implement key updates for TLS1.3
On Thu, 19 Jan 2023 16:40:39 +0100 Sabrina Dubroca wrote:
> > > IIRC support for KeyUpdates is mandatory in TLS1.3, so currently the
> > > kernel can't claim to support 1.3, independent of offloading.
> >
> > The problem is that we will not be able to rekey offloaded connections.
> > For Tx it's a non-trivial problem given the current architecture.
> > The offload is supposed to be transparent, we can't fail the rekey just
> > because the TLS gotten offloaded.
>
> What's their plan when the peer sends a KeyUpdate request then? Let
> the connection break?
I believe so, yes, just open a new connection. TLS rekeying seems
to be extremely rare.
You mentioned nbd as a potential use case for kernel SW implementation.
Can nbd rekey? Is use space responding to control messages in case of
nbd?
Powered by blists - more mailing lists