Re:Ruby Bug: SecureRandom should try /dev/urandom first
by matt_wulfeck on Wednesday May 04, 2016 @01:58AM
(#11626519)
Cryptographers really are part of the problem. Do you ever Read the discussions in the metzdowd/crypto list? Nobody agrees on anything.
Re:Ruby Bug: SecureRandom should try /dev/urandom first
by tptacek on Wednesday May 04, 2016 @08:07AM
(#11627728)
The metzdowd list is a running joke among practitioners. The direct answer to your question is "no."
Re:Ruby Bug: SecureRandom should try /dev/urandom first
by azet on Wednesday May 04, 2016 @10:33AM
(#11628616)
I stopped reading these 'cypherpunk'-epilog lists a few years back. I'm still subscribed because of cross-postings. The amount of tinfoil-hattery is just unsustainable. And there's barely any interesting information for people working on real cryptography-, systems or engineering.
Re:Ruby Bug: SecureRandom should try /dev/urandom first
by nitrogen on Wednesday May 04, 2016 @01:25AM
(#11626396)
I didn't mean to dismiss the word of the experts. I only said "on HN" because that's where I'm familiar with your arguments, which I already put into practice by reading /dev/urandom when I need pseudorandom bytes.
The reason this is a problem is simply that the Linux maintainer is obstinately wrong. Theodore Ts'o was on HN a year or so ago, and in defending the current design (and man pages), made some incoherent arguments, such as that urandom might be OK for nonces, but not key generation (a head-scratcher for anyone familiar with cryptography engineering).