[fprint] uru4000, number of enroll stages

Vasily Khoruzhick anarsoul at gmail.com
Tue Jun 24 23:49:41 PDT 2014


On 25 June 2014 09:33:37 Timo Teras wrote:
> On Wed, 25 Jun 2014 09:15:29 +0300
> 
> Vasily Khoruzhick <anarsoul at gmail.com> wrote:
> > > It did. Thanks. Forget the earlier patch, it's irrelevant and the
> > > original code is right. Seems the bug is in the generic code and
> > > affects all drivers that are capable of 'finger present' detection.
> > > 
> > > It seems to be a bug since 2008 but mostly unnoticed due to doing
> > > only that one enrollment.
> > 
> > Well, I'm testing libfprint on several Authentec scanners and on
> > single UPEK, and it didn't affect any of my devices.
> 
> It depends a lot on the driver internals if the bug affects it or not.
> But fundamentally there was a confusion in enum type. The mismatch
> basically caused driver to go to 'capture' mode immediately instead of
> 'await finger on' as intended. If the device does mandatory asynchronous
> hardware finger recognition like uru does, there are high changes that
> the bug affects it.

Ok, I'll take a deeper look tonight.

Regards
Vasily
 
> -Timo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/fprint/attachments/20140625/615c4101/attachment.sig>


More information about the fprint mailing list