| ReaperX7 |
02-19-2015 08:52 AM |
Quote:
Originally Posted by Alien Bob
(Post 5319921)
Let me add a last post before giving up on this ugly thread with its ugly Subject line.
You are ignoring the use-case for PAM.
If you have the time to tinker with your Slackware system and add PAM in a meaningful way, then that is not trivial, takes time, and introduces a maintenance burden because your computer may refuse to let you in after any official Slackware update if the "wrong" package gets updated and you did not notice. Also, this is a typical case where you are not going to have any use for PAM, since tinkering usually means, you are dealing with a single-user system.
Requiring someone like kikinovak to add PAM himself seems reasonable, because he can make a decision between the added work load of maintaining out-of-tree Slackware packages versus the increased functionality he can offer his customers (aka increasing revenue). Still, this strategy will introduce "islands" of non-standard Slackware setups that are hard to troubleshoot because if you post your issues here at LQ, none of us will be able to help because of the unknown implementation.
PAM is not evil despite rumors of the past. If implemented in a proper way, it will not add complexity to your computer. In its simplest implementation, you can just continue with your user management the way you are used even with PAM inbetween, while allowing others to add more complex authentication schemes without having to rebuild several core packages.
|
And that is what I said, just more drawn out. We could have a semi-standardized Linux-PAM package in SBo, for example, with enough of a detailed README-Slackware file explaining everything anyone would need to know. Rebuilding and reinstalling packages, configuration files, etc. Yes it would be "work" but that's not the point. The problem is until someone is willing to take it up, all we'll have is private out-of-tree packages in personal repositories.
Bart has done an exemplary job with his work and is leading by example of doing hard work with high pay out. His packages may never go official, but at least he's stood his ground and let his package speak for themselves.
As far as the use-case... it all depends is the best answer I can give you, and depending on what can be simple or complex on a case by case basis.
And yes, I agree with hitest, this topic has ran for enough time. By now we all should have gotten the information we all need, learned what we needed to learn, and forged our paths for whatever scenario comes, if and/or when. |
