Re: FireWire Security issues

From: Bruce M Simpson (bms_at_spc.org)
Date: 11/17/04

  • Next message: Julian Elischer: "Re: FireWire Security issues" 
    Date: Tue, 16 Nov 2004 17:40:37 -0800
To: Maximillian Dornseif <dornseif@informatik.rwth-aachen.de>

    On Tue, Nov 16, 2004 at 09:30:09PM +0100, Maximillian Dornseif wrote:
    > looking into the issue described in the advisory below I wonder how to
    > tackle this issues. Primarily
    > I ask myself
    >
    > * is there any reason not to filter all physical memory access by default
    > * what would be the appropriate way to change the filter set? a sysctl?

    This is totally not news, this has been discussed in various circles for
    the past 5 years, though it's nice to see someone presenting an old attack
    in a new way.

    You can only filter the accesses by implementing filter logic in the PCI
    bridge to main memory to deny the accesses, or the PCI bus arbiter, or
    failing that, the FireWire to PCI host controller itself.

    The CPU and operating system are not able to intervene here in any way.

    Regards,
    BMS

  • Next message: Julian Elischer: "Re: FireWire Security issues"

    Relevant Pages

    • Re: getting handle to device
      ... Please do not send e-mail directly to this alias. ... I have a bus filter driver to pci.sys. ... My company builds PCI and PCIE ...
      (microsoft.public.development.device.drivers)
    • Re: Device stack reordering when driver is reloaded
      ... you need to determine how the IBM driver comes to be installed. ... That makes me wonder if IBM has some "bus" logic somewhere to ensure the filter is placed on the stack and isn't relying purely on the OS. ... Although if it is truly a hotplug pci bus attitude adjuster one would think that pci device insertion/removal would have been tested. ...
      (microsoft.public.development.device.drivers)
    • Re: Insert Update Delete CLOB in trigger
      ... CTX_DOC.FILTERrequires a Text index and accesses the base table ... because CTX_DOC.FILTERtruncates the output CLOB ... I was unable to force this procedure to filter to plaintext regardless ...
      (comp.databases.oracle.misc)