I have been trying to force TLSv1.2 for Flashphoner manager (port 8888) and for streaming certificate (port 8443). I tried to adjust it by changing the following directive in wcs-core.properties:
from
-Djdk.tls.client.protocols = “TLSv1,TLSv1.1,TLSv1.2”
to
-Djdk.tls.client.protocols = “TLSv1.2”
Once I restart webcallserver, flashphoner manager logs even show that the manager is started with
-Djdk.tls.client.protocols = “TLSv1.2”
option
However, vulnerability test of my server still shows that ports 8443 and 8888 allow TLSv1.0 connection which is not very secure
and also I can access Flashphoner manager using old Windows Safari browser, which should not be possible because that browser doesn’t support TLSv1.2 and must use some older version like TLSv1.0.
Is it even possible to force TLSv1.2 or at least TLSv1.1 on Flashphoner web call server 5.1 by changing this directive or can it be forced in some other configuration file?
from
-Djdk.tls.client.protocols = “TLSv1,TLSv1.1,TLSv1.2”
to
-Djdk.tls.client.protocols = “TLSv1.2”
Once I restart webcallserver, flashphoner manager logs even show that the manager is started with
-Djdk.tls.client.protocols = “TLSv1.2”
option
However, vulnerability test of my server still shows that ports 8443 and 8888 allow TLSv1.0 connection which is not very secure
and also I can access Flashphoner manager using old Windows Safari browser, which should not be possible because that browser doesn’t support TLSv1.2 and must use some older version like TLSv1.0.
Is it even possible to force TLSv1.2 or at least TLSv1.1 on Flashphoner web call server 5.1 by changing this directive or can it be forced in some other configuration file?