-
Notifications
You must be signed in to change notification settings - Fork 78
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
update to liboqs 0.9.1 #266
Conversation
This is fascinating
Does the fuzzer crash reproduce when you run locally? |
Oh by the way, it is possible that the updated OQS actually has new versions of McEliece & Kyber, in which case this crash would make sense |
How so? |
In other words, does this mean with a bump all deployed setups would break? |
Well, occasionally OQS just updates their implementations
I would say: All deployed setups should update. Anway. Lets fix and merge this but please add info to the commit indicating whether the algorithm versions where changed. |
The release updated the Classic McEliece implemented and since we use it, might be a good idea to update the lib. Signed-off-by: Paul Spooren <mail@aparcar.org>
Looking into the cargo fuzz failure, will add any findings here |
Great thanks |
The secret key size and the cipher text length have changed in the McEliece KEM we are using. So the slice size turns out to be smaller when copying the slice into Secret for the handle_msg.rs test I've added some updates to use constants instead of manually specifying slice sizes in these tests for KEMs on this branch: https://github.com/prabhpreet/rosenpass/tree/liboqs-910 @aparcar I don't have permissions to write to your branch. Can you add the changes from the branch and see if the pipeline passes? |
Superseded by #292 |
The release updated the Classic McEliece implemented and since we use it, might be a good idea to update the lib.