liboqs icon indicating copy to clipboard operation
liboqs copied to clipboard

C library for prototyping and experimenting with quantum-resistant cryptography

Results 128 liboqs issues
Sort by recently updated
recently updated
newest added

`liboqs` integrates various code bases under one "quantum-safe friendly" API. For some algorithms, integration is done manually, for some automated (`copy_from_upstream`, `copy_from_xkcp`). While care has been taken to document the...

enhancement

Preserving @baentsch's suggestion from #1618 so that it doesn't get buried after the merge: >> I don't know how to change the "2 approvals needed" rule to only apply to...

enhancement

Currently, we handle `malloc` failures in common code by immediately exiting with a nonzero return code. It [could be a good idea](https://github.com/open-quantum-safe/liboqs/pull/1650#discussion_r1498209133) to give the program a chance to clear...

refactor

At least for the [production ready](https://github.com/orgs/open-quantum-safe/discussions/1689) variant of the library, align with the platforms supported by [OpenSSL](https://github.com/openssl/general-policies/blob/master/policy-supplemental/platforms.md).

platform-specific

OpenSSL is adding the feature for [SHAKE to squeeze multiple times with different output sizes](https://github.com/openssl/openssl/pull/21511) which changes the [baseline in liboqs OpenSSL integration for SHA3](https://github.com/open-quantum-safe/liboqs/blob/0dafd4f02c5a8fc000502ae51005a9962b671860/src/common/sha3/ossl_sha3.c#L147-L162). This issue is to propose...

refactor
good first issue

Enabling BIKE on x86 builds leads to [test failures](https://app.circleci.com/pipelines/github/open-quantum-safe/liboqs/3279/workflows/e8d367d9-2717-4105-a2f4-4bee216b0de3/jobs/26246), so we don't do it. However, the [upstream](https://github.com/awslabs/bike-kem/tree/master) documentation states that BIKE is supported for x86. It would be nice to...

future-work
platform-specific

In [compiler_opts.cmake](https://github.com/open-quantum-safe/liboqs/blob/main/.CMake/compiler_opts.cmake#L112), we have the following code: ``` elseif(USE_SANITIZER STREQUAL "Memory") add_compile_options(-fsanitize=address) set(SANITIZER_LD_FLAGS "-fsanitize=memory") elseif(USE_SANITIZER STREQUAL "MemoryWithOrigins") ... ``` I opened this issue to ask whether we should be running...

enhancement
future-work

Dear colleagues, we are planning to package liboqs for Fedora. We build liboqs with `-DOQS_ALGS_ENABLED=STD` to minimize support of non-standardized algorithms. We found that the folders ``` ./src/kem/kyber/pqclean_kyber*_aarch64 ./src/sig/dilithium/pqclean_dilithium*_aarch64 ./src/sig/sphincs/pqclean_sphincs*...

enhancement

https://github.com/open-quantum-safe/liboqs/pull/1585 updates HQC to the 2023-04-30 (currently latest) version, but it only includes a "clean" portable C implementation. An optimized AVX2 implementation is available from https://pqc-hqc.org, although it has a...

enhancement

Currently liboqs uses OpenSSL as the default backend for low-level support algorithms, such as AES and SHA3 if the `OQS_USE_OPENSSL` build flag is `ON`; otherwise it will use the bundled...

enhancement
help wanted