10-07-2006 10:05 AM
- SSL Server Supports Weak Encryption
- SSL Server Uses Weak Encryption
- SSL Server Has SSLv2 Enabled
- SSL Certificate - Signature Verification Failed
- SSL Certificate - Self-Signed Certificate
- SSL Certificate - Subject Common Name Does Not Match Server FQDN
I would like to know on how to disable SSL2 and only enable SSL3 and how to solve a SSL certificate problem.
10-07-2006 01:29 PM
It is the revision history for thr HP System Management Homepage. If you scroll down you will see in the revision notes that starting with revision 18.104.22.168, that was released in January, default disabled SSLv2. You have the ability to enable it with a switch if you wish starting with that release, but it is not enabled unless you do that.
If you have that revision or later you should not have a problem. You will need to be specific as to what your certificate issue is.
You may want to look at this HPSIM security white paper: http://h10018.www1.hp.com/wwsolutions/misc/hpsim-h
It discusses how to implement a strong security model, it may or may not satisfy your Quayls report as I don't know all of what it looks for. Good Luck,
10-08-2006 07:17 PM
I try to get a certificate from Windows 2003 Certificate however, it still report the Common Name does not match server FQDN.
Let say, the server FQDN is AV-MBX002.SG.INTERNAL.COM but the certificate subject name is AV-MBX002. How can I request a cert with a FQDN.
03-19-2007 07:09 AM
03-19-2007 12:38 PM
09-10-2012 05:22 AM
Have you tried the following HowTo:
This explains that you need to use the alternative name for the FQND.