Last night I found out the hard way that if a user creates a .k5login
file that isn't correct, (has Windows linebreaks or has multiple
pricipal names on the same line) that they cannot login at all to
systems using pam-krb5 for authentication. (This is on Ubuntu 6.06 on
x86.) Further, no
Christopher D. Clausen wrote:
Similarly, I've been completely locked out of systems if there are
syntax errors in the krb5.conf file and I've seen Windows BSOD if the
system krb5.ini isn't correct. Is there no way to have a fail-safe
method of operation?
If you ever have Windows BSOD with
