linux-kernel - Re: [PATCH 0/1] HID: Report Descriptor in Sysfs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D39A660.7040302@signal11.us>
Date:	Fri, 21 Jan 2011 10:29:36 -0500
From:	Alan Ott <alan@...nal11.us>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] HID: Report Descriptor in Sysfs

On 01/21/2011 10:09 AM, Jiri Kosina wrote:
> On Fri, 21 Jan 2011, Alan Ott wrote:
>
>    
>> Maybe it is. To be honest I didn't check debugfs. I have two concerns about
>> it:
>> 1. Is it wise for userspace programs to rely on:
>>      
> Ah, I didn't realize that you want it to be used by some acutal userspace
> applications. Out of curiosity -- what is the usage pattern you are
> targetting?
>    

Well, what I really want is the Usage Page and Usage of the device. For 
some background, I maintain a library called hidapi[1] for accessing HID 
devices in a cross platform way. There are currently four backends, 
Linux-hidraw, Linux-libusb, Mac OS, and Windows.

I've recently received requests for supporting composite HID devices. 
Since a composite device will show up as multiple devices with the same 
VID/PID, one needs a way to differentiate between its different 
interfaces. On Windows and Mac, the platform HID libraries support 
getting the Usage Page and Usage of each interface. On Linux/libusb I 
can request the HID report descriptor and parse it myself, but I have to 
claim the interface to do it, and to do that, I have to detach the 
kernel driver. Needless to say, detaching the kernel driver is not good, 
especially when the library is supposed to be just scanning for devices.

For these reasons, it would be really convenient to get the report 
descriptor from sysfs.

Alan.

[1] http://www.signal11.us/oss/hidapi/

--
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/