<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Nobody is perfect</title>
	<atom:link href="http://blog.phishme.com/2009/01/nobody-is-perfect/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.phishme.com/2009/01/nobody-is-perfect/</link>
	<description>Posts about innovative phishing ploys, social engineering techniques, and the latest hacks.  PhishMe is your one stop blog for the latest in anti-phishing and security news.</description>
	<lastBuildDate>Sat, 04 Feb 2012 10:16:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dominic Montgomery</title>
		<link>http://blog.phishme.com/2009/01/nobody-is-perfect/comment-page-1/#comment-3660</link>
		<dc:creator>Dominic Montgomery</dc:creator>
		<pubDate>Thu, 23 Apr 2009 13:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phishme.com/?p=130#comment-3660</guid>
		<description>I work for secure128.com who is a wholesale reseller (registerd agent) of several SSL brands. We considered also reselling the Comodo SSL brand but decided against it because of this very issue.  
 
As Bjorn posted above, &quot;there are proper CAs doing their best to make the world a safer place, and there are those out for easy money.&quot; is 100% correct in Comodo&#039;s case. 
 
The simple fact is that when you become a reseller of Comodo, you get the option in their portal to simply &quot;checkmark&quot; a box acknowledging that you have gathered all the required vetting documentation from your SSL customer for each order placed. This completely pushes off the responsibility of verifying domain owner&#039;s identities from the Certificate Authority (Comodo) to the resellers who are NOT in the business of verifying identities. 
 
In short, Comodo does not provide any form of domain owner identity verification through the resellers of their products at all! Sure they provide encryption but give you no idea of who actually owns the website you&#039;re attempting to trust. 
 
Pathetic! 
 
