We’ve just started using BINSEC for RustCrypto, by way of cargo-checkct.
https://binsec.github.io/
It’s static analysis tooling that lets you write a test harness that answers the question “does the code under test ever perform non-constant-time CPU instructions on secret inputs?” and it works across a variety of different CPU architectures.
In a world of optimizing compilers that don’t give assurances, at least this way we can have tests (and they run in CI to prevent regressions!)
#rust #cryptography
Tony “Abolish ICE” Arcieri🌹🦀
npub1es…2z8gv
2026-10-23 17:23:48 UTC
Author Public Key
npub1ese6na4ymxez6faql2zmqwp5f6vt5rc0zkhd54ykxwezk7ucry9sq2z8gvSeen on
wss://relay.ditto.pubPublished at
2026-10-23 17:23:48 UTCEvent JSON
{
"id": "53b0de5a993fb31f1db0e94b6f80f1925b2c7960f06fbe0393183fd153e39ec5",
"pubkey": "cc33a9f6a4d9b22d27a0fa85b038344e98ba0f0f15aeda549633b22b7b98190b",
"created_at": 1792776228,
"kind": 1,
"tags": [
[
"t",
"cryptography"
],
[
"t",
"Rust"
],
[
"proxy",
"https://mas.to/users/bascule/statuses/117491382880172666",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "We’ve just started using BINSEC for RustCrypto, by way of cargo-checkct.\n\nhttps://binsec.github.io/\n\nIt’s static analysis tooling that lets you write a test harness that answers the question “does the code under test ever perform non-constant-time CPU instructions on secret inputs?” and it works across a variety of different CPU architectures.\n\nIn a world of optimizing compilers that don’t give assurances, at least this way we can have tests (and they run in CI to prevent regressions!)\n\n#rust #cryptography",
"sig": "4cb9a99b396248a5329064af5f1f4aa806354a70b82b37304269ae806888650ca490a6411feccb7bc1586119e3a64238f722fb80c256a6d481c5633c9d9ead56"
}