Awesome
This repository contains a wide range of cryptographic algorithms specified in the Cryptol language. Our long-term goal is for these specifications to be literate files that share as much common code as possible, and to allow implementation correctness proofs to depend on one shared, canonical description of the algorithms they target. As a starting point, however, we plan to collect as many specifications as we can find, as-is, and incrementally improve their presentation and inter-dependency.
Some of the widely adopted cryptographic algorithms contained in this repository are listed below.
| Primitive | Synthesis | Verification | |
|---|---|---|---|
| Block Cipher | AES | ||
| Triple DES | |||
| Stream Cipher | ChaCha20-Poly1305 | ||
| Message Authentication | HMAC | ||
| Digital Signature | ECDSA | ||
| SPHINCS+ | |||
| FALCON | |||
| CRYSTALS Dilithium | |||
| Hash | SHA1 | ||
| SHA256 | |||
| SHA2 | |||
| SHA3 | |||
| Key Encapsulation | ML-KEM (CRYSTALS-Kyber) | ||
| Asymmetric Encryption | RSA |
All Cryptol files in this repository are covered by the BSDv3 license. See LICENSE file.
NIST Post-Quantum Cryptography Standardization Selections
This repo includes executable specifications of several quantum-resistant schemes. These are drawn from the finalists of the NIST Post-Quantum Cryptography competition. In some cases, we have multiple versions of the algorithms from various rounds of the competition, as well as from the initial public draft (IPD) and final specifications produced by NIST.
| Primitive | NIST Name (Original Name) | Type | Versions Available |
|---|---|---|---|
| PKE / KEM | ML-KEM (CRYSTALS-Kyber) | Lattice-based | Final version, Round 3.01 |
| Signature | ML-DSA (CRYSTALS-Dilithium) | Lattice-based | IPD, Round 2, Round 1 |
| Signature | FN-DSA (FALCON) | Lattice-based | Round 1.2 |
| Signature | SLH-DSA (SPHINCS+) | Hash-based | Round 3.1 |
Remarks
The Cryptol specs presented here are written with the objective of being as close as possible to the specs as presented in the official papers so that even someone without cryptographic experience can verify that the Cryptol code meets the spec by reading it "line by line". As a result, the Cryptol code may not be as efficient as other implementations (for example it may implement DFT instead of FFT), yet it is closer to the paper definitions and aims to be functionally equivalent to them.
Properties
The Cryptol specs define several correctness properties. Cryptol is capable of proving several of these properties hence guaranteeing the cryptographic correctness of the code. However, Cryptol cannot verify properties that hold only with overwhelming probability, i.e. properties that hold for almost all but not all possible inputs. As a result, cryptographic schemes with approximate correctness can only be checked by Cryptol on uniformly random inputs.
Appreciations
Without the generous help of the authors, who were willing to share their work with us, our team would not have been able to create such an effective codebase. We are truly grateful for their support. In particular, we'd like to thank:
- Vadim Lyubashevsky (CRYSTALS Kyber and CRYSTALS Dilithium)
- Andreas Hülsing (SPHINCS+)
- Pierre-Alain Fouque and Thomas Pornin (FALCON)
Contributing
You can contribute to this project by submitting issues or bug reports.