RFC/patch: authorizing (or not) devices to connect to the system

Hi All

As part of the work for Wireless USB, I need to introduce in the USB stack
the concept of unauthorized vs authorized device. The first one is one that
cannot be really used until we move it to authorized, but at least we have
some knowledge of it.

I've been toying with some patches to implement this concept also in a 
generic way so that it could be used to implement a control mechanism
for locking down systems (like for example, don't connect this kind of 
hw, because policy won't allow it being configured).

How this is done is adding an authorized bit to struct usb_device, and
checking for that in usb_*_probe(). If zero, we reject it. We also have
a per-host default we can set via sysfs and now I am working on the 
mechanism to authorize them, which is basically a reissue of usb_new_device()
(part of it)...still is not finished, but I laid the groundwork by
breaking up usb_new_device() on functional parts. The last patch has the
initial plumbing for this.

So, this is just a RFC, I'd like to ask for some feedback on the patches
that follow (that btw, apply to 2.6.21-rc7).

Thanks,

-- Inaky

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel