nvme-auth: always set valid seq_num in dhchap reply

Browse source

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@posteo.net>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Hannes Reinecke <hare@suse.de>

...

This commit is contained in:

Mark O'Donovan 2023-10-25 10:51:25 +00:00 • committed by Keith Busch

parent fc1e03eaca

commit 6f66d046ea

2 changed files with 2 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/nvme/host/auth.c

View file

2

drivers/nvme/target/fabrics-cmd-auth.c

View file