<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Technosailor.com &#187; web security</title>
	<atom:link href="http://technosailor.com/tag/web-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosailor.com</link>
	<description>Business and Technology with Common Sense</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:54:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19888</generator>
		<item>
		<title>How to Handle Security Flaws</title>
		<link>http://technosailor.com/2007/01/05/how-to-handle-security-flaws/</link>
		<comments>http://technosailor.com/2007/01/05/how-to-handle-security-flaws/#comments</comments>
		<pubDate>Sat, 06 Jan 2007 04:04:25 +0000</pubDate>
		<dc:creator>Aaron</dc:creator>
				<category><![CDATA[Aaron Brazell]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[web security]]></category>

		<guid isPermaLink="false">http://www.technosailor.com/how-to-handle-security-flaws/</guid>
		<description><![CDATA[Yesterday, over at Blog Herald, the new management demonstrated the entirely wrong way of handling security flaws. (The flaw I detailed here) WordPress celebrated it&#8217;s 500,000 install last month and cheers to them. The platform is stable, fast, easy to &#8230; <a href="http://technosailor.com/2007/01/05/how-to-handle-security-flaws/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Yesterday, over at <a href="http://www.blogherald.com">Blog Herald</a>, the new management demonstrated the <a href="http://www.blogherald.com/2007/01/04/wordpress-cross-site-scripting-vulnerability-in-templatesphp-uncovered/#comment-143079">entirely wrong way of handling security flaws</a>. (The flaw I detailed <a href="http://www.technosailor.com/wordpress-206-critical-security-release/">here</a>)</p>
<p>WordPress celebrated it&#8217;s 500,000 install last month and cheers to them. The platform is stable, fast, easy to use. It has no cumbersome plugin architecture (like Textpattern). That&#8217;s not to say that it has never had its share of security vulnerabilities. In fact, there have been a number of <a href="http://wordpress.org/development/2005/05/security-update/">documented fixes</a> over the years.</p>
<p>WordPress has it&#8217;s own contact address for securtiy issues. It is <a href="mailto:security@wordpress.org">security@wordpress.org</a>. In a dangerous world of XSS and SQL injection, the proper way to handle the discovery of a security flaw is to report it first and allow the vendor to provide a patch or a new version. I demonstrated this process when I reported the <a href="http://www.technosailor.com/democracy-plugin-xss-vulnerability-alert/">XSS flaw in the Democracy 1.2</a> plugin for WordPress. I alerted the plugin author, gave him an opportunity to provide a fixed version and he did.</p>
<p>That&#8217;s the responsible thing to do. Alert the autrhor. Let the vendor produce a fix. When a solution is handy, make the exploit public. Instead, J. Angelo Racoma, in his quest to be popular after buying Blog Herald, <a href="http://www.blogherald.com/2007/01/04/wordpress-cross-site-scripting-vulnerability-in-templatesphp-uncovered/">leaked the story</a> the day before WordPress 2.0.6 was released.</p>
<p>Now, I&#8217;m not in on the day to day conversations at <a href="http://www.automattic.com">Automattic</a>. I really have no idea if the release was scheduled for today or not. But regardless, reporting a bug that has not been publicized before ample time was provided for a bugfix, is irresponsible. The thousands of readers at the Blog Herald could very well have gone into a panic. The rumor mill could have begun to spin. And for what? Simply waiting a day or two would have meant Blog Herald could suggest installing WordPress 2.0.6. Instead, they mentioned a <em>beta</em> (read: could have bugs still) version of WordPress 2.0.6 was being publically tested.</p>
<p>J. Angelo&#8217;s comment to me was this:</p>
<blockquote><p>the news would&#8217;ve spread even without us posting about it, so I thought it best to post this as a warning. Patching WP to fix bugs would always be a good idea.</p></blockquote>
<p>Ah, but the word would spread after the public had been notified &#8211; which <a href="http://www.securityfocus.com/bid/21893">happened</a> <a href="http://www.securityfocus.com/bid/21896">today</a> with two reports &#8211; a day after J. Angelo decided to spook the world. Wave your hands in the air but offer no solution. Sounds like Democrats in Congress regarding Iraq.</p>
<p>Blog Herald&#8217;s reputation slipped with me <a href="http://www.technosailor.com/interview-with-matt-craven-on-the-sale-of-the-blog-herald/">ater the purchase from Matt Craven and BlogMedia</a>. This incident causes me less to trust them because it appears they are only concerned with getting the scoop and not behaving as good blogizens.</p>
]]></content:encoded>
			<wfw:commentRss>http://technosailor.com/2007/01/05/how-to-handle-security-flaws/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
	
	</item>
	</channel>
</rss>

