From: Chris Leech <cleech@redhat.com>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH V3 0/3] iscsi: chap: introduce support for SHA1, SHA256 and SHA3-256
Date: Wed, 06 Nov 2019 03:26:51 +0000 [thread overview]
Message-ID: <20191106032651.GA7899@localhost.localdomain> (raw)
In-Reply-To: <20191028123822.5864-1-mlombard@redhat.com>
On Mon, Oct 28, 2019 at 01:38:19PM +0100, Maurizio Lombardi wrote:
> 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
> V3: rebased on top of 5.5/scsi-queue
> PATCH 3: renames initiatorchg_* variables to client_challenge_*
>
> 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 | 235 +++++++++++++++--------
> drivers/target/iscsi/iscsi_target_auth.h | 17 +-
> 2 files changed, 163 insertions(+), 89 deletions(-)
>
> --
I've tested this latest version against the latest upstream Open-iSCSI
tools and verified that all of the new digest modes negotiate and
function for mutual CHAP authentication.
Tested-by: Chris Leech <cleech@redhat.com>
Note that configfs in 5.5/scsi-queue is currently broken and you can't
actually configure the target subsystem with first applying the patch
"configfs: calculate the depth of parent item" from Honggang Li.
Also, I didn't actually put the target system into FIPS enforcing mode,
becuase that kernel failed to boot due to a FIPS self-test failure for
ofb(aes)
next prev parent reply other threads:[~2019-11-06 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 12:38 [PATCH V3 0/3] iscsi: chap: introduce support for SHA1, SHA256 and SHA3-256 Maurizio Lombardi
2019-11-06 3:26 ` Chris Leech [this message]
2019-11-06 5:15 ` 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=20191106032651.GA7899@localhost.localdomain \
--to=cleech@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox