Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
userdoc:tt_asterisk-fop2-ssl [2020/03/18 05:32] mkeuter [SSL/HTTPS with FOP2 (Self-Signed Certificate)] |
userdoc:tt_asterisk-fop2-ssl [2022/02/10 10:11] (current) 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 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 | + | !!Tip ->!! For Firefox |
- | !!Tip ->!! For Firefox 74 you need to re-enable TLS 1.0 +1.1 as a workaround. | + | !!Tip ->!! For Firefox 74 you might need to [[https:// |
+ | |||
+ | Since version **2.31.28** (mid 2020) FOP2 does finally support **TLS 1.2** (within AstLinux 1.3.10 or later)! | ||
===== Mac OS X ===== | ===== 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 | * Firefox 3.6 (10.5) works fine with HTTPS | ||
* Chrome works fine with HTTPS | * Chrome works fine with HTTPS | ||
Line 48: | Line 50: | ||
===== Windows ===== | ===== 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 | * Chrome works fine with HTTPS | ||
* IE8 (XP SP3) + IE10 (Win7 x86) works fine with HTTPS | * IE8 (XP SP3) + IE10 (Win7 x86) works fine with HTTPS |