lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20231025105125.134443-1-shiftee@posteo.net> Date: Wed, 25 Oct 2023 10:51:22 +0000 From: Mark O'Donovan <shiftee@...teo.net> To: linux-kernel@...r.kernel.org Cc: linux-nvme@...ts.infradead.org, sagi@...mberg.me, hch@....de, axboe@...nel.dk, kbusch@...nel.org, hare@...e.de, Mark O'Donovan <shiftee@...teo.net> Subject: [PATCH v3 0/3] nvme-tcp: always set valid seq_num in dhchap reply The first patch is a small unrelated fix which makes it clear that the response data section of the Success1 message is not optional. The second patch removes use of the host sequence number (S2) as an indicator of bi-directional authentication. The third patch causes us to always set the host sequence number (S2) to a non-zero value instead of the 0 value reserved for the secure channel feature. v1: original submission v2: rebased + added dedicated variable for bi-directional auth v3: nvme-target code now reads seq-num Mark O'Donovan (3): nvme-auth: auth success1 msg always includes resp nvme-auth: add flag for bi-directional auth nvme-auth: always set valid seq_num in dhchap reply drivers/nvme/host/auth.c | 13 ++++++------- drivers/nvme/target/fabrics-cmd-auth.c | 2 +- include/linux/nvme.h | 2 +- 3 files changed, 8 insertions(+), 9 deletions(-) base-commit: 4f82870119a46b0d04d91ef4697ac4977a255a9d -- 2.39.2
Powered by blists - more mailing lists