diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2015-08-18 12:57:15 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2015-08-18 12:57:15 -0400 |
| commit | dba3398381dd1175c74721c97d1daf8fc5939276 (patch) | |
| tree | 2cc22ff580a687b7f2274c6b24eb4aabf6bd36e2 /Documentation/usb | |
| parent | a1b93ab71587b8b44d45d114937cb4e75f9a5f27 (diff) | |
Revert "usb: interface authorization: Documentation part"
This reverts commit 6ef2bf71764708f7c58ee9300acd8df05dbaa06f as the
signed-off-by address is invalid.
Cc: Stefan Koch <stefan.koch10@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/usb')
| -rw-r--r-- | Documentation/usb/authorization.txt | 34 |
1 files changed, 0 insertions, 34 deletions
diff --git a/Documentation/usb/authorization.txt b/Documentation/usb/authorization.txt index 020cec5585ce..c069b6884c77 100644 --- a/Documentation/usb/authorization.txt +++ b/Documentation/usb/authorization.txt | |||
| @@ -3,9 +3,6 @@ Authorizing (or not) your USB devices to connect to the system | |||
| 3 | 3 | ||
| 4 | (C) 2007 Inaky Perez-Gonzalez <inaky@linux.intel.com> Intel Corporation | 4 | (C) 2007 Inaky Perez-Gonzalez <inaky@linux.intel.com> Intel Corporation |
| 5 | 5 | ||
| 6 | Interface authorization part: | ||
| 7 | (C) 2015 Stefan Koch <skoch@suse.de> SUSE LLC | ||
| 8 | |||
| 9 | This feature allows you to control if a USB device can be used (or | 6 | This feature allows you to control if a USB device can be used (or |
| 10 | not) in a system. This feature will allow you to implement a lock-down | 7 | not) in a system. This feature will allow you to implement a lock-down |
| 11 | of USB devices, fully controlled by user space. | 8 | of USB devices, fully controlled by user space. |
| @@ -93,34 +90,3 @@ etc, but you get the idea. Anybody with access to a device gadget kit | |||
| 93 | can fake descriptors and device info. Don't trust that. You are | 90 | can fake descriptors and device info. Don't trust that. You are |
| 94 | welcome. | 91 | welcome. |
| 95 | 92 | ||
| 96 | |||
| 97 | Interface authorization | ||
| 98 | ----------------------- | ||
| 99 | There is a similar approach to allow or deny specific USB interfaces. | ||
| 100 | That allows to block only a subset of an USB device. | ||
| 101 | |||
| 102 | Authorize an interface: | ||
| 103 | $ echo 1 > /sys/bus/usb/devices/INTERFACE/authorized | ||
| 104 | |||
| 105 | Deauthorize an interface: | ||
| 106 | $ echo 0 > /sys/bus/usb/devices/INTERFACE/authorized | ||
| 107 | |||
| 108 | The default value for new interfaces | ||
| 109 | on a particular USB bus can be changed, too. | ||
| 110 | |||
| 111 | Allow interfaces per default: | ||
| 112 | $ echo 1 > /sys/bus/usb/devices/usbX/interface_authorized_default | ||
| 113 | |||
| 114 | Deny interfaces per default: | ||
| 115 | $ echo 0 > /sys/bus/usb/devices/usbX/interface_authorized_default | ||
| 116 | |||
| 117 | Per default the interface_authorized_default bit is 1. | ||
| 118 | So all interfaces would authorized per default. | ||
| 119 | |||
| 120 | Note: | ||
| 121 | If a deauthorized interface will be authorized so the driver probing must | ||
| 122 | be triggered manually by writing INTERFACE to /sys/bus/usb/drivers_probe | ||
| 123 | |||
| 124 | For drivers that need multiple interfaces all needed interfaces should be | ||
| 125 | authroized first. After that the drivers should be probed. | ||
| 126 | This avoids side effects. | ||
