<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Two tiered SSL certificates</title>
	<atom:link href="http://www.sethsblog.com/two-tiered-ssl-certificates/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sethsblog.com/two-tiered-ssl-certificates</link>
	<description>Facts are meaningless. You could use facts to prove anything that's even remotely true!</description>
	<pubDate>Fri, 21 Nov 2008 05:15:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Nick</title>
		<link>http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3151</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Tue, 22 Jul 2008 08:06:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3151</guid>
		<description>Seth:
"My point is that why should a normal person, not an attacker with a site not be able to use SSL without having a warning in a user’s browser? A free CA that’s pre-installed would work for that just fine."
Who decides if you're an attacker or not? Someone has to - and that's the checking part that costs CAs money, which is why they charge.

Actually, the product you ask for already exists. It's called a DV (Domain Validated) certificate. The 'checking' is done by verifying your ownership of the domain (usually via emailing a contact from the WHOIS or someone@thedomain.com). As this can be automated, the cost is dramatically less. If you look around, the certs can be had for anything from $50 to $10.</description>
		<content:encoded><![CDATA[<p>Seth:<br />
&#8220;My point is that why should a normal person, not an attacker with a site not be able to use SSL without having a warning in a user’s browser? A free CA that’s pre-installed would work for that just fine.&#8221;<br />
Who decides if you&#8217;re an attacker or not? Someone has to - and that&#8217;s the checking part that costs CAs money, which is why they charge.</p>
<p>Actually, the product you ask for already exists. It&#8217;s called a DV (Domain Validated) certificate. The &#8216;checking&#8217; is done by verifying your ownership of the domain (usually via emailing a contact from the WHOIS or <a href="mailto:someone@thedomain.com">someone@thedomain.com</a>). As this can be automated, the cost is dramatically less. If you look around, the certs can be had for anything from $50 to $10.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3150</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Tue, 22 Jul 2008 03:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3150</guid>
		<description>Nick you fail to see my point. I understand this can be faked. I mistakenly used the wrong example because I realize that it won't solve these sorts problems and don't intend to use this to solve them.

My point is that why should a normal person, not an attacker with a site not be able to use SSL without having a warning in a user's browser? A free CA that's pre-installed would work for that just fine.</description>
		<content:encoded><![CDATA[<p>Nick you fail to see my point. I understand this can be faked. I mistakenly used the wrong example because I realize that it won&#8217;t solve these sorts problems and don&#8217;t intend to use this to solve them.</p>
<p>My point is that why should a normal person, not an attacker with a site not be able to use SSL without having a warning in a user&#8217;s browser? A free CA that&#8217;s pre-installed would work for that just fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3148</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Tue, 22 Jul 2008 00:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3148</guid>
		<description>Have you heard of a Man In The Middle attack?

I run a public wifi hotspot, but proxy all traffic to your bank through my server, which uses a self-signed ssl certificate.  You are not warned by your browser, and bank online care free.  I now have your credentials, even though everything you sent *was* encrypted.

Fail.

You pay Verisign to verify that the certificates they issue are only issued to the rightful owner of that domain.  Whether or not they actually do that is a different question.</description>
		<content:encoded><![CDATA[<p>Have you heard of a Man In The Middle attack?</p>
<p>I run a public wifi hotspot, but proxy all traffic to your bank through my server, which uses a self-signed ssl certificate.  You are not warned by your browser, and bank online care free.  I now have your credentials, even though everything you sent *was* encrypted.</p>
<p>Fail.</p>
<p>You pay Verisign to verify that the certificates they issue are only issued to the rightful owner of that domain.  Whether or not they actually do that is a different question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3147</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Mon, 21 Jul 2008 23:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3147</guid>
		<description>I agree that this is a good solution but unless its supported in most browsers, it's rubbish.

Firefox on the Linux desktop is a very tiny portion of the market share who are likely to already be tech saavy enough to not mind the warning anyway.

Firefox including a free CA on all builds of their browser is what's needed to take hold.</description>
		<content:encoded><![CDATA[<p>I agree that this is a good solution but unless its supported in most browsers, it&#8217;s rubbish.</p>
<p>Firefox on the Linux desktop is a very tiny portion of the market share who are likely to already be tech saavy enough to not mind the warning anyway.</p>
<p>Firefox including a free CA on all builds of their browser is what&#8217;s needed to take hold.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holden Karau</title>
		<link>http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3145</link>
		<dc:creator>Holden Karau</dc:creator>
		<pubDate>Mon, 21 Jul 2008 22:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sethsblog.com/two-tiered-ssl-certificates#comment-3145</guid>
		<description>There is a free root (known as cacert.org ) I &lt;i&gt;think&lt;/i&gt; they might be in some linux distributions firefox, which is well better than self-signed.</description>
		<content:encoded><![CDATA[<p>There is a free root (known as cacert.org ) I <i>think</i> they might be in some linux distributions firefox, which is well better than self-signed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
