welcome: please sign in

Diff for "MemberManual/ServingWebsites/SslCert"

Differences between revisions 14 and 15
Revision 14 as of 2007-11-17 03:06:17
Size: 2311
Editor: MichaelOlson
Comment: More fields
Revision 15 as of 2007-11-17 04:32:08
Size: 2690
Editor: MichaelOlson
Comment: Finally figure all this stuff out
Deletions are marked like this. Additions are marked like this.
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. 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.
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. To create a cerificate request in `file.crt` and a private 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.
Line 27: Line 27:
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.

When we process your request, we will:

 * Sign the certificate request as a Certificate Authority (CA).
 * 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 key in your Domtool configuration.
Line 31: Line 38:
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 for one of your own machines.
Line 36: Line 43:
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.

TableOfContents

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. 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.

openssl req -newkey rsa:2048 -keyout file.key -out file.crt -days DAYS -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.

When we process your request, we will:

  • Sign the certificate request as a Certificate Authority (CA).
  • 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 key 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.

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

MemberManual/ServingWebsites/SslCert (last edited 2019-01-11 01:40:03 by ClintonEbadi)