openssl: RDRAND used directly when default engines loaded in openssl-1.0.1-beta1 through openssl-1.0.1e
Details: http://seclists.org/fulldisclosure/2013/Dec/99
Quote:
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.
Links:
-
“FreeBSD Developer Summit: Security Working Group, /dev/random”
https://wiki.freebsd.org/201309DevSummit/Security -
“Surreptitiously Tampering with Computer Chips”
https://www.schneier.com/blog/archives/2013/09/surreptitiously.html -
“How does the NSA break SSL? … Weak random number generators”
http://blog.cryptographyengineering.com/2013/12/how-does-nsa-break-ssl.html
(from redmine: issue id 2508, created on 2013-12-17, closed on 2013-12-17)
- Relations:
- child #2509 (closed)
- child #2510 (closed)
- child #2511 (closed)
- child #2512 (closed)