From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [PATCH] Input notifier support Date: Sat, 28 Feb 2009 16:42:59 -0800 Message-ID: <20090228164126.ZZRA012@mailhub.coreip.homeip.net> References: <20090225044730.GA9106@july> <87skly16gh.fsf@basil.nowhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-gx0-f174.google.com ([209.85.217.174]:59866 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754974AbZCAAnM (ORCPT ); Sat, 28 Feb 2009 19:43:12 -0500 Content-Disposition: inline In-Reply-To: <87skly16gh.fsf@basil.nowhere.org> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Andi Kleen Cc: Kyungmin Park , linux-kernel@vger.kernel.org, linux-input@vger.kernel.org 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. -- Dmitry