-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🤖 Audit: Auto-update with latest upstream patches #221
Conversation
See: randombit/botan#3887 This is a fairly minimal adaption, once the full refactoring is merged, we'll have to rewrite this more substantially. That won't happen before Botan 3.5.0, though. See also: randombit/botan#4024
a2331d3
to
367a052
Compare
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.
I reviewed the audit and the Kyber cryptodoc updates. Both look good to me 👍
The only remark I have is not related to this specific PR.
The TODO above the Kyber cryptodoc:
.. todo::
This documentation is outdated (and potentially too detailed).
It should be updated as soon as those pull requests are merged:
* https://github.com/randombit/botan/pull/4024
Until then, I've removed some of the source links to pass CI.
Is there a switch to prevent todo renderings in the release version? Otherwise, we could rephrase it to make it less technical.
Anyway, I think we should merge this PR soon, so that the bot does not push any more patches :)
(I did not look into the CI failures, though)
Let's merge and clean up tomorrow. Thanks for the review! |
This pull request was created automatically and contains the latest uncategorized patches from Botan's repository.
Typically, you will need to pull this branch (
audit/autoupdate
) to categorize and audit the newly added patches. It is perfectly fine to push into this pull request and merge it after a code review.If not merged, this pull request will be updated with new patches continuously.