Re: Hotplug, 1394, and security

[Stefan Richter <stefanr@s5r6.in-berlin.de>]

Jody McIntyre wrote:
> On Sun, Nov 27, 2005 at 02:39:54PM +0100, Stefan Richter wrote:
>>Raw1394 and libraw1394 do support async streams AFAIU from the sources.
...
> Let's leave it in "iso" for now. 

What about naming it "streams" then?

...
>>>Do you know of any cases where read transactions are harmful?
>>
>>Read access to the physical address range of PCs with OHCI interface.
> 
> Sure, but as far as I know, non-root processes do not need any access to
> other PCs on the bus.

This means furthermore that only privileged users (e.g. root) should be 
allowed to add unit directories to the local configROM, or generally to 
manipulate the ROM.

OTOH the problem with phys DMA should rather be solved in the driver 
stack which enables phys DMA.

...
>>IEEE 1394 itself does not explicitly deal with security matters,
...
> Yes, therefore my proposal is not in violation of IEEE 1394, 1394a, or
> 1394b.

No, it isn't, and I never wanted to imply the contrary. I just assumed 
so far that IEEE 1394 makes it very difficult to combine security and 
functionality. But what you describe sounds feasible.
-- 
Stefan Richter
-===-=-=-= =-= ==-http://arcgraph.de/sr/


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel