Skip to content
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

crypto/x509: add more detail to the error message arising from a missing hash function. #7735

agl opened this issue Apr 9, 2014 · 5 comments


Copy link

@agl agl commented Apr 9, 2014

If a certificate is signed with a hash function that wasn't compiled in the error
message isn't bad, but could be better:

x509: certificate signed by unknown authority (possibly because of "x509: cannot
verify signature: algorithm unimplemented" while trying to verify candidate
authority certificate "CA Cert Signing Authority")
Copy link

@rsc rsc commented Sep 15, 2014

Comment 1:

Labels changed: added release-go1.5, removed release-go1.4.

Copy link

@bradfitz bradfitz commented Mar 21, 2017

(More details in closed dup #5301)

Copy link

@odeke-em odeke-em commented Mar 22, 2017

@agl would the direct error message

x509: cannot verify signature: algorithm unimplemented

suffice? Catch it right after it has occured.
I took a break from studying Chemistry to get something in, I'll now need to compile a test when free, then submit a CL, probably on the weekend, if this is cool with you.

Copy link
Contributor Author

@agl agl commented Mar 24, 2017

I don't believe that the problem is that the error message is too long, but that it doesn't hint at a solution. I.e. perhaps it could hint that it might be a hash function that's not compiled in.

Copy link

@gopherbot gopherbot commented Apr 29, 2017

CL mentions this issue.

@bradfitz bradfitz modified the milestones: Go1.10, Go1.9Maybe Jul 20, 2017
@rsc rsc modified the milestones: Go1.10, Go1.11 Nov 22, 2017
@ianlancetaylor ianlancetaylor modified the milestones: Go1.11, Go1.12 Jun 29, 2018
@andybons andybons modified the milestones: Go1.12, Go1.13 Feb 12, 2019
@andybons andybons removed this from the Go1.13 milestone Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants