[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Re: Secure Certificate
- Subject: Re: [cobalt-developers] Re: Secure Certificate
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Wed Jul 17 07:57:00 2002
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
OWSA> Date: Wed, 17 Jul 2002 10:05:08 -0400
OWSA> From: Ontario Web System Administrator
OWSA> How dose some other servers I see run ssl under there
OWSA> servers for there clients with the certificate from
OWSA> root???
In addition to what Gerald correctly stated: blanket certs.
One pays, say, about five times as much for
*.somedomain.tld
for which there is no limit on "*" subdomains.
I contend that
secure.somedomain.tld/customer/
is a security risk. The certificate validates the provider, but
what is to stop me from signing up with them, using a valid cert,
and impersonating a competitor that they host?
An individual cert validates as well as encrypts -- at least in
theory.
(Side note: Why is this on the "developers" list? It belongs on
"users".)
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.