Re: RFC/patch 1/6: wusb: add authorization control for devices
David Brownell <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday 24 April 2007, Inaky Perez-Gonzalez wrote: > > This patch introduces 'struct usb_device'->authorized. Devices with > that bit set can be used in the system (drivers are allow to > attach). Devices that don't will have the usb_probe routine aborting > driver binding. > > This is needed for WUSB devices: until we don't do the crypto > handshake, we can't allow the device to be used -- but in the > meantime, we need to be able to talk to it's default endpoint. How would this be different from testing whether udev->state == USB_STATE_UNAUTHENTICATED Other than "authenticated" != "authorized" ... as in, WUSB talks about the not-authenticated state, but a "not authorized" notion exceeds (what I recall of the) WUSB specs by presuming an identity based acceess control mechanism. (Access control list, etc.) - Dave ------------------------------------------------------------------------- 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