According to this http://www.hashbangbash.com/downloads/pam/NOTES.txt

And especially this http://www.slackware.com/~vbatts/pam/
It looks like Vincent Batts and Robby Workman are testing the integration of Linux Pam for the next slackware release.

I think this a good news. It will greatly ease the integration of Kerberos/LDAP authentication in slackware.

5 members found this post helpful.

Did I sleep through the release of Slackware 14.2?

Good news indeed.

No, but I'm ready for beta , so here's my 14.2 prediction ...
Setting Orange, The Aftermath 63, 3180 YOLD

Better hurry

2 members found this post helpful.

Yeah, hope we'll see something in the ChangeLog.

Service configs in /etc/pam.d need a lot of testing and customization. And for now Batts and Workman's configs look plain vanilla. So I am pretty sure there will be no PAM in 14.2. Lets hope for 15.

That said I uploaded several PAM enabled slackbuilds for those willing to tweak service configs.

Tested cups, vsftpd, at, cron(dcron has no PAM support so I replaced it with cronie from SBo).

Will test openvpn at some point.

Not sure about ipopd, imapd. Is there somebody who still uses wu-imap.

Cheers

Added cracklib. Kerberos has his own passord policy. So it's your choice.

Added slackbuilds for xdm xlockmore screen.
Changed PAM slackbuild to make unix_chkpwd sgid shadow. That makes xlock and screen C+a x work. No need for sgid shadow for xlock.

Added PASSWDTYPE=pam to alpine slackbuild to make imapd and ipop3d actually use PAM. Works fine.

Replaced sendmail. I prefer killing brain cells with a glass of wine than reading sendmail.cf. Exim is in SBo and I changed the slackbuild to use PAM. Put a reasonable default config, relay on auth over tls only. Works fine with PAM+LDAP.

I think I'll stop here. There are some 30 slackbuilds that provide a complete PAM, LDAP, Kerberos, NFS4, ADS support. If some work on PAM is going on at slackware.com I think my little project will be helpful. For me the advantages of having these technologies in Slackware are more than obvious.


Cheers.

3 members found this post helpful.

Sendmail, c'est spécial

Anyway, lets look at the Slackware's mail subsystem. Sendmail uses procmail as LDA. Procmail supports mbox and maildir. UW-IMAP supports mbox mbx and mix. It has tmail and dmail to support delivery in mbx/mix but both are not shipped by default ?!?. So we are left with the old flat file mbox. IMO nowadays mbox is only suitable for collecting mails from failed cron jobs.

At least exim supports mbx and has a human readable config. I am doing my best to keep compatible, but in it's present state Slackware's mail subsystem is not suitable for more than several dozen users setup.

Hope someone will prove me wrong.

Cheers.

I use getmail, dovecot and procmail. I have 2 users.

I'm happily using Postfix and Dovecot.

http://www.microlinux.fr/slackware/L...Mail-HOWTO.txt

The recent discussion about PAM revived my interest in this project. So I did a clean install of the current (skipped only KDE) and pamified it. Did some cleanup and recompiled more stuff that uses pam or kerberos. The process went flawlessly. XFCE, xdm, xlock, network-manager, Console-kit, polkit ... work as expected. The default authentication method is pam_unix (shadow) so nothing changes for the user
The number of packages that have to be recompiled is considerable and growing. I think we are close to 14.2 release so my intention is to maintain this stuff until the the start of the next development cycle. If Pat considers PAM for Slackware 15 this project is a good starting point.

BTW this link http://hashbangbash.com/downloads/pam/ seems to be dead. Does somebody know what's going on with VBatts project.

Cheers

2 members found this post helpful.

I just read this on his twitter, dunno really if related (hashbangbash.com is his own domain/homepage): I suppose you can try pinging him on freenode or write a message (as written here).

If anybody needs something from that repository, here is a mirror (updated at the beginning of october).

Terribly sorry. Dumb VPS project went flakey and I haven't been able to migrate cleanly to another provider yet.

Nice work ivandi! You probably should add package kmod to the list. Kmod does have a tool that uses PAM if available.

If you redo any Slackbuilds for SBo, it might be useful to name them with the *-pam.SlackBuild schema. Most likely several Slackbuild scripts will need PAM enabling modifications.

http://www.hashbangbash.com/downloads/pam/ is back online. Sorry for the inconvenience. Not all parts of the site are up, but that is.

@vbatts: is there any chance you might put up a package repository for a PAM-ified Slackware stable? On a 1-to-10-scale, this would be 12-helpful.

Cheers,

Niki