This directory contains research on the post-quantum key encapsulation mechanism (KEM) Kyber, now standardized as ML-KEM (FIPS 203) by NIST.
Topics
| File | Topic | Status |
|---|---|---|
| fundamentos-lwe | LWE and Lattice Fundamentals — the mathematical basis of Kyber | Complete |
| estructura-kem | KEM Structure — generation, encapsulation, decapsulation | Complete |
| parametros-seguridad | Parameters and Security Levels — ML-KEM-512/768/1024 | Complete |
| implementacion | Implementation — algorithmic details, Compress/Decompress, FO transform | Complete |
| implementacion-dart | Dart Implementation — code extracted from xkyber_crypto, contrast with FIPS 203 | Complete |
| constante-tiempo-dart | Constant Time in Dart — VM limitations, identified critical points | Complete |
| ataques | Known Attacks — classical and quantum cryptanalysis against LWE/Kyber | Complete |
| estandarizacion | Standardization — NIST process, competition, adoption | Complete |
| conclusiones | Conclusions — integrated analysis, implications, open questions | Complete |
Knowledge Structure
The research follows the logical flow:
- Fundamentals (LWE, lattices, decision vs search problem)
- Mechanism (how Kyber works step by step)
- Security (parameters, NIST levels, equivalent strength)
- Implementation (Compress, FO transform, optimizations)
- Attacks (classical, quantum, side-channel, hybrid)
- Context (NIST process, competitors, real-world adoption)
- Dart Implementation (extractions from xkyber_crypto, contrast with C reference)
- Security in Dart (constant time, VM limitations, critical points)
Related Documents
- Obscura — Conclusions — parallelism: Kyber and fingerprinting share the same defender-attacker asymmetry
- Chat Control — Homomorphic Cryptography — other post-quantum techniques and their relation to surveillance
- xKyber Crypto — Personal implementation of Kyber in Dart/Flutter during the algorithm learning phase, archived after concluding that secure management of post-quantum cryptography in the Dart ecosystem is unfeasible without constant-time guarantees at the VM level