linux-kernel - Re: USB remote control missing keycodes

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: <Pine.LNX.4.64.0706141425180.23280@twin.jikos.cz>
Date:	Thu, 14 Jun 2007 14:30:27 +0200 (CEST)
From:	Jiri Kosina <jikos@...os.cz>
To:	Islam Amer <pharon@...il.com>
cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: USB remote control missing keycodes

On Thu, 14 Jun 2007, Islam Amer wrote:

> Ok here is everything from dmesg after the point of plugging in the usb 
> IR receiver, which is quite lengthy so as an attachment.

Thanks. Obviously this remote has broken report descriptor -- it generates 
0xfa usage code from Consumer page for the "back" key (not to mention that 
it should rather generate 0x224 for KEY_BACK), but logical maximum for 
coresponding field is set to 0xf9, as far as I can see from the dump you 
provided.

I have met such devices already, we are fixing their report descriptors on 
the fly before they enter the HID parser. I will prepare a patch for you 
to test (probably tomorrow, sorry).

BTW this also means that the support for the BACK key can't currently be 
written in userspace using the setkeycodes() method, because this usage is 
currently just ignored, due to being out of range.

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