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: No expected chain matched #7824

peterGo opened this issue Apr 20, 2014 · 3 comments

crypto/x509: No expected chain matched #7824

peterGo opened this issue Apr 20, 2014 · 3 comments


Copy link

@peterGo peterGo commented Apr 20, 2014

Windows 7 with all updates applied.

C:\go\src>go version
go version devel +70af843fed44 Sat Apr 19 09:55:09 2014 +0200 windows/amd64

C:\go\src\pkg\crypto\x509>go test
--- FAIL: TestSystemVerify (0.03 seconds)
        verify_test.go:382: #15: No expected chain matched BR/Moip Pagamentos S.A./MOIP,SSL Blindado
 EV/ -> GB/COMODO CA Limited//COMODO RSA Extended Validation Secure Server CA -> GB/C
OMODO CA Limited//COMODO RSA Certification Authority
exit status 1
FAIL    crypto/x509     1.117s
Copy link

@ianlancetaylor ianlancetaylor commented May 9, 2014

Comment 1:

Labels changed: added repo-main, release-go1.4.

Copy link

@gopherbot gopherbot commented Jun 12, 2014

Comment 2 by

After reverting all tests are
passing on the aforementioned platform (Windows 7 with all updates applied).
Copy link

@rsc rsc commented Sep 15, 2014

Comment 3:

If you update your Windows system I bet this will start working. It's just a mismatch
between the trusted certs on the Windows machine and the trusted certs the test expects
on the Windows machine. Not a big deal either way.

Status changed to WorkingAsIntended.

@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.