WeSearch

Reducing ML-KEM-768 encapsulation key sizes by 24 octets

·4 min read · 0 reactions · 0 comments · 1 view
#cryptography#post-quantum#networking#optimization#compression
⚡ TL;DR · AI summary

The article discusses a method to reduce the size of ML-KEM-768 public keys by 24 octets through coefficient compression, improving efficiency in network transmission. By packing groups of four coefficients into fewer bits using arithmetic encoding, the key size is reduced from 1184 to 1160 octets. This technique draws from prior work on NTRU Prime and aims to optimize post-quantum cryptographic key transmission within constrained packet sizes.

Key facts
Original article
Lobsters
Read full at Lobsters →
Opening excerpt (first ~120 words) tap to expand

Disclaimer: I am not a cryptographer. There may be serious bugs or side channels! The minimum MTU for IPv6 is 1280 octets; if you subtract the 40-octet IPv6 header and the 8-octet UDP header, you get 1232 usable octets. ML-KEM-768 public keys are 1184 octets long, leaving little space for other protocol material that you might want to stuff into a single UDP packet. Can you compress ML-KEM-768 public keys? Note that, in the standard ML-KEM-768 public key layout, octets [0,1152)\left[0, 1152\right) are three polynomials, each with 256 coefficients, each 12 bits. Octets [1152,1184)\left[1152, 1184\right) are the seed ρ\rho which is considered to be indistinguishable from random. But wait. q=3329q = 3329, and log⁡2q≈11.70087316\log_2 q \approx 11.70087316.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Lobsters.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Lobsters