ERR_SSL_VERSION_INTERFERENCE
Reported by
overlo...@gmail.com,
Sep 13 2017
|
||||||
Issue descriptionChrome Version : 61.0.3163.79 OS Version: 6.1 (Windows 7, Windows Server 2008 R2) URLs (if applicable) : https://mail.google.com/mail/u/0/#inbox Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: IE 11: OK What steps will reproduce the problem? 1. Visit mail.google.com What is the expected result? GMail loads What happens instead of that? Gmail doesn't load 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/61.0.3163.79 Safari/537.36
,
Sep 13 2017
TLS 1.3 flag: Default: Fail Disabled: OK Enabled (Draft): OK Enabled (Experiment): Fail Enabled (Record Type Experiment): Fail Enabled (No Session ID Experiment): Fail Corporate McAfee Web Gateway
,
Sep 13 2017
,
Sep 14 2017
Unable to reproduce this issue on Win 7,ubuntu 14.04 and Mac 10.12.1 with the reported version 61.0.3163.79 and latest Stable 61.0.3163.91 and latest Canary 63.0.3215.0 Could you please re-try follwing steps and update your observation 1.Either clear your cachae and visit mail.google.com or Create a New profile and visit mail.google.com Here are the steps to Create a New profile (i)Launch chrome>>Press Alt+E>>Settings) (ii)Under the section headed People, Click on link Manage other people>>Add person
,
Sep 14 2017
,
Sep 14 2017
overlordq: I think you can safely skip the steps in comment 4 - this is presumably due to a TLS 1.3 MITM (Which presumably you're already aware of, as indicated by the details you give in comment #2)
,
Sep 14 2017
This is likely caused by a middlebox on your network. Do you know if there are other network proxy/firewall devices on the network (other than the McAfee product)? If you can grab the latest Chrome Canary (63.0.3215.0 or later) from https://www.google.com/chrome/browser/canary.html and do the following steps, that would be helpful: 1) Set to TLS 1.3 to "Enabled (Experiment 2)" and restart Chrome. 2) Go to chrome://net-export and start logging. 3) Visit https://tls.ctf.network/version.php 4) Stop logging in chrome://net-export and attach the log. 5) Repeat the above steps for "Enabled (Experiment 3)".
,
Sep 14 2017
Cool, it looks like once we start running those variants of TLS 1.3 on the next release of Chrome, issues should be fixed. For now, you can leave the variant to 'Draft' on your non-Canary release, which should work around the problems caused by the middlebox. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by overlo...@gmail.com
, Sep 13 2017