From: Eric Biggers <ebiggers@kernel.org>
To: David Disseldorp <ddiss@suse.de>
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
"Martin K . Petersen" <mkp@kernel.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Duncan <lduncan@suse.com>,
Alexandru Hossu <hossu.alexandru@gmail.com>
Subject: Re: [PATCH] scsi: target: iscsi: Use crypto library API
Date: Sun, 11 Oct 2026 21:12:35 +0200 [thread overview]
Message-ID: <20261011191235.GA22483@quark> (raw)
In-Reply-To: <20261011233600.5bb5d6c9.ddiss@suse.de>
On Sun, Oct 11, 2026 at 11:36:00PM +1100, David Disseldorp wrote:
> Could e.g. SHA1 also require fips filtering here in future?
It might.
> If so, would it make sense to track the fips compat status (preferably
> at build time) in chap_digest_algs?
Let's wait until there's actually more than one before generalizing it.
- Eric
next prev parent reply other threads:[~2026-10-11 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 4:48 Eric Biggers
2026-10-11 12:36 ` David Disseldorp
2026-10-11 19:12 ` Eric Biggers [this message]
2026-10-12 1:46 ` David Disseldorp
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=20261011191235.GA22483@quark \
--to=ebiggers@kernel.org \
--cc=ddiss@suse.de \
--cc=hossu.alexandru@gmail.com \
--cc=lduncan@suse.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@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
all inboxes | Powered by JetHome®