|
BugTraq
Firewire Attack on Windows Vista Mar 05 2008 03:53PM Bernhard Mueller (research sec-consult com) (2 replies) RE: Firewire Attack on Windows Vista Mar 05 2008 09:30PM Roger A. Grimes (roger banneretcs com) (4 replies) RE: Firewire Attack on Windows Vista Mar 06 2008 10:01AM bzhbfzj3001 sneakemail com (1 replies) Re: Firewire Attack on Windows Vista Mar 07 2008 07:51AM Tonnerre Lombard (tonnerre lombard sygroup ch) (1 replies) Re: Firewire Attack on Windows Vista Mar 06 2008 07:54AM Tonnerre Lombard (tonnerre lombard sygroup ch) Re: Firewire Attack on Windows Vista Mar 06 2008 12:37AM Peter Watkins (peterw usa net) (1 replies) RE: Firewire Attack on Windows Vista Mar 06 2008 05:50PM Larry Seltzer (Larry larryseltzer com) (2 replies) RE: Firewire Attack on Windows Vista Mar 06 2008 09:11PM Thor (Hammer of God) (thor hammerofgod com) Re: [Full-disclosure] Firewire Attack on Windows Vista Mar 06 2008 08:00PM Tim (tim-security sentinelchicken org) (2 replies) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 07 2008 05:42PM Thor (Hammer of God) (thor hammerofgod com) (1 replies) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 07 2008 07:40PM Thor (Hammer of God) (thor hammerofgod com) (1 replies) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 07 2008 07:44PM Larry Seltzer (Larry larryseltzer com) (1 replies) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 07 2008 07:51PM Larry Seltzer (Larry larryseltzer com) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 06 2008 08:13PM Larry Seltzer (Larry larryseltzer com) (1 replies) Re: [Full-disclosure] Firewire Attack on Windows Vista Mar 06 2008 08:20PM Tim (tim-security sentinelchicken org) (1 replies) RE: [Full-disclosure] Firewire Attack on Windows Vista Mar 06 2008 08:35PM Larry Seltzer (Larry larryseltzer com) (1 replies) |
|
Privacy Statement |
> only to a certain range?
>
> If not, what options are available?
I have various forms of RSI and don't feel like typing it again:
On Thu, Mar 06, 2008 at 12:00:09PM -0800, Tim wrote:
> [...]
> Of course this is not an optimal fix. The drivers should just
> automatically restrict the DMA accesses in real time to a range that is
> safe but still permits devices to use it. (Presumably to buffers
> allocated specifically for I/O.) Not sure if some devices would still
> have problems with this, but I think this is the intended operation of
> ieee1394 based on the specs and I'd imagine it would work on a greater
> number of devices than having it disabled completely.
> [...]
So yes, this is possible. AFAIK, driver writers on all sides have just
been lazy. At least with free OSes they have a lame hack to protect
you.
tim
[ reply ]