On Mon, Jun 08, 2015 at 03:02:25PM -0700, Greg KH wrote: > On Mon, Jun 08, 2015 at 11:58:55PM +0200, Stefan Koch wrote: > > Am 08.06.2015 um 16:40 schrieb Greg KH: > > > On Mon, Jun 08, 2015 at 03:24:26PM +0200, Stefan Koch wrote: > > >> Hi > > >> > > >> This is a patch that introduces an interface authorization for USB devices. > > >> > > >> The kernel supports already a device authorization bacause of wireless USB. > > >> > > >> But the new interface authorization allows to enable or disable individual interfaces per bitmask instead allow or deny a whole device. > > >> > > >> As example you can allow the interface for a TV signal from a USB TV card, but deny a HID for the remote control. > > >> > > >> This was added against BadUSB attacks. Refer to: https://srlabs.de/badusb/ > > >> > > >> The interface authorization is used by an usb firewall named "usbauth". > > >> The code and binaries for openSUSE 13.2 can be found here: https://build.opensuse.org/project/show/home:skoch_suse > > >> > > >> The patch was tested with Linux 4.1-rc3. The functionality is oriented at existing kernel code like usb_set_configuration(), the device authorization, etc. > > >> > > >> If the interface authorization is not used, the kernel behavior is the same as without the patch. > > >> > > >> Best regards > > >> > > >> Stefan Koch > > > Care to resend this in a format that it could be applied in (i.e. broken > > > up into logical chunks with the proper Signed-off-by: lines)? > > > > > > As this is, there's nothing we can do with it. > > > > > > thanks, > > > > > > greg k-h > > Hi > > > > I have split the patches now... > > You need to resend these as a series, I can't pick them out of a single > email. Also, please provide a good Subject: for the patch, and some > information in the body of each changelog area describing why you are > making these changes. Also, all of the whitespace is broken in your patches, making them impossible to apply even if I wanted to :( -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
