mirror of
https://github.com/status-im/secp256k1.git
synced 2025-02-23 03:08:10 +00:00
3d2302257f
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
52 lines
733 B
Plaintext
52 lines
733 B
Plaintext
bench_inv
|
|
bench_ecdh
|
|
bench_ecmult
|
|
bench_sign
|
|
bench_verify
|
|
bench_schnorr_verify
|
|
bench_recover
|
|
bench_internal
|
|
tests
|
|
exhaustive_tests
|
|
gen_context
|
|
valgrind_ctime_test
|
|
*.exe
|
|
*.so
|
|
*.a
|
|
!.gitignore
|
|
|
|
Makefile
|
|
configure
|
|
.libs/
|
|
Makefile.in
|
|
aclocal.m4
|
|
autom4te.cache/
|
|
config.log
|
|
config.status
|
|
*.tar.gz
|
|
*.la
|
|
libtool
|
|
.deps/
|
|
.dirstamp
|
|
*.lo
|
|
*.o
|
|
*~
|
|
src/libsecp256k1-config.h
|
|
src/libsecp256k1-config.h.in
|
|
src/ecmult_static_context.h
|
|
build-aux/config.guess
|
|
build-aux/config.sub
|
|
build-aux/depcomp
|
|
build-aux/install-sh
|
|
build-aux/ltmain.sh
|
|
build-aux/m4/libtool.m4
|
|
build-aux/m4/lt~obsolete.m4
|
|
build-aux/m4/ltoptions.m4
|
|
build-aux/m4/ltsugar.m4
|
|
build-aux/m4/ltversion.m4
|
|
build-aux/missing
|
|
build-aux/compile
|
|
build-aux/test-driver
|
|
src/stamp-h1
|
|
libsecp256k1.pc
|