Create Root CA (self-signed):
Let's have a look at the options in detail:
- x509 identifies that a certificate is required, rather than just a certificate request (see below).
- days 30000 sets the certificate to expire in a 30000 days. You may want to extend this period. Make a note of the expiry date so that you can renew it when necessary!
- sha1 specifies that SHA1 encryption should be used.
rsa:2048 sets the key as 2048 bit RSA.
- nodes specifies no passphrase.
- keyout and -out specify where to store the certificate and key. The key should be root-readable only; the certificate can be world-readable, and must be readable by the user that Apache runs as.
- subj flag sets the company name, department name, and the web site address. If you leave these out, you'll be prompted for them. The CN must be the same as the address of your web site, otherwise the certificate won't match and users will receive a warning when connecting. Make sure you don't use a challenge password.
Create it :
sudo openssl req -x509 -nodes -newkey rsa:2048 -sha1 -keyout rootkey.key -out rootca.crt -passin pass:root -days 30000 -subj "/C=DU/ST=Dubai/L=TownCenter/O=AmesCom/CN=AmesCom Int" -config openssl.cnf.my
Encrypt the key manually :
key is not encrypted because of -nodes option , so we encrypt it manually :
sudo cp rootkey.key rootkey.key.org
sudo openssl rsa -in rootkey.key.org -out rootkey.key
Test it :
for testing immediately , you may follow two ways :
openssl x509 -text -noout -in rootca.crt
or examine its contents on browser :
cp rootca.crt /var/www/html/
from browser ask for address :
http://yourserverdomain/rootca.crt
Now you can create certificate requests and sign them with this self-signed certificate
Just add -sha1
or -sha256
to the end of your request command to specify which message digest algorithm to use. See OpenSSL's Documentation for a list of valid signing algorithms.
For example (SHA-1):
openssl req -new -key server.key -out www.domain.server.csr -sha1
OR (SHA-256):
openssl req -new -key server.key -out www.domain.server.csr -sha256
Best Answer
You lack entropy - the randomness the server needs to generate the key.
Try moving the mouse, or hitting random keys on the keyboard - you should see progress when you do.
Alternatively, use this one-liner to generate a self-signed certificate with less steps:
openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout server.key -out server.crt