Re: Overwriting with random data

"Carlos E.R." <[email protected]> writes:
> Using true random data is slow, specially if the disk or partition is
> very big. Depends on how fast can the machine create new random data
> (see man random and urandom). So I do tricks to do it faster.

With very few exceptions nobody uses true random[1] data directly.
/dev/random is a DRBG seeded from the random sources the kernel finds;
shred sees its internal RNG with 32 bytes from the kernel (strace
it...); I don’t know where you’re getting random data from but the
chances that it’s direct from a TRNG are negligible.

[1] in the sense described by
    e.g. https://link.springer.com/content/pdf/10.1007/978-3-540-85053-3_10.pdf

-- 
https://www.greenend.org.uk/rjk/