-
Notifications
You must be signed in to change notification settings - Fork 18k
crypto/ecdsa: Sign() panics if public key is not set #70468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This used to always work. Presumably broken due to 9776d02 or any of the related commits. |
CC @golang/security |
The joys of malleable key types. I am tempted to argue that such a key is corrupted, you can't just nil fields of a type arbitrarily, and worked by chance, but I guess we should avoid breakage if we can. |
This was caused by https://go.dev/cl/628677. |
@FiloSottile What is the status of this issue? Should this be fixed for 1.25? Thanks. |
This fell off the radar. My mistake. However now that it shipped, I wonder if we should just let it be: we'd have fixed it to avoid potentially breaking applications that are upgrading to Go 1.24, not because this is documented to work anywhere. It doesn't look like anyone else ended up hitting it, though? |
Go version
go version devel go1.24-7c7170e Wed Nov 20 18:27:31 2024 +0000 linux/amd64
Output of
go env
in your module/workspace:What did you do?
What did you see happen?
What did you expect to see?
No panic and output like:
The text was updated successfully, but these errors were encountered: