149 lines
7.7 KiB
Markdown
149 lines
7.7 KiB
Markdown
# PQClean
|
|
|
|
[](https://travis-ci.com/PQClean/PQClean)
|
|
[](https://ci.appveyor.com/project/PQClean/pqclean/branch/master)
|
|
[](https://circleci.com/gh/PQClean/PQClean/tree/master)
|
|
|
|
**PQClean**, in short, is an effort to collect **clean** implementations of the post-quantum
|
|
schemes that are in the
|
|
[NIST post-quantum project](https://csrc.nist.gov/projects/post-quantum-cryptography).
|
|
The goal of PQClean is to provide *standalone implementations* that
|
|
|
|
* can easily be integrated into libraries such as [liboqs](https://openquantumsafe.org/#liboqs) or [libpqcrypto](https://libpqcrypto.org/);
|
|
* can efficiently upstream into higher-level protocol integration efforts such as [Open Quantum Safe](https://openquantumsafe.org/#integrations);
|
|
* can easily be integrated into benchmarking frameworks such as [SUPERCOP](https://bench.cr.yp.to/supercop.html);
|
|
* can easily be integrated into frameworks targeting embedded platforms such as [pqm4](https://github.com/mupq/pqm4);
|
|
* are suitable starting points for architecture-specific optimized implementations;
|
|
* are suitable starting points for evaluation of implementation security; and
|
|
* are suitable targets for formal verification.
|
|
|
|
What PQClean is **not** aiming for is
|
|
|
|
* a build system producing an integrated library of all schemes;
|
|
* including benchmarking of implementations; and
|
|
* including integration into higher-level applications or protocols.
|
|
|
|
As a first main target, we are collecting C implementations that fulfill the requirements
|
|
listed below.
|
|
|
|
## Requirements on C implementations that are automatically checked
|
|
|
|
_The checking of items on this list is still being developed. Checked items should be working._
|
|
|
|
* [x] Code is valid C99
|
|
* [x] Passes functional tests
|
|
* [x] API functions do not write outside provided buffers
|
|
* [x] Compiles with `-Wall -Wextra -Wpedantic -Werror` with `gcc` and `clang`
|
|
* [x] Consistent test vectors across runs
|
|
* [x] Consistent test vectors on big-endian and little-endian machines
|
|
* [x] Consistent test vectors on 32-bit and 64-bit machines
|
|
* [x] No errors/warnings reported by valgrind
|
|
* [x] No errors/warnings reported by address sanitizer
|
|
* [ ] Only dependencies:
|
|
* [x] `fips202.c`
|
|
* [x] `sha2.c`
|
|
* [ ] `aes.c`
|
|
* [x] `randombytes.c`
|
|
* [x] API functions return `0` on success
|
|
* [x] No dynamic memory allocations
|
|
* [ ] No branching on secret data (dynamically checked using valgrind)
|
|
* [ ] No access to secret memory locations (dynamically checked using valgrind)
|
|
* [x] Separate subdirectories (without symlinks) for each parameter set of each scheme
|
|
* [x] Builds under Linux, MacOS, and Windows
|
|
* [x] Linux
|
|
* [x] MacOS
|
|
* [x] Windows
|
|
* [x] Makefile-based build for each separate scheme
|
|
* [x] Makefile-based build for Windows (`nmake`)
|
|
* [x] All exported symbols are namespaced with `PQCLEAN_SCHEMENAME_`
|
|
* [x] Each implementation comes with a `LICENSE` file (see below)
|
|
* [x] Each scheme comes with a `META.yml` file giving details about version of the algorithm, designers
|
|
* [x] Each individual implementation is specified in `META.yml`.
|
|
|
|
|
|
## Requirements on C implementations that are manually checked
|
|
|
|
* Makefiles without explicit rules (rely on implicit, built-in rules)
|
|
* `#ifdef`s only for header encapsulation
|
|
* No stringification macros
|
|
* Output-parameter pointers in functions are on the left
|
|
* `const` arguments are labeled as `const`
|
|
* All exported symbols are namespaced in place
|
|
* All integer types are of fixed size, using `stdint.h` types (including `uint8_t` instead of `unsigned char`)
|
|
* Integers used for indexing are of size `size_t`
|
|
* variable declarations at the beginning (except in `for (size_t i=...`)
|
|
|
|
|
|
## Clean C implementations currently in PQClean
|
|
|
|
Currently, the continuous-integration and testing environment of PQClean is still work in progress
|
|
and as a consequence PQClean does not yet have many implementations.
|
|
|
|
<!--
|
|
Currently, PQClean includes clean C implementations of the following KEMs:
|
|
|
|
* [Kyber-512](https://pq-crystals.org/kyber/)
|
|
* [Kyber-768](https://pq-crystals.org/kyber/)
|
|
* [Kyber-1024](https://pq-crystals.org/kyber/)
|
|
|
|
Currently, PQClean includes clean C implementations of the following signature schemes:
|
|
|
|
* [Dilithium-III](https://pq-crystals.org/dilithium/)
|
|
-->
|
|
|
|
## API used by PQClean
|
|
|
|
PQClean is essentially using the same API as required for the NIST reference implementations,
|
|
which is also used by SUPERCOP and by libpqcrypto. The only two differences to that API are
|
|
the following:
|
|
* All lengths are passed as type `size_t` instead of `unsigned long long`; and
|
|
* Signatures offer two additional functions that follow the "traditional" approach used
|
|
in most software stacks of computing and verifying signatures instead of producing and
|
|
recovering signed messages. Specifically, those functions have the following name and signature:
|
|
|
|
```
|
|
int crypto_sign_signature(uint8_t *sig, size_t *siglen, const uint8_t *m, size_t mlen, const uint8_t *sk);
|
|
int crypto_sign_verify(const uint8_t *sig, size_t siglen, const uint8_t *m, size_t mlen, const uint8_t *pk);
|
|
```
|
|
|
|
## Building PQClean
|
|
|
|
As noted above, PQClean is **not** meant to be built as a single library: it is a collection of source code that can be easily integrated into other libraries. The PQClean repository includes various test programs which do build various files, but you should not use the resulting binaries for any purpose.
|
|
|
|
List of required dependencies: ``gcc or clang, make, python3, python-yaml library, valgrind, astyle (>= 3.0)``.
|
|
|
|
## Using source code from PQClean in your own project
|
|
|
|
Each implementation directory in PQClean (e.g., crypto\_kem/kyber768\clean) can be extracted for use in your own project. You will need to:
|
|
|
|
1. Copy the source code from the implementation's directory into your project.
|
|
2. Add the files to your project's build system.
|
|
3. Provide instantiations of any of the common cryptographic algorithms used by the implementation. This likely includes `common/randombytes.h` (a cryptographic random number generator), and possibly `common/sha2.h` (the SHA-2 hash function family) and `common/fips202.h` (the SHA-3 hash function family).
|
|
|
|
Regarding #2, adding the files to your project's build system, each implementation in PQClean is accompanied by example two makefiles that show how one could build the files for that implementation:
|
|
|
|
- The file `Makefile` which can be used with GNU Make, BSD Make, and possibly others.
|
|
- The file `Makefile.Microsoft_nmake` which can be used with Visual Studio's nmake.
|
|
|
|
## License
|
|
|
|
Each subdirectory containing implementations contains a LICENSE file stating under what license
|
|
that specific implementation is released. All other code for testing etc. in this repository
|
|
is released under the conditions of [CC0](http://creativecommons.org/publicdomain/zero/1.0/).
|
|
|
|
## Running tests locally
|
|
|
|
While we run extensive automatic testing on [Travis CI][travis-pqc] and [Appveyor][appveyor-pqc], most tests can also be run locally.
|
|
To do this, make sure the following is installed:
|
|
|
|
* Python 3.5+
|
|
* `nosetests` or `nose2` (either for Python 3)
|
|
|
|
Run the Python-based tests by going into the `test` directory and running `nosetests -v` or `nose2 -B -v`, depending on what you installed.
|
|
If you have the `rednose` plugin for `nosetests` installed, run `nosetests --rednose` to get colored output.
|
|
|
|
You may also run `python <testmodule>` where `<testmodule>` is any of the files starting with `test_` in the `test/` folder.
|
|
|
|
[travis-pqc]: https://travis-ci.com/PQClean/PQClean/
|
|
[appveyor-pqc]: https://ci.appveyor.com/project/PQClean/pqclean
|