[fprint] why enum fp_finger?
Joshua N Pritikin
jpritikin at pobox.com
Thu Sep 24 16:21:51 BST 2009
On Thu, Sep 24, 2009 at 02:43:46PM +0100, Simon Kenyon wrote:
> Joshua N Pritikin wrote:
> > I must be missing something really basic. Why is enum fp_finger part of
> > the API? Do people actually enroll all their fingers? If they do, why?
> >
> > It seems to me that I want to be identified by a single finger for most
> > applications. Perhaps for high security, it would be worth testing more
> > than one finger?
>
> bacause single finger is usually not good enough
>
> Representative Finger 1:1 FAR Rates for FRR = 0.01% to 0.001%
>
> The above table shows that with single finger, you will be 1 false
> accepts in 100
> If you are happy with that, then go for it.
Regardless of FAR rates, I am skeptical that enum fp_finger belongs in
the API. The header might include enum fp_finger, but why should any
functions use it?
On the other hand, I am not going to submit a patch to remove it.
I guess it's not a big deal.
More information about the fprint
mailing list