From: Maurizio Lombardi <mlombard@redhat.com>
To: target-devel@vger.kernel.org
Subject: [PATCH V2 0/3] iscsi: chap: introduce support for SHA1, SHA256 and SHA3-256
Date: Thu, 17 Oct 2019 13:10:34 +0000 [thread overview]
Message-ID: <20191017131037.9903-1-mlombard@redhat.com> (raw)
iSCSI with the Challenge-Handshake Authentication Protocol is not FIPS compliant.
This is due to the fact that CHAP currently uses MD5 as the only supported
digest algorithm and MD5 is not allowed by FIPS.
When FIPS mode is enabled on the target server, the CHAP authentication
won't work because the target driver will be prevented from using the MD5 module.
Given that CHAP is agnostic regarding the algorithm it uses, this
patchset introduce support for three new alternatives: SHA1, SHA256 and SHA3-256.
They all have their protocol identifiers assigned by IANA:
https://www.iana.org/assignments/ppp-numbers/ppp-numbers.xml#ppp-numbers-9
Initiator-side code for open-iscsi has already been merged:
https://github.com/open-iscsi/open-iscsi/pull/170
V2: adds SHA256
Maurizio Lombardi (3):
target-iscsi: CHAP: add support to SHA1, SHA256 and SHA3-256 hash
functions
target-iscsi: tie the challenge length to the hash digest size
target-iscsi: rename some variables to avoid confusion.
drivers/target/iscsi/iscsi_target_auth.c | 232 +++++++++++++++--------
drivers/target/iscsi/iscsi_target_auth.h | 17 +-
2 files changed, 161 insertions(+), 88 deletions(-)
--
Maurizio Lombardi
next reply other threads:[~2019-10-17 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 13:10 Maurizio Lombardi [this message]
2019-10-25 0:20 ` [PATCH V2 0/3] iscsi: chap: introduce support for SHA1, SHA256 and SHA3-256 Martin K. Petersen
2019-10-25 8:58 ` Maurizio Lombardi
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=20191017131037.9903-1-mlombard@redhat.com \
--to=mlombard@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.