[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20220111171059.GA10674@srcf.ucam.org>
Date: Tue, 11 Jan 2022 17:10:59 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: "Alexander E. Patrakov" <patrakov@...il.com>
Cc: Theodore Ts'o <tytso@....edu>, Andy Lutomirski <luto@...nel.org>,
"Jason A. Donenfeld" <Jason@...c4.com>,
Marcelo Henrique Cerri <marcelo.cerri@...onical.com>,
Simo Sorce <simo@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jeffrey Walton <noloader@...il.com>,
Stephan Mueller <smueller@...onox.de>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Willy Tarreau <w@....eu>, Nicolai Stange <nstange@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Ahmed S. Darwish" <darwish.07@...il.com>,
Vito Caputo <vcaputo@...garu.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.cz>, Ray Strode <rstrode@...hat.com>,
William Jon McCann <mccann@....edu>,
zhangjs <zachary@...shancloud.com>,
Florian Weimer <fweimer@...hat.com>,
Lennart Poettering <mzxreary@...inter.de>,
Peter Matthias <matthias.peter@....bund.de>,
Neil Horman <nhorman@...hat.com>,
Randy Dunlap <rdunlap@...radead.org>,
Julia Lawall <julia.lawall@...ia.fr>,
Dan Carpenter <dan.carpenter@...cle.com>,
Andy Lavr <andy.lavr@...il.com>,
Petr Tesarik <ptesarik@...e.cz>,
John Haxby <john.haxby@...cle.com>,
Alexander Lobakin <alobakin@...lbox.org>,
Jirka Hladky <jhladky@...hat.com>,
Eric Biggers <ebiggers@...nel.org>
Subject: Re: [PATCH v43 01/15] Linux Random Number Generator
On Tue, Jan 11, 2022 at 02:57:54PM +0500, Alexander E. Patrakov wrote:
> LD_PRELOAD is not a solution because of containers and statically-linked
> binaries.
No, it doesn't solve all problems, but the question is whether it needs
to. We're talking about the scenario where:
a) a customer requires FIPS compliance, and
b) the customer has an app that calls getrandom() and doesn't fallback,
and
c) they're doing so with statically linked binaries or container
infrastructure that doesn't allow injection of other libraries
How common is this? Does the kernel need to solve this scenario?
Powered by blists - more mailing lists