<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BlogSecurity &#187; Tools</title>
	<atom:link href="http://blogsecurity.net/category/wordpress/tools/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Mon, 22 Feb 2010 21:41:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>bs-wp-encrypt plugin: Encrypt Logins</title>
		<link>http://blogsecurity.net/wordpress/bs-wp-encrypt-plugin</link>
		<comments>http://blogsecurity.net/wordpress/bs-wp-encrypt-plugin#comments</comments>
		<pubDate>Wed, 09 Apr 2008 22:39:07 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress tools]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/bs-wp-encrypt-encrypt-logins/</guid>
		<description><![CDATA[
This simple plugin will ensure that all requests to &#8216;wp-login.php&#8217; and &#8216;wp-admin/*&#8217; are redirected over HTTPS. By using HTTPS you mitigate the risk of attackers capturing sensitive information such as usernames and passwords, which when accessed over HTTP provide no level of security.


Please ensure that your site supports HTTPS before enabling this plugin. This can [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/bs-wp-encrypt-plugin/feed</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>bs-wp-sandbox plugin: Lock WP Functions</title>
		<link>http://blogsecurity.net/wordpress/bs-wp-sandbox-plugin</link>
		<comments>http://blogsecurity.net/wordpress/bs-wp-sandbox-plugin#comments</comments>
		<pubDate>Wed, 26 Dec 2007 20:39:07 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/bs-wp-sandbox-plugin-lock-wp-functions/</guid>
		<description><![CDATA[The BlogSec WordPress Sandbox plugin works on a whitelist principle. We accept all pages and posts (including wp-admin, feeds and xmlrpc) but deny requests for any other resources or WordPress functions.
I came up with the idea for this plugin when developing my homepage WithDK.com (where it is currently being tested). I wanted WordPress to act [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/bs-wp-sandbox-plugin/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>bs-wp-noversion plugin: Removes WordPress Version</title>
		<link>http://blogsecurity.net/wordpress/bs-wp-noversion</link>
		<comments>http://blogsecurity.net/wordpress/bs-wp-noversion#comments</comments>
		<pubDate>Mon, 24 Dec 2007 13:44:51 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/bs-wp-noversion/</guid>
		<description><![CDATA[BlogSecurity Wordpress Noversion plugin (bs-wp-noversion), prevents WordPress version leakage. Another simple, yet extremely useful WordPress security plugin.

Alot of attackers and automated tools will try and determine software versions before launching exploit code. Removing your WordPress blog version may discourage some attackers and certainly will mitigate virus and worm programs that rely on software versions.


Plugin Name: [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/bs-wp-noversion/feed</wfw:commentRss>
		<slash:comments>42</slash:comments>
		</item>
		<item>
		<title>bs-wp-noerrors: removing WordPress DB errors</title>
		<link>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors</link>
		<comments>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors#comments</comments>
		<pubDate>Tue, 11 Dec 2007 13:40:04 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/</guid>
		<description><![CDATA[This plugin is now deprecated as of WordPress 2.3.2. WordPress 2.3.2 has error messages disable by default. This plugin may still be useful for those running older versions.
WordPress by default has error messaging turned on:

function show_errors() {
                $this->show_errors = true;
 [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/wpdberrors-plugin-removing-wordpress-db-errors/feed</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>WPIDS &#8211; WordPress Intruder Detection System</title>
		<link>http://blogsecurity.net/wordpress/wpids-wordpress-intruder-detection-system</link>
		<comments>http://blogsecurity.net/wordpress/wpids-wordpress-intruder-detection-system#comments</comments>
		<pubDate>Thu, 22 Nov 2007 03:00:52 +0000</pubDate>
		<dc:creator>Philipp</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wpids-wordpress-intruder-detection-system/</guid>
		<description><![CDATA[WPIDS is the WP port of PHPIDS, an Intrusion Detection system for PHP. With PHPIDS it&#8217;s possible to check all delivered user-generated content for malicious code, like SQL Injection/XSS/CSRF, and so on. In short, its a defense plugin for WordPress that BlogSec members have been working on for a few months now. I would say [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/wpids-wordpress-intruder-detection-system/feed</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Spambam: comments anti-spam plugin</title>
		<link>http://blogsecurity.net/wordpress/spambam-comment-anti-spam-plugin</link>
		<comments>http://blogsecurity.net/wordpress/spambam-comment-anti-spam-plugin#comments</comments>
		<pubDate>Wed, 26 Sep 2007 20:39:09 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/wordpress/spambam-comment-anti-spam-plugin/</guid>
		<description><![CDATA[
Anyone who is familiar with blogging is more then likely familiar with comment spam. It is a well known fact that 93% of comments are spam! In this article we discuss a little about comment spammers and discuss BlogSecurity&#8217;s latest project, Spambam!

The goal behind comment spam is to ultimately generate traffic for the attackers advertised [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/spambam-comment-anti-spam-plugin/feed</wfw:commentRss>
		<slash:comments>32</slash:comments>
		</item>
		<item>
		<title>WP Prefix Table Changer</title>
		<link>http://blogsecurity.net/wordpress/tool-130707</link>
		<comments>http://blogsecurity.net/wordpress/tool-130707#comments</comments>
		<pubDate>Fri, 13 Jul 2007 09:54:21 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=43</guid>
		<description><![CDATA[
Philipp Heinze developed WP Prefix Table Changer for the BlogSecurity toolbox. The idea came from Stefan Essar BlogSecurity Interview recently, where he suggested changing the WordPress table prefix from the default &#34;wp_&#34; to something a little more obscure to mitigate SQL Injection vulnerabilities. Nice job Phil.

This plugin is useful for two reasons:
Firstly, if your WordPress [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/tool-130707/feed</wfw:commentRss>
		<slash:comments>54</slash:comments>
		</item>
		<item>
		<title>WordPress Scanner Information Page</title>
		<link>http://blogsecurity.net/wordpress/tools/wp-scanner</link>
		<comments>http://blogsecurity.net/wordpress/tools/wp-scanner#comments</comments>
		<pubDate>Sat, 26 May 2007 14:25:08 +0000</pubDate>
		<dc:creator>DK</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[blog scanner]]></category>
		<category><![CDATA[vulnerability scanner]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wp-scanner]]></category>
		<category><![CDATA[wpscan]]></category>

		<guid isPermaLink="false">http://blogsecurity.net/?p=14</guid>
		<description><![CDATA[About us
BlogSecurity are security evangelists with a specific target on web 2.0 related security. Learn more about us.
Introduction
WordPress scanner is a free online resource that blog administrators can use to provide a measure of their wordpress security level. It is BETA software and is continually being developed.
This page is the primary help page for wp-scanner. [...]]]></description>
		<wfw:commentRss>http://blogsecurity.net/wordpress/tools/wp-scanner/feed</wfw:commentRss>
		<slash:comments>168</slash:comments>
		</item>
	</channel>
</rss>
