liboqs

liboqs copied to clipboard

Introduce constant time build variable

1

With https://github.com/open-quantum-safe/liboqs/pull/1618 CT testing toggles to testing the reference code. At the same time we enable building optimized code (activated in most use cases). If the optimized code for some...

baentsch

CI tooling for variable-time operations on some platforms

1

Is there any tooling available that would have allowed us to detect #1631 and #1636?

dstebila

It would be nice to have documentation that links to the "sources of truth" for our KAT hashes. This would improve both ease of maintenance for developers and transparency for...

SWilson4

RISC-V support

10

Hello, I am porting various packages to riscv64 platform. I saw comments on compilation in CMakeLists.txt: ``` Compilation on an unsupported processor should only be used for testing, as it...

hack3ric

Integrate Kyber implementation from libjade

4

libjade is a Jasmin project involving @cryptojedi and others that has a formally verified implementation of Kyber for some platforms. We have talked about incorporating that into liboqs. From an...

dstebila

Environment-specific Classic McEliece constant-time leaks

4

**Describe the bug** The testing suite is reporting [potential memory leaks](https://github.com/open-quantum-safe/liboqs/pull/1527#issuecomment-1701305585) ([test_constant_time.txt](https://github.com/open-quantum-safe/liboqs/files/12553409/test_constant_time.txt)) for Classic McEliece which are not documented in the suppression files. **To Reproduce** I am unable to reproduce...

praveksharma

This issue is to suggest adding tests to (automatically) exercise all scripts within this project. The goals would be - to ensure no "local setup" problems will hit anyone (new)...

baentsch

Many OQS functions return void "for historical reasons". Nevertheless they can fail. Right now two (pretty user unfriendly) macros are used (sporadically) to react to internal failures: https://github.com/open-quantum-safe/liboqs/blob/9f912c957bfe7f4b894aa9661168a310e8dd1a58/src/common/common.h#L22-L49 This issue...

baentsch

AFAIK `liboqs` only has multi-processing tests, but no multi-threading tests. Please point to such tests if I'm wrong. Otherwise this issue is to suggest adding such tests to catch problems...

baentsch

Use modern CMake syntax

6

Instead of depending on `make/msbuild etc`, we should use only modern `cmake` and `ctest`, such as ```shell cmake -B build -DCMAKE_FLAGS... cmake --build build --parallel 4 [--target ... ] ctest...

vsoftco