lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 23 Dec 2020 15:10:14 +0100
From:   Petr Tesarik <>
To:     Torsten Duwe <>
Cc:     Marcelo Henrique Cerri <>,
        "Jason A. Donenfeld" <>,
        "Theodore Y. Ts'o" <>,
        Linus Torvalds <>,
        Stephan Müller <>,
        Willy Tarreau <>,
        Linux Crypto Mailing List <>,
        Nicolai Stange <>,
        LKML <>,
        Arnd Bergmann <>,
        "Eric W. Biederman" <>,
        "Alexander E. Patrakov" <>,
        "Ahmed S. Darwish" <>,
        Matthew Garrett <>,
        Vito Caputo <>,
        Andreas Dilger <>,
        Jan Kara <>, Ray Strode <>,
        William Jon McCann <>,
        zhangjs <>,
        Andy Lutomirski <>,
        Florian Weimer <>,
        Lennart Poettering <>,
        Peter Matthias <>,
        Neil Horman <>,
        Randy Dunlap <>,
        Julia Lawall <>,
        Dan Carpenter <>,
        And y Lavr <>,
        Eric Biggers <>,
        Ard Biesheuvel <>,
Subject: Re: drivers/char/random.c needs a (new) maintainer

On Wed, 23 Dec 2020 13:28:51 +0100
Torsten Duwe <> wrote:

> > collaboration and disengage people. More than simply reviewing patches
> > I would expect a maintainer to give directions and drive the
> > community. Asking Jason to review Nicolai's patches was a step towards
> > that, but I believe we still could benefit from better communication.  
> Even regarding this I'm not so sure it was a good idea. Jason seems to
> narrow the proposed changes down to "FIPS certification", when it
> actually is a lot more. I think his motivation suffers because of his
> personal dislike.

Upfront, let me admit that SUSE has a vested interest in a FIPS-certifiable Linux kernel.

However, it seems to me that nobody can be happy about keeping the current status quo forever. Even in the hypothetical case that the RNG maintainer rejected the whole idea merely because it makes it possible to achieve NIST compliance, and he detests standards compliance, it would still be better than no decision at all. The silence is paralyzing, as it blocks any changes in upstream, while also making it difficult to maintain an out-of-tree implementation that aims at becoming upstream eventually.

The only option ATM is a fork (similar to what the Xen folks did with XenLinux many years ago). IOW the current situation demotivates contributors from being good citizens. I hope we can find a better solution together.

Petr Tesarik
SUSE HW Enablement Team

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists