SSL Certificates Support - CSR Generation Instructions- Stronghold Server - VeriSign UK Ltd.
VeriSign, Inc.® United Kingdom Home | Worldwide Sites | Site Map
You Are Here: United Kingdom Home > Support > SSL Certificates Support > CSR Generation Instructions- Stronghold Server

SSL Certificates Support

CSR Generation Instructions- Stronghold Server

To generate a CSR, you will need to create a key pair for your server. These two items are a digital certificate key pair and cannot be separated. If you lose your public/private key file or your password and generate a new one, your SSL Certificate will no longer match. You will have to request a new SSL Certificate and may be charged.

VeriSign recommends that you contact the Stronghold vendor for additional information. 

Generate a Key Pair

Stronghold keys and certificates are managed through three scripts: genkey, getca and genreq. These are part of the normal Stronghold distribution. Keys and certificates are stored in the directory$SSLTOP/private/, where SSLTOP is typically /usr/local/ssl. To generate a key pair and CSR for your server:

  1. Run genkey, specifying the name of the host or virtual host: genkey hostname. The genkey script displays the filenames and locations of the key file and CSR file it will generate:  
     
    Key file: /usr/local/www/sslhostname.key  
    CSR file: /usr/local/www/sslhostname.cert  
     
    Note: If you already have a key for your server, run genreq [servername] to generate only the CSR.
  2. Press Enter. The genkey script reminds you to be sure you are not overwriting an existing key pair and certificate.
  3. When prompted, enter a key size in bits. We recommend using the largest key size available: 1024 bits.
  4. When prompted, enter random key strokes. Stop when the counter reaches zero and genkey beeps. This random data to create a unique public and private key pair.
  5. When prompted, enter y to create the key pair and CSR.
  6. Select VeriSign as your CA.
  7. Enter all of the information requested and press Enter. Back up your key file and CSR on a floppy disk and store the disk in a secure location. If you lose your private key or forget the password, you will not be able to install your Secure Server ID and will need to request and purchase a new one from VeriSign.
  8. You have just created a key pair and a CSR. To copy and paste the information into the enrolment form, open the file in a text editor that does not add extra characters (Notepad or Vi are recommended).
  9. Go to Enrolment.

Terms Defined

Common Name

The Common Name is the Host + Domain Name. It looks like "www.company.co.uk" or "company.co.uk".

VeriSign certificates can only be used on Web servers using the Common Name specified during enrolment. For example, a certificate for the domain "domain.co.uk" will receive a warning if accessing a site named "www.domain.co.uk" or "secure.domain.co.uk", because "www.domain.co.uk" and "secure.domain.co.uk" are different from "domain.co.uk".

Organisation Information

  • If your company or department has an &, @, or any other symbol using the shift key in its name, you must spell out the symbol or omit it to enrol.
  • The “Org Unit” field is the name of the department or organisation unit making the request.
  • The Locality field is the city or town name, for example: Guildford.
  • Do not abbreviate the county name, for example: Surrey.
  • Use the two-letter code without punctuation for country, for example: GB.

Contact Information

During the verification process, VeriSign may need to contact your organisation. Be sure to provide an email address, phone number, and fax number that will be checked and responded to quickly. These fields are not part of the certificate.


Contact VeriSign Legal Notices Privacy Repository © 2003 - 2008 VeriSign UK Limited. All rights reserved.
6/29/08 10:00 PM