ci: detect compiler-induced side-channel leakage #16
Conversation
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
tob-scott-a
changed the title
tob-scott-a
changed the title
tob-scott-a
added
component:CI/CD 🤖
Collaborator
Author
|
When testing locally, remember the context of a function. This will find variable-time behavior, but UseHint is only used in signature verification, which contains only public inputs. Instead, focus on the functions that matter: |
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.
(Code generated by Claude Code, as part of Maker Week.)
Limitations
This only inspects the output of the Go compiler. It doesn't verify what the processor actually does with the binaries. This tool is not a replacement for the Valgrind trick.