- Trusted : No NOT TRUSTED
- IE 6 / XP No FS 1 No SNI 2 : Protocol or cipher suite mismatch : Fail3
- Fail3 They say “Only first connection attempt simulated. Browsers tend to retry with a lower protocol version.” My SSL server doesn’t accept lower protocols, but it’s no problem for me.
As above I have nothing to be done about Reds.
- Prefix handling : Not valid for “www.o6asan.com” :CONFUSING
- Signature algorithm : SHA1withRSA : WEAK
- Chain issues : Contains anchor Ivan Ristić replied about “Chain issues Contains anchor”. So I ignore the message.
- Not in trust store
- Downgrade attack prevention : No, TLS_FALLBACK_SCSV not supported
- Forward Secrecy : With some browsers
As above I have something to be done about 1, 2, 5 and 6. First I handle 5 and 6 because I need to re-create a new certificate for 1 and 2.
- I update Apache 2.4.10 (httpd-2.4.10-win32-VC11.zip) to October 20 version. Because it was built with openssl-1.0.1j which supported TLS_FALLBACK_SCSV.
- I uncommented SSLHonorCipherOrder on and changed SSLCipherSuite Directive value in the httpd-ssl.conf.
EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384
EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256
EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP
!PSK !SRP !DSS
Ref : Configuring Apache, Nginx, and OpenSSL for Forward Secrecy
IF your server should support some mobile OS/browser or legacy ones, you need more additional configuration. But the above is enough to my server.
After them the test gives me “Downgrade attack prevention : Yes, TLS_FALLBACK_SCSV supported” and “Forward Secrecy : Yes (with most browsers) ROBUST”.
Second I handle 1 and 2.
The 1 is caused by my self-sighed certificate only has o6asan.com as its Common Name. So I have to create a new certificate supporting both o6asan.com and www.o6asan.com. But there is a problem that I want to use only one IP address for my SSL server. Nowadays we have the solution for this issue that is called SNI(Server Name Indication) though all OS/browser haven’t supported it yet. I can use a wildcard certificate or SAN for SNI. I use SANs because I don’t want to allow my SSL server to accept all sub domains though I can restrict them by Apache configuration.
The 2 is caused by my creation of the certificate by OpenSSL default, which is set to use SHA1. So I’ll use
default_md = sha256 for the new certificate.
I copy the file openssl.cnf(← this is the default name) from Apche24\conf folder to c:\openssl-1.0.1x-winxx\ssl(← this is the default location) and customize like the followings.
- Change values and uncomment a line.
dir = ./demoCA—->>
dir = X:/demoCA
default_crl_days = 30—->>
default_crl_days = 365
default_md = default—->>
default_md = sha256
default_bits = 1024—->>
default_bits = 2048
# req_extensions = v3_req—->>
req_extensions = v3_req
- Adding lines.
subjectAltName = @alt_namesto [ v3_req ] area.
[ alt_names ]to just before [ v3_ca ] area.
DNS.1 = example.com
DNS.2 = www.example.com
You can add your domains, like DNS.1, DNS.2, DNS.3, ….
- If you make a client certificate, add the followings to the end of the openssl.cnf.
[ ssl_client ]
basicConstraints = CA:FALSE
nsCertType = client
keyUsage = digitalSignature, keyEncipherment
extendedKeyUsage = clientAuth
nsComment = "OpenSSL Certificate for SSL Client"
Now I’ll create new certificate. (Ref : WordPress: Administration Over SSL #1)
- ||Create myCA||
- Make myCA folder at X:/
- Make two folders and a file named private, newcerts and index.txt in the myCA.
- Run cmd.exe as Administrator
echo 01 > serial
openssl req -new -keyout private\cakey.pem -out careq.pem
openssl ca -selfsign -in careq.pem -extensions v3_ca -out cacert.pem
copy cacert.pem (Drive_SV):\Apache24\conf\ssl.crt
copy cacert.pem my_ca.crt
Note) (Drive_SV) is a partition for server components on my home server PC.
- ||Create Server Cert||
openssl genrsa -out server.key 2048
openssl req -new -out server.csr -key server.key
- Check multiple SANs in the CSR (Can you see ‘Subject Alternative Name’ area in it?)
openssl req -text -noout -in server.csr
openssl ca -in server.csr -out server.crt -extensions v3_req
copy server.key cp_server.key
openssl rsa <cp_server.key> server.key
copy server.key (Drive_SV):\Apache24\conf
copy server.crt (Drive_SV):\Apache24\conf
- ||Create Client Cert||
openssl req -new -keyout client.key -out client.csr
openssl ca -policy policy_anything -extensions ssl_client -in client.csr -out client.crt
openssl pkcs12 -export -in client.crt -inkey client.key -out clientcert.p12
I have a self-sighed certificate with SANs and SHA256 now. Mission complete!!