• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Why SSLv2 and SSLv3?

Azurel

Silver Pleskian
In nginx /etc/nginx/plesk.conf.d/server.conf I found
ssl_protocols SSLv2 SSLv3 TLSv1 TLSv1.1 TLSv1.2;

Why? See here: http://disablessl3.com/ or here https://blog.qualys.com/ssllabs/2014/10/15/ssl-3-is-dead-killed-by-the-poodle-attack


Maybe that helps here too:
https://mozilla.github.io/server-side-tls/ssl-config-generator/

SSLLabs give you Grade C for using SSLv3
This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C.

From Apache Config:
Default: SSLProtocol all -SSLv3 (up to 2.4.16: all)

From nginx Config:
Default: ssl_protocols TLSv1 TLSv1.1 TLSv1.2;


SOLUTION:

http://kb.odin.com/en/123160

for Plesk 12.5

For all sites in Plesk 12.0 for Linux:

# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` psa > psa_backup.sql
# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
mysql> insert into misc values('disablesslv3', 'true');

Then, reconfigure Apache and Nginx:

# /usr/local/psa/admin/bin/httpdmng --reconfigure-all
 
Last edited:
Hi Azurel,

not all SSLv2/SSLv3 - protocols have a protocol weaknesses, that's why it is very much recommended and wise, to define your ciphers lists carefully!
If you intend to remove all SSLv3 ciphers, you remove as well some TLSv1 ciphers and if you remove all SSLv2 ciphers as well, you will now only support TLSv1.2 - which is a bad idea, because you will experience quite a lot of issues now. ;)

Pls. read more about ciphers and it's usage, as for example at: => https://www.openssl.org/docs/manmaster/apps/ciphers.html
 
Back
Top