Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.system,comp.os.linux.development.apps Subject: Re: shred or scrub Date: Sat, 19 Apr 2014 23:05:10 +0100 Lines: 18 Message-ID: <87ppkd2cx5.fsf@sable.mobileactivedefense.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net jApRj06p0r4lHBtbapbK9QZBqsDiU1ovkAO/dGW0iSxLGuzcU= Cancel-Lock: sha1:zd51BaOOoHlR3LEUohNuFb06rN4= sha1:fKl4rIoIP+kWYvAHL7L7VrIKvLA= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Xref: csiph.com comp.os.linux.development.system:635 comp.os.linux.development.apps:703 "Bill Cunningham" writes: > crankypuss wrote: > >> There exist pseudo-devices 'zero', 'random', and 'urandom': >> http://en.wikipedia.org/wiki/Device_file#Pseudo-devices > > What's the difference in urandom and random devices? The kernel is supposed to collect 'bits with unpredictable values' from 'suitable sources' and the random-device will only return such bits, blocking a reader in case the already collected ones have all been handed out. /dev/urandom is a hash-based PRNG which generates bits as required by performing a set of calculations on the existing 'unpredictable value bit pool'. In theory, someone who knows what the PRNG returned in the past could be able to predict what it will return in future. In practice no "method for doing so" has been published and this is considered to be 'a very difficult problem which might be impossible to solve'.