On Fri, Mar 1, 2013 at 5:42 AM, Pete Batard <p...@akeo.ie> wrote: > But there should still be an issue when using interface with WinUSB, as > it overrides the low byte of wIndex with the destination interface: [3] > > [3] http://www.lvr.com/forum/index.php?topic=331 >
The following is from Tim Roberts. http://www.osronline.com/showthread.cfm?link=223812 (Message 12) ++++++++++++++ Xiaofan Chen wrote: > 5) When using interface control requests (LIBUSB_RECIPIENT_INTERFACE), > WinUSB overrides the low byte of wIndex with the destination interface. > This is a limitation of the Microsoft driver. One can also argue that this is a security measure. The USB spec requires that the low byte of wIndex be set to the interface number when the recipient is set to "interface". Devices that use that field for other purposes are broken. -- Tim Roberts +++++++++++++++++ And Microsoft's Dolan Holan's answer in Message 13. ++++++++++ "5. this is so you only target your interface on a composite device. Letting a user mode stack manipulate a sibling interface is bad security and encapsulation, no?" ++++++++++ -- Xiaofan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
