|
Size: 2199
Comment: 2048 is the new 1024, or so says my Security class
|
Size: 4707
Comment: stop recommending members have hcoop ign their certs: there really is no value to having us do that any more (or really ever)
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| [[TableOfContents]] | <<TableOfContents>> |
| 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 a few options for acquiring 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 so that visitors to your website never see an annoying nag dialog box, then this is your best option. Alternatively, you can generate a self-signed certificate. There are several good introductions to SSL and x509 certificates in general if you are unfamiliar with the subject: * [[http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#aboutcerts|Apache SSL FAQ]] * [[http://www.tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html|The SSL Certificate HOWTO]] == Security Precautions == At some point, your certificate and private key will need to be stored in afs. Since afs is publicly accessible, you need to take a few precautions to ensure that your data remains private. For all key operations, keep the files in a directory that only you and the admins can read: |
| Line 14: | Line 25: |
| openssl req -x509 -newkey rsa:2048 -keyout file.key -out file.crt -days DAYS -nodes | mkdir certificates fs setacl certificates -clear $USER all }}} == Obtaining a Certificate == === Getting a certificate from a trusted CA === There are several options available. By far the largest providers are [[http://www.verisign.com/|VeriSign]] and [[http://www.thawte.com/|Thawte]]. Several members seem to like [[http://gandi.net|Gandi]]. You can also get a basic zero-cost certificate from [[http://startssl.com|StartSSL]]. We make no specific recommendations concerning which CA to choose: just make certain that their root CA certificates are included with the majority of web browsers. === Option 2: 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 "certificate 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. 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. 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 |
| Line 21: | Line 49: |
| * '''Organizational Unit''': This can be anything you want. It can be left blank. | * '''Organizational Unit Name''': This can be anything you want. It can be left blank. |
| Line 24: | Line 52: |
| * '''Challenge Password''': Leave blank. * '''Company Name''': This can be anything you want. It can be left blank. |
|
| Line 25: | Line 55: |
| 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. | === Making a self-signed certificate === |
| Line 27: | Line 57: |
| = 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. |
| Line 29: | Line 59: |
| This is for reference, in case you want to make a cert for one of your own machines. '''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. |
'''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. |
| Line 36: | Line 64: |
== Installing the Certificate == Now that you have a certificate, we need to install it. Use the [[https://members.hcoop.net/portal/cert|SSL permissions]] page on the portal to request installation of your new certificate. You need to provide us with either: * A `pem` containing your public certificate and private key concatenated together * Your public certificate and private key, both in `pem` format We will then verify the certificate and install it, providing you with a path that you can use to [[DomTool/Examples#UsingSSL.28HTTPS.29|enable SSL using domtool]]. ---- CategoryNeedsWork CategoryMemberManual |
This is the page of the MemberManual that describes how to generate a valid SSL cert.
Contents
Introduction
There are a few options for acquiring 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 so that visitors to your website never see an annoying nag dialog box, then this is your best option.
Alternatively, you can generate a self-signed certificate.
There are several good introductions to SSL and x509 certificates in general if you are unfamiliar with the subject:
Security Precautions
At some point, your certificate and private key will need to be stored in afs. Since afs is publicly accessible, you need to take a few precautions to ensure that your data remains private. For all key operations, keep the files in a directory that only you and the admins can read:
mkdir certificates fs setacl certificates -clear $USER all
Obtaining a Certificate
Getting a certificate from a trusted CA
There are several options available. By far the largest providers are VeriSign and Thawte. Several members seem to like Gandi. You can also get a basic zero-cost certificate from StartSSL. We make no specific recommendations concerning which CA to choose: just make certain that their root CA certificates are included with the majority of web browsers.
Option 2: 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 "certificate 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. 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. 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.
Making a self-signed certificate
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
Installing the Certificate
Now that you have a certificate, we need to install it.
Use the SSL permissions page on the portal to request installation of your new certificate. You need to provide us with either:
A pem containing your public certificate and private key concatenated together
Your public certificate and private key, both in pem format
We will then verify the certificate and install it, providing you with a path that you can use to enable SSL using domtool.