linux-kernel - Re: [GIT PULL] random number generator fixes for 5.17-rc1

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wj-DoruDmbAojOJ=VtpZG6piwbRJXO1N1Uq6uX7Q4UVoA@mail.gmail.com>
Date:   Wed, 19 Jan 2022 10:49:23 +0200
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] random number generator fixes for 5.17-rc1

On Tue, Jan 18, 2022 at 6:49 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
>
> 1) Some Kconfig changes resulted in BIG_KEYS being unselectable, which Justin
>    sent a patch to fix.

Ugh. I think the old "don't ask" model was the correct one, and
BIG_KEYS is probably broken (ie it should just select whatever crypto
it wants, not depend on people having selected it).

But I've taken this.

On a tangential note - looking at the resulting config file, I do note
that 'CRYPTO_LIB_POLY1305_RSIZE' should probably depend on
CRYPTO_LIB_POLY1305, because right now that sily thing gets set
whether POLY1305 is enabled or not.

That was true before too, of course - not related to this pull except
in the "this caused me to look at the end result" sense.

              Linus