linux-kernel - Re: [PATCH 2/2] nvme-tcp: always set valid seq

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f96856ae-4842-8a50-dca1-2786153e491f@grimberg.me>
Date:   Tue, 29 Aug 2023 14:48:40 +0300
From:   Sagi Grimberg <sagi@...mberg.me>
To:     Mark O'Donovan <shiftee@...teo.net>, linux-kernel@...r.kernel.org
Cc:     linux-nvme@...ts.infradead.org, hch@....de, axboe@...nel.dk,
        kbusch@...nel.org, hare@...e.de
Subject: Re: [PATCH 2/2] nvme-tcp: always set valid seq_num in dhchap reply



On 8/29/23 00:20, 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.

Hannes?