Fix: Add support for 06cb:0088 (closes #34 and #74)#258
Open
visorcraft wants to merge 1 commit into
Open
Conversation
…river 06cb:0088 is a pre-Prometheus Synaptics/Validity chip and uses a different protocol from the post-Prometheus 06cb:009a that this codebase targets: no fwext partition, different pre-TLS pairing, different cert flow. Rather than failing with a confusing 'no matching devices found' error when a VeriMark is plugged in, detect the device and print a clear redirect to the dedicated FLOSS libfprint driver at https://github.com/visorcraft/Kensington_VeriMark_06cb-0088 which covers enroll, verify, and PAM/login integration for this device. Closes uunicorn#34. Closes uunicorn#74.
This was referenced May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
06cb:0088(Kensington VeriMark) USB devices and prints a clear redirect rather than failing with a confusing "no matching devices found" error.libfprintdriver for this device.Context
06cb:0088is a pre-Prometheus Synaptics/Validity chip. It uses a meaningfully different protocol from the post-Prometheus06cb:009athis codebase targets:0x4f).So it doesn't fit cleanly under the existing
validitysensor/code paths. A clean-roomlibfprintdriver for it exists at:https://github.com/visorcraft/Kensington_VeriMark_06cb-0088
It covers enroll, verify, and PAM/login integration end-to-end. The driver auto-pairs with the device on first plug-in and persists pairing material to the standard libfprint state directory.
This PR is the smallest useful change: surface the redirect in both the README and in the
usb.pyopen path, so a VeriMark user tryingpython-validitygets pointed at the right driver instead of an opaque failure.Test plan
python3 -m py_compile validitysensor/usb.pypasses06cb:0088is present — does not affect existing flows for0090/0097/009a/009dusersCloses #34.
Closes #74.