<?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: Physical Attacks via FireWire</title>
	<atom:link href="http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/feed/" rel="self" type="application/rss+xml" />
	<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/</link>
	<description>Little boxes made of words, by Jens Alfke</description>
	<lastBuildDate>Sun, 14 Mar 2010 11:32:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Adams</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2434</link>
		<dc:creator>Chris Adams</dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2434</guid>
		<description>nate - thanks for the link to Rentzsch&#039;s article. I was looking for that yesterday.

Rosyna - has anyone looked into whether the current hardware offers support for restricted DMA? I last ran into this with cluster interconnects which were completely insecure at first but later acquired hardware support – probably motivated more by system stability than security.</description>
		<content:encoded><![CDATA[<p>nate - thanks for the link to Rentzsch&#8217;s article. I was looking for that yesterday.</p>
<p>Rosyna - has anyone looked into whether the current hardware offers support for restricted DMA? I last ran into this with cluster interconnects which were completely insecure at first but later acquired hardware support – probably motivated more by system stability than security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2433</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2433</guid>
		<description>To answer my own question: &lt;a href=&quot;http://docs.info.apple.com/article.html?artnum=106482&quot; rel=&quot;nofollow&quot;&gt;Here&#039;s Apple&#039;s support article.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>To answer my own question: <a href="http://docs.info.apple.com/article.html?artnum=106482" rel="nofollow">Here&#8217;s Apple&#8217;s support article.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2432</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2432</guid>
		<description>OK, next step is to figure out &lt;i&gt;how&lt;/i&gt; to enable the &lt;strike&gt;OpenFirmware&lt;/strike&gt; EFI password. But I&#039;m sure I can google for that...</description>
		<content:encoded><![CDATA[<p>OK, next step is to figure out <i>how</i> to enable the <strike>OpenFirmware</strike> EFI password. But I&#8217;m sure I can google for that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rosyna</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2431</link>
		<dc:creator>Rosyna</dc:creator>
		<pubDate>Fri, 14 Mar 2008 09:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2431</guid>
		<description>Yeah, just enable the OpenFirmware password to disable FireWire DMA. It&#039;s been like this for, like, forever. (Yes, I call it the Open Firmware password, even when you enable it on the ICBMs). But note, doing so may lead to a substantial speed decrease with high-bandwidth FireWire devices. IIRC, there was a bug in the very first releases of 10.4.4-10.4.something that made the password not disable DMA on the ICBMs. But this was fixed.</description>
		<content:encoded><![CDATA[<p>Yeah, just enable the OpenFirmware password to disable FireWire DMA. It&#8217;s been like this for, like, forever. (Yes, I call it the Open Firmware password, even when you enable it on the ICBMs). But note, doing so may lead to a substantial speed decrease with high-bandwidth FireWire devices. IIRC, there was a bug in the very first releases of 10.4.4-10.4.something that made the password not disable DMA on the ICBMs. But this was fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2430</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Fri, 14 Mar 2008 04:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2430</guid>
		<description>Michael — First, I&#039;ve turned on password locking. Second, rebooting and messing with single-user mode takes longer, and is more obvious during and afterwards.</description>
		<content:encoded><![CDATA[<p>Michael — First, I&#8217;ve turned on password locking. Second, rebooting and messing with single-user mode takes longer, and is more obvious during and afterwards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: n[ate]vw</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2429</link>
		<dc:creator>n[ate]vw</dc:creator>
		<pubDate>Fri, 14 Mar 2008 04:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2429</guid>
		<description>I tried so hard, but left out a piece of Rentzsch&#039;s last name, sorry. I even had the URL right there!!</description>
		<content:encoded><![CDATA[<p>I tried so hard, but left out a piece of Rentzsch&#8217;s last name, sorry. I even had the URL right there!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: n[ate]vw</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2428</link>
		<dc:creator>n[ate]vw</dc:creator>
		<pubDate>Fri, 14 Mar 2008 04:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2428</guid>
		<description>Rentzsh actually seems to have the definitive article on this (and it appears to have been up since November, 2004): http://rentzsch.com/macosx/securingFirewire

The way I understand it is that OS X will indeed disable Firewire DMA, all the way back to 10.2.2, but only if a firmware password is set.</description>
		<content:encoded><![CDATA[<p>Rentzsh actually seems to have the definitive article on this (and it appears to have been up since November, 2004): <a href="http://rentzsch.com/macosx/securingFirewire" rel="nofollow">http://rentzsch.com/macosx/securingFirewire</a></p>
<p>The way I understand it is that OS X will indeed disable Firewire DMA, all the way back to 10.2.2, but only if a firmware password is set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Brundage</title>
		<link>http://jens.mooseyard.com/2008/03/physical-attacks-via-firewire/comment-page-1/#comment-2427</link>
		<dc:creator>Michael Brundage</dc:creator>
		<pubDate>Fri, 14 Mar 2008 03:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2008/03/physical-attacks-via-firewire/#comment-2427</guid>
		<description>Jens, hacking a Mac that you have physical access to is far easier.

First of all, the Mac OS defaults are no password locking on sleep or boot, so you probably already have full access to the user&#039;s data.

Ignoring that, just reboot the machine and hold down cmd-S.  You now have a root shell.  It&#039;s trivial from there to do anything you want, such as just deleting the tmp file that tells Mac OS X the machine has been configured and then rebooting, which will prompt you to create an admin (sudoers) account.</description>
		<content:encoded><![CDATA[<p>Jens, hacking a Mac that you have physical access to is far easier.</p>
<p>First of all, the Mac OS defaults are no password locking on sleep or boot, so you probably already have full access to the user&#8217;s data.</p>
<p>Ignoring that, just reboot the machine and hold down cmd-S.  You now have a root shell.  It&#8217;s trivial from there to do anything you want, such as just deleting the tmp file that tells Mac OS X the machine has been configured and then rebooting, which will prompt you to create an admin (sudoers) account.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->