[Samba] Not authenticating on Slackware domain member

Mark Foley mfoley at ohprs.org
Fri Sep 9 13:44:23 UTC 2016

I've found that in Slackware none of the programs are built for PAM. For example 

ldd /bin/login

shows no libpam.so.0. Likewise for su, samba, sshd, and basically everything.

For whatever reason, Slackware doesn't believe in PAM. Does AD login/authentication from a
domain member absolutely *require* PAM?


-----Original Message-----
Date: Fri, 09 Sep 2016 00:23:24 -0400
Organization: Ohio Highway Patrol Retirement System
To: samba at lists.samba.org
Subject: [Samba] Not authentication on Slackware domain member
From: Mark Foley via samba <samba at lists.samba.org>

I've successfully set up a single-sign-on for a domain member using Ubuntu. Now I'm trying to
do the same for Slackware. I've and installed kerberos and PAM and followed the instructions in

I can successfully do `wbinfo -u` and `getent passwd userID`. But, when I try to log I get:

$ su - mark
su: Authentication failure

In my /var/log/secure I have:

Sep  8 22:59:34 labrat su[1396]: Authentication failed for mark
Sep  8 22:59:34 labrat su[1396]: FAILED su for mark by mfoley
Sep  8 22:59:34 labrat su[1396]: - /dev/pts/0 mfoley:mark

I'm suspecting PAM. The Slackware PAM did not ship with a /etc/pam.d directory so I used the
one from the wiki website.  That one did pass all the `make check` tests in the pam build

What can I do to get more information on figuring this out? I can rebuild pam with debugging
if that seems the likely culprit.

Thanks --Mark

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

More information about the samba mailing list