linux-kernel - Re: Entropy Pool Contents

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]

Date:	Mon, 27 Nov 2006 10:19:41 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Phillip Susi <psusi@....rr.com>
CC:	G.Ohrner@...t.rwth-aachen.de, linux-kernel@...r.kernel.org
Subject: Re: Entropy Pool Contents

Phillip Susi wrote:

> I ran into this the other day myself and when I investigated the kernel 
> code, I found that writes to /dev/random do accept the data into the 
> entropy pool, but do NOT update the entropy estimate.  In order to do 
> that, you have to use a root only ioctl to add the data and update the 
> estimate.  I am not sure why this is, or if there is a tool already 
> written somewhere to use this ioctl, maybe someone else can comment?

I believe the idea was that you don't want random users being able to 
artificially inflate your entropy count.  So the kernel tries to make 
use of entropy entered by regular users (by stirring it into the pool) 
but it doesn't increase the entropy estimate unless root says its okay.

Chris
-
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/