From: "Theodore Ts'o" <tytso@mit.edu>
To: Simo Sorce <simo@redhat.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"nstange@suse.de" <nstange@suse.de>,
"Wang, Jay" <wanjay@amazon.com>
Subject: Re: 6.17 crashes in ipv6 code when booted fips=1 [was: [GIT PULL] Crypto Update for 6.17]
Date: Wed, 8 Oct 2025 08:13:16 -0400 [thread overview]
Message-ID: <20251008121316.GJ386127@mit.edu> (raw)
In-Reply-To: <0acd44b257938b927515034dd3954e2d36fc65ac.camel@redhat.com>
On Mon, Oct 06, 2025 at 03:45:46PM -0400, Simo Sorce wrote:
> Note: this may change going forward, but I am confident that as issues
> arise people will propose upstream patches to keep it as close as
> possible within acceptable parameters for upstream behavior.
What I'm curious about is what falls within the acceptable parameters
of *distro* behavior. If NIST-certified labs really insist that
certifying requires making the kernel completely unsupportable from a
commercial perspective, at what point will *distros* decide to give it
up as a bad idea, or to have a completely different binary kernel
package that only crazy customers would be willing to use?
If there is something beyond hard-disabling CONFIG_CRYPTO_SHA1 which
all distributions could agree with --- what would that set of patches
look like, and would it be evenly vaguely upstream acceptable. It
could even hidden behind CONFIG_BROKEN. :-)
- Ted
next prev parent reply other threads:[~2025-10-08 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aIirh_7k4SWzE-bF@gondor.apana.org.au>
[not found] ` <05b7ef65-37bb-4391-9ec9-c382d51bae4d@kernel.org>
2025-10-02 9:30 ` [GIT PULL] Crypto Update for 6.17 Herbert Xu
2025-10-02 10:05 ` Jiri Slaby
2025-10-02 10:13 ` Jiri Slaby
2025-10-02 10:57 ` 6.17 crashes in ipv6 code when booted fips=1 [was: [GIT PULL] Crypto Update for 6.17] Jiri Slaby
2025-10-02 11:27 ` Herbert Xu
2025-10-02 11:30 ` Vegard Nossum
2025-10-02 17:23 ` Eric Biggers
2025-10-06 11:53 ` Vegard Nossum
2025-10-06 16:12 ` Eric Biggers
2025-10-06 16:19 ` Linus Torvalds
2025-10-06 16:32 ` Vegard Nossum
2025-10-06 17:11 ` Linus Torvalds
2025-10-06 19:11 ` Vegard Nossum
2025-10-06 19:26 ` Eric Biggers
2025-10-06 19:45 ` Simo Sorce
2025-10-08 12:13 ` Theodore Ts'o [this message]
2025-10-08 16:15 ` Linus Torvalds
2025-10-06 20:09 ` Vegard Nossum
2025-10-06 19:29 ` Linus Torvalds
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=20251008121316.GJ386127@mit.edu \
--to=tytso@mit.edu \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nstange@suse.de \
--cc=simo@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
--cc=wanjay@amazon.com \
/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;
as well as URLs for NNTP newsgroup(s).