liboqs
liboqs copied to clipboard
open-quantum-safe
C library for prototyping and experimenting with quantum-resistant cryptography
Follow the approach taken by [OpenSSL](https://github.com/openssl/openssl/blob/master/fuzz/README.md) or another one: Suggestions welcome below.
Ideally, this project should be compilable via emscripten to WASM. Adding compatibility and documentation to make this possible should exist.
When a KEM keypair is derived in liboqs, it relies on randomness using [rand.h](https://github.com/open-quantum-safe/liboqs/blob/main/src/common/rand/rand.h). In some situations, it's useful to generate keypairs deterministically from a seed. When [RFC9180](https://www.rfc-editor.org/rfc/rfc9180#name-cryptographic-dependencies) defines a...
As per [this discussion](https://github.com/open-quantum-safe/liboqs/issues/1199#issuecomment-1110578343) and the [feature announcement of clang-15](https://clang.llvm.org/docs/ReleaseNotes.html) consider ensuring `void` parameter lists are declared as such. Impacted code bases: liboqs (some few locations & generated code), Frodo,...
As per a discussion on https://github.com/open-quantum-safe/liboqs/pull/1184#issuecomment-1026988491, it might be worth adding a build variable to `liboqs` that specifies the instruction set version when compiling for amv8. This would allow individuals...
Ensure all code is designed such that it can not only be configured at compile time to deal with different CPU feature sets (e.g., presence/absence of AVX2) but also handle...
[LMS](https://datatracker.ietf.org/doc/html/rfc8554) and [XMSS](https://datatracker.ietf.org/doc/html/rfc8391) as standardized by [CFRG](https://irtf.org/cfrg) may be of use to Verisign and others.
The implementation of this feature is brittle when new optimizations/cmake-subtargets are introduced (as was the case with #1117): Using the feature then leads to "strange" performance drops (vs. building all...
[Circl](https://github.com/cloudflare/circl) implements several algorithms also provided by liboqs. An automated interop test set would be good to avoid issues like #909 in the future. Possibly an application for [liboqs-go](https://github.com/open-quantum-safe/liboqs-go)?
After reading https://queue.acm.org/detail.cfm?id=3468263 one might be tempted to activate more compiler warning flags than just `-Wall -Wextra`). When doing this in `liboqs` (only adding `-Wnull-dereference` and `-Wduplicated-branches`) the following code...
Metadata
Owner
Metadata
C library for prototyping and experimenting with quantum-resistant cryptography