<?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: http versus https</title>
	<atom:link href="http://blogsecurity.net/wordpress/article-220807/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/article-220807</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Better Blogging Link Blast for September 14th, 2007 &#124; Better Blogging with Michael Martine</title>
		<link>http://blogsecurity.net/wordpress/article-220807/comment-page-1#comment-1050</link>
		<dc:creator>Better Blogging Link Blast for September 14th, 2007 &#124; Better Blogging with Michael Martine</dc:creator>
		<pubDate>Fri, 14 Sep 2007 11:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/article-220807/#comment-1050</guid>
		<description>[...] about WordPress security? You should be. Learn about accessing your WordPress admin via secure connection. at Blog Security, by David [...]</description>
		<content:encoded><![CDATA[<p>[...] about WordPress security? You should be. Learn about accessing your WordPress admin via secure connection. at Blog Security, by David [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/wordpress/article-220807/comment-page-1#comment-779</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Wed, 22 Aug 2007 16:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/article-220807/#comment-779</guid>
		<description>tenest, absolutely right, thanks for bringing it up.
&lt;blockquote&gt;
the browser will warn us if the certificate doesn&#039;t match the current site or if it a self-signed or a demo certificate, so watch out for this. 
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>tenest, absolutely right, thanks for bringing it up.</p>
<blockquote><p>
the browser will warn us if the certificate doesn&#8217;t match the current site or if it a self-signed or a demo certificate, so watch out for this.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: tenest</title>
		<link>http://blogsecurity.net/wordpress/article-220807/comment-page-1#comment-778</link>
		<dc:creator>tenest</dc:creator>
		<pubDate>Wed, 22 Aug 2007 16:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/article-220807/#comment-778</guid>
		<description>And on that same note, dont blindly accept SSL certs when you get an ssl cert error, otherwise you are STILL open to man-in-the-middle attacks even with https.</description>
		<content:encoded><![CDATA[<p>And on that same note, dont blindly accept SSL certs when you get an ssl cert error, otherwise you are STILL open to man-in-the-middle attacks even with https.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
