Bug#563987: /lib/libnss_hesiod.so.2: hesiod users not fully supported
- To: 563987@bugs.debian.org
- Subject: Bug#563987: /lib/libnss_hesiod.so.2: hesiod users not fully supported
- From: Ken Raeburn <raeburn@permabit.com>
- Date: Mon, 23 Sep 2013 20:03:42 -0400
- Message-id: <[🔎] 6ea9j313xd.fsf@just-testing.permabit.com>
- Reply-to: Ken Raeburn <raeburn@permabit.com>, 563987@bugs.debian.org
- In-reply-to: <4B461AD9.3010000@aurel32.net> (Aurelien Jarno's message of "Thu, 07 Jan 2010 18:33:13 +0100")
- References: <20100106212404.25279.16186.reportbug@just-testing.permabit.com> <20100107000955.GV7032@hall.aurel32.net> <4B4602C5.8030809@permabit.com> <4B460C89.8060001@aurel32.net> <4B460E36.8000607@permabit.com> <4B461AD9.3010000@aurel32.net>
(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
Reply to: