pingou wrote:
> *First about the compilation, the path is hardcoded for /lib/security, 
> however on x86_64 arch the right folder is /lib64/security on Fedora, I 
> would say that something like if the folder lib64 exist use it else use 
> /lib/ would do it...

Please file a bug for this at http://www.reactivated.net/fprint/bugs/

> *The second point is about the gdm integration, it is workly nicely 
> however a small window indicated which finger has been recognized pop 
> up, and I have to press enter to get rid of it, is there a way to 
> configure it ?

This is a question for the GDM mailing list :)
pam_fprint just uses the standard messaging context found in libpam_misc.

> *The third point is about kde, when we tried with kscreensaver we have 
> not been able to make it work. Have you ever face that problem ?

I'm not a KDE user, maybe someone else here can help you out.
I would not be surprised if pam_fprint does not work in all scenarios. 
It is only a proof of concept. A real solution requires more effort.

> *My fourth point is about the use of a second user, I have several users 
> on my conputer and I would like to use fprint for switching from one to 
> the other, however when I tried I ended with an error message saying:
> "Could not locate any suitable fingerprints matched with available 
> hardware."
> Have you met that problem before ?

This is probably because UserA cannot access the homedir of UserB -- 
which is obviously by-design. Home directory access is required in order 
to read the enroll data. It works for login just fine because the login 
manager runs as root.

This is a flaw in pam_fprint and is documented on the pam_fprint 
homepage. It likely will not be fixed any time soon, and I would not 
advise using pam_fprint as anything more than a toy :)

As for the compile warnings, they are in the NBIS code which could do 
with a lot of cleanup. Patches accepted. It's not high priority at the 
moment.

Thanks for the feedback,
Daniel
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint

Reply via email to