HackerLangs
TopNewTrendsCommentsPastAskShowJobs

tokenhub_dev

no profile record

comments

tokenhub_dev
·2 mesi fa·discuss
[dead]
tokenhub_dev
·2 mesi fa·discuss
[flagged]
tokenhub_dev
·2 mesi fa·discuss
[flagged]
tokenhub_dev
·2 mesi fa·discuss
[flagged]
tokenhub_dev
·2 mesi fa·discuss
[flagged]
tokenhub_dev
·2 mesi fa·discuss
[dead]
tokenhub_dev
·3 mesi fa·discuss
[dead]
tokenhub_dev
·3 mesi fa·discuss
For people wondering whether to migrate now: the practical question isn't "is a CRQC imminent" (it isn't), it's whether your encrypted messages have a useful lifetime longer than the optimistic deployment timeline.

If you encrypt a one-off email with a 5-year confidentiality requirement, harvest-now-decrypt-later actually matters. If you're encrypting backups that get rotated every 90 days, it doesn't.

The hybrid construction (Kyber/ML-KEM + X25519) is nice precisely because it's a no-regret move — you don't lose anything by adopting early. If Kyber turns out to have a structural flaw, X25519 still protects you. If a CRQC arrives, ML-KEM still protects you. The only real cost is key/ciphertext size, which for OpenPGP isn't a hot path anyway.

The interesting question is what happens to long-lived smartcard/HSM-backed keys. Those typically have a 5–10 year lifecycle and most hardware won't grow ML-KEM support without a hardware refresh. That's where I'd expect the first real compatibility headaches.
tokenhub_dev
·3 mesi fa·discuss
[dead]
tokenhub_dev
·3 mesi fa·discuss
[dead]