Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 23 Dec 2020 17:00:57 +0100
From:   Petr Tesarik <ptesarik@suse.cz>
To:     "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc:     Torsten Duwe <duwe@lst.de>,
        Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
        "Theodore Y. Ts'o" <tytso@mit.edu>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Stephan =?UTF-8?B?TcO8bGxlcg==?= <smueller@chronox.de>,
        Willy Tarreau <w@1wt.eu>,
        Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
        Nicolai Stange <nstange@suse.de>,
        LKML <linux-kernel@vger.kernel.org>,
        Arnd Bergmann <arnd@arndb.de>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        "Alexander E. Patrakov" <patrakov@gmail.com>,
        "Ahmed S. Darwish" <darwish.07@gmail.com>,
        Matthew Garrett <mjg59@srcf.ucam.org>,
        Vito Caputo <vcaputo@pengaru.com>,
        Andreas Dilger <adilger.kernel@dilger.ca>,
        Jan Kara <jack@suse.cz>, Ray Strode <rstrode@redhat.com>,
        William Jon McCann <mccann@jhu.edu>,
        zhangjs <zachary@baishancloud.com>,
        Andy Lutomirski <luto@kernel.org>,
        Florian Weimer <fweimer@redhat.com>,
        Lennart Poettering <mzxreary@0pointer.de>,
        Peter Matthias <matthias.peter@bsi.bund.de>,
        Neil Horman <nhorman@redhat.com>,
        Randy Dunlap <rdunlap@infradead.org>,
        Julia Lawall <julia.lawall@inria.fr>,
        Dan Carpenter <dan.carpenter@oracle.com>,
        And y Lavr <andy.lavr@gmail.com>,
        Eric Biggers <ebiggers@kernel.org>,
        Ard Biesheuvel <ardb@kernel.org>, simo@redhat.com
Subject: Re: drivers/char/random.c needs a (new) maintainer
Message-ID: <20201223170057.7c8fd710@ezekiel.suse.cz>
In-Reply-To: <CAHmME9ooV1HRGO4bLsNKqv1EjDsUYsM6TcMbmEL=4CejTB+1ZQ@mail.gmail.com>
References: <20201130151231.GA24862@lst.de>
        <CAHmME9p4vFGWh7+CKF4f3dw5r+ru5PVG0-vP77JowX8sPhin1g@mail.gmail.com>
        <20201130165339.GE5364@mit.edu>
        <CAHmME9pksS8ec17RAwCNJimt4B0xZgd3qYHUPnaT4Bj4CF7n0A@mail.gmail.com>
        <20201218132519.kj3nz7swsx7vvlr5@valinor.lan>
        <20201223132851.55d19271@blackhole.lan>
        <20201223151014.57caf98b@ezekiel.suse.cz>
        <CAHmME9ooV1HRGO4bLsNKqv1EjDsUYsM6TcMbmEL=4CejTB+1ZQ@mail.gmail.com>
Organization: SUSE Linux, s.r.o.
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/Z+YdJ+mMHvgvuEAz.pJLK3V";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/Z+YdJ+mMHvgvuEAz.pJLK3V
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Wed, 23 Dec 2020 15:32:55 +0100
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> On Wed, Dec 23, 2020 at 3:17 PM Petr Tesarik <ptesarik@suse.cz> wrote:
> > Upfront, let me admit that SUSE has a vested interest in a FIPS-certifi=
able Linux kernel. =20
>=20
> Sorry, but just because you have a "vested interest", or a financial
> interest, or because you want it does not suddenly make it a good
> idea. The idea is to have good crypto, not to merely check some boxes

I never suggested that this should serve as a supportive argument. I was ju=
st trying to be honest about our motivations.

I'm a bit sad that this discussion has quickly gone back to the choice of a=
lgorithms and how they can be implemented. The real issue is that the RNG s=
ubsystem has not developed as fast as it could. This had not been much of a=
n issue as long as nobody was really interested in making any substantial c=
hanges to that code, but it is more apparent now. Torsten believes it can b=
e partly because of a maintainer who is too busy with other tasks, and he s=
uggested we try to improve the situation by giving the RNG-related tasks to=
 someone else.

I have not seen a clear answer to this suggestion, except Jason offering hi=
s helping hand with Nicolai's cleanup patches, but nothing wrt Stephan's pa=
tches. So, what is the plan?

Petr Tesarik
SUSE HW Enablement Team

--Sig_/Z+YdJ+mMHvgvuEAz.pJLK3V
Content-Type: application/pgp-signature
Content-Description: Digitální podpis OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEHl2YIZkIo5VO2MxYqlA7ya4PR6cFAl/jabkACgkQqlA7ya4P
R6cEBgf+PcUW8Z/pkOT7Dc2JOAZJ5iMJXmOEGKLvG42J6pZ5P7f00bw7KP8fCBty
H56op4nW/kpSJ57neekDzz0w84iaQwtSNCgBvpaDWayIXurrEcPNzpQknLSR8NHX
qVfwQO6lLmYRJPHMcVHdiwDAD50mBzVpNuCCfJjQNVeVJXT5Qcq0H0cvj9WtU7HP
IxxnEZmC++fukffpZvW3E4cBntb6BPTT3nVtQwKHcUPLgSNsnojKhCPYIxse8Tzz
vum5nMTlhNhxnHkcblfqnk0Cnp9eS2eM6OeYlNQ+4LK1gF0ZcBvjBNCeoLw/5Nbx
/1rXFSsJ8UsuJ9Wh1e0paTx8iyeVpA==
=Sd6I
-----END PGP SIGNATURE-----

--Sig_/Z+YdJ+mMHvgvuEAz.pJLK3V--