<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Noah's Mark - Latest Comments in Firefox&amp;#8217;s SSL policy is not bad, you idiot</title><link>http://noahsmark.disqus.com/</link><description></description><language>en</language><lastBuildDate>Sun, 14 Sep 2008 13:23:55 -0000</lastBuildDate><item><title>Re: Firefox&amp;#8217;s SSL policy is not bad, you idiot</title><link>http://noahsmark.com/2008/08/19/firefoxs-ssl-policy-is-not-bad-you-idiot/#comment-2347808</link><description>Good read. I think it's a good system to get in your face; especially for my relatives who are computer illiterate. This step is completely necessary to protect any user from doing harm to themself.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PaulSolt</dc:creator><pubDate>Sun, 14 Sep 2008 13:23:55 -0000</pubDate></item><item><title>Re: Firefox&amp;#8217;s SSL policy is not bad, you idiot</title><link>http://noahsmark.com/2008/08/19/firefoxs-ssl-policy-is-not-bad-you-idiot/#comment-1668040</link><description>Because they are different services - note the keyword _verification_ in that second part. The first part, the "I want a domain name here plzthx", isn't a complicated problem because there aren't many (enforced) trust/identity strings attached. Also, because there are an inordinate amount of domains being registered and a much smaller number of sites getting SSL certs, I can only imagine the cost for the first will be much cheaper than the second. Sounds pretty simple to me.&lt;br&gt;&lt;br&gt;Oh, and the real answer is, "because they charge that much and people will pay it." Enter capitalism.&lt;br&gt;&lt;br&gt;Your suggestion, in the first paragraph, is for how a "trusted" authority should establish trust with an untrusted endpoint - you do some activity to prove to that party that you "own" the domain, and that third party, which is a trusted authority by some other definition, is depended on for its verification of your site. Maybe that is enough to establish trust, but how does it relate to the post?&lt;br&gt;&lt;br&gt;If you want to complain about the methods CAs use to verify identity, then that is a different discussion. If you feel a CA charges too much for its services, find a different one. The digicert price I found was after clicking 2 links in a google search. I bet you can find better prices without looking too hard.&lt;br&gt;&lt;br&gt;Or you get behind someone like &lt;a href="http://CACert.org" rel="nofollow"&gt;CACert.org&lt;/a&gt;, who gives out free (as in beer) certs and (I believe) is still trying to be accepted by mozilla as a trusted root CA:&lt;br&gt;&lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=21" rel="nofollow"&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=21&lt;/a&gt;...&lt;br&gt;&lt;br&gt;Mozilla has a nice, fair, and public policy for how to become a trusted CA:&lt;br&gt;&lt;a href="http://www.mozilla.org/projects/security/certs/" rel="nofollow"&gt;http://www.mozilla.org/projects/security/certs/&lt;/a&gt;...&lt;br&gt;&lt;br&gt;So I don't think there are major roadblocks preventing somebody from using your method to establish trust and charging less than $100 a year and getting accepted by mozilla as a root CA. Except, you know, capitalism.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">noahrichards</dc:creator><pubDate>Tue, 19 Aug 2008 23:50:44 -0000</pubDate></item><item><title>Re: Firefox&amp;#8217;s SSL policy is not bad, you idiot</title><link>http://noahsmark.com/2008/08/19/firefoxs-ssl-policy-is-not-bad-you-idiot/#comment-1667871</link><description>Server identity verification can and should be tested in the same manner that Google Apps does it - stick a new page up on your server or add a new CNAME record to prove you control the domain.&lt;br&gt;&lt;br&gt;If domain names can be registered for under $10, why should domain name verification cost hundreds of dollars per year?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">trevelyan</dc:creator><pubDate>Tue, 19 Aug 2008 16:02:26 -0000</pubDate></item></channel></rss>