Reference implementations of PQC
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
 
 
 
 
Henry Case 59df9a3f73
Create SECURITY.md
il y a 3 ans
.cmake KEM and Sign C-API il y a 3 ans
.github/workflows Fix testing against KATs il y a 3 ans
3rd adds benchmark tool il y a 3 ans
public/pqc Adds DRBG based on AES il y a 3 ans
src Adds DRBG based on AES il y a 3 ans
test use aes_ctr_drbg crate il y a 3 ans
.astylerc Disable AStyle line endings formatter il y a 5 ans
.gitattributes Fix tidy for signing il y a 5 ans
.gitignore Parallel tests (#206) il y a 5 ans
.gitmodules fix path to gbench il y a 3 ans
CMakeLists.txt Adds DRBG based on AES il y a 3 ans
LICENSE Create LICENSE il y a 3 ans
README.md Update README.md il y a 3 ans
SECURITY.md Create SECURITY.md il y a 3 ans

README.md

PQ Crypto Catalog

This is a repository of post-quantum schemes copied from either the submission to the NIST Post-Quantum Standardization or PQClean project. The goal of the library is to provide easy to use API which enables quick experimentation with some post-quantum cryptographic schemes.

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

Schemes support

Name NIST Round x86 optimized
Kyber 3 x
NTRU 3 x
SABER 3 x
FrodoKEM 3
NTRU Prime 3 x
HQC-RMRS 3 x
Dilithium 3 x
Falcon 2
Rainbow 3
SPHINCS+ SHA256/SHAKE256 3 x

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>

    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));

    const params_t *p = pqc_kem_alg_by_id(KYBER512);
    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