https://github.com/pq-crystals/kyber
https://github.com/pq-crystals/kyber
crypto cryptography key-exchange-algorithms lattice-based-crypto module-lattices post-quantum post-quantum-cryptography
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/pq-crystals/kyber
- Owner: pq-crystals
- License: other
- Created: 2017-06-08T06:03:36.000Z (about 8 years ago)
- Default Branch: main
- Last Pushed: 2024-08-21T23:49:54.000Z (10 months ago)
- Last Synced: 2024-08-22T15:59:42.090Z (10 months ago)
- Topics: crypto, cryptography, key-exchange-algorithms, lattice-based-crypto, module-lattices, post-quantum, post-quantum-cryptography
- Language: C
- Size: 901 KB
- Stars: 757
- Watchers: 49
- Forks: 171
- Open Issues: 22
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Authors: AUTHORS
Awesome Lists containing this project
README
# Kyber
[](https://travis-ci.org/pq-crystals/kyber)
[](https://coveralls.io/github/pq-crystals/kyber?branch=master)
This repository contains the official reference implementation of the [Kyber](https://www.pq-crystals.org/kyber/) key encapsulation mechanism,
and an optimized implementation for x86 CPUs supporting the AVX2 instruction set.
Kyber has been selected for standardization in [round 3](https://csrc.nist.gov/Projects/post-quantum-cryptography/round-3-submissions)
of the [NIST PQC](https://csrc.nist.gov/projects/post-quantum-cryptography) standardization project.
## Build instructions
The implementations contain several test and benchmarking programs and a Makefile to facilitate compilation.
### Prerequisites
Some of the test programs require [OpenSSL](https://openssl.org).
If the OpenSSL header files and/or shared libraries do not lie in one of the standard locations on your system,
it is necessary to specify their location via compiler and linker flags in the environment variables `CFLAGS`, `NISTFLAGS`, and `LDFLAGS`.
For example, on macOS you can install OpenSSL via [Homebrew](https://brew.sh) by running
```sh
brew install openssl
```
Then, run
```sh
export CFLAGS="-I/usr/local/opt/[email protected]/include"
export NISTFLAGS="-I/usr/local/opt/[email protected]/include"
export LDFLAGS="-L/usr/local/opt/[email protected]/lib"
```
before compilation to add the OpenSSL header and library locations to the respective search paths.
### Building all binaries
To compile the test and benchmarking programs on Linux or macOS, go to the `ref/` or `avx2/` directory and run
```sh
make
```
This produces the executables
```sh
test/test_kyber$ALG
test/test_vectors$ALG
test/test_speed$ALG
```
where `$ALG` ranges over the parameter sets 512, 768, 1024.
* `test_kyber$ALG` tests 1000 times to generate keys, encapsulate a random key and correctly decapsulate it again.
Also, the program tests that the keys cannot correctly be decapsulated using a random secret key
or a ciphertext where a single random byte was randomly distorted in order to test for trivial failures of the CCA security.
The program will abort with an error message and return 1 if there was an error.
Otherwise it will output the key and ciphertext sizes and return 0.
* `test_vectors$ALG` generates 10000 sets of test vectors containing keys, ciphertexts and shared secrets
whose byte-strings are output in hexadecimal. It also generates test vector for decapsulation of invalid
(pseudorandom) ciphertexts.
The required random bytes are deterministic and come from SHAKE128 on empty input.
* `test_speed$ALG` reports the median and average cycle counts of 1000 executions of various internal functions
and the API functions for key generation, encapsulation and decapsulation.
By default the Time Step Counter is used.
If instead you want to obtain the actual cycle counts from the Performance Measurement Counters, export `CFLAGS="-DUSE_RDPMC"` before compilation.
Please note that the reference implementation in `ref/` is not optimized for any platform, and, since it prioritises clean code,
is significantly slower than a trivially optimized but still platform-independent implementation.
Hence benchmarking the reference code does not provide particularly meaningful results.
## Shared libraries
All implementations can be compiled into shared libraries by running
```sh
make shared
```
For example in the directory `ref/` of the reference implementation, this produces the libraries
```sh
libpqcrystals_kyber$ALG_ref.so
```
for all parameter sets `$ALG`, and the required symmetric crypto libraries
```
libpqcrystals_aes256ctr_ref.so
libpqcrystals_fips202_ref.so
```
All global symbols in the libraries lie in the namespaces `pqcrystals_kyber$ALG_ref`, `libpqcrystals_aes256ctr_ref` and `libpqcrystals_fips202_ref`. Hence it is possible to link a program against all libraries simultaneously and obtain access to all implementations for all parameter sets. The corresponding API header file is `ref/api.h`, which contains prototypes for all API functions and preprocessor defines for the key and signature lengths.