liboqs-0.7.1-bp155.2.19

- Ship the README.md mentioned in the description.
- Compact descriptions.

- Add upstream changes:
  * 0001-Add-support-for-powerpc64.-1160.patch
  * 0002-Mark-stack-non-executable-when-compiling-with-clang-.patch
- Spec cleanup

- Stop building with march=native to get reproducible binaries (boo#1100677)

- Trim redundancies from description. Remove old specfile
  constructs.

- initial import of the liboqs Open Quantum Safe library, version 0.7.1

- liboqs-python311.patch: use python3.11 for tests on SLES 15, the
  python 3.6 there is too old.
- disable KEM_HQC and SIG_MQOM and KEM_NTRUPRIME on s390x for now,
  testsuite fails.

- disabled network using testcases.
- Updated to 0.16.0:
  Deprecation notice:
  - SPHINCS+ was removed in 0.16.0.
  Security issues:
  - Fixed uninitialized `encaps_derand` pointer dereference
  - CVE-2026-46344, CVE-2026-44518: Fixed out-of-bounds read in XMSS/XMSS^MT signature verification
    (bsc#1267007 bsc#1267001)
  - Fixed Integer underflow in CROSS `crypto_sign_open()`
  - Fixed incorrect array size when calling `secure_clean`
  - Implemented optimization barrier `OQS_MEM_BLACK_BOX` and applied to `ct_select` in FrodoKEM
  Significant change:
  FrodoKEM algorithm change:
  * Existing FrodoKEM in 0.15.0 was renamed to ephemeral
    FrodoKEM (`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](https://github.com/microsoft/PQCrypto-LWEKE/#frodokem-learning-with-errors-key-encapsulation)
    for more details.
  * mldsa-native integration:
    mldsa-native is a secure, fast, and portable C90 implementation of the
    ML-DSA post-quantum signature standard. It also includes optimized
    builds for x86_64 and aarch64. It is now the default implementation
    behind `SIG_ml_dsa_<44|65|87>`.
  * Updated HQC implementation:
    The HQC implementations in liboqs were updated to 20250822
    spec. Its upstream switched from PQClean to the [official
    repo](https://gitlab.com/pqc-hqc/hqc). `KEM_hqc_<1|3|5>` is now enabled
    by default.
  * MQOM integration and memory-optimized build flag:
    MQOM is a third-round candidate in NIST's Additional Digital
    Signatures for the PQC Standardization Process. Portable,
    x86_64-optimized, and memory-optimized implementations were
    integrate into liboqs under `OQS_ENABLE_SIG_MQOM`.
  * OpenSSH implementation of NTRU Prime:
    A public-domain OpenSSH implementation of NTRUPrime761
    replaced the PQClean implementation as the default backend for
    `KEM_ntruprime_sntrup761`.
  Bug fixes:
  - Fixed incremental absorption bug in AVX512VL SHA3-512 [#2442](https://github.com/open-quantum-safe/liboqs/pull/2442)
  - Implemented fallback for when `EVP_DigestSqueeze` is unavailable [#2433](https://github.com/open-quantum-safe/liboqs/pull/2433)
  - Added API for detecting stateful signature support at runtime [#2434](https://github.com/open-quantum-safe/liboqs/pull/2434)
  - Fixed missing initialization and indexing bug in LMS [#2416](https://github.com/open-quantum-safe/liboqs/pull/2416)
  - Fixed erroneous MAYO_OK despite failed sample_solution() attempts in MAYO [#2403](https://github.com/open-quantum-safe/liboqs/pull/2403)
  - Limited pytest parallelism to prevent memory exhaustion in constrained environment [#2397](https://github.com/open-quantum-safe/liboqs/pull/2397)
  - Fixed cuPQC ML-KEM derand symbol names and `#if/#elif` chains [#2396](https://github.com/open-quantum-safe/liboqs/pull/2396)
  - Tightened Windows compiler detection [#2394](https://github.com/open-quantum-safe/liboqs/pull/2394)
  - Fixed mismatched macros in LMS [#2379](https://github.com/open-quantum-safe/liboqs/pull/2379)
  - Made fuzzers tolerant to disabled algorithms [#2359](https://github.com/open-quantum-safe/liboqs/pull/2359)
  - Removed inlined exponentiation in CROSS-RSDPG-1 [#2357](https://github.com/open-quantum-safe/liboqs/pull/2357)
  - Fixed incorrect arg register update in AVX512 Keccak [#2330](https://github.com/open-quantum-safe/liboqs/pull/2330)

- Update to 0.15.0:
  * Significant changes:
  - Integrated SLH-DSA implementation from pq-code-package/slhdsa-c
  - SLH-DSA ACVP tests (#2237)
  - Integrate SLH-DSA-C Library (#2175)
  - Added NTRU back (#2176)
  - Removed all Dilithium implementations (#2275)
  - Replaced SPHINCS+ with SLH-DSA for CMake build option
    OQS_ALGS_ENABLED=STD (#2290)
  - Updated CROSS to version 2.2 (#2247)
  - Included DeriveEncapsulation functionality (#2221)
  - Integrated ML-KEM implementation from ICICLE-PQC (#2216)
  * Bug fixes:
  - Fixed erroneously disabled LMS variants with build flag
    OQS_ENABLE_SIG_STFL_LMS (#2310)
  - Fixed incorrect import in OV-III-pkc_skc (#2299)
  - Fixed incorrect actual signature length in signature full-cycle
    speed test (#2293)
  - Fixed ICICLE ML-KEM integration (#2288)
  - Disabled strict aliasing on SPHINCS+-SHAKE (#2264)
  - Fixed uninitialized length_encaps_seed for NTRU implementations (#2266)
  - Changed 64 bit add to 32 bit add to wrap on 32 bit counter for
    AES-CTR AES-NI implementation (#2252)
  - Improved random number generator security (#2225)
  - Added Classic McEliece sanitization patch (#2218)
  * Miscellaneous:
  - Deprecated noregress scripts (#2295)
  - Updated no-pass explanation for constant-time testing (#2294)
  - Re-enabled all ACVP tests (#2283)
  - Updated license info for ML-KEM (#2250)
  - Added Poutine SASL (#2213)
  - Updated ACVP to 1.1.0.40 (#2172)
  - Switched to dev mode for 0.14.1 (#2199)
  * 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.
  * Rebase liboqs-fix-prototypemismatch.patch

- Updated to 0.14.0:
  * Key encapsulation mechanisms:
  - HQC: Disabled compiler optimizations to avoid secret-dependent branching in certain configurations. HQC remains disabled by default.
  - ML-KEM: Updated the default ML-KEM implementation to [PQCP's mlkem-native v1.0.0](https://github.com/pq-code-package/mlkem-native/releases/tag/v1.0.0).
  * Digital signature schemes:
  - New API: added an API function to check if a signature scheme supports signing with a context string.
  - SNOVA: added [SNOVA](https://snova.pqclab.org/) from NIST Additional Signature Schemes Round 2.
  * Other changes:
  - Added an AVX512VL-optimized backend for SHA3.
  - Improved memory management throughout the codebase.
- 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

- enable testsuite

- add -DOQS_ENABLE_KEM_HQC=ON even due to security issues, as otherwise
  we dropped binary compatibility with postquantumcryptoengine (bsc#1242701)

- Add reproducible.patch to not embed the buildhost's kernel version (boo#1101107)

- Updated to 0.13.0:
  - Key encapsulation mechanisms
  - New API: Added a deterministic key generation and API for KEMs (only ML-KEM supported at the moment).
  - ML-KEM: Changed the default ML-KEM implementation to [PQCP's mlkem-native](https://github.com/pq-code-package/mlkem-native). There are three variants: Portable C, AVX2, and AArch64. Large +parts of these implementations are formally verified: all of the C code is verified for memory and type safety using [CBMC](https://github.com/diffblue/cbmc) and the functional correctness +of the core AArch64 assembly routines is verified using [HOL-Light](https://github.com/jrh13/hol-light).
  - ML-KEM: Added support for the ML-KEM implementation from [Nvidia cuPQC](https://developer.nvidia.com/cupqc), a GPU accelerated cryptography library.
  - ML-KEM: Implementation from mlkem-native upstream updated to add Pair-wise Consistency Test (PCT) and Intel CET support.
  - ML-KEM: Improved testing of ML-KEM keys.
  - HQC: Disabled HQC by default until [a new security flaw](https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/Wiu4ZQo3fP8) is fixed.
  - Digital signature schemes
  - ML-DSA: Improved testing for ML-DSA.
  - CROSS: Updated to NIST Additional Signatures Round 2 version.
  - MAYO: Updated to NIST Additional Signatures Round 2 version.
  - UOV: Added support for UOV algorithm from NIST Additional Signatures Round 2.

- Updated to 0.12.0:
  - This release updates the ML-DSA implementation to the [final
    FIPS 204](https://csrc.nist.gov/pubs/fips/204/final) version. This
    release still includes the NIST Round 3 version of Dilithium for
    interoperability purposes, but we plan to remove Dilithium Round 3 in
    a future release.
  - This will be the last release of liboqs to include Kyber (that is,
    the NIST Round 3 version of Kyber, prior to its standardization by NIST
    as ML-KEM in FIPS 203). Applications should switch to ML-KEM (FIPS 203).
  - The addition of ML-DSA FIPS 204 final version to liboqs has
    introduced a new signature API which includes a context string
    parameter. We are planning to remove the old version of the API
    without a context string in the next release to streamline the
    API and bring it in line with NIST specifications. Users who
    have an opinion on this removal are invited to provide input at
    https://github.com/open-quantum-safe/liboqs/issues/2001.
  Security issues:
  - CVE-2024-54137: Fixed bug in HQC decapsulation that leads to incorrect
    shared secret value during decapsulation when called with an invalid
    ciphertext. (bsc#1234292)

- Updated to 0.11.0:
  * This release updates ML-KEM implementations to their final FIPS 203
    https://csrc.nist.gov/pubs/fips/203/final versions .
  * This release still includes the NIST Round 3 version of Kyber for
    interoperability purposes, but we plan to remove Kyber Round 3 in a
    future release.
  * Additionally, this release adds support for MAYO and CROSS
    digital signature schemes from [NIST Additional Signatures Round 1
    https://csrc.nist.gov/Projects/pqc-dig-sig/round-1-additional-signatures
    along with stateful hash-based signature schemes XMSS
    https://datatracker.ietf.org/doc/html/rfc8391 and LMS
    https://datatracker.ietf.org/doc/html/rfc8554.
  * Finally, this release provides formally verified
    implementations of Kyber-512 and Kyber-768 from libjade
    https://github.com/formosa-crypto/libjade/releases/tag/release%2F2023.05-2
  * LMS and XMSS are disabled by default due to the security risks associated with their use in software.
    See the note on stateful hash-based signatures in CONFIGURE.md
  * Key encapsulation mechanisms:
  - Kyber: Added formally-verified portable C and AVX2 implementations
    of Kyber-512 and Kyber-768 from libjade.
  - ML-KEM: Updated portable C and AVX2 implementations of ML-KEM-512,
    ML-KEM-768, and ML-KEM-1024 to FIP 203 version.
  - Kyber: Patched ARM64 implementations of Kyber-512, Kyber-768, and
    Kyber-1024 to work with AddressSanitizer.
  * Digital signature schemes:
  - LMS/XMSS: Added implementations of stateful hash-based signature
    schemes: XMSS and LMS
  - MAYO: Added portable C and AVX2 implementations of MAYO signature
    scheme from NIST Additional Signatures Round 1.
  - CROSS: Added portable C and AVX2 implementations of CROSS signature
    scheme from NIST Additional Signatures Round 1.
  * Other changes:
  - Added callback API to use custom implementations of AES, SHA2, and SHA3.
  - Refactor SHA3 implementation to use OpenSSL's EVP_DigestSqueeze() API.
- new library major version 6