|
Size: 2311
Comment: More fields
|
Size: 4379
Comment: Add big fat disclaimer about using our cert, and link to it
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| = Making a cert for use with Domtool = | = Introduction = |
| Line 9: | Line 9: |
| 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. | There are several different options available for providing an SSL certificate to use with us. |
| Line 11: | Line 11: |
| To create a self-signed SSL cerificate in `file.crt` with key in `file.key`, do the following. '''DAYS''' indicates the number of days that you want the certificate to be valid. The certificate should be placed somewhere in your home directory, like "~/certs", for example. | The first option is to get a signed certificate from a trusted Certificate Authority ("CA" for short). If you want to make it os that visitors to your website never see an annoying nag dialog box, then this is your best option. Alternatively, you can provide us with a certificate request ("CSR" for short), and we can provide you with a signed certificate. Please be aware that since our [http://deleuze.hcoop.net/ca/ca.crt CA certificate] is not included by default with any web browsers or operating systems, you won't really gain much benefit from having us sign your cert, except for a nebulous "cool factor" :) . If you want to be sure that the people who browse your website won't be prompted about accepting your SSL certificate, then this is not for you. The last option is to make a self-signed certificate. = Having HCoop provide you with a certificate = 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 csr file. The csr file is called a "certifcate signing request" (sometimes abbreviated "certificate 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.csr` 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 14: | Line 24: |
| openssl req -newkey rsa:2048 -keyout file.key -out file.crt -days DAYS -nodes | openssl req -newkey rsa:2048 -keyout file.key -out file.csr -nodes |
| Line 27: | Line 37: |
| These files should be readable only by you, the HCoop admins, and your ".daemon" alter ego, so be sure to set permissions properly on the directory where you store the certificate. | 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). * Place a complimentary copy of the resulting certificate in the same directory as the certificate request, with a ".crt" extension. * Concatenate the signed request with your key. * 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. This allows you to import a single [http://deleuze.hcoop.net/ca/ca.crt CA certificate] (click on the link to install), which avoids the "certificate confirmation" dialog box when you browse one of our websites (or one of our member websites). Be aware that '''we are not in any way recommending that you do this'''; it is solely for the sake of convenience that we provide this option. |
| Line 31: | Line 51: |
| This is for reference, in case you want to make a cert for one of your own machines. | This is for reference, in case you want to make a self-signed certificate rather than having HCoop sign it. '''DAYS''' indicates the number of days that you want the certificate to be valid. |
| Line 36: | Line 56: |
| openssl req -x509 -newkey rsa:2048 -keyout FILE -out FILE -days DAYS | openssl req -x509 -newkey rsa:2048 -keyout FILE -out FILE -days DAYS -nodes |
This is the page of the MemberManual that describes how to generate a valid SSL cert.
Introduction
There are several different options available for providing an SSL certificate to use with us.
The first option is to get a signed certificate from a trusted Certificate Authority ("CA" for short). If you want to make it os that visitors to your website never see an annoying nag dialog box, then this is your best option.
Alternatively, you can provide us with a certificate request ("CSR" for short), and we can provide you with a signed certificate. Please be aware that since our [http://deleuze.hcoop.net/ca/ca.crt CA certificate] is not included by default with any web browsers or operating systems, you won't really gain much benefit from having us sign your cert, except for a nebulous "cool factor" 
. If you want to be sure that the people who browse your website won't be prompted about accepting your SSL certificate, then this is not for you.
The last option is to make a self-signed certificate.
Having HCoop provide you with a certificate
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 csr file. The csr file is called a "certifcate signing request" (sometimes abbreviated "certificate 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.csr 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.csr -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).
- Place a complimentary copy of the resulting certificate in the same directory as the certificate request, with a ".crt" extension.
- Concatenate the signed request with your key.
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.
This allows you to import a single [http://deleuze.hcoop.net/ca/ca.crt CA certificate] (click on the link to install), which avoids the "certificate confirmation" dialog box when you browse one of our websites (or one of our member websites). Be aware that we are not in any way recommending that you do this; it is solely for the sake of convenience that we provide this option.
Making a self-signed .pem file
This is for reference, in case you want to make a self-signed certificate rather than having HCoop sign it. 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