linux-kernel - Re: [PATCH v4 3/3] m68k: generate new RNG seed on reboot

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: <CAHmME9qLcfT5Mjw1cudhA-zGaLUubkPCTF7trw1ek40==BwumQ@mail.gmail.com>
Date:   Mon, 26 Sep 2022 15:13:01 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
        Laurent Vivier <laurent@...ier.eu>
Subject: Re: [PATCH v4 3/3] m68k: generate new RNG seed on reboot

Hi Geert,

On Mon, Sep 26, 2022 at 1:38 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
>
> Rather than rebooting into a system with no entropy, regenerate the RNG
> seed before rebooting, so that the new system has a fresh seed.
>
> Fixes: a1ee38ab1a75 ("m68k: virt: Use RNG seed from bootinfo block")
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>

Laurent made a compelling case *against* this approach. So feel free
to drop this 3/3 patch. However, 1/3 and 2/3 should still be
committed.

Thanks,
Jason