This is in response to a bug where after an upgrade libpam-krb5 failed to 
authenticate giving an unsupported encryption type.

Around march of 2011, MIT changed how they pick the principal to use
for krb5_verify_init_creds, a function used internally by libpam-krb5.

If that's the case, then this issue should be fixed by the upcoming
1.10.1+dfsg-1 release. I've include a May 2012 patch to try all keys
in the keytab.  I'd appreciate it if you try that release when it
comes out (hopefully later this week) and let me know if that fixes
the issue.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to