Version history for TLS/SSL support in web browsers

Last updated

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

TLS/SSL support history of web browsers
Browser
or OS API
VersionPlatformsSSL protocolsTLS protocolsCertificate supportVulnerability [n 1] Protocol selection by user [n 2]
SSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3 EV [n 3] [1] SHA-2 [2] ECDSA [3] BEAST [n 4] CRIME [n 5] POODLE (SSLv3) [n 6] RC4 [n 7] FREAK [4] [5] Logjam
Google Chrome
(Chrome for Android) [n 8] [n 9]
1–9 Windows (10+)
macOS (11+)
Linux
Android (8.0+)
iOS (14+)
ChromeOS
Disabled by defaultYesYesNoNoNoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affected [10] Vulnerable
(HTTPS)
VulnerableVulnerableVulnerable
(except Windows)
VulnerableYes [n 10]
10–20No [11] YesYesNoNoNoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affectedVulnerable
(HTTPS/SPDY)
VulnerableVulnerableVulnerable
(except Windows)
VulnerableYes [n 10]
21NoYesYesNoNoNoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affectedMitigated [12] VulnerableVulnerableVulnerable
(except Windows)
VulnerableYes [n 10]
22–29NoYesYesYes [13] No [13] [14] [15] [16] NoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affectedMitigatedVulnerableVulnerableVulnerable
(except Windows)
VulnerableTemporary [n 11]
30–32NoYesYesYesYes [14] [15] [16] NoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affectedMitigatedVulnerableVulnerableVulnerable
(except Windows)
VulnerableTemporary [n 11]
33–37NoYesYesYesYesNoYes
(only desktop)
Requires SHA-2 compatible OS [2] Needs ECC compatible OS [3] Not affectedMitigatedPartly mitigated [n 12] Lowest priority [19] [20] [21] Vulnerable
(except Windows)
VulnerableTemporary [n 11]
38, 39NoYesYesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedPartly mitigatedLowest priorityVulnerable
(except Windows)
VulnerableTemporary [n 11]
40NoDisabled by default [18] [22] YesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedMitigated [n 13] Lowest priorityVulnerable
(except Windows)
VulnerableYes [n 14]
41, 42NoDisabled by defaultYesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedMitigatedLowest priorityMitigatedVulnerableYes [n 14]
43NoDisabled by defaultYesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedMitigatedOnly as fallback [n 15] [23] MitigatedVulnerableYes [n 14]
44–47NoNo [24] YesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedNot affectedOnly as fallback [n 15] MitigatedMitigated [25] Temporary [n 11]
48, 49NoNoYesYesYesNoYes
(only desktop)
YesNeeds ECC compatible OS [3] Not affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
50–53NoNoYesYesYesNoYes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
54–66NoNoYesYesYesDisabled by default
(draft version)
Yes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
67–69NoNoYesYesYesYes
(draft version)
Yes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
70–83NoNoYesYesYesYesYes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
84–90NoNoWarn by defaultWarn by defaultYesYesYes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
91–129NoNoNo [28] No [28] YesYesYes
(only desktop)
YesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [26] [27] MitigatedMitigatedTemporary [n 11]
ESC 130131
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Microsoft Edge
(Chromium-based)
OS-independent
79–83 Windows (10+)
macOS (11+)
Linux 
Android (8.0+)
iOS (14.0+)
NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by defaultMitigatedMitigatedYes [n 10]
84–90NoNoWarn by defaultWarn by defaultYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by defaultMitigatedMitigatedYes [n 10]
91-129NoNoNo [29] No [29] YesYesYesYesYesMitigatedNot affectedNot affectedDisabled by defaultMitigatedMitigatedYes [n 10]
ESC 130131
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Mozilla Firefox
(Firefox for mobile) [n 17]
1.0, 1.5 Windows (10+)
macOS (10.15+)
Linux
Android (5.0+)
iOS (15+)
Firefox OS
Maemo

ESR 115 only for:
Windows (7–8.1)
macOS (10.12–10.14)

ESR 128+ only for:
Windows (10+)
macOS (10.15+)
Linux
Yes [30] Yes [30] Yes [30] NoNoNoNoYes [2] NoNot affected [31] Not affectedVulnerableVulnerableNot affectedVulnerableYes [n 10]
2Disabled by default [30] [32] YesYesNoNoNoNoYesYes [3] Not affectedNot affectedVulnerableVulnerableNot affectedVulnerableYes [n 10]
3–7Disabled by defaultYesYesNoNoNoYesYesYesNot affectedNot affectedVulnerableVulnerableNot affectedVulnerableYes [n 10]
8–10
ESR 10
No [32] YesYesNoNoNoYesYesYesNot affectedNot affectedVulnerableVulnerableNot affectedVulnerableYes [n 10]
11–14NoYesYesNoNoNoYesYesYesNot affectedVulnerable
(SPDY) [12]
VulnerableVulnerableNot affectedVulnerableYes [n 10]
15–22
ESR 17.0–17.0.10
NoYesYesNoNoNoYesYesYesNot affectedMitigatedVulnerableVulnerableNot affectedVulnerableYes [n 10]
ESR 17.0.11NoYesYesNoNoNoYesYesYesNot affectedMitigatedVulnerableLowest priority [33] [34] Not affectedVulnerableYes [n 10]
23NoYesYesDisabled by default [35] NoNoYesYesYesNot affectedMitigatedVulnerableVulnerableNot affectedVulnerableYes [n 18]
24, 25.0.0
ESR 24.0–24.1.0
NoYesYesDisabled by defaultDisabled by default [36] NoYesYesYesNot affectedMitigatedVulnerableVulnerableNot affectedVulnerableYes [n 18]
25.0.1, 26
ESR 24.1.1–24.8.1
NoYesYesDisabled by defaultDisabled by defaultNoYesYesYesNot affectedMitigatedVulnerableLowest priority [33] [34] Not affectedVulnerableYes [n 18]
27–33
ESR 31.0–31.2.0
NoYesYesYes [37] [38] Yes [39] [38] NoYesYesYesNot affectedMitigatedVulnerableLowest priorityNot affectedVulnerableYes [n 18]
34, 35
ESR 31.3.0–31.7.0
NoDisabled by default [40] [41] YesYesYesNoYesYesYesNot affectedMitigatedMitigated [n 19] Lowest priorityNot affectedVulnerableYes [n 18]
ESR 31.8.0NoDisabled by defaultYesYesYesNoYesYesYesNot affectedMitigatedMitigatedLowest priorityNot affectedMitigated [44] Yes [n 18]
36–38
ESR 38.0–38.0.1
NoDisabled by defaultYesYesYesNoYesYesYesNot affectedMitigatedMitigatedOnly as fallback [n 15] [45] Not affectedVulnerableYes [n 18]
ESR 38.1.0–38.8.0NoDisabled by defaultYesYesYesNoYesYesYesNot affectedMitigatedMitigatedOnly as fallback [n 15] Not affectedMitigated [44] Yes [n 18]
39–43NoNo [46] YesYesYesNoYesYesYesNot affectedMitigatedNot affectedOnly as fallback [n 15] Not affectedMitigated [44] Yes [n 18]
44–48
ESR 45
NoNoYesYesYesNoYesYesYesNot affectedMitigatedNot affectedDisabled by default [n 16] [47] [48] [49] [50] Not affectedMitigatedYes [n 18]
49–59
ESR 52
NoNoYesYesYesDisabled by default
(draft version) [51]
YesYesYesNot affectedMitigatedNot affectedDisabled by default [n 16] Not affectedMitigatedYes [n 18]
60–62
ESR 60
NoNoYesYesYesYes
(draft version)
YesYesYesNot affectedMitigatedNot affectedDisabled by default [n 16] Not affectedMitigatedYes [n 18]
63–77
ESR 68
NoNoYesYesYesYesYesYesYesNot affectedMitigatedNot affectedDisabled by default [n 16] Not affectedMitigatedYes [n 18]
78–131
ESR 78–115.16
ESR 128.0–128.3
NoNoDisabled by default [52] Disabled by default [52] YesYesYesYesYesNot affectedMitigatedNot affectedDisabled by default [n 16] Not affectedMitigatedYes [n 18]
ESR 115.17
ESR 128.4
132
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Microsoft Internet Explorer
(1–10) [n 20]

Windows Schannel
1.x Windows 3.1, 95, NT, [n 21] [n 22]
Mac OS 7, 8
No SSL/TLS support
2 YesNoNoNoNoNoNoNoNoNo SSL 3.0 or TLS supportVulnerableVulnerableVulnerable
3 YesYes [55] NoNoNoNoNoNoNoVulnerableNot affectedVulnerableVulnerableVulnerableVulnerable ?
4, 5, 6 Windows 3.1, 95, 98, NT, 2000 [n 21] [n 22]
Mac OS 7.1, 8, X,
Solaris, HP-UX
YesYesDisabled by default [55] NoNoNoNoNoNoVulnerableNot affectedVulnerableVulnerableVulnerableVulnerableYes [n 10]
6 Windows XP [n 22] YesYesDisabled by defaultNoNoNoNoYes (Since SP3) [n 23] [56] NoMitigatedNot affectedVulnerableVulnerableVulnerableVulnerableYes [n 10]
7, 8 Disabled by default [57] YesYes [57] NoNoNoYesYes (Since SP3) [n 23] [56] NoMitigatedNot affectedVulnerableVulnerableVulnerableVulnerableYes [n 10]
6 Server 2003 [n 22] YesYesDisabled by defaultNoNoNoNoYes
(KB938397+KB968730) [n 23] [56]
NoMitigatedNot affectedVulnerableVulnerableMitigated [60] Mitigated [61] Yes [n 10]
7, 8 Disabled by default [57] YesYes [57] NoNoNoYesYes
(KB938397+KB968730) [n 23] [56]
NoMitigatedNot affectedVulnerableVulnerableMitigated [60] Mitigated [61] Yes [n 10]
7, 8, 9 Windows Vista Disabled by defaultYesYesNoNoNoYesYesYes [3] MitigatedNot affectedVulnerableVulnerableMitigated [60] Mitigated [61] Yes [n 10]
7, 8, 9 Server 2008 Disabled by defaultYesYesDisabled by default [62]
(KB4019276)
[n 24]
Disabled by default [62]
(KB4019276)
[n 24]
NoYesYesYes [3] MitigatedNot affectedVulnerableVulnerableMitigated [60] Mitigated [61] Yes [n 10]
8, 9, 10 7, 8
Server 2008 R2
Server 2012
Disabled by defaultYesYesDisabled by default [n 24] [64] Disabled by default [n 24] [64] NoYesYesYesMitigatedNot affectedVulnerableLowest priority [65] [n 25] Mitigated [60] Mitigated [61] Yes [n 10]
Internet Explorer 11 [n 20]

Windows Schannel
11 [n 26] [67] 7, 8.1
Server 2008 R2
Server 2012 [67]
Server 2012 R2
Disabled by defaultDisabled by default [n 27] Disabled by default [n 28] Disabled by default [n 24] [n 28] Yes [n 24] [73] NoYesYesYesMitigatedNot affectedMitigated [n 27] Disabled by default [n 16] Mitigated [60] Mitigated [61] Yes [n 10]
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Microsoft Edge
(12–18)
(EdgeHTML-based)
Client only


Internet Explorer 11 [n 20]

Windows Schannel
1112–13Windows 10 15071511 Disabled by defaultYes [63] YesYesYes [n 24] NoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
1114–18
(client only)
Windows 10 16072004
Windows Server (SAC)
1709–2004
No [74] Disabled by defaultYesYesYesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Internet Explorer 11 [n 20]

Windows Schannel
11 [n 29] Windows 10 20H221H2
Windows Server (SAC)
20H2
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 10 22H2
Windows Schannel Windows 11 21H2 NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYes [63] YesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 11 22H2
(Home/Pro)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 11 22H2
(Ent/Edu)
Windows 11 23H2
(Home/Pro)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 11 23H2
(Ent/Edu)
Windows 11 24H2 NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Internet Explorer 11 [n 20]
LTSB/LTSC

Windows Schannel
LTSB/LTSC
11 Windows 10
LTSB 2015 (1507)
Disabled by defaultYes [63] Disabled by default [n 28] Disabled by default [n 28] Yes [n 24] NoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 10
LTSB 2016 (1607)
No [74] Disabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows Server 2016
(LTSB/1607)
No [74] Disabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 10
LTSC 2019 (1809)
Windows Server 2019
(LTSC/1809)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows 10
LTSC 2021 (21H2)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesNo [63] YesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows Server 2022
(LTSC/21H2)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows Schannel
LTSC
Windows 11
LTSC 2024 (24H2)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Windows Server 2025
(LTSC/24H2)
NoDisabled by defaultDisabled by default [n 28] Disabled by default [n 28] YesYesYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedYes [n 10]
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Microsoft Internet Explorer Mobile [n 20] 7–9 Windows Phone 7, 7.5, 7.8 Disabled by default [57] YesYesNo[ citation needed ]No[ citation needed ]NoNo[ citation needed ]YesYes [77]  ?Not affectedVulnerableVulnerableVulnerableVulnerableOnly with 3rd party tools [n 30]
10 Windows Phone 8 Disabled by defaultYesYesDisabled by default [79] Disabled by default [79] NoNo[ citation needed ]YesYes [80] MitigatedNot affectedVulnerableVulnerableVulnerableVulnerableOnly with 3rd party tools [n 30]
11 Windows Phone 8.1 Disabled by defaultYesYesYes [81] Yes [81] NoNo[ citation needed ]YesYesMitigatedNot affectedVulnerableOnly as fallback [n 15] [82] [83] VulnerableVulnerableOnly with 3rd party tools [n 30]
Microsoft Edge
(13–15)
(EdgeHTML-based) [n 31]
13 Windows 10 Mobile 1511Disabled by defaultDisabled by defaultYesYesYesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedNo
14, 15 Windows 10 Mobile
1607–1709
No [74] Disabled by defaultYesYesYesNoYesYesYesMitigatedNot affectedMitigatedDisabled by default [n 16] MitigatedMitigatedNo
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Apple Safari [n 32] 1Mac OS X 10.2, 10.3 No [88] YesYesNoNoNoNoNoNoVulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
2–5Mac OS X 10.4, 10.5, Win XP NoYesYesNoNoNoYes (Since v3.2)NoNoVulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
3–5 Vista, Win 7 NoYesYesNoNoNoYes (Since v3.2)NoYes [77] VulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
4–6Mac OS X 10.6, 10.7 NoYesYesNoNoNoYesYes [2] Yes [3] VulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
6 OS X 10.8 NoYesYesNoNoNoYesYesYes [3] Mitigated [n 33] Not affectedMitigated [n 34] Vulnerable [n 34] Mitigated [94] VulnerableNo
7, 9 OS X 10.9 NoYesYesYes [95] Yes [95] NoYesYesYesMitigated [90] Not affectedMitigated [n 34] Vulnerable [n 34] Mitigated [94] VulnerableNo
8–10 OS X 10.10 NoYesYesYesYesNoYesYesYesMitigatedNot affectedMitigated [n 34] Lowest priority [96] [n 34] Mitigated [94] Mitigated [97] No
9–11 OS X 10.11 NoNoYesYesYesNoYesYesYesMitigatedNot affectedNot affectedLowest priorityMitigatedMitigatedNo
10–15macOS
10.12, 10.13,
10.14, 10.15
NoNoYesYesYesYes (Since macOS 10.14.4) [98] YesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
14–16 macOS 11 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
15–17 macOS 12 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
16, 1718 macOS 13 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
1718 macOS 14 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
18 macOS 15 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Apple Safari
(mobile) [n 35]
3iPhone OS 1, 2 No [102] YesYesNoNoNoNoNoNoVulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
4, 5 iPhone OS 3, iOS 4 NoYesYesNoNoNoYes [103] YesYes (Since iOS 4) [77] VulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
5, 6iOS 5, 6 NoYesYesYes [99] Yes [99] NoYesYesYesVulnerableNot affectedVulnerableVulnerableVulnerableVulnerableNo
7 iOS 7 NoYesYesYesYesNoYesYesYes [104] Mitigated [105] Not affectedVulnerableVulnerableVulnerableVulnerableNo
8 iOS 8 NoYesYesYesYesNoYesYesYesMitigatedNot affectedMitigated [n 34] Lowest priority [106] [n 34] Mitigated [107] Mitigated [108] No
9 iOS 9 NoNoYesYesYesNoYesYesYesMitigatedNot affectedNot affectedLowest priorityMitigatedMitigatedNo
10, 11iOS 10, 11 NoNoYesYesYesNoYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
12–14iOS
12, 13, 14
NoNoYesYesYesYes (Since iOS 12.2) [98] YesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
iPadOS
13, 14
15 iOS 15 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
iPadOS 15
16 iOS 16 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
iPadOS 16
17 iOS 17 NoNoYesYesYesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
iPadOS 17
18 iOS 18 NoNo ? ?YesYesYesYesYesMitigatedNot affectedNot affectedDisabled by default [n 16] MitigatedMitigatedNo
iPadOS 18
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV [n 3] SHA-2ECDSABEAST [n 4] CRIME [n 5] POODLE (SSLv3) [n 6] RC4 [n 7] FREAK [4] [5] LogjamProtocol selection by user
Google Android OS [109] Android 1.0–4.0.4 NoYesYesNoNoNo ?Yes [2] Yes (Since 3.0) [77] [3]  ? ?VulnerableVulnerableVulnerableVulnerableNo
Android 4.1–4.4.4 NoYesYesDisabled by default [110] Disabled by default [110] No ?YesYes ? ?VulnerableVulnerableVulnerableVulnerableNo
Android 5.0–5.0.2 NoYesYesYes [110] [111] Yes [110] [111] No ?YesYes ? ?VulnerableVulnerableVulnerableVulnerableNo
Android 5.1–5.1.1 NoDisabled by default[ citation needed ]YesYesYesNo ?YesYes ? ?Not affectedOnly as fallback [n 15] MitigatedMitigatedNo
Android 6.07.1.2 NoDisabled by default[ citation needed ]YesYesYesNo ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 8.09 NoNo [112] YesYesYesNo ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 1011 NoNoYesYesYesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 12 NoNoYesYesYesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 12L NoNoYesYesYesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 13 NoNoYesYesYesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 14 NoNoYesYesYesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 15 NoNo ? ?YesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Android 16 NoNo ? ?YesYes ?YesYes ? ?Not affectedDisabled by defaultMitigatedMitigatedNo
Browser
or OS API
VersionPlatformsSSL 2.0 (insecure)SSL 3.0 (insecure)TLS 1.0 (deprecated)TLS 1.1 (deprecated)TLS 1.2TLS 1.3EV certificateSHA-2 certificateECDSA certificateBEASTCRIMEPOODLE (SSLv3)RC4FREAKLogjamProtocol selection by user
Color or NoteSignificance
Browser versionPlatform
Browser versionOperating systemFuture release; under development
Browser versionOperating systemCurrent latest release
Browser versionOperating systemFormer release; still supported
Browser versionOperating systemFormer release; long-term support still active, but will end in less than 12 months
Browser versionOperating systemFormer release; no longer supported
Operating systemMixed/Unspecified
Operating system (Version+)Minimum required operating system version (for supported versions of the browser)
Operating systemNo longer supported for this operating system
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. 1 2 Whether EV SSL and DV SSL (normal SSL) can be distinguished by indicators (green lock icon, green address bar, etc.) or not.
  4. 1 2 e.g. 1/n-1 record splitting.
  5. 1 2 e.g. Disabling header compression in HTTPS/SPDY.
  6. 1 2
    • 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.
  7. 1 2
    • Complete mitigation; disabling cipher suites with RC4.
    • Partial mitigations to keeping compatibility with old systems; setting the priority of RC4 to lower.
  8. 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]
  9. 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.
  10. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 Configure enabling/disabling of each protocols via setting/option (menu name is dependent on browsers).
  11. 1 2 3 4 5 6 7 8 9 10 11 12 configure the maximum and the minimum version of enabling protocols with command-line option.
  12. TLS_FALLBACK_SCSV is implemented. [17] Fallback to SSL 3.0 is disabled since version 39. [18]
  13. In addition to TLS_FALLBACK_SCSV and disabling a fallback to SSL 3.0, SSL 3.0 itself is disabled by default. [18]
  14. 1 2 3 Configure the minimum version of enabling protocols via chrome://flags [22] (the maximum version can be configured with command-line option).
  15. 1 2 3 4 5 6 7 Only when no cipher suites with other than RC4 is available, cipher suites with RC4 will be used as a fallback.
  16. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 All RC4 cipher suites are disabled by default.
  17. 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.
  18. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Configure the maximum and the minimum version of enabling protocols via about:config.
  19. 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]
  20. 1 2 3 4 5 6 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]
  21. 1 2 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.
  22. 1 2 3 4 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]
  23. 1 2 3 4 MS13-095 or MS14-049 for Windows Server 2003, Windows XP x64 and Windows XP SP3 (32-bit).
  24. 1 2 3 4 5 6 7 8 DTLS protocol counterpart version, however, is not supported. [63]
  25. 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]
  26. IE11 will continue to support these operating systems if they are with ESUs until at least October 13, 2026.
  27. 1 2 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]
  28. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 TLS 1.0 and 1.1 are disabled by default in Internet Explorer 11 and EdgeHTML since September 2022. [71] [72]
  29. IE11 ran out of support for GAC (formerly CB and SAC) editions of Windows 10 since June 15, 2022. [75] [76]
  30. 1 2 3 Could be disabled via registry editing but need 3rd Party tools to do this. [78]
  31. Edge (formerly known as Project Spartan) is based on a fork of the Internet Explorer 11 rendering engine.
  32. 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]
  33. 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]
  34. 1 2 3 4 5 6 7 8 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.
  35. 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]

Related Research Articles

<span class="mw-page-title-main">HTTPS</span> Extension of the HTTP communications protocol to support TLS encryption

Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It uses encryption for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL.

In cryptography, RC4 is a stream cipher. While it is remarkable for its simplicity and speed in software, multiple vulnerabilities have been discovered in RC4, rendering it insecure. It is especially vulnerable when the beginning of the output keystream is not discarded, or when nonrandom or related keys are used. Particularly problematic uses of RC4 have led to very insecure protocols such as WEP.

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network, such as the Internet. The protocol is widely used in applications such as email, instant messaging, and voice over IP, but its use in securing HTTPS remains the most publicly visible.

In cryptography, Camellia is a symmetric key block cipher with a block size of 128 bits and key sizes of 128, 192 and 256 bits. It was jointly developed by Mitsubishi Electric and NTT of Japan. The cipher has been approved for use by the ISO/IEC, the European Union's NESSIE project and the Japanese CRYPTREC project. The cipher has security levels and processing abilities comparable to the Advanced Encryption Standard.

The Online Certificate Status Protocol (OCSP) is an Internet protocol used for obtaining the revocation status of an X.509 digital certificate. It is described in RFC 6960 and is on the Internet standards track. It was created as an alternative to certificate revocation lists (CRL), specifically addressing certain problems associated with using CRLs in a public key infrastructure (PKI). Messages communicated via OCSP are encoded in ASN.1 and are usually communicated over HTTP. The "request/response" nature of these messages leads to OCSP servers being termed OCSP responders.

This is a comparison of both historical and current web browsers based on developer, engine, platform(s), releases, license, and cost.

SEED is a block cipher developed by the Korea Information Security Agency (KISA). It is used broadly throughout South Korean industry, but seldom found elsewhere. It gained popularity in Korea because 40-bit encryption was not considered strong enough, so the Korea Information Security Agency developed its own standard. However, this decision has historically limited the competition of web browsers in Korea, as no major SSL libraries or web browsers supported the SEED algorithm, requiring users to use an ActiveX control in Internet Explorer for secure web sites.

Datagram Transport Layer Security (DTLS) is a communications protocol providing security to datagram-based applications by allowing them to communicate in a way designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the stream-oriented Transport Layer Security (TLS) protocol and is intended to provide similar security guarantees. The DTLS protocol datagram preserves the semantics of the underlying transport—the application does not suffer from the delays associated with stream protocols, but because it uses User Datagram Protocol (UDP) or Stream Control Transmission Protocol (SCTP), the application has to deal with packet reordering, loss of datagram and data larger than the size of a datagram network packet. Because DTLS uses UDP or SCTP rather than TCP it avoids the TCP meltdown problem when being used to create a VPN tunnel.

The Online Certificate Status Protocol (OCSP) stapling, formally known as the TLS Certificate Status Request extension, is a standard for checking the revocation status of X.509 digital certificates. It allows the presenter of a certificate to bear the resource cost involved in providing Online Certificate Status Protocol (OCSP) responses by appending ("stapling") a time-stamped OCSP response signed by the CA to the initial TLS handshake, eliminating the need for clients to contact the CA, with the aim of improving both security and performance.

<span class="mw-page-title-main">WebGL</span> JavaScript bindings for OpenGL in web browsers

WebGL is a JavaScript API for rendering interactive 2D and 3D graphics within any compatible web browser without the use of plug-ins. WebGL is fully integrated with other web standards, allowing GPU-accelerated usage of physics, image processing, and effects in the HTML canvas. WebGL elements can be mixed with other HTML elements and composited with other parts of the page or page background.

SPDY is an obsolete open-specification communication protocol developed for transporting web content. SPDY became the basis for HTTP/2 specification. However, HTTP/2 diverged from SPDY and eventually HTTP/2 subsumed all usecases of SPDY. After HTTP/2 was ratified as a standard, major implementers, including Google, Mozilla, and Apple, deprecated SPDY in favor of HTTP/2. Since 2021, no modern browser supports SPDY.

HTTP Strict Transport Security (HSTS) is a policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks and cookie hijacking. It allows web servers to declare that web browsers should automatically interact with it using only HTTPS connections, which provide Transport Layer Security (TLS/SSL), unlike the insecure HTTP used alone. HSTS is an IETF standards track protocol and is specified in RFC 6797.

A cipher suite is a set of algorithms that help secure a network connection. Suites typically use Transport Layer Security (TLS) or its deprecated predecessor Secure Socket Layer (SSL). The set of algorithms that cipher suites usually contain include: a key exchange algorithm, a bulk encryption algorithm, and a message authentication code (MAC) algorithm.

StartCom was a certificate authority founded in Eilat, Israel, and later based in Beijing, China, that had three main activities: StartCom Enterprise Linux, StartSSL and MediaHost. StartCom set up branch offices in China, Hong Kong, the United Kingdom and Spain. Due to multiple faults on the company's end, all StartCom certificates were removed from Mozilla Firefox in October 2016 and Google Chrome in March 2017, including certificates previously issued, with similar removals from other browsers expected to follow.

The Transport Layer Security (TLS) protocol provides the ability to secure communications across or inside networks. This comparison of TLS implementations compares several of the most notable libraries. There are several TLS implementations which are free software and open source.

Firefox was created by Dave Hyatt and Blake Ross as an experimental branch of the Mozilla browser, first released as Firefox 1.0 on November 9, 2004. Starting with version 5.0, a rapid release cycle was put into effect, resulting in a new major version release every six weeks. This was gradually accelerated further in late 2019, so that new major releases occur on four-week cycles starting in 2020.

Application-Layer Protocol Negotiation (ALPN) is a Transport Layer Security (TLS) extension that allows the application layer to negotiate which protocol should be performed over a secure connection in a manner that avoids additional round trips and which is independent of the application-layer protocols. It is used to establish HTTP/2 connections without additional round trips.

POODLE is a security vulnerability which takes advantage of the fallback to SSL 3.0. If attackers successfully exploit this vulnerability, on average, they only need to make 256 SSL 3.0 requests to reveal one byte of encrypted messages. Bodo Möller, Thai Duong and Krzysztof Kotowicz from the Google Security Team discovered this vulnerability; they disclosed the vulnerability publicly on October 14, 2014. On December 8, 2014, a variation of the POODLE vulnerability that affected TLS was announced.

FREAK is a security exploit of a cryptographic weakness in the SSL/TLS protocols introduced decades earlier for compliance with U.S. cryptography export regulations. These involved limiting exportable software to use only public key pairs with RSA moduli of 512 bits or fewer, with the intention of allowing them to be broken easily by the National Security Agency (NSA), but not by other organizations with lesser computing resources. However, by the early 2010s, increases in computing power meant that they could be broken by anyone with access to relatively modest computing resources using the well-known Number Field Sieve algorithm, using as little as $100 of cloud computing services. Combined with the ability of a man-in-the-middle attack to manipulate the initial cipher suite negotiation between the endpoints in the connection and the fact that the finished hash only depended on the master secret, this meant that a man-in-the-middle attack with only a modest amount of computation could break the security of any website that allowed the use of 512-bit export-grade keys. While the exploit was only discovered in 2015, its underlying vulnerabilities had been present for many years, dating back to the 1990s.

DNS over HTTPS (DoH) is a protocol for performing remote Domain Name System (DNS) resolution via the HTTPS protocol. A goal of the method is to increase user privacy and security by preventing eavesdropping and manipulation of DNS data by man-in-the-middle attacks by using the HTTPS protocol to encrypt the data between the DoH client and the DoH-based DNS resolver. By March 2018, Google and the Mozilla Foundation had started testing versions of DNS over HTTPS. In February 2020, Firefox switched to DNS over HTTPS by default for users in the United States. In May 2020, Chrome switched to DNS over HTTPS by default.

References

  1. "What browsers support Extended Validation (EV) and display an EV indicator?". Symantec. Archived from the original on 2015-12-31. Retrieved 2014-07-28.
  2. 1 2 3 4 5 6 7 8 9 10 "SHA-256 Compatibility". Archived from the original on 2015-07-01. Retrieved 2015-06-12.
  3. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 "ECC Compatibility". Archived from the original on 2016-02-17. Retrieved 2015-06-13.
  4. 1 2 "Tracking the FREAK Attack". Archived from the original on 2015-03-06. Retrieved 2015-03-08.
  5. 1 2 "FREAK: Factoring RSA Export Keys". Archived from the original on 2015-03-11. Retrieved 2015-03-08.
  6. "Dev Channel Update". 2012-05-29. Archived from the original on 2013-03-02. Retrieved 2011-06-01.
  7. "Stable Channel Update". 2012-08-21. Archived from the original on 2012-08-25. Retrieved 2012-08-22.
  8. Chromium Project (2013-05-30). "Chromium TLS 1.2 Implementation".
  9. "The Chromium Project: BoringSSL". Archived from the original on 2015-09-23. Retrieved 2015-09-05.
  10. "Chrome Stable Release". Chrome Releases. 2011-10-25. Archived from the original on 2015-02-20. Retrieved 2015-02-01.
  11. "SVN revision log on Chrome 10.0.648.127 release". Archived from the original on 2014-06-19. Retrieved 2014-06-19.
  12. 1 2 "ImperialViolet – CRIME". 2012-09-22. Archived from the original on 2015-01-10. Retrieved 2014-10-18.
  13. 1 2 "SSL/TLS Overview". 2008-08-06. Archived from the original on 2013-07-03. Retrieved 2013-03-29.
  14. 1 2 "Chromium Issue 90392". 2008-08-06. Archived from the original on 2013-08-03. Retrieved 2013-06-28.
  15. 1 2 "Issue 23503030 Merge 219882". 2013-09-03. Archived from the original on 2014-02-26. Retrieved 2013-09-19.
  16. 1 2 "Issue 278370: Unable to submit client certificates over TLS 1.2 from Windows". 2013-08-23. Archived from the original on 2013-10-05. Retrieved 2013-10-03.
  17. Möller, Bodo (2014-10-14). "This POODLE bites: exploiting the SSL 3.0 fallback". Google Online Security blog. Google (via Blogspot). Archived from the original on 2014-10-28. Retrieved 2014-10-28.
  18. 1 2 3 "An update on SSLv3 in Chrome". Security-dev. 2014-10-31. Retrieved 2014-11-04.
  19. "Stable Channel Update". Mozilla Developer Network. 2014-02-20. Archived from the original on 2014-10-24. Retrieved 2014-11-14.
  20. "Changelog for Chrome 33.0.1750.117". Google. Archived from the original on 2014-01-16. Retrieved 2014-11-14.
  21. "Issue 318442: Update to NSS 3.15.3 and NSPR 4.10.2". Archived from the original on 2015-03-15. Retrieved 2014-11-14.
  22. 1 2 "Issue 693963003: Add minimum TLS version control to about:flags and Finch gate it. – Code Review". Archived from the original on 2015-04-16. Retrieved 2015-01-22.
  23. "Issue 375342: Drop RC4 Support". Archived from the original on 2015-09-12. Retrieved 2015-05-22.
  24. "Issue 436391: Add info on end of life of SSLVersionFallbackMin & SSLVersionMin policy in documentation". Archived from the original on 2015-04-18. Retrieved 2015-04-19.
  25. "Issue 490240: Increase minimum DH size to 1024 bits (tracking bug)". Archived from the original on 2015-09-12. Retrieved 2015-05-29.
  26. 1 2 3 4 5 6 7 "Intent to deprecate: RC4" . Retrieved 2015-12-21.
  27. 1 2 3 4 5 6 7 "An update on SHA-1 certificates in Chrome". 2015-12-18. Archived from the original on 2015-12-18. Retrieved 2015-12-21.
  28. 1 2 "Chrome Enterprise release notes - Google Chrome Enterprise Help".
  29. 1 2 "Microsoft Edge Browser Policy Documentation | Microsoft Docs". Docs.microsoft.com. 2021-10-15. Retrieved 2022-02-15.
  30. 1 2 3 4 "Security in Firefox 2". 2008-08-06. Archived from the original on 2014-07-14. Retrieved 2009-03-31.
  31. "Attack against TLS-protected communications". Mozilla Security Blog. Mozilla. 2011-09-27. Archived from the original on 2015-03-04. Retrieved 2015-02-01.
  32. 1 2 "Introduction to SSL". MDN. Archived from the original on 2014-07-14. Retrieved 2014-06-19.
  33. 1 2 "NSS 3.15.3 Release Notes". Mozilla Developer Network. Mozilla. Archived from the original on 2014-06-05. Retrieved 2014-07-13.
  34. 1 2 "MFSA 2013-103: Miscellaneous Network Security Services (NSS) vulnerabilities". Mozilla. Archived from the original on 2014-07-14. Retrieved 2014-07-13.
  35. "Bug 565047 – (RFC4346) Implement TLS 1.1 (RFC 4346)" . Retrieved 2013-10-29.
  36. "Bug 480514 – Implement support for TLS 1.2 (RFC 5246)" . Retrieved 2013-10-29.
  37. "Bug 733647 – Implement TLS 1.1 (RFC 4346) in Gecko (Firefox, Thunderbird), on by default" . Retrieved 2013-12-04.
  38. 1 2 "Firefox Notes – Desktop". 2014-02-04. Archived from the original on 2014-02-07. Retrieved 2014-02-04.
  39. "Bug 861266 – Implement TLS 1.2 (RFC 5246) in Gecko (Firefox, Thunderbird), on by default" . Retrieved 2013-11-18.
  40. 1 2 3 "The POODLE Attack and the End of SSL 3.0". Mozilla blog. Mozilla. 2014-10-14. Archived from the original on 2014-10-18. Retrieved 2014-10-28.
  41. "Firefox — Notes (34.0) — Mozilla". mozilla.org. 2014-12-01. Archived from the original on 2015-04-09. Retrieved 2015-04-03.
  42. "Bug 1083058 – A pref to control TLS version fallback". bugzilla.mozilla.org. Retrieved 2014-11-06.
  43. "Bug 1036737 – Add support for draft-ietf-tls-downgrade-scsv to Gecko/Firefox". bugzilla.mozilla.org. Retrieved 2014-10-29.
  44. 1 2 3 "Bug 1166031 – Update to NSS 3.19.1". bugzilla.mozilla.org. Retrieved 2015-05-29.
  45. "Bug 1088915 – Stop offering RC4 in the first handshakes". bugzilla.mozilla.org. Retrieved 2014-11-04.
  46. "Firefox — Notes (39.0) — Mozilla". mozilla.org. 2015-06-30. Archived from the original on 2015-07-03. Retrieved 2015-07-03.
  47. "Google, Microsoft, and Mozilla will drop RC4 encryption in Chrome, Edge, IE, and Firefox next year". VentureBeat. 2015-09-01. Archived from the original on 2015-09-05. Retrieved 2015-09-05.
  48. "Intent to ship: RC4 disabled by default in Firefox 44". Archived from the original on 2011-01-22. Retrieved 2015-10-18.
  49. "RC4 is now allowed only on whitelisted sites (Reverted)" . Retrieved 2015-11-02.
  50. "Firefox — Notes (44.0) — Mozilla". mozilla.org. 2016-01-26. Archived from the original on 2016-03-04. Retrieved 2016-03-09.
  51. "Bug 1342082 – Disable TLS 1.3 for FF52 Release" . Retrieved 2017-03-29.
  52. 1 2 "Firefox 78.0, See All New Features, Updates and Fixes".
  53. Microsoft (2012-09-05). "Secure Channel". Archived from the original on 2012-08-29. Retrieved 2012-10-18.
  54. Microsoft (2009-02-27). "MS-TLSP Appendix A". Archived from the original on 2013-09-27. Retrieved 2009-03-19.
  55. 1 2 "What browsers only support SSLv2?" . Retrieved 2014-06-19.
  56. 1 2 3 4 "SHA2 and Windows – Windows PKI blog – Site Home – TechNet Blogs". 2010-09-30. Archived from the original on 2014-07-16. Retrieved 2014-07-29.
  57. 1 2 3 4 5 "HTTPS Security Improvements in Internet Explorer 7". Archived from the original on 2013-10-10. Retrieved 2013-10-29.
  58. "TLS Cipher Suites". Microsoft. Archived from the original on 2017-03-13.
  59. "Cipher Suites in TLS/SSL (Schannel SSP) - Win32 apps". Archived from the original on 2015-03-11. Retrieved 2017-07-19.
  60. 1 2 3 4 5 6 MSRC (2015-03-10). Vulnerability in Schannel Could Allow Security Feature Bypass (3046049). Security Bulletins (Technical report). MS15-031. Retrieved 2021-10-24 via Microsoft Docs.
  61. 1 2 3 4 5 6 MSRC (2015-05-12). Vulnerability in Schannel Could Allow Information Disclosure (3061518). Security Bulletins (Technical report). MS15-055. Retrieved 2021-10-24 via Microsoft Docs.
  62. 1 2 "Update to add support for TLS 1.1 and TLS 1.2 in Windows Server 2008 SP2, Windows Embedded POSReady 2009, and Windows Embedded Standard 2009" . Retrieved 2017-07-19.
  63. 1 2 3 4 5 "Protocols in TLS/SSL (Schannel SSP) - Win32 apps". learn.microsoft.com. Retrieved 2022-02-20.
  64. 1 2 "Windows 7 adds support for TLSv1.1 and TLSv1.2 – IEInternals – Site Home – MSDN Blogs". Archived from the original on 2013-12-26. Retrieved 2013-10-29.
  65. Thomlinson, Matt (2014-11-11). "Hundreds of Millions of Microsoft Customers Now Benefit from Best-in-Class Encryption". Microsoft Security. Archived from the original on 2014-11-14. Retrieved 2014-11-14.
  66. "Microsoft security advisory: Update for disabling RC4". Support.microsoft.com. Archived from the original on 11 March 2015. Retrieved 20 February 2022.
  67. 1 2 "Internet Explorer 11 for Windows Server 2012 and Windows Embedded 8 Standard". Microsoft Support. 2019-04-16.
  68. "February 2015 security updates for Internet Explorer". 2015-02-11. Archived from the original on 2015-02-11. Retrieved 2015-02-11.
  69. "Update turns on the setting to disable SSL 3.0 fallback for protected mode sites by default in Internet Explorer 11". Archived from the original on 2015-02-14. Retrieved 2015-02-11.
  70. MSRC (2014-10-14). Vulnerability in SSL 3.0 Could Allow Information Disclosure. Security Advisories (Technical report). 3009008. Retrieved 2021-10-24 via Microsoft Docs.
  71. Pflug, Kyle (2020-03-31). "Plan for change: TLS 1.0 and TLS 1.1 soon to be disabled by default". Windows Blogs.
  72. "KB5017811—Manage Transport Layer Security (TLS) 1.0 and 1.1 after default behavior change on September 20, 2022". Microsoft Support. Retrieved 2023-01-09.
  73. Microsoft (2013-09-24). "IE11 Changes". Archived from the original on 2013-10-30. Retrieved 2013-11-01.
  74. 1 2 3 4 "TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016". Microsoft. 2017-03-21. Archived from the original on 2017-03-30. Retrieved 2017-03-29.
  75. "Internet Explorer 11 has retired and is officially out of support—what you need to know". June 15, 2022.
  76. "Internet Explorer 11 desktop app support ended for certain versions of Windows 10". June 15, 2022.
  77. 1 2 3 4 "What browsers work with Universal SSL". Archived from the original on 2016-03-04. Retrieved 2015-06-15.
  78. "POODLE SSL vulnerability – secure your Windo… – Windows Phone 8 Development and Hacking". XDA Developers. Archived from the original on 2016-09-23.
  79. 1 2 "What TLS version is used in Windows Phone 8 for secure HTTP connections?". Microsoft. Archived from the original on 2016-03-04. Retrieved 2014-11-07.
  80. "Qualys SSL Labs – Projects/User Agent Capabilities: Unknown". Archived from the original on 2017-03-01.
  81. 1 2 "Platform Security". TechNet. Microsoft Docs . 2014-06-25. Retrieved 2021-10-24.
  82. "Release Notes: Important Issues in Windows 8.1 Preview". TechNet. Microsoft Docs . 2013-06-24. Retrieved 2021-10-24.
  83. "W8.1(IE11) vs RC4". Qualys Community. Archived from the original on 2014-11-04. Retrieved 2014-11-04.
  84. Adrian, Dimcev. "Common browsers/libraries/servers and the associated cipher suites implemented". TLS Cipher Suites Project. Archived from the original on 2013-07-20.
  85. "Features". Safari. Apple. 2009-06-10. Archived from the original on 2013-04-20. Retrieved 2009-06-10.
  86. "Curl: Patch to add TLS 1.1 and 1.2 support & replace deprecated functions in SecureTransport". Sweden: haxx.se. Archived from the original on 2017-03-01.
  87. "SSL Server Test: google.co.uk". Archived from the original on February 1, 2017.
  88. "Apple Secures Mac OS X with Mavericks Release". eSecurity Planet. 2013-10-25. Archived from the original on 2014-07-08. Retrieved 2014-06-23.
  89. Ristic, Ivan (2013-09-10). "Is BEAST Still a Threat?". Qualys. Archived from the original on 2014-10-12.
  90. 1 2 Ristić, Ivan (2013-10-31). "Apple enabled BEAST mitigations in OS X 10.9 Mavericks". Archived from the original on 2013-11-07. Retrieved 2013-11-07.
  91. Ristić, Ivan (2014-02-26). "Apple finally releases patch for BEAST". Qualys. Archived from the original on 2014-07-14. Retrieved 2014-07-01.
  92. "About Security Update 2014-005". Apple Support knowledge base article. Apple. Archived from the original on 2014-10-24.
  93. "About the security content of iOS 8.1". Apple Support knowledge base article. Apple. Archived from the original on 2014-10-23.
  94. 1 2 3 "About Security Update 2015-002". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-16. Retrieved 2015-03-09.
  95. 1 2 "About the security content of OS X Mavericks v10.9". Archived from the original on 2014-07-04. Retrieved 2014-06-20.
  96. "User Agent Capabilities: Safari 8/OS X 10.10". Qualys SSL Labs. Archived from the original on 2015-09-06. Retrieved 2015-03-07.
  97. "About the security content of OS X Yosemite v10.10.4 and Security Update 2015-005". Archived from the original on 2015-07-02. Retrieved 2015-07-03.
  98. 1 2 Pauly, Tommy (2019-01-29). "TLS 1.3 in iOS". tls@ietf.org (Mailing list).
  99. 1 2 3 "Technical Note TN2287 – iOS 5 and TLS 1.2 Interoperability Issues". Apple. 2011-10-14. Archived from the original on 2011-09-07. Retrieved 2012-12-10.
  100. Liebowitz, Matt (2011-10-13). "Apple issues huge software security patches". NBC News. Archived from the original on February 15, 2020. Retrieved 2012-12-10.
  101. "Adventures with iOS UIWebviews". MWR Info Security. 2012-04-16. Archived from the original on 2013-03-20. Retrieved 2012-12-10., section "HTTPS (SSL/TLS)"
  102. "Secure Transport Reference". Archived from the original on 2014-06-04. Retrieved 2014-06-23.kSSLProtocol2 is deprecated in iOS
  103. "iPhone 3.0: Mobile Safari Gets Enhanced Security Certificate Visualization". The iPhone Blog. 2009-03-31. Archived from the original on 2009-04-03.
  104. "Projects/User Agent Capabilities: Safari 7/iOS 7.1". Qualys SSL Labs. Archived from the original on 2017-03-13.
  105. "SOAP Request fails randomly on one Server but works on another on iOS7". Stack Overflow. 2013-10-11. Retrieved 2014-01-05.
  106. "User Agent Capabilities: Safari 8/iOS 8.1.2". Qualys SSL Labs. Archived from the original on 2016-03-04. Retrieved 2015-03-07.
  107. "About the security content of iOS 8.2". Apple Support knowledge base article. Apple. Archived from the original on 2015-03-09. Retrieved 2015-03-09.
  108. "About the security content of iOS 8.4". Archived from the original on 2015-07-03. Retrieved 2015-07-03.
  109. "SSLSocket|Android Developers". Archived from the original on 2015-03-18. Retrieved 2015-03-11.
  110. 1 2 3 4 "SSLSocket|Android Developers". Archived from the original on 2016-03-04. Retrieved 2015-12-17.
  111. 1 2 "Android 5.0 Behavior Changes|Android Developers". Archived from the original on 2015-03-09. Retrieved 2015-03-11.
  112. "Android 8.0 Behavior Changes". Archived from the original on 2017-12-01.