<?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, What Do You Think?</title>
	<atom:link href="http://unsakred.net/2008/06/25/full-disclosure-what-do-you-think/feed/" rel="self" type="application/rss+xml" />
	<link>http://unsakred.net/2008/06/25/full-disclosure-what-do-you-think/</link>
	<description>Yahoo! Messenger News, Software, Bug Tracking, Hacks, Tips, Tricks, Skins</description>
	<pubDate>Tue, 02 Dec 2008 00:16:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Ian Kenefick</title>
		<link>http://unsakred.net/2008/06/25/full-disclosure-what-do-you-think/#comment-303</link>
		<dc:creator>Ian Kenefick</dc:creator>
		<pubDate>Sat, 28 Jun 2008 15:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://unsakred.net/?p=71#comment-303</guid>
		<description>If the vendor fails to respond within a reasonable length of time it's necessary.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->If the vendor fails to respond within a reasonable length of time it&#8217;s necessary.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SGFC</title>
		<link>http://unsakred.net/2008/06/25/full-disclosure-what-do-you-think/#comment-296</link>
		<dc:creator>SGFC</dc:creator>
		<pubDate>Thu, 26 Jun 2008 10:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://unsakred.net/?p=71#comment-296</guid>
		<description>I believe it sometimes is necessary. Especially where Yahoo! Inc. is concerned. We are all familiar with Yahoo's slow responses to exploits found in their chat servers. Example the buffer exploit. 6+ months before it was finally patched after public consumption. Public consumption meaning released in various "programs" to effectively disrupt Yahoo! Chat. The latest exploit through Yahoo! Mobile was patched in a record breaking time. I totally agree with full disclosure unless the exploit is extremely dangerous.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->I believe it sometimes is necessary. Especially where Yahoo! Inc. is concerned. We are all familiar with Yahoo&#8217;s slow responses to exploits found in their chat servers. Example the buffer exploit. 6+ months before it was finally patched after public consumption. Public consumption meaning released in various &#8220;programs&#8221; to effectively disrupt Yahoo! Chat. The latest exploit through Yahoo! Mobile was patched in a record breaking time. I totally agree with full disclosure unless the exploit is extremely dangerous.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
