linux-kernel - Re: [PATCH] random: add a way to get some random bits into the entropy pools early on

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: <20081125220627.4a07f6b7@infradead.org>
Date:	Tue, 25 Nov 2008 22:06:27 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Matt Mackall <mpm@...enic.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH] random: add a way to get some random bits into the
 entropy pools early on

On Tue, 25 Nov 2008 15:41:22 -0600
Matt Mackall <mpm@...enic.com> wrote:


> > 
> > This patch adds a function to the random driver so that various
> > pieces of the kernel can add random bits (but not entropy!) to the
> > pool, to avoid this dupicate ID problem.
> 
> This appears to be equivalent to making random initialize earlier,
> except with more code?

well sort of kinda, but arbitrarily early (eg I made the oops ID just
call this whenever it's called first)

> 
> If we're going down a route like this, I'd like to see the ability to
> actually mix in data (ie MAC addresses, DMI data, etc.) rather than
> just timing.

I'll make a second patch for that; it does make sense to do this,
but it also makes sense to just have a "just do the time" helper



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/