-
Notifications
You must be signed in to change notification settings - Fork 228
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
Implement CertCompressionAlgo extension #48
Comments
the same issue persist in Ubuntu-18.04 amd64 using go version 1.8 |
Could be a server issue. Did you take a look at which |
This is what I got in wireshark |
When I visit https://104.27.159.141 in Chrome 83 I get this:
Looks like that server needs to update TLS config and/or implementation. |
I got the same exact problem when running on google.com or even facebook as in the example as well, so I believe it's not a server side issue. Also for the problem you mentioned, it's due to the IP owned by cloudflare. You need to enter the hostname so it can resolve it and look if the domain is set with their SSL or not. |
I can confirm this issue with HelloChrome_83 and cloudflare.com:443. I believe this is due to this extension not being implemented: Lines 280 to 282 in ada0bb9
When you comment this extension out, the TLS handshake succeeds. Of course, that's no longer Chrome 83. Fwiw, a fix exists: #22. We cannot merge that here due to license issues. Perhaps we can develop our own implementation of certificate compression, or check for another one. |
Perhaps we can. Or perhaps @Yawning can agree to dual license his uTLS changes so we can pull them here. I am pretty busy right now, since I have a thesis defense next month, so I would really appreciate help with the library. |
I'll need to think about this. |
I've resolved some of the issues that I received. It turns out that for some websites (example: www.something.com) I need to put something.com as the ServerName in tls.Config and dial the www.something.com. Putting the www. subdomain in tls.Config will result in handshake error |
Confirmed, @Yawning works, UTLS fails with anything using |
I have meet the same problem like you. Do you have any solution? Any help to me will be appreciated! |
Env: Go 1.14, Windows amd64
Whenever I use the client hello of chrome for version 70, 72, or 83, the program will run into this error
HttpGetByHelloID(HelloChrome_70) failed: uTlsConn.Handshake() error: local error: tls: unexpected message
How to reproduce:
The text was updated successfully, but these errors were encountered: