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/tls: some broken servers need SHA384 signatures with TLS 1.2 #8190

Closed
agl opened this issue Jun 11, 2014 · 5 comments
Closed

crypto/tls: some broken servers need SHA384 signatures with TLS 1.2 #8190

agl opened this issue Jun 11, 2014 · 5 comments
Milestone

Comments

@agl
Copy link
Contributor

agl commented Jun 11, 2014

https://groups.google.com/forum/#!topic/golang-nuts/oK3EBAY2Uig
@rsc
Copy link
Contributor

rsc commented Sep 15, 2014

Comment 1:

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

@gopherbot
Copy link

Comment 2 by conrad.irwin:

Is this the same bug as described 
http://bridge.grumpy-troll.org/2014/05/golang-tls-comodo/ and
bugsnag/bugsnag-go#9 ?

@agl
Copy link
Contributor Author

agl commented Sep 19, 2014

Comment 3:

This was fixed a while back.

Status changed to Fixed.

@agl agl added fixed labels Sep 19, 2014
@bradfitz bradfitz modified the milestone: Go1.5 Dec 16, 2014
@mikioh
Copy link
Contributor

mikioh commented Feb 3, 2015

@agl,

I just failed to find out the fix of this issue. Can you please point out the hash or change identifier?

@mewmew
Copy link
Contributor

mewmew commented May 29, 2015

For reference, this seems to be the CL which fixed the issue: https://codereview.appspot.com/87670045

@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.
Projects
None yet
Development

No branches or pull requests

6 participants