Skip to Content [alt-c]

Andrew Ayer


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

Comment by Reader henning

This comment is owned by whoever posted it. I am not responsible for it in any way.

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.

| Posted on 2014-07-15 at 13:06:38 UTC by Reader henning | Reply to This

Post a Reply

Your comment will be public. If you would like to contact me privately, please email me. Please keep your comment on-topic, polite, and comprehensible. Use the "Preview" button to make sure your comment is properly formatted. Name and email address are optional. If you specify an email address it will be kept confidential.

Post Comment

(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.
  • Text surrounded by *asterisks* is italicized.
  • Text surrounded by `back ticks` is monospaced.
  • URLs are turned into links.