[SOLVED] [Poll] Should future versions of Slackware include Linux-PAM?
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.
View Poll Results: Should future versions of Slackware include PAM?
Yes, future versions of Slackware should include PAM.
[Poll] Should future versions of Slackware include Linux-PAM?
Hi,
The subject has already been discussed to some extent, but here's the corresponding poll.
Slackware is one of the very few Linux distributions that doesn't ship PAM. While the absence of PAM may be of no consequence to the average desktop user or even the administrator of simple Slackware servers (LAMP, simple file servers, etc.), it's actually a showstopper to all those of us who'd like to use Slackware for tasks like secure LDAP-based central authentication, where PAM is a requirement.
Judging from the actual state of things, implementing PAM would only offer advantages. Those of us who are currently using RHEL, CentOS, SLES or Debian could make the move to Slackware for "enterprise" tasks. The presence of PAM under the hood will likely go completely unnoticed for the casual desktop user. As for the casual Slackware server admin, he or she will have to add the odd line to the relevant configuration file. No dramatic changes, and only a significant benefit for server administrators.
I take it, the 3-rd option is for those who don't care one way or the other. Nice to see reasonable poll options for a change
I bluntly admit that everytime I write something like "include PAM under the hood", the mental image of young Victoria Principal in the trunk of my car flashes briefly before my eyes.
MEANING: If you want PAM, man up and make the Slackbuild and share, don't throw a poll up and try and strong-arm Pat into more work.
Doing this is simply too much work, since it involves rebuilding and maintaining a significant number of base Slackware packages. On a side note, if you don't think I'm man enough for the task, let me point out that I'm the maintainer of a Slackware package repository that holds 402 packages on the latest count.
"significant number of base Slackware packages" - EXACTLY! but Pat provides all of the base Slackbuilds so halfthe work is already done.
AlienBOB has no problem doing this for MULTILIB packages.
It's not that I don't think you're man enough to do it, I'm not pointing at you specifically. I'm trying to point out to ANY user who thinks that X should change to Y because they want it, that they have the ability to do it without burdening the (volunteer) devs with more work.
If you want a simple answer to your poll- I vote NO. I don't need it, have never needed it, can't see a future need for it and it just introduces potential instabilities/vulnerabilities/dependencies
But, may I point out that you are polling a group of people who are living fine without it and therefore don't miss it so your results will probably be skewed in the "NO" direction.
We authenticate against a Kolab2-based LDAP directory without PAM on any machine (despite the name 'nss-pam-ldapd' doesn't need PAM). Exim for example is a pain to configure for LDAP-authentication, but it's possible. Perhaps there are applications which require PAM, but saying PAM is required in general is just wrong.
We authenticate against a Kolab2-based LDAP directory without PAM on any machine (despite the name 'nss-pam-ldapd' doesn't need PAM). Exim for example is a pain to configure for LDAP-authentication, but it's possible. Perhaps there are applications which require PAM, but saying PAM is required in general is just wrong.
Mike
You mean Linux-PAM was only included for fun here?
Here's the thing. One of the selling points of Slackware is the basic install does not overdo itself with every bell and whistle. This is left largely to the third party groups that add packages and package management systems (alienBob, etc).
If PAM is included by default, why not GRUB? Why not any arbitrary package that someone might find a user for? If it isn't needed to have a stable and running linux install that will allow you to install whatever you want (including a PAM system), then I do not think it should be added.
I do not see one, single, reason why this should be included in the base install. Not one person has come up with a reason other than "in some relatively remote situations it would make my life easier."
While this is a valid reason to make a slackbuild, et al for such a situation, this is not a reason to include something in the base install. Half of the reason Slackware hasn't been bloated beyond sanity as Debian/Ubuntu, RedHat, and others is the avoidance of this type of thing.
I say slackbuild it. Same relative amount of effort without pooping all over the idea of Slackware.
EDIT:
Furthermore, these words bother me.
"simple Slackware servers"
This means Slackware that doesn't run LDAP. This likely means most Slackware servers. I have no numbers to look at for this, but a single use case amonst many is not a reason for fundamental additions.
"Judging from the actual state of things, implementing PAM would only offer advantages. Those of us who are currently using RHEL, CentOS, SLES or Debian could make the move to Slackware for "enterprise" tasks."
I would like to know (I don't mean this to sound combative) what the 'actual state of things' means. I would love for this to be a rather elaborate reply since this seems to be the main point behind why PAM should be included.
Last edited by LysergicFacet; 02-07-2015 at 05:26 PM.
My post seems to have been dissapeared. It was a NO vote. Any ideas, anyone, where it went?
Welcome to LQ!
Sometimes a new user's early posts can take a few minutes to pass through the spam filters, or be queued for moderation. It will probably reappear soon.
Sometimes a new user's early posts can take a few minutes to pass through the spam filters, or be queued for moderation. It will probably reappear soon.
I've lurked for years. Figured I would get involved with all this as most of the other linux distros went to hell. I appreciate the response. I don't think I've used a forum system for almost ten years, so everyone please forgive my oldness.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.