[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70ec751d-8aba-42b4-861c-e7e17c4a7476@suse.de>
Date: Wed, 25 Oct 2023 12:56:41 +0200
From: Hannes Reinecke <hare@...e.de>
To: Mark O'Donovan <shiftee@...teo.net>, linux-kernel@...r.kernel.org
Cc: linux-nvme@...ts.infradead.org, sagi@...mberg.me, hch@....de,
axboe@...nel.dk, kbusch@...nel.org
Subject: Re: [PATCH v3 3/3] nvme-auth: always set valid seq_num in dhchap
reply
On 10/25/23 12:51, Mark O'Donovan wrote:
> Currently a seqnum of zero is sent during uni-directional
> authentication. The zero value is reserved for the secure channel
> feature which is not yet implemented.
>
> Relevant extract from the spec:
> The value 0h is used to indicate that bidirectional authentication
> is not performed, but a challenge value C2 is carried in order to
> generate a pre-shared key (PSK) for subsequent establishment of a
> secure channel
>
> Signed-off-by: Mark O'Donovan <shiftee@...teo.net>
> Reviewed-by: Christoph Hellwig <hch@....de>
>
> ---
> v1: used incorrect prefix nvme-tcp
> v2: added spec extract to commit message
> v3: read the seq-num in nvme-target code
>
Reviewed-by: Hannes Reinecke <hare@...e.de>
Cheers,
Hannes
Powered by blists - more mailing lists