uunicorn

Yes, there's an open PR to fix it, but I think some work is still required. Feel free to contribute: https://github.com/uunicorn/python-validity/pull/92#issuecomment-890463731

Hi @faaizajaz , I think it is the intended behavior if you wish your `login` keyring to be protected/encrypted. The fingerprint authentication itself yields no secrets which could be used...

It should be safe to ignore `xpfwext` instructions as long as the Windows driver for your device does not have one. I'm not sure where or why it crashed, though....

Thanks. > My logs can be found here: logs.zip > `Unhandled exception: unimplemented function POWRPROF.dll.PowerSettingRegisterNotification called in 64-bit code (0x000000007bc64eac).` This looks like the root cause of the crash. Your...

Sorry I've disappeared for a month. I've just pushed the promised stub. I managed to reproduce your crash using the logs, and I can confirm that the stub stops it...

Looking at the logs, winusb.dll stub has prevented the factory reset by intentionally crashing. The driver attempted to do a factory reset because of the initial handshake has failed. And...

> Exception: Failed: 0401 This looks suspiciously similar to #71 . Can you check which device you have with `lsusb`?

Yeah, as explained in #71 , match-on-host devices are not supported by python-validity. There is [a branch](https://github.com/3v1n0/libfprint/blob/vfs0090/README.md) of the official libfprint project which adds partial 138a:0090 support. "Partial" here means...

Yeah, neither of these projects receive much love unfortunately. Ages ago I created a branch of python-validity to add a proper support for match-on-host devices (138a:0090 specifically). I wanted it...

@neithere , it does not look like anyone is actively working on this PR the moment. If you fork and complete the work I mentioned in https://github.com/uunicorn/python-validity/pull/92#issuecomment-890463731 I'm happy to...