Skip to Content [alt-c]

Andrew Ayer


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

Comment by Anonymous

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

If an application knows it is going to chroot it's child away from accessing /dev/urandom, why doesn't the parent take responsibility to provide a named pipe in the chroot environment?

Part of the problem also seems to be that to be a drop-in replacement to OpenSSL requires leaving the API the way it is. Hopefully if LibreSSL gain popularity, they will be able to revise the API to include such things as being able to specify the entropy quality where the calling app decides if a scary function is an acceptable source of entropy or not.

| Posted on 2014-07-17 at 04:40:40 UTC by Anonymous | 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.