[v2.4] openssl: RDRAND used directly when default engines loaded in openssl-1.0.1-beta1 through openssl-1.0.1e
if you are using an application linked with openssl-1.0.1-beta1
through openssl-1.0.1e you should do one of the following:
a.) rebuild your OpenSSL with OPENSSL_NO_RDRAND defined.
b.) call RAND_set_rand_engine(NULL) after ENGINE_load_builtin_engines().
c.) git pull latest openssl with commit: “Don’t use rdrand engine as
default unless explicitly requested.” - Dr. Stephen Henson
the OPENSSL_NO_RDRAND option is recommended; an inadvertent call to
load engines elsewhere could re-enable this bad rng behavior.
“FreeBSD Developer Summit: Security Working Group, /dev/random”
“Surreptitiously Tampering with Computer Chips”
“How does the NSA break SSL? … Weak random number generators”
(from redmine: issue id 2509, created on 2013-12-17, closed on 2013-12-17)
- parent #2508 (closed)
- Revision ea7fd685 by Timo Teräs on 2013-12-17T13:05:59Z:
main/openssl: don't use rdrand engine as default As security measure, do not rely solely on hardware random source. fixes #2509 (cherry picked from commit 1fd915b81678c58d35bf63761c260efd5362a93d) Conflicts: main/openssl/APKBUILD