In reply to
Daniel J. Bernstein
@djb@mastodon.cr.yp.to
Designing cryptography (deployed now: X25519, Ed25519, ChaCha20, sntrup, Classic McEliece) to proactively reduce risks. Coined phrase "post-quantum" in 2003.
mastodon.cr.yp.to
Daniel J. Bernstein
@djb@mastodon.cr.yp.to
Designing cryptography (deployed now: X25519, Ed25519, ChaCha20, sntrup, Classic McEliece) to proactively reduce risks. Coined phrase "post-quantum" in 2003.
mastodon.cr.yp.to
@djb@mastodon.cr.yp.to
·
3d ago
@huitema @paulehoffman @rsalz Let's try an example. Google and Cloudflare used CECPQ2b = ECC+SIKE for tens of millions of user connections, instead of the usual ECC. That wasn't _removing_ ECC in favor of SIKE; it was _supplementing_ ECC with SIKE. This is why the break of SIKE still left those connections with the usual security of ECC. If they had instead incompetently _removed_ ECC and replaced that with SIKE, the SIKE attack would have immediately broken all of those connections.
View full thread on mastodon.cr.yp.to
0
0
0
Loading comments...