don't use ".site.com", as this is not a URL anyone will use. The correct wildcard is
*.site.com, which is a wildcard cert. These cost at least 4 times as much through Thawte
than they used to, if they are even still available. You really should just choose a single
URL to secure, and type it in exactly; eg "www.site.com" or "secure.site.com" (without the
quotes)
Good luck
Victor wrote:
> Thanks go to both Mark and Adam for clearing this up for me. However I do have one more
> question.
>
> Where does the URL of a site goes when I generate a CSR? I sometime get an error that the
> name on the certificate doesn't match the name of the site. Does the name go to the
> CommonName (eg YOUR name) field? I am using OpenSSL (latest version, I think, 0.9.5a).
> And how should I specify it?
>
> Example
> www.site.com
> site.com
> .site.com
> *.site.com
>
> ???
>
> Thank you very much for your help. IP's are not that big a problem, I just wanted to
> understand what was going on.
>
> Victor
>
> Mark Holt wrote:
>
> > Mod_ssl is the same way. I think it's the way it has to be, since you must store a
> > session cache for visitors. I don't know of any products that are not that way. It
> > isn't that hard to get more IP's, is it?