RT @tqbf: It’s not crazy for OpenSSL to redesign and simplify its CSPRNG. It is silly to make it MORE complicated. https://github.com/openssl/openssl/pull/3758 …
-
-
I offered to PR a fork-safe DRBG that we've formally verified, but bad faith from poisonous lunatics on openssl-prng made me give up.
3 replies 3 retweets 4 likes -
I think it's a different world now. Please get in touch. And I'm sorry.
2 replies 0 retweets 1 like -
Happy to go again. Is there a particularly good PR or Issue to put some observations/references/thoughts in?
2 replies 0 retweets 1 like -
I replied to the cryptography@ thread with links, proofs and rationale for the s2n design. You've been getting some undeserved hate there!
1 reply 0 retweets 1 like -
Look forward to reading your post. It wouldn't be the Internet without undeserved hate; I can handle it.
1 reply 0 retweets 1 like -
http://www.metzdowd.com/pipermail/cryptography/2017-June/032361.html … for the twitter gallery.
2 replies 0 retweets 1 like -
I don’t understand “if you’re doing a lot of ECDSA”. Per-record IVs, sure: little overhead except syscall. But ECDSA?
1 reply 0 retweets 0 likes
Oh yep! urandom is awful when you have 100s of threads, getrandom() better, but still slow. Handshake storms are a thing :( failover etc
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.