Clear sensitive memory without getting optimized out (revival of #636)#1579

Merged

real-or-random merged 9 commits intobitcoin-core:masterfrom

theStack:revival_of_pr636_cleanse

Nov 4, 2024

Commits on Oct 22, 2024

Don't clear secrets in pippenger implementation

real-or-random
authored and
theStack
committed

Commits on Oct 25, 2024

Add secp256k1_memclear() for clearing secret data

real-or-random
authored and
theStack
committed
Separate secp256k1_fe_set_int( . , 0 ) from secp256k1_fe_clear()

authored and
theStack
committed
Separate between clearing memory and setting to zero in tests

authored and
theStack
committed
Use secp256k1_memclear() to clear stack memory instead of memset()

authored and
theStack
committed
Implement various _clear() functions with secp256k1_memclear()

real-or-random
authored and
theStack
committed
Don't rely on memset to set signed integers to 0

real-or-random
authored and
theStack
committed
Introduce separate _clear functions for hash module

real-or-random
authored and
theStack
committed
Clear _gej instances after point multiplication to avoid potential leaks
theStack
committed