Fingerprint Unlock Module Version 1.3.0

0 views

Skip to first unread message

Tea Rochlitz

unread,

Aug 3, 2024, 4:29:53 PM8/3/24

to resretereb

It looks like an issue with the firmware and libfprint on the new module, in the Goodix drivers specifically, on the firmware type matching being done: libfprint/drivers/goodixmoc/goodix.c master libfprint / libfprint GitLab

Tangent: My older module is still functional, but the adhesive in the housing has deteriorated, causing the face of it to tilt and lift, hence the replacement. I suspect this is due to 90% of my usage of the device is while having the lid closed and doing CPU heavy work, causing excessive heat buildup in the case.

Hello, I'm currently developing drivers for Goodix fingerprint chips with a community. The chips use the TLS protocol to communicate. So we need to write a PSK key. But to do that we need to erase ...

And some linux driver work here, but this specific device is currently omitted: GitHub - goodix-fp-linux-dev/goodix-fp-dump: All our work to make Goodix fingerprint sensors work on Linux. Thanks to @markusressel and @PJungkamp for sponsoring.

Framework currently lists compatibility with libfprint 1.92.0 or newer: Fingerprint enrollment
I can confirm this newer firmware does not work for the latest libfprint v1.94.5 libfprint / libfprint GitLab

Was this firmware change on Marketplace shipped parts intentional?
If so, was it tested with any linux distribution by Framework?
And is there/will there be a method supplied by either Goodix / Framework for updating/downgrading the firmware for Linux compatibility?

I started a Windows 10 VM, and forwarded the Goodix USB interface to it.
Windows recognized that it was a Goodix device, but was unable to communicate with it, and Windows Update did not have any standard drivers for it.

These pages cover Drivers / BIOS firmware for the mainboard, but if smaller components (like the fingerprint reader) are having firmware updated / changed by the driver install, it would be great to have that info listed in addition to the driver version info.

There was never an official resolution from the Framework side of things on this, after I informed support that using the Windows driver installer in a VM changed the firmware version, allowing the reader to work, the issue was closed.

Ah, Manjaro and LightDM. I had to pull official fingerprint reader support because it broke on the Manjaro side of things recently. It should still be usable for sudo, but logging is not supported (officially).

The Biometric Fingerprint Reader plug-in allows for fast identification and secure verification capabilities that enable your FileMaker Pro solution to recognize individual users without requiring passwords or card swipes.

Combat fraud and boost customer efficiency with the Biometric Fingerprint Reader and the Digital Persona U.are.U 4500 Fingerprint Reader. The device was specifically designed for business-critical applications that require a high-level of durability and a high degree of accuracy from fingerprint readers.

As of FileMaker 19, all plug-ins need to be 64-bit. If using older plug-ins or older versions of FileMaker, the plug-in bit version that you use depends upon the FileMaker Pro bit version you have installed. FileMaker and the plug-in need to be running in the same bit version.

The Digital Persona U.are.U 4500 Reader and Digital Personal U.are.U 5160 Reader devices and were specifically designed for business-critical applications that require a high-level of durability and a high degree of accuracy from fingerprint readers. The compact design, high-quality metal casing and special undercoating ensure reliable performance over the widest population of users. The unsurpassed performance and design deliver unequaled accuracy with dry, moist or rough hard-to-read fingerprints in any shared environment.

Successful integration of FileMaker plug-ins requires the creation of integration scripts within your FileMaker solution. Intermediate to advanced experience with FileMaker Pro, especially in the areas of scripting and calculations is necessary to integrate this plug-in. After review of our overview videos, sample scripts and documentation you find you need assistance please contact us or fill out a Request For Quote.

Microsoft offers plenty of sign-in options and account protection mechanisms to protect your Windows PC, and you don't necessarily have to rely on plain old passwords to secure them. Windows Hello, for instance, allows you to sign in with your face or fingerprint if your device has Windows Hello hardware. But what if your Windows PC doesn't meet the necessary hardware requirements, and you still want to unlock your PC remotely? Well, you're not entirely out of luck, at least not until you have an Android phone with a fingerprint scanner.

That's right, there's an Android app called 'Remote Fingerprint Unlock' which you can install on pretty much any Android phone with a fingerprint scanner, and use it to unlock your Windows PC remotely without any issues. This particular application was created by XDA Member Andrew-X, and it works very well.

