linux-kernel - Re: Blacklisting a usbhid device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2009 08:33:04 +1000
From:	Adam Nielsen <a.nielsen@...kadi.net>
To:	"Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
CC:	Linux USB <linux-usb@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Blacklisting a usbhid device

> Any suggestions on how to either work within the usbhid framework or how
> to get usbhid to stop claiming the device?

>From userland you can get the usbhid driver to release the device like this:

  cd /sys/bus/usb/drivers/usbhid
  echo '9-1:1.0' > unbind

Where '9-1:1.0' is the device you want to release.  Presumably you could do
the same thing on the kernel side when your driver is loaded.  This would give
better functionality, in that the usbhid driver would handle basic
functionality if your driver isn't loaded, but as soon as your driver was
loaded the extra functionality would become available.

Of course this bypasses usbhid's functionality.  I imagine it would be better
to write a hid driver and let usbhid handle the USB side of things.  Have a
look in drivers/hid/ for some hid driver examples that do this.

Cheers,
Adam.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/