mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@elstempel.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux@horizon.com, linux-kernel@vger.kernel.org
Subject: Re: Driver for Microsoft USB Fingerprint Reader
Date: Thu, 06 Jul 2006 23:39:44 +0200	[thread overview]
Message-ID: <E1FybZs-0000e5-5K@be1.lrz> (raw)
In-Reply-To: <6vFQ5-1iV-71@gated-at.bofh.it>

Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Iau, 2006-07-06 am 00:48 -0400, ysgrifennodd linux@horizon.com:

>> As far as I can tell, the only thing you want is AUTHENTICATION - you
>> want proof that you are getting a "live" scan taken from a user
>> who's present, and not a replay of what was sent last week.
> 
> Read the papers on the subject. If I can get copies of the unencrypted
> data I can use those to make fake fingers.

Copies like the one on the glass I used in the restaurant ...

> A finger print is personal data, arguably sensitive personal data. That
> means there are lots of duties to store it securely.

That's why every waiter will assiduously clean your glass. won't he?

> It is also very
> hard to revoke a fingerprint so theft of data is highly problematic as
> it will allow me to generate fake fingers.

That's the problem: You can't know who is acting responsibly and who isn't.
Therefore you can't reuse your fingerprint on different sites.

> Theft of encrypted data might
> allow replay attacks on one PC. Big deal.

ACK. It should be protected by a nonce, too, as long as you depend on
encryption. You should also authenticate the reader before prompting for
a fingerprint, otherwise the replacement device might store the image to a
secondary location. And don't forget to prompt for cleaning the scanner, I
have heared rumors about scanners erroneously authenticating the previous
user. You should also install a camera preventing an attacker to place his
own scanner on top of yours.
-- 
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html

       reply	other threads:[~2006-07-06 21:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6vtYr-w2-5@gated-at.bofh.it>
     [not found] ` <6vFQ5-1iV-71@gated-at.bofh.it>
2006-07-06 21:39   ` Bodo Eggert [this message]
2006-07-06  4:48 linux
2006-07-06 12:26 ` Daniel Drake
2006-07-06 17:38 ` Alan Cox
2006-07-06 17:49   ` Joel Jaeggli
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 16:32 Daniel Bonekeeper
2006-07-03  6:51 Daniel Bonekeeper
2006-07-03  8:52 ` Daniel Drake
2006-07-03 10:04 ` Alon Bar-Lev
2006-07-03 18:04   ` Daniel Bonekeeper
2006-07-03 18:16     ` Alon Bar-Lev
2006-07-03 20:53       ` Daniel Bonekeeper
2006-07-03 21:45         ` Greg KH
2006-07-03 22:11           ` Daniel Bonekeeper
2006-07-03 22:26             ` Greg KH
2006-07-03 23:24               ` Daniel Bonekeeper
2006-07-03 23:29                 ` Greg KH
2006-07-04  0:04                   ` Daniel Bonekeeper
2006-07-04  0:13                     ` Greg KH
2006-07-05 17:58                     ` Daniel Drake
2006-07-05 18:09                       ` Daniel Bonekeeper
2006-07-05 18:55                         ` Daniel Drake
2006-07-05 19:46                           ` Daniel Bonekeeper
2006-07-05 23:23                             ` Daniel Drake
2006-07-06  2:05                               ` Daniel Bonekeeper
2006-07-06 10:35                                 ` Daniel Drake
2006-07-04  3:56               ` Daniel Bonekeeper
2006-07-04  3:58                 ` Greg KH
2006-07-03 22:35             ` Alan Cox
2006-07-03 22:49               ` Daniel Bonekeeper
2006-07-04  8:39                 ` Alan Cox
2006-07-05  4:01               ` Bill Davidsen
2006-07-05 15:55                 ` Daniel Bonekeeper
2006-07-03 11:44 ` Alon Bar-Lev
2006-07-03 15:00   ` Valdis.Kletnieks
2006-07-03 17:09     ` Alon Bar-Lev

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=E1FybZs-0000e5-5K@be1.lrz \
    --to=7eggert@elstempel.de \
    --cc=7eggert@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    /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

all inboxes | Powered by JetHome®