News for hackers. Stuff that matters.

A comment on Ruby Bug: SecureRandom should try /dev/urandom first. Parent comment

Re:Ruby Bug: SecureRandom should try /dev/urandom first by ryuuchin on Tuesday May 03, 2016 @10:14PM (#11625696)
Obligatory "How To Safely Generate A Random Number" link[1] that I always wind up posting in threads like these. There's also the getrandom syscall[2] which uses the /dev/urandom pool.

[1] http://sockpuppet.org/blog/2014/02/25/safely-generate-random...

[2] http://man7.org/linux/man-pages/man2/getrandom.2.html

[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by duaneb on Tuesday May 03, 2016 @10:27PM (#11625734)
Why are the man pages not so clear?
[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by ryuuchin on Tuesday May 03, 2016 @10:59PM (#11625848)
I'm not sure. I think part of the problem is that Linux still uses entropy estimation. This is also one of the issues I have with the proposed replacement[1][2] for Linux's current CSPRNG implementation since it still retains entropy estimations.

[1] https://lwn.net/Articles/684568/

[2] https://news.ycombinator.com/item?id=11561340 (HN thread for [1])

[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by disposeofnick9 on Wednesday May 04, 2016 @06:12AM (#11627321)
Btw Linux / Fortuna

http://lkml.iu.edu/hypermail/linux/kernel/0504.1/1964.html

[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by masklinn on Wednesday May 04, 2016 @04:22AM (#11626963)
> There's also the getrandom syscall[2] which uses the /dev/urandom pool.

Sadly they just had to include GRND_RANDOM then compound that with GRND_NONBLOCK.

[ Parent | on HN ]