linux-kernel - Fwd: Re: Phis in /proc/bus/input/devices same for all devices?

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

Message-Id: <200702212313.30359.cijoml@volny.cz>
Date:	Wed, 21 Feb 2007 23:13:29 +0100
From:	CIJOML <cijoml@...ny.cz>
To:	linux-kernel@...r.kernel.org
Subject: Fwd: Re: Phis in /proc/bus/input/devices same for all devices?

Hi,

can anybody reply to this and share his/her opinion?

Thanks a lot

Michal

----------  Předaná zpráva  ----------

Subject: Re: Phis in /proc/bus/input/devices same for all devices?
Date: středa 21 únor 2007 23:06
From: Marcel Holtmann <marcel@...tmann.org>
To: CIJOML <cijoml@...ny.cz>
Cc: bluez-users@...ts.sourceforge.net

Hi Michal,

> I use 2.6.20-mh1 patch and would like to differ devices based on Phis, but
> it is the same for all devices??
>
> I: Bus=0005 Vendor=045e Product=007c Version=0035
> N: Name="Microsoft Five Button Mouse"
> P: Phys=00:0D:88:8E:AB:2F
> S: Sysfs=/class/input/input19
> H: Handlers=mouse1 event6
> B: EV=7
> B: KEY=1f0000 0 0 0 0 0 0 0 0
> B: REL=103
>
> I: Bus=0005 Vendor=045e Product=007b Version=0039
> N: Name="Microsoft Bluetooth keyboard"
> P: Phys=00:0D:88:8E:AB:2F
> S: Sysfs=/class/input/input20
> H: Handlers=kbd event7
> B: EV=12000b
> B: KEY=10f80 44007 ffe01878 800d7ff febeffdf f3cfffff ffffffff fffffffe
> B: ABS=700 0
> B: LED=107
>
> I: Bus=0005 Vendor=046d Product=b3e3 Version=2503
> N: Name="Logitech Bluetooth Mediapad"
> P: Phys=00:0D:88:8E:AB:2F
> S: Sysfs=/class/input/input21
> H: Handlers=kbd event8
> B: EV=12000f
> B: KEY=7fff 2c3027 bf004440 0 0 1 10f80 8807c007 ffe67bfa d9415fff febeffdf
> ffefffff ffffffff fffffffe
> B: REL=40
> B: ABS=301 0
> B: LED=1f
>
> Shouldn't be there it's BDADDR?

please post this question to LKML. I am not sure that is the right
approach. Currently we fill in phys and uniq like this:

        strncpy(hid->phys, batostr(&src), 64);
        strncpy(hid->uniq, batostr(&dst), 64);

Maybe the input or HID subsystem should be changed to also export the
uniq values to udev.

Regards

Marcel

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