-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PRNG unsafe against forking #37
Comments
This was addressed over a year ago - did you read the full article, particularly the part under the heading "Update (2014-07-16 03:33 UTC): LibreSSL releases fix for fork issue"? |
We even integrated the test from this article into the portable build at the time this was raised. Simply configure with the Operating systems can also improve and make solving this problem easier as well. Some have made progress in the year since we addressed this, others have not. I'm looking forward to unmasking some of the blacklisted OS arc4random implementations in the future. |
Thanks for your 'kind' words. Apart from angry reactions stating I did not RTFM, I would prefer having read replies to that part. |
Following this link, LibreSSL's PRNG is not safe and can provide the same 'random' bytes when called from a fork, compared to a call in the original program.
The text was updated successfully, but these errors were encountered: