Fix some misspellings
Some files contained English misspellings or math issues (`lamba` instead of `lambda`).
This commit is contained in:
@@ -55,7 +55,7 @@ option(SECP256K1_INSTALL "Enable installation." ${PROJECT_IS_TOP_LEVEL})
|
|||||||
## Modules
|
## Modules
|
||||||
|
|
||||||
# We declare all options before processing them, to make sure we can express
|
# We declare all options before processing them, to make sure we can express
|
||||||
# dependendencies while processing.
|
# dependencies while processing.
|
||||||
option(SECP256K1_ENABLE_MODULE_ECDH "Enable ECDH module." ON)
|
option(SECP256K1_ENABLE_MODULE_ECDH "Enable ECDH module." ON)
|
||||||
option(SECP256K1_ENABLE_MODULE_RECOVERY "Enable ECDSA pubkey recovery module." OFF)
|
option(SECP256K1_ENABLE_MODULE_RECOVERY "Enable ECDSA pubkey recovery module." OFF)
|
||||||
option(SECP256K1_ENABLE_MODULE_EXTRAKEYS "Enable extrakeys module." ON)
|
option(SECP256K1_ENABLE_MODULE_EXTRAKEYS "Enable extrakeys module." ON)
|
||||||
|
|||||||
@@ -254,8 +254,8 @@ fi
|
|||||||
print_msan_notice=no
|
print_msan_notice=no
|
||||||
if test x"$enable_ctime_tests" = x"yes"; then
|
if test x"$enable_ctime_tests" = x"yes"; then
|
||||||
SECP_MSAN_CHECK
|
SECP_MSAN_CHECK
|
||||||
# MSan on Clang >=16 reports unitialized memory in function parameters and return values, even if
|
# MSan on Clang >=16 reports uninitialized memory in function parameters and return values, even if
|
||||||
# the uninitalized variable is never actually "used". This is called "eager" checking, and it's
|
# the uninitialized variable is never actually "used". This is called "eager" checking, and it's
|
||||||
# sounds like good idea for normal use of MSan. However, it yields many false positives in the
|
# sounds like good idea for normal use of MSan. However, it yields many false positives in the
|
||||||
# ctime_tests because many return values depend on secret (i.e., "uninitialized") values, and
|
# ctime_tests because many return values depend on secret (i.e., "uninitialized") values, and
|
||||||
# we're only interested in detecting branches (which count as "uses") on secret data.
|
# we're only interested in detecting branches (which count as "uses") on secret data.
|
||||||
|
|||||||
@@ -90,11 +90,11 @@ static void secp256k1_scalar_split_lambda_verify(const secp256k1_scalar *r1, con
|
|||||||
#endif
|
#endif
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Both lambda and beta are primitive cube roots of unity. That is lamba^3 == 1 mod n and
|
* Both lambda and beta are primitive cube roots of unity. That is lambda^3 == 1 mod n and
|
||||||
* beta^3 == 1 mod p, where n is the curve order and p is the field order.
|
* beta^3 == 1 mod p, where n is the curve order and p is the field order.
|
||||||
*
|
*
|
||||||
* Furthermore, because (X^3 - 1) = (X - 1)(X^2 + X + 1), the primitive cube roots of unity are
|
* Furthermore, because (X^3 - 1) = (X - 1)(X^2 + X + 1), the primitive cube roots of unity are
|
||||||
* roots of X^2 + X + 1. Therefore lambda^2 + lamba == -1 mod n and beta^2 + beta == -1 mod p.
|
* roots of X^2 + X + 1. Therefore lambda^2 + lambda == -1 mod n and beta^2 + beta == -1 mod p.
|
||||||
* (The other primitive cube roots of unity are lambda^2 and beta^2 respectively.)
|
* (The other primitive cube roots of unity are lambda^2 and beta^2 respectively.)
|
||||||
*
|
*
|
||||||
* Let l = -1/2 + i*sqrt(3)/2, the complex root of X^2 + X + 1. We can define a ring
|
* Let l = -1/2 + i*sqrt(3)/2, the complex root of X^2 + X + 1. We can define a ring
|
||||||
|
|||||||
@@ -232,7 +232,7 @@ static SECP256K1_INLINE void secp256k1_memclear(void *ptr, size_t len) {
|
|||||||
* As best as we can tell, this is sufficient to break any optimisations that
|
* As best as we can tell, this is sufficient to break any optimisations that
|
||||||
* might try to eliminate "superfluous" memsets.
|
* might try to eliminate "superfluous" memsets.
|
||||||
* This method is used in memzero_explicit() the Linux kernel, too. Its advantage is that it
|
* This method is used in memzero_explicit() the Linux kernel, too. Its advantage is that it
|
||||||
* is pretty efficient, because the compiler can still implement the memset() efficently,
|
* is pretty efficient, because the compiler can still implement the memset() efficiently,
|
||||||
* just not remove it entirely. See "Dead Store Elimination (Still) Considered Harmful" by
|
* just not remove it entirely. See "Dead Store Elimination (Still) Considered Harmful" by
|
||||||
* Yang et al. (USENIX Security 2017) for more background.
|
* Yang et al. (USENIX Security 2017) for more background.
|
||||||
*/
|
*/
|
||||||
|
|||||||
Reference in New Issue
Block a user