<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss 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" version="2.0">
<channel>
	<title>BlogSec News</title>
	
	<link>http://blogsecurity.net</link>
	<description>Contribute and Enjoy!</description>
	<pubDate>Fri, 22 Aug 2008 09:40:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/BlogSecNews" type="application/rss+xml" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">1942143</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://www.feedburner.com</feedburner:feedburnerHostname><item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-11613</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Wed, 18 Jun 2008 09:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-11613</guid>
		<description>RE: Security in 2.3.3

&lt;blockquote&gt;
1) re 2.3.3 - Is version 2.3.3 secure? Are there any security issues with this version?
&lt;/blockquote&gt;
There have been some whispers in the dark so to speak, but no hard evidence that this version is vulnerable, see: http://blogsecurity.net/wordpress/wordpress-231-sql-injection-vulnerability/

&lt;blockquote&gt;
2) re 2.5 - Are the 3 security file updates in the 2.5.1 upgrade only for 2.5? Does the security hole that is fixed in 2.5.1 exist in 2.3.3 as well?
&lt;/blockquote&gt;

No, I believe 2.3.3 is unaffected by some of the recent vulnerabilities in 2.5x.

&lt;blockquote&gt;
3) Can I safely assume that if WordPress’s “Hardening WordPress” procedures
http://codex.wordpress.org/Hardening_WordPress

or BlogSecurity.net’s “How to create a secure WordPress install v1.1″
blogsecurity.net/projects/secure-wp-whitepaper.pdf

are applied that ANY version of WordPress would then be secure?
&lt;/blockquote&gt;

Applying these guidelines would certainly provide additional layers of security buying you time to apply the needed fixes as they are released, however, it cannot guarantee your security.

&lt;blockquote&gt;
4) It seems that 2.5.1 only has feature enhancements?
Do I have to go with version 2.5.1 for security reasons?
&lt;/blockquote&gt;

At the moment a number of people are still using the latest 2.3x branch, however, WordPress does suggest you upgrade to 2.5.1.

Hope this helps.</description>
		<content:encoded><![CDATA[<p>RE: Security in 2.3.3</p>
<blockquote><p>
1) re 2.3.3 - Is version 2.3.3 secure? Are there any security issues with this version?
</p></blockquote>
<p>There have been some whispers in the dark so to speak, but no hard evidence that this version is vulnerable, see: <a href="http://blogsecurity.net/wordpress/wordpress-231-sql-injection-vulnerability/" rel="nofollow">http://blogsecurity.net/wordpress/wordpress-231-sql-injection-vulnerability/</a></p>
<blockquote><p>
2) re 2.5 - Are the 3 security file updates in the 2.5.1 upgrade only for 2.5? Does the security hole that is fixed in 2.5.1 exist in 2.3.3 as well?
</p></blockquote>
<p>No, I believe 2.3.3 is unaffected by some of the recent vulnerabilities in 2.5x.</p>
<blockquote><p>
3) Can I safely assume that if WordPress’s “Hardening WordPress” procedures<br />
<a href="http://codex.wordpress.org/Hardening_WordPress" rel="nofollow">http://codex.wordpress.org/Hardening_WordPress</a></p>
<p>or BlogSecurity.net’s “How to create a secure WordPress install v1.1″<br />
blogsecurity.net/projects/secure-wp-whitepaper.pdf</p>
<p>are applied that ANY version of WordPress would then be secure?
</p></blockquote>
<p>Applying these guidelines would certainly provide additional layers of security buying you time to apply the needed fixes as they are released, however, it cannot guarantee your security.</p>
<blockquote><p>
4) It seems that 2.5.1 only has feature enhancements?<br />
Do I have to go with version 2.5.1 for security reasons?
</p></blockquote>
<p>At the moment a number of people are still using the latest 2.3x branch, however, WordPress does suggest you upgrade to 2.5.1.</p>
<p>Hope this helps.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=divB8I"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=divB8I" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=FA6StI"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=FA6StI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=2vdIei"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=2vdIei" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=s2ulxI"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=s2ulxI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=25P0Ji"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=25P0Ji" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: jbiethan</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-11610</link>
		<dc:creator>jbiethan</dc:creator>
		<pubDate>Tue, 17 Jun 2008 18:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-11610</guid>
		<description>Security in 2.3.3

I have several questions regarding security and version 2.3.3.

1) re 2.3.3 - Is version 2.3.3 secure? Are there any security issues with this version?

2) re 2.5 - Are the 3 security file updates in the 2.5.1 upgrade only for 2.5? Does the security hole that is fixed in 2.5.1 exist in 2.3.3 as well?

3) Can I safely assume that if WordPress's "Hardening WordPress" procedures
http://codex.wordpress.org/Hardening_WordPress

or BlogSecurity.net's "How to create a secure WordPress install v1.1"
blogsecurity.net/projects/secure-wp-whitepaper.pdf

are applied that ANY version of WordPress would then be secure?

