<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: MoAB: Feh!</title>
	<atom:link href="http://www.extrapepperoni.com/2007/01/11/moab-feh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.extrapepperoni.com/2007/01/11/moab-feh/</link>
	<description>Chris Pepper on whatever (the non-Julia blog)</description>
	<pubDate>Tue, 06 Jan 2009 04:17:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: .:Computer Defense:. &#187; Oracle to release pre-patch notifications; Drama from MOAB.</title>
		<link>http://www.extrapepperoni.com/2007/01/11/moab-feh/comment-page-1/#comment-7</link>
		<dc:creator>.:Computer Defense:. &#187; Oracle to release pre-patch notifications; Drama from MOAB.</dc:creator>
		<pubDate>Fri, 12 Jan 2007 02:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.extrapepperoni.com/2007/01/11/moab-feh/#comment-7</guid>
		<description>&lt;p&gt;[...] Secondly it seems there&#8217;s been some interesting activities spurred from the MOAB project.Â  Apparently some &#8220;enterprising&#8221; individuals were scanning the directories where the new MOABs were being posted. To put a stop to this LMH put up a backdoored exploit ( Article 1 &#124; Article 2 ). I&#8217;m not sure I&#8217;m impressed with this&#8230; After reading LMH&#8217;s blog post on the subject and seeing this line, &#8220;It&#8217;s just that you&#8217;ve been caught doing a rather unethical business.&#8221;, yet I would say that backdooring the &#8220;pre-release&#8221; file is much worse. There are those that would say that putting something on a public website, whether or not you provide a link to it, makes it publicly available. If you don&#8217;t want people to have it, don&#8217;t add it to the website. In the first article I linked, there was mention of MOAB saying, &#8220;We didn&#8217;t install it, the user did&#8221;&#8230; and as the first article says, this is how plenty of malware spreads&#8230; Blaming the user is just wrong. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Secondly it seems there&#8217;s been some interesting activities spurred from the MOAB project.Â  Apparently some &#8220;enterprising&#8221; individuals were scanning the directories where the new MOABs were being posted. To put a stop to this LMH put up a backdoored exploit ( Article 1 | Article 2 ). I&#8217;m not sure I&#8217;m impressed with this&#8230; After reading LMH&#8217;s blog post on the subject and seeing this line, &#8220;It&#8217;s just that you&#8217;ve been caught doing a rather unethical business.&#8221;, yet I would say that backdooring the &#8220;pre-release&#8221; file is much worse. There are those that would say that putting something on a public website, whether or not you provide a link to it, makes it publicly available. If you don&#8217;t want people to have it, don&#8217;t add it to the website. In the first article I linked, there was mention of MOAB saying, &#8220;We didn&#8217;t install it, the user did&#8221;&#8230; and as the first article says, this is how plenty of malware spreads&#8230; Blaming the user is just wrong. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: On the Month of Apple Bugs, Backdoor Drama, and Why Security Researches Need Exceptional Ethics &#124; securosis.com</title>
		<link>http://www.extrapepperoni.com/2007/01/11/moab-feh/comment-page-1/#comment-6</link>
		<dc:creator>On the Month of Apple Bugs, Backdoor Drama, and Why Security Researches Need Exceptional Ethics &#124; securosis.com</dc:creator>
		<pubDate>Thu, 11 Jan 2007 23:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.extrapepperoni.com/2007/01/11/moab-feh/#comment-6</guid>
		<description>&lt;p&gt;[...] Being on the road this week, I missed the latest drama at the Month of Apple Bugs pointed out in this post by Chris Pepper. (One thing Chris doesn&#8217;t mention is that this backdoor was only included in a pre-release version of the exploit, not the released proof of concept code). [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Being on the road this week, I missed the latest drama at the Month of Apple Bugs pointed out in this post by Chris Pepper. (One thing Chris doesn&#8217;t mention is that this backdoor was only included in a pre-release version of the exploit, not the released proof of concept code). [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>
