From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 1/3] crypto: af_alg - Make cbc(paes) privileged-only
Date: Sun, 2 Aug 2026 16:00:53 -0700 [thread overview]
Message-ID: <20260802230055.100746-2-ebiggers@kernel.org> (raw)
In-Reply-To: <20260802230055.100746-1-ebiggers@kernel.org>
So far the only reported use cases for cbc(paes) have involved processes
running as root. Therefore, make af_alg_restrict=1 allow only
privileged use of this algorithm for now.
Fixes: 947d62c09436 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6")
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
crypto/algif_skcipher.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c
index 4c86b1993bde..68b48d805e92 100644
--- a/crypto/algif_skcipher.c
+++ b/crypto/algif_skcipher.c
@@ -41,7 +41,7 @@ static const struct af_alg_allowlist_entry skcipher_allowlist[] = {
{ "cbc(aes)", true }, /* iwd */
{ "cbc(des)", true }, /* iwd */
{ "cbc(des3_ede)", true }, /* iwd */
- { "cbc(paes)", false }, /* caam and others */
+ { "cbc(paes)", true }, /* caam and others */
{ "ctr(aes)", true }, /* iwd */
{ "ecb(aes)", true }, /* iwd, bluez */
{ "ecb(des)", true }, /* iwd */
--
2.55.0
next prev parent reply other threads:[~2026-08-02 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 23:00 [PATCH 0/3] crypto: af_alg_restrict cleanups Eric Biggers
2026-08-02 23:00 ` Eric Biggers [this message]
2026-08-04 6:39 ` [PATCH 1/3] crypto: af_alg - Make cbc(paes) privileged-only Richard Weinberger
2026-08-02 23:00 ` [PATCH 2/3] crypto: af_alg - Replace 'bool privileged' with flags Eric Biggers
2026-08-02 23:00 ` [PATCH 3/3] crypto: af_alg - Stop after finding name in allowlist Eric Biggers
2026-08-10 8:36 ` [PATCH 0/3] crypto: af_alg_restrict cleanups 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=20260802230055.100746-2-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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.