On Tue, May 26, 2009 at 8:01 PM, Jeff Yang <[email protected]> wrote:
> 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? > > It is quite possible that the linux API (version 1.1.0) does not support 4500 at all. That would be my guess. On the other hand, Digital Persona is not the only figerprint devices SDK out there. There is another interesting one, http://www.griaulebiometrics.com/page/en-us/fingerprint_sdk/what_is_new It was the case with 4000B that they uploaded a different firmware blob than DP driver (and it was the same under windows and linux). While their drivers do not officially support 4500, it may be worth to try it out in case it just works. But the chances of that happening are very slim as well since in their 2009 version of the SDK they have added "support to Digital Persona using manufacture's driver". If we were able to interface with the original 4000B firmware, understand the calls and data and decode the encrypted image, I'm sure we would have a better chance to interface with 4500. -Artem
_______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
