mirror of
https://gitlab.com/mishakmak/pam-fprint-grosshack.git
synced 2026-04-09 04:13:33 +02:00
04fd09cfa8
On Mon, 2009-01-12 at 12:18 +0000, Konstantin V. Gavrilenko wrote: > Hi Bastien, > > by default the fprintd installs the pam_fprintd into the /usr/lib64/security, whil egentoo searches them in /lib/security. > So I simply simlinked it to the correct location /usr/lib64/security/pam_fprintd.so to /lib/security/pam_fprintd.so > I've removed the symlink, and copied the file, but it does not change anything, the same error appears. > > As you asked, recompiled some of the packages with "-O1 -gddb" and "nostrip" options. > #4 0x00007fa3344a3899 in dbus_connection_unref (connection=0x624e20) at dbus-connection.c:2686 > __FUNCTION__ = "dbus_connection_unref" > #5 0x00007fa334915284 in pam_sm_authenticate (pamh=0x6105c0, flags=<value optimized out>, argc=<value optimized out>, argv=<value optimized out>) at pam_fprintd.c:375 > rhost = 0x0 > username = 0x610740 "root" > i = <value optimized out> > r = 0 Could you please test the attached patch? Cheers
PAM module for fingerprint authentication ----------------------------------------- Using: * Modify the appropriate PAM configuration file (/etc/pam.d/system-auth-ac on Fedora systems), and add the line: auth sufficient pam_fprintd.so before the line: auth sufficient pam_unix.so ... * You can now enroll fingerprints using fprintd-enroll. The first available fingerprint available will be used to log you in. Options: * You can add the "debug" option on the pam configuration file line above, this will log more information from PAM to the file specified in your syslog configuration (/var/log/secure by default on Fedora) Known issues: * pam_fprintd does not support identifying the user itself as that would mean having the fingerprint reader on for all the time the user selection is displayed, and could damage the hardware. It could be fixed by having gdm/login only start the PAM conversation when there is activity * pam_fprintd doesn't support entering either the password or a fingerprint, as pam_thinkfinger does, because it's a gross hack, and could be fixed by having the login managers run 2 separate PAM stacks