(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
Ken Raeburn a écrit :
Aurelien Jarno wrote:
hesiod is not supposed to be used to provide password. Even if used that
way, I don't really see the point of providing a shadow database though
hesiod, as the data will anyway be public, as published in the DNS.
Certainly not password
Aurelien Jarno wrote:
hesiod is not supposed to be used to provide password. Even if used that
way, I don't really see the point of providing a shadow database though
hesiod, as the data will anyway be public, as published in the DNS.
Certainly not password authentication data, but it can
Aurelien Jarno wrote:
Wouldn't it be possible to also use Kerberos for shadow information, as
it is actually where the encrypted passwords are stored?
Kerberos doesn't necessarily have the information in its database, and
the protocol provides no way to pass the information around.
Ken Raeburn a écrit :
Aurelien Jarno wrote:
Wouldn't it be possible to also use Kerberos for shadow information, as
it is actually where the encrypted passwords are stored?
Kerberos doesn't necessarily have the information in its database, and
the protocol provides no way to pass the
Package: libc6
Version: 2.7-18
Severity: normal
File: /lib/libnss_hesiod.so.2
We've found that since updating to lenny, cron jobs for normal,
non-local users (who are listed in hesiod) aren't being run. Adding
entries to /etc/shadow works around it. The following message gets
logged, and the
On Wed, Jan 06, 2010 at 04:24:04PM -0500, Ken Raeburn wrote:
Package: libc6
Version: 2.7-18
Severity: normal
File: /lib/libnss_hesiod.so.2
We've found that since updating to lenny, cron jobs for normal,
non-local users (who are listed in hesiod) aren't being run. Adding
entries to
7 matches
Mail list logo
