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: <alpine.LNX.2.00.1101211607290.5725@pobox.suse.cz>
Date:	Fri, 21 Jan 2011 16:09:25 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Alan Ott <alan@...nal11.us>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] HID: Report Descriptor in Sysfs

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?

The idea behind debugfs-provided userspace descriptor is that driver 
developer is easily able to inspect the descriptor, and write a kernel 
driver that fixes it up in case it is bogus.
There were also efforts to make the report descriptor replaceable in a 
request_firmware() way, but that never converged to state in which it 
could be applied IIRC.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/