-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
pull kyber from upstream: dda29cc63af721981ee2c831cf00822e69be3220 (#1631) #1633
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the Travis build is failing due since #1629 is not merged into either branch. We know that Travis passes on the current main
branch, which includes this patch, so I don't think it's necessary for those tests to be green on this branch.
Thanks Spencer. I've cherry-picked that commit over to this branch as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. But why doesn't this target "main"?
These have already been merged to main. The point here is to do a quick 0.9.1 security release that takes the 0.9.0 release and just ports back the Kyber security fix (plus one extra commit that makes things build cleanly on Travis). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the same issue still exists in the aarch64 code that we pull from PQClean:
https://github.com/open-quantum-safe/liboqs/blob/8449e546491e77b52ca5b2f1451086ef564e16aa/src/kem/kyber/oldpqclean_kyber1024_aarch64/poly.c#L217C1-L217C1
If you agree, I'll create two PRs with a patch: one targeting main, and one targeting the 0.9.1 branch.
That would be great, thanks Basil. |
Applies fix from #1631 to dev branch for 0.9.1 release.