-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible problem with prototype and 138a:00ab #50
Comments
Same on HP Elite x2 1013 G3. |
Yours isn't in the 90 series as this repo is tailored for. You can probaby check the other issues for the setup to submit USB data captures from a Windows VM. |
We can submit it here, by attaching to this bugreport, or there is some other place for such stuff? |
You can submit it here, and test prototype manually adding your devise pid:vid to filter |
Done, log. |
I wasn't able to capture device traffic because I can't get fingerprint reader works in VM. In VirtualBox driver doesn't work with Code 10, and in QEMU (Gnome Boxes) driver doesn't work with Code 31. Is there known ways to workaround this? |
I am not aware of such issues in VM. It would be good if you will research this further. |
Turns out that I have to reset fingerprint sensor in BIOS to make it work in VM. Not sure why, maybe because I initialize it in preinstalled Windows, maybe because I tried to run prototype - I have no idea. As for SGX - I disabled it, and seems like nothing changed. I was able to successfully record it: https://yadi.sk/d/KDJhcSks3mVUFw In first record device initialization, attempt to register two fingers (via SynapticsFingerprintManager.exe) then attempts to register two more, use it for authorization, but that attempts mostly fail. So I made second record, where I just register finger, and get successful authorization with it. Unfortunately, in both cases device fall off the bus and change address for some reason. in both cases it happened at registration of first finger, so I had to repeat it. Also I had to use Wireshark filter with two address as device change it's address after reconnect, like this: |
Yes, they love to disconnect for some reason. I will check your logs and post results here |
@nmikhailov please let me jknow, if additional recordings is necessary or published record is fine? |
@nmikhailov any news? |
Any news? xD |
Sorry, can you retest prototype and paste logs again? |
@nmikhailov could you please clarify, what changes has been made to prototype, that could be relevant to 138a:00ab? Here is see only single change for 9a variant: https://github.com/nmikhailov/Validity90/commits/master/prototype |
No changes so far, it is that your pastebin link expired. |
@nmikhailov would you still be interested in checking this out if I provide logs? |
@nmikhailov I don't see this type list in the README. Is this device within the scope of this repo? |
I have the very same sensor, can do some testing in case of need. |
Is |
HP ProBook 440 G6, same USB device ID |
138a:00ab Validity Sensors, Inc. is also used in HP ZBook Studio x360 G5 |
Same problem in HP ZBook G5 15u: 138a:00ab Validity Sensors, Inc |
Bus 001 Device 005: ID 138a:00ab Validity Sensors, Inc. some news on this? |
Also interested :( |
Same problem for Zbook 14u G5. The same model is used on this notebook. :( |
I'm interested too, I can help testing if needed! |
Doing something similar to this, ( Folded codeblock
|
bump +1 |
bump +1 |
4 similar comments
bump +1 |
bump +1 |
bump +1 |
bump +1 |
lsusb scans:
./prototype results:
It's a fingerprint scanner in an hp zbook 15v g5.
The text was updated successfully, but these errors were encountered: