Re: Why does reading from /dev/urandom deplete entropy so much?

On Sat, Dec 08, 2007 at 11:33:57AM -0600, Mike McGrath wrote:
>> Huh?  What's the concern?  All you are submitting is a list of
>> hardware devices in your system.  That's hardly anything sensitive....
>
> We actually had a very vocal minority about all of that which ended up 
> putting us in the unfortunate position of generating a random UUID instead 
> of using a hardware UUID from hal :-/

Tinfoil hat responses indeed!  Ok, if those folks are really that
crazy, my suggestion then would be to do a "ifconfig -a > /dev/random"
before generating the UUID, and/or waiting until you just about to
send the first profile, and/or if you don't yet have a UUID,
generating it at that very moment.  The first will mix in the MAC
address into the random pool, which will help guarantee uniqueness,
and waiting until just before you send the result will mean it is much
more likely that the random pool will have collected some entropy from
user I/O, thus making the random UUID not only unique, but also
unpredictable.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Jeff Garzik <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Matt Mackall <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Jon Masters <[email protected]>

• References:
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Matt Mackall <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Mike McGrath <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Matt Mackall <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Mike McGrath <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Matt Mackall <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Mike McGrath <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Theodore Tso <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Jon Masters <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Theodore Tso <[email protected]>
  • Re: Why does reading from /dev/urandom deplete entropy so much?
    • From: Mike McGrath <[email protected]>

• Prev by Date: Re: tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52, [2.6.24-rc4-git5: Reported regressions from 2.6.23]
• Next by Date: Re: tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52, [2.6.24-rc4-git5: Reported regressions from 2.6.23]
• Previous by thread: Re: Why does reading from /dev/urandom deplete entropy so much?
• Next by thread: Re: Why does reading from /dev/urandom deplete entropy so much?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]