Facebook
Twitter
C
cah4i
Guest
I've read previous posts on this but am still having some weird issues.
My /usr/local/psa/admin/conf/httpsd.custom.include file contains
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!NULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:-LOW:+SSLv3:+TLSv1:-SSLv2:+EXP:+eNULL
Nevertheless, after restarting psa, using openssl s_client -connect mydomain.com:8443 -ssl2 is still negotiating an ssl2 connection.
BUT if I change the port in my httpsd.conf to 8445 and run the above command with port obviously changed, ssl2 negotiation fails and sslv3 works (ie my directives are being applied). When I went to logon to the admin panel on 8445, I logged in successfully but got a license agreement screen which scared me so I went back to 8443. So any ideas on what is going on here? I have read about people changing the admin ssl port successfully. Do I need to worry about the license agreement screen? I was expecting to just see the normal screen on the new port. I don't want to blow away my configs. Any help would be immensely appreciated. Thanks!
My /usr/local/psa/admin/conf/httpsd.custom.include file contains
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!NULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:-LOW:+SSLv3:+TLSv1:-SSLv2:+EXP:+eNULL
Nevertheless, after restarting psa, using openssl s_client -connect mydomain.com:8443 -ssl2 is still negotiating an ssl2 connection.
BUT if I change the port in my httpsd.conf to 8445 and run the above command with port obviously changed, ssl2 negotiation fails and sslv3 works (ie my directives are being applied). When I went to logon to the admin panel on 8445, I logged in successfully but got a license agreement screen which scared me so I went back to 8443. So any ideas on what is going on here? I have read about people changing the admin ssl port successfully. Do I need to worry about the license agreement screen? I was expecting to just see the normal screen on the new port. I don't want to blow away my configs. Any help would be immensely appreciated. Thanks!
