> This is not a bug in the hesiod package; the hesiod package only provides > the hesinfo utility and the libhesiod library. Support for Hesiod-based > logins comes from glibc itself.
ah. I hadn't realized it was the glibc package and not libhesiod > Unless you are trying to connect your system to a site with a pre-existing > Hesiod deployment, I strongly recommend *not* using Hesiod. I can't agree with this. hesiod is vastly simpler than the alternatives. > In any case, I > have never heard of a site that distributed passwords using Hesiod -- you > most likely cannot use pam_unix with libnss_hesiod, but need something like > pam_krb5 instead for authentication purposes. correct, in my environments authentication is down through kerberos (tickets or passwords) or by ssh host keys. The bug is that I need a dummy shadow file entry for the account to be recognized. One workaround would be to have hesiod always spit a placeholding entry back. But you're right, I guess this isn't really a bug in the hesiod package. seph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
