If you think about it, a lot of crypto vulnerabilities come down to code that was meant to optimize/speed things. Heartbleed, most RSA problems, DH prime generations, ROCA, ...
I disagree. Even unoptimized implementations are fast enough for most applications. Yes, even on a cheap mobile device.
-
-
yeah definitely, I agree with your statement. People saying SHA-3 is too slow for their application (compared to K12) are (almost) always wrong. But even with this, uneducated decisions will choose what is faster if given the choice.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
RSA > 2048 without CRT on a smartcard highly disagrees with you. But that's why everyone is now using ECC. :3
-
in the defense of Frank comment I'd say that smartcards are not included in the "most applications" (even though they are a widespread illustration of the problem)
End of conversation
New conversation -
-
-
This ignores impact of standardization. Apple needed Curve25519 to encrypt push messages and meet battery lifetime+security goals
-
Benefited from having same extensively optimized implementation. if they had to use ideosyncratic system, would suffer
End of conversation
New conversation -
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.