Symantec was alerted to an interoperability issue between Symantec WSS, ProxySG and ASG products and TLS 1.3 in certain configurations. Google recently enabled field trial support for TLS 1.3, in Chrome Browser and ChromeOS 56 while accessing select Google servers. Users of Symantec ProxySG, other proxy and filtering solutions may see a connection issues as a result. Clients that enable TLS 1.3, (Chrome 56, FireFox 52) and access TLS 1.3 enabled servers, may experience SSL connection failures when going through ProxySG, WSS or ASG.

Fixes for TLS 1.3 interoperability are complete and included in the releases listed in the Resolution section.

Below is the list of releases and their release schedules that include fixes for TLS 1.3 interoperability. Symantec recommends that customers upgrade to these or later releases to avoid the issue.

Note: The Fix for the Web Security Service (WSS) was rolled out on March 4, 2017.

For the other products, the fix will be included in all future SW versions starting with:

• SG 6.5.10.3 was released on May 16, 2017
• SG 6.6.5.4 was released on Mar 16, 2017
• ASG 6.6.5.6 was released on Apr 7, 2017
• SG 6.7.1.2 was released on Mar 21, 2017

For Chrome users:
TLS 1.3 can be disabled by accessing URL “chrome://flags/#ssl-version-max”, changing the setting from “Default” to “TLS 1.2”, and then relaunching Chrome. The below image shows the configuration set to TLS 1.2:

(Note: A recent update changed Chrome to not use TLS 1.3 by default. This change was to help mitigate issues seen in the field.)

For FireFox users:
TLS 1.3 can be disabled by accessing URL “about:config”, search for security.tls.version.max, change it from “4”, which is TLS 1.3, to “3”, which is TLS 1.2, and restart the browser. The below image shows the the configuration set to “3”, which is TLS 1.2:


How to confirm if TLS 1.3 is supported by a browser:
SSL Labs provides a URL which will test and report the TLS versions supported by the browser requesting the URL. That URL is: https://www.ssllabs.com/ssltest/viewMyClient.html. The following screen shots show the results of the above URL on FireFox 52 with its default configuration:

And after following the steps above to disable TLS 1.3 support:


Work around on the ProxySG or ASG:
For explicit deployments policy can be added to disable protocol detection for any impacted website. The following knowledge base article describes how this is done in policy: http://bluecoat.force.com/knowledgebase/articles/Solution/SSL-interception-prevents-device-from-connecting-out-on-port-443.  For transparent deployments a TCP-Tunnel service will need to be created that includes the affected destination IPs. The following knowledge base article describes how this is done in proxy services: http://bluecoat.force.com/knowledgebase/articles/Solution/000029291

6.6.x.x - Bug # 244389
6.5.x.x - Bug # 244448