One of the most common forms of cryptography today is public-key cryptography. Public-key cryptography uses a public key and a private key. The system works by encrypting information using the public key. The information can then only be decrypted using the private key.

A common use for public-key cryptography is encrypting application traffic using a Secure Socket Layer (SSL) or Transport Layer Security (TLS) connection. One example: configuring Apache to provide HTTPS, the HTTP protocol over SSL/TLS. This allows a way to encrypt traffic using a protocol that does not itself provide encryption.

A certificate is a way to distribute a public key and other information about a server and the organisation responsible for it. Certificates can be digitally signed by a Certification Authority (CA), which is a trusted third party that has confirmed the information contained in the certificate is accurate.

Types of certificates

To set up a secure server using public-key cryptography, in most cases, you send your certificate request (including your public key), proof of your company’s identity, and payment to a CA. The CA verifies the certificate request and your identity, and then sends back a certificate for your secure server. Alternatively, you can create your own self-signed certificate.

Self-signed certificates should not be used in most production environments.

Continuing the HTTPS example, a CA-signed certificate provides two important capabilities that a self-signed certificate does not:

  • Browsers will (usually) automatically recognise the CA signature and allow a secure connection to be made without prompting the user.

  • When a CA issues a signed certificate, it is guaranteeing the identity of the organisation providing the web pages to the browser.

Most software supporting SSL/TLS has a list of CAs whose certificates they automatically accept. If a browser encounters a certificate whose authorising CA is not in the list, the browser asks the user to either accept or decline the connection. Also, other applications may generate an error message when using a self-signed certificate.

The process of getting a certificate from a CA is fairly straightforward. A quick overview is as follows:

  1. Create a private and public encryption key pair.

  2. Create a certificate signing request based on the public key. The certificate request contains information about your server and the company hosting it.

  3. Send the certificate request, along with documents proving your identity, to a CA. We cannot tell you which certificate authority to choose. Your decision may be based on your past experiences, or on the experiences of your friends or colleagues, or purely on monetary factors.

    Once you have decided upon a CA, you need to follow the instructions they provide on how to obtain a certificate from them.

  4. When the CA is satisfied that you are indeed who you claim to be, they send you a digital certificate.

  5. Install this certificate on your secure server, and configure the appropriate applications to use the certificate.

Generate a Certificate Signing Request (CSR)

Whether you are getting a certificate from a CA or generating your own self-signed certificate, the first step is to generate a key.

If the certificate will be used by service daemons, such as Apache, Postfix, Dovecot, etc., a key without a passphrase is often appropriate. Not having a passphrase allows the services to start without manual intervention, usually the preferred way to start a daemon.

This section will cover generating a key both with or without a passphrase. The non-passphrase key will then be used to generate a certificate that can be used with various service daemons.

Running your secure service without a passphrase is convenient because you will not need to enter the passphrase every time you start your secure service. But it is insecure – a compromise of the key means a compromise of the server as well.

To generate the keys for the Certificate Signing Request (CSR) run the following command from a terminal prompt:

openssl genrsa -des3 -out server.key 2048

Generating RSA private key, 2048 bit long modulus
e is 65537 (0x10001)
Enter pass phrase for server.key:

You can now enter your passphrase. For best security, it should contain at least eight characters. The minimum length when specifying -des3 is four characters. As a best practice it should also include numbers and/or punctuation and not be a word in a dictionary. Also remember that your passphrase is case-sensitive.

Re-type the passphrase to verify. Once you have re-typed it correctly, the server key is generated and stored in the server.key file.

Now create the insecure key, the one without a passphrase, and shuffle the key names:

openssl rsa -in server.key -out server.key.insecure
mv server.key server.key.secure
mv server.key.insecure server.key

The insecure key is now named server.key, and you can use this file to generate the CSR without a passphrase.

To create the CSR, run the following command at a terminal prompt:

openssl req -new -key server.key -out server.csr

It will prompt you to enter the passphrase. If you enter the correct passphrase, it will prompt you to enter ‘Company Name’, ‘Site Name’, ‘Email ID’, etc. Once you enter all these details, your CSR will be created and it will be stored in the server.csr file.

You can now submit this CSR file to a CA for processing. The CA will use this CSR file and issue the certificate. Alternatively, you can create self-signed certificate using this CSR.

Creating a self-signed certificate

To create the self-signed certificate, run the following command at a terminal prompt:

openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

The above command will prompt you to enter the passphrase. Once you enter the correct passphrase, your certificate will be created and it will be stored in the server.crt file.

If your secure server is to be used in a production environment, you probably need a CA-signed certificate. It is not recommended to use self-signed certificates in production environments.

Install the certificate

You can install the key file server.key and certificate file server.crt, or the certificate file issued by your CA, by running following commands at a terminal prompt:

sudo cp server.crt /etc/ssl/certs
sudo cp server.key /etc/ssl/private

Now configure any applications that have the ability to use public-key cryptography so that they use the certificate and key files. For example, Apache can provide HTTPS, Dovecot can provide IMAPS and POP3S, etc.

Certification Authority

If the services on your network require more than a few self-signed certificates it may be worth the additional effort to setup your own internal Certification Authority (CA). Using certificates signed by your own CA allows the various services using the certificates to easily trust other services using certificates issued from the same CA.

First, create the directories to hold the CA certificate and related files:

