public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dag-Erling Smørgrav" <des@des.no>
To: David Wagner <daw@cs.berkeley.edu>
Cc: rwatson@FreeBSD.org (Robert Watson),
	freebsd-hackers@FreeBSD.org, linux-kernel@vger.kernel.org,
	Oliver Pinter <oliver.pntr@gmail.com>
Subject: Re: Security: information leaks in /proc enable keystroke recovery
Date: Wed, 19 Aug 2009 03:57:44 +0200	[thread overview]
Message-ID: <861vn85zvr.fsf@ds4.des.no> (raw)
In-Reply-To: <200908162109.n7GL9JNK029605@taverner.cs.berkeley.edu> (David Wagner's message of "Sun, 16 Aug 2009 14:09:19 -0700 (PDT)")

David Wagner <daw@cs.berkeley.edu> writes:
> I agree we certainly shouldn't discuss the keystroke recovery attack
> as hypothetical, because it is clearly not hypothetical: the authors
> implemented it and found that it works.

It *is* hypothetical.  They were able to collect some keystrokes (but
not all) in Linux, but IIUC, all they could do in FreeBSD was figure out
whether or not a key was pressed at a certain time (or during a certain
interval).  They *hypothesize* that the interval between keystrokes can
be used to identify the keys being pressed, but they haven't actually
done it.  I can imagine - purely hypothetically - that it would be
possible, but only while the user was typing running text; the
parameters would vary greatly from typist to typist, and between
keyboard layouts, and you could probably defeat it pretty easily (at
least some of the time) by deliberately typing slowly and arythmically,
e.g. typing in your password with only one finger.

DES
-- 
Dag-Erling Smørgrav - des@des.no

  parent reply	other threads:[~2009-08-19  9:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 22:21 Security: information leaks in /proc enable keystroke recovery David Wagner
2009-08-15 23:25 ` Oliver Pinter
2009-08-16 20:06   ` Robert Watson
2009-08-16 21:09     ` David Wagner
2009-08-16 23:25       ` Robert N. M. Watson
2009-08-17  0:58         ` David Wagner
2009-08-17 10:11           ` Robert Watson
2009-08-19  1:57       ` Dag-Erling Smørgrav [this message]
2009-08-16  0:33 ` Theodore Tso
2009-08-16  0:44   ` David Wagner
2009-08-16  1:33     ` Theodore Tso
2009-08-16  8:18       ` david
2009-08-17  0:31       ` David Wagner
2009-08-17  2:22         ` Theodore Tso
2009-08-17  2:45           ` James Morris
2009-08-17  3:16             ` Arjan van de Ven
2009-08-21 14:02           ` Pavel Machek
2009-08-22 17:22             ` Henrique de Moraes Holschuh
2009-08-17  1:39 ` Amerigo Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861vn85zvr.fsf@ds4.des.no \
    --to=des@des.no \
    --cc=daw@cs.berkeley.edu \
    --cc=freebsd-hackers@FreeBSD.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.pntr@gmail.com \
    --cc=rwatson@FreeBSD.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox