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 16:22:22 +0100
From:   Stephan Mueller <>
To:     "Jason A. Donenfeld" <>,
        Petr Tesarik <>
Cc:     Torsten Duwe <>,
        Marcelo Henrique Cerri <>,
        "Theodore Y. Ts'o" <>,
        Linus Torvalds <>,
        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

Am Mittwoch, dem 23.12.2020 um 15:32 +0100 schrieb Jason A. Donenfeld:
> I would, however, be interested in a keccak-based construction. But
> just using the keccak permutation does not automatically make it
> "SHA-3", so we're back at the same issue again. FIPS is simply not
> interesting for our requirements.

Your requirements? Interesting approach.

Using non-assessed cryptography? Sounds dangerous to me even though it may be
based on some well-known construction.

I thought Linux in general and crypto in particular is about allowing user (or
the vendor) to decide about the used algorithm. So, let us have a mechanism
that gives them this freedom.

Thus the proposed idea sounds to me like a dangerous proposition upon which
almost all cryptography shall rest. This will surely invite even more


PS: This entire discussion is NOT about the crypto side of the random numbers,
but about how get the entropy for the random numbers.

Powered by blists - more mailing lists