Sorry - I now added debug to the right line:
auth sufficient pam_thinkfinger.so debug
auth required pam_unix.so nullok_secure try_first_pass
But i still get no output in /var/log/messages.
Are you sure thinkfinger is used by pam?
Here is my /etc/pam.d/login from Ubuntu 7.10:
#
# The PAM configuration file for the Shadow `login' service
#
# Outputs an issue file prior to each login prompt (Replaces the
# ISSUE_FILE option from login.defs). Uncomment for use
# auth required pam_issue.so issue=/etc/issue
# Disallows root logins except on tty's listed in /etc/securetty
# (Replaces the `CONSOLE' setting from login.defs)
auth requisite pam_securetty.so
# Disallows other than root logins when /etc/nologin exists
# (Replaces the `NOLOGINS_FILE' option from login.defs)
auth requisite pam_nologin.so
# This module parses environment configuration file(s)
# and also allows you to use an extended config
# file /etc/security/pam_env.conf.
#
# parsing /etc/environment needs "readenv=1"
session required pam_env.so readenv=1
# locale variables are also kept into /etc/default/locale in etch
# reading this file *in addition to /etc/environment* does not hurt
session required pam_env.so readenv=1 envfile=/etc/default/locale
# Standard Un*x authentication.
@include common-auth
# This allows certain extra groups to be granted to a user
# based on things like time of day, tty, service, and user.
# Please edit /etc/security/group.conf to fit your needs
# (Replaces the `CONSOLE_GROUPS' option in login.defs)
auth optional pam_group.so
# Uncomment and edit /etc/security/time.conf if you need to set
# time restrainst on logins.
# (Replaces the `PORTTIME_CHECKS_ENAB' option from login.defs
# as well as /etc/porttime)
# account requisite pam_time.so
# Uncomment and edit /etc/security/access.conf if you need to
# set access limits.
# (Replaces /etc/login.access file)
# account required pam_access.so
# Sets up user limits according to /etc/security/limits.conf
# (Replaces the use of /etc/limits in old login)
session required pam_limits.so
# Prints the last login info upon succesful login
# (Replaces the `LASTLOG_ENAB' option from login.defs)
session optional pam_lastlog.so
# Prints the motd upon succesful login
# (Replaces the `MOTD_FILE' option in login.defs)
session optional pam_motd.so
# Prints the status of the user's mailbox upon succesful login
# (Replaces the `MAIL_CHECK_ENAB' option from login.defs).
#
# This also defines the MAIL environment variable
# However, userdel also needs MAIL_DIR and MAIL_FILE variables
# in /etc/login.defs to make sure that removing a user
# also removes the user's mail spool file.
# See comments in /etc/login.defs
session optional pam_mail.so standard
# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context.
# Uncomment the following line to enable SELinux
# session required pam_selinux.so multiple
# Standard Un*x account and session
@include common-account
@include common-session
@include common-password
Post by Daniel Muryginauth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass debug
But there are still no pam related messages in /var/log/messages...
Post by Justin DuggerPost by Daniel MuryginHello,
i installed and run thinkfinger-0.3 on my ThinkPad T60 with Ubuntu
7.04 without problems. I upgraded to Ubuntu 7.10 (Gutsy Gibbon) and
https://wiki.ubuntu.com/ThinkFinger
All tf-tool commands are working fine but pam authentication is not
working anymore. I could not find any error messages.
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass
/lib/security/pam_thinkfinger.so is installed.
Do you have any idea how to debug?
Thanks and greetings - Daniel.
The place to check is /var/log/messages. Odds are that uinput is not
acting nicely. To get a good debug log from this, add the parameter
debug to pam_thinkfinger.so just like you have try_first_pass in
pam_unix. Once you've done that, bring up a console, and run tail -f
/var/log/messages. Then on another console, run a sudo command like
"sudo yes" or "sudo ls". That should give a first hint at what's gone
wrong.
--
Daniel Murygin
Email: daniel.murygin [at-nospam] googlemail [dot] com
--
Daniel Murygin
Lehmbruckstr. 15
10245 Berlin
Tel.: +49 30 25 29 46 37
Mobil: +49 179 22 62 181
Email: ***@googlemail.com