uunicorn

Do you know if it is a Match-on-Chip or Match-on-Host device?

@giovannicaligaris some sensors are capable of identifying a finger without exposing any biometric information to the host computer. Those are Match-on-Chip. Can you share a link to a Windows driver...

Your driver seems to be [here]( https://novacustom.stackstorage.com/s/s2zVcQyd004hRQJ?dir=%2FPC50D-PC70D%2FOptions%2F02_Finger%2FSynaptics_Gamma&node-id=179613). It is not quite clear from the `.inf` file if it is MoH or MoC. If you manage to set up the [synaWudfBioUsb-sandbox](https://github.com/uunicorn/synaWudfBioUsb-sandbox)...

Almost all the USB communication between the sensor and the host is TLS encrypted. There are two ways to work around it. 1. Use Windows debugger to extract the session...

Try renaming `synaWudfBioUsb115.dll` to `synaWudfBioUsb.dll` and running the script again. `a.exe` looks for `synaWudfBioUsb.dll` file.

That's odd. Can you share a link to the driver which you are using?

This looks more promising. Can you check that the device path is calculated correctly in `run.sh`? ``` DEVICE=$(lsusb | grep 'Fingerprint' | awk -F '[^0-9]+' '{ print "/dev/bus/usb/" $2 "/"...

Ok, I think there are a few problems. I guess you'll need to get the `DEVICE` variable to work properly first. As part of initial pairing the sensor is rebooted...

@himekifee , I've created a `python-validity` Discord server, but I'm not very familiar with Discord.

Hi @candyman2903 , `06cb:00be` is not currently supported. You can try setting up [synaWudfBioUsb-sandbox](https://github.com/uunicorn/synaWudfBioUsb-sandbox) environment and capturing the pair/enroll/identify logs - this may help to add the support for your...