From: Jiri Slaby <jirislaby@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
netdev@vger.kernel.org
Subject: Re: [GIT PULL] Crypto Update for 6.17
Date: Thu, 2 Oct 2025 12:05:03 +0200 [thread overview]
Message-ID: <562363e8-ea90-4458-9f97-1b1cb433c863@kernel.org> (raw)
In-Reply-To: <aN5GO1YLO_yXbMNH@gondor.apana.org.au>
On 02. 10. 25, 11:30, Herbert Xu wrote:
> On Thu, Oct 02, 2025 at 10:10:41AM +0200, Jiri Slaby wrote:
>> On 29. 07. 25, 13:07, Herbert Xu wrote:
>>> Vegard Nossum (1):
>>> crypto: testmgr - desupport SHA-1 for FIPS 140
>>
>> Booting 6.17 with fips=1 crashes with this commit -- see below.
>>
>> The crash is different being on 6.17 (below) and on the commit --
>> 9d50a25eeb05c45fef46120f4527885a14c84fb2.
>>
>> 6.17 minus that one makes it work again.
>>
>> Any ideas?
>
> The purpose of the above commit is to remove the SHA1 algorithm
> if you boot with fips=1. As net/ipv6/seg6_hmac.c depends on the
> sha1 algorithm, it will obviously fail if SHA1 isn't there.
Ok, but I don't immediately see what is one supposed to do to boot 6.17
distro (openSUSE) kernel with fips=1 then?
--
js
suse labs
next prev parent reply other threads:[~2025-10-02 10:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 11:07 Herbert Xu
2025-07-31 17:54 ` pr-tracker-bot
2025-10-02 8:10 ` Jiri Slaby
2025-10-02 9:30 ` Herbert Xu
2025-10-02 10:05 ` Jiri Slaby [this message]
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
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=562363e8-ea90-4458-9f97-1b1cb433c863@kernel.org \
--to=jirislaby@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.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
all inboxes | Powered by JetHome®