<?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: Welcome to SSLFail</title>
	<atom:link href="http://www.sslfail.com/2009/01/welcome-to-sslfail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/</link>
	<description>1.2.840.113549.1.1</description>
	<lastBuildDate>Thu, 01 Jul 2010 03:13:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ToddH</title>
		<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/comment-page-1/#comment-25</link>
		<dc:creator>ToddH</dc:creator>
		<pubDate>Sun, 25 Jan 2009 23:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=3#comment-25</guid>
		<description>I think SSL failures and the reliance on self-signed certs in many products is a great area to highlight. The recent browser warnings have served to bring it into focus where it was previously ignored by many.

We spent a lot of time designing our product (and paying for thousands of genuine SSL certs) to avoid exactly this problem. My cofounder blogged about it last year at http://www.napera.com/blog/?p=52. An SSL certificate failure in our product is treated as a showstopper bug.</description>
		<content:encoded><![CDATA[<p>I think SSL failures and the reliance on self-signed certs in many products is a great area to highlight. The recent browser warnings have served to bring it into focus where it was previously ignored by many.</p>
<p>We spent a lot of time designing our product (and paying for thousands of genuine SSL certs) to avoid exactly this problem. My cofounder blogged about it last year at <a href="http://www.napera.com/blog/?p=52" rel="nofollow">http://www.napera.com/blog/?p=52</a>. An SSL certificate failure in our product is treated as a showstopper bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cd-MaN</title>
		<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/comment-page-1/#comment-23</link>
		<dc:creator>Cd-MaN</dc:creator>
		<pubDate>Thu, 22 Jan 2009 09:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=3#comment-23</guid>
		<description>Hello guys.

Inspired by this site, I did a little research of my own: http://hype-free.blogspot.com/2009/01/sslfail.html

The results are incredible (incredibly sad): less than 5% of the sites have proper certs. If you would like to get the final list or the script I used, let me know (it can keep this blog updated for years :-().</description>
		<content:encoded><![CDATA[<p>Hello guys.</p>
<p>Inspired by this site, I did a little research of my own: <a href="http://hype-free.blogspot.com/2009/01/sslfail.html" rel="nofollow">http://hype-free.blogspot.com/2009/01/sslfail.html</a></p>
<p>The results are incredible (incredibly sad): less than 5% of the sites have proper certs. If you would like to get the final list or the script I used, let me know (it can keep this blog updated for years <img src='http://www.sslfail.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> ).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcin</title>
		<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/comment-page-1/#comment-7</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Tue, 13 Jan 2009 20:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=3#comment-7</guid>
		<description>Michael, You do know you can install your own CA into IE and Firefox before you rollout.  This would prevent your users&#039; browsers from popping up an error on internally hosted applications using SSL.</description>
		<content:encoded><![CDATA[<p>Michael, You do know you can install your own CA into IE and Firefox before you rollout.  This would prevent your users&#8217; browsers from popping up an error on internally hosted applications using SSL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgraver</title>
		<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/comment-page-1/#comment-6</link>
		<dc:creator>jgraver</dc:creator>
		<pubDate>Tue, 13 Jan 2009 19:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=3#comment-6</guid>
		<description>Just wait until our posts on EV SSL Certs :-)

If you find some great sites with non-SSL logins, send us the link.</description>
		<content:encoded><![CDATA[<p>Just wait until our posts on EV SSL Certs <img src='http://www.sslfail.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>If you find some great sites with non-SSL logins, send us the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Dickey</title>
		<link>http://www.sslfail.com/2009/01/welcome-to-sslfail/comment-page-1/#comment-2</link>
		<dc:creator>Michael Dickey</dc:creator>
		<pubDate>Tue, 13 Jan 2009 16:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=3#comment-2</guid>
		<description>Pre-comment question: Are you accepted screenshots of prominent sites whose logins are not SSL-protected? :)


Ugh. The state of browsers right now has made screenshots of ssl failures so amazing. Every little discrepancy (or less money spent on &#039;normal&#039; certs) results in error pages. It&#039;s pretty ridiculous.

I can&#039;t wait to go to IE7/FF3 in my work environment (I use it, but it&#039;s not installed widely on users). I have about 40 internal-only web servers hosting roughly 300 different sites internally (mostly development copies of public sites). Every one is protected by a non-EV SSL internally-signed cert. Let alone almost all of my network devices...

The band-aid of error alerts and green address bars to increase user awareness doesn&#039;t work, and was a stupid idea in the first place (way to make more money for CAs). It would be just a minorly stupid idea if it weren&#039;t so forced... :(

Sorry, the state of SSL is a bit of a peeve of mine. I don&#039;t mind if a site like www.gmail.com uses the www.google.com SSL, but I do mind that browsers have moved away from pop-up warnings that can be turned off to obscure full-page warnings that make it sound like the site is evil and broken.</description>
		<content:encoded><![CDATA[<p>Pre-comment question: Are you accepted screenshots of prominent sites whose logins are not SSL-protected? <img src='http://www.sslfail.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Ugh. The state of browsers right now has made screenshots of ssl failures so amazing. Every little discrepancy (or less money spent on &#8216;normal&#8217; certs) results in error pages. It&#8217;s pretty ridiculous.</p>
<p>I can&#8217;t wait to go to IE7/FF3 in my work environment (I use it, but it&#8217;s not installed widely on users). I have about 40 internal-only web servers hosting roughly 300 different sites internally (mostly development copies of public sites). Every one is protected by a non-EV SSL internally-signed cert. Let alone almost all of my network devices&#8230;</p>
<p>The band-aid of error alerts and green address bars to increase user awareness doesn&#8217;t work, and was a stupid idea in the first place (way to make more money for CAs). It would be just a minorly stupid idea if it weren&#8217;t so forced&#8230; <img src='http://www.sslfail.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>Sorry, the state of SSL is a bit of a peeve of mine. I don&#8217;t mind if a site like <a href="http://www.gmail.com" rel="nofollow">http://www.gmail.com</a> uses the <a href="http://www.google.com" rel="nofollow">http://www.google.com</a> SSL, but I do mind that browsers have moved away from pop-up warnings that can be turned off to obscure full-page warnings that make it sound like the site is evil and broken.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
