kriskwiatkowski / pqc

Licence: BSD-3-Clause license
Reference implementations of post-quantum cryptographic primitives

Programming Languages

c
50402 projects - #5 most used programming language
assembly
5116 projects
CMake
9771 projects
rust
11053 projects
C++
36643 projects - #6 most used programming language
POV-Ray SDL
72 projects

Projects that are alternatives of or similar to pqc

pqps
Tools for power measurements of post-quantum cryptographic algorithms
Stars: ✭ 18 (-14.29%)
Mutual labels:  post-quantum
openssl
Fork of OpenSSL that includes prototype quantum-resistant algorithms and ciphersuites based on liboqs
Stars: ✭ 215 (+923.81%)
Mutual labels:  post-quantum
liboqs-rust
Rust bindings for liboqs
Stars: ✭ 46 (+119.05%)
Mutual labels:  post-quantum
dilithium
No description or website provided.
Stars: ✭ 166 (+690.48%)
Mutual labels:  post-quantum
pqcrypto
Rust Post-Quantum cryptography
Stars: ✭ 124 (+490.48%)
Mutual labels:  post-quantum
openssh
Fork of OpenSSH that includes prototype quantum-resistant key exchange and authentication in SSH based on liboqs
Stars: ✭ 80 (+280.95%)
Mutual labels:  post-quantum
kyber
No description or website provided.
Stars: ✭ 170 (+709.52%)
Mutual labels:  post-quantum

PQ Crypto Catalog

Implementation of quantum-safe signature and KEM schemes submitted to NIST PQC Standardization Process.

The goal is to provide an easy-to-use API in C and Rust to enable experimentation. The code is derived from the submission to the NIST Post-Quantum Standardization, either directly or by leveraging PQClean project.

Users shouldn't expect any level of security provided by this code. The library is not meant to be used on live production systems.

Supported schemes

All schemes selected by NIST duing PQC standardization:

Name x86 optimized
Kyber x
Dilithium x
Falcon
SPHINCS+ SHA256/SHAKE256 x

KEM candidates for an additional round 4.

Name x86 optimized
HQC-RMRS x
McEliece

Building

CMake is used to build the library:

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

Build outputs two libraries, a static libpqc_s.a and dynamic libpqc.so, which can be linked with a project.

API

Library provides simple API, wrapping PQClean. For example to use KEM, one should call the library in following way:

    #include <pqc/pqc.h>

    const params_t *p = pqc_kem_alg_by_id(KYBER512);
    std::vector<uint8_t> ct(ciphertext_bsz(p));
    std::vector<uint8_t> ss1(shared_secret_bsz(p));
    std::vector<uint8_t> ss2(shared_secret_bsz(p));
    std::vector<uint8_t> sk(private_key_bsz(p));
    std::vector<uint8_t> pk(public_key_bsz(p));

    pqc_keygen(p, pk.data(), sk.data());
    pqc_kem_encapsulate(p, ct.data(), ss1.data(), pk.data());
    pqc_kem_decapsulate(p, ss2.data(), ct.data(), sk.data());

    p = pqc_sig_alg_by_id(DILITHIUM2);
    size_t sigsz = sig.capacity();
    pqc_keygen(p, pk.data(), sk.data());
    pqc_sig_create(p, sig.data(), &sigsz, msg.data(), msg.size(), sk.data());
    pqc_sig_verify(p, sig.data(), sig.size(), msg.data(), msg.size(), pk.data());

See test implemetnation in test/ut.cpp for more details.

Rust binding

Rust bindgings are provided in the src/rustapi/pqc-sys and can be regenerated automatically by running cargo build in that directory.

Testing against Known Answer Tests

Algorithms are tested against KATs, by the Rust-based runner implemented in the test/katrunner (only verification/decpaulation). The runner uses katwalk crate for parsing NIST format. To run it:

    cd test/katrunner
    curl http://amongbytes.com/~flowher/permalinks/kat.zip --output kat.zip
    unzip kat.zip
    cargo run -- --katdir KAT
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].