Repository navigation
Prepare 0.16.0.2 release - #162
Merged
Merged
Conversation
Maintenance release of liboqs-python 0.16.0 carrying the fix for GHSA-w696-4vrr-x6x3 (ML-DSA signature forgery and ML-KEM shared-secret recovery when an application passes an empty or very short public key). It still pairs with liboqs 0.16.0. - Bump version 0.16.1-dev -> 0.16.0.2 (pyproject.toml); the runtime auto-installer maps this to the liboqs 0.16.0 tag. - CHANGES.md: add the 0.16.0.2 section. - RELEASE.md: rewrite for 0.16.0.2, leading with the security fix and listing the behavior changes from #160 and #161. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Douglas Stebila <dstebila@uwaterloo.ca>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Maintenance release of liboqs-python 0.16.0 carrying the fix for GHSA-w696-4vrr-x6x3 (ML-DSA signature forgery and ML-KEM shared-secret recovery when an application passes an empty or very short public key, fixed in #161). It still pairs with liboqs 0.16.0.
pyproject.toml); the runtime auto-installer maps this to the liboqs 0.16.0 tag.CHANGES.md: add the 0.16.0.2 section (Validate key and ciphertext lengths before passing them to liboqs #161, Fix StatefulSignature.free leaking the native OQS_SIG_STFL struct #160, Bump pypa/gh-action-pypi-publish to v1.14.2 #158).RELEASE.md: rewrite for 0.16.0.2, leading with the security fix and listing the behavior changes that can make existing code raise (wrong-length inputs and emptysecret_keyraiseValueError;StatefulSignaturemethods raiseRuntimeErrorafterfree()).The advisory will be published at the same time as the release.
Testing
Run locally on macOS against liboqs 0.16.0 cloned from the
0.16.0tag and built with the CI flags (shared, STFL LMS/XMSS keygen enabled):examples/kem.py,sig.py,rand.py,stfl_sig.py: all passnose2 --verbose: 1683 tests, OK0.16.0tag (5a1a854), built and installed it, and loaded liboqs 0.16.0After merge
0.16.0.2(publish_pypi.ymlpublishes four-part tags to PyPI).RELEASE.md.0.16.1-dev.🤖 Generated with Claude Code