ERR_SSL_VERSION_INTERFERENCE
Reported by
kusnanda...@gmail.com,
Dec 11 2017
|
||||||
Issue description
Chrome Version : 63.0.3239.84
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: OK
Firefox: OK
IE/Edge: OK
What steps will reproduce the problem?
1. update new version of google chrome
2. when i disable tls 1.3 i can access github, but some website not open normaly
3.
What is the expected result?
can open all website normaly
What happens instead of that?
github.com is currently unreachable.
ERR_SSL_VERSION_INTERFERENCE
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36
,
Dec 11 2017
Hi, Does this only effect Github or all websites? Are you able to access https://mail.google.com and https://tls.ctf.network/version.php (in the latter case, if so what version does it return)? Do you know if you have any firewall/network interception proxies/network devices on your network, we've occasionally seen this pop up due to badly acting network security devices.
,
Dec 11 2017
Please provide Netlog and instructions can be found here : https://dev.chromium.org/for-testers/providing-network-details
,
Dec 11 2017
,
Dec 12 2017
@svaldez this only effect to Github, gmail is normal, https://tls.ctf.network/version.php => You are connecting with TLSv1.3 Experiment 2. when i disable TLS 1.3 from chrome://flags/ ,i can access Github normaly, so i think this not from firewall from my network
,
Dec 12 2017
@pbomm this is my chrome net log
,
Dec 12 2017
Thanks for the NetLog! The log, however, does indeed suggest this is from something local. In the TLS 1.2 connection to github.com, it takes 247ms to get a response to the ClientHello. In the TLS 1.3-capable connection (TLS is backwards-compatible, so a correct TLS implementation will tolerate a TLS 1.2 ClientHello), we see that the connection is closed in 2ms. That timing suggests something close to you is breaking the connection. Why it only happens on github.com, which hasn't deployed TLS 1.3 yet, is puzzling, but perhaps your firewall is configured to treat that site differently? Thus, again, do you know if you have any firewall/network interception proxies/network devices on your network? We've had a host of problems this year with buggy networking middleware, so identifying what you're running is necessary to diagnose this. Thanks!
,
Dec 12 2017
> TLS is backwards-compatible, so a correct TLS implementation will tolerate a TLS 1.2 ClientHello Sorry, I mistyped: A correct *TLS 1.2* implementation will tolerate a *TLS 1.3* ClientHello. Every TLS ClientHello is also a ClientHello for prior versions.
,
Jan 12 2018
@kusnandar...: Any response to David's question in c#7 about firewalls?
,
Jan 12 2018
Thank you for providing more feedback. Adding requester "davidben@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 18 2018
kusnandartoni@ Can you please reply to comment #7, which will help in further triaging of this issue. Thanks..
,
Feb 3 2018
Archiving bug due to lack of response. kusnandartoni@, if you have the info requested in comment 7, please submit it in a new bug. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kochi@chromium.org
, Dec 11 2017