Fingerprinting

Over the last couple of days, I found the time to finish off the dpfp kernel-side driver so that it exports fingerprint data into userspace, to make it easier to investigate the image format.

I had it working relatively easily. Running a small program on /dev/dpfp0 produces 7 data files, one of which is the fingerprint data, the others are interrupt data and other blocks of data that are probably interesting but we don’t know the purpose of.

I was going to leave it at that (others seem to be very interested in the image format), but I thought I might as well have a quick look at the fingerprint data and see if I can find anything interesting. I had glanced at some data previously, but had not done anything with my findings – it’s awkward to work with until you reach the stage where you can obtain data with just a single command.

I noticed the strange structure that I saw before: the data appears to be separated into chunks, each chunk being separated by 26 zero bytes. Each chunk is about 358 bytes long, so I decided that one chunk may be equivalent to one row of pixels in an image.

I noticed that the final part of the transfer ends right in the middle of the zeroes. I also noticed that the number of zeroes between chunks varies a little here and there.

Unusual, but not totally out of the question. Maybe each chunk starts and ends with zeroes, which would mean each chunk starts halfway through these series of zeroes I was seeing. That would explain why the transfer ends halfway through a block of zeroes.

Picturing that in an image scenario (where 0 = black), I realised that this would result in two black columns down the left and right side of the image. I then recalled an image that Jose M Robles sent me recently: a raw image from a fingerprint scanner (not really sure which one) which had black columns down either side. Jose has been doing a fantastic job throwing around theories about the image format, sending me histograms, pixel averages, sample images like that one, etc. Jose’s experiments also seemed to indicate that the encryption was weak, and at this point, things were starting to fall together.

After a few more calculations I decided that the image data starts after a 64-byte header. I also deduced the width (358 + 26 zeroes = 384 pixels) and height (exactly 259 ‘rows’ of pixels are included in the transfer). I cut out the header and replaced it with a PGM header.

I was both happy and amazed to see the result:

No encryption whatsoever, despite DigitalPersona’s claims (PDF).
Update: Those claims may be true. The UareU 4000 isn’t advertised to be included in the MS devices, we just put 2 and 2 together and saw all the simlarities. Now that I have looked closer at the UareU 4000 behaviour, it looks like encryption may be in place on those devices (but not the MS ones).
Another update: I discovered that the devices do support encryption but the Microsoft devices ship with encryption turned off.

This isn’t a real fingerprint scan – I actually scanned one of my toes, to protect the identity of my innocent fingers. Proper scans look more fingerprint-like.

3 imagemagick commands later (invert colours, increase brightness, decrease gamma) and it is perfect for processing:

Fancy stuff. It is lucky that those solid black columns are there, otherwise this wouldn’t have been anything like as obvious. I’ll be rewriting the driver soon, to be more simplistic and to export PGM images straight from the /dev node.

19 Responses to “Fingerprinting”

  1. Mike Says:

    Dan… you rock.

  2. Peter Says:

    Awesome, Dan. You’re amazing…

  3. Anonymous Says:

    scanning your toe! incredibly funny! (and wise)

  4. dsd Says:

    Heh, I tried my palm, knuckles, and side of my hand but they just weren’t having the right effect (infact the scanner picks up some really weird things, will probably blog about that sometime). It was time to try the feet…

    Thanks people :)

  5. dsd’s weblog » Blog Archive » Breaking encryption the easy way Says:

    [...] dsd’s weblog it’s not you, it’s the e-talking « Fingerprinting [...]

  6. Christopher Says:

    Congratulations! Nice work.

  7. mp Says:

    Excellent work!

    If you take the housing off the device, is there a white/black band hidden on the underside of the housing probably near the glass?

    I’m just wondering how the device calibrates itself…

  8. Phillip Michael Says:

    Where can I get a copy of the code?

  9. dsd Says:

    See http://dpfp.berlios.de/

  10. Ricardo Navarro Says:

    Dan, I need to obtain a RAW image using the MS Fingerprint. Can you help me?

  11. dsd Says:

    In a few weeks there will be a library and driver released which will provide data in 8-bit monochrome format very easily. You are free to contribute code to convert that into whatever format you desire.

  12. amazed guest Says:

    [quote]other blocks of data that are probably interesting but we don’t know the purpose of.[/quote]

    Just a wild guest, maybe these blocks of data represent some kind of “hint” needed to identify fingerprints.
    For more information go to http://www.webopedia.com/DidYouKnow/Computer_Science/2004/fingerprint.asp
    [quote]
    Fingerprint scanning essentially provides an identification of a person based on the acquisition and recognition of those unique patterns and ridges in a fingerprint.
    [/quote]

    you rock!!!

  13. kkkkoaaa Says:

    Keep a good job up!

  14. sekar Says:

    woderful work

  15. dsd’s weblog » Blog Archive » Fingerprint enhancement and recognition Says:

    [...] A while ago, I posted some pretty pictures of my toe when I figured out the image format used by the Digital Persona and Microsoft fingerprint readers. [...]

  16. atlas Says:

    Yes the drivers is working with microsoft fingerprint reader!
    But, How to use it next?
    I’m using gnome and gdm for example…how to log into gnome with my fingerprint?

    Thanks a lot for your job,
    Best regards.

  17. dj Honk Says:

    I did some tests with the program. First thing was that the proportions seemed to be wrong. So I inked my finger, got a print on paper, scanned it and compared it with the image from the FPS. That seemed to be too short (ore too wide). Additionally I had the impression, as if every now and then in the image a line was missing. Then I remembered some stuff I learned in earlier days about television. I googled for some more information and everything fits.

    In NTSC a picture is 384 pixel high and 576 pixel wide. The picture is transmitted in two halfs with one picture ending in the middle of the line and starting in the middle of the next first line. Digital Persona is using a simple chip from a video-camera and the camera in the FPS is turned by 90 degrees. Good and extremely cheap solution!

    There aught to be another half picture in the transmitted data and this one should end with half a line. Additionally I saw pictures from the same sensor using other SDK´s with the proportions looking right.

    Best regards.

  18. soumaya Says:

    I need a source code for finger print image enhansment with gabor filter (matlab)
    pleas help me.
    thank you very much

  19. soumaya Says:

    I am a student.
    I need a source code for image enhansment using gabor filters please help me..
    thankyou very much

Leave a Reply

You must be logged in to post a comment.