From: Justin Forbes <jforbes@fedoraproject.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow hmac(sha512) for unpriviledged users
Date: Sat, 3 Oct 2026 11:05:31 -0600 [thread overview]
Message-ID: <asE128W4CxHDCFiB@fedora64.linuxtx.org> (raw)
In-Reply-To: <20261003161859.GA152469@quark>
On Sat, Oct 03, 2026 at 06:18:59PM +0200, Eric Biggers wrote:
> On Sat, Oct 03, 2026 at 10:03:02AM -0600, Justin M. Forbes wrote:
> > By default users cannot run sha512hmac with the current set up. This
> > is problematic because our kernel builds call this for FIPS compliance.
> > Rather than have anyone turn off af_alg_restrict all together, let's
> > allow a common use case.
> >
> > Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
>
> The fips hook in dracut was taken into account already, and it runs as
> root. So this patch shouldn't be needed. Can you clarify why you think
> it is needed?
>
> - Eric
Specifically for the case of Fedora and all Red Hat kernels, we call
sha512hmac to sign the kernel, and a couple of UKI images that are
created during the kernel build. Users on Fedora 45 and newer are now
unable to build the kernel from spec without turning off af_alg_restrict
all together, while any user can build a kernel on Fedora 44 or older.
Justin
next prev parent reply other threads:[~2026-10-03 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:03 [PATCH] Allow hmac(sha512) for unpriviledged users Justin M. Forbes
2026-10-03 16:18 ` Eric Biggers
2026-10-03 17:05 ` Justin Forbes [this message]
2026-10-03 17:37 ` Eric Biggers
2026-10-03 17:43 ` Justin Forbes
2026-10-08 8:35 ` Herbert Xu
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=asE128W4CxHDCFiB@fedora64.linuxtx.org \
--to=jforbes@fedoraproject.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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.