[346] in Hesiod
Re: Hesiod 2.0.0
daemon@ATHENA.MIT.EDU (Russell McOrmond)
Mon Dec 30 15:35:31 1996
From: Russell McOrmond <russell@flora.ottawa.on.ca>
To: ghudson@MIT.EDU (Greg Hudson)
Date: Mon, 30 Dec 1996 15:33:51 -0500 (EST)
Cc: russell@flora.ottawa.on.ca, ghudson@MIT.EDU, hesiod@MIT.EDU
In-Reply-To: <199612240825.DAA16798@lola-granola.MIT.EDU> from Greg Hudson at "Dec 24, 96 03:25:57 am"
-----BEGIN PGP SIGNED MESSAGE-----
> > I am using the 'shadow passwords' to allow a hes_getpwname() to get
> > the 'Finger info' and other stuff from HESIOD, while obtaining the
> Sorry to take so long to get back to you on this. As you probably
> guessed, I don't want to take these changes. I don't want to
> introduce a dependency on the APACHE DBM file format, and this problem
> can be handled at the application level better than it can be handled
> in the Hesiod library.
While I can understand the desire to keep an APACHE DBM format out of
hesiod, I don't think I agree that it is better handled at the
application layer.
Would it be possible to introduce a hook that would allow various
authentication methods to be added for those who might wish this type of
functionality? What I'm trying to avoid is needing to send out a diff to
a specific version of hesiod, rather than something much more generic.
Otherwise, no problem: I can just keep a separate library which links
to the hesiod library that quickly enables this functionality.
- --
Russell McOrmond, Consultant: <http://www.flora.org/russell/work/>
(Internet/Intranet server admin,CGI programming,Web,Email,News, ...)
Community Volunteer: <http://www.flora.org/> <http://www.ox.org/ox/>
Help fight Spam on the Internet! <http://www.vix.com/spam/>
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAwUBMsgnLlnBbqL7SY1BAQEpugP/bMWsXn62foE24VgL5V/oee6y1ODRMF8n
zo8TMSFkucOODI2rDg6+Swqkr2sbXgJP+1JoQbNqdLZTcMLClbiQsNWBTBb18m1w
NgT8YdhlAojNtOh0RLbeOa7ck76znYFVtyEKTsUSimBYtr/PFNYMu/vdeYeOT3dl
wkHqzRUYyF4=
=nnXe
-----END PGP SIGNATURE-----
