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  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:	Sun, 1 Mar 2009 12:16:24 +0900
From:	Kyungmin Park <>
To:	Dmitry Torokhov <>
Cc:	Andi Kleen <>,,
Subject: Re: [PATCH] Input notifier support


On Sun, Mar 1, 2009 at 12:07 PM, Dmitry Torokhov
<> wrote:
> On Sun, Mar 01, 2009 at 11:52:56AM +0900, Kyungmin Park wrote:
>> On Sun, Mar 1, 2009 at 9:42 AM, Dmitry Torokhov
>> <> wrote:
>> > On Sun, Mar 01, 2009 at 12:34:38AM +0100, Andi Kleen wrote:
>> >> Kyungmin Park <> writes:
>> >>
>> >> > Some hardware doesn't connected with key button and led. In this case key should be connected with led by software. Of course each application can control it however it's too big burden to application programmer.
>> >> >
>> >> > So add input notifier and then use it at other frameworks such as led.
>> >> > Of course, other input device can use this one.
>> >> >
>> >> > Any commnets are welcome.
>> >>
>> >> It looks like the perfect interface for a password stealing root kit.
>> >>
>> >> Yes there are probably other ways to do this, but still this seems to
>> >> make it very easy.
>> >>
>> >
>> > We already have good interface for that. That's why you want to limit
>> > access to /dev/input/eventX ;) and not make it world-readable.
>> >
>> Hi Dmitry,
>> Could you tell me know which interface you're talking?
>> I agreed it's not good idea to pass key code value to drivers. it
>> caused security issues.
> The interface to steal the root password. One can simply open all input
> devices and read all events (if the process has sufficient rights).
"I don't think we need to do the notifier route. It is very easy to add
another input handler in style of rfkill-input or apm-power that would
listen to events from all ungrabbed input devices and act accordingly.
Your LED trigger example should work very well if implemented as another
input handler."

Ah, I mean the this one, sorry for confusing you. You mean add led
trigger using input handler.
Then my question how to know which input device is connected trigger
As know it's input device is allocated by dynamically then how do we
know which input event is used and set?

Thank you,
Kyungmin Park
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists