On Sunday 25 November 2007, Daniel Drake wrote: > Mark Vytlacil wrote: > > When I reboot to linux from Win XP, the image seems to be encrypted until > > I replug the device. I had to get an updated driver to work with Win XP. > > I wonder if ms is now using encryption in the new driver. > > Yes, the new drivers do use image encryption. But your understanding is > actually the inverse of the actual problem. > > fprint under Linux *disables* the encryption bit. When you reboot to > windows, the encryption bit is still disabled, but the Windows driver > assumes it is enabled. I guess it then tries to decrypt the plaintext > greyscale image data, resulting in some jumbled mess which you thought > was encrypted data.
Actually my experience is really the reverse. When I boot to windows whether from a cold start or from linux, it sets up things just fine for itself and I login with my fingerprint, no problem. When I boot to linux from a cold start, everything works fine. When I boot to linux after windows, I cannot login with fprint and using fprint_demo gives me an jumbled image. If I unplug and replug the device under linux, it works fine. I interpret this as meaning that the new windows driver has found a different way to turn on encryption and that fprint is not turning it off or maybe fprint is somehow not initializing the device when I reboot to linux. > This is hard to solve properly, but there may be something we can do. > Could you please file a bug for this at > http://www.reactivated.net/fprint/bugs/ I will do that. Thanks for your continued work. > > Thanks! > Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
