On Mon, 2009-01-12 at 16:04 +0000, Konstantin V. Gavrilenko wrote: > Bastien, > > the patch has applied fine, and fprintd seems to be working ok. > > g_...@dynomob ~ $ su - > ** Message: debug on > Swipe your right index finger on UPEK TouchStrip > dynomob ~ # id > uid=0(root) gid=0(root) > dynomob ~ #
Cool, I'll get Daniel to apply it to master. > However, when I try to run it through the gdb, i don't get the "swipe the > finger" prompt, > it goes directly to the password prompt. > > g_...@dynomob ~ $ gdb /bin/su > GNU gdb 6.7.1 > Copyright (C) 2007 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-pc-linux-gnu"... > Using host libthread_db library "/lib/libthread_db.so.1". > (gdb) set args - > (gdb) run > Starting program: /bin/su - > ** Message: debug on > Password: > su: Permission denied > > Program exited with code 01. > (gdb) bt full > No stack. > (gdb) Nothing to do with pam_fprintd I believe, su just doesn't like being run under gdb (it's an suid program). Feel free to test without pam_fprintd in the configuration. > Another issue, I though that fprintd was suppose to allow simultaneous > non interlocking access to the fingerprint device by several > processes. > However, if i run one instance of su - and another one in the second > terminal, the second goes straight into Password prompt. > > Was I wrong in assuming that it can be used by several processes > simultaneously? Yes and no. Both programs were waiting on a read on the fingerprint reader. They are "interlocking", only one process can access the device at a time... Cheers _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
