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: incompatibility with IE6 #3677

gopherbot opened this issue May 29, 2012 · 2 comments

crypto/tls: incompatibility with IE6 #3677

gopherbot opened this issue May 29, 2012 · 2 comments


Copy link

by andrew.p.clausen:

The SSL handshake does not work for Internet Explorer 6.  IE6 uses SSL 3.0, which is
supported by crypto/tls.  The problem seems to be that IE6 sends an empty Session ID in
it's client hello message.  The unmarshal() function for clientHelloMsg in
crypto/tls/handshake_messages.go fails.  (I will continue investigating if I get a

I attached a minimal example HTTPS server in Go, and a shell script to generate the key
& self-signed certificate.


  1. hello.go (307 bytes)
  2. gen-ssl (147 bytes)
Copy link

rsc commented May 29, 2012

Comment 1:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

Copy link

agl commented May 29, 2012

Comment 2:

IE6, by default, will send SSLv2 compat handshakes which Go doesn't support. You can
change this under "Tools", "Internet Options...", "Advanced", (scroll to the bottom),
uncheck "Use SSL 2.0" and check "Use SSL 3.0" and "Use TLS 1.0".
On a wider note: if you're running a secure, production server with Go then terminating
the SSL connections with something else is probably a good idea. The Go TLS stack has
been substantially written by me and hasn't received any of the security review that
something like OpenSSL has. OpenSSL and the like will also use less CPU and include all
the quirks needed to support browsers like IE6.

Status changed to WontFix.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

3 participants