Changes between Version 11 and Version 12 of mosh-x509

Timestamp:

Aug 15, 2016, 1:29:47 PM (9 years ago)

Author:

Jamie McClelland

Comment:

--

mosh-x509

@@ -11 +11 @@
  * /etc/ssl/HOST.mayfirst.org.crt: contains both the X.509 End Entity (EE) certificate and any required intermediary certificates (server (EE) cert first, intermediary second)
  * /etc/ssl/private/HOST.mayfirst.org.pem: contains the key file, the EE certificate, and any required intermediary certificates (in that order)
- * /etc/ssl/HOST.mayfirst.org.csr: certificate signing request (CSR), used to request a new certificate when the existing one expires
+ 
+These files are all symlinks to the actual files in the /etc/letsencrypt/live hierarchy.
 
-On a new server, puppet will generate a 2048-bit RSA key as /etc/ssl/private/HOST.mayfirst.org.uncertified.key and /etc/ssl/HOST.mayfirst.org.csr. In addition /etc/ssl/HOST.mayfirst.org.crt is created as a symlink to /etc/ssl/cert/ssl-cert-snakeoil.pem and /etc/ssl/private/HOST.mayfirst.org.pem is a symlink to /etc/ssl/private/ssl-cert-snakeoil.key. These symlinks are created to ensure that services that rely on them are properly started.
+On a new MOSH server [wiki:configure-mosh-x509 configured to use letsencrypt], puppet will generate all needed files and symlinks
 
-A sysadmin is required to submit the CSR to a [wiki:ordering-cartel-x509-certificates company that provides x509 certs]. Once the sysadmin has the certificate, s/he should replace the symlinked files with the appropriate files:
- * replace the /etc/ssl/HOST.mayfirst.org.crt symlink with a file containing the actual certificate and any intermediary certificates
- * delete the /etc/ssl/private/HOST.mayfirst.org.pem symlink
- * move /etc/ssl/private/HOST.mayfirst.org.uncertified.key to /etc/ssl/private/HOST.mayfirst.org.pem
- * append both the certificate and any intermediary certificates to /etc/ssl/private/HOST.mayfirst.org.pem
- * restart apache2, postfix, courier-imap-ssl and courier-pop-ssl
-
-If, for some reason, the MOSH server is using a common name other than HOST.mayfirst.org (e.g. secure.critpath.org is used instead of didier.mayfirst.org), then the files should be named after the common name (secure.critpath.org) and HOST.mayfirst.org should be a symlink to the actual file. This naming convention helps us easily identify what common name the certificates should be presenting.
 
 = Service configuration =