| 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
| ||
|
Message-ID: <ep50n7$dni$1@sea.gmane.org> Date: Tue, 23 Jan 2007 13:57:11 +0100 From: Rolf Offermanns <roffermanns@...il.com> To: linux-kernel@...r.kernel.org Subject: Re: How to use an usb interface than is claimed by HID? Ivan Ukhov wrote: >> .. which wouldn't help you either, supposing that you don't want to touch >> the kernel sources at all, because this function is unexported and >> static. >> >> So I think that there is no straightforward way, sorry. >> >> Is this a device that doesn't exist anywhere else than on your table? I >> still think that putting the code in kernel (if possible) and >> blacklisting the device on the hid_blacklist[] is the simplest way. >> >> The other possibility is writing the driver completely in userspace, >> using libhid/hiddev. Would that suit your needs? > > I'm afraid it wouldn't. > > Thank you very much. > There is another way. Have a look at this article: http://lwn.net/Articles/143397/ Maybe this is an option for you. -Rolf -- Rolf Offermanns <roffermanns@...go.com> SYSGO AG Tel.: +49-6136-9948-0 Am Pfaffenstein 14 Fax: +49-6136-9948-10 55270 Klein-Winternheim http://www.sysgo.com - 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/
Powered by blists - more mailing lists