mleku/secp256k1
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

examples: fix case typos in secret clearing paragraphs (s/, Or/, or/)

Browse Source
This commit is contained in:
Sebastian Falbesoner
2024-06-25 16:52:38 +02:00
parent f473c959f0
commit fe4fbaa7f3
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
examples/ecdh.c
View File

@@ -108,7 +108,7 @@ int main(void) {
/* It's best practice to try to clear secrets from memory after using them. /* It's best practice to try to clear secrets from memory after using them.
* This is done because some bugs can allow an attacker to leak memory, for * This is done because some bugs can allow an attacker to leak memory, for
* example through "out of bounds" array access (see Heartbleed), Or the OS * example through "out of bounds" array access (see Heartbleed), or the OS
* swapping them to disk. Hence, we overwrite the secret key buffer with zeros. * swapping them to disk. Hence, we overwrite the secret key buffer with zeros.
* *
* Here we are preventing these writes from being optimized out, as any good compiler * Here we are preventing these writes from being optimized out, as any good compiler

2
examples/ecdsa.c
View File

@@ -128,7 +128,7 @@ int main(void) {
/* It's best practice to try to clear secrets from memory after using them. /* It's best practice to try to clear secrets from memory after using them.
* This is done because some bugs can allow an attacker to leak memory, for * This is done because some bugs can allow an attacker to leak memory, for
* example through "out of bounds" array access (see Heartbleed), Or the OS * example through "out of bounds" array access (see Heartbleed), or the OS
* swapping them to disk. Hence, we overwrite the secret key buffer with zeros. * swapping them to disk. Hence, we overwrite the secret key buffer with zeros.
* *
* Here we are preventing these writes from being optimized out, as any good compiler * Here we are preventing these writes from being optimized out, as any good compiler

2
examples/schnorr.c
View File

@@ -146,7 +146,7 @@ int main(void) {
/* It's best practice to try to clear secrets from memory after using them. /* It's best practice to try to clear secrets from memory after using them.
* This is done because some bugs can allow an attacker to leak memory, for * This is done because some bugs can allow an attacker to leak memory, for
* example through "out of bounds" array access (see Heartbleed), Or the OS * example through "out of bounds" array access (see Heartbleed), or the OS
* swapping them to disk. Hence, we overwrite the secret key buffer with zeros. * swapping them to disk. Hence, we overwrite the secret key buffer with zeros.
* *
* Here we are preventing these writes from being optimized out, as any good compiler * Here we are preventing these writes from being optimized out, as any good compiler