Do not commit any private keys to your repo.

This file documents notes about our SSL configuration.

Let's Encrypt is a free certificate authority. This section describes our setup and the renewals process. We run everything as the cloud user to minimize the need for root access.

Snap!Cloud runs on 2 servers right now, with 6 total domains. Those paths are "hard-coded" for simplicity, but should be easy to adapt.

• ~/lets-encrypt This stores the LetsEncrypt config and certs.
• A cron job checks daily if the certs need to be renewed
• Renewed certs are copied in snapCloud/certs/ and the server is restarted.
• bin/setup-lets-encrypt.sh will do most of the setup.
• bin/renew-certs.sh is the nightly script.

mkdir ~/lets-encrypt/
certbot certonly --webroot -w /home/cloud/snapCloud/html/ -d snap-cloud.cs10.org
--config-dir=lets-encrypt --logs-dir=lets-encrypt --work-dir=lets-encrypt

After this, certbot will give you the name of the certs it generated. Copy them to the certs/ folder and update the file paths as necessary.

First, generate a CSR and key using openssl. Use the EECS website to request a new cert. (You need an EECS account to do this; at least on Snap! team member should be able to do this.)

When generating a cert from UC Berkeley, there are many possible cert types. We need to concatenate the proper files for nginx to be able to read them. You need to include the individual cert along with the intermediate certs in a single file.

cp cloud_snap_berkeley_edu_cert.cer cloud_snap_berkeley_edu_combined.cer
echo '' >> cloud_snap_berkeley_edu_combined.cer
cat cloud_snap_berkeley_edu_interm-reversed.cer >> cloud_snap_berkeley_edu_combined.cer

The concatenation combined the cert for the main domain, i.e. cloud.snap.berkeley.edu along with certs for the intermediate domains, i.e. snap.berkeley.edu and berkeley.edu. Combining the certs helps to improve the speed of making the SSL handshake because we have turned on "OCSP Stapling" in the nginx config. Otherwise, including the intermediate certs is a best practice, but not required.

Use the combined file as the ssl_certificate in the nginx configuration.

Perfect Forward Secrecy is an extension to SSL/TLS that aids in protecting connections in the event of a private key being comprised. To do enable this, you need generate an additional key on each server. Generating this takes a few minutes, but it easy. Save this to the certs/ directory, too.

openssl dhparam -out dhparam.cert 4096