Skip to Content [alt-c]


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

Reader Jayson Vantuyl on 2014-07-15 at 22:09:

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.


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.