From: Eric Biggers <ebiggers@kernel.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
demiobenour@gmail.com, davem@davemloft.net,
herbert@gondor.apana.org.au, upstream+linux@sigma-star.at
Subject: Re: [PATCH] crypto: af_alg: Allow cbc(paes)
Date: Mon, 27 Jul 2026 18:25:11 +0000 [thread overview]
Message-ID: <20260727182511.GA1021387@google.com> (raw)
In-Reply-To: <20260726192716.2351505-1-richard@nod.at>
On Sun, Jul 26, 2026 at 09:27:16PM +0200, Richard Weinberger wrote:
> Commit 7524070f26d8 ("crypto: af_alg - Drop support for off-CPU cryptography")
> breaks a special use case. The cbc-paes-caam driver implements the
> algorithm cbc(paes), it offers a way to use AES in CBC mode with key
> material unknown to userspace. Instead of an AES key a CAAM BLOB is
> passed to the kernel. So, this crypto operation cannot be
> implemented in a userspace library and needs always help from the
> kernel.
>
> Explicitly allow this use case.
>
> Cc: Demi Marie Obenour <demiobenour@gmail.com>
> Suggested-by: Eric Biggers <ebiggers@kernel.org>
> Fixes: 7524070f26d8 ("crypto: af_alg - Drop support for off-CPU cryptography")
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> crypto/algif_skcipher.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c
> index df20bdfe1f1f..035fed7db81f 100644
> --- a/crypto/algif_skcipher.c
> +++ b/crypto/algif_skcipher.c
> @@ -32,6 +32,7 @@
> #include <linux/mm.h>
> #include <linux/module.h>
> #include <linux/net.h>
> +#include <linux/string.h>
> #include <net/sock.h>
>
> static int skcipher_sendmsg(struct socket *sock, struct msghdr *msg,
> @@ -309,7 +310,12 @@ static struct proto_ops algif_skcipher_ops_nokey = {
>
> static void *skcipher_bind(const char *name)
> {
> - return crypto_alloc_skcipher(name, 0, AF_ALG_CRYPTOAPI_MASK);
> + u32 mask = AF_ALG_CRYPTOAPI_MASK;
> +
> + if (strcmp(name, "cbc(paes)") == 0)
> + mask = 0;
> +
> + return crypto_alloc_skcipher(name, 0, mask);
> }
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
I'll note that this overrides userspace's request if they call bind()
with salg_feat=0 && salg_mask=CRYPTO_ALG_KERN_DRIVER_ONLY, expressing an
intent to exclude algorithms that have CRYPTO_ALG_KERN_DRIVER_ONLY set.
However, it doesn't make sense to request that with "cbc(paes)". Also,
salg_feat and salg_mask seem to be de facto unused anyway: the only
supported flag has ever been CRYPTO_ALG_KERN_DRIVER_ONLY; alg_bind()
returns -EINVAL on anything else. And it isn't even declared in a UAPI
header. I think every use of AF_ALG I've seen uses salg_feat=0 &&
salg_mask=0, usually by leaving those fields default-zero-initialized.
So we could go a bit further and integrate this correctly with the
salg_feat and salg_mask. But I wouldn't consider it essential.
- Eric
prev parent reply other threads:[~2026-07-27 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 19:27 [PATCH] crypto: af_alg: Allow cbc(paes) Richard Weinberger
2026-07-27 18:25 ` Eric Biggers [this message]
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=20260727182511.GA1021387@google.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=demiobenour@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=upstream+linux@sigma-star.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox