<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://whijo.net" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>exploit</title>
 <link>http://whijo.net/taxonomy/term/124/feed</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Stop the impending buffer overflow</title>
 <link>http://whijo.net/blog/brad/2006/08/16/stop-impending-buffer-overflow.html</link>
 <description>&lt;p&gt;I realised the other day that IRC clients and servers are prey to a terrible buffer flaw. People too often leave open &quot; and &#039; and even ( and {&#039;s in idle conversation. Imagine how many servers &lt;u&gt;Right now&lt;/u&gt; are filling up buffers and buffers of unclosed entities. I say we stop the madness now. Everyone needs to start chucking a few extra &quot;,&#039;,) and }&#039;s into their conversations, to &lt;strong&gt;Stop the impending buffer nightmare&lt;/strong&gt;. We don&#039;t know how many buffers are slowly ticking up, but we do know they are out there. Rather err on the side of caution, and stop those buffers &lt;u&gt;before it is too late&lt;/u&gt;. Imagine if the Internet crashed. Imagine how much extra work google&#039;s server farms do because of it. I am starting today. }}}}}))))&quot;&quot;&quot;&quot;&quot;&#039;&#039;&#039;&#039;&lt;/p&gt;</description>
 <comments>http://whijo.net/blog/brad/2006/08/16/stop-impending-buffer-overflow.html#comments</comments>
 <category domain="http://whijo.net/geek-tags/buffer-overflow">buffer overflow</category>
 <category domain="http://whijo.net/geek-tags/exploit">exploit</category>
 <category domain="http://whijo.net/tags/geek">geek</category>
 <pubDate>Wed, 16 Aug 2006 16:45:19 +0200</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">395 at http://whijo.net</guid>
</item>
</channel>
</rss>
