Conversation

From previous RT of

@sejaques

' post - the most compelling argument for the PQC work underway now. eprint.iacr.org/2015/1075.pdf

"Even though quantum computers are far away, you should still replace RSA and ECC. Michele Mosca pointed out the main problem: Suppose quantum computers that can break RSA-2048 are 30 years away. If it will take 10 years to standardize new cryptography, 10 years for your organization to implement it, and you need your secrets to remain safe for 12 years, then you’re already 2 years too late, since someone can record your encrypted data and break it later. Basically, it’s a race between the world’s most brilliant quantum engineers and the world’s laziest sysadmins, where the sysadmins have about a 30 year headstart."

read image description

ALT

Replying to

and

If one really believes that, the most rational choice is 64kbit RSA not dubious PQ systems that break to classical math on laptops.

Replying to

and

The default OpenSSH key exchange since OpenSSH 8.9 is sntrup761x25519-sha512@openssh.com which is only broken if both ed25519 and the PQC algorithm they chose are broken.

Replying to

Key exchange is what needs to be improved in the short term because that's what has to hold up to future attacks. It's already almost entirely ECDHE with ed25519 or in some cases still P-256. Only legacy setups still use RSA for key exchange because it lacks forward secrecy.

Replying to

TLS 1.3 only has ECDHE key exchange. DHE and RSA key exchange are gone. It still supports RSA for server / client authentication but that's not as important and doesn't need to be secure into the future. It's a legacy feature since it isn't an option for key exchange anymore.

11:54 PM · Aug 2, 2022Twitter Web App

Replying to

If you're using RSA certs with TLS 1.3, it doesn't matter if RSA is broken in 10 years. Does matter if x25519 is broken in 10 years. RSA is heavily used for update signing, etc. since P-256, ed25519, etc. are slower to verify. Common not to have easy key rotation for that too.

Show replies