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 derefr on Wednesday May 04, 2016 @03:43AM (#11626832)
I'm surprised there's no talk of essentially making reads from /dev/urandom occur via a VDSO that grabs a seed for each process from the common pool, and then runs entropy generation from then on in the process's address space.
[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by caf on Wednesday May 04, 2016 @05:59AM (#11627279)
You really want a separate instance of the CSPRNG per thread, not per process.
[ Parent | on HN ]
Re:Ruby Bug: SecureRandom should try /dev/urandom first by ryuuchin on Thursday May 05, 2016 @05:12PM (#11639697)
You can also use the hw rng if supported (e.g. rdrand) for fork/VM duplication safety. /dev/urandom should be fork safe though so long as you're not buffering data from it.
[ Parent | on HN ]