go-ethereum

Commit Graph

Author	SHA1	Message	Date
Felix Lange	9244d5cd61	all: update license headers and AUTHORS from git history (#24947 )	3 years ago
Marius van der Wijden	0703ef62d3	crypto/secp256k1: fix undefined behavior in BitCurve.Add (#22621 ) This commit changes the behavior of BitCurve.Add to be more inline with btcd. It fixes two different bugs: 1) When adding a point at infinity to another point, the other point should be returned. While this is undefined behavior, it is better to be more inline with the go standard library. Thus (0,0) + (a, b) = (a,b) 2) Adding the same point to itself produced the point at infinity. This is incorrect, now doubleJacobian is used to correctly calculate it. Thus (a,b) + (a,b) == 2* (a,b) and not (0,0) anymore. The change also adds a differential fuzzer for Add, testing it against btcd. Co-authored-by: Felix Lange <fjl@twurst.com>	4 years ago

Author

SHA1

Message

Date

Felix Lange

9244d5cd61

all: update license headers and AUTHORS from git history (#24947 )

3 years ago

Marius van der Wijden

0703ef62d3

crypto/secp256k1: fix undefined behavior in BitCurve.Add (#22621 )

This commit changes the behavior of BitCurve.Add to be more inline
with btcd. It fixes two different bugs:

1) When adding a point at infinity to another point, the other point
   should be returned. While this is undefined behavior, it is better
   to be more inline with the go standard library.
   Thus (0,0) + (a, b) = (a,b)

2) Adding the same point to itself produced the point at infinity.
   This is incorrect, now doubleJacobian is used to correctly calculate it.
   Thus (a,b) + (a,b) == 2* (a,b) and not (0,0) anymore.

The change also adds a differential fuzzer for Add, testing it against btcd.

Co-authored-by: Felix Lange <fjl@twurst.com>

4 years ago

2 Commits (b46d37ea521ebca31e795b274461490c549b7309)