From: Jason DiCioccio (geniusj at gmail dot com)
Date: Tue Nov 09 2004 - 17:31:25 EST
Does anyone have any other ideas? I'm digging around in the SASL code
for answers at this point but coming up short. Has anyone here
written a PAM module that they later used with SASL?
Thanks in advance!
On Tue, 9 Nov 2004 09:53:58 -0500, Jason DiCioccio <geniusj at gmail dot com> wrote:
> I have the following already:
> int pam_sm_setcred(pam_handle_t *pamh,int flags,int argc
> ,const char **argv)
> D(("setcred called"));
> return PAM_SUCCESS;
> It is never even called though. I have stub functions like that for
> the account and session functions too.. But again, I don't see any
> functions called from sasl except for pam_sm_authenticate.
> On Mon, 8 Nov 2004 15:17:41 -0500, Derrick J Brashear
> <shadow at andrew dot cmu dot edu> wrote:
> > On Nov 8, 2004, at 1:08 PM, Jason DiCioccio wrote:
> > >
> > > In my PAM debug log, I'm getting the message "Authentication
> > > successful" when I enter in a correct user/pass pair (using smtptest).
> > > However, sendmail is giving me an authentication failure (-13). I
> > > do not get this same error if I change the pam config so that sendmail
> > > uses pam_pwdb.so instead. However, I cannot figure out why, if SASL
> > > is receiving a PAM_SUCCESS return code from pam_sm_authenticate, and
> > > it's not calling any of the other functions in pam_alakazam, it would
> > > return a fail code.
> > >
> > I'd guess you need a setcred function that returns success; setcred is
> > part of the auth hook.