Repository navigation
Initial cargo checkct harness/driver - #732
Merged
Merged
Conversation
tarcieri
force-pushed
the
cargo-checkct
branch
3 times, most recently
from
October 23, 2026 13:26
10230af to
58fbd1f
Compare
Adds some initial testing of operations intended to be constant-time using `cargo checkct`, a wrapper for BINSEC that is able to static analysis looking for constant-time issues. Namely this checks that `i2osp_zeroizing` avoids secret-dependent control flow and memory accesses for small fixed-width encoding, padding, and truncation cases. We currently check RISCV32, Thumb-2, and x86-64, since these are what are supported by `cargo checkct`. Unlike other places we've deployed this, we can't test Thumb-1 due to use of `Arc`. These tests have been configured to run in CI to detect regressions.
tarcieri
force-pushed
the
cargo-checkct
branch
from
October 23, 2026 13:30
58fbd1f to
65ca275
Compare
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
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.
Adds some initial testing of operations intended to be constant-time using
cargo checkct, a wrapper for BINSEC that is able to static analysis looking for constant-time issues.Namely this checks that
i2osp_zeroizingavoids secret-dependent control flow and memory accesses for small fixed-width encoding, padding, and truncation cases.We currently check RISCV32, Thumb-2, and x86-64, since these are what are supported by
cargo checkct. Unlike other places we've deployed this, we can't test Thumb-1 due to use ofArc.These tests have been configured to run in CI to detect regressions.
See also:
borrowing_subconstant-timeness; usecargo checkctcrypto-bigint#1358div_rem,nlimbs, and Montgomery mul crypto-bigint#1360