<?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: SSLFail is SSL Enabled</title>
	<atom:link href="http://www.sslfail.com/2009/02/sslfail-is-ssl-enabled/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sslfail.com/2009/02/sslfail-is-ssl-enabled/</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: Tyler</title>
		<link>http://www.sslfail.com/2009/02/sslfail-is-ssl-enabled/comment-page-1/#comment-88</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Fri, 27 Feb 2009 11:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=283#comment-88</guid>
		<description>Michael,

I just said this on your other comment, but I&#039;ll repeat it here in case you don&#039;t see both... I figure the people wanting SSL wanted to bypass basic content filtering, meaning they only needed encryption not trust. 

I agree 100% that we shouldn&#039;t need SSL and for that reason I won&#039;t spend the money on a cert. That&#039;s why I provided the self signed cert, I haven&#039;t redirected HTTP to it, other than one link I&#039;m not advertising it... it&#039;s there for the people that want it. 

As for the CA Cert... I will add an addendum to the post. Personally I see humor in a cert signed by SSLFail, one of the reasons I shared it (I honestly don&#039;t expect much of a non-technical readership on a blog like this), but that is indeed my bad. 

Tyler.</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>I just said this on your other comment, but I&#8217;ll repeat it here in case you don&#8217;t see both&#8230; I figure the people wanting SSL wanted to bypass basic content filtering, meaning they only needed encryption not trust. </p>
<p>I agree 100% that we shouldn&#8217;t need SSL and for that reason I won&#8217;t spend the money on a cert. That&#8217;s why I provided the self signed cert, I haven&#8217;t redirected HTTP to it, other than one link I&#8217;m not advertising it&#8230; it&#8217;s there for the people that want it. </p>
<p>As for the CA Cert&#8230; I will add an addendum to the post. Personally I see humor in a cert signed by SSLFail, one of the reasons I shared it (I honestly don&#8217;t expect much of a non-technical readership on a blog like this), but that is indeed my bad. </p>
<p>Tyler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Coates</title>
		<link>http://www.sslfail.com/2009/02/sslfail-is-ssl-enabled/comment-page-1/#comment-82</link>
		<dc:creator>Michael Coates</dc:creator>
		<pubDate>Thu, 26 Feb 2009 16:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sslfail.com/?p=283#comment-82</guid>
		<description>Since this site is dedicated to the secure use of SSL, I think this approach is worth a bit of discussion. First off, I don&#039;t see any reason for this site to need SSL.  Not having SSL does not equal a problem. The need for SSL depends on whether the guarantees SSL provides are necessary - guarantees of integrity, confidentiality, reply prevention and end-point authentication.  Since this site is intended for people to read provided information, I don&#039;t personally see a reason for SSL.

Aside from that note, let&#039;s look at the practice of providing a certificate for download.  The link above allows a user to download the certificate to prevent the browser&#039;s warning message of unknown issuer. Since the certificate is available of http, a MitM could just as easily switch the URL so it points to there cert which they&#039;ve created for sslfail.com.  So, providing a cert for download over http provides zero security.

Now, to restate my original point. I bring this up only since this site is intended to discuss security of SSL and certificates. I really don&#039;t see any reason to use SSL for SSLfail.com.

-Michael</description>
		<content:encoded><![CDATA[<p>Since this site is dedicated to the secure use of SSL, I think this approach is worth a bit of discussion. First off, I don&#8217;t see any reason for this site to need SSL.  Not having SSL does not equal a problem. The need for SSL depends on whether the guarantees SSL provides are necessary &#8211; guarantees of integrity, confidentiality, reply prevention and end-point authentication.  Since this site is intended for people to read provided information, I don&#8217;t personally see a reason for SSL.</p>
<p>Aside from that note, let&#8217;s look at the practice of providing a certificate for download.  The link above allows a user to download the certificate to prevent the browser&#8217;s warning message of unknown issuer. Since the certificate is available of http, a MitM could just as easily switch the URL so it points to there cert which they&#8217;ve created for sslfail.com.  So, providing a cert for download over http provides zero security.</p>
<p>Now, to restate my original point. I bring this up only since this site is intended to discuss security of SSL and certificates. I really don&#8217;t see any reason to use SSL for SSLfail.com.</p>
<p>-Michael</p>
]]></content:encoded>
	</item>
</channel>
</rss>
