Self-Signed SSL Certificates

Instructions adapted from http://www.tc.umn.edu/~brams006/selfsign.html.

Rather than paying for an SSL certificate from a signing authority, we'll use a self-signed certificate to provide encryption in Apache. The client's web browser will prompt them to whether the certificate should be accepted or not - if that is going to be a problem, then you'll need to get a certificate from a recognized signing authority.

Create a directory, readable only by root to hold our working files:

Generate your own Certificate Authority (CA)
The first thing we need to do is establish ourselves as a CA
Create an RSA Private Key;

Then generate a Certificate Signing Request. You will be prompted for a various information. One of the prompts will be for "Common Name" - this should be the FQDN of the server you are protecting. However, it should also be different from the server key's CN, so add " CA" to the end of this one.

You will be prompted for a variety of information:

Generate a server key and request for signing (csr).
This time, when prompted for a Common Name, use the FQDN of the server you want to protect. It should match the FQDN or IP address you specify in httpd.conf or ssl.conf for your server. If it doesn't, client browsers will give a "domain mismatch" message when they go to your server. The "challenge password" and "optional company name" can be left blank.
For a wildcard certficate, use *.domain.com for the server name.

Again, you'll have a variety of information to provide:

Sign the cerficate signing request (csr) with the self-created certificate authority (CA)
Note that 365 days is used here. After a year you'll need to do this again.
The serial number of the signed server certificate is set to "01". Each time you do this, especially if you do this before a previously-signed certificate expires, you'll need to change the serial key to something else. If you don't someone visiting your site who has a cached version of your certificate will get an error message.
The following command It takes your signing request (csr) and makes a one-year valid signed server certificate (crt) out of it. In doing so, we need to tell it which Certificate Authority (CA) to use, which CA key to use, and which Server key to sign.

If you want to inspect the components of the key:

Need to know the serial of your current key?

Make a server.key for Apache that doesn't require a password
Here we create an insecure version of the server.key that will be used for when Apache starts, and will not require a password with every restart of the web server. But keep in mind that while this means you don't have to type in a password when restarting Apache (or worse -- coding it somewhere in plaintext), it does mean that anyone obtaining this insecure key will be able to decrypt your transmissions. Guard it for permissions VERY carefully.

Copy the files into position

If you want to use this same certificate with your mail server?:
Order in the pem file matters: https://www.digicert.com/ssl-support/pem-ssl-creation.htm

• Qmail
  (Other method for SMTP-SSL: http://qmail.jms1.net/smtp-service.shtml )
  cat server.key server.crt>/var/qmail/control/servercert.pem
• Courier-IMAP
  
  cat server.key server.crt>/usr/local/share/imapd.pem
• Dovecot
  
  cat server.key server.crt > /usr/local/etc/dovecot.pem