]> Git Repo - secp256k1.git/commit - Makefile.am
Constant-time behaviour test using valgrind memtest.
authorGregory Maxwell <[email protected]>
Wed, 8 Jan 2020 11:56:15 +0000 (11:56 +0000)
committerGregory Maxwell <[email protected]>
Mon, 24 Feb 2020 18:59:30 +0000 (18:59 +0000)
commit3d2302257f19533932cd53547e9745b6283a907d
treefa9bb20ecae74354f55a636e6490519e146dee86
parent96d8ccbd16090551aa003bfa4acd108b0496cb89
Constant-time behaviour test using valgrind memtest.

Valgrind does bit-level tracking of the "uninitialized" status of memory,
 property tracks memory which is tainted by any uninitialized memory, and
 warns if any branch or array access depends on an uninitialized bit.

That is exactly the verification we need on secret data to test for
 constant-time behaviour. All we need to do is tell valgrind our
 secret key is actually uninitialized memory.

This adds a valgrind_ctime_test which is compiled if valgrind is installed:

Run it with libtool --mode=execute:
$ libtool --mode=execute valgrind ./valgrind_ctime_test
.gitignore
Makefile.am
configure.ac
src/valgrind_ctime_test.c [new file with mode: 0644]
This page took 0.022267 seconds and 4 git commands to generate.