"SSL protocol version" error should be "TLS protocol version"
Reported by
m...@certsimple.com,
Jul 4 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: 1. Visit an SSLv3 site, eg: https://ssl-v3.badssl.com:1003/ What is the expected behavior? Since Chrome communication generally doesn't use SSL to mean TLS, and since Chrome doesn't support SSLv3, the error should be: "The client and server don't support a common TLS protocol version or cipher suite." What went wrong? Instead the error is: "The client and server don't support a common SSL protocol version or cipher suite." Did this work before? No Chrome version: 51.0.2704.103 Channel: n/a OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 22.0 r0 Picky but hey, consistency is good.
,
Jul 4 2016
I'll let Enamel folks decide what they want here. In my mind, the SSL/TLS naming mess isn't worth bothering with and, for better or worse, everyone thinks the protocol is called "SSL" anyway. But if we normally use "TLS" (do we?), I suppose we should be consistent.
,
Jul 8 2016
We normally try to avoid using either "TLS" or "SSL" at all. I don't think this is worth fussing with though for the same reasons that davidben mentioned.
,
Dec 9 2016
Security>UX component is deprecated in favor of the Team-Security-UX label |
||||
►
Sign in to add a comment |
||||
Comment 1 by ashej...@chromium.org
, Jul 4 2016