It's be neat to have clean hooks to replace the /etc/passwd based authentication with an external one (perhaps via #define?). MANY platforms don't have PAM and those that do, are sometimes not quite compatible.
Being able to cleanly pull the auth out into LDAP (for example) would be a boon. I've done this before for 2.5, but not the current code base. Quoting Ted Cabeen ([EMAIL PROTECTED]): > In message <[EMAIL PROTECTED]>, "J.D. Bronson" writes: > >I am seriously hoping that somone out there knows what to do here. > >I compiled qpopper4.0.3 on OpenBSD 3.0 i386 and it built with NO ERRORS. > >I launched it and it starts fine. > >It answers and then IMMEDIATELY slams the door shut! ... > >What can I check?? any hints at all? > > There's a known bug when running qpopper on OpenBSD. The socket handling > code in qpopper triggers a bug in OpenBSD. There was a thread about this on > tech@openbsd about a month ago, but I haven't heard any developments since > then. It will work fine if you run qpopper through inetd, so I'd suggest > doing that as a workaround. > > Another thing to note is that with OpenBSD, you have to force DES passwords, > as OpenBSD defaults to blowfish, and since there's no PAM in OpenBSD, qpopper > has to do the authenication itself. I was working on a patch that would > provide support for blowfish and MD5 crypt replacements, but I haven't > finished it yet. > - -- > Ted Cabeen http://www.pobox.com/~secabeen [EMAIL PROTECTED]
