![]() ![]() Older versions of Valgrind did not expose the necessary interface so a patch was needed, however, no patches are needed for current versions of Valgrind. Testing constant-timeness using Valgrind #Īs far as I know, the original idea of using Valgrind’s MemCheck for testing constant-timeness goes to Adam Langley’s ctgrind, introduced in a blog post and on github, back in 2010. In this post I looked at using Valgrind’s memcheck tool to test constant-timeness of primitives in the NSS cryptographic library. There are a few ways of testing or verifying that code is constant-time, for example using the tools I described in a previous post. ![]() No secret-dependent values given to some variable time functions.No memory access based on secret-dependent values.No branching on secret-dependent values.Being constant-time is usually defined as: Cryptographic code needs to be constant-time to not leak secrets via timing.
0 Comments
Leave a Reply. |