[fprint] Support for my fingerprint reader 138a:003d Validity Sensors, where to start?
Charles Lane
lane at duphy4.physics.drexel.edu
Tue Oct 27 18:11:42 PDT 2015
Rather than decoding the USB conversation, if it's a device
that is understood by the Validity-Sensor-Setup (vcsFPServiceDaemon)
..I think originally for HP computers, then the only thing that
is needed is an interface between libfprint and the vcsFP daemon.
It's what I got working for the VFS495, for example. Unfortunately
the Validity-Sensor-Setup binary package doesn't seem to have
source code available anywhere.
On Tue, 27 Oct 2015 17:48:59 -0700
Vasily Khoruzhick <anarsoul at gmail.com> wrote:
> On Mon, Oct 26, 2015 at 4:05 AM, <gregory.bahde at laposte.net> wrote:
> > Hello,
>
> Hi Gregory,
>
> > though I found some websites saying that you could build drivers
> > for my fingerprint reader I never had it working.
> >
> > Is it's support supposed to get integrated?
> >
> > I remember having learned that to make its driver it was needed
> > that I dumped some infos from the USB pot under windows but I don't
> > remember where I read that.
> >
> > Well anyway, I wanna help build the open source driver for this - I
> > hate typing passwords over and over-.
> >
> > Please, tell me how I can help?
>
> It's not that easy. You need to capture usb protocol with whatever
> tool you prefer (I usually use wireshark on Linux host while running
> Windows in VM) and reverse engineer it, i.e.
> understand what exactly Windows driver does when sending some USB
> transfer and how exactly device responds. Usually, it involves several
> try-and-fail iterations. I prefer to develop
> small prototype (see https://github.com/anarsoul/fprint_aes1660 as an
> example) for playing with device before starting libfprint driver
> development.
>
> Regards,
> Vasily
>
> > Below is its lsusb -v description
>
> > Regards
> >
> > gregory bahde
> > "
> > Bus 003 Device 003: ID .
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 1.10
> > bDeviceClass 255 Vendor Specific Class
> > bDeviceSubClass 17
> > bDeviceProtocol 255
> > bMaxPacketSize0 8
> > idVendor 0x138a Validity Sensors, Inc.
> > idProduct 0x003d
> > bcdDevice 1.04
> > iManufacturer 0
> > iProduct 0
> > iSerial 1 00b07aab3692
> > bNumConfigurations 1
> > Configuration Descriptor:
> > bLength 9
> > bDescriptorType 2
> > wTotalLength 46
> > bNumInterfaces 1
> > bConfigurationValue 1
> > iConfiguration 0
> > bmAttributes 0xa0
> > (Bus Powered)
> > Remote Wakeup
> > MaxPower 100mA
> > Interface Descriptor:
> > bLength 9
> > bDescriptorType 4
> > bInterfaceNumber 0
> > bAlternateSetting 0
> > bNumEndpoints 4
> > bInterfaceClass 255 Vendor Specific Class
> > bInterfaceSubClass 0
> > bInterfaceProtocol 0
> > iInterface 0
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x01 EP 1 OUT
> > bmAttributes 2
> > Transfer Type Bulk
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0040 1x 64 bytes
> > bInterval 0
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x81 EP 1 IN
> > bmAttributes 2
> > Transfer Type Bulk
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0040 1x 64 bytes
> > bInterval 0
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x82 EP 2 IN
> > bmAttributes 2
> > Transfer Type Bulk
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0040 1x 64 bytes
> > bInterval 0
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x83 EP 3 IN
> > bmAttributes 3
> > Transfer Type Interrupt
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0008 1x 8 bytes
> > bInterval 4
> > Device Status: 0x0000
> > (Bus Powered)
> > "
> >
> > ________________________________
> > De: "Vasily Khoruzhick" <anarsoul at gmail.com>
> > À: "Marcos Alano" <marcoshalano at gmail.com>
> > Cc: fprint at lists.freedesktop.org
> > Envoyé: Samedi 24 Octobre 2015 07:04:35
> > Objet: <DKIM> Re: [fprint] Minutiae question
> >
> > Hi Marcos,
> >
> > On Fri, Oct 23, 2015 at 8:26 PM, Marcos Alano
> > <marcoshalano at gmail.com> wrote:
> >> Hello folks,
> >>
> >> How many minutiae is considered a match during verification? I
> >> can't find this information on fprint documentation.
> >
> > We're using bozorth3 algo, which provides a matching score, not a
> > count of matching minutiae.
> > Bozorth3 threshold depends on driver, for most drivers it's 40
> > (default value), for some drivers it's lowered.
> >
> > Regards,
> > Vasily
> >
> >> Cheers.
> >> --
> >> Marcos Alano
> >> ----------------------------------------------
> >> P: Por que este email é tão curto?
> >> R: http://five.sentenc.es
> >> ----------------------------------------------
> >> _______________________________________________
> >> fprint mailing list
> >> fprint at lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/fprint
> > _______________________________________________
> > fprint mailing list
> > fprint at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/fprint
> >
> _______________________________________________
> fprint mailing list
> fprint at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/fprint
--
Drexel University \V --Chuck Lane
======]---------->-----*------<--------[===========
(215) 895-1545 / \_/*~~~~~ Particle Physics
FAX: (215) 895-1281 lane at duphy4.physics.drexel.edu
More information about the fprint
mailing list