Re: saslauthd + pam_mysql broken ?

From: Andreas Winkelmann (ml at awinkelmann dot de)
Date: Thu Mar 25 2004 - 03:47:10 EST

  • Next message: Román Medina: "Re: saslauthd + pam_mysql broken ?"

    Am Donnerstag, 25. März 2004 01:39 schrieb Román Medina:

    > I'm using Debian unstable with Postfix+saslauthd+pam_mysql. Everything was
    > working ok until I did a "apt-get upgrade" today. Then "smtp auth" got
    > broken and I always get:
    > Mar 25 01:19:34 localhost saslauthd[6420]: pam_mysql: select returned more
    > than one result
    > Mar 25 01:19:34 localhost saslauthd[6420]: DEBUG: auth_pam:
    > pam_authenticate failed: Permission denied
    > Mar 25 01:19:34 localhost saslauthd[6420]: do_auth : auth failure:
    > [user=roman] [service=smtp] [realm=rs-labs.com] [mech=pam] [reason=PAM
    > auth error]
    >
    > I've researched a bit and I've seen that saslauthd is sending an incorrect
    > query to Mysql: saslauthd is asking for the pass of "user" instead of
    > "user at domain dot com", which is the complete sasl_username received by postfix
    > (although saslauthd takes the domain part as "realm").
    >
    > Since Postfix hasn't been updated I suspect that the problems comes from
    > saslauthd. Is it possible that the behaviour of saslauthd have been
    > changed between last versions/snapshots? How could I fix it? (perhaps it
    > is possible to force the use of domain by changing any switch/variable, or
    > may be it's a bug introduced in last versions? :-? )

    Because of there are many lines of code written to implement this behavior, i
    wouldn't call it "Bug". Maybe "Feature" is a better term...

    I personally don't understand the reason, but it is not configurable.

    Use a version before 2.1.17, best to downgrade to 2.1.15.

    -- 
    	Andreas
    

  • Next message: Román Medina: "Re: saslauthd + pam_mysql broken ?"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD