Re: [patch #6797] shred option to use internal RNG

[Jim Meyering]

Steven Schveighoffer wrote:
>   <http://savannah.gnu.org/patch/?6797>
> Our company is looking at using GNU shred to wipe customer data from RMA'd
> drives in our systems.
>
> One thing we have noticed is that shred runs about 90% slower if /dev/urandom
> exists versus when it does not.  Researching this, it seems this is because
> gl/lib/randread.c will use an internal RNG when null is passed into
> randread_new, and /dev/urandom cannot be opened.

Someone asked the same question not long ago.
here's the thread:

  http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/15581

Quick answer:

  How about

    --random-source=FILE

  where FILE contains a bunch of random data,
  like a chunk from the middle of a well-compressed tarball?
  Or even this:

    --random-source=/dev/zero