resilar / hotfinger Goto Github PK

Most fingerprint readers have a LED activity indicator which turns on when there is an ongoing identify operation. In HotFinger, the fingerprint reader is held constantly in "identifying" mode in order to capture touches. Therefore, the LED indicator stays always on when using HotFinger (even if running in the background or minimized in the system tray). This can be quite annoying to some people.

An ideal solution would be something like monitoring presence (i.e., is the user touching the sensor) so that identify could be performed whenever needed instead of all the time. Unfortunately, at least the basic WinBio API does not seem to have support for this. There may be a way to implement the functionality using low-level hacks (Sensor Adapter Functions looks promising).

Alternatively, toggling HotFinger's identification on/off based on a configurable hotkey may be an acceptable solution as well.

Hi! Firs of all, thanks a lot. That app is the only one I found that fulfill this role.
Other than that, I would like to ask for help with that problem written on issue #6. I, too, have a Windows Hello compatible reader, but I'm getting the same error. Probably because of the same reasons, too. Is there a way to solve this? Maybe if I modify the code to save only 1 finger on the private pool? Thanks!!

The current mess can be simplified a lot.

Uninstallation is currently the only supported way to delete enrollments. Moreover, the GUI does not show which subfactors (fingers) are enrolled. The root issue is that certain WinBio enumeration functions are broken under Wow64 a lacking WinBio API (see the next comment), which prevents us listing enrollments for deletion or other purposes.

Old info: Wow64 registry redirection of HKLM\SOFTWARE seems to break WinBio's enumeration of enrollments/templates because WinBio.dll fails to read 64-bit WinBio registry keys due to missing KEY_WOW64_64KEY flag. For a possible workaround, see Wow64 registry reflection and in particular functions RegEnableReflectionKey()/RegDisableReflectionKey().

If the enumeration cannot be fixed with reasonable effort, then we could try to call WinBioDeleteTemplate() with WINBIO_ID_TYPE_WILDCARD to delete all enrollments for a specific subfactor (finger). However, according to the documentation, this requires administrator privileges and thus is not a feasible solution. Alternatively, a list of successful enrollments could be maintained in settings.ini by HotFinger.

In VirusTotal, 6/67 engines falsely detect hotfinger.exe as malicious. This is bad because the 6 engines include popular antivirus software such as Avast, AVG, Cylance & Symantec. Users do not like this, so do something about it. Possible solutions:

1. Carefully modify HotFinger to resolve false positives one by one. However, this is non-trivial because 4 out of the 6 false detections are based on heuristics (that is, cannot be addressed by changing few bytes in the hotfinger.exe executable).

2. Do not modify HotFinger itself, but use existing packer/protector to make hotfinger.exe undetectable. Writing a custom "dropper" is also an option.

I'm trying to download hotfinger.exe from here: https://github.com/resilar/HotFinger/releases/tag/v0.1.0

I get this error: https://i.imgur.com/mWAzx42.png

Hey. I run into the following issue with my USB fingerprint reader. The inbuilt (Synaptics) one seems to work fine with your software.

Install works fine, but when I try to enroll a command, it shows error code 0x800106EF

My guess is, this reader is just "not compatible"? It works natively with Windows Hello, so my guess was, that it is in fact "WBF-compatible".

I'ts this one: https://acekool.net/products/fingerprint-reader-hub-with-type-c-wire-and-3usb-port
and I did not install any additional software from the manufacturer.

getting this error every time i enroll a software

The current code locates fingerprint sensor devices by enumerating the registry tree HKLM\System\CurrentControlSet\Enum. A better approach would be to use SetupDi* family of functions to enumerate the biometric device class, i.e., ClassGuid = {53D29EF7-377C-4D14-864B-EB3A85769359}.