[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RDRAND used directly when default engines loaded in openssl-1.0.1-beta1 through openssl-1.0.1e
- To: cpunks <[email protected]>, Full Disclosure <[email protected]>
- Subject: RDRAND used directly when default engines loaded in openssl-1.0.1-beta1 through openssl-1.0.1e
- From: [email protected] (coderman)
- Date: Fri, 20 Dec 2013 04:32:33 -0800
- In-reply-to: <CAJVRA1St=tXDdv59Ya7TQjWFyrCiCWH4GySgGLoQxm3ZLduwag@mail.gmail.com>
- References: <CAJVRA1RZJgO2wOKsY8pMxnwpHPnLgx9DiW4_1CzxotT==f3rFw@mail.gmail.com> <CAJVRA1St=tXDdv59Ya7TQjWFyrCiCWH4GySgGLoQxm3ZLduwag@mail.gmail.com>
On Mon, Dec 16, 2013 at 7:27 PM, coderman <[email protected]> wrote:
> ...
> "what is affected??"
fortunately impacts are less than anticipated!
nickm devised most concise fix: RAND_set_rand_method(RAND_SSLeay());
always after ENGINE_load_builtin_engines().
https://gitweb.torproject.org/tor.git/commitdiff/7b87003957530427eadce36ed03b4645b481a335
---
full write up is here including a BADRAND engine patch for testing:
https://peertech.org/goodrand
---
last but not least, notable omissions on NSA role in reqs for random
number sources in Appendix E: US Government Role in Current Encryption
Standards.:
http://cryptome.org/2013/12/nsa-usg-crypto-role.pdf
can we get a do-over?