-Dom Montgomery </description>
		<content:encoded><![CDATA[<p>I work for secure128.com who is a wholesale reseller (registerd agent) of several SSL brands. We considered also reselling the Comodo SSL brand but decided against it because of this very issue. </p>
<p>As Bjorn posted above, &quot;there are proper CAs doing their best to make the world a safer place, and there are those out for easy money.&quot; is 100% correct in Comodo&#039;s case.</p>
<p>The simple fact is that when you become a reseller of Comodo, you get the option in their portal to simply &quot;checkmark&quot; a box acknowledging that you have gathered all the required vetting documentation from your SSL customer for each order placed. This completely pushes off the responsibility of verifying domain owner&#039;s identities from the Certificate Authority (Comodo) to the resellers who are NOT in the business of verifying identities.</p>
<p>In short, Comodo does not provide any form of domain owner identity verification through the resellers of their products at all! Sure they provide encryption but give you no idea of who actually owns the website you&#039;re attempting to trust.</p>
<p>Pathetic!</p>
<p>-Dom Montgomery</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ismael Casimpan</title>
		<link>http://blog.phishme.com/2009/01/nobody-is-perfect/comment-page-1/#comment-3504</link>
		<dc:creator>Ismael Casimpan</dc:creator>
		<pubDate>Wed, 28 Jan 2009 06:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phishme.com/?p=130#comment-3504</guid>
		<description>Wow, thanks for the timely blog. I found this via Google researching for the keyword &quot;comodo sucks&quot; just to check if there is something negative being said about the company. 
 
We were about to consider purchasing code signing certificate from them. But with this issue, I think we better stick with the other guys: either Verisign or Godaddy 
 
- Ismael </description>
		<content:encoded><![CDATA[<p>Wow, thanks for the timely blog. I found this via Google researching for the keyword &quot;comodo sucks&quot; just to check if there is something negative being said about the company.</p>
<p>We were about to consider purchasing code signing certificate from them. But with this issue, I think we better stick with the other guys: either Verisign or Godaddy</p>
<p>- Ismael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bj&#248;rn Vermo</title>
		<link>http://blog.phishme.com/2009/01/nobody-is-perfect/comment-page-1/#comment-3405</link>
		<dc:creator>Bj&#248;rn Vermo</dc:creator>
		<pubDate>Mon, 05 Jan 2009 09:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phishme.com/?p=130#comment-3405</guid>
		<description>As you say, there are proper CAs doing their best to make the world a safer place, and there are those out for easy money.  
 
Since there is no international system of approval for CAs, we are in a more difficult situation than when we want to know if a chartered accountant can be trusted. Each browser maker has to either do their own rather expensive vetting of CAs who want to be included in their rootstore, or they have to rely on somebody else&#039;s rootstore. Those who go with their own rootstore risk negative attention if they are being more careful than the most lenient competitor - &quot;browser X does not work with site Y&quot; - because most users do not understand that it has something to do with security until after they have been burned.   
 
Another problem is even bigger than the unreliable CA. The unreliable domain registrar has mostly been overlooked, even though they are in many cases easier to target.  
 
Even if the certificate providers do their job, that does not help much if the registrar does not provide up to date and truthful information about who owns the domain. Nor does it further net safety that some will let a domain be transferred quickly and without an audit trail, do not check the identity of the new owner, or any number of other sloppy behaviours we know have caused problems in the past. </description>
		<content:encoded><![CDATA[<p>As you say, there are proper CAs doing their best to make the world a safer place, and there are those out for easy money. </p>
<p>Since there is no international system of approval for CAs, we are in a more difficult situation than when we want to know if a chartered accountant can be trusted. Each browser maker has to either do their own rather expensive vetting of CAs who want to be included in their rootstore, or they have to rely on somebody else&#039;s rootstore. Those who go with their own rootstore risk negative attention if they are being more careful than the most lenient competitor &#8211; &quot;browser X does not work with site Y&quot; &#8211; because most users do not understand that it has something to do with security until after they have been burned.  </p>
<p>Another problem is even bigger than the unreliable CA. The unreliable domain registrar has mostly been overlooked, even though they are in many cases easier to target. </p>
<p>Even if the certificate providers do their job, that does not help much if the registrar does not provide up to date and truthful information about who owns the domain. Nor does it further net safety that some will let a domain be transferred quickly and without an audit trail, do not check the identity of the new owner, or any number of other sloppy behaviours we know have caused problems in the past.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddy Nigg</title>
		<link>http://blog.phishme.com/2009/01/nobody-is-perfect/comment-page-1/#comment-3396</link>
		<dc:creator>Eddy Nigg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 23:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phishme.com/?p=130#comment-3396</guid>
		<description>StartCom made the &quot;Critical Event Report&quot; publicly available &lt;a href=&quot;https://blog.startcom.org/?p=161&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. </description>
		<content:encoded><![CDATA[<p>StartCom made the &quot;Critical Event Report&quot; publicly available <a href="https://blog.startcom.org/?p=161" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddy Nigg</title>
		<link>http://blog.phishme.com/2009/01/nobody-is-perfect/comment-page-1/#comment-3394</link>
		<dc:creator>Eddy Nigg</dc:creator>
		<pubDate>Fri, 02 Jan 2009 22:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phishme.com/?p=130#comment-3394</guid>
		<description>Yes that&#039;s correct. Mike Zusman detected a real flaw in our system by using an SSL proxy tool to change the values of the validation emails. The attempt to get a certificate for &lt;a href=&quot;http://www.verisign.com&quot; rel=&quot;nofollow&quot;&gt;www.verisign.com&lt;/a&gt; was detected within 8 minutes and Mike was blocked from our systems. After a short conversation, it was reproduced and correctly fixed. 
 
Nevertheless, this is under our direct control and needless to say that our further layers of defenses succeeded to prevent an attack on a high-profile target such as Verisign. A such, you are right, no system is perfect and mistakes do happen. However exactly because of that, special care must be taken and the system itself must be protected. More than that, retaining all evidences are important as well. As such we also had the capability to verify if other such attempts happened. We&#039;ve found none. 
 
There is a huge difference in my opinion between this flaw and that of Comodo, as no validation system was in place at all. That&#039;s not a flaw, it was simply non-existent. Would StartCom outsource domain validation to a third party? Most likely not. </description>
		<content:encoded><![CDATA[<p>Yes that&#039;s correct. Mike Zusman detected a real flaw in our system by using an SSL proxy tool to change the values of the validation emails. The attempt to get a certificate for <a href="http://www.verisign.com" rel="nofollow">http://www.verisign.com</a> was detected within 8 minutes and Mike was blocked from our systems. After a short conversation, it was reproduced and correctly fixed.</p>
<p>Nevertheless, this is under our direct control and needless to say that our further layers of defenses succeeded to prevent an attack on a high-profile target such as Verisign. A such, you are right, no system is perfect and mistakes do happen. However exactly because of that, special care must be taken and the system itself must be protected. More than that, retaining all evidences are important as well. As such we also had the capability to verify if other such attempts happened. We&#039;ve found none.</p>
<p>There is a huge difference in my opinion between this flaw and that of Comodo, as no validation system was in place at all. That&#039;s not a flaw, it was simply non-existent. Would StartCom outsource domain validation to a third party? Most likely not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

