From 45832c9347251df24efdd8ea98a9202c6d0ebd36 Mon Sep 17 00:00:00 2001 From: bit2swaz Date: Thu, 1 Jan 2026 06:26:23 +0530 Subject: [PATCH] crypto, clef: fix various spelling errors This change fixes three specific typos: - crypto: fix 'occurences' in wycheproof JSON vectors - crypto: rename 'test_intialized_inf' to 'test_initialized_inf' in tests.c - clef: fix 'writeable' to 'writable' in rules.md --- cmd/clef/rules.md | 2 +- crypto/secp256k1/libsecp256k1/src/tests.c | 4 ++-- .../src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/cmd/clef/rules.md b/cmd/clef/rules.md index ef89ec00c8..6473754eac 100644 --- a/cmd/clef/rules.md +++ b/cmd/clef/rules.md @@ -81,7 +81,7 @@ Additionally, a few more have been added Some security precautions can be made, such as: -* Never load `ruleset.js` unless the file is `readonly` (`r-??-??-?`). If the user wishes to modify the ruleset, he must make it writeable and then set back to readonly. +* Never load `ruleset.js` unless the file is `readonly` (`r-??-??-?`). If the user wishes to modify the ruleset, he must make it writable and then set back to readonly. * This is to prevent attacks where files are dropped on the users disk. * Since we're going to have to have some form of secure storage (not defined in this section), we could also store the `sha3` of the `ruleset.js` file in there. * If the user wishes to modify the ruleset, he'd then have to perform e.g. `signer --attest /path/to/ruleset --credential ` diff --git a/crypto/secp256k1/libsecp256k1/src/tests.c b/crypto/secp256k1/libsecp256k1/src/tests.c index 88628a14ea..10071f7eda 100644 --- a/crypto/secp256k1/libsecp256k1/src/tests.c +++ b/crypto/secp256k1/libsecp256k1/src/tests.c @@ -3889,7 +3889,7 @@ static void test_ge(void) { free(gej); } -static void test_intialized_inf(void) { +static void test_initialized_inf(void) { secp256k1_ge p; secp256k1_gej pj, npj, infj1, infj2, infj3; secp256k1_fe zinv; @@ -4015,7 +4015,7 @@ static void run_ge(void) { test_ge(); } test_add_neg_y_diff_x(); - test_intialized_inf(); + test_initialized_inf(); test_ge_bytes(); } diff --git a/crypto/secp256k1/libsecp256k1/src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json b/crypto/secp256k1/libsecp256k1/src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json index 9c90747993..7e8fd1a46e 100644 --- a/crypto/secp256k1/libsecp256k1/src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json +++ b/crypto/secp256k1/libsecp256k1/src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json @@ -10,7 +10,7 @@ "notes" : { "ArithmeticError" : { "bugType" : "EDGE_CASE", - "description" : "Some implementations of ECDSA have arithmetic errors that occur when intermediate results have extreme values. This test vector has been constructed to test such occurences.", + "description" : "Some implementations of ECDSA have arithmetic errors that occur when intermediate results have extreme values. This test vector has been constructed to test such occurrences.", "cves" : [ "CVE-2017-18146" ]