You would think by now in 2017, we would have poodle figured out.
In /etc/httpd/conf/plesk.conf.d/server.conf the SSL protocols are wrong. I fix it, but it doesn't survive the next time plesk writes to that file!
WHY does plesk insist on making me vulnerable??
I have seen the warning that says....
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
But it doesn't say where else to fix this. Where is...
Plesk keeps reintroducing poodle vulnerability
In /etc/httpd/conf/plesk.conf.d/server.conf the SSL protocols are wrong. I fix it, but it doesn't survive the next time plesk writes to that file!
WHY does plesk insist on making me vulnerable??
I have seen the warning that says....
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
But it doesn't say where else to fix this. Where is...
Plesk keeps reintroducing poodle vulnerability