From: Daniel Drake <dsd@gentoo.org>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driver for Microsoft USB Fingerprint Reader
Date: Thu, 06 Jul 2006 13:26:53 +0100 [thread overview]
Message-ID: <44AD018D.8050204@gentoo.org> (raw)
In-Reply-To: <20060706044838.30651.qmail@science.horizon.com>
linux@horizon.com wrote:
> I utterly fail to see why multiple, generally knowledgeable people are
> claiming that encryption in a fingerprint scanner is desirable.
>
> 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.
>
> This is called "freshness" and is usually provided by including a
> random "nonce" (known in other contexts as "magic cookie") in the
> authenticated data.
The Digital Persona readers apparently use a challenge-response
authentication scheme for the encryption. I think I know the
challenge-sending and response-reading command structure but have not
yet examined their effect on the encrypted fingerprint data.
> Not that I expect "A-1 Computer Corporation" in Shenzhen to have a clue
> about these things, but you'd think that Microsoft would have one or
> two competent employees left on the payroll.
Now theres an interesting story in this area. The Microsoft fingerprint
readers are based on Digital Persona devices, and actually they seem to
be completely identical. But when comparing bus traffic for the DP
devices vs the MS devices, the DP devices send encrypted fingerprint
data and the MS devices send it as unencrypted 8-bit greyscale.
Anyway, further investigation shows a 1 bit difference in the firmware
uploaded to each device, and I have confirmed that this bit turns
encryption on and off.
IOW, MS's device are capable of encryption but they explicitly turned it
off at the firmware level.
Daniel
next prev parent reply other threads:[~2006-07-06 12:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 4:48 Driver for Microsoft USB Fingerprint Reader linux
2006-07-06 12:26 ` Daniel Drake [this message]
2006-07-06 17:38 ` Alan Cox
2006-07-06 17:49 ` Joel Jaeggli
[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
-- 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=44AD018D.8050204@gentoo.org \
--to=dsd@gentoo.org \
--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