<?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>Weblog Tools Collection &#187; sql column truncation</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/sql-column-truncation/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Tue, 14 Feb 2012 14:00:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress 2.6.2 Released</title>
		<link>http://weblogtoolscollection.com/archives/2008/09/09/wordpress-262-released/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/09/09/wordpress-262-released/#comments</comments>
		<pubDate>Tue, 09 Sep 2008 04:03:00 +0000</pubDate>
		<dc:creator>Mark Ghosh</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[mt_rand]]></category>
		<category><![CDATA[sql column truncation]]></category>
		<category><![CDATA[wordpress 2.6.2]]></category>
		<category><![CDATA[wordpress upgrade]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=4115</guid>
		<description><![CDATA[WordPress 2.6.2.: This release is in response to a recent warning to developers from Stefan Esser about the dangers of SQL Column Truncation and weaknesses of mt_rand(). The issue at hand that forced the release is discussed in detail on the WordPress.org blog post linked above. Basically the attack is complex, is dependent on open registration being turned on in your blog, but can be executed in theory and turns out to be more of an annoyance than an actual exploit. If you have open registration on your blog, the WordPress.org team recommends that you upgrade your install to WordPress 2.6.2 A handful of other fixes are also included in this upgrade. Here is a list of changed files.]]></description>
			<content:encoded><![CDATA[<p><a href="http://wordpress.org/development/2008/09/wordpress-262/">WordPress 2.6.2</a>.: This release is in response to a <a href="http://blogs.zdnet.com/security/?p=1868">recent warning to developers</a> from <a href="http://www.suspekt.org/">Stefan Esser</a> about the dangers of <a href="http://www.suspekt.org/2008/08/18/mysql-and-sql-column-truncation-vulnerabilities/">SQL Column Truncation</a> and <a href="http://www.suspekt.org/2008/08/17/mt_srand-and-not-so-random-numbers/">weaknesses of mt_rand()</a>. The issue at hand that forced the release is discussed in detail on the WordPress.org blog post linked above. Basically the attack is complex, is dependent on open registration being turned on in your blog, but can be executed in theory and turns out to be more of an annoyance than an actual exploit.</p>
<p>If you have open registration on your blog, the WordPress.org team recommends that you upgrade your install to <a href="http://wordpress.org/download/">WordPress 2.6.2</a> A <a href="http://trac.wordpress.org/query?status=closed&amp;milestone=2.6.2&amp;resolution=fixed&amp;order=priority">handful of other fixes</a> are also included in this upgrade. Here is a list of <a href="http://trac.wordpress.org/changeset?old_path=tags%2F2.6.1&amp;old=8849&amp;new_path=tags%2F2.6.2&amp;new=8849">changed files</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/09/09/wordpress-262-released/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/sql-column-truncation/feed/ ) in 0.72656 seconds, on Feb 14th, 2012 at 5:07 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 6:07 pm UTC -->
