I did compare the USB traces between 4000B and 4500 with 1.3.0 SDK. Like I mentioned in my previous email, the driver does NOT send any "firmware" data blob to 4500. It DOES send "firmware" data blob to 4000B. Now I don't know where to start to figure out how to disable hardware encryption since we don't know what's in the "firmware" (data chunk? or compiled binary code? and what the compiler is?). I think DigitalPersona uses Windows Crypto API for the encryption. I need to do more study to see if it's possible to decrypt the image. An interesting thought is how they decrypt the image under Linux? They write some compatible library to simulate the windows Crypto API?
What do you guys think? Ji Yang From: [email protected] [mailto:[email protected]] On Behalf Of Artem Egorkine Sent: Sunday, May 24, 2009 9:04 PM To: [email protected] Subject: Re: [fprint] About DigitalPersona U.are.U 4500 On Mon, May 25, 2009 at 6:54 AM, Philip Nelson <[email protected]> wrote: On Mon, May 25, 2009 at 06:43:28AM +0300, Artem Egorkine wrote: > I am wondering, are there _any_ SDKs that support "U.are.U 4500" readers? > Digital Persona themselves offer SDK 1.3.0 (Windows) and 1.1.0 (Linux) for > download. These same SDKs were available before the "U.are.U 4500" reader > came to market and, to no surprise, the SDK datasheet only mentions 4000 and > 4000B. The free digitalperson sdk (1.3.0) does support the 4500 reader (perhaps unofficially?). I have a program that uses this SDK and we ordered a 4500 reader to see what it was like, I didn't expect it to work, but I plugged it in and it Just Worked with my program. Would be interesting to compare the USB traces of 4000B and 4500 devices with 1.3.0 SDK...
_______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
