RichardW
-
Posts
25 -
Joined
-
Last visited
Kudos
-
RichardW received kudos from Peter Randziak in Question over Eset Updates via proxy and Port 80
Thanks very much for looking into this with the developers. I admit the use case is kind of unusual in that I'm not using apache for caching. But unfortunately the PCI auditors tend to be quite strict over what is allowed when it comes to non SSL ports.
Typically allowing port 80 requires a lot of paperwork is part of the reason, even though the proxy limits access to certain hosts and the updates are signed.
-
RichardW received kudos from Gtt in Query over TLS1.0
Hi,
we're currently trying to use "ESET File Security for Servers" and "ESET Security Management Center" within a PCI environment
one of the requirements of this is to avoid TLS1.0 and use TLS1.1 or TLS1.2 instead.
One of the things that showing up on the nessus port scan is that ESET Security Management Center is using TLS1.0 on ports 443 / 2222 / 2223
I have TLS1.0 disabled at the operating system level (within the registry) but is there any way to get ESET Security Management Center to use TLS1.1 or TLS1.2? (to disable the use of TLS1.0)
-
RichardW received kudos from Peter Randziak in Query over TLS1.0
Thanks
I just needed to change
sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" to
sslEnabledProtocols="TLSv1.1,TLSv1.2" within C:\Program Files\Apache Software Foundation\apache-tomcat-7.0.92\conf\server.conf