Subject: Defining MKKERBEROS=no breaks logins on current
To: None <>
From: Ralf Huvendiek <>
List: current-users
Date: 10/02/2005 21:05:15

I've set MKKERBEROS=no and MKKERBEROS5=no in my mk.conf. After an update
I noticed that I was unable to login. The culprit is It
did not get installed, but it is required by some pam conf's.
I had to delete this line in all of them:
auth           optional   no_warn try_first_pass

After this I was able to login again.

On a side note: I noticed that pam relies on Which is built
and installed. requires libkrb5 which is built and
installed, too.
Are those MKKERBEROS settings still valid?