(Sorry to revisit such an old bug, but we keep running into it now and then...)
If this is deemed to be a PAM bug, can this bug report just be re-tagged as a PAM bug and reassigned to the appropriate party? The high-level problem -- cron doesn't work for Kerberos/Hesiod users unless you manually add /etc/shadow entries -- seems pretty clearly like a bug to me, regardless of which package is eventually deemed at fault. Ken -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
