Talk:Random number generation
on the bashing of /dev/urandom
I don't take an opinion on whether old overwritten data can be read.
However, there is an unrelated reason to fill a LUKS partition from
/dev/urandom before LUKS-initializing it (and after checking for bad blocks if you wanted to do that).
It makes it harder for people trying to read your disk and find out what's on it. If you filled it with zeroes, for example, then they would be able to tell which portions of the partition had been written to since you initialized it.
compare gentoo docs, http://en.gentoo-wiki.com/wiki/DM-Crypt_with_LUKS#Filling_the_disk_with_random_data --Idupree 22:45, 3 March 2010 (EST)
/dev/urandomshould be used to clear partitions, at least as default in the examples. If anyone wants to zero the partitions instead of using random data, they are free to do so. --Montschok 20:53, 11 August 2010 (EDT)
Links with content
This is to provide some links which may be useful, if this page is going to be expanded.
Proposals to renew the linux /dev/random:
http://www.phoronix.com/scan.php?page=news_item&px=MTI5NzY leading to http://lkml.indiana.edu/hypermail/linux/kernel/1302.1/00479.html
and an article on /dev/random robustness (current; June 2013):