<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	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"
	>
<channel>
	<title>Comments on: Full disclosure</title>
	<atom:link href="http://thinkhole.org/wp/2006/08/10/full-disclosure/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkhole.org/wp/2006/08/10/full-disclosure/</link>
	<description>There should be one obvious way to do it.</description>
	<pubDate>Fri, 21 Nov 2008 08:35:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: import this. &#187; Blog Archive &#187; Security hole found in Django</title>
		<link>http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6450</link>
		<dc:creator>import this. &#187; Blog Archive &#187; Security hole found in Django</dc:creator>
		<pubDate>Thu, 17 Aug 2006 12:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6450</guid>
		<description>[...] Last Thursday (talking about Rails) I said: The time will come when each of the other frameworks will be found to have critical security flaws as well. [...]</description>
		<content:encoded><![CDATA[<p>[...] Last Thursday (talking about Rails) I said: The time will come when each of the other frameworks will be found to have critical security flaws as well. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6249</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Fri, 11 Aug 2006 22:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6249</guid>
		<description>The other frameworks, hopefully learned something from this.  Tell your users what the problem is.  Which is good, since RoR made a mistake, got thwacked in the knuckles, and made amends.  The others can then learn without having to go through it themselves.</description>
		<content:encoded><![CDATA[<p>The other frameworks, hopefully learned something from this.  Tell your users what the problem is.  Which is good, since RoR made a mistake, got thwacked in the knuckles, and made amends.  The others can then learn without having to go through it themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lon</title>
		<link>http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6241</link>
		<dc:creator>Lon</dc:creator>
		<pubDate>Fri, 11 Aug 2006 13:17:05 +0000</pubDate>
		<guid isPermaLink="false">http://thinkhole.org/wp/2006/08/10/full-disclosure/#comment-6241</guid>
		<description>I think what amuses me the most is the "internet time accelleration." This went from zero to full disclosure in about a day, with some security by obscurity thrown in the midst. It's been touted as a scandal of Lewiskian proportions but when you look back it was a 24 hour blip.

Not defending how it happened, just find it funny for such a short-term problem.</description>
		<content:encoded><![CDATA[<p>I think what amuses me the most is the &#8220;internet time accelleration.&#8221; This went from zero to full disclosure in about a day, with some security by obscurity thrown in the midst. It&#8217;s been touted as a scandal of Lewiskian proportions but when you look back it was a 24 hour blip.</p>
<p>Not defending how it happened, just find it funny for such a short-term problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
