HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] Hylafax+ 5.1.1 with pam_winbind Debian
On Apr 9, 2007, at 4:10 PM, Rick Romero wrote:
On Mon, 2007-04-09 at 12:32 -0700, Lee Howard wrote:
Rick Romero wrote:
Apr 9 10:13:33 localhost hfaxd[32636]: pam_authenticate failed in
pamCheck with 0x7: Authentication failure
Apr 9 10:13:33 localhost *** glibc detected *** corrupted double-
linked
list: 0x08098018 ***
The error "pam_authenticate failed in pamCheck with 0x7:
Authentication
failure" is fairly clear. pam_authenticate (PAM function to
authenticate the user/pass) is failing and returning 0x7 which,
translated, means "Authentication failure". And that's perhaps a
fairly
generic-sounding error-message to get from a "pam_authenticate"
function, but it typically just means that your username or
password are
not matching up. In any case, the authentication failure is a
matter to
resolve with your underlying PAM configuration or authentication
mechanism.
I would concur, and just to be sure, I'm able to authenticate via ssh
using pam_winbind. I get kicked out for some reason (no shell?),
but my
home directory is created per the mk_homedir module. AFAICT, the pam
module is functional per the auth.log:
Ok, you're right. I had to change my pam.d/hylafax to have the
pam_winbind listed first.
Now the user can log in, but a group change doesn't seem to take.
Maybe something is cached, because my test user _was_ in the faxadmin
group - and after removing it I can still see all faxes. Maybe
that's how it supposed to be, I'll have to look into that more.
I'm good for the moment :)
Thanks for the help!
Rick
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*