3 ms·
Current Linux disables the device-initiated DMA mechanism for firewire and other "untrusted" busses, though it should probably consider more types of busses "un
by JoshTriplett 15y ago
Current Linux disables the device-initiated DMA mechanism for firewire and other "untrusted" busses, though it should probably consider more types of busses "untrusted" than it does. This requires the host driver to initiate DMA, which it'll only do for devices it knows how to talk to safely. Turning this protection off (and thus making the system insecure) requires both compiling a kernel with the debugging-only option CONFIG_FIREWIRE_OHCI_REMOTE_DMA turned on and passing a kernel parameter at boot time, so you can't do it accidentally.
I thought more recent versions of OS X fixed this problem as well, but perhaps not.
- ryannielsen 15y agoFireWire and Thunderbolt DMA is disabled if you set an firmware password. On systems which support Intel's VT-d technology, the OS will actually allow restricted DMA even with the firmware password set so you get almost all the benefits of DMA without the security compromise of having all memory exposed to the foreign device.
- mike-cardwell 15y agoThis is a great article about this subject: http://www.hermann-uwe.de/blog/physical-memory-attacks-via-firewire-dma-part-1-overview-and-mitigation http://www.hermann-uwe.de/blog/physical-memory-attacks-via-f... It contains mitigation information for OSX, Linux, Windows and various flavours of Unix.