1
1
镜像来自 https://github.com/henrydcase/pqc.git synced 2024-11-22 15:39:07 +00:00
Go to file
2021-05-17 16:00:10 +01:00
.cmake KEM and Sign C-API 2021-03-24 21:06:56 +00:00
.github/workflows Fix testing against KATs 2021-03-25 18:47:56 +00:00
3rd SIKE: enable optimized version 2021-04-26 12:20:39 +01:00
buid.dbg add drone.yml 2021-04-26 12:20:39 +01:00
public/pqc reorder scheme definitions 2021-05-17 11:24:49 +01:00
src prefix structs with pqc_ 2021-05-10 16:36:24 +01:00
test change comment 2021-05-17 16:00:10 +01:00
.gitignore add benchmarking framework 2021-04-22 21:41:46 +01:00
.gitmodules SIKE: enable optimized version 2021-04-26 12:20:39 +01:00
CMakeLists.txt fix build 2021-04-26 12:36:24 +01:00
LICENSE Create LICENSE 2021-03-25 09:17:59 +00:00
README.md Update README.md 2021-05-15 22:21:09 +01:00
SECURITY.md Create SECURITY.md 2021-04-21 10:50:15 +01:00

PQ Crypto Catalog

Implementation of quantum-safe signature and KEM schemes submitted to NIST PQC Standarization 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.

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
SIKE/p434 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>

    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