forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-07-22 20:56:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

crypto, clef: fix various spelling errors

Browse source 
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
This commit is contained in:
bit2swaz 2026-01-01 06:26:23 +05:30
parent b635e0632c
commit 45832c9347
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
cmd/clef/rules.md
View file

@ -81,7 +81,7 @@ Additionally, a few more have been added
Some security precautions can be made, such as: 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. * 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. * 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 <creds>` * If the user wishes to modify the ruleset, he'd then have to perform e.g. `signer --attest /path/to/ruleset --credential <creds>`

4
crypto/secp256k1/libsecp256k1/src/tests.c
View file

@ -3889,7 +3889,7 @@ static void test_ge(void) {
free(gej); free(gej);
} }
static void test_intialized_inf(void) { static void test_initialized_inf(void) {
secp256k1_ge p; secp256k1_ge p;
secp256k1_gej pj, npj, infj1, infj2, infj3; secp256k1_gej pj, npj, infj1, infj2, infj3;
secp256k1_fe zinv; secp256k1_fe zinv;
@ -4015,7 +4015,7 @@ static void run_ge(void) {
test_ge(); test_ge();
} }
test_add_neg_y_diff_x(); test_add_neg_y_diff_x();
test_intialized_inf(); test_initialized_inf();
test_ge_bytes(); test_ge_bytes();
} }

2
crypto/secp256k1/libsecp256k1/src/wycheproof/ecdsa_secp256k1_sha256_bitcoin_test.json
View file

@ -10,7 +10,7 @@
"notes" : { "notes" : {
"ArithmeticError" : { "ArithmeticError" : {
"bugType" : "EDGE_CASE", "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" : [ "cves" : [
"CVE-2017-18146" "CVE-2017-18146"
] ]