Hi gals and guys
I'm having problems with Slackware 15's user authentication and authorization process, as managed by pam(8), and need some advice.
I've got a machine that's long been running 64bit Slackware 14.2. With this latest
PHP trouble (CVE-2026-109618 and CVE-2026-109619, aka "PHP2Shell"), I finally decided to upgrade the system to 64bit Slackware 15. While I've got the upgrade
mostly settled in, I've run into a bit of an issue with PAM.
With Slackware 14.2, I understood how logins worked, and had made sure that a) nobody could sudo(8) into root access, and
b) nobody could indiscriminately su(1) into root (you needed to know the root
password to successfully su(1) to root)
And then, I upgraded to Slackware 15. With pam(8).
Now, with no substantive changes to /etc/passwd, /etc/group, /etc/shadow, or /etc/login.defs, any logged in user can successfully "su - root" without answering
a password prompt or other authorization.
So, I've done something wrong. Or left something out.
As most of you have been running Slackware 15 for as long as it has been out, and a few of you came from other environments where pam(8) is a given, I'm hoping for some advice as to how to diagnose and fix this problem. My goal
is to regain the /simple/ authentication and authorization exhibited in
my old Slackware 14.2 system. Simple authorization by password would be sufficient for now; it's better than the open authorization I've currently got.
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
Hi gals and guys
I'm having problems with Slackware 15's user authentication and authorization
process, as managed by pam(8), and need some advice.
I don't recall having to do much or understand PAM, but I hadn't
Hi, Mike.--
Thanks for your reply. I'll review my pam setup with an eye
to your comments.
On Thu, 29 Oct 2026 00:00:55 -0400, Mike Small wrote:
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
Hi gals and guys
I'm having problems with Slackware 15's user authentication and authorization
process, as managed by pam(8), and need some advice.
[snip relevant problem description]
I don't recall having to do much or understand PAM, but I hadn't
[snip relevant discussion, not necessary to this reply]
In my thrashing around with this problem, I made some changes to /etc/pam.d/su and /etc/pam.d/elogind-user, that I've now backed out
(by "upgradepkg --reinstall", and ensuring the relevant .new files
have been properly taken care of).
I'm assuming that I've either missed some critical package or
misconfigured the authentication and authorization facilities
(both are possible).
I will keep looking, as per your suggestions. In the mean time,
I'd appreciate any further assistance you or the denizens of alt.os.linux.slackware can provide.
Many, many thanks.
Well, that /was/ useful, and I think that I've fixed my problem.
At least, I've managed to stop the privilege escalation, and
can look into the issue that lead to it at my convenience.
Mike's advice helped centre me, and, in expressing the problem
details, I had a thought: As all the problems seem to centre
around the root user's password, what would happen if I
/changed/ the password?
So, I logged on as root (no password prompt), issued the
passwd(1) command, and changed root's password. Then I
logged off.
Back at the login prompt, I tried to log in as root, and
lo and behold, login wanted the root password. I gave it
the new password, and got in properly.
I tested "su - root" from an unprivileged user, and, again
got the (previously missing) password prompt.
So, my guess is that, somehow, the /etc/shadow entry for
root wasn't properly formatted, when I copied it from the
14.2 shadow file.
Anyway, it's fixed. Thanks to all.
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:[snip]
Well, that /was/ useful, and I think that I've fixed my problem.
At least, I've managed to stop the privilege escalation, and
can look into the issue that lead to it at my convenience.
[snip]So, I logged on as root (no password prompt), issued the
passwd(1) command, and changed root's password. Then I
logged off.
Back at the login prompt, I tried to log in as root, and
lo and behold, login wanted the root password. I gave it
the new password, and got in properly.
I tested "su - root" from an unprivileged user, and, again
got the (previously missing) password prompt.
Anyway, it's fixed. Thanks to all.
Nice. Glad you've closed that up.
But just to be paranoid, have you tried mistyping the root password?
I'm concerned that if su (and pam_unix?) failed before at authorizing
against shadow, and speculating that its step 2 might have been something like, "well, proceed to next authorization; oh, there is no other so let
them in," then failing by wrong password might go down the same path
with the same result.
I don't understand PAM well, but it sounded like the pam_deny module was
very important to have active to make sure problems fail closed. I'm wondering if there was and still is something wrong with your system
with that.
Now, with no substantive changes to /etc/passwd, /etc/group,
/etc/shadow, or /etc/login.defs, any logged in user can successfully "su
- root" without answering a password prompt or other authorization.
So, I logged on as root (no password prompt), issued the passwd(1)
command, and changed root's password. Then I logged off.
Sorry about my previous reply which I wrote before relizing that the
thread had more posts and was already solved...
On Thu, 29 Oct 2026 16:26:49 +0000, Lew Pitcher wrote:
So, I logged on as root (no password prompt), issued the passwd(1)
command, and changed root's password. Then I logged off.
If I remember right, at the end of a stock Slackware installation, there used to be a dialog to set a password for the root user. Is that dialog
gone now? Or did you simply choose not to set a password at that dialog?
Since many years back I have customized my installation media to remove
all questions at the end of the installation to allways get the settings
I prefer. I set the root password with a custom /etc/shadow file in a
custom Slackware package instead of answering questions from dialogs.
For instance, I don't have any need for Samba as I don't have any
MSWindows systems.
There was a question here, this past year, asking "How do *you* install Slackware". It seems that many here (including me) have some variation
of "I do it my way" :-) I say, if it works, go for it.
For instance, I don't have any need for Samba as I don't have any MSWindows >systems. The standard UPGRADE instructions would have me install Samba, just >to leave it there, untouched, and a security exposure that I don't need. So, >instead of install, then delete, I don't install.
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
For instance, I don't have any need for Samba as I don't have any MSWindows >>systems. The standard UPGRADE instructions would have me install Samba, just >>to leave it there, untouched, and a security exposure that I don't need. So, >>instead of install, then delete, I don't install.
Audio and video related programs link to libavformat which is built to link to libsmbclient. So, without samba, many programs don't start.
On Tue, 03 Nov 2026 08:21:14 +0000, Petri Kaukasoina wrote:
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
For instance, I don't have any need for Samba as I don't have any MSWindows >>>systems. The standard UPGRADE instructions would have me install Samba, just >>>to leave it there, untouched, and a security exposure that I don't need. So, >>>instead of install, then delete, I don't install.
Audio and video related programs link to libavformat which is built to link >> to libsmbclient. So, without samba, many programs don't start.
That's good to know. When I get around to upgrading my workstation, I'll
look into that.
For the system that I just upgraded, it isnt necessary. That system performs server duties, and doesn't normally expose the sound utilities.
Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
On Tue, 03 Nov 2026 08:21:14 +0000, Petri Kaukasoina wrote:
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
For instance, I don't have any need for Samba as I don't have any MSWindows >>>>systems. The standard UPGRADE instructions would have me install Samba, just
to leave it there, untouched, and a security exposure that I don't need. So,
instead of install, then delete, I don't install.
Audio and video related programs link to libavformat which is built to link >>> to libsmbclient. So, without samba, many programs don't start.
That's good to know. When I get around to upgrading my workstation, I'll
look into that.
For the system that I just upgraded, it isnt necessary. That system performs >> server duties, and doesn't normally expose the sound utilities.
In case it ever becomes important to you it's quite easy to build an
ffmpeg package without libavformat linking to libsmbclient.
I feel much
as you do about having samba on my system. I see I have a local copy of
the ffmpeg slackbuild with this shell script next to it:
------------------------------------------------------------------------ #!/usr/bin/rc
SAMBA = no
BUILD = 2_slack15.0_nosamba
cd `{dirname $0}
sh ./ffmpeg.SlackBuild ------------------------------------------------------------------------
i.e. all you have to do is rebuild it with SAMBA set to no in the environment:
(Crossing my fingers that I'm not discrediting this approach by being
behind on the ffmpeg version in 15.0. There's the rub. You have to
remember what you did.)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:48:15 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |