On Tue, 8 Mar 2005, Quentin Garnier wrote:

> Speaking of which, there is an issue for people like me who compile with
> MKKERBEROS=no.  That way, pam_krb5.so is not built, but yet it is referenced

Have the set lists been fixed for MKKERBEROS=no case? When PAM
was initally commited, I did a build with MKKERBEROS=no, but the
set lists still referenced pam krb modules. IIRC, I haven't seen
a commit to fix this.

> by the pam configuration files.  Hence after the installation of such a
> system, I can't login.

Uh-oh, that's way worse than mere set list lossage.