Probably fixed, I'll debug on my own a little more.
** Changed in: yubico-pam (Ubuntu)
Status: New => Invalid
** Changed in: yubico-pam (Ubuntu)
Assignee: (unassigned) => Claus Holm Christensen (clausholm-christensen)
** Information type changed from Public to Private
--
You receiv
DOH, too quick on the cut'n'paste here, that log file contains some
confidential information. How to I edit the response?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335106
Title:
Could not pars
The full log-file:
[../pam_yubico.c:parse_cfg(761)] called.
[../pam_yubico.c:parse_cfg(762)] flags 1 argc 5
[../pam_yubico.c:parse_cfg(764)] argv[0]=id=17260
[../pam_yubico.c:parse_cfg(764)] argv[1]=key=qTVnv3Nd/kjpxZM7TYZJdWyyCuk=
[../pam_yubico.c:parse_cfg(764)] argv[2]=debug
[../pam_yubico.c:pa
Hello,
I don't think that bug has any bearing on the issue at hand here. That
bug was marked as resolved in 2011 and released with version 2.5 of
yubico-c-client. According to Dependencies.txt you're running version
2.12 of that software.
How is the PAM module configured when this happens? It mig
