<?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 for SecurityCritics.org</title>
	<atom:link href="http://securitycritics.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://securitycritics.org</link>
	<description>Truthful, independent criticism of the computer security industrial complex</description>
	<lastBuildDate>Mon, 17 Aug 2009 22:26:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on &#8221;The need for computer security outweighs the profit of copyrights&#8221; by Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/08/17/copyright/comment-page-1/#comment-186</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Mon, 17 Aug 2009 22:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=775#comment-186</guid>
		<description>Journalist Wayne Rash noticed &lt;a target=_blank href=&quot;http://www.washingtonpost.com/wp-dyn/content/article/2009/07/31/AR2009073102476.html?hpid=opinionsbox1&quot; rel=&quot;nofollow&quot;&gt;an opinion piece&lt;/a&gt; in the &lt;cite&gt;Washington Post&lt;/cite&gt; titled &quot;The Death of Journalism.&quot;  Well worth the read.  You&#039;ll realize computer security mailing lists are part of the problem...</description>
		<content:encoded><![CDATA[<p>Journalist Wayne Rash noticed <a target=_blank href="http://www.washingtonpost.com/wp-dyn/content/article/2009/07/31/AR2009073102476.html?hpid=opinionsbox1" rel="nofollow">an opinion piece</a> in the <cite>Washington Post</cite> titled &#8220;The Death of Journalism.&#8221;  Well worth the read.  You&#8217;ll realize computer security mailing lists are part of the problem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8221;The need for computer security outweighs the profit of copyrights&#8221; by Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/08/17/copyright/comment-page-1/#comment-185</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Mon, 17 Aug 2009 20:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=775#comment-185</guid>
		<description>Radvanovsky&#039;s rationalization makes me wonder what excuse he&#039;ll come up with for Dan Goodin at The Register.  &quot;Bob, stop reprinting my stories like you did on 10 July.&quot;  And I wonder what he&#039;ll say to an editor at Govt&#039; Computer News.  &quot;Sir, stop reprinting our stories like you did on 18 May.&quot;  And I wonder how he&#039;d react to Janet Raloff at U.S. News &amp; World Report.  &quot;Dude, stop reprinting my stories like you did on 28 July...&quot;</description>
		<content:encoded><![CDATA[<p>Radvanovsky&#8217;s rationalization makes me wonder what excuse he&#8217;ll come up with for Dan Goodin at The Register.  &#8220;Bob, stop reprinting my stories like you did on 10 July.&#8221;  And I wonder what he&#8217;ll say to an editor at Govt&#8217; Computer News.  &#8220;Sir, stop reprinting our stories like you did on 18 May.&#8221;  And I wonder how he&#8217;d react to Janet Raloff at U.S. News &#038; World Report.  &#8220;Dude, stop reprinting my stories like you did on 28 July&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From the &#8220;we don&#8217;t make this up&#8221; dept: by Rob Rosenberger</title>
		<link>http://securitycritics.org/2008/04/28/goza/comment-page-1/#comment-146</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Thu, 16 Jul 2009 20:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=8#comment-146</guid>
		<description>Amazing catch, FMJohnson!  Yet another reason for Rob Goza to wince...  I wish I&#039;d caught that error myself.</description>
		<content:encoded><![CDATA[<p>Amazing catch, FMJohnson!  Yet another reason for Rob Goza to wince&#8230;  I wish I&#8217;d caught that error myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From the &#8220;we don&#8217;t make this up&#8221; dept: by FMJohnson</title>
		<link>http://securitycritics.org/2008/04/28/goza/comment-page-1/#comment-145</link>
		<dc:creator>FMJohnson</dc:creator>
		<pubDate>Thu, 16 Jul 2009 19:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=8#comment-145</guid>
		<description>&#039;The illustrative segue that brings “Mighty Eighth” alumni Jimmy Stewart into the picture (literally);&#039;

Even worse, Jimmy Stewart wasn&#039;t in &quot;North by Northwest&quot;; that was Cary Grant.</description>
		<content:encoded><![CDATA[<p>&#8216;The illustrative segue that brings “Mighty Eighth” alumni Jimmy Stewart into the picture (literally);&#8217;</p>
<p>Even worse, Jimmy Stewart wasn&#8217;t in &#8220;North by Northwest&#8221;; that was Cary Grant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oops!  McAfee expert slanders Armadillo, Themida by Joris Evers</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-134</link>
		<dc:creator>Joris Evers</dc:creator>
		<pubDate>Tue, 02 Jun 2009 22:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-134</guid>
		<description>A quick note from McAfee. The Muttik blog post is online as you noticed in your update, it was taken offline briefly just for a couple of additions. 
Joris Evers
McAfee PR</description>
		<content:encoded><![CDATA[<p>A quick note from McAfee. The Muttik blog post is online as you noticed in your update, it was taken offline briefly just for a couple of additions.<br />
Joris Evers<br />
McAfee PR</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oops!  McAfee expert slanders Armadillo, Themida by Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-132</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Sat, 30 May 2009 09:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-132</guid>
		<description>Update.  My RSS feed reader did something unusual: it retrieved a duplicate feed for Igor Muttik&#039;s column, as if it had been re-published.  A similar duplicate feed occurred for Guilherme Venere&#039;s column &quot;A closer look at Swine Flu spam&quot; (originally?) published on 1 May.</description>
		<content:encoded><![CDATA[<p>Update.  My RSS feed reader did something unusual: it retrieved a duplicate feed for Igor Muttik&#8217;s column, as if it had been re-published.  A similar duplicate feed occurred for Guilherme Venere&#8217;s column &#8220;A closer look at Swine Flu spam&#8221; (originally?) published on 1 May.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oops!  McAfee expert slanders Armadillo, Themida by Corrections &#38; clarifications</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-131</link>
		<dc:creator>Corrections &#38; clarifications</dc:creator>
		<pubDate>Sat, 30 May 2009 06:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-131</guid>
		<description>Roughly twelve hours after this column went to press, About.com antivirus expert Mary Landesman posted a comment on her blog to this column&#039;s author.  She noted the fact Igor Muttik&#039;s column was visible on McAfee&#039;s website.  Ms. Landesman questioned if Mr. Rosenberger made a mistake.  Mr. Rosenberger replied in a comment to Ms. Landesman:

&quot;I first questioned if the link in the RSS feed was broken. I checked it against the link you provided in your own RSS feed and they proved identical.  I surfed to the top of the Avert Labs Blog where I discovered no copy of Muttik’s column. A search on “elephant” failed to bring up any columns. A search of the May archive failed to bring it up. I concluded that direct visitors to the blog could not read Muttik’s column.  In hindsight, I should have taken snapshots of McAfee’s blog. (grrrr!)  I see you reviewed Muttik’s content for changes. I’ll do the same, then I’ll post an update to my own column.&quot;

At this time, Mr. Rosenberger believes McAfee did remove the column for a short period.  &quot;Content reviewers have the power to return any column to &#039;draft&#039; status,&quot; he explained.  &quot;I believe someone did this for a few hours with Igor Muttik&#039;s column.  Its temporary removal may perhaps have occurred as part of an op-ed review protocol.&quot;

Mr. Rosenberger concedes &quot;I didn&#039;t later re-test the broken link when I posted the text of Muttik&#039;s column; nor did I check Landesman&#039;s blog to see if she replied to the comment I left.&quot;  SecurityCritics.org will wait for public comment before deciding if this qualifies as a research failure during follow-up.

In the name of clarification, SecurityCritics.org will (1) change &quot;deleted&quot; to &quot;missing&quot; in the first paragraph&#039;s URL tooptip; (2) change &quot;deleted&quot; to &quot;missing&quot; in the excerpt; (3) change &quot;deleted&quot; to &quot;missing&quot; in the lead-in to the reprint of Mr. Muttik&#039;s column; (4) preface this column with an editor&#039;s note.

Mr. Rosenberger will contact McAfee&#039;s PR team to request their comment on why Mr. Muttik&#039;s column disappeared for a short time.</description>
		<content:encoded><![CDATA[<p>Roughly twelve hours after this column went to press, About.com antivirus expert Mary Landesman posted a comment on her blog to this column&#8217;s author.  She noted the fact Igor Muttik&#8217;s column was visible on McAfee&#8217;s website.  Ms. Landesman questioned if Mr. Rosenberger made a mistake.  Mr. Rosenberger replied in a comment to Ms. Landesman:</p>
<p>&#8220;I first questioned if the link in the RSS feed was broken. I checked it against the link you provided in your own RSS feed and they proved identical.  I surfed to the top of the Avert Labs Blog where I discovered no copy of Muttik’s column. A search on “elephant” failed to bring up any columns. A search of the May archive failed to bring it up. I concluded that direct visitors to the blog could not read Muttik’s column.  In hindsight, I should have taken snapshots of McAfee’s blog. (grrrr!)  I see you reviewed Muttik’s content for changes. I’ll do the same, then I’ll post an update to my own column.&#8221;</p>
<p>At this time, Mr. Rosenberger believes McAfee did remove the column for a short period.  &#8220;Content reviewers have the power to return any column to &#8216;draft&#8217; status,&#8221; he explained.  &#8220;I believe someone did this for a few hours with Igor Muttik&#8217;s column.  Its temporary removal may perhaps have occurred as part of an op-ed review protocol.&#8221;</p>
<p>Mr. Rosenberger concedes &#8220;I didn&#8217;t later re-test the broken link when I posted the text of Muttik&#8217;s column; nor did I check Landesman&#8217;s blog to see if she replied to the comment I left.&#8221;  SecurityCritics.org will wait for public comment before deciding if this qualifies as a research failure during follow-up.</p>
<p>In the name of clarification, SecurityCritics.org will (1) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the first paragraph&#8217;s URL tooptip; (2) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the excerpt; (3) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the lead-in to the reprint of Mr. Muttik&#8217;s column; (4) preface this column with an editor&#8217;s note.</p>
<p>Mr. Rosenberger will contact McAfee&#8217;s PR team to request their comment on why Mr. Muttik&#8217;s column disappeared for a short time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oops!  McAfee expert slanders Armadillo, Themida by Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-130</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Fri, 29 May 2009 20:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-130</guid>
		<description>The full text of Igor Muttik&#039;s missing blog entry follows, for your edification:

It is ironic but the extreme growth rate of malware attacks is actually partly due to how successful AV technology really is. Quite simply - if AV scanners were not so successful in blocking trojans and viruses there would be little need for the bad guys to write new ones. One can even say that malware writers are digging an elephant trap for all computer users because lots of new malware demands a response from AV, which can contribute to the slower operation of computers for all of us.

Figuratively speaking, the primary tools that the bad guys are using to dig their side of the trap and evade detection are packers (like UPX and Petite) and protectors (like Armadillo and Themida). Packers are legitimately used to reduce the size of programs (saving disk space), while protectors are legitimately used to prevent patching, hacking or reverse engineering. For malware production, however, packers and protectors are useful as they can often obfuscate original malware beyond recognition by AV.

Commercial protectors are especially loved by malware writers because they can put a protective envelope on top of, say, their spam-bot and it will be well hidden inside. Additionally, it will now really look more like a legitimate file obfuscated with the same protector. Malware writers use this trick more and more frequently.

As a result, on any average computer, AV can frequently encounter, say, a Themida-packed computer game and a Themida-packed spam-bot. To determine what is what an AV product has to know what is “under” the protecting envelope. Unfortunately, this simply cannot be done very quickly. It takes computing cycles…..

We would urge all developers who use software protection to think twice before doing so. There is an increasing risk that your legitimate files will be blocked by AV software by mistake or that there will be an unpleasant slowdown due to long analysis. Either can cause troubles for users. If you feel that you really must use an obfuscating protector at least digitally sign your files. That would reduce the level of suspicion by introducing traceability to the source.

The point is that software protectors are just not a secure software technology any longer because they have been misused so much. Do not use it if you can avoid it.</description>
		<content:encoded><![CDATA[<p>The full text of Igor Muttik&#8217;s missing blog entry follows, for your edification:</p>
<p>It is ironic but the extreme growth rate of malware attacks is actually partly due to how successful AV technology really is. Quite simply &#8211; if AV scanners were not so successful in blocking trojans and viruses there would be little need for the bad guys to write new ones. One can even say that malware writers are digging an elephant trap for all computer users because lots of new malware demands a response from AV, which can contribute to the slower operation of computers for all of us.</p>
<p>Figuratively speaking, the primary tools that the bad guys are using to dig their side of the trap and evade detection are packers (like UPX and Petite) and protectors (like Armadillo and Themida). Packers are legitimately used to reduce the size of programs (saving disk space), while protectors are legitimately used to prevent patching, hacking or reverse engineering. For malware production, however, packers and protectors are useful as they can often obfuscate original malware beyond recognition by AV.</p>
<p>Commercial protectors are especially loved by malware writers because they can put a protective envelope on top of, say, their spam-bot and it will be well hidden inside. Additionally, it will now really look more like a legitimate file obfuscated with the same protector. Malware writers use this trick more and more frequently.</p>
<p>As a result, on any average computer, AV can frequently encounter, say, a Themida-packed computer game and a Themida-packed spam-bot. To determine what is what an AV product has to know what is “under” the protecting envelope. Unfortunately, this simply cannot be done very quickly. It takes computing cycles…..</p>
<p>We would urge all developers who use software protection to think twice before doing so. There is an increasing risk that your legitimate files will be blocked by AV software by mistake or that there will be an unpleasant slowdown due to long analysis. Either can cause troubles for users. If you feel that you really must use an obfuscating protector at least digitally sign your files. That would reduce the level of suspicion by introducing traceability to the source.</p>
<p>The point is that software protectors are just not a secure software technology any longer because they have been misused so much. Do not use it if you can avoid it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virus cripples self-checkout aisles at Lowe&#8217;s hardware stores by Corrections &#38; Clarifications</title>
		<link>http://securitycritics.org/2009/03/08/lowes/comment-page-1/#comment-115</link>
		<dc:creator>Corrections &#38; Clarifications</dc:creator>
		<pubDate>Thu, 07 May 2009 00:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=595#comment-115</guid>
		<description>The RV friend who went to Lowes with Rob Rosenberger recalls the &quot;verbatim&quot; virus quote without the word &quot;computer.&quot;  Mr. Rosenberger believes his friend deserves the benefit of the doubt and agreed to place the word &quot;computer&quot; in brackets.</description>
		<content:encoded><![CDATA[<p>The RV friend who went to Lowes with Rob Rosenberger recalls the &#8220;verbatim&#8221; virus quote without the word &#8220;computer.&#8221;  Mr. Rosenberger believes his friend deserves the benefit of the doubt and agreed to place the word &#8220;computer&#8221; in brackets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virus cripples self-checkout aisles at Lowe&#8217;s hardware stores by Postle</title>
		<link>http://securitycritics.org/2009/03/08/lowes/comment-page-1/#comment-71</link>
		<dc:creator>Postle</dc:creator>
		<pubDate>Mon, 09 Mar 2009 17:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=595#comment-71</guid>
		<description>Intriguing. Not doubting YOU, Rob, or your analysis of the issue -- if it&#039;s true, it&#039;s disturbing on a number of levels. (I doubt I need to describe them.)
However, it may be worth noting that I made a purchase via a Lowe&#039;s self-checkout on Saturday afternoon (3/7) about 1PM, using a credit card. (Just tossed the receipt this morning.) I had no problems.
So, either the &quot;guard&quot; is lying about the scope of this thing, or well, I guess that&#039;s pretty much the only possible conclusion, other than to wonder whether *she* invented the story, or how high up the official ladder the story goes.
I do have to admit that I&#039;ve wondered - given that most self-checkout kiosks run OEM Windows XP, how long it would be before s/o decided to intentionally infect (or accidentally infected) those boxes. Will be an interesting story (or non-story) to follow.</description>
		<content:encoded><![CDATA[<p>Intriguing. Not doubting YOU, Rob, or your analysis of the issue &#8212; if it&#8217;s true, it&#8217;s disturbing on a number of levels. (I doubt I need to describe them.)<br />
However, it may be worth noting that I made a purchase via a Lowe&#8217;s self-checkout on Saturday afternoon (3/7) about 1PM, using a credit card. (Just tossed the receipt this morning.) I had no problems.<br />
So, either the &#8220;guard&#8221; is lying about the scope of this thing, or well, I guess that&#8217;s pretty much the only possible conclusion, other than to wonder whether *she* invented the story, or how high up the official ladder the story goes.<br />
I do have to admit that I&#8217;ve wondered &#8211; given that most self-checkout kiosks run OEM Windows XP, how long it would be before s/o decided to intentionally infect (or accidentally infected) those boxes. Will be an interesting story (or non-story) to follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
