2 messages in net.sourceforge.lists.courier-users[courier-users] authdaemon sporadic a...
FromSent OnAttachments
Gregor LawatscheckApr 22, 2002 4:21 pm 
Sam VarshavchikApr 22, 2002 4:43 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] authdaemon sporadic authfailure FreeBSDActions...
From:Gregor Lawatscheck (gp@mpex.net)
Date:Apr 22, 2002 4:21:44 pm
List:net.sourceforge.lists.courier-users

This is about authdaemon with sqwbmail - I'm posting this to the courier group because I've seen authdaemon appears to be used by other courier applications too - so I'm hoping for a broader group of people with authdaemon experience...

I'm using sqwebmail with vpopmail 5.2 (passwords in mysql through vchkpw) and authdaemon(.plain) on FreeBSD 4.2. Everything worked fine - at least I thought. I've noticed that after a while I just couldn't login anymore and I was pretty sure the password was right (even reset it with vpasswd ). So I started some debugging with authtest:

customer /etc/rc.d# /usr/src/sqwebmail-3.3.3.20020418/authlib/authtest thor@webmail.mpex.net <password> Authenticated: module authdaemon [...] works

customer /etc/rc.d# /usr/src/sqwebmail-3.3.3.20020418/authlib/authtest gre@webmail.mpex.net <password> Authenticated: module authdaemon [...] works

customer /etc/rc.d# /usr/src/sqwebmail-3.3.3.20020418/authlib/authtest gre@mpextest.net <password> Authenticated: module authdaemon [...] works

customer /etc/rc.d# /usr/src/sqwebmail-3.3.3.20020418/authlib/authtest gre@webmail.mpex.net <passwort> Authentication FAILED!

suddenly stops working

restarting the daemon will make it work again - for a while - ... until I try gre@webmail.mpex.net (works) then gre@mpextest.net (works) and back to gre@webmail.mpex.net (fails). I've reduced the number of daemons to 1 (two daemons run weird enough even when set to 0) - so that doesn't appear to make a difference. I went back from the snapshot to the 3.3.3 stable release - same problem.

I then kicked out authdaemon altogether configuring with --without-authdaemon and straight with --with-module=authvchkpw. That works fine. Obviously I can't use authtest to check but I can't reproduce the error on the web interface anymore...

Very weird - has anyone ideas what this could be - I'm willing to do some more debugging. Should I even bother trying to get authdaemon running - will it make a big performance difference when intented for a larger usergroup?

Thx for your advise, Gregor