• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Disabling SSLv2 for PCI compliance

A

akiva

Guest
Hi

I've RTFM. I've googled. I've tried every possible change to every possible config file suggested.

And SSLv2 stayed active (according to our PCI security check)

Anyone have any suggestions?

TIA
 
I have the same problem.. have you had any luck fixing this?
 
ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM

in

/var/qmail/control/tlsserverciphers

and

var/qmail/control/tlsclientciphers


then restart Qmail
 
Originally posted by McMac
ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM
in
/var/qmail/control/tlsserverciphers
and
var/qmail/control/tlsclientciphers
then restart Qmail

Thanks -- the two files don't exist -- I assume I can just create them? What permissions do I need to assign?

And how do I restart qmail? the qmail FAQ gives a method, but it didn't seem to work for me...

thanks
 
And how do I restart qmail? the qmail FAQ gives a method, but it didn't seem to work for me...

You can restart qmail using Plesk under Server -> Service Management. I don't know what distro you're running, but I can use 'service qmail restart' on CentOS.
 
Thanks -- that did it

(I had been trying from the command line...)
 
The quickest fix we found was using hackersafe/scan alert.

Ours passed no issues
 
Back
Top