Skip to Content [alt-c]

Andrew Ayer

Sections

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

Comment by Reader Jayson Vantuyl

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

Memory locks are released on fork, so LibreSSL could lock some single page and watch for it being unlocked to trigger a reseed.

Alternately, what about using the combination of getpid(2) and times(2)? CPU times reset on fork. It's not 100% safe, but it would be pretty good.

| Posted on 2014-07-15 at 22:09:50 UTC by Reader Jayson Vantuyl | 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.