All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] avoid keyloggers: enter password with mouse	(virtual keyboard)
Date: Wed, 14 Apr 2010 17:30:50 +0200	[thread overview]
Message-ID: <20100414153050.GA3966@tansi.org> (raw)
In-Reply-To: <v2q61722e191004140611zc1eb0076xe17b9fdf80b09594@mail.gmail.com>

On Wed, Apr 14, 2010 at 03:11:50PM +0200, Olivier Sessink wrote:
> 2010/4/13 Milan Broz <mbroz@redhat.com>:
> > On 04/13/2010 09:38 PM, Heinz Diehl wrote:
> >> On 13.04.2010, Arno Wagner wrote:
> >>
> >>> If he has a hardware Keylogger on his system, somebody
> >>> did physically manipulate his machine and all bets
> >>> are off anyways.
> >>
> >> Of course.
> >>
> >> So this boils down to the fact that a software keyboard is useless :-)
> >> If somebody had physical access to the machine, there will be no
> >> way to detect any backdoors, and if somebody had been able to install a
> >> software keylogger, this person has already gained root access to the machine
> >> and could simply have read the master key from memory or whatever, you
> >> name it.
> >
> > I just remember schoolbook example with "software keyboard" where
> > such keyboard was used to enter PIN using mouse.
> >
> > Instead of sending the key scan code back to hidden logger program,
> > it simply send rectangular areas on screen (screenshot) centered to
> > mouse clicks...
> > So attacker can easily read pin code from these few-bytes small pictures
> > of visual keyboard:-)
> 
> 1) a hardware keylogger costs about $100,-, can be ordered on many
> places, and requires no technical expertise whatsoever. A hardware
> keylogger is 100X easier than software modifications, or a
> hardware-mouse-sniffer (I've never seen them)

It is also about 10'000 times easier to find. 

> 2) we have protected ourselves from software modifications already
> (boot from USB). So a hardware keylogger is our biggest threat.

As an attacker with physical access can modify your boot
USB device contents or replace the device in the first place.
Adding a software keyboard sniffer is easy with that.

> 3) most virtual keyboards I have seen are randomly positioned on the
> screen, so you really need a well-positioned camera to capture the
> password (which, again, is much more complex than a hardware
> keylogger, requires a lot of technical expertise).

But physically getting to your computer to place, and, more important
later retrieve, a hardware keylogger is easy? 

I still think your security analysis is invalid. For example, why 
not attach the keyboard cable in such a way that placing a hardware 
keylogger in it gets very hard, e.g. needs cable cutting? If your 
attackers have no technical expertise, that would reliable defeat 
them. This can be as easy as gluing the keyboard connector in, or 
fixing it in place with hard to open cable ties.

Maybe tell us a bit more about your scenario?

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2010-04-14 15:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 15:10 [dm-crypt] avoid keyloggers: enter password with mouse (virtual keyboard) Olivier Sessink
2010-04-12 17:15 ` Arno Wagner
2010-04-12 17:58   ` Heinz Diehl
2010-04-13 15:48     ` Arno Wagner
2010-04-13 19:38       ` Heinz Diehl
2010-04-13 19:55         ` Milan Broz
2010-04-14 13:11           ` Olivier Sessink
2010-04-14 15:30             ` Arno Wagner [this message]
2010-04-14 18:42               ` Olivier Sessink
2010-04-14 23:30                 ` Arno Wagner
2010-04-14 23:54                   ` Sven Eschenberg
2010-04-15  6:24                   ` Milan Broz
2010-04-15 10:00                     ` Arno Wagner
2010-04-15  7:50                   ` test532
2010-04-15 10:04                     ` Arno Wagner
2010-04-15 17:44                   ` Richard Zidlicky
2010-04-15 18:04                     ` [dm-crypt] avoid keyloggers: enter password with mouse(virtual keyboard) Vladimir Giszpenc
2011-10-04 15:02                   ` [dm-crypt] avoid keyloggers: enter password with mouse (virtual keyboard) Jan
2011-10-04 18:28                     ` [dm-crypt] avoid keyloggers: enter password with mouse?(virtual?keyboard) Arno Wagner
2011-10-04 21:42                       ` Jan
2011-10-04 22:48                         ` Arno Wagner
2011-10-05  9:37                           ` Jan
2011-10-05 12:15                             ` Arno Wagner
2011-10-05 18:18                               ` Jan
2011-10-04 18:48                     ` Heinz Diehl
2011-11-30 14:22                       ` Ma Begaj
2011-11-30 14:28                         ` Ma Begaj
2011-11-30 14:46                         ` Arno Wagner
2011-11-30 15:11                           ` Ma Begaj
2010-04-12 21:43   ` [dm-crypt] avoid keyloggers: enter password with mouse (virtual keyboard) Olivier Sessink
2010-04-12 17:51 ` Richard Zidlicky

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=20100414153050.GA3966@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.