Top Qs
Timeline
Chat
Perspective

Version history for TLS/SSL support in web browsers

History of web browser protocol support From Wikipedia, the free encyclopedia

Remove ads
Remove ads

Version history for TLS/SSL support in web browsers tracks the implementation of Transport Layer Security protocol versions in major web browsers.

More information Browser or OS API, Platforms ...
More information Color or Note, Significance ...
Notes
  1. Note actual security depends on other factors such as negotiated cipher, encryption strength, etc. (see § Cipher table).
  2. Whether a user or administrator can choose the protocols to be used or not. If yes, several attacks such as BEAST (vulnerable in SSL 3.0 and TLS 1.0) or POODLE (vulnerable in SSL 3.0) can be avoided.
  3. Whether EV SSL and DV SSL (normal SSL) can be distinguished by indicators (green lock icon, green address bar, etc.) or not.
  4. e.g. 1/n-1 record splitting.
  5. e.g. Disabling header compression in HTTPS/SPDY.
    • Complete mitigations; disabling SSL 3.0 itself, "anti-POODLE record splitting". "Anti-POODLE record splitting" is effective only with client-side implementation and valid according to the SSL 3.0 specification, however, it may also cause compatibility issues due to problems in server-side implementations.
    • Partial mitigations; disabling fallback to SSL 3.0, TLS_FALLBACK_SCSV, disabling cipher suites with CBC mode of operation. If the server also supports TLS_FALLBACK_SCSV, the POODLE attack will fail against this combination of server and browser, but connections where the server does not support TLS_FALLBACK_SCSV and does support SSL 3.0 will still be vulnerable. If disabling cipher suites with CBC mode of operation in SSL 3.0, only cipher suites with RC4 are available, RC4 attacks become easier.
    • When disabling SSL 3.0 manually, POODLE attack will fail.
    • Complete mitigation; disabling cipher suites with RC4.
    • Partial mitigations to keeping compatibility with old systems; setting the priority of RC4 to lower.
  6. Google Chrome (and Chromium) supports TLS 1.0, and TLS 1.1 from version 22 (it was added, then dropped from version 21). TLS 1.2 support had been added, then dropped from Chrome 29.[6][7][8]
  7. Uses the TLS implementation provided by BoringSSL for Android, OS X, and Windows[9] or by NSS for Linux. Google is switching the TLS library used in Chrome to BoringSSL from NSS completely.
  8. Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers).
  9. configure the maximum and the minimum version of enabling protocols with command-line option.
  10. TLS_FALLBACK_SCSV is implemented.[17] Fallback to SSL 3.0 is disabled since version 39.[18]
  11. In addition to TLS_FALLBACK_SCSV and disabling a fallback to SSL 3.0, SSL 3.0 itself is disabled by default.[18]
  12. Configure the minimum version of enabling protocols via chrome://flags[22] (the maximum version can be configured with command-line option).
  13. Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback.
  14. All RC4 cipher suites are disabled by default.
  15. Uses the TLS implementation provided by NSS. As of Firefox 22, Firefox supports only TLS 1.0 despite the bundled NSS supporting TLS 1.1. Since Firefox 23, TLS 1.1 can be enabled, but was not enabled by default due to issues. Firefox 24 has TLS 1.2 support disabled by default. TLS 1.1 and TLS 1.2 have been enabled by default in Firefox 27 release.
  16. Configure the maximum and the minimum version of enabling protocols via about:config.
  17. SSL 3.0 itself is disabled by default.[40] In addition, fallback to SSL 3.0 is disabled since version 34,[42] and TLS_FALLBACK_SCSV is implemented since 35.0 and ESR 31.3.0.[40][43]
  18. IE uses the TLS implementation of the Microsoft Windows operating system provided by the Schannel security support provider. TLS 1.1 and 1.2 are disabled by default until IE11.[53][54]
  19. Windows NT 3.1 supports IE 1–2, Windows NT 3.5 supports IE 1–3, Windows NT 3.51 and Windows NT 4.0 supports IE 1–6.
  20. Windows XP as well as Server 2003 and older support only weak ciphers like Triple DES and RC4 out of the box.[58] The weak ciphers of these Schannel version are not only used for IE, but also for other Microsoft products running on this OS, like Microsoft Office or Windows Update. Only Windows Server 2003 can get a manual update to support AES ciphers by KB948963[59]
  21. MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit).
  22. DTLS protocol counterpart version, however, is not supported.[63]
  23. RC4 can be disabled except as a fallback (Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback).[66]
  24. IE11 will continue to support these operating systems if they are with ESUs until at least October 13, 2026.
  25. Fallback to SSL 3.0 is sites blocked by default in Internet Explorer 11 for Protected Mode.[68][69] SSL 3.0 is disabled by default in Internet Explorer 11 since April 2015.[70]
  26. TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022.[71][72]
  27. IE11 ran out of support for GAC (formerly CB and SAC) editions of Windows 10 since June 15, 2022.[75][76]
  28. Could be disabled via registry editing but need 3rd Party tools to do this.[78]
  29. Edge (formerly known as Project Spartan) is based on a fork of the Internet Explorer 11 rendering engine.
  30. Safari uses the operating system implementation on Mac OS X, Windows (XP, Vista, 7)[84] with unknown version,[85] Safari 5 is the last version available for Windows. OS X 10.8 on have SecureTransport support for TLS 1.1 and 1.2[86] Qualys SSL report simulates Safari 5.1.9 connecting with TLS 1.0 not 1.1 or 1.2.[87]
  31. In September 2013, Apple implemented BEAST mitigation in OS X 10.8 (Mountain Lion), but it was not turned on by default, resulting in Safari still being theoretically vulnerable to the BEAST attack on that platform.[89][90] BEAST mitigation has been enabled by default from OS X 10.8.5 updated in February 2014.[91]
  32. Because Apple removed support for all CBC protocols in SSL 3.0 to mitigate POODLE,[92][93] this leaves only RC4, which is also completely broken by the RC4 attacks in SSL 3.0.
  33. Mobile Safari and third-party software utilizing the system UIWebView library use the iOS operating system implementation, which supports TLS 1.2 as of iOS 5.0.[99][100][101]
Remove ads

References

Loading content...
Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads