Releases: open-quantum-safe/oqs-provider
Release 0.10.0
oqs-provider 0.10.0
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is release candidate 1 of version 0.10.0 of oqs-provider which continues from the earlier 0.9.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.14.0 of liboqs.
Deprecation notice
This release of oqsprovider removes support for composite signatures.
What's New
What's Changed
- 0.9.0 release by @praveksharma in #681
- Add SNOVA signatures by @vacuas in #674
- Switch to dev mode by @praveksharma in #686
- chore: remove Windows 2019 by @ryjones in #685
- Remove Composite Signature logic, templating, and documentation. by @praveksharma in #687
New Contributors
Full Changelog: 0.9.0...0.10.0
Contributors
Assets 2
Release 0.10.0 RC1
oqs-provider 0.10.0-rc1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is release candidate 1 of version 0.10.0 of oqs-provider which continues from the earlier 0.9.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.14.0 of liboqs.
Deprecation notice
This release of oqsprovider removes support for composite signatures.
What's New
What's Changed
- 0.9.0 release by @praveksharma in #681
- Add SNOVA signatures by @vacuas in #674
- Switch to dev mode by @praveksharma in #686
- chore: remove Windows 2019 by @ryjones in #685
- Remove Composite Signature logic, templating, and documentation. by @praveksharma in #687
New Contributors
Full Changelog: 0.9.0...0.10.0-rc1
Contributors
Assets 2
0.9.0
848b4e6
praveksharma
Pravek Sharma
oqs-provider 0.9.0
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.9.0 of oqs-provider which continues from the earlier 0.8.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.13.0 of liboqs.
Deprecation notice
This release of oqsprovider removes default support for Kyber and Dilithium (Round 3 version).
What's New
In addition to improving CI and testing, fixing platform specific build issues and bugs, and updating build dependencies this release of oqs-provider:
- Adds support for UOV (NIST Additional Signatures Round 2)
- Adds support for Mayo (NIST Additional Signatures Round 2)
- Adds support for CROSS (NIST Additional Signatures Round 2)
- Disables HQC KEM by default, following liboqs v0.13.0, until a security flaw is fixed.
- Disables default support for Kyber (Round 3 version).
- Disables default support for Dilithium (Round 3 version).
- Restricts non-standard TLS group code points to IANA private use range.
- Updates TLS group code point and name for ML-KEM 1024 hybrid SecP384r1MLKEM1024.
- Disables ML-KEM (along with certain hybrid variants) and ML-DSA (along with all composite/hybrid variants) when oqs-provider is loaded with OpenSSL (version >= 3.5.0) which offers native support for some of these algorithms. Please see README.md for detailed information.
What's Changed
- revert to dev by @baentsch in #602
- Bump jinja2 from 3.1.4 to 3.1.5 in /oqs-template in the pip group by @dependabot in #601
- remove default Kyber and Dilithium support by @baentsch in #603
- Allow overriding OPENSSL_MODULES_PATH from the command line by @embetrix in #607
- change code point and name for mlkem1024 hybrid by @baentsch in #606
- Include use of loaded 'libctx' context in KEM and SIG procedures (#557) by @RodriM11 in #614
- limit testing to oqsprovider by @baentsch in #611
- add more complete KEM ENCODERS testing in recent openssl versions by @baentsch in #616
- enable run-time disablement for erroring algs in openssl 3.5 by @baentsch in #642
- Update fullbuild.sh by @dgargar-laude in #633
- Update fullbuild.sh - add OSSL_CONFIG variable for customization. by @tglowka in #640
- restrict libctx test to oqsprovider by @baentsch in #620
- update SIG alg info by @baentsch in #645
- Drop oqsprovider2, appears unused by @vdukhovni in #648
- Integrate UOV by @mkannwischer in #651
- Integrate liboqs upstream updates by @SWilson4 in #657
- Fix windows build in CI by @bhess in #656
- Update OIDs for CROSS 2.0 by @rtjk in #652
- Update OIDs and code points for MAYO round 2 by @bhess in #654
- Update GOVERNANCE.md by @ashman-p in #664
- Prepare for 0.9.0 release by @praveksharma in #670
- Make non-standard TLS code points IANA compliant by @praveksharma in #676
- Finalise #671 by @praveksharma in #678
- Make NID lookup for hybrid KEMs with P and X curves more robust by @Lekensteyn in #671
- Update HQC codepoints following #676 by @praveksharma in #680
New Contributors
- @embetrix made their first contribution in #607
- @RodriM11 made their first contribution in #614
- @dgargar-laude made their first contribution in #633
- @tglowka made their first contribution in #640
- @vdukhovni made their first contribution in #648
- @mkannwischer made their first contribution in #651
- @rtjk made their first contribution in #652
- @Lekensteyn made their first contribution in #671
Full Changelog: 0.8.0...0.9.0
Contributors
Assets 2
0.9.0-rc1
afd1eab
praveksharma
Pravek Sharma
oqs-provider 0.9.0-rc1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is release candidate 1 of version 0.9.0 of oqs-provider which continues from the earlier 0.8.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.13.0 of liboqs.
Deprecation notice
This release of oqsprovider removes default support for Kyber and Dilithium (Round 3 version).
What's New
In addition to improving CI and testing, fixing platform specific build issues and bugs, and updating build dependencies this release of oqs-provider:
- Adds support for UOV (NIST Additional Signatures Round 2)
- Adds support for Mayo (NIST Additional Signatures Round 2)
- Adds support for CROSS (NIST Additional Signatures Round 2)
- Disables HQC KEM by default, following liboqs v0.13.0, until a security flaw is fixed.
- Disables default support for Kyber (Round 3 version).
- Disables default support for Dilithium (Round 3 version).
- Restricts non-standard TLS group code points to IANA private use range.
- Updates TLS group code point and name for ML-KEM 1024 hybrid SecP384r1MLKEM1024.
- Disables ML-KEM (along with certain hybrid variants) and ML-DSA (along with all composite/hybrid variants) when oqs-provider is loaded with OpenSSL (version >= 3.5.0) which offers native support for some of these algorithms. Please see README.md for detailed information.
What's Changed
- revert to dev by @baentsch in #602
- Bump jinja2 from 3.1.4 to 3.1.5 in /oqs-template in the pip group by @dependabot in #601
- remove default Kyber and Dilithium support by @baentsch in #603
- Allow overriding OPENSSL_MODULES_PATH from the command line by @embetrix in #607
- change code point and name for mlkem1024 hybrid by @baentsch in #606
- Include use of loaded 'libctx' context in KEM and SIG procedures (#557) by @RodriM11 in #614
- limit testing to oqsprovider by @baentsch in #611
- add more complete KEM ENCODERS testing in recent openssl versions by @baentsch in #616
- enable run-time disablement for erroring algs in openssl 3.5 by @baentsch in #642
- Update fullbuild.sh by @dgargar-laude in #633
- Update fullbuild.sh - add OSSL_CONFIG variable for customization. by @tglowka in #640
- restrict libctx test to oqsprovider by @baentsch in #620
- update SIG alg info by @baentsch in #645
- Drop oqsprovider2, appears unused by @vdukhovni in #648
- Integrate UOV by @mkannwischer in #651
- Integrate liboqs upstream updates by @SWilson4 in #657
- Fix windows build in CI by @bhess in #656
- Update OIDs for CROSS 2.0 by @rtjk in #652
- Update OIDs and code points for MAYO round 2 by @bhess in #654
- Update GOVERNANCE.md by @ashman-p in #664
- Prepare for 0.9.0 release by @praveksharma in #670
- Make non-standard TLS code points IANA compliant by @praveksharma in #676
- Finalise #671 by @praveksharma in #678
- Make NID lookup for hybrid KEMs with P and X curves more robust by @Lekensteyn in #671
- Update HQC codepoints following #676 by @praveksharma in #680
New Contributors
- @embetrix made their first contribution in #607
- @RodriM11 made their first contribution in #614
- @dgargar-laude made their first contribution in #633
- @tglowka made their first contribution in #640
- @vdukhovni made their first contribution in #648
- @mkannwischer made their first contribution in #651
- @rtjk made their first contribution in #652
- @Lekensteyn made their first contribution in #671
Full Changelog: 0.8.0...0.9.0-rc1
Contributors
Assets 2
0.8.0
oqs-provider 0.8.0
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.8.0 of oqs-provider which continues from the earlier 0.7.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.12.0 of liboqs.
Deprecation notice
This is to notify users of Kyber and Dilithium (Round 3 version) to switch to the ML-KEM (FIPS 203 final version) and ML-DSA (FIPS 204 final version), respectively, as support for both will be removed with the next release of oqsprovider.
Security considerations
- CVE-2024-54137: The associated liboqs v0.12.0 release fixed a bug in HQC decapsulation that leads to incorrect shared secret value during decapsulation when called with an invalid ciphertext. Thank you to Célian Glénaz and Dahmun Goudarzi from Quarkslab for identifying the issue.
What's New
In addition to improving testing, CI, and fixing platform specific build issues this release of oqs-provider:
- Updates IANA code points for ML-KEM and changes FrodoKEM code points.
- Adds support for ML-DSA (FIPS 204 final version).
- Adds support for context strings in OpenSSL versions >= 3.2.
- Updates the implementation of draft-ietf-lamps-pq-composite-sigs from version 01 to version 02.
- Adds a SBOM template in the CycloneDX 1.6 format.
- Adds support for DTLS 1.3 (pending support in OpenSSL).
What's Changed
- Switch to dev mode again by @praveksharma in #535
- Add alexrow to CODEOWNERS by @praveksharma in #537
- Correct 0.7.0 release notes by @praveksharma in #540
- switch doc to release, add backlevel liboqs support by @baentsch in #544
- fix file location error in P12 test by @baentsch in #546
- update MLKEM code points by @baentsch in #559
- Composite sigs update by @feventura in #549
- Remove macos-12 runner due to GitHub deprecation. by @SWilson4 in #563
- update IANA code points for ML-KEM by @baentsch in #577
- Adding version-conditional context string support by @baentsch in #583
- Tracker for FIPS204 / ML-DSA by @bhess in #568
- Add a SBOM template in CycloneDX format by @hughsie in #585
- Changes needed when building with a static libcrypto on Linux by @ashman-p in #584
- Add DTLS 1.3 support by @baentsch in #586
New Contributors
Full Changelog: 0.7.0...0.8.0
Contributors
Assets 2
0.8.0-rc1
oqs-provider 0.8.0 release candidate 1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.8.0-rc1 of oqs-provider which continues from the earlier 0.7.0 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.12.0 of liboqs.
Deprecation notice
This is to notify users of Kyber (Round 3 version) to switch to the ML-KEM (FIPS 203 final version) as support for Kyber will be removed with the next release of liboqs and oqsprovider.
Security considerations
- CVE-2024-54137: The associated liboqs v0.12.0 release fixed a bug in HQC decapsulation that leads to incorrect shared secret value during decapsulation when called with an invalid ciphertext. Thank you to Célian Glénaz and Dahmun Goudarzi from Quarkslab for identifying the issue.
What's New
In addition to improving testing, CI, and fixing platform specific build issues this release of oqs-provider:
- Updates IANA code points for ML-KEM and changes FrodoKEM code points.
- Adds support for ML-DSA (FIPS 204 final version).
- Adds support for context strings in OpenSSL versions >= 3.2.
- Updates the implementation of draft-ietf-lamps-pq-composite-sigs from version 01 to version 02.
- Adds a SBOM template in the CycloneDX 1.6 format.
- Adds support for DTLS 1.3 (pending support in OpenSSL).
What's Changed
- Switch to dev mode again by @praveksharma in #535
- Add alexrow to CODEOWNERS by @praveksharma in #537
- Correct 0.7.0 release notes by @praveksharma in #540
- switch doc to release, add backlevel liboqs support by @baentsch in #544
- fix file location error in P12 test by @baentsch in #546
- update MLKEM code points by @baentsch in #559
- Composite sigs update by @feventura in #549
- Remove macos-12 runner due to GitHub deprecation. by @SWilson4 in #563
- update IANA code points for ML-KEM by @baentsch in #577
- Adding version-conditional context string support by @baentsch in #583
- Tracker for FIPS204 / ML-DSA by @bhess in #568
- Add a SBOM template in CycloneDX format by @hughsie in #585
- Changes needed when building with a static libcrypto on Linux by @ashman-p in #584
- Add DTLS 1.3 support by @baentsch in #586
New Contributors
Full Changelog: 0.7.0...0.8.0-rc1
Contributors
Assets 2
0.7.0
oqs-provider 0.7.0
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.7.0 of oqs-provider which continues from the earlier 0.6.1 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.11.0 of liboqs.
Errata
This release was updated on October 10, 2024 after being first published on October 08, 2024. Prior to being updated the release notes heading incorrectly reported the release version number to be 0.7.1; this error was limited to oqs-provider 0.7.0 release notes and did not affect any oqs-provider functionality.
Security considerations
None.
What's New
In addition to updating documentation, improving the CI, and fixing issues uncovered by compiler warnings and static analysis, this release of oqs-provider:
- Adds support for MAYO from Round 1 of NIST’s Post-Quantum Signature On-Ramp process.
- Adds support for CROSS from Round 1 of NIST’s Post-Quantum Signature On-Ramp process.
- Updates ML-KEM's code points in line with internet draft draft-kwiatkowski-tls-ecdhe-mlkem-02.
- Updates the
fullbuild.shbuild script to build against liboqs with formally verified Kyber-512 and Kyber-768 from libjade turned on by default; seeOQS_LIBJADE_BUILDunderCONFIGURE.mdfor more information. - Reverses keyshares for X25519MLKEM768 and X448-ML-KEM-768 TLS hybrids in line with draft-kwiatkowski-tls-ecdhe-mlkem-02.
What's Changed
- Point CI back to liboqs main by @SWilson4 in #431
- Fix a typo in NOTES-Windows.md by @qnfm in #436
- Fix #439: install the static library under
$PREFIX/lib. by @thb-sb in #441 - Fix #440: disable tests and examples using
BUILD_TESTING. by @thb-sb in #442 - Add MAYO by @bhess in #413
- update the composite to draft-ietf-lamps-pq-composite-sigs-02 by @feventura in #454
- Update codeowners by @baentsch in #458
- Remove external encoding lib by @baentsch in #460
- update coding style and test facilities by @baentsch in #477
- Fix various warnings. by @ashman-p in #480
- A note about key encapsulation/decapsulation support in OpenSSL by @beldmit in #486
- Force liboqs as a debian package dependency requirement only if it is not a static linked library. by @fwh-dc in #493
- openssl and contribution documentation updates [skip ci] by @baentsch in #499
- Adds note on supported openssl versions for tls certificates. by @fwh-dc in #498
- add support for the CMAKE_PARAMS environment variable by @jschauma in #510
- update MLKEM code points by @baentsch in #511
- Actionlint workflow checking by @jplomas in #516
- add explicit usage warning [skip ci] by @baentsch in #515
- Address some Static Analysis Issues #519 by @ashman-p in #521
- Only overwrite default library prefix for module library type build. by @fwh-dc in #525
- Add build option to toggle libjade implementations in liboqs by @praveksharma in #529
- Reverse TLS hybrid keyshares for x25519/x448-mlkem hybrids by @bhess in #524
- Rebase and add CROSS by @praveksharma in #530
- Remove unmanaged KEM OIDs by @baentsch in #522
- Use more future-proof hash for signature by @beldmit in #532
New Contributors
- @ashman-p made their first contribution in #480
- @fwh-dc made their first contribution in #493
- @jschauma made their first contribution in #510
- @jplomas made their first contribution in #516
- @praveksharma made their first contribution in #529
Full Changelog: 0.6.1...0.7.0
Contributors
Assets 2
0.7.0-rc1
oqs-provider 0.7.0 release candidate 1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is release candidate 1 of version 0.7.0 of oqs-provider which continues from the earlier 0.6.1 release. This release is fully tested to be used in conjunction with the main branch of liboqs and is guaranteed to be in sync with v0.11.0 of liboqs.
Errata
This release candidate was updated on October 10, 2024 after being first published on October 07, 2024. Prior to being updated the release notes heading incorrectly reported the release candidate version number to be 0.7.1 release candidate 1; this error was limited to oqs-provider 0.7.0 release candidate 1 release notes and did not affect any oqs-provider functionality.
Security considerations
None.
What's New
In addition to updating documentation, improving the CI, and fixing issues uncovered by compiler warnings and static analysis, this release of oqs-provider:
- Adds support for MAYO from Round 1 of NIST’s Post-Quantum Signature On-Ramp process.
- Adds support for CROSS from Round 1 of NIST’s Post-Quantum Signature On-Ramp process.
- Updates ML-KEM's code points in line with internet draft draft-kwiatkowski-tls-ecdhe-mlkem-02.
- Updates the
fullbuild.shbuild script to build against liboqs with formally verified Kyber-512 and Kyber-768 from libjade turned on by default; seeOQS_LIBJADE_BUILDunderCONFIGURE.mdfor more information. - Reverses keyshares for X25519MLKEM768 and X448-ML-KEM-768 TLS hybrids in line with draft-kwiatkowski-tls-ecdhe-mlkem-02.
What's Changed
- Point CI back to liboqs main by @SWilson4 in #431
- Fix a typo in NOTES-Windows.md by @qnfm in #436
- Fix #439: install the static library under
$PREFIX/lib. by @thb-sb in #441 - Fix #440: disable tests and examples using
BUILD_TESTING. by @thb-sb in #442 - Add MAYO by @bhess in #413
- update the composite to draft-ietf-lamps-pq-composite-sigs-02 by @feventura in #454
- Update codeowners by @baentsch in #458
- Remove external encoding lib by @baentsch in #460
- update coding style and test facilities by @baentsch in #477
- Fix various warnings. by @ashman-p in #480
- A note about key encapsulation/decapsulation support in OpenSSL by @beldmit in #486
- Force liboqs as a debian package dependency requirement only if it is not a static linked library. by @fwh-dc in #493
- openssl and contribution documentation updates [skip ci] by @baentsch in #499
- Adds note on supported openssl versions for tls certificates. by @fwh-dc in #498
- add support for the CMAKE_PARAMS environment variable by @jschauma in #510
- update MLKEM code points by @baentsch in #511
- Actionlint workflow checking by @jplomas in #516
- add explicit usage warning [skip ci] by @baentsch in #515
- Address some Static Analysis Issues #519 by @ashman-p in #521
- Only overwrite default library prefix for module library type build. by @fwh-dc in #525
- Add build option to toggle libjade implementations in liboqs by @praveksharma in #529
- Reverse TLS hybrid keyshares for x25519/x448-mlkem hybrids by @bhess in #524
- Rebase and add CROSS by @praveksharma in #530
- Remove unmanaged KEM OIDs by @baentsch in #522
- Use more future-proof hash for signature by @beldmit in #532
New Contributors
- @ashman-p made their first contribution in #480
- @fwh-dc made their first contribution in #493
- @jschauma made their first contribution in #510
- @jplomas made their first contribution in #516
- @praveksharma made their first contribution in #529
Full Changelog: 0.6.1...0.7.0-rc1
Contributors
Assets 2
0.6.1
oqs-provider 0.6.1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.6.1 of oqs-provider. This version is closely in sync with liboqs v.0.10.1.
Most important updates are fixed references to a security update to liboqs, fixes of potential buffer overrun errors in hybrid key decoding, adding of composite OID setting logic and several documentation updates.
Security considerations
This fixes potential buffer overrun problems in hybrid key decoding. Use of prior versions is strongly discouraged.
What's Changed
- reverting to dev mode [skip ci] by @baentsch in #394
- add caveat regarding OpenSSL installs [skip ci] by @baentsch in #402
- cpack x64 CI fix by @baentsch in #401
- Add PKCS#12 test by @iyanmv in #400
- Fix CI (Add Ubuntu 24 support) by @baentsch in #410
- Bump jinja2 from 3.1.3 to 3.1.4 in /oqs-template by @dependabot in #409
- Extra parentheses removed by @bencemali in #405
- No unwanted error left in queue from OBJ_create by @bencemali in #404
- update security issue reporting [skip ci] by @baentsch in #414
- DECODE_UINT32 without lengths checked fixed by @bencemali in #416
- add composite OIDs to getenv logic by @baentsch in #419
- Switch to https for git access by @baentsch in #423
- STANDARDS.md update by @baentsch in #420
New Contributors
Full Changelog: 0.6.0...0.6.1
Contributors
Assets 2
0.6.1-rc1
oqs-provider 0.6.1
About
The Open Quantum Safe (OQS) project has the goal of developing and prototyping quantum-resistant cryptography. More information on OQS can be found on the website: https://openquantumsafe.org/ and on Github at https://github.com/open-quantum-safe/.
oqs-provider is a standalone OpenSSL 3 provider enabling liboqs-based quantum-safe and hybrid key exchange for TLS 1.3, as well as quantum-safe and hybrid X.509 certificate generation, CMS, CMP and dgst (signature) operations.
When deployed, the oqs-provider binary (shared library) thus adds support for quantum-safe cryptographic operations to any standard OpenSSL(v3) installation. The ultimate goal is that all openssl functionality shall be PQC-enabled.
In general, the oqs-provider main branch is meant to be usable in conjunction with the main branch of liboqs and the master branch of OpenSSL.
Further details on building, testing and use can be found in README.md. See in particular limitations on intended use.
Release notes
This is version 0.6.1 of oqs-provider.
Most important updates are fixed references to a security update to liboqs, fixes of potential buffer overrun errors in hybrid key decoding, adding of composite OID setting logic and several documentation updates.
Security considerations
This fixes potential buffer overrun problems in hybrid key decoding. Use of prior versions is strongly discouraged.
What's Changed
- reverting to dev mode [skip ci] by @baentsch in #394
- add caveat regarding OpenSSL installs [skip ci] by @baentsch in #402
- cpack x64 CI fix by @baentsch in #401
- Add PKCS#12 test by @iyanmv in #400
- Fix CI (Add Ubuntu 24 support) by @baentsch in #410
- Bump jinja2 from 3.1.3 to 3.1.4 in /oqs-template by @dependabot in #409
- Extra parentheses removed by @bencemali in #405
- No unwanted error left in queue from OBJ_create by @bencemali in #404
- update security issue reporting [skip ci] by @baentsch in #414
- DECODE_UINT32 without lengths checked fixed by @bencemali in #416
- add composite OIDs to getenv logic by @baentsch in #419
- Switch to https for git access by @baentsch in #423
- STANDARDS.md update by @baentsch in #420
New Contributors
Full Changelog: 0.6.0...0.6.1-rc1