Remote Fingerprint Unlock requires two modules: a library for Windows and an Android app, which securely communicate between themselves over the local network. This means you can use the fingerprint sensor on your Android device to authenticate on the app and the Windows module, upon validating, seamlessly unlocks your Windows user account.

Under the hood, the credentials are encrypted using a key that is generated based on your fingerprint. Thanks to Android's security mechanism, the key is safeguarded by the Trusted Execution Environment (TEE) of the SoC that powers the phone. The app itself doesn't store any passwords, and it doesn't even require internet permission to function.

The fingerprint authentication may fail to work on some devices, forcing you to troubleshoot by uninstalling the app and removing the stored fingerprints on your phone via the settings before trying again. It may or may not work even after troubleshooting, so keep that in mind. We were unable to get this app working on a OnePlus 12, but your mileage may vary.

Setting up Remote Fingerprint Unlock is fairly simple. All you need to do is download the Android app, install the Windows Fingerprint Credential Module, and go through the setup process in the app. As mentioned earlier, the utility doesn't require an Internet connection, but a local network is still needed. Hence, you have to make sure that your Windows PC and your Android phone are connected to the same Wi-Fi/access point.

I have managed to scan 3 of my right hand fingers, and it almost never unlocks on first try, regardless of finger used, comparing with my Note10+, the poor performance is identical, so is the feel and way the scanner works, so I am sure they are the same scanner and am sure that the Exynos does DEFINITELY NOT have an ultra-sonic fingerprint scanner.

Maybe the Qualcomm version is great, but this is extremely disappointing and is the reason I returned my Galaxy S20, Galaxy Note 20 Ultra upgrades after a few days, and now it looks like I will be returning this phone. It is not a substantive upgrade on my Note10+ the same annoyances.

I set up the Microsoft Authenticator and 2FA in 1Password. Then I set up a Kensington Verimark fingerprint reader. However, 1Password did not enable me to use the Verimark reader to log onto 1Password. Verimark DOES allow me to use my fingerprint to access my desktop computer. I pulled up the Kensington Verimark Setup Guide that walks you through the process of setting up the Verimark and 1Password to sign into 1Password. However, since it is not working I went into 1Password and disabled the Verimark key, but got this 1Password error message, "the security key you're using is already registered with your account". Should I disable all 2FA in 1Password and try again? I don't know the consequence of disabling 2FA in 1Password.
(I could NOT find version in Settings on desktop, used iPhone version.)

I went ahead and turned off 2FA and deleted all devices and started over with 2FA by loading Microsoft Auth. and then the Verimark. Did this twice. These two times, the only difference was that the process did NOT produce an error message, but instead stated, "Your security key was successfully registered". However, the Verimark still doesn't allow me to log into 1Password using my fingerprint!!
Help, I have run out of things to try!

With help, I finally realized I do NOT need 2FA to make the Verimark fingerprint reader to work.
So I turned 2FA off.
Then with 1Password HELP, I came to realize that to use Windows HELP, I needed to load the DESKTOP APPLICATION, which when setting up 1Password the first time, I had deleted because I though the WINDOWS APP had everything I needed.
I reloaded the DESKTOP APP and now the fingerprint reader works to log onto the DESKTOP APP, but NOT the WINDOWS10 APP.

The Window Desktop app runs in MS Windows (not in a browser) and CAN BE accessed through Hello. The Windows Desktop app is optional, not required to use 1Password on the web.
The Web interface started from CANNOT be accessed through Hello.
However, the browser EXTENSION CAN BE accessed through Hello.
And... if I log into the Windows Desktop App, I am also logged onto the browser extension and conversely if I log into the browser extension, I am also logged onto the Windows Desktop App, but neither of these log me into the Web Interface.

Our getting started guide covers the apps in a little more detail but I understand where you are coming from in that it might be useful to describe the difference between the separate places you can use 1Password.

f13a-6c3a I tried to connect phone and recalibrate after assessing the fingerprint scanner removal. In the end I can't recalibrate as the version of 'android' is not supported apparently. Anyone else have this issue or can share how they have managed to recalibrate recently?

James calibration is done in fastboot mode and you need appropriate drivers for your computer OS, Android version is irrelevant. Instead of attempting to have Google calibration tool reboot your phone into fastboot, do it yourself - boot in fastboot, then connect to the PC (make sure phone is recognized by the PC), then run calibration (you might need to try multiple times for it to succeed)