status-im/secp256k1
2
0
Fork 0
mirror of https://github.com/status-im/secp256k1.git synced 2025-02-23 03:08:10 +00:00
Code Issues Projects Releases Wiki Activity

tests: Switch to NONE contexts in exhaustive and ctime tests

Browse Source
This commit is contained in:
Jonas Nick 2022-11-28 16:21:18 +00:00
parent 8d7a9a8eda
commit 37ba744f5b
No known key found for this signature in database
GPG Key ID: 4861DBF262123605
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/tests_exhaustive.c
View File

@ -396,7 +396,7 @@ int main(int argc, char** argv) {
while (count--) { while (count--) {
/* Build context */ /* Build context */
ctx = secp256k1_context_create(SECP256K1_CONTEXT_SIGN | SECP256K1_CONTEXT_VERIFY); ctx = secp256k1_context_create(SECP256K1_CONTEXT_NONE);
secp256k1_testrand256(rand32); secp256k1_testrand256(rand32);
CHECK(secp256k1_context_randomize(ctx, rand32)); CHECK(secp256k1_context_randomize(ctx, rand32));

4
src/valgrind_ctime_test.c
View File

@ -39,9 +39,7 @@ int main(void) {
fprintf(stderr, "Usage: libtool --mode=execute valgrind ./valgrind_ctime_test\n"); fprintf(stderr, "Usage: libtool --mode=execute valgrind ./valgrind_ctime_test\n");
return 1; return 1;
} }
ctx = secp256k1_context_create(SECP256K1_CONTEXT_SIGN ctx = secp256k1_context_create(SECP256K1_CONTEXT_DECLASSIFY);
| SECP256K1_CONTEXT_VERIFY
| SECP256K1_CONTEXT_DECLASSIFY);
/** In theory, testing with a single secret input should be sufficient: /** In theory, testing with a single secret input should be sufficient:
* If control flow depended on secrets the tool would generate an error. * If control flow depended on secrets the tool would generate an error.
*/ */