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]

Message-ID: <456B4CD2.7090208@cfl.rr.com>
Date:	Mon, 27 Nov 2006 15:38:42 -0500
From:	Phillip Susi <psusi@....rr.com>
To:	David Wagner <daw-usenet@...erner.cs.berkeley.edu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Entropy Pool Contents

David Wagner wrote:
> Nope, I don't think so.  If they could, that would be a security hole,
> but /dev/{,u}random was designed to try to make this impossible, assuming
> the cryptographic algorithms are secure.
> 
> After all, some of the entropy sources come from untrusted sources and
> could be manipulated by an external adversary who doesn't have any
> account on your machine (root or non-root), so the scheme has to be
> secure against introduction of maliciously chosen samples in any event.

Assuming it works because it would be a bug if it didn't is a logical 
fallacy.  Either the new entropy pool is guaranteed to be improved by 
injecting data or it isn't.  If it is, then only root should be allowed 
to inject data.  If it isn't, then the entropy estimate should increase 
when the pool is stirred.

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