<<<
Chronological Index
>>> <<<
Thread Index
>>>
[wildcard-comments] Verisign has broken DNS
- To: wildcard-comments@xxxxxxxxx
- Subject: [wildcard-comments] Verisign has broken DNS
- From: Mike Heins <mike@xxxxxxxxxxxx>
- Date: Sat, 27 Sep 2003 15:23:39 -0400
- Reply-to: mike@xxxxxxxxxxxx
- Sender: owner-wildcard-comments@xxxxxxxxx
- User-agent: Mutt/1.4i
There is an NXDOMAIN response for a reason -- for when a domain does
not exist. While perhaps not codified in the RFC explicitly, certainly
years of practice have given it the status of common law.
Please deal with this incredibly arrogant and shortsighted move by
Verisign.
This is not the first time this company has run roughshod over
the Internet, and this repeated pattern of behavior means I no
longer trust them in any way. As a consequence, I have revoked all
of their root certificates and my web browser will no longer trust
Verisign-signed SSL certificates as a result.
I have pulled the last of my business from Verisign, and I will be
urging all of my clients to do the same. I am an ecommerce consultant
and use PayflowPro and SSL certificates routinely; none of those
will be going to Verisign.
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.513.523.7621 <mike@xxxxxxxxxxxx>
Few blame themselves until they have exhausted all other possibilities.
-- anonymous
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|