You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The approach that this project took to integrate an unsupported fingerprint reader with libfprint is unusual, but afaik doesn't require designing custom algorithms for fingerprint matching. It's basically a modified libfprint that returns a fake fingerprint image on enrollment and returns whether a match was successful based on what the hardware itself says. This of course requires finger enrollment to be done in Windows. On the other hand, I personally wouldn't mind that.
So I was wondering if a similar approach could be taken in our case?
The text was updated successfully, but these errors were encountered:
Or honestly maybe I just misunderstood the whole thing. I haven't done any actual research into this by myself yet, as I'm not yet an owner of an XPS 15. So take my words with a grain of salt.
On the other hand, I'll gladly be of service once I get my hands on an XPS 15.
Hey,
I’m not sure how te sensor works. You might have some luck asking synaptics
or validity. They might surprise you with an answer.
I’m mostly sure fingerprint detection with this sensor is done in windows
just because it returns an image. That said, I never fully went on to go
through the enrolment process logs.
Best of luck when you get yours reverse engineering it. Maybe you will find
the enrolment command.
I wrote a good skeleton for it in python. You should be able to hack things
together quickly for a proof of concept if you find the command.
Mark
On Sun, May 27, 2018 at 1:51 AM Jan Neumann ***@***.***> wrote:
Or honestly maybe I just misunderstood the whole thing. I haven't done any
actual research into this by myself yet, as I'm not yet an owner of an XPS
15. So take my words with a grain of salt.
On the other hand, I'll gladly be of service once I get my hands on an XPS
15.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFfmDtgJxi_x8RWYqGO3SAEoQe9SNDXks5t2mkKgaJpZM4UPMyJ>
.
I just stumbled across this project: https://github.com/hrenod/libfprint
The approach that this project took to integrate an unsupported fingerprint reader with libfprint is unusual, but afaik doesn't require designing custom algorithms for fingerprint matching. It's basically a modified libfprint that returns a fake fingerprint image on enrollment and returns whether a match was successful based on what the hardware itself says. This of course requires finger enrollment to be done in Windows. On the other hand, I personally wouldn't mind that.
So I was wondering if a similar approach could be taken in our case?
The text was updated successfully, but these errors were encountered: