linux-kernel - Re: [RESEND] [PATCH] Input: add appleir USB driver

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:	Tue, 5 Oct 2010 18:07:36 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Bastien Nocera <hadess@...ess.net>,
	"linux-input" <linux-input@...r.kernel.org>,
	Jiri Kosina <jkosina@...e.cz>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND] [PATCH] Input: add appleir USB driver

Am Dienstag, 5. Oktober 2010, 17:55:52 schrieb Dmitry Torokhov:
> > Yes, but based on sane timing. From the time stamps user space
> > would conclude that the key had been pressed at an unknown time
> > before open and released at the time the event indicates. Possibly
> > it would compute that the key had been held for at least hours.
> > 
> 
> I do not understand. If a client never seen the "press" event and only
> saw "release" event it can't make any assumptions about timing. Press
> could be a millisecond ago or an hour ago, it just does not know. And
> such scenario can easily happen if the client is second to open the
> device.

As soon as you open a device you see key presses. If you see a release
without a press, the press must have happened before you opened.
So if you know when you opened and when a key is released, you'll
have a lower limit on how long the key must have been held down.

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