[SOLVED] Pam + krb5 + samba

mfoley · 10-03-2016, 09:22 PM

That looks easy enough. I'll give that a shot and post back, but it may not be for a several days. Actual work is impinging on my play time!

mfoley · 10-03-2016, 09:27 PM

Meanwhile, a minor issue that may be simple ... I have the following in /etc/suauth:

root:mfoley:NOPASS

Before installing the _pam packages, I used to be able to `su -` (from user mfoley) and it would dump me into root user without having to enter the root password. After installing _pam packages, that no longer works. Is this a simple pam.d config issue or a more complex build? This is totally non-critical, but I've grown accustom to this mechanism.

kjhambrick · 10-04-2016, 05:47 AM

Quote:

Originally Posted by ivandi

kde-workspace-4.11.22-x86_64-1_pam.txz

And the slackbuild.

Works fine.

Cheers

Thanks ivandi !

Very clean and complete !

-- kjh

kjhambrick · 10-04-2016, 08:20 AM

p.s.

ivandi --

Thank you for the updates !

I just noticed that kde-workspace is a sub-directory of PAM-packages and in addition to adding kde-workspace/ you've also updated bind and php with the latest Slackware64-14.2 Packages.

Woo Hoo !

I want to install on a clean Slackware64-14.2 System so I'll be starting over with a fresh install for proper testing.

I had to delete my VMWare snapshots in order to bump the HDD size in the VMWare Machine so I could recompile all of KDE last weekend.

Anyhow, I am going to blow away the PAM-enabled Client, reinstall Slackware64-14.2 and upgradepkg your _pam Packages, including kde-workspace.

It won't be until this weekend but I'll get-r-dunn and report back.

Thanks again.

-- kjh

ivandi · 10-04-2016, 08:41 AM

Quote:

Originally Posted by mfoley

Meanwhile, a minor issue that may be simple ... I have the following in /etc/suauth:

root:mfoley:NOPASS

Before installing the _pam packages, I used to be able to `su -` (from user mfoley) and it would dump me into root user without having to enter the root password. After installing _pam packages, that no longer works. Is this a simple pam.d config issue or a more complex build? This is totally non-critical, but I've grown accustom to this mechanism.

pam_wheel

/etc/pam.d/su

Code:

auth		sufficient	pam_rootok.so
auth		sufficient	pam_wheel.so trust use_uid
#auth		required	pam_wheel.so use_uid
auth		required	pam_env.so
auth		include		system-auth

account		required	pam_nologin.so
account		required	pam_time.so
account		include		system-auth

session		required	pam_limits.so
session		optional	pam_umask.so
session		optional	pam_xauth.so
session		include		system-auth

password	include		system-auth

Cheers

mfoley · 10-04-2016, 11:03 AM

Ivandi: That worked! Adding the user to group wheel plus uncommenting that auth line in /etc/pam.d/su did the trick. Your knowledge of Linux/Slackware esoterica is truly impressive. Between kjhambrick and myself you are getting a fan club.

kjhambrick · 10-04-2016, 11:07 AM

Quote:

Originally Posted by mfoley

Ivandi: That worked! Adding the user to group wheel plus uncommenting that auth line in /etc/pam.d/su did the trick. Your knowledge of Linux/Slackware esoterica is truly impressive. Between kjhambrick and myself you are getting a fan club.

+1