From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] crypto: af_alg_restrict cleanups
Date: Mon, 10 Aug 2026 18:36:26 +1000 [thread overview]
Message-ID: <anmNigs3W1DwtTLG@gondor.apana.org.au> (raw)
In-Reply-To: <20260802230055.100746-1-ebiggers@kernel.org>
On Sun, Aug 02, 2026 at 04:00:52PM -0700, Eric Biggers wrote:
> - Make cbc(paes) privileged-only for now, as previously discussed
> - Make it more explicit when unprivileged use is allowed
> - Avoid some redundant work during allowlist checking
>
> Eric Biggers (3):
> crypto: af_alg - Make cbc(paes) privileged-only
> crypto: af_alg - Replace 'bool privileged' with flags
> crypto: af_alg - Stop after finding name in allowlist
>
> crypto/af_alg.c | 10 +++++++---
> crypto/algif_aead.c | 2 +-
> crypto/algif_hash.c | 28 ++++++++++++++--------------
> crypto/algif_skcipher.c | 28 ++++++++++++++--------------
> include/crypto/if_alg.h | 6 +++++-
> 5 files changed, 41 insertions(+), 33 deletions(-)
>
>
> base-commit: 947d62c094367ef6064907d570b47612cd579df6
> --
> 2.55.0
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-08-10 8:36 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 ` [PATCH 1/3] crypto: af_alg - Make cbc(paes) privileged-only Eric Biggers
2026-08-04 6:39 ` 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 ` Herbert Xu [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=anmNigs3W1DwtTLG@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ebiggers@kernel.org \
--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.