Here it is (my opinion):
My opinion is that SSL certs, whichever company they come from, are not a
forefront consideration to John Q. Public. I don't think they know the
difference between Verisign or Thwate or Ripoff.com (well, maybe they'll
recognize ripoff.com as suspect), but, seriously, I don't think that level
of sophistication is there yet. Anyway, we use Verisign. We may switch to a
cert sold by TUCOWS. It's only $99.00
John Cesta
ColdFusion ASP ActiveState PERL Hosting
Includes 10 Domains - 100% Browser Based Administration
http://www.cybersmarts.net
LogFileManager - IIS LogFile Management Tool
WebPageChecker - Helps Maintain Server UpTime
http://www.serverautomationtools.com
> -----Original Message-----
> From: John Lucas [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 01, 2001 9:33 AM
> To: CF-Server
> Subject: RE: wildcard SSL certs
>
>
> Verisign does not support wildcards.
>
> Thawte (somehow a verisign company which sells certs for less $$$) does
> support wildcards. www.thawte.com
>
> My only thoughts on it is that the insurances that Verisign
> provides do not
> appear to be offered with the thawte certificate (not that it is a big
> deal). Also, there is the unfortunate issues with public
> branding. A large
> majority of the public will recognize Verisign and their site seal on your
> sites. They may not readily recognize Thawte. People can be so
> fickle over
> things some times because they do not truly understand the underlying
> technology. You may have a harder time convincing end users (John Q.
> Shopper) that the Thawte certificate provides the same technology as
> Verisign.
>
> John Lucas
> [EMAIL PROTECTED]
> http://www.fastestisp.com
>
>
> -----Original Message-----
> From: Dylan Bromby [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 01, 2001 8:03 AM
> To: CF-Server
> Subject: RE: wildcard SSL certs
>
>
> i have to admit i'm no expert with SSL/TLS. i use certificates on several
> servers. but my understanding is you can only use a certificate for *one*
> FQDN.
>
> do you have more info on where i can read about "wildcard" certificates? i
> could definitely use them in some for some of my clients.
>
> thanks!
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 01, 2001 5:56 AM
> To: CF-Server
> Subject: OT: wildcard SSL certs
>
>
> Does anyone have experience with wildcard SSL certs, like *.mycompany.com,
> which could theoretically be installed on www1.mycompany.com,
> www2.mycompany.com, etc? I am specifically wondering:
>
> 1) Are there compatibility problems with web server or web
> browser software?
>
> 2) Are they harder to work with in any other way than "normal"
> server certs?
>
> I'm investigating this because I think I have a problem. Right now I have
> server A and server B, each with an individual server cert. I have
> ClusterCats failover set up, so if server A dies server B will
> assume A's IP
> address. But the browser is still trying to connect to ServerA.com, and
> server B doesn't have the right cert for that, so I predict chaos. But I
> haven't tested it yet.
>
> ------------------------------------
> Martin Herbener
> Kentucky Department of Education
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
