Tested so far:

• domain and local logins (login,xdm,kdm) and session lock.
• SSO domain shares access (dolphin)
• SSO sftp (dolphin)
• SSH SSO (PAM should work, but password logins are not recommended anyway)
• HTTP SSO with mod_auth_kerb
• IMAP dovecot with SSO and PAM (GSSAPI and LOGIN)
• SMTP postfix with dovecot sasl (GSSAPI and LOGIN)

NOTES updated.

Happy New Year


Cheers

5 members found this post helpful.

Let me welcome your initiative.

Slackware really has serious problems in an office.

thanks for your work, ivandi!

Tested so far:

• DHCP clients updating their DNS records (SAMBA INTERNAL DNS)
• Domain provision with BIND9_DLZ (basically works, didn't test it further)
• NFSv4 with KRB5 Security (within Samba AD domain)
• Openldap + Krb5 for central authentication (basically works, didn't test it further, probably sssd will be better than nss-pam-ldapd + pam-krb5)

NOTES updated.


Cheers

3 members found this post helpful.

OK, CUPS SSO works. And ... RSH works with PAM (huh).

So, the repository is perfectly usable. If you follow my NOTES setting up a Samba AD domain with Single Sign-on (SSO) works out of the box. Anyway, if netatalk doesn't work please let me know, but better send patches.

REMINDER:
PAM is a nice lady, but keep an active root login while playing with /etc/pam.d/system-auth.
Kerberos can be a messy dog, it won't obey root. RTFM carefully.


Have fun

Cheers

5 members found this post helpful.

What is the current state of that? Will it work on Slackware-Current with KDE5 from Eric?

It works fine on Slackware-current with the stock KDE4.

No idea, KDE5 is not part of current for now.


Cheers

Ivandi,

If one wants to build this from source, what would be the best way to accomplish this? Using the spamware.SlackBuild or individually? Also, do I need to remove certain packages from the baseline install before doing this? Thank you very much for spending time doing this for the community.

The intended way is to use spamware.SlackBuild on a full install of Slackware-current. It will follow the build order and run the the slackbuild for every package if there is no a txz package or the slackbuild is newer than the package. Then it will upgradepkg --reinstall --install-new.

In every package directory the getsrc.sh if executable is sourced by the slackbuild to download the source. This could fail sometimes because of endless redirections from github or sourceforge. You can download the source manually and make getsrc.sh non-executable.

And finally after all packages are built and installed you can use the genmeta.sh in /meta to generate PACKAGES.TXT and CHECKSUMS.md5.


Cheers

1 members found this post helpful.

Thank you!

The current is shaping up and the stuff here looks quite stable too. So I encourage those of you who would like to use PAM and Kerberos in Slackware to give these packages a try and report back.

I have no problem maintaining this project for my own needs, but now that we have /extra/pure-alsa-system/ I wonder if we could also have /extra/pam+kerberos


Cheers.

5 members found this post helpful.

Honestly, I hope someday to see instead a /extra/pure-non-pam+kerberos but I know I ask too much...

Thanks ivandi !

Downloaded a fresh copy spamware via your sync-spamware.sh script.

Will set up a pair of Slackware64 14.2+current VMWare Machines and I'll take spamware for a spin as an AD DC and an AD Client on a VMWare Network along with a Win7 Pro Client in the next couple weeks.

Thanks again !

-- kjh( still love that name -- it is a keeper )

1 members found this post helpful.

Well, better late than never



Lately I've been reviewing the configs in /etc/pam.d with the idea to ensure consistent behavior across all PAM enabled services. There are still some tweaks to do but I think I am pretty close. Give it a try.


Cheers

5 members found this post helpful.

Every time I see the title of this thread I think of...


Cooking up some Spam. <grin>