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
| ||
|
Message-ID: <20221001160910.GB13443@alpha.franken.de> Date: Sat, 1 Oct 2022 18:09:10 +0200 From: Thomas Bogendoerfer <tsbogend@...ha.franken.de> To: "Jason A. Donenfeld" <Jason@...c4.com> Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mips: allow firmware to pass RNG seed to kernel On Fri, Sep 30, 2022 at 04:01:38PM +0200, Jason A. Donenfeld wrote: > Nearly all other firmware environments have some way of passing a RNG > seed to initialize the RNG: DTB's rng-seed, EFI's RNG protocol, m68k's > bootinfo block, x86's setup_data, and so forth. This adds something > similar for MIPS, which will allow various firmware environments, > bootloaders, and hypervisors to pass an RNG seed to initialize the > kernel's RNG. > > Signed-off-by: Jason A. Donenfeld <Jason@...c4.com> > --- > arch/mips/kernel/setup.c | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) applied to mips-next. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists