The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	 Herbert Xu <herbert@gondor.apana.org.au>,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] crypto: af_alg - Make cbc(paes) privileged-only
Date: Tue, 4 Aug 2026 08:39:03 +0200 (CEST)	[thread overview]
Message-ID: <630163276.8329.1785825543421.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20260802230055.100746-2-ebiggers@kernel.org>

----- Ursprüngliche Mail -----
> Von: "Eric Biggers" <ebiggers@kernel.org>
> An: "Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>, "Herbert Xu" <herbert@gondor.apana.org.au>
> CC: "richard" <richard@nod.at>, "linux-kernel" <linux-kernel@vger.kernel.org>, "Eric Biggers" <ebiggers@kernel.org>
> Gesendet: Montag, 3. August 2026 01:00:53
> Betreff: [PATCH 1/3] crypto: af_alg - Make cbc(paes) privileged-only

> 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>

Good catch, my intention was making it privileged only. :-S

Reviewed-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard

  reply	other threads:[~2026-08-04  6:48 UTC|newest]

Thread overview: 5+ 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 [this message]
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

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=630163276.8329.1785825543421.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox