News for hackers. Stuff that matters.
Re:Debugging mechanism in Intel CPUs allows seizing control ... by Animats on Tuesday January 10, 2017 @12:11AM (#13362770)
I tried to get that disabled in Linux. There's a register in the FireWire interface which sets the range of addresses into which external memory access requests can be made. By default, it was at 4GB, even on 64 bit systems. Setting it to zero would break some external kernel debugger, though, so it was left open.

(Firewire isn't DMA. PCI-E is DMA. Firewire is a network cable, over which software sends packets. LAN over FireWire was sometimes done. But there's an optional feature which recognizes special packets for doing word-size loads and stores. This is usually used to talk to dumb slave devices, where you write "registers" to make things happen. It's not needed on a computer, and it's far too slow for bulk transfers. FireWire isn't inherently more vulnerable than a LAN port.)

Re:Debugging mechanism in Intel CPUs allows seizing control ... by kalleboo on Tuesday January 10, 2017 @04:35AM (#13363724)
IIRC Apple's "fix" was to just disable recognition of new FireWire devices when the computer was locked. So a nasty device could still compromise you, but it would be one that you plugged in yourself.
Re:Debugging mechanism in Intel CPUs allows seizing control ... by mikeash on Tuesday January 10, 2017 @10:06AM (#13365291)
It looks like your recollection is indeed correct. See the entry for CVE-2011-3215 here: https://support.apple.com/en-us/HT202348
Re:Debugging mechanism in Intel CPUs allows seizing control ... by psybin on Tuesday January 10, 2017 @02:06AM (#13363235)
Firewire in most setups allows DMA access to the host, but only to the first 32 bits of RAM. There's tools for unlocking, reading out keys from memory while asleep, all sorts of nasties.
Re:Debugging mechanism in Intel CPUs allows seizing control ... by Animats on Tuesday January 10, 2017 @03:04AM (#13363441)
In Linux, that's a constant in the Linux driver.