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

Try haybale-pitchfork to detect constant time violations #4

Open
LLFourn opened this issue Jun 1, 2020 · 0 comments
Open

Try haybale-pitchfork to detect constant time violations #4

LLFourn opened this issue Jun 1, 2020 · 0 comments

Comments

@LLFourn
Copy link
Owner

LLFourn commented Jun 1, 2020

See: rust-bitcoin/rust-secp256k1#213

Obviously all the functions in https://github.com/LLFourn/secp256kfun/blob/master/secp256kfun/src/backend/parity/constant_time.rs should be constant time and we should be able to empirically verify they are and do the tests in CI. There are several obvious violations here but as we fix them they should be tested.

Thanks to @thomaseizinger for putting me onto this.

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

No branches or pull requests

1 participant