• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PCI Complience SSLv3 for Plesk Control Panel

P

prussell

Guest
I recently upgraded from the Plesk 8.1 version on Windows to 9.5. Version 8.1 was running in IIS. The new version of Plesk is running from Apache. I am trying to pass PCI Scan and the last problem I have is a SSLv2 vulnerability. I have already made the adjustments for IIS in the registry, but not for tcp/8443 which is running from apache.

How do I configure Apache to only use SSLv3.

Thanks
Patrick
 
Hi IgorG

Yes, I have read and made the modifications for a Windows Server according to the guide. The problem is that Plesk Panel is now using Apache instead of IIS. Even though I have disabled PCT1 and SSLv2 per the Windows section of the guide, the Plesk Panel & Apache is still using SSLv2. The guide does not cover PCI Complience for Apache on Windows.

I can't run the resolver described in the Linix/FreeBSD section of the guide. Is there a way to do it manually?

Thanks
Patrick
 
Yes that would be an option.

Thanks Igor

Regards
Patrick
 
Back
Top