"Daniel Richard G." <[email protected]> writes: > What about just punting on upgrades altogether, and putting in the > rearranged config only on a new install? Could that be done with > appropriate postinst magic?
The tricky part is coordination. At what point can libpam-krb5 drop the minimum_uid setting and assume that it's in krb5.conf? > Alternately, you could pop up a big scary debconf warning... there's > ample precedent for that. My concern with this is that I think this only affects a small set of users of the packages, so I'm reluctant to bother the other ones. One has to both have a mix of Kerberos-authenticated and non-Kerberos users, distinguish by UID, and mind the silent Kerberos authentication failure when handling the UNIX login. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- Why is /usr/share/pam-configs/krb5 specifying minimum_uid= ? https://bugs.launchpad.net/bugs/369575 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
