On Wed, Jan 4, 2017 at 12:10 PM, Matthew Garrett <mj...@coreos.com> wrote: > > The USB authentication feature was intended for handling wireless USB > devices - it can be reused for this, but the code isn't generic enough > to apply to other bus types. The two interact in exactly the way you'd > expect, ie they don't. If you use both, then you need to handle both.
And as an example of why the USB authorisation feature isn't sufficient - the interface configuration isn't picked until after you've authorised the device, which means you can't necessarily tell the difference between a keyboard and an ethernet adapter until after you've authorised it. That defeats the object, but it can't be changed without breaking the wireless USB case.
