diff options
| author | Mark O'Donovan <shiftee@posteo.net> | 2023-10-25 10:51:25 +0000 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2023-11-06 08:34:20 -0800 |
| commit | 6f66d046eade7a5b979e349ac52026ddfe2776b3 (patch) | |
| tree | a42ceaa1ce98c46079fcdb3b4b5b4c76881d0836 /drivers/nvme/host/auth.c | |
| parent | fc1e03eacac8e5ff8664ce2ebadabba8604f09f4 (diff) | |
| download | lwn-6f66d046eade7a5b979e349ac52026ddfe2776b3.tar.gz lwn-6f66d046eade7a5b979e349ac52026ddfe2776b3.zip | |
nvme-auth: always set valid seq_num in dhchap reply
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>
Diffstat (limited to 'drivers/nvme/host/auth.c')
| -rw-r--r-- | drivers/nvme/host/auth.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/nvme/host/auth.c b/drivers/nvme/host/auth.c index bff2b2c3cd79..48328e36e93b 100644 --- a/drivers/nvme/host/auth.c +++ b/drivers/nvme/host/auth.c @@ -316,15 +316,14 @@ static int nvme_auth_set_dhchap_reply_data(struct nvme_ctrl *ctrl, chap->bi_directional = true; get_random_bytes(chap->c2, chap->hash_len); data->cvalid = 1; - chap->s2 = nvme_auth_get_seqnum(); memcpy(data->rval + chap->hash_len, chap->c2, chap->hash_len); dev_dbg(ctrl->device, "%s: qid %d ctrl challenge %*ph\n", __func__, chap->qid, (int)chap->hash_len, chap->c2); } else { memset(chap->c2, 0, chap->hash_len); - chap->s2 = 0; } + chap->s2 = nvme_auth_get_seqnum(); data->seqnum = cpu_to_le32(chap->s2); if (chap->host_key_len) { dev_dbg(ctrl->device, "%s: qid %d host public key %*ph\n", |