This update for liboqs, oqs-provider fixes the following issues:
Updated to 0.16.0:
Deprecation notice:
Security issues:
encaps_derand pointer dereferencecrypto_sign_open()secure_cleanOQS_MEM_BLACK_BOX and applied to ct_select in FrodoKEMSignificant change:
FrodoKEM algorithm change:
KEM_efrodokem_<640|976|1344>_<aes|shake>), and
the salted variant of FrodoKEM was added under the prior names
(KEM_frodokem_<640|976|1344>_<aes|shake>).
Ephemeral FrodoKEM is recommended for applications
where each keypair will encapsulate only a small number
of shared secrets and ciphertexts. Standard (salted)
FrodoKEM is recommended for applications where each keypair
is expected to encapsulate large number of ciphertexts. Please consult
upstream
for more details.SIG_ml_dsa_<44|65|87>.KEM_hqc_<1|3|5> is now enabled
by default.OQS_ENABLE_SIG_MQOM.KEM_ntruprime_sntrup761.Bug fixes:
EVP_DigestSqueeze is unavailable #2433#if/#elif chains #2396Update to 0.15.0:
Significant changes:
Bug fixes:
Miscellaneous:
Deprecation notice: liboqs 0.15.0 is the last version to officially support SPHINCS+. SPHINCS+ will be removed in the 0.16.0 release and replaced by SLH-DSA. liboqs 0.15.0 also removes support for Dilithium.
Updated to 0.14.0:
Key encapsulation mechanisms:
Digital signature schemes:
Other changes:
CVE-2025-52473: Disabled compiler optimizations for HQC to avoid secret-dependent branches. Thank you to Zhenzhi Lai and Zhiyuan Zhang from from the University of Melbourne and the Max Planck Institute for Security and Privacy for identifying the issue. (bsc#1246301)
new major library version liboqs.so.8
add -DOQS_ENABLE_KEM_HQC=ON even due to security issues, as otherwise we dropped binary compatibility with postquantumcryptoengine (bsc#1242701)
Do not embed the buildhost's kernel version to help reproducibility (bsc#1101107)
Updated to 0.13.0:
Key encapsulation mechanisms
Digital signature schemes
Update to 0.11.0:
Updated to 0.10.0:
updated to 0.9.0: