On Sat, 9 Aug 2014, Yves-Alexis Perez wrote: > On ven., 2014-08-08 at 18:17 -0400, Alan Stern wrote: > > The authorized_default module parameter affects USB buses when they > > are > > discovered and registered; after that it has no effect. Therefore to > > accomplish what you want, you need to put > > "usbcore.authorized_default=0" in the kernel's boot command line. > > > > Alternatively, you can change the default authorization value for a > > particular bus after it has been created, by writing to the > > authorized_default sysfs file for the bus's root hub. For example, > > > > echo 0 >/sys/bus/usb/devices/usb1/authorized_default > > > > will set the default value for new devices on bus 1 to 0. > > Thanks for your answer. So that confirms it's not possible to toggle > that value depending on a platform state (for example if the session is > locked). I'm not sure what you mean. You can toggle these values at any time, but toggling them may not accomplish anything useful. What do you want to accomplish? Note that in addition to changing the default values, you can change the actual authorization value for an existing device at any time by writing to the device's "authorized" sysfs file. Alan Stern -- 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
