From: Eric Biggers <ebiggers@kernel.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Demi Marie Obenour <demiobenour@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-bluetooth@vger.kernel.org, iwd@lists.linux.dev,
linux-hardening@vger.kernel.org, Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH] crypto: af_alg - Add af_alg_restrict sysctl, defaulting to 1
Date: Tue, 30 Jun 2026 20:04:51 -0700 [thread overview]
Message-ID: <20260701030451.GA1799@sol> (raw)
In-Reply-To: <d96594ba-4ad5-4541-9660-2469875db9b7@hogyros.de>
On Wed, Jul 01, 2026 at 11:53:16AM +0900, Simon Richter wrote:
> Hi,
>
> On 7/1/26 12:54 AM, Demi Marie Obenour wrote:
>
> > That said, if the crypto_rng support is to remain, should it have a
> > non-empty allowlist for privileged processes? Otherwise, it's dead code
> > with the default sysctl value.
[...]
> I think that embedded systems will still use this code until a better
> alternative exists, so it's not entirely dead, and the best way to get rid
> of it is to build something better.
/dev/urandom, /dev/random, and /dev/hwrng. I.e. what userspace
*actually* uses already. algif_rng is a redundant, much harder to use
interface that got added off to the side for some reason.
- Eric
next prev parent reply other threads:[~2026-07-01 3:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 23:48 [PATCH] crypto: af_alg - Add af_alg_restrict sysctl, defaulting to 1 Eric Biggers
2026-06-22 23:53 ` bluez.test.bot
2026-06-23 8:42 ` [PATCH] " Bastien Nocera
2026-06-23 16:54 ` Eric Biggers
2026-06-23 15:04 ` Luiz Augusto von Dentz
2026-06-23 16:52 ` Eric Biggers
2026-06-23 17:29 ` Demi Marie Obenour
2026-06-23 17:45 ` Eric Biggers
2026-06-23 18:05 ` Eric Biggers
2026-06-23 18:51 ` Luiz Augusto von Dentz
2026-06-23 17:24 ` Demi Marie Obenour
2026-06-23 17:58 ` Eric Biggers
2026-06-23 19:12 ` Andy Lutomirski
2026-06-23 19:27 ` Eric Biggers
2026-06-24 2:09 ` Demi Marie Obenour
2026-06-28 18:54 ` Eric Biggers
2026-06-29 3:11 ` Simon Richter
2026-06-30 15:54 ` Demi Marie Obenour
2026-07-01 2:53 ` Simon Richter
2026-07-01 3:04 ` Eric Biggers [this message]
2026-06-23 19:24 ` Kees Cook
2026-06-23 19:49 ` Eric Biggers
2026-06-23 21:28 ` Rosen Penev
2026-06-23 21:47 ` Eric Biggers
2026-06-23 22:06 ` Rosen Penev
2026-07-05 8:39 ` 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=20260701030451.GA1799@sol \
--to=ebiggers@kernel.org \
--cc=Simon.Richter@hogyros.de \
--cc=demiobenour@gmail.com \
--cc=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=iwd@lists.linux.dev \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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.