Comment 2 for bug 1882878

Hi Sebastian,

I am just referring s per windows implementation here. So the user may try to enroll the same finger several times and since the templates are stored in device(Not the host) it may run out of memory. Hence this duplicate check is necessary for those devices which stores the templates in device memory itself.

The other thing is you need to provide an API in the libfprint to do the duplicate check when enrolling a new finger. So this command goes to the device all through and device itself sees whether the finger is already enrolled or not. Depending on this output further enrollment process can be continued or a warning message can be displayed(As in windows).

You can refer the windows WBF API's for the same.