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

Improve secret independence guarantees in compiled code. #299

Open
xvzcf opened this issue Jun 4, 2024 · 0 comments
Open

Improve secret independence guarantees in compiled code. #299

xvzcf opened this issue Jun 4, 2024 · 0 comments

Comments

@xvzcf
Copy link
Contributor

xvzcf commented Jun 4, 2024

Following up on this: https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU, we should re-examine the way we write secret-independent code and we should also check the resulting binary code to see whether the compiler has optimized away from the constant time code or deviated in any other way from our intentions.

We could mark any function that is intended to produce a mask in constant time as "never inline".

We could also run checks on the resulting binary using https://github.com/rozbb/dudect-bencher. Perhaps we could mimic a TIMECOP like checking approach using Miri and https://doc.rust-lang.org/nomicon/leaking.html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant