Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_asterisk-fop2-ssl [2018/05/26 04:20]
droemel [Windows]
+++ userdoc:tt_asterisk-fop2-ssl [2022/02/10 10:11]
mkeuter [SSL/HTTPS with FOP2 (Self-Signed Certificate)]
@@ Line 34: / Line 34: @@
 !!Tip ->!! For any browser: You need to accept an URL exception for the certificate because it's self-signed (for the hostname or the IP).
-!!Tip ->!! For Firefox (v22+): You need to add a separate URL exception for "https://hostname:4445/fop2/" and then again\\ connect to "https://hostname/fop2/" (do the same for the IP if no hostname).
+!!Tip ->!! For Firefox 22+: You need to add a separate URL exception for "https://hostname:4445/fop2/" and then again\\ connect to "https://hostname/fop2/" (do the same for the IP if no hostname).
+!!Tip ->!! For Firefox 74 you might need to [[https://hacks.mozilla.org/2020/02/its-the-boot-for-tls-1-0-and-tls-1-1/|re-enable TLS 1.0 +1.1]] as a workaround.
+Since version 2.31.28 (mid 2020) FOP2 does finally support **TLS 1.2** (within AstLinux 1.3.10 or later)!
 ===== Mac OS X =====
-  * Safari 5, 6 + 9 (10.5-10.12) work fine with HTTPS
+  * Safari 5-13 (10.5-10.13) work fine with HTTPS
-  * Firefox 22+ (10.6-10.12) works fine with the above workaround
+  * Firefox 22+ (10.6-10.13) works fine with the above workaround(s)
   * Firefox 3.6 (10.5) works fine with HTTPS
   * Chrome works fine with HTTPS
@@ Line 46: / Line 50: @@
 ===== Windows =====
-  * Firefox 22+ (XP SP3, Win7 x86, Win10) works fine with the above workaround
+  * Firefox 22+ (XP SP3, Win7 x86, Win10) works fine with the above workaround(s)
   * Chrome works fine with HTTPS
   * IE8 (XP SP3) + IE10 (Win7 x86) works fine with HTTPS