Wednesday, Wednesday, August 22, 2001, 4:40:42 PM, Bryan Waters wrote:
> As to whether people actually use it...I dunno, but using an invalid cert
> and generating that popup...that I think is a huge mistake...make it simple
> for the user, cert or not...explaining away that obnoxious "unknown" cert
> popup...thats not something I want to do. For a first time customer, that
> just looks tacky!
I agree for the most part. However, if a new CA started, that wasn't
in the browsers, then perhaps an educational process for getting them
to add the root cert would be an interesting path to take.
But what we were really discussing is the merits of a system
like this:
https://bia.safe-order.net/gnp-fastdns/
Which is the secure site for http://www.gnp-fastdns.net/
And the cert is in the name of the hosting company that hosts the
site.
They have a single cert for each machine, in teh form
machinename.safe-order.net and user SSL sites are at
https://machinename.safe-order.net/customername/
This is just one example of many hosting services that do this.
As I said, I see this as a legitimate and valid method, and one that
has been in widespread use for over 5 years without dire consequences
by some of the largest hosting farms in the industry.
Obviously some people disagree with me :)
Oh well, I'm not known for being popular with everyone :)
--
Best regards,
William X Walsh <[EMAIL PROTECTED]>
Userfriendly.com Domains
The most advanced domain lookup tool on the net
DNS Services from $1.65/mo
