That doesn't necessarily follow. It's easy to put a real RNG into silicon; the problem is simply that very few people bother.
That doesn't necessarily follow. It's easy to put a real RNG into silicon; the problem is simply that very few people bother.
In the meantime, I'd dispute the idea that embedded developers even understand the relationship between secure random number generation and cryptography, outside of the abstract.
It's also the case that amongst security practioners in general purpose code there is still precious little best-practice understanding of how to groom and maintain secure RNGs; a Black Hat talk from just a few years ago busted up a bunch of RNGs on security products, both with algorithmic attacks and things like cold-start entropy.
Sure, of course. My point was that, compare to issues such as power constraints, code size, bandwidth, et cetera, the problem of getting entropy was more of a "people are doing things wrong" issue and less of a "laws of physics get in the way" issue.
Here's a paper on the Via hardware RNG I helped write. I have not seen this level of analysis from vendors of other hardware RNGs. In summary, the entropy source is pretty good but has some bad modes if you mess with some of the config bits.
http://www.cryptography.com/resources/whitepapers/VIA_rng.pd...
I crusaded for a long time for FreeBSD to not use this source directly. Instead, someone put in a Davies-Meyer AES hack that just whitens the last few bytes of output. So if you can get a predictable series of sequential bytes out of the Via RNG at any point, you've broken /dev/random on that machine.
Oh look, that code is still there:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/random/neh...
Here's where it swaps out the decent Yarrow PRNG for this ad-hoc one:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/random/pro...
So running FreeBSD on a Via machine is actually LESS secure because other entropy, such as disk IO, timers, etc. doesn't get hashed in. This is exactly what I'm arguing when I say a single hardware source can sometimes lead to less secure system choices.
BTW, I doubt this constitutes vuln disclosure since I wrote core@ about this about 4 years ago and the maintainer decided it wasn't important. Ironically, the reason given was that this is higher-performance than Yarrow and the hardware RNG appears good.
That said, I'd say that there are probably bigger issues in FreeBSD than this.
And btw, tarnsap is awesome!
And btw, tarnsap is awesome!
Thanks! Good to see I'm not the only person who makes that typo...
Ah fudge!