Oh, and tucows.* will not work in the browser, in case anyone is wondering
(not that GeoTrust would sign such a thing anyway).
I'm surprised that *.*.tucows.com works.
Adam
----- Original Message -----
From: "Kim Phelan" <kphelan@tucows.com>
To: "Derek J. Balling" <dredd@megacity.org>; "James Hsiung"
<james@tucows.com>
Cc: <discuss-list@opensrs.net>
Sent: Tuesday, April 01, 2003 3:36 PM
Subject: RE: Wildcards in QuickSSL Certs
> I just had an enlightening conversation with Geotrust.
> This is the deal.
>
> 1. You can have *.tucows.com
> this would work for mail.tucows.com, secure.tucows.com etc. but not
> secure.mail.tucows.com
>
> 2. You can also buy for *.*.tucows.com
> so that would work for secure.mail.tucows.com
> But it would *not* work for mail.tucows.com.
> You have to fill in each spot where the asterisk is in the common name.
>
> I hope that made sense.
>
> Kim Phelan
> Product Manager
> Tucows, Inc.
>
>
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of Derek J. Balling
> Sent: Tuesday, April 01, 2003 4:08 PM
> To: James Hsiung
> Cc: discuss-list@opensrs.net
> Subject: Re: Wildcards in QuickSSL Certs
>
>
>
> On Tuesday, April 1, 2003, at 03:06 PM, James Hsiung wrote:
> > The Geotrust wildcard allows you to secure *unlimited* number of
> > sub-domains, as long at they are 1) on the same server and 2) under
> > the same
> > base domain.
>
> Does CN=*.foo.com
>
> allow
>
> bar.foo.com
> intranet.bar.foo.com
>
> ?
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:41 EDT