<?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: WP Blogsecurify</title>
	<atom:link href="http://www.gnucitizen.org/blog/wp-blogsecurify/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/wp-blogsecurify/</link>
	<description>Information Security Think Tank</description>
	<lastBuildDate>Sat, 02 Feb 2013 17:50:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Featured Plugins for October &#124; Word Press Magazine</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-127631</link>
		<dc:creator>Featured Plugins for October &#124; Word Press Magazine</dc:creator>
		<pubDate>Thu, 16 Jul 2009 18:42:10 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-127631</guid>
		<description>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</description>
		<content:encoded><![CDATA[<p>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Featured Plugins for October&#160;&#124;&#160;Mamma Mac.com</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124335</link>
		<dc:creator>Featured Plugins for October&#160;&#124;&#160;Mamma Mac.com</dc:creator>
		<pubDate>Fri, 14 Nov 2008 07:18:21 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124335</guid>
		<description>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</description>
		<content:encoded><![CDATA[<p>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Featured Plugins for October &#8212; WPCandy &#8212; WordPress Themes, Plugins, Tips, and Tricks</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124243</link>
		<dc:creator>Featured Plugins for October &#8212; WPCandy &#8212; WordPress Themes, Plugins, Tips, and Tricks</dc:creator>
		<pubDate>Fri, 31 Oct 2008 10:09:32 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124243</guid>
		<description>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</description>
		<content:encoded><![CDATA[<p>[...] WP Blogsecurify 1.0 is a security plugin for WordPress designed to integrate several simple but important security patches for the popular blogging platform. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124174</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Mon, 27 Oct 2008 10:12:38 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124174</guid>
		<description>Hi Martin,

The plugin does a few things. First of all, it detects whether you want to authenticate or you are already authenticated. If yes, then it forces you over SSL. Underneath it is a bit more tricky. The plugin tries to guarantee that no matter what you do, your session identifiers never get sent over an unencrypted channel. The plugin uses its own cookies to keep your session state when browsing your site while authenticated. This mechanism preserves your user experience while enforcing extra security. In case of XSS, httpOnly is enabled to prevent damages. This only prevents session hijacking attacks though.

The plugin is coded in very clear fashion. It is easy to understand once you have a look at what it is inside.</description>
		<content:encoded><![CDATA[<p>Hi Martin,</p>
<p>The plugin does a few things. First of all, it detects whether you want to authenticate or you are already authenticated. If yes, then it forces you over SSL. Underneath it is a bit more tricky. The plugin tries to guarantee that no matter what you do, your session identifiers never get sent over an unencrypted channel. The plugin uses its own cookies to keep your session state when browsing your site while authenticated. This mechanism preserves your user experience while enforcing extra security. In case of XSS, httpOnly is enabled to prevent damages. This only prevents session hijacking attacks though.</p>
<p>The plugin is coded in very clear fashion. It is easy to understand once you have a look at what it is inside.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MartinJ</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124173</link>
		<dc:creator>MartinJ</dc:creator>
		<pubDate>Mon, 27 Oct 2008 09:27:32 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124173</guid>
		<description>Out of curiosity: How does the promised protection against session hijacking work? http_only?</description>
		<content:encoded><![CDATA[<p>Out of curiosity: How does the promised protection against session hijacking work? http_only?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ehmo</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124170</link>
		<dc:creator>ehmo</dc:creator>
		<pubDate>Sun, 26 Oct 2008 12:54:29 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124170</guid>
		<description>hey, i&#039;m sceptic. so far as i know, mostly blogs running on hostings, which don&#039;t have ssl connection allowed. i don&#039;t think that this is a good way. i&#039;ve some others ideas, which will protect ppl, but will not bounds them.

but good job anyway.</description>
		<content:encoded><![CDATA[<p>hey, i&#8217;m sceptic. so far as i know, mostly blogs running on hostings, which don&#8217;t have ssl connection allowed. i don&#8217;t think that this is a good way. i&#8217;ve some others ideas, which will protect ppl, but will not bounds them.</p>
<p>but good job anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dian</title>
		<link>http://www.gnucitizen.org/blog/wp-blogsecurify/comment-page-1/#comment-124168</link>
		<dc:creator>dian</dc:creator>
		<pubDate>Sun, 26 Oct 2008 12:35:10 +0000</pubDate>
		<guid isPermaLink="false">https://www.gnucitizen.org/?p=1675#comment-124168</guid>
		<description>i&#039;ve been reading your site along time, this one i&#039;m goin to use it in my site after wordpress 2.7 comes out. Thx for the tips guys :)</description>
		<content:encoded><![CDATA[<p>i&#8217;ve been reading your site along time, this one i&#8217;m goin to use it in my site after wordpress 2.7 comes out. Thx for the tips guys :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
