<?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: Why Mac Security Matters: OS X Rootkit Hunter</title>
	<atom:link href="http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/feed/" rel="self" type="application/rss+xml" />
	<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/</link>
	<description>TheAppleBlog, published by and for the day-to-day Apple user, is a prominent source for news, reviews, walkthroughs, and real life application of all Apple products.</description>
	<pubDate>Wed, 03 Dec 2008 00:08:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-121233</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Fri, 26 Sep 2008 23:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-121233</guid>
		<description>Good comment, Matt. But to clarify something, when these vulnerabilities say "may cause unwanted code execution", it doesn't mean that it actually *can*. It just means that they haven't ruled out the possibility. It's generally very tricky to actually turn a buffer overflow into an exploit, and just as hard to prove that it can't. So most of these vulnerabilities get patched without ever knowing if they were a real vector for attack, or just a simple crash.</description>
		<content:encoded><![CDATA[<p>Good comment, Matt. But to clarify something, when these vulnerabilities say &#8220;may cause unwanted code execution&#8221;, it doesn&#8217;t mean that it actually *can*. It just means that they haven&#8217;t ruled out the possibility. It&#8217;s generally very tricky to actually turn a buffer overflow into an exploit, and just as hard to prove that it can&#8217;t. So most of these vulnerabilities get patched without ever knowing if they were a real vector for attack, or just a simple crash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-121214</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 26 Sep 2008 15:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-121214</guid>
		<description>I tend to read security reports I find in the tech press with a large grain of Kosher Salt. The general security in OS X works well with a few notable items. Strangely, although these holes are widely known and perhaps even easily exploited they continue to NOT be exploited. Just like the Quicktime vulnerabilities that always seem to state 'May cause unwanted code execution' (The ever present buffer overflow issue everyone seems to get hit by)

I have my doubts as to how well, or even at all that they could actually be utilized.

Certainly we can look back on the past 3 or 4 years to stories surfacing in January that 'THIS IS THE YEAR FOR THE MAC VIRUS" only to find exploits available, exploits 'supposedly' IN THE WILD that never amount to anything. If it genuinely, fully is as easy to pwn (Ghod I hate l33t, it's so 1993) an OSX machine then there oughta be millions of zombied macs out there happily buzzing away.

As for Trojans, I can't see how any real defense can be made against them other than understanding you can’t download whatever the devil you wish from the Internet. The OS is SUPPOSED to run applications for heavens sake. Now, one can make sure certain vital organs are not dangling out to get hit by the Trojan’s sword and I think OS X does a reasonably good job doing so.

So what am I saying with this rambling missive?

I'm saying this, have the tools at hand, but don't be an idiot! I ran on Windows for years with nary a security app and the like and never got hit. Behind OS X I might as well be behind a wall of armor plate steel compared to my windows days.</description>
		<content:encoded><![CDATA[<p>I tend to read security reports I find in the tech press with a large grain of Kosher Salt. The general security in OS X works well with a few notable items. Strangely, although these holes are widely known and perhaps even easily exploited they continue to NOT be exploited. Just like the Quicktime vulnerabilities that always seem to state &#8216;May cause unwanted code execution&#8217; (The ever present buffer overflow issue everyone seems to get hit by)</p>
<p>I have my doubts as to how well, or even at all that they could actually be utilized.</p>
<p>Certainly we can look back on the past 3 or 4 years to stories surfacing in January that &#8216;THIS IS THE YEAR FOR THE MAC VIRUS&#8221; only to find exploits available, exploits &#8217;supposedly&#8217; IN THE WILD that never amount to anything. If it genuinely, fully is as easy to pwn (Ghod I hate l33t, it&#8217;s so 1993) an OSX machine then there oughta be millions of zombied macs out there happily buzzing away.</p>
<p>As for Trojans, I can&#8217;t see how any real defense can be made against them other than understanding you can’t download whatever the devil you wish from the Internet. The OS is SUPPOSED to run applications for heavens sake. Now, one can make sure certain vital organs are not dangling out to get hit by the Trojan’s sword and I think OS X does a reasonably good job doing so.</p>
<p>So what am I saying with this rambling missive?</p>
<p>I&#8217;m saying this, have the tools at hand, but don&#8217;t be an idiot! I ran on Windows for years with nary a security app and the like and never got hit. Behind OS X I might as well be behind a wall of armor plate steel compared to my windows days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ex2bot</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-119197</link>
		<dc:creator>ex2bot</dc:creator>
		<pubDate>Tue, 05 Aug 2008 02:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-119197</guid>
		<description>Joe,

You may have missed something in the article. The last sentence indicates that Apple has hardened their update mechanism against a man-in-the-middle attack such as this. Just because these fools (the people who created Evilgrade) SAY they can attack OS X's Software Update doesn't make it so.

From the article (http://blogs.pcmag.com/securitywatch/2008/07/evilgrade_exploit_toolkit_atta.php accessed on 8/4/08):

"Krebs also reports that, contrary to the claims of Evilgrade's authors, Apple has strengthened their update mechanism to defeat this attack. "

Bot</description>
		<content:encoded><![CDATA[<p>Joe,</p>
<p>You may have missed something in the article. The last sentence indicates that Apple has hardened their update mechanism against a man-in-the-middle attack such as this. Just because these fools (the people who created Evilgrade) SAY they can attack OS X&#8217;s Software Update doesn&#8217;t make it so.</p>
<p>From the article (http://blogs.pcmag.com/securitywatch/2008/07/evilgrade_exploit_toolkit_atta.php accessed on 8/4/08):</p>
<p>&#8220;Krebs also reports that, contrary to the claims of Evilgrade&#8217;s authors, Apple has strengthened their update mechanism to defeat this attack. &#8221;</p>
<p>Bot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-119118</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Sun, 03 Aug 2008 17:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-119118</guid>
		<description>New Rootkit - installs via updates: Reason to Scan for Rootkits 
 
http://blogs.pcmag.com/securitywatch/2008/07/evilgrade_exploit_toolkit_atta.php</description>
		<content:encoded><![CDATA[<p>New Rootkit - installs via updates: Reason to Scan for Rootkits </p>
<p><a href="http://blogs.pcmag.com/securitywatch/2008/07/evilgrade_exploit_toolkit_atta.php" rel="nofollow">http://blogs.pcmag.com/securitywatch/2008/07/evilgrade_exploit_toolkit_atta.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114511</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 19 Feb 2008 21:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114511</guid>
		<description>Awesome. Just found RootKit Hunter on VersionTracker and wasn't sure if I should trust it. Great write - appreciate the post.</description>
		<content:encoded><![CDATA[<p>Awesome. Just found RootKit Hunter on VersionTracker and wasn&#8217;t sure if I should trust it. Great write - appreciate the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinod</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114191</link>
		<dc:creator>Vinod</dc:creator>
		<pubDate>Tue, 05 Feb 2008 22:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114191</guid>
		<description>oh my first Kernel panic!.. Thanks for letting me know. I promptly uninstalled the beast.</description>
		<content:encoded><![CDATA[<p>oh my first Kernel panic!.. Thanks for letting me know. I promptly uninstalled the beast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114186</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Tue, 05 Feb 2008 21:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114186</guid>
		<description>CJ: Yes, Quicktime vulnerabilities are not a good thing, but Apple is good about pushing out security updates, and I've never actually heard of an exploit in the wild for one of these vulnerabilities.

As for ClamAV, yes, that's for detecting Windows malware. Don't even bother looking for something to detect OS X malware, though, as that hinges upon the assumption that there is OS X malware, which is, for all practical purposes, untrue.</description>
		<content:encoded><![CDATA[<p>CJ: Yes, Quicktime vulnerabilities are not a good thing, but Apple is good about pushing out security updates, and I&#8217;ve never actually heard of an exploit in the wild for one of these vulnerabilities.</p>
<p>As for ClamAV, yes, that&#8217;s for detecting Windows malware. Don&#8217;t even bother looking for something to detect OS X malware, though, as that hinges upon the assumption that there is OS X malware, which is, for all practical purposes, untrue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CJ</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114176</link>
		<dc:creator>CJ</dc:creator>
		<pubDate>Tue, 05 Feb 2008 21:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114176</guid>
		<description>Hello!

I know OS X is generally more secure than Windows, but hearing lately about Quicktime vulnerabilities where code can be executed and what not makes me a little worried.

Reading ClamXav website, it doesn't look like it's a security software for OS X. It looks like it's basically security software for Windows PCs that runs on OS X to make sure you don't spread Windows malware. Can it even detect OS X malware? I'm looking for something that can.</description>
		<content:encoded><![CDATA[<p>Hello!</p>
<p>I know OS X is generally more secure than Windows, but hearing lately about Quicktime vulnerabilities where code can be executed and what not makes me a little worried.</p>
<p>Reading ClamXav website, it doesn&#8217;t look like it&#8217;s a security software for OS X. It looks like it&#8217;s basically security software for Windows PCs that runs on OS X to make sure you don&#8217;t spread Windows malware. Can it even detect OS X malware? I&#8217;m looking for something that can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114138</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Mon, 04 Feb 2008 22:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114138</guid>
		<description>Vinod - You saw a Kernel Panic. If this software triggered a Kernel Panic, then this software is even worse than I thought. In any case, no, you are not infected. Kernel Panics are rare, but they do happen. If you see another Kernel Panic, you might want to consider having your hardware checked out at your local Apple Store, as it might indicate damaged or faulty hardware. It's also possible that this software behaves much worse than I thought and is mucking around with your system. I certainly hope it's not.

In any case, I recommend uninstalling this software, as it is completely useless.</description>
		<content:encoded><![CDATA[<p>Vinod - You saw a Kernel Panic. If this software triggered a Kernel Panic, then this software is even worse than I thought. In any case, no, you are not infected. Kernel Panics are rare, but they do happen. If you see another Kernel Panic, you might want to consider having your hardware checked out at your local Apple Store, as it might indicate damaged or faulty hardware. It&#8217;s also possible that this software behaves much worse than I thought and is mucking around with your system. I certainly hope it&#8217;s not.</p>
<p>In any case, I recommend uninstalling this software, as it is completely useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinod</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114135</link>
		<dc:creator>Vinod</dc:creator>
		<pubDate>Mon, 04 Feb 2008 21:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-114135</guid>
		<description>I installed this and after installation, during the first run, the system asked me to power-off (in multiple language). Does that mean my Mac was infected?</description>
		<content:encoded><![CDATA[<p>I installed this and after installation, during the first run, the system asked me to power-off (in multiple language). Does that mean my Mac was infected?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OS X Rootkit Scanner at philippe::niquille</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113991</link>
		<dc:creator>OS X Rootkit Scanner at philippe::niquille</dc:creator>
		<pubDate>Sun, 27 Jan 2008 16:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113991</guid>
		<description>[...] by a post on theappleblog.com I installed the rkhunter and wrapper program in order to do a system scan for [...]</description>
		<content:encoded><![CDATA[<p>[...] by a post on theappleblog.com I installed the rkhunter and wrapper program in order to do a system scan for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Around the Net Links - MacTips</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113959</link>
		<dc:creator>Around the Net Links - MacTips</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113959</guid>
		<description>[...] AirFacebook IM Client Social.im Now Available For MacChat with your Facebook friends through Adium.Why Mac Security Matters: OS X Rootkit Hunter - The Apple BlogGood article from TAB on why Mac security is still important.UNIX tips: Learn 10 good UNIX usage [...]</description>
		<content:encoded><![CDATA[<p>[...] AirFacebook IM Client Social.im Now Available For MacChat with your Facebook friends through Adium.Why Mac Security Matters: OS X Rootkit Hunter - The Apple BlogGood article from TAB on why Mac security is still important.UNIX tips: Learn 10 good UNIX usage [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Localiza posibles rootkits en tu OS X con Rootkit Hunter &#124; SomosMac</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113936</link>
		<dc:creator>Localiza posibles rootkits en tu OS X con Rootkit Hunter &#124; SomosMac</dc:creator>
		<pubDate>Fri, 25 Jan 2008 18:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113936</guid>
		<description>[...] The Apple Blog    Seguridad, Actualidad, BSD, detección, herramienta, rootkit, Rootkit Hunter       var uri = [...]</description>
		<content:encoded><![CDATA[<p>[...] The Apple Blog    Seguridad, Actualidad, BSD, detección, herramienta, rootkit, Rootkit Hunter       var uri = [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113924</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Fri, 25 Jan 2008 04:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113924</guid>
		<description>Bob, please point to an article that indicates that OS X users are getting infected with rootkits. The only information I can find on any real-world rootkits for OS X is a specific one called Opener, which only ever affected one real user (it requires admin privileges to be installed anyhow), and requires admin privileges to even be installed in the first place anyhow. It also was nothing more than a bash script, put in the startup items folder, that attempted to gather password information and run John the Ripper on it. This was 3 years ago, and this is the only information I can find about real rootkits on OS X.

If you're talking about a business-critical machine that handles sensitive data, sure, it's better to be safe than sorry, as such a machine will be a juicy target for hackers or social engineers. On such a machine, it might make sense to run a rootkit scanner. But on any other machine, it's a complete waste of resources. And it even might still be a waste of resources on such a sensitive, critical machine because I'm not convinced that any of the rootkits this software actually scans for even function on OS X.

Even if rootkits existed in the wild for OS X, and even if this software was proven to be able to detect rootkits on OS X, I still wouldn't recommend that regular people use it. To have a rootkit installed on your system, you must a) run untrusted code, and b) provide your password. I would hope that people are smart enough to not type their password at a password prompt unless they know what the software is actually going to do with it. But even if they are not, the chances that a regular user would ever be exposed to a rootkit (assuming they exist and are infecting people in the wild) is so small that running this software is useless.

In short, I don't have any reason to believe this software is actually capable of finding rootkits that even function on OS X, and running it is a complete waste of time.

HOWEVER, you should always keep your system up-to-date with the latest security releases, pay attention to news of any new potential exploits (such as the recent QuickTime holes), and simply exercise caution and proper judgement when running untrusted code or typing your password.</description>
		<content:encoded><![CDATA[<p>Bob, please point to an article that indicates that OS X users are getting infected with rootkits. The only information I can find on any real-world rootkits for OS X is a specific one called Opener, which only ever affected one real user (it requires admin privileges to be installed anyhow), and requires admin privileges to even be installed in the first place anyhow. It also was nothing more than a bash script, put in the startup items folder, that attempted to gather password information and run John the Ripper on it. This was 3 years ago, and this is the only information I can find about real rootkits on OS X.</p>
<p>If you&#8217;re talking about a business-critical machine that handles sensitive data, sure, it&#8217;s better to be safe than sorry, as such a machine will be a juicy target for hackers or social engineers. On such a machine, it might make sense to run a rootkit scanner. But on any other machine, it&#8217;s a complete waste of resources. And it even might still be a waste of resources on such a sensitive, critical machine because I&#8217;m not convinced that any of the rootkits this software actually scans for even function on OS X.</p>
<p>Even if rootkits existed in the wild for OS X, and even if this software was proven to be able to detect rootkits on OS X, I still wouldn&#8217;t recommend that regular people use it. To have a rootkit installed on your system, you must a) run untrusted code, and b) provide your password. I would hope that people are smart enough to not type their password at a password prompt unless they know what the software is actually going to do with it. But even if they are not, the chances that a regular user would ever be exposed to a rootkit (assuming they exist and are infecting people in the wild) is so small that running this software is useless.</p>
<p>In short, I don&#8217;t have any reason to believe this software is actually capable of finding rootkits that even function on OS X, and running it is a complete waste of time.</p>
<p>HOWEVER, you should always keep your system up-to-date with the latest security releases, pay attention to news of any new potential exploits (such as the recent QuickTime holes), and simply exercise caution and proper judgement when running untrusted code or typing your password.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Rudis</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113923</link>
		<dc:creator>Bob Rudis</dc:creator>
		<pubDate>Fri, 25 Jan 2008 03:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113923</guid>
		<description>(neglected to turn subscriptions on for the thread, apologies folks)

If you've looked at my some of my previous posts, you'll see that I put security in the context of risk management. Clearly, Kevin's risk analysis in his particular context gives him the conclusion that there is little-to-no risk &lt;b&gt;for him&lt;/b&gt;. That doesn't make my advice to use anti-malware software FUD. Furthermore, the existence of malware for any platform is not necessarily a factor in determining risk (I have supporting links if pressed for them...kinda tired tonight). When Windows security patches come out each month, many of them do not have public exploit code. Kevin's argument can be extrapolated to mean the lack of such code is cause to &lt;b&gt;not&lt;/b&gt; install those security patches (which would be &lt;i&gt;insane&lt;/i&gt;, especially on that platform).  [NOTE: @ex2bot is absolutely right when he encourages everyone to keep their Mac systems updated as well]

I reiterate that you may choose to accept the risk of running without anti-malware software if you are an experienced user who fully understands his/her computing environments, habits and exposure.

@Scott B is also right on target. Having been a programmer (Mac, Windows, Solaris, Linux, *BSD and *VMS*) and also now working as a security professional with developers I can say with some authority that programmers in general care little about security and even less about thorough software life cycle development. In many shops, it's "code fast or die" and for open source, the mantra is release often (some might call that iterative development, I call it rapid bug fixing). In either case. Most software is rife with buffers waiting to be overflown (overflew?).

@march has a very good suggestion (anyone else on this thread remember tripwire?), but it's not very practical for the average user.

@Graham: I'm pretty convinced to do a complete series on practical security solutions for OS X at this point. I'm as annoyed with the "OS X is a target" news in the feeds and in the press and one of the only ways to help make sense of it is to document what (good stuff) is available. Keep an eye out.

@Patrick, stick with ClamXav. @Mike, if you're *really* interested, I can build a command-line only version for Tiger.

again, apologies for the subscription foible...I'll try to remember to click the checkbox next time.</description>
		<content:encoded><![CDATA[<p>(neglected to turn subscriptions on for the thread, apologies folks)</p>
<p>If you&#8217;ve looked at my some of my previous posts, you&#8217;ll see that I put security in the context of risk management. Clearly, Kevin&#8217;s risk analysis in his particular context gives him the conclusion that there is little-to-no risk <b>for him</b>. That doesn&#8217;t make my advice to use anti-malware software FUD. Furthermore, the existence of malware for any platform is not necessarily a factor in determining risk (I have supporting links if pressed for them&#8230;kinda tired tonight). When Windows security patches come out each month, many of them do not have public exploit code. Kevin&#8217;s argument can be extrapolated to mean the lack of such code is cause to <b>not</b> install those security patches (which would be <i>insane</i>, especially on that platform).  [NOTE: @ex2bot is absolutely right when he encourages everyone to keep their Mac systems updated as well]</p>
<p>I reiterate that you may choose to accept the risk of running without anti-malware software if you are an experienced user who fully understands his/her computing environments, habits and exposure.</p>
<p>@Scott B is also right on target. Having been a programmer (Mac, Windows, Solaris, Linux, *BSD and *VMS*) and also now working as a security professional with developers I can say with some authority that programmers in general care little about security and even less about thorough software life cycle development. In many shops, it&#8217;s &#8220;code fast or die&#8221; and for open source, the mantra is release often (some might call that iterative development, I call it rapid bug fixing). In either case. Most software is rife with buffers waiting to be overflown (overflew?).</p>
<p>@march has a very good suggestion (anyone else on this thread remember tripwire?), but it&#8217;s not very practical for the average user.</p>
<p>@Graham: I&#8217;m pretty convinced to do a complete series on practical security solutions for OS X at this point. I&#8217;m as annoyed with the &#8220;OS X is a target&#8221; news in the feeds and in the press and one of the only ways to help make sense of it is to document what (good stuff) is available. Keep an eye out.</p>
<p>@Patrick, stick with ClamXav. @Mike, if you&#8217;re *really* interested, I can build a command-line only version for Tiger.</p>
<p>again, apologies for the subscription foible&#8230;I&#8217;ll try to remember to click the checkbox next time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: march</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113904</link>
		<dc:creator>march</dc:creator>
		<pubDate>Thu, 24 Jan 2008 02:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113904</guid>
		<description>ballard is right. Do an md5 checksum after each sw update. Keep records, if weird things happen, rechecksum. Thats how you would detect rootkits iv there were any...</description>
		<content:encoded><![CDATA[<p>ballard is right. Do an md5 checksum after each sw update. Keep records, if weird things happen, rechecksum. Thats how you would detect rootkits iv there were any&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113903</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Thu, 24 Jan 2008 01:41:08 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113903</guid>
		<description>"Why do you think this is FUD? It is possible to root-kit MacOS X. It is not a proof of concept."

Have you ever seen an OS X box with a root kit? Have you ever actually heard of this happening in the wild? I sure haven't. In fact, the only malware I've ever actually seen was the Merry Xmas Hypercard virus which only affected Hypercard stacks under the classic Mac OS and was about as benign as a virus could possibly be.

The differences between installing a root-kit on Windows and one on OS X is people actually write root-kits for Windows. People don't write them for OS X. Testing for existing root kits under OS X is quite pointless if they don't actually affect the system, which is what the Rootkit Hunter seems to be doing.

People have been saying "when" an exploit occurs for years and years, and yet, OS X is still incredibly secure. I'm not saying don't practice safe habits like being careful when opening attachments or downloads, or keeping the system up-to-date. I'm saying using tools like Rootkit Hunter is a complete waste of time, because I can guarantee it'll never find anything. If you actually see confirmed reports of a rootkit being found in the wild on OS X systems, at that point it may make sense to start using a tool like this. However, even then you can avoid any trouble by simply being smart about what you launch. Unlike a virus, a rootkit still needs the user's help to be installed.

In short, I guarantee this tool will never find anything on your system. Don't bother.</description>
		<content:encoded><![CDATA[<p>&#8220;Why do you think this is FUD? It is possible to root-kit MacOS X. It is not a proof of concept.&#8221;</p>
<p>Have you ever seen an OS X box with a root kit? Have you ever actually heard of this happening in the wild? I sure haven&#8217;t. In fact, the only malware I&#8217;ve ever actually seen was the Merry Xmas Hypercard virus which only affected Hypercard stacks under the classic Mac OS and was about as benign as a virus could possibly be.</p>
<p>The differences between installing a root-kit on Windows and one on OS X is people actually write root-kits for Windows. People don&#8217;t write them for OS X. Testing for existing root kits under OS X is quite pointless if they don&#8217;t actually affect the system, which is what the Rootkit Hunter seems to be doing.</p>
<p>People have been saying &#8220;when&#8221; an exploit occurs for years and years, and yet, OS X is still incredibly secure. I&#8217;m not saying don&#8217;t practice safe habits like being careful when opening attachments or downloads, or keeping the system up-to-date. I&#8217;m saying using tools like Rootkit Hunter is a complete waste of time, because I can guarantee it&#8217;ll never find anything. If you actually see confirmed reports of a rootkit being found in the wild on OS X systems, at that point it may make sense to start using a tool like this. However, even then you can avoid any trouble by simply being smart about what you launch. Unlike a virus, a rootkit still needs the user&#8217;s help to be installed.</p>
<p>In short, I guarantee this tool will never find anything on your system. Don&#8217;t bother.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: En busca de los Rootkits en la Mac : Canal Apple</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113900</link>
		<dc:creator>En busca de los Rootkits en la Mac : Canal Apple</dc:creator>
		<pubDate>Wed, 23 Jan 2008 23:55:33 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113900</guid>
		<description>[...] entrar en el debate de cuál plataforma es más segura, es siempre bueno estar alerta sobre el asunto. Hay el [...]</description>
		<content:encoded><![CDATA[<p>[...] entrar en el debate de cuál plataforma es más segura, es siempre bueno estar alerta sobre el asunto. Hay el [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott B</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113895</link>
		<dc:creator>Scott B</dc:creator>
		<pubDate>Wed, 23 Jan 2008 22:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113895</guid>
		<description>Kevin Ballard (#7): There is an old saying that an ounce of prevention is worth a pound of cure! Why be reactive and not proactive?

Why do you think this is FUD? It is possible to root-kit MacOS X. It is not a proof of concept. Any script kiddie can download a root-kit, gain access to a MacOS X system, and install a root-kit. The difference between installing root-kit under Windows versus MacOS X are the access control mechanisms that make it more difficult to do so under MacOS X. 

Those of us who are information security professionals know that it is a matter of time before issues occur. Apple has increased the risk by using an application level firewall and suppressing the built-in BSD firewall to be accessible by techies who are not afraid to use Terminal.app. Looking at the risk, we infosec professionals say "when" an exploit occurs.

Unfortunately, many of the risks we find are the result of programmers not understanding the side effects of their coding. From buffer overruns to hard-coding passwords, programming short-cuts are our biggest headache. Rather than attacking the writer, why not try to understand the risks so that we can all ensure elimination of all issues!</description>
		<content:encoded><![CDATA[<p>Kevin Ballard (#7): There is an old saying that an ounce of prevention is worth a pound of cure! Why be reactive and not proactive?</p>
<p>Why do you think this is FUD? It is possible to root-kit MacOS X. It is not a proof of concept. Any script kiddie can download a root-kit, gain access to a MacOS X system, and install a root-kit. The difference between installing root-kit under Windows versus MacOS X are the access control mechanisms that make it more difficult to do so under MacOS X. </p>
<p>Those of us who are information security professionals know that it is a matter of time before issues occur. Apple has increased the risk by using an application level firewall and suppressing the built-in BSD firewall to be accessible by techies who are not afraid to use Terminal.app. Looking at the risk, we infosec professionals say &#8220;when&#8221; an exploit occurs.</p>
<p>Unfortunately, many of the risks we find are the result of programmers not understanding the side effects of their coding. From buffer overruns to hard-coding passwords, programming short-cuts are our biggest headache. Rather than attacking the writer, why not try to understand the risks so that we can all ensure elimination of all issues!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gary</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113894</link>
		<dc:creator>gary</dc:creator>
		<pubDate>Wed, 23 Jan 2008 21:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113894</guid>
		<description>I use ClamXav and sent in a donation. Seem about right to me. Read up a little on configuring it and setting sentry to check particular folder (mail downloads etc.)</description>
		<content:encoded><![CDATA[<p>I use ClamXav and sent in a donation. Seem about right to me. Read up a little on configuring it and setting sentry to check particular folder (mail downloads etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ex2bot</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113893</link>
		<dc:creator>ex2bot</dc:creator>
		<pubDate>Wed, 23 Jan 2008 21:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113893</guid>
		<description>Right now, Mac users need to keep their updates current (via Software Update in the Apple menu) and be careful about blindly accepting download of video codecs.

More general security tips:

Using a router between your Mac and the Internet is a good idea since it acts as a firewall.

Don't open attachments unless you are absolutely sure they are from trusted sources. The general security motto is "Don't open attachments. Period."

Do we Mac users have to run security suites at this point? Debatable. If you depend on MS Office documents with macros, you probably should run one. Otherwise, it's not as clear-cut as with a Windows machine.

Bot</description>
		<content:encoded><![CDATA[<p>Right now, Mac users need to keep their updates current (via Software Update in the Apple menu) and be careful about blindly accepting download of video codecs.</p>
<p>More general security tips:</p>
<p>Using a router between your Mac and the Internet is a good idea since it acts as a firewall.</p>
<p>Don&#8217;t open attachments unless you are absolutely sure they are from trusted sources. The general security motto is &#8220;Don&#8217;t open attachments. Period.&#8221;</p>
<p>Do we Mac users have to run security suites at this point? Debatable. If you depend on MS Office documents with macros, you probably should run one. Otherwise, it&#8217;s not as clear-cut as with a Windows machine.</p>
<p>Bot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ballard</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113887</link>
		<dc:creator>Kevin Ballard</dc:creator>
		<pubDate>Wed, 23 Jan 2008 17:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113887</guid>
		<description>Stop spreading FUD. There's no reason to believe any of these rootkits will even run under OS X, let alone that any have ever been found in the wild on an OS X box.

If (and I say If, not When) the day comes that OS X starts getting some real malware (meaning not the occasional little proof of concept that doesn't do anything), on that day you can start using antivirus/antirootkit software. But until that day comes, you're just wasting resources, not only on your computer, but on the computers of everybody who follows your advice.

And I'm speaking as a Mac computer programmer, not as just another user.</description>
		<content:encoded><![CDATA[<p>Stop spreading FUD. There&#8217;s no reason to believe any of these rootkits will even run under OS X, let alone that any have ever been found in the wild on an OS X box.</p>
<p>If (and I say If, not When) the day comes that OS X starts getting some real malware (meaning not the occasional little proof of concept that doesn&#8217;t do anything), on that day you can start using antivirus/antirootkit software. But until that day comes, you&#8217;re just wasting resources, not only on your computer, but on the computers of everybody who follows your advice.</p>
<p>And I&#8217;m speaking as a Mac computer programmer, not as just another user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Weigel</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113886</link>
		<dc:creator>Patrick Weigel</dc:creator>
		<pubDate>Wed, 23 Jan 2008 17:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113886</guid>
		<description>I'm interested - has anyone run this on a Macintosh and found any rootkits installed on their system? I can understand somewhat the theory in the above blog article, but have there been any real-world rootkits?

I'm willing to run this Rootkit Hunter and ClamXav as it seems relatively painless, but I want to know if I'm defending against an existing problem or a potential problem.

Thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;m interested - has anyone run this on a Macintosh and found any rootkits installed on their system? I can understand somewhat the theory in the above blog article, but have there been any real-world rootkits?</p>
<p>I&#8217;m willing to run this Rootkit Hunter and ClamXav as it seems relatively painless, but I want to know if I&#8217;m defending against an existing problem or a potential problem.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113884</link>
		<dc:creator>Graham</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113884</guid>
		<description>Is there a MAC-like security program that works? Norton Internet Security is very clunky, not intuitive at all. Also it's  very heavy handed in its intrusiveness and its updating.
I use Macs to avoid such programs - and dealing with Unix.
Thanks for any suggestions.</description>
		<content:encoded><![CDATA[<p>Is there a MAC-like security program that works? Norton Internet Security is very clunky, not intuitive at all. Also it&#8217;s  very heavy handed in its intrusiveness and its updating.<br />
I use Macs to avoid such programs - and dealing with Unix.<br />
Thanks for any suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113882</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113882</guid>
		<description>Looks like RootKitHunter only works on Leopard. Any help for those still running Tiger?</description>
		<content:encoded><![CDATA[<p>Looks like RootKitHunter only works on Leopard. Any help for those still running Tiger?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Rudis</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113881</link>
		<dc:creator>Bob Rudis</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113881</guid>
		<description>@Steve: I was using OS X Rootkit Hunter primarily as an example of how there are valid historical and current security concerns on OS X. The developer did a great job and service porting it as well as he did to the Mac, but I would purport that it's still something only more technical users of OS X go out and investigate.

ClamXav (http://www.clamxav.com/) is another great, free security tool with *nix origins and an even better OS X front-end. TAB did a mention (http://theappleblog.com/2007/01/30/5-tips-for-a-new-mac-user/) of them last year and it may be time for a detailed comprehensive review of commercial (and qualified open source) anti-virus solutions for OS X.

I would highly recommend using ClamXav over OS X Rootkit Hunter as a baseline layer of security.</description>
		<content:encoded><![CDATA[<p>@Steve: I was using OS X Rootkit Hunter primarily as an example of how there are valid historical and current security concerns on OS X. The developer did a great job and service porting it as well as he did to the Mac, but I would purport that it&#8217;s still something only more technical users of OS X go out and investigate.</p>
<p>ClamXav (http://www.clamxav.com/) is another great, free security tool with *nix origins and an even better OS X front-end. TAB did a mention (http://theappleblog.com/2007/01/30/5-tips-for-a-new-mac-user/) of them last year and it may be time for a detailed comprehensive review of commercial (and qualified open source) anti-virus solutions for OS X.</p>
<p>I would highly recommend using ClamXav over OS X Rootkit Hunter as a baseline layer of security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113879</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 23 Jan 2008 14:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113879</guid>
		<description>What about the free virus app, clamXav
?  What's the difference?  Is one better than the other?  Should one run both?</description>
		<content:encoded><![CDATA[<p>What about the free virus app, clamXav<br />
?  What&#8217;s the difference?  Is one better than the other?  Should one run both?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RootKit Hunter, la seguridad en OSX ante todo : planetamac</title>
		<link>http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113870</link>
		<dc:creator>RootKit Hunter, la seguridad en OSX ante todo : planetamac</dc:creator>
		<pubDate>Wed, 23 Jan 2008 12:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2008/01/23/why-mac-security-matters-os-x-rootkit-hunter/#comment-113870</guid>
		<description>[...] theAppleBlog   &#160;fresqui &#124; &#160;men&#233;ame&#160;&#124;&#160;permalink&#160;&#124;&#160;trackback url  Si te ha [...]</description>
		<content:encoded><![CDATA[<p>[...] theAppleBlog   &nbsp;fresqui | &nbsp;men&eacute;ame&nbsp;|&nbsp;permalink&nbsp;|&nbsp;trackback url  Si te ha [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
