Add support for Kensington VeriMark (06cb:0088)

[Prism019]

This device also seems to fit in with this project, as the wireshark dissector recognizes the traffic. I ran it through prototype, and the output is attached to this post.

Thanks a lot!
Prism
out.txt

also current commit is 9fb1b5b

[OwenPemberton]

Would also be interested in getting this working.
I'm getting "Expert Info (Error/Malformed): Vector length 2 is too large, truncating it to 0"
on the 'elliptic curve points format length' part of the TLS 'client hello' packet.

[IncPlusPlus]

I've been looking everywhere for a way to use my VeriMark reader to work in Ubuntu. I don't know how to contribute to this process, though. If I can provide any useful info to move this issue along, please let me know and I'd be happy to help.

[elmcrest]

Hey everyone,

any updates on this?

[jontis]

#94

[visorcraft]

For anyone still watching this issue: there's now a working FLOSS libfprint driver for the Kensington VeriMark (06cb:0088) at https://github.com/visorcraft/Kensington_VeriMark_06cb-0088.

It covers enroll, verify, and PAM/login integration end-to-end on Linux. The driver auto-pairs with the device on first plug-in (no Windows extraction needed) and persists pairing material to the standard libfprint state directory. README has the full clone → build → enroll → PAM walkthrough.

Protocol-wise, 06cb:0088 turned out to be a pre-Prometheus chip — it doesn't have the fwext partition that 06cb:009a loads, and the pre-TLS pairing differs from what's documented in spec.md. So it's effectively a separate device family that didn't fit cleanly into the existing 009a-focused work here.

A docs-only PR to add it to this project's README + status table is at #117.

[Nerixyz]

at visorcraft/Kensington_VeriMark_06cb-0088.

This repo doesn't exist or it's private.

[visorcraft]

@Nerixyz was doing one final documentation cleanup; I have now made it public.