[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200901.114732.1206867680814103555.davem@davemloft.net>
Date: Tue, 01 Sep 2020 11:47:32 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: yhayakawa3720@...il.com
Cc: borisp@...lanox.com, aviadye@...lanox.com,
john.fastabend@...il.com, daniel@...earbox.net, kuba@...nel.org,
michio.honda@...ac.uk, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net/tls: Implement getsockopt SOL_TLS TLS_RX
From: Yutaro Hayakawa <yhayakawa3720@...il.com>
Date: Tue, 1 Sep 2020 22:59:45 +0900
> From: Yutaro Hayakawa <yhayakawa3720@...il.com>
>
> Implement the getsockopt SOL_TLS TLS_RX which is currently missing. The
> primary usecase is to use it in conjunction with TCP_REPAIR to
> checkpoint/restore the TLS record layer state.
>
> TLS connection state usually exists on the user space library. So
> basically we can easily extract it from there, but when the TLS
> connections are delegated to the kTLS, it is not the case. We need to
> have a way to extract the TLS state from the kernel for both of TX and
> RX side.
>
> The new TLS_RX getsockopt copies the crypto_info to user in the same
> way as TLS_TX does.
>
> We have described use cases in our research work in Netdev 0x14
> Transport Workshop [1].
>
> Also, there is an TLS implementation called tlse [2] which supports
> TLS connection migration. They have support of kTLS and their code
> shows that they are expecting the future support of this option.
>
> [1] https://speakerdeck.com/yutarohayakawa/prism-proxies-without-the-pain
> [2] https://github.com/eduardsui/tlse
>
> Signed-off-by: Yutaro Hayakawa <yhayakawa3720@...il.com>
> Reviewed-by: Jakub Kicinski <kuba@...nel.org>
Applied, thank you.
Powered by blists - more mailing lists