|
Size: 2766
Comment: -days is useless for a certificate request
|
Size: 2934
Comment: Add complementary copy text
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| To create a cerificate request in `file.crt` and a private key in `file.key`, do the following. The certificate should be placed somewhere in your home directory, like "~/certs", for example. | To create a cerificate request in `file.crt` and a private key in `file.key`, do the following. The certificate should be placed somewhere in your home directory, like "{{{~/certs}}}", for example. |
| Line 33: | Line 33: |
| * Place a complementary copy of the result in the smae directory as the certificate request. | |
| Line 34: | Line 35: |
| * Grant you Domtool permissions so that you can use this key in your Domtool configuration. | * Grant you Domtool permissions so that you can use this certificate at location {{{/etc/apache2/ssl/user/yourdomain.org.pem}}} in your Domtool configuration. |
This is the page of the MemberManual that describes how to generate a valid SSL cert.
Making a cert for use with Domtool
If you are creating an SSL certificate to use for a web virtual host via DomTool, then you need to create both a key file and a crt file. The crt file is called a "certifcate request", and you will want to specify that on the SSL form in the HCoop Portal. We'll also need access to your key.
To create a cerificate request in file.crt and a private key in file.key, do the following. The certificate should be placed somewhere in your home directory, like "~/certs", for example.
openssl req -newkey rsa:2048 -keyout file.key -out file.crt -nodes
Here is an explanation of the parameters that you will be asked to provide. Replace yourdomain.org with your domain name.
Country/State/Locality: These are self-explanatory.
Organization Name: This can be anything you want. It is often the full name or description of your organization or website.
Organizational Unit Name: This can be anything you want. It can be left blank.
Common Name: This is the domain that goes with the certificate. It can be either a single name (i.e. "yourdomain.org"), or a wildcard domain (like "*.yourdomain.org"). The wildcard domain is used for sharing the same certificate in multiple subdomains of your domain.
Email Address: A valid email address. People often use ca@yourdomain.org.
Challenge Password: Leave blank.
Company Name: This can be anything you want. It can be left blank.
These files should be readable only by you and the HCoop admins, so be sure to set permissions properly on the directory where you store the certificate request and key. Now you're ready to follow the rest of the instructions on [:../:the previous page].
When we process your request, we will:
- Sign the certificate request as a Certificate Authority (CA).
- Concatenate the signed request with your key.
- Place a complementary copy of the result in the smae directory as the certificate request.
Place the result in /etc/apache2/ssl/user/yourdomain.org.pem.
Grant you Domtool permissions so that you can use this certificate at location /etc/apache2/ssl/user/yourdomain.org.pem in your Domtool configuration.
Making a self-signed .pem file
This is for reference, in case you want to make a self-signed certificate for one of your own machines. DAYS indicates the number of days that you want the certificate to be valid.
FILE is the filename of the certificate that will be generated: it should end in ".pem". DAYS indicates the number of days that you want the certificate to be valid.
openssl req -x509 -newkey rsa:2048 -keyout FILE -out FILE -days DAYS -nodes