mirror of
https://github.com/golang/go
synced 2024-11-18 09:24:54 -07:00
crypto/elliptic: call IsOnCurve via the interface.
https://go-review.googlesource.com/#/c/2421/ contains an unfortunate slip where IsOnCurve is called on the CurveParams rather than the curve. This doesn't really matter, but it's a pain for people doing tricks with crypto/elliptic and means that 1.5 would be a regression for them without this change. See https://groups.google.com/forum/#!topic/golang-dev/i8OPUTYctOk Change-Id: Ifa5f25f9a95d7484cb53d4883cfd78dc58a0f9a7 Reviewed-on: https://go-review.googlesource.com/12506 Reviewed-by: Russ Cox <rsc@golang.org>
This commit is contained in:
parent
a502fb2182
commit
bad52b352a
@ -320,7 +320,7 @@ func Unmarshal(curve Curve, data []byte) (x, y *big.Int) {
|
||||
}
|
||||
x = new(big.Int).SetBytes(data[1 : 1+byteLen])
|
||||
y = new(big.Int).SetBytes(data[1+byteLen:])
|
||||
if !curve.Params().IsOnCurve(x, y) {
|
||||
if !curve.IsOnCurve(x, y) {
|
||||
x, y = nil, nil
|
||||
}
|
||||
return
|
||||
|
Loading…
Reference in New Issue
Block a user