linux-kernel - Re: [PATCH v5 1/1] HID: Add full support for Logitech Unifying receivers

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]

Date:	Thu, 29 Sep 2011 17:22:17 +0200
From:	Richard Schütz <r.schtz@...nline.de>
To:	Nestor Lopez Casado <nlopezcasad@...itech.com>
CC:	Benjamin Tissoires <benjamin.tissoires@...il.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, rtitmuss@...itech.com,
	ogay@...itech.com, jzanone@...itech.com
Subject: Re: [PATCH v5 1/1] HID: Add full support for Logitech Unifying receivers

Am 23.09.2011 00:21, schrieb Benjamin Tissoires:
> On Thu, Sep 22, 2011 at 23:17, Richard Schütz<r.schtz@...nline.de>  wrote:
>> Am 22.09.2011 22:48, schrieb Benjamin Tissoires:
>>>
>>> Hi Richard,
>>>
>>> here, you'll find a small C program that allows you to do a pairing of
>>> a new device to a receiver.
>>
>> Thanks.
>>
>> Could you also add the possibility to remove a pairing? It would be nice if
>> the program would print the product name of device detected during the
>> pairing process, too.
>
> mmm... this would be more complicated:
> - the first problem is a NDA and political one. As I worked in
> Logitech, I had access to some internal (confidential) documentation.
> I was able to release this piece of code as it can be easily retrieved
> by adding a spy on the usb stack when doing the pairing on windows.
> Discovering the command that removes devices is not so easy (to my
> mind), thus, I can not give it right now.  Please note that I asked
> them if I could release this magic sequence, and it went quite high in
> the hierarchy (but this piece of code has nothing to do with Logitech,
> just to be clear).
> - the second problem is more a technical one. The removal of the
> device would require you two know which device you want to remove. So
> it would require the ability to know all the different devices and
> their pairing number. This information shows up somewhere in the log
> but there is no way to ask the receiver for this information with the
> current status of the driver (without knowing internal commands).
> Getting it from the list of devices would be quite complicated
> depending on the number of receivers you have plugged, etc...
> - Obtaining the name of the device can not be retrieved at the moment
> without knowing the different commands to send to the device. As it's
> confidential Logitech, I can not give them to you unless someone else
> does the retro-engineering.
>
> So, to sum up, I agree this would be better, but today, this has to be
> done by someone else, either officially at Logitech, or by someone not
> related to Logitech that does the retro-engineering.

So what do the Logitech guys think about this? Without userspace tools 
for creating/removing pairings a Unifying receiver is quite useless for 
Linux users.

-- 
Regards,
Richard Schütz
--
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/