sudo mkdir /etc/ssl/CA
sudo mkdir /etc/ssl/newcerts

The CA needs a few additional files to operate; one to keep track of the last serial number used by the CA (each certificate must have a unique serial number), and another file to record which certificates have been issued:

sudo sh -c "echo '01' > /etc/ssl/CA/serial"
sudo touch /etc/ssl/CA/index.txt

The third file is a CA configuration file. Though not strictly necessary, it is convenient when issuing multiple certificates. Edit /etc/ssl/openssl.cnf, and in the [ CA_default ], change:

dir             = /etc/ssl              # Where everything is kept
database        = $dir/CA/index.txt     # database index file.
certificate     = $dir/certs/cacert.pem # The CA certificate
serial          = $dir/CA/serial        # The current serial number
private_key     = $dir/private/cakey.pem# The private key

Next, create the self-signed root certificate:

openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.pem -days 3650

You will then be asked to enter the details about the certificate. Next, install the root certificate and key:

sudo mv cakey.pem /etc/ssl/private/
sudo mv cacert.pem /etc/ssl/certs/

You are now ready to start signing certificates. The first item needed is a Certificate Signing Request (CSR) – see the “Generating a CSR” section above for details. Once you have a CSR, enter the following to generate a certificate signed by the CA:

sudo openssl ca -in server.csr -config /etc/ssl/openssl.cnf

After entering the password for the CA key, you will be prompted to sign the certificate, and again to commit the new certificate. You should then see a somewhat large amount of output related to the certificate creation.

There should now be a new file, /etc/ssl/newcerts/01.pem, containing the same output. Copy and paste everything beginning with the -----BEGIN CERTIFICATE----- line and continuing through to the ----END CERTIFICATE----- lines to a file named after the hostname of the server where the certificate will be installed. For example mail.example.com.crt, is a nice descriptive name.

Subsequent certificates will be named 02.pem, 03.pem, etc.

Replace mail.example.com.crt with your own descriptive name.

Finally, copy the new certificate to the host that needs it, and configure the appropriate applications to use it. The default location to install certificates is /etc/ssl/certs. This enables multiple services to use the same certificate without overly complicated file permissions.

For applications that can be configured to use a CA certificate, you should also copy the /etc/ssl/certs/cacert.pem file to the /etc/ssl/certs/ directory on each server.

Further reading

  • The Wikipedia HTTPS page has more information regarding HTTPS.

  • For more information on OpenSSL see the OpenSSL Home Page.

  • Also, O’Reilly’s “Network Security with OpenSSL” is a good in-depth reference.

1 Like

A question/comment - should the server certificate end up in /etc/ssl/certs This path contains the trusted ca certs, and would be subject to having the c_rehash command run against everything within the /etc/ssl/certs path to update if adding a private CA to the set.

It would seem to make better sense to have an /etc/ssl/public or something else… or have /etc/ssl/certs be /etc/ssl/cacerts to disambiguate with an /etc/ssl/certs for for the signed (or selfsigned) certificate file for the host?

Or am I missing a finer point to gloming the issued (Ca signed) or self-signed certificate for the host, into the same place as the CA certificates?

Server certs should not be in /etc/ssl/certs. That’s for CAs.

I suspect this “trend” of putting server certs in that directory started because many people generate self-signed certs for testing (which are essentially dummy CAs), and need the client (from the same host many times) to trust it. Even then, the right place is /usr/local/share/ca-certificates and run update-ca-certificates after that. It will take care of creating a symlink in /etc/ssl/certs and running c_rehash.

1 Like

This passage seems then to be the point where things go wrong then, in that it instructs the end user to copy their selfsigned cert into that path (when generating one). It would be nice to establish (and document) the handling in a common place of CA signed certificates to end up in. The document goes on to discuss selfsigned CA procedures as well, instantiating a “/etc/ssl/newcert” path, but that discussion is for generating certs for multiple hosts beyond the local host scenario we are discussing.

I realize admin’s can put the server cert and key anywhere on the filesystem, it just seems to be a missed opportunity to not fully define the “private CA” signed certificate handling scenario, and having a “home” for it within that space.

Agreed. Could you please take a look at what I did for the ldap + tls topic, in the part where the generated certificates are copied to their final places? See what you think?

We should probably correctly define this here instead of repeating it over and over for each service that supports TLS/SSL.

@ahasenack - Thank you - I came to this page trying to figure out how to give a linux application access to read the SSL Certificate private key and Cert - I found that not here but at the link you posted above. Appreciate that. I would like to add to your writeup that one of those packages, either “gnutls-bin” or “ssl-cert” must be installed in order to create the “ssl-cert” group in the /etc/groups file that should be used to set the permissions on the directory where the hosts ssl certs that processes like apache, Postgres, etc need in order to start up

Appreciate the good documentation !


Great documentation thank you! I think there may be one small error, this has you create the /etc/ssl/newcerts directory, but I do not see any configuration that specifies that as the new certs directory for openssl. I believe your [ ca_default ] section should be updated with the line new_certs_dir = $dir/newcerts Thank you!

Hi @afewell,

While you stand correct, the ca_default section for a default openssl installation already contains that entry for new_certs_dir. Do note that this docs only suggest that the user should make specific changes to that configuration section (instead of re-writing the whole section or configuration file).