Skip to content
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

Fix Classic McEliece unpoison issue #4605

Merged
merged 2 commits into from
Jan 29, 2025
Merged

Conversation

randombit
Copy link
Owner

Cherry picked from #4562

@reneme feel free to force push this with signed commits

@randombit randombit requested a review from reneme January 28, 2025 13:40
@randombit randombit added this to the Botan 3.7.0 milestone Jan 28, 2025
@coveralls
Copy link

coveralls commented Jan 28, 2025

Coverage Status

coverage: 91.237% (-0.002%) from 91.239%
when pulling 9545c7b on jack/fix-cmce-unpoison
into 1df758d on master.

Copy link
Collaborator

@reneme reneme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Fine with merging under your signature.

For reasons unknown this caused a side-channel warning from valgrind
on aarch64 but not on x86. In any case, this being a sanity-check it
is not a side-channel.
Our hypothesis: valgrind on aarch64 fails to properly handle the bit-level
'uninitialized data' tracking here.

This is a regression test for the issues seen in #4562.
@randombit randombit force-pushed the jack/fix-cmce-unpoison branch from 1cd3a05 to 9545c7b Compare January 29, 2025 12:18
@randombit randombit merged commit 076c839 into master Jan 29, 2025
39 checks passed
@randombit randombit deleted the jack/fix-cmce-unpoison branch January 29, 2025 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants