[PATCHv14 00/10] nvme: implement secure concatenation

Sagi Grimberg sagi at grimberg.me
Thu Jan 23 14:13:07 PST 2025




On 22/01/2025 18:58, Hannes Reinecke wrote:
> Hi all,
>
> here's my attempt to implement secure concatenation for NVMe-of TCP
> as outlined in TP8018.
> The original (v5) patchset had been split in two, the first part of
> which has already been merged with nvme-6.11, and this is the second part
> which actually implements secure concatenation.
>
> Secure concatenation means that a TLS PSK is generated from the key
> material negotiated by the DH-HMAC-CHAP protocol, and the TLS PSK
> is then used for a subsequent TLS connection.
> The difference between the original definition of secure concatenation
> and the method outlined in TP8018 is that with TP8018 the connection
> is reset after DH-HMAC-CHAP negotiation, and a new connection is setup
> with the generated TLS PSK.
>
> To implement that Sagi came up with the idea to directly reset the
> admin queue once the DH-CHAP negotiation has completed; that way
> it will be transparent to the upper layers and we don't have to
> worry about exposing queues which should not be used.
>
> A blktest submission is in
> https://github.com/osandov/blktests/pull/158
> in case anyone want to run their own tests.
>
> As usual, comments and reviews are welcome.

Looks good. already reviewed.



More information about the Linux-nvme mailing list