Public bug reported:
Since karmic libkrb5 is acting weird. When a user fail to give a valid
password, it loops until account is locked ... After some wireshark
capture and some comparaison between 1.6 (from Jaunty) et the 1.7 of
Karmic i succeded to make a patch which solve the problem...
In 1.7 while the client get KDC_ERR_PREAUTH_FAILED or
KDC_ERR_PREAUTH_REQUIRED from the server it loops until it gets another
message (in our case it's KDC_ACCOUNT_LOCKED or something...)
In 1.6 it loops only if it receive KDC_ERR_PREAUTH_REQUIRED which is
quite normal...
I'm tired ;) it's 1am here if you need more info just ask here. patch +
pcaps in attachement
Btw, there is no problem without our configuration since it's the same
we were used to use in jaunty and it was generated by pam-auth-config
tool :)
** Affects: krb5 (Ubuntu)
Importance: Undecided
Status: New
--
Strange behavior of libkrb5 since karmic ...
https://bugs.launchpad.net/bugs/489418
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
