Skip to Content [alt-c]


In reply to LibreSSL's PRNG is Unsafe on Linux [Update: LibreSSL fork fix]

Reader henning on 2014-07-15 at 13:06:

We really want to see linux provide the getentropy() syscall, which fixes all the mentioned issues. Requiring the consumers to fiddle with the PRNG is not a sustainable "solution".

/dev/*random has way more issues than just chroot. For one - what do you do in the fd exhaustion case?

And yes, there are no such issues natively on OpenBSD, since we do have getentropy and our PIDs are random, plus they don't get recycled quickly.


Post a Reply

Your comment will be public. To contact me privately, email me. Please keep your comment polite, on-topic, and comprehensible. Your comment may be held for moderation before being published.

(Optional; will be published)

(Optional; will not be published)

(Optional; will be published)

  • Blank lines separate paragraphs.
  • Lines starting with > are indented as block quotes.
  • Lines starting with two spaces are reproduced verbatim (good for code).
  • Text surrounded by *asterisks* is italicized.
  • Text surrounded by `back ticks` is monospaced.
  • URLs are turned into links.
  • Use the Preview button to check your formatting.