In message <200308260232.h7Q2WINv017170@ginger.cmf.nrl.navy.mil>, Ken Hornstein
 writes:
>Do you care if someday, later, BSD Auth kept the same external interface,
>but the backend was rewritten to incorporate PAM as well?  By that I mean
>we could have a PAM module that did BSD Auth, or some super-API that did
>both PAM and BSD Auth.

My only objection, and I think it's trivial, is that I've had several negative
experiences involving PAM setups.  However, I think NetBSD is more likely to
do things right, so I'm not very worried.  Here's what I want:

1.  Something basically like a current BSD/OS ftpd or similar program
will "just work" - all the library calls and headers for BSD Auth are present,
and I can share code.
2.  I can share login.conf files between BSD/OS and NetBSD.

That's all *I* care about.  Obviously, this is a woefully incomplete spec
compared to what we probably want for a "real" implementation in NetBSD.

-s