Chuck Yerkes writes:
>There.  Now who's up for coding the BSD Auth stuff and not
>writing more mail??

The issue isn't "coding BSD Auth".
Its what do you put in apps like login, sshd, su etc.
So that they can use BSD Auth OR PAM, without having to code the logic
twice in each application for each API.

An early proposal was to do a shim API, but that got shot down but the
"I only want BSD Auth" gallery.
Another option was do BSD Auth via PAM - also shot down by the 
"I only want BSD Auth" gallery.  
Another alternative may be to implement BSD Auth and PAM via nsswitch
but I gather the "I only want BSD Auth" gallery won't like that either
because they don't like nsswitch...

The only proposal that has been offered by the "I only want BSD Auth" 
gallery is "just do BSD Auth and I'll be happy", but of course that doesn't
meet the needs of the project or anyone else.

Note that all of the solutions that are likely to be acceptible to
"the project" will involve considerably more effort that the 
"I only want BSD Auth" gallery seem to think, since the project developers
have made it clear that just BSD Auth isn't enough.

So this thread is doomed to loop forever in states of flame, sleep, sulk
whatever...

Sorry
--sjg