4) It seems that 2.5.1 only has feature enhancements?
Do I have to go with version 2.5.1 for security reasons?</description>
		<content:encoded><![CDATA[<p>Security in 2.3.3</p>
<p>I have several questions regarding security and version 2.3.3.</p>
<p>1) re 2.3.3 - Is version 2.3.3 secure? Are there any security issues with this version?</p>
<p>2) re 2.5 - Are the 3 security file updates in the 2.5.1 upgrade only for 2.5? Does the security hole that is fixed in 2.5.1 exist in 2.3.3 as well?</p>
<p>3) Can I safely assume that if WordPress&#8217;s &#8220;Hardening WordPress&#8221; procedures<br />
<a href="http://codex.wordpress.org/Hardening_WordPress" rel="nofollow">http://codex.wordpress.org/Hardening_WordPress</a></p>
<p>or BlogSecurity.net&#8217;s &#8220;How to create a secure WordPress install v1.1&#8243;<br />
blogsecurity.net/projects/secure-wp-whitepaper.pdf</p>
<p>are applied that ANY version of WordPress would then be secure?</p>
<p>4) It seems that 2.5.1 only has feature enhancements?<br />
Do I have to go with version 2.5.1 for security reasons?</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=r54vOI"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=r54vOI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=tRNbnI"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=tRNbnI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=i8jQKi"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=i8jQKi" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=2aaVmI"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=2aaVmI" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=HdqbIi"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=HdqbIi" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-11222</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Sat, 17 May 2008 18:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-11222</guid>
		<description>The WPLite project looks quite cool. Check it out here: http://mahalkita.nanogeex.com/wplite/

Will have to take a look at this in more detail.</description>
		<content:encoded><![CDATA[<p>The WPLite project looks quite cool. Check it out here: <a href="http://mahalkita.nanogeex.com/wplite/" rel="nofollow">http://mahalkita.nanogeex.com/wplite/</a></p>
<p>Will have to take a look at this in more detail.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=6FORZH"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=6FORZH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=eDrRBH"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=eDrRBH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=2VPTQh"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=2VPTQh" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=Jj4PhH"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=Jj4PhH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=gFiJhh"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=gFiJhh" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: Wolfgang Digo Hollin</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-11078</link>
		<dc:creator>Wolfgang Digo Hollin</dc:creator>
		<pubDate>Mon, 12 May 2008 18:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-11078</guid>
		<description>Hello! Some time ago I released a plugin for Wordpress: DigoWatchWP.

The plugin will monitor your WP-posts and pages. Whenever an entry has been changed it informs you via email. So if you receive an email and you have nothing changed you should have a closer look at your post or page. Maybe somebody changed your post or page to include a spam-link (e.g. links to OnlineCasino, adult-content are very popular).

The plugin can be downloaded here: http://wordpress.org/extend/plugins/digowatchwp/

Ciao
digo
http://www.showhypnose.org</description>
		<content:encoded><![CDATA[<p>Hello! Some time ago I released a plugin for Wordpress: DigoWatchWP.</p>
<p>The plugin will monitor your WP-posts and pages. Whenever an entry has been changed it informs you via email. So if you receive an email and you have nothing changed you should have a closer look at your post or page. Maybe somebody changed your post or page to include a spam-link (e.g. links to OnlineCasino, adult-content are very popular).</p>
<p>The plugin can be downloaded here: <a href="http://wordpress.org/extend/plugins/digowatchwp/" rel="nofollow">http://wordpress.org/extend/plugins/digowatchwp/</a></p>
<p>Ciao<br />
digo<br />
<a href="http://www.showhypnose.org" rel="nofollow">http://www.showhypnose.org</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=eyZaDH"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=eyZaDH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=n9Fj5H"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=n9Fj5H" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=fAkkAh"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=fAkkAh" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=HJqnWH"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=HJqnWH" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=lNGFPh"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=lNGFPh" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Clark</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10919</link>
		<dc:creator>Michael Clark</dc:creator>
		<pubDate>Wed, 30 Apr 2008 03:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10919</guid>
		<description>I've just released a new tool for your security arsenal to be used to protect your WordPress installation. It's a set of scripts that will monitor the WordPress files for changes. Details at http://www.planetmike.com/goto/720</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just released a new tool for your security arsenal to be used to protect your WordPress installation. It&#8217;s a set of scripts that will monitor the WordPress files for changes. Details at <a href="http://www.planetmike.com/goto/720" rel="nofollow">http://www.planetmike.com/goto/720</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=ILFHSG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=ILFHSG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=SMfWPG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=SMfWPG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=GLCwHg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=GLCwHg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=9ROMiG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=9ROMiG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=kiJXfg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=kiJXfg" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10844</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Mon, 28 Apr 2008 23:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10844</guid>
		<description>BlogSec Changes: Modified Feedburner to allow page feeds; Added Gravatars; Added Feeds for BlogSec-News; Added BlogSec-News Banner on main.</description>
		<content:encoded><![CDATA[<p>BlogSec Changes: Modified Feedburner to allow page feeds; Added Gravatars; Added Feeds for BlogSec-News; Added BlogSec-News Banner on main.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=c586JG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=c586JG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=iK8JHG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=iK8JHG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=CG95wg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=CG95wg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=LdPuRG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=LdPuRG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=dL8Npg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=dL8Npg" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10804</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Mon, 28 Apr 2008 08:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10804</guid>
		<description>&lt;a href="http://copesflavio.com/en" rel="nofollow"&gt;Flavio Copes&lt;/a&gt; has provided an &lt;a href="http://blogsecurity.net/wordpress/wordpress-security-whitepaper/" rel="nofollow"&gt;Italian version of our popular WordPress Whitepaper.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://copesflavio.com/en" rel="nofollow">Flavio Copes</a> has provided an <a href="http://blogsecurity.net/wordpress/wordpress-security-whitepaper/" rel="nofollow">Italian version of our popular WordPress Whitepaper.</a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=srdMnG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=srdMnG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=umzHuG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=umzHuG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=SNRuKg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=SNRuKg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=ybn7GG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=ybn7GG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=Fpe3jg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=Fpe3jg" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10760</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Sun, 27 Apr 2008 12:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10760</guid>
		<description>Was playing with Automatic's &lt;a href="http://en.gravatar.com/" rel="nofollow"&gt;Gravatars&lt;/a&gt; (central blog user pictures). I think they have done it the right way by uploading all images to their servers. 

I can't think of any immediate security concerns, unless the Gravatars server is actually compromised. If this is done, it means an attacker could perform some rather devious attacks, affecting all blogs using Gravatars.</description>
		<content:encoded><![CDATA[<p>Was playing with Automatic&#8217;s <a href="http://en.gravatar.com/" rel="nofollow">Gravatars</a> (central blog user pictures). I think they have done it the right way by uploading all images to their servers. </p>
<p>I can&#8217;t think of any immediate security concerns, unless the Gravatars server is actually compromised. If this is done, it means an attacker could perform some rather devious attacks, affecting all blogs using Gravatars.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=DeJMYG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=DeJMYG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=aIi7HG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=aIi7HG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=xJMldg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=xJMldg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=JILltG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=JILltG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=H6Xf1g"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=H6Xf1g" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: Dani</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10650</link>
		<dc:creator>Dani</dc:creator>
		<pubDate>Fri, 25 Apr 2008 14:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10650</guid>
		<description>In response to the growing concerns that social network site user’s have had over privacy, Flugpo ( http://www.flugpo.com )has sponsored the development of a plug-in to help counteract the collection and sale of personal information. 

This plug-in will be available through &lt;a href="http://www.mydataismydata.org" rel="nofollow"&gt;MyDataIsMyData.org&lt;/a&gt;.  The plug-in (a small toolbar) allows each user to decide what information they will delete off their computer and what they will make visible as well as alerting them whenever they enter a site that is collaborating with a social network to sell their personal information. Selling private information for profit unbeknownst to the user’s is an abuse of their trust and MyDataIsMyData.org hopes to empower these user’s by allowing them to control the amount of personal information that they make visible.</description>
		<content:encoded><![CDATA[<p>In response to the growing concerns that social network site user’s have had over privacy, Flugpo ( <a href="http://www.flugpo.com" rel="nofollow">http://www.flugpo.com</a> )has sponsored the development of a plug-in to help counteract the collection and sale of personal information. </p>
<p>This plug-in will be available through <a href="http://www.mydataismydata.org" rel="nofollow">MyDataIsMyData.org</a>.  The plug-in (a small toolbar) allows each user to decide what information they will delete off their computer and what they will make visible as well as alerting them whenever they enter a site that is collaborating with a social network to sell their personal information. Selling private information for profit unbeknownst to the user’s is an abuse of their trust and MyDataIsMyData.org hopes to empower these user’s by allowing them to control the amount of personal information that they make visible.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=0LJ25G"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=0LJ25G" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=PjtIzG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=PjtIzG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=Wb3Xag"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=Wb3Xag" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=wMxsaG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=wMxsaG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=sBBiig"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=sBBiig" border="0"></img></a>
</div>]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/blogsec-news/#comment-10612</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Thu, 24 Apr 2008 22:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/blogsec-news/#comment-10612</guid>
		<description>Dan, its a shame you guys don't provide a free, open source version.</description>
		<content:encoded><![CDATA[<p>Dan, its a shame you guys don&#8217;t provide a free, open source version.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/BlogSecNews?a=03qZPG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=03qZPG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=aAbdIG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=aAbdIG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=oZ0Bgg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=oZ0Bgg" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=AxflUG"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=AxflUG" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/BlogSecNews?a=XbYUTg"><img src="http://feeds.feedburner.com/~f/BlogSecNews?i=XbYUTg" border="0"></img></a>
</div>]]></content:encoded>
	</item>
</channel>
</rss>
