From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH 0/2] scsi: target: minor CHAP fixes
Date: Fri, 5 Jun 2026 22:16:46 +1000 [thread overview]
Message-ID: <20260605122019.24146-1-ddiss@suse.de> (raw)
These patches resolve a couple of other issues pointed out by the
sashiko bot when reviewing a separate CHAP change:
https://sashiko.dev/#/patchset/20260521151121.808477-1-hossu.alexandru%40gmail.com
Hexadecimal CHAP_I handling appears to have been broken for over a
decade, so another option might be to pull out support for such encoded
values.
----------------------------------------------------------------
David Disseldorp (2):
scsi: target: fix hexadecimal CHAP_I handling
scsi: target: use constant-time crypto_memneq for CHAP digests
drivers/target/iscsi/iscsi_target_auth.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
next reply other threads:[~2026-06-05 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 12:16 David Disseldorp [this message]
2026-06-05 12:16 ` [PATCH 1/2] scsi: target: fix hexadecimal CHAP_I handling David Disseldorp
2026-06-05 16:02 ` Lee Duncan
2026-06-08 15:12 ` John Garry
2026-06-05 12:16 ` [PATCH 2/2] scsi: target: use constant-time crypto_memneq for CHAP digests David Disseldorp
2026-06-05 16:04 ` Lee Duncan
2026-06-09 1:38 ` [PATCH 0/2] scsi: target: minor CHAP fixes Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260605122019.24146-1-ddiss@suse.de \
--to=ddiss@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox