vickkkkkyy 8581125a21 crypto: add hash length check in nocgo VerifySignature (#33839) ... I was tracing a signature verification issue in a nocgo build and found that `VerifySignature` doesn't validate hash length. #33104 added the check to `Sign` and `sigToPub` but missed this one. The cgo path in `secp256k1/secp256.go` already rejects non-32-byte hashes, so the nocgo path should do the same — otherwise a wrong-length hash gets passed to decred's `Verify` and silently gives a bogus result.		2026-05-10 11:49:17 +02:00
..
blake2b
bn256
ecies
keccak
kzg4844
secp256k1
secp256r1
signify
crypto.go
crypto_test.go
keccak.go
keccak_ziren.go
signature_cgo.go
signature_nocgo.go	crypto: add hash length check in nocgo VerifySignature (#33839)	2026-05-10 11:49:17 +02:00
signature_test.go