secp256k1/.gitignore

bench
bench_ecmult
bench_internal
tests
exhaustive_tests
precompute_ecmult_gen
precompute_ecmult
valgrind_ctime_test
ecdh_example
ecdsa_example
schnorr_example
*.exe
*.so
*.a
*.csv
*.log
*.trs
*.sage.py

Makefile
configure
.libs/
Makefile.in
aclocal.m4
autom4te.cache/
config.log
config.status
conftest*
*.tar.gz
*.la
libtool
.deps/
.dirstamp
*.lo
*.o
*~

coverage/
coverage.html
coverage.*.html
*.gcda
*.gcno
*.gcov

build-aux/ar-lib
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
libsecp256k1.pc
Combine bench_sign and bench_verify into single bench 2021-10-17 16:08:06 +00:00			`bench`
Add bench_ecmult to .gitignore 2017-12-31 03:59:17 +00:00			`bench_ecmult`
Add bench_internal to gitignore. 2015-04-22 19:11:19 +00:00			`bench_internal`
Revamp makefile 2013-04-06 22:37:06 +00:00			`tests`
Add exhaustive test for group functions on a low-order subgroup We observe that when changing the b-value in the elliptic curve formula `y^2 = x^3 + ax + b`, the group law is unchanged. Therefore our functions for secp256k1 will be correct if and only if they are correct when applied to the curve defined by `y^2 = x^3 + 4` defined over the same field. This curve has a point P of order 199. This commit adds a test which computes the subgroup generated by P and exhaustively checks that addition of every pair of points gives the correct result. Unfortunately we cannot test const-time scalar multiplication by the same mechanism. The reason is that these ecmult functions both compute a wNAF representation of the scalar, and this representation is tied to the order of the group. Testing with the incomplete version of gej_add_ge (found in 5de4c5dff^) shows that this detects the incompleteness when adding P - 106P, which is exactly what we expected since 106 is a cube root of 1 mod 199. 2015-09-17 23:54:52 +00:00			`exhaustive_tests`
Rename gen_ecmult_gen_static_prec_table -> precompute_ecmult_gen 2021-12-17 16:15:37 +00:00			`precompute_ecmult_gen`
Rename gen_ecmult_static_pre_g -> precompute_ecmult 2021-12-17 16:19:45 +00:00			`precompute_ecmult`
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 2020-01-08 11:56:15 +00:00			`valgrind_ctime_test`
Optionally compile the examples in autotools, compile+run in travis 2020-04-30 11:34:24 +00:00			`ecdh_example`
			`ecdsa_example`
			`schnorr_example`
Better .gitignore for bench binaries 2014-11-01 13:01:40 +00:00			`*.exe`
Revamp makefile 2013-04-06 22:37:06 +00:00			`*.so`
			`*.a`
create csv file from the benchmark output 2021-10-19 00:41:59 +00:00			`*.csv`
Optionally compile the examples in autotools, compile+run in travis 2020-04-30 11:34:24 +00:00			`*.log`
			`*.trs`
gitignore: Add *.sage.py files autogenerated by sage 2022-12-01 11:07:00 +00:00			`*.sage.py`
autotools: autotools'ify libsecp256k1 2014-01-18 03:52:33 +00:00
			`Makefile`
			`configure`
			`.libs/`
			`Makefile.in`
			`aclocal.m4`
			`autom4te.cache/`
			`config.log`
			`config.status`
build: Ensure that configure's compile checks default to -O2 Fixes #896. 2021-05-13 17:34:16 +00:00			`conftest*`
autotools: autotools'ify libsecp256k1 2014-01-18 03:52:33 +00:00			`*.tar.gz`
			`*.la`
			`libtool`
			`.deps/`
			`.dirstamp`
			`*.lo`
			`*.o`
			`*~`
Clean up git tree This removes the ununsed `obj` directory. It also suggests in the README to create the "coverage" files in a separate directory and adds the coverage files to .gitignore. readme: Improve instructions for coverage reports 2021-05-12 09:49:36 +00:00
			`coverage/`
			`coverage.html`
			`coverage.*.html`
			`*.gcda`
			`*.gcno`
			`*.gcov`

configure: Use modern way to set AR This uses AM_PROG_AR to discover ar, which is the recommended way to do so. Among other advantages, it honors the AR environment variable (as set from the outside). The macro has been around since automake 1.11.2 (Dec 2011). This commit also removes code that discovers ranlib and strip. ranlib has been obsolete for decades (ar does its task now automatically), and anyway LT_INIT takes care of discovering it. The code we used to set STRIP was last mentioned in the automake 1.5 manual. Since automake 1.6 (Mar 2002), strip is discovered automatically when necessary (look for the private macro AM_PROG_INSTALL_STRIP in the automake manual). 2022-03-13 09:39:55 +00:00			`build-aux/ar-lib`
Update .gitignore Don't ignore everything under build-aux 2016-02-16 22:59:00 +00:00			`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`
packaging: add pkg-config file to gitignore 2014-05-21 01:04:31 +00:00			`libsecp256k1.pc`