Re: [OATH-Toolkit-help] One Time Password in SLiM

[Christian Hesse]

Christian Hesse <address@hidden> on Fri, 29 Apr 2011 22:24:19 +0200:
> xscreensaver to go...

This is gonna be kind of monologue... :D

Ok, here are the new facts: Authentication succeeds if I add 'alwaysok' to
pam_oath. So the communication between xscreensaver and pam_oath is ok. Does
the pam module have a problem accessing the usersfile? xscreensaver is run
as user (uid 1000 or something...).

This is the debug output:
[pam_oath.c:parse_cfg(118)] called.
[pam_oath.c:parse_cfg(119)] flags 0 argc 3
[pam_oath.c:parse_cfg(121)] argv[0]=usersfile=/etc/users.oath
[pam_oath.c:parse_cfg(121)] argv[1]=debug
[pam_oath.c:parse_cfg(121)] argv[2]=alwaysok
[pam_oath.c:parse_cfg(122)] debug=1
[pam_oath.c:parse_cfg(123)] alwaysok=1
[pam_oath.c:parse_cfg(124)] try_first_pass=0
[pam_oath.c:parse_cfg(125)] use_first_pass=0
[pam_oath.c:parse_cfg(126)] usersfile=/etc/users.oath
[pam_oath.c:parse_cfg(127)] digits=0
[pam_oath.c:parse_cfg(128)] window=5
[pam_oath.c:pam_sm_authenticate(157)] get user returned: eworm
[pam_oath.c:pam_sm_authenticate(232)] conv returned: 123456
[pam_oath.c:pam_sm_authenticate(292)] OTP: 123456
[pam_oath.c:pam_sm_authenticate(303)] authenticate rc -11 last otp Thu Jan  1
01:00:00 1970
[pam_oath.c:pam_sm_authenticate(309)] One-time password not authorized to
login as user 'eworm'
[pam_oath.c:pam_sm_authenticate(322)] alwaysok needed (otherwise return with
7)
[pam_oath.c:pam_sm_authenticate(325)] done. [Success]
-- 
Schoene Gruesse
Chris