On Tue, Apr 15, 1997 at 10:09:15PM -0500, Adam Slattery wrote: > > Does the ability to specify alternate locations for the password file come > at > > the expense of being able to use the system getpwnam() call (and therefore > > make use of other NSS backends), or have you balanced both of these > > requirements in a single module? > > Unfortunatly, yes. That was a sacrafice I decided to make. I don't use any > of the standard libc calls for interfacing to a password file at the moment. > I knew this would probably be a source of flames, but I decided to do it > anyway. I've been thinking about doing "both" at the same time where the > administrator could select which one to use with an option in the pam.d > service file. Now that I've had somebody request this (or mention it..), I > will probably implement it. This is not a priority, however, and may not be > added for a little while. So in short, it does come at the expense of not > using NSS, but in the future it will be well balanced with the best of both > worlds. Well, I think it would be nice to have getpwnam() be a source for pam_crypt. Also, how do you plan to support password changing? Is it done in a modular way as well? If so, which modules are available? > Thanks, > Adam Slattery Nico --
