This document summarizes issues with OpenSSL's PRNG not being fully fork-safe. When a process forks, the child process starts with the same PRNG state as the parent. This allows an attacker to predict random values or force collisions. The document provides proofs-of-concept code to demonstrate stack- and heap-based attacks. It recommends alternatives to OpenSSL's PRNG for security-critical applications and notes that proper initialization in each process can mitigate risks.