SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I created a set of packages that add PAM support to Slackware 10.0 . In this first release only login, su, passwd, useradd, and proftpd use PAM, and it's configured to use your existing unix password mechanism.
Future releases will include more PAM-aware applications, will work on more recent versions of Slackware, and will have other configuration choices (e.g. authenticate to a Windows NT domain controller or ActiveDirectory server).
Looking for people to try it out. Let me know what you think, or if you run into any problems.
First of all I think you should a) publish your build-script(s)
and b) split the package into the modified 4 modules you're using.
Also, Slack 10 has quite clearly come of age, 10.2 has been out
for ages, and 11 is on the horizon (looking at the big steps in
the changelogs for current).
No, no mention of that in the logs... but it's not THAT hard to do,
just to begin with. All it takes is to grab the Linux-PAM from
kernel.org, compile and install it (--exec-prefix=/usr) and compile
both util-linux and shadow against it (use Pat's build-scripts and
modify them accordingly).
Do the same for all other apps you need to be PAM aware. If there's
enough interest I can put a "How-to" in the Linux-answers section ;}
that would be cool! i'm sure lots of users would find that useful.
sigh, i feel like leaving slackware these days. No PAM? I really don't have the time to compile a load of stuff. nor should i have to for something that one would expect in any modern linux/unix.
not your fault tho. not getting at you. just really dissapointed with 10.2 and things getting worse. IMHO. maybe i am just expecting the wrong things. i understand the slack philosophy, but there is a limit. used to love my slack :-(
...split the package into the modified 4 modules you're using.
What do you mean by this? Right now I'm delivering 9 individual packages: Linux-PAM, gnutls, libgcrypt, libgpg-error, libprelude, pam-config-unix, proftpd, shadow, and util-linux.
Quote:
Originally Posted by Tinkster
Also, Slack 10 has quite clearly come of age, 10.2 has been out
for ages, and 11 is on the horizon (looking at the big steps in
the changelogs for current).
Yeah, but I had a Slackware 10.0 box just sitting here ready to go. ;-) I have a gazillion things I want to do with this that are more important than upgrading Slackware. I'll get to it eventually, probably about the time that Patrick has a change of heart about PAM and decides to include it in Slackware.
Quote:
Originally Posted by Tinkster
I've only just PAMified my slack-box last week ;}
Really? What apps did you PAMify? Have you set up other authentication modules? Did you put these together as slack packages so they're easy to install?
BLASPHEMY!!! It shall rain frogs and blood from the sky, sticks that are just lying around on the ground will be turning into snakes at will. Dogs and Cats living together, MASS HYSTERIA!
FYI, Dropline GNOME already has PAM installed and have a VERY easy build system where you can "PAMify" pert near any app you want.
What do you mean by this? Right now I'm delivering 9 individual packages: Linux-PAM, gnutls, libgcrypt, libgpg-error, libprelude, pam-config-unix, proftpd, shadow, and util-linux.
Doesn't say that on the site, neither does the link to a single download-package
suggest that it contains other tarballs. I didn't download it to check it since I
don't have any machines running on 10 any more.
Quote:
Originally Posted by eric.r.turner
Really? What apps did you PAMify?
So far only PostgreSQL, and the shadow and util-linux packages.
Am looking at using it with LDAP for centralised authentication.
Quote:
Originally Posted by eric.r.turner
Have you set up other authentication modules?
Nope - no need atm.
Quote:
Originally Posted by eric.r.turner
Did you put these together as slack packages so they're easy to install?
BLASPHEMY!!! It shall rain frogs and blood from the sky, sticks that are just lying around on the ground will be turning into snakes at will. Dogs and Cats living together, MASS HYSTERIA! :D
Heh - let's hope Pat doesn't visit much ;}
Quote:
Originally Posted by MMYoung
FYI, Dropline GNOME already has PAM installed and have a VERY easy build system where you can "PAMify" pert near any app you want.
Well, yeah. But I'd rather have haemorrhoids and zits than
Gnome on my machines... :}
Am looking at using it with LDAP for centralised authentication.
Just a thought (I have no experience with touching PAM or LDAP), but from the alt.os.linux.slackware FAQ, couldn't you use nss_ldap to authenticate instead of trying to add PAM into Slackware?
I'd rather have haemorrhoids and zits than
Gnome on my machines... :}
I totaly agree
Quote:
Originally Posted by Tinkster
If there's
enough interest I can put a "How-to" in the Linux-answers section ;}
I would be very interested in this.
I'm trying to build a Slax (live-cd based on Slackware-current) OpenLDAP/PAM authentication gateway.
My goal is have a system (Slax-Server) where I can create some user account that can be used in all the clients that the user decides to login in.
ATM I just sync the server's /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow files with the clients'
This kinda sucks, but it's a start.
I'm a complete noob in linux, but willing to learn
I just found out that Slackware does not support PAM... Why not? Is there a better way to do this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.