[Bug 1335106] Re: Could not parse server response

2014-06-27 Thread Klas Lindfors
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 might be helpful
if you could turn on the debug flag in the configuration and post the
output.

/klas

-- 
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 parse server response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yubico-pam/+bug/1335106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1335106] Re: Could not parse server response

2014-06-27 Thread Claus Holm Christensen
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:parse_cfg(764)] argv[3]=authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(764)] argv[4]=mode=client
[../pam_yubico.c:parse_cfg(765)] id=17260
[../pam_yubico.c:parse_cfg(766)] key=qTVnv3Nd/kjpxZM7TYZJdWyyCuk=
[../pam_yubico.c:parse_cfg(767)] debug=1
[../pam_yubico.c:parse_cfg(768)] alwaysok=0
[../pam_yubico.c:parse_cfg(769)] verbose_otp=0
[../pam_yubico.c:parse_cfg(770)] try_first_pass=0
[../pam_yubico.c:parse_cfg(771)] use_first_pass=0
[../pam_yubico.c:parse_cfg(772)] authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(773)] ldapserver=(null)
[../pam_yubico.c:parse_cfg(774)] ldap_uri=(null)
[../pam_yubico.c:parse_cfg(775)] ldapdn=(null)
[../pam_yubico.c:parse_cfg(776)] user_attr=(null)
[../pam_yubico.c:parse_cfg(777)] yubi_attr=(null)
[../pam_yubico.c:parse_cfg(778)] yubi_attr_prefix=(null)
[../pam_yubico.c:parse_cfg(779)] url=(null)
[../pam_yubico.c:parse_cfg(780)] capath=(null)
[../pam_yubico.c:parse_cfg(781)] token_id_length=12
[../pam_yubico.c:parse_cfg(782)] mode=client
[../pam_yubico.c:parse_cfg(783)] chalresp_path=(null)
[../pam_yubico.c:pam_sm_authenticate(823)] get user returned: chch
[../pam_yubico.c:pam_sm_authenticate(929)] conv returned 12 bytes
[../pam_yubico.c:pam_sm_authenticate(937)] OTP too short to be considered : 12 
 44
[../pam_yubico.c:pam_sm_authenticate(1038)] done. [Authentication failure]
[../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:parse_cfg(764)] argv[3]=authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(764)] argv[4]=mode=client
[../pam_yubico.c:parse_cfg(765)] id=17260
[../pam_yubico.c:parse_cfg(766)] key=qTVnv3Nd/kjpxZM7TYZJdWyyCuk=
[../pam_yubico.c:parse_cfg(767)] debug=1
[../pam_yubico.c:parse_cfg(768)] alwaysok=0
[../pam_yubico.c:parse_cfg(769)] verbose_otp=0
[../pam_yubico.c:parse_cfg(770)] try_first_pass=0
[../pam_yubico.c:parse_cfg(771)] use_first_pass=0
[../pam_yubico.c:parse_cfg(772)] authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(773)] ldapserver=(null)
[../pam_yubico.c:parse_cfg(774)] ldap_uri=(null)
[../pam_yubico.c:parse_cfg(775)] ldapdn=(null)
[../pam_yubico.c:parse_cfg(776)] user_attr=(null)
[../pam_yubico.c:parse_cfg(777)] yubi_attr=(null)
[../pam_yubico.c:parse_cfg(778)] yubi_attr_prefix=(null)
[../pam_yubico.c:parse_cfg(779)] url=(null)
[../pam_yubico.c:parse_cfg(780)] capath=(null)
[../pam_yubico.c:parse_cfg(781)] token_id_length=12
[../pam_yubico.c:parse_cfg(782)] mode=client
[../pam_yubico.c:parse_cfg(783)] chalresp_path=(null)
[../pam_yubico.c:pam_sm_authenticate(823)] get user returned: chch
[../pam_yubico.c:pam_sm_authenticate(929)] conv returned 44 bytes
[../pam_yubico.c:pam_sm_authenticate(947)] Skipping first 0 bytes. Length is 
44, token_id set to 12 and token OTP always 32.
[../pam_yubico.c:pam_sm_authenticate(954)] OTP: 
ccdiljghbbcktfvbnjivrtdicbhkbtjtukrgefkr ID: ccdiljgh
[../pam_yubico.c:pam_sm_authenticate(985)] ykclient return value (101): Could 
not parse server response
[../pam_yubico.c:pam_sm_authenticate(1038)] done. [Authentication service 
cannot retrieve authentication info]
[../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:parse_cfg(764)] argv[3]=authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(764)] argv[4]=mode=client
[../pam_yubico.c:parse_cfg(765)] id=17260
[../pam_yubico.c:parse_cfg(766)] key=qTVnv3Nd/kjpxZM7TYZJdWyyCuk=
[../pam_yubico.c:parse_cfg(767)] debug=1
[../pam_yubico.c:parse_cfg(768)] alwaysok=0
[../pam_yubico.c:parse_cfg(769)] verbose_otp=0
[../pam_yubico.c:parse_cfg(770)] try_first_pass=0
[../pam_yubico.c:parse_cfg(771)] use_first_pass=0
[../pam_yubico.c:parse_cfg(772)] authfile=/etc/libpam-yubico.conf
[../pam_yubico.c:parse_cfg(773)] ldapserver=(null)
[../pam_yubico.c:parse_cfg(774)] ldap_uri=(null)
[../pam_yubico.c:parse_cfg(775)] ldapdn=(null)
[../pam_yubico.c:parse_cfg(776)] user_attr=(null)
[../pam_yubico.c:parse_cfg(777)] yubi_attr=(null)
[../pam_yubico.c:parse_cfg(778)] yubi_attr_prefix=(null)
[../pam_yubico.c:parse_cfg(779)] url=(null)
[../pam_yubico.c:parse_cfg(780)] capath=(null)
[../pam_yubico.c:parse_cfg(781)] token_id_length=12
[../pam_yubico.c:parse_cfg(782)] mode=client
[../pam_yubico.c:parse_cfg(783)] chalresp_path=(null)
[../pam_yubico.c:pam_sm_authenticate(823)] get user returned: chch

[Bug 1335106] Re: Could not parse server response

2014-06-27 Thread Claus Holm Christensen
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 parse server response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yubico-pam/+bug/1335106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1335106] Re: Could not parse server response

2014-06-27 Thread Claus Holm Christensen
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 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 parse server response

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yubico-pam/+bug/1335106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs