Kyber

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Kyber is a key encapsulation method (KEM) designed to be resistant to cryptanalytic attacks with future powerful quantum computers. It is used to establish a shared secret between two communicating parties without an (IND-CCA2) attacker in the transmission system being able to decrypt it. This asymmetric cryptosystem uses a variant of the learning with errors lattice problem as its basic trapdoor function. It won the NIST competition for the first post-quantum cryptography (PQ) standard.[1] Kyber is named after the fictional kyber crystals used to power lightsabers in the Star Wars universe (compare [Light-]SABER).

Properties

The system is based on module learning with errors (M-LWE) from the field of machine learning, in conjunction with cyclotomic rings.[2] Recently, there has also been a tight formal mathematical security reduction of the ring-LWE problem to MLWE.[3][4] Compared to competing PQ methods, it has typical advantages of lattice-based methods, e.g. in regard to runtime as well as the size of the ciphertexts and the key material.[5] Variants with different security levels have been defined: Kyber512 (NIST security level 1, ≈AES 128), Kyber768 (NIST security level 3, ≈AES 192), and Kyber1024 (NIST security level 5, ≈AES 256).[6] At a complexity of 161 bits, the secret keys are 2400, the public keys 1088, and the ciphertexts 1184 bytes in size.[7][8] With an accordingly optimized implementation, 4 kilobytes of memory can be sufficient for the cryptographic operations.[9] For a chat encryption scenario using liboqs, replacing the extremely efficient, non-quantum-safe ECDH key exchange using Curve25519 was found to increase runtime by a factor of about 2.3 (1.5–7), an estimated 2.3-fold (1.4–3.1) increase in energy consumption, and have about 70 times (48–92) more data overhead.[10] Internal hashing operations account for the majority of the runtime, which would thus potentially benefit greatly from corresponding hardware acceleration.

Development

Kyber is derived from a method published in 2005 by Oded Regev, developed by developers from Europe and North America, who are employed by various government universities or research institutions, or by private companies, with funding from the European Commission, Switzerland, the Netherlands, and Germany.[11] They also developed the related and complementary signature scheme Dilithium, as another component of their "Cryptographic Suite for Algebraic Lattices" (CRYSTALS). Like other PQC-KEM methods, Kyber makes extensive use of hashing internally. In Kyber's case, variants of Keccak (SHA-3/SHAKE) are used here, to generate pseudorandom numbers, among other things.[9] In 2017 the method was submitted to the US National Institute of Standards and Technology (NIST) for its public selection process for a first standard for quantum-safe cryptographic primitives (NISTPQC). It is the only key encapsulation mechanism that has been selected for standardization at the end of the third round of the NIST standardization process.[3] According to a footnote the report announcing the decision, it is conditional on the execution of various patent-related agreements, with NTRU being a fallback option. Currently, a fourth round of the standardization process is underway, with the goal of standardizing an additional KEM. In the second phase of the selection process, several parameters of the algorithm were adjusted and the compression of the public keys was dropped.[9] Most recently, NIST paid particular attention to costs in terms of runtime and complexity for implementations that mask runtimes in order to prevent corresponding side-channel attacks (SCA).[3]

Evolution

During the NIST standardization process, Kyber has undergone changes. In particular, in the submission for round 2 (so called Kyber v2), the following features have been changed:[12]

  • public key compression removed (due to NIST comments on the security proof);
  • parameter q reduced to 3329 (from 7681);
  • ciphertext compression parameters changed;
  • number-theoretic transform (NTT) definition changed along the lines of NTTRU for faster polynomial multiplication;
  • noise parameter reduced to \eta = 2 for faster noise sampling;
  • public key representation is changed to NTT domain in order to save the NTT operations.

Submission to round 3 underwent further tweaks:[13]

  • the use of Fujisaki-Okamoto transformation (FO transform) modified;
  • noise level increased and ciphertext compression reduced for the level 1 parameter set;
  • sampling algorithm improved.

Usage

The developers have released a reference implementation into the public domain (or under CC0), which is written in C.[14] The program library liboqs of the Open Quantum Safe (OQS) project contains an implementation based[15] on that.[10] OQS also maintains a quantum-safe development branch of OpenSSL,[16] has integrated it into BoringSSL, and its code has also been integrated into WolfSSL.[17] There are a handful of implementations using various other programming languages from third-party developers, including JavaScript and Java.[18][19][20] Various (free) optimized hardware implementations exist, including one that is resistant to side-channel attacks.[21][22] The German Federal Office for Information Security is aiming for implementation in Thunderbird, and in this context also an implementation in the Botan program library and corresponding adjustments to the OpenPGP standard.[23]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. What was NIST thinking? (PDF-Datei)
  3. 3.0 3.1 3.2 Status Report on the Second Round of the NIST PQC Standardization Process (PDF-Datei)
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lattice-based cryptography and Kyber – Andrea Basso (PDF; 2,0 MB)
  6. Overview of NIST Round 3 Post-Quantum cryptography Candidates (PDF; 157 kB)
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. https://pq-crystals.org/kyber/data/kyber-specification-round3-20210804.pdf[bare URL PDF]
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. https://pq-crystals.org/[bare URL]
  12. Roberto Avanzi, Joppe Bos, Léo Ducas, Eike Kiltz, Tancrède Lepoint, Vadim Lyubashevsky, John M. Schanck, Peter Schwabe, Gregor Seiler, Damien Stehlé. CRYSTALS–Kyber (Round 2 presentation) August 23, 2019.
  13. Roberto Avanzi, Joppe Bos, Léo Ducas, Eike Kiltz, Tancrède Lepoint, Vadim Lyubashevsky, John M. Schanck, Peter Schwabe, Gregor Seiler, Damien Stehlé. CRYSTALS–Kyber (Round 3 presentation) June 9, 2021.
  14. Kyber/LICENSE at master · pq-crystals/kyber · GitHub
  15. Kyber – Open Quantum Safe
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.

External links