Re: Driver for Microsoft USB Fingerprint Reader

Alan Cox wrote:
> Ar Llu, 2006-07-03 am 18:11 -0400, ysgrifennodd Daniel Bonekeeper:
>> That's one problem: I don't want to create one more userspace
>> interface for that. I suppose that all the hundreds of fingerprint
>> readers that ships with a SDK have their own way of doing that.. that
>
> The very cheap readers all appear to be fairly crude image scanners, and
> they even lack hardware encryption/perturbation so they are actually of
> very limited value.

As I said before, usefulness is something relative, and sometimes, security is not a concern (even when talking about fingerprint readers).
My intention with this is to try to create a catalog of fingerprint readers' properties and I think that taking a look at vendors' SDKs would be a good start.
As pointed out by Greg, it would be also interesting to export those properties via sysfs instead of structure passing (or in addiction, not sure yet).
I'm not sure though about relating fingerprint devices with V4L2 (even the cheapest ones). Some other considerations discussed with Greg are also:

1) extending those device informations to other classes, not only to fingerprint readers
2) maybe using another layer to hold device properties based on classes ( device driver -> device information layer -> sysfs+kobjects ) so we can have specific properties for "fingerprintreader" objects and easier ways to export them to the sysfs layer, without explicit declaration on the device driver
3) extend that layer also to non-USB devices ( bus-independent )

Maybe sysfs classes could have a list of default properties (for example, /sys/class/fingerprint objects could hold a list of commom fingerprint properties).

Crude, like beauty, is in the eye of the beholder. I like hardware which
does as little as possible because I can then apply the appropriate
software to the data. I can see that if cost is no object and the
algorithm is never going to change, I can build all that stuff into the
device. But I don't need to... as long as I can take the data, pass it
through a transform, and get out of that a key which works or not, then
I can do useful things with it.

Useful includes many things. I'm playing with using a combined secret
and SecureID(tm) to decrypt and boot a virtual machine, such that I can
do many unrelated things and have reduced chance of "unintended data
migration." It also allows ad-hoc users (read that as undergrads) given
a temporary machine fairly easily, visiting professors, etc.

I can see the benefits of having the whole package be a black box, I
hope I have explained why I find even a dumb scanner useful in some cases.

--
Bill Davidsen < davidsen@xxxxxxx >

Which fingerprint reader are you using ?