News for hackers. Stuff that matters.
Re:ML-KEM Mythbusting by westurner on Friday November 28, 2025 @02:54AM (#46076499)
Is this the thing with ML-KEM, then:

> [With AuthKEM,] you would replace the ~2.4 KB ML-DSA signature with a ~1 KB ML-KEM ciphertext.

Re:ML-KEM Mythbusting by durumcrustulum on Friday November 28, 2025 @08:03AM (#46078288)
What "the thing"? AuthKEM isn't being deployed anywhere.
Re:ML-KEM Mythbusting by westurner on Friday November 28, 2025 @01:08PM (#46081119)
How much more complex is the difference than 2.4 KB w/ ML-DSA or ~1 KB w/ ML-KEM?
Re:ML-KEM Mythbusting by durumcrustulum on Monday December 01, 2025 @07:34PM (#46115712)
I'm sorry I don't understand what you're asking
Re:ML-KEM Mythbusting by westurner on Tuesday December 02, 2025 @11:27PM (#46130301)
Though there is a difference between a cert signature (ML-DSA) and a challenge (ML-KEM), ultimately and fundamentally, isn't real key size still a relevant metric for comparison.

(Everyone dnvoted this like -6/-7. I guess they didn't understand the relevance.)

IDK a terse analogy then:

MerkleCerts + ML-DSA : ML-DSA :: Challenge (ML-KEM,) : ____ (ML-DSA)

Merkle-signing cert trust roots is a security/bytes-transferred efficiency tradeoff.

What is the difference in number of bytes seemed usefully relevant to me at least.