The USE_OPENSSL_RANDOM macro is defined when OpenSSL is used as a randomness provider, but the implementation of strong randomness is guarded by USE_OPENSSL in most places. This is technically the same thing today, but it seems hygienic to use the appropriate macro in case we ever want to allow OS randomness together with OpenSSL or something similar (or just make git grep easier which is my itch to scratch with this).
The attached moves all invocations under the correct guards. RAND_poll() in fork_process.c needs to happen for both OpenSSL and OpenSSL random, thus the check for both. cheers ./daniel
openssl_random_macros.patch
Description: Binary data