Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2001

    WildCard SSL question

    I'm thinking in get a wildcard SSL certificate, but I have a problem

    When I generate the .crt which "Common name" should I use?

    Or what must I use?
    Shared Web Hosting - Reseller Hosting - Semi-Dedicated Servers - SolusVM/XEN VPS
    LiteSpeed Powered - R1Soft Continuous Data Protection - 24/7 Chat/Email/Helpdesk Support
    Cpanel/WHM - Softaculous - R1soft Backup - Litespeed - Cloudlinux -Site Builder- SSH support - Account Migration
    DowntownHost LLC - In Business since 2001- West/Center/East USA - Netherlands - Singapore

  2. #2
    From Thawte:
    The domain name entered here will be the "common name" used for the
    certificate. Clients will verify that the system to which they connected
    matches this domain name, so you'll want to ensure that you choose the
    appropriate name for the server. For example, if a system is really named, but people will be accessing it as, the
    domain name chosen here should be

    Some Certificate Authorities (such as Thawte) will permit a "wildcard"
    domain name here, i.e., * If you have several hostnames within
    a particular domain that you will be supporting, this may be a better
    choice, but you'll need to ensure that the Certificate Authority that
    you'll be using to sign your certificate will support this form for the
    certificate's common name. Unfortunately, not all clients will recognize
    wildcard characters in the domain name, and those clients will be
    presented with a warning that the certificate's domain name doesn't match
    the server's domain name. The current versions of both Microsoft's and
    Netscape's clients, however, do support wildcarded domain names.

    Domain name of TLS/SSL server for which request is being
    generated: *

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts