oqs-provider icon indicating copy to clipboard operation
oqs-provider copied to clipboard

OpenSSL 3 provider containing post-quantum algorithms

Results 35 oqs-provider issues
Sort by recently updated
recently updated
newest added

[Profiling runs](https://openquantumsafe.org/benchmarking/visualization/handshakes.html) for TLS handshaking showed a marked increase in heap usage when switching from oqs-openssl111 to oqsprovider+openssl3. Most likely, things like [this](https://github.com/open-quantum-safe/oqs-provider/blob/12a6418f1b6c532a88bccd2d6dac5c10a2460af4/oqsprov/oqs_sig.c#L488) need to be improved. In general, review...

bug
enhancement

Code to integrate all supported QSC algorithms is currently generated using `python` and `jinja2` using the full `liboqs` code base. This issue is to propose eliminating this dependency by using...

/Suppose I configure the OQS provider for cross-compilation with ``` cmake \ -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_PROCESSOR=aarch64 \ -DCMAKE_CROSSCOMPILING_EMULATOR=qemu-aarch64 \ -DCMAKE_C_COMPILER=.../bin/aarch64-linux-gnu \ .. ``` My build fails with ``` $ make VERBOSE=1 [...]...

futurework

**Describe the bug** I was looking around at the source, in this case [`oqsprov/oqsprov.c`](https://github.com/open-quantum-safe/oqs-provider/blob/main/oqsprov/oqsprov.c), which I noticed these sorts of calls: https://github.com/open-quantum-safe/oqs-provider/blob/4dec0fe04f4e9814775026a657e40045fdf075d3/oqsprov/oqsprov.c#L523 That's really not recommended. Consider if there are...

futurework

Follow-up after #16: - So far, the shared secret uses "Comb-Concat" as described in https://tools.ietf.org/html/draft-ietf-tls-hybrid-design-01#appendix-B.4.1. The same is done in OSSL111. This is suitable for inputting the shared secret to...

enhancement