From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Milan Broz <gmazyland@gmail.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH] crypto: af_alg - Allow additional ciphers for cryptsetup
Date: Sun, 5 Jul 2026 11:44:19 -0700 [thread overview]
Message-ID: <20260705184419.40762-1-ebiggers@kernel.org> (raw)
Add "xts(camellia)", "xts(serpent)", and "xts(twofish)" to the allowlist
for af_alg_restrict=1. These niche AES alternatives have continued to
see rare but persistent use via cryptsetup, which has historically
relied on the AF_ALG support for these ciphers in XTS mode for
performing the keyslot encryption. (cryptsetup v2.8.7 and later fall
back to a temporary dm-crypt mapping, but that requires root.)
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
crypto/algif_skcipher.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c
index 2b8069667974..49ae779b3b6b 100644
--- a/crypto/algif_skcipher.c
+++ b/crypto/algif_skcipher.c
@@ -45,6 +45,9 @@ static const struct af_alg_allowlist_entry skcipher_allowlist[] = {
{ "ecb(des)", true }, /* iwd */
{ "hctr2(aes)", false }, /* cryptsetup */
{ "xts(aes)", false }, /* cryptsetup benchmark */
+ { "xts(camellia)", false }, /* cryptsetup */
+ { "xts(serpent)", false }, /* cryptsetup */
+ { "xts(twofish)", false }, /* cryptsetup */
{},
};
base-commit: e264401ce4776a288524e5b87593d4d864147115
--
2.54.0
next reply other threads:[~2026-07-05 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 18:44 Eric Biggers [this message]
2026-07-06 18:20 ` [PATCH] crypto: af_alg - Allow additional ciphers for cryptsetup Milan Broz
2026-07-06 20:24 ` Eric Biggers
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=20260705184419.40762-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@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.