possible to expand this to Kensington Validity 06cb:0088 ?

[jontis]

Hi, I started following your:
https://github.com/uunicorn/synaWudfBioUsb-sandbox

But encountered a slightly different folder structure and that's about where my skills end.
The item is a Kensington Verimark USB fingerprint reader.
If you could determine if it is suitable for this project and guide me how to proceed, I'd be happy to help.

Folder structure of the driver is:
KensingtonFingerprintApplication.exe
KensingtonFingerprintApplication.lnk
synaBscAdapter66.dll
SynaCP66.dll
SynaFPCoInstaller.dll
SynaFPService.exe
synahidumdf.sys
SynaU2F.exe
synaumdf.cat
synaWudfBioUsb66.dll
synaWudfBioUsbKensProd.inf
synaWudfU2fhid.dll
synaWudfU2fhid.ini
WudfUpdate_01011.dll

synaWudfBioUsbKensProd.inf.txt

[uunicorn]

Looking at the .inf file, it appears that the driver GUID is the same as for 0097 and 009a (96710705-B080-4B29-A3EC-B16935AE663A), which means that synaWudfBioUsb-sandbox approach might just work. Have you tried renaming synaWudfBioUsb66.dll to synaWudfBioUsb.dll and following the rest of synaWudfBioUsb-sandbox instructions? I know, it's not an easy task. I've tried to make synaWudfBioUsb-sandbox and wine setup to be a bit more user friendly but got bogged down by the Wine packaging and gave up.

Do you know if your sensor is Match-on-Sensor or Match-on-Host?

[oofnikj]

@uunicorn I'm about done writing up some instructions for building the patched Wine in a Debian container, happy to open a PR for it if you're interested.

[jontis]

I can absolutely try to rename the dll.
What about:
Copy *.xpfwext file from the extracted windows driver to c:\windows\system32 inside youre new Wine prefix
There is no such file.

The sensor is claimed to be match-on-host.

[uunicorn]

There is no such file.

Well, fwext is just an overlay on top of firmware in ROM. Perhaps it is not needed for this device.
The .inf file has an empty [FWextCopy] section, which implies that it is expected.
synaWudfBioUsb-sandbox may still work.

The sensor is claimed to be match-on-host.

This is unfortunate. python-validity lacks support for MoH devices at the moment.
I've provided a bit more details in this comment.

[jontis]

Interesting. Thank you for explaining.

In that case, I might get it's younger sibling to experiment with adding support.
It announced to be match-in-sensor.

Kensington VeriMark IT Fingerprint Key

What do you think of this?

[uunicorn]

What do you think of this?

I think we can definitely try. Probably worth raising another issue with a correct usb id.

[jaxjexjox]

I apologise, I think I've gone and made a new thread, when I should have read this one.
Am I correct in interpreting this discussion as the :0088 device isn't going to work / may not ever work?

[himekifee]

I apologise, I think I've gone and made a new thread, when I should have read this one.
Am I correct in interpreting this discussion as the :0088 device isn't going to work / may not ever work?

You should look for Validity90, that one is generally for MoH.

[uunicorn]

@jaxjexjox

isn't going to work / may not ever work?

It is not that it may never work, it is just (unlike Validity90) there is no existing framework to do the fingerprint matching inside the python-validity code at the moment. You are more than welcome to contribute it though.

[jaxjexjox]

I apologise, I think I've gone and made a new thread, when I should have read this one.
Am I correct in interpreting this discussion as the :0088 device isn't going to work / may not ever work?

You should look for Validity90, that one is generally for MoH.

I thought it was all but abandoned several years ago?

[himekifee]

Well, yes, but that is the most relative project.

[uunicorn]

I think @3v1n0 's branch of fprintd is still alive: https://github.com/3v1n0/libfprint

[jaxjexjox]

Thanks for your hard work and replies, people like you make using free software awesome, appreciate it.

[jontis]

About Validity90, I just want to add that I wouldn't call it abandoned. I think the project was making progress and had a lot of traction among users. Then the owner disappeared. No idea if something happened to him, or if he got tired of the project and made a new github identity. I believe something happened to him, or he would have transferred ownership of the project. 3v1n0 picked it up, but it doesn't seem to keep the same pace.