• Moving to Slackware 15, having troubles with PAM

    From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Wed Oct 28 21:11:43 2026
    From Newsgroup: alt.os.linux.slackware

    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.


    Thanks in advance for any advice you can supply.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Small@smallm@panix.com to alt.os.linux.slackware on Thu Oct 29 00:00:55 2026
    From Newsgroup: alt.os.linux.slackware

    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'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.

    I don't recall having to do much or understand PAM, but I hadn't
    customized the shadow system much if at all.

    First I'm noticing this comment at the end of login.defs(5):

    Much of the functionality that used to be provided by the shadow password
    suite is now handled by PAM. Thus, /etc/login.defs is no longer used by
    passwd(1), or less used by login(1), and su(1). Please refer to the correrCE
    sponding PAM configuration files instead.

    So I'm thinking of two possibilities for your case:

    1. something in your login.defs is confusing su+PAM. The above says "less
    used" not "no longer used".

    2. your past configuration has nothing to do with it, but PAM's
    configuration is somehow messed up or you're missing module files.

    I think #2 more likely, myself. In my /etc/pam.d/su I have...

    ------------------------------------------------------------------------ #%PAM-1.0
    auth sufficient pam_rootok.so
    # Uncomment the following line to implicitly trust users in the "wheel" group. #auth sufficient pam_wheel.so trust use_uid
    # Uncomment the following line to require a user to be in the "wheel" group. #auth required pam_wheel.so use_uid
    auth include system-auth
    account include system-auth
    password include system-auth
    session include system-auth
    session optional pam_xauth.so ------------------------------------------------------------------------

    The included /etc/pam.d/system-auth is longer, so I'm not pasting it in.
    You can look at your installed copy vs what's in the Slackware package.
    Here are the password related entries:

    ------------------------------------------------------------------------ password requisite pam_pwquality.so minlen=6 retry=3
    password sufficient pam_unix.so nullok sha512 shadow minlen=6 try_first_pass use_authtok

    # ATTENTION: always keep this line for pam_deny.so:
    password required pam_deny.so ------------------------------------------------------------------------

    Each of these modules have man pages. pam_deny(8) has this paragraph:

    This module can be used to deny access. It always indicates a failure to the
    application through the PAM framework. It might be suitable for using for
    default (the OTHER) entries.

    I could imagine your behaviour coming from a 'sufficient' module line and
    no pam_deny.so line, but I don't know how you'd end up with that. The
    meanings of requisite, sufficient, and required are defined in
    pam.conf(5).

    Or if it's not the password entries, maybe examine the auth
    entries. Between pam.conf(5) and each module (3rd field, e.g. pam_deny
    or pam_unix) having a man page, there's lots to read that might point
    you right.

    Finally, you can get some pretty extensive debug output about what
    modules are loaded if you do the following before running su -:

    1. touch /etc/suid-debug (don't forget to remove this later)
    2. setenv LD_DEBUG libs or export LD_DEBUG=libs

    Regards,
    Mike Sm.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Thu Oct 29 16:04:14 2026
    From Newsgroup: alt.os.linux.slackware

    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).

    As far as I know, I've got all the relevant packages installed, but
    I will recheck this. I'm not seeing any evidence of error or misbehaviour
    in the log files, but will keep watch. If necessary, I'll enable
    debugging and watch the results for clues.

    I have a local privilege escalation issue that seems to have come from
    the upgrade. A logged in unprivileged user can gain root access without providing any credentials. A user physically at the system console can
    log in as root without providing any credentials. THIS bothers me greatly.

    To describe the specific problems I'm seeing, let me first describe
    the behaviour of the 14.2 system I'm migrating from:

    a) shadow passwords implemented, ssh installed and configured.

    b) The only terminal device is the console. I have NO other physical
    terminals on the system.

    c) ALL logins at the console (including root) ask for a password
    and prevent login if user is unknown or password is incorrect

    d) sudoers does not enable wheel group, /etc/group wheel group unused,

    e) /etc/ssh/sshd_config only contains
    LoginGraceTime 30s
    PermitRootLogin no
    MaxAuthTries 2
    MaxSessions 5
    PubkeyAuthentication yes
    AuthorizedKeysFile .ssh/authorized_keys
    PasswordAuthentication no
    X11Forwarding yes
    UsePrivilegeSeparation sandbox
    Subsystem sftp /usr/libexec/sftp-server

    f) ssh logins work to ssh rules (~/.ssh/authorized_keys, etc)
    the root user does not permit ssh login: /root/.ssh is empty

    g) from an unprivileged session (either at console, or via ssh)
    a user must provide the root password to "su - root"

    So, ssh logins require ssh keys, and physical logins and
    privilege-escalation commands require passwords.

    OTOH, with the upgraded system, behaviour is different.
    a) shadow passwords implemented, ssh installed and configured.

    b) The only terminal device is the console. I have NO other physical
    terminals on the system.

    These two are the same as before, but...
    c) root login at the console DOES NOT ask for a password, but immediatly
    grants a root session. It is /this/ behaviour that bothers me.

    OTOH, unprivileged logins at the console DO ask for a password. I
    have not exercised the "unknown user" or "incorrect password"
    scenarios yet.

    To continue:
    d) sudoers does not enable wheel group, /etc/group wheel group unused,

    e) /etc/ssh/sshd_config only contains
    LoginGraceTime 30s
    PermitRootLogin no
    MaxAuthTries 2
    MaxSessions 5
    PubkeyAuthentication yes
    AuthorizedKeysFile .ssh/authorized_keys
    PasswordAuthentication no
    X11Forwarding yes
    UsePrivilegeSeparation sandbox
    Subsystem sftp /usr/libexec/sftp-server

    f) ssh logins work to ssh rules (~/.ssh/authorized_keys, etc)
    the root user does not permit ssh login: /root/.ssh is empty

    HOWEVER...

    g) from an unprivileged session (either at console, or via ssh)
    a user is not prompted for the root password on "su - root",
    but is immediately granted a root session. /This/ behaviour
    also bothers me.

    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.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Thu Oct 29 16:26:49 2026
    From Newsgroup: alt.os.linux.slackware

    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.


    On Thu, 29 Oct 2026 16:04:14 +0000, Lew Pitcher wrote:

    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.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Small@smallm@panix.com to alt.os.linux.slackware on Thu Oct 29 13:16:15 2026
    From Newsgroup: alt.os.linux.slackware

    Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:

    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.

    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.

    Regards,
    Mike Sm.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Thu Oct 29 18:10:45 2026
    From Newsgroup: alt.os.linux.slackware

    On Thu, 29 Oct 2026 13:16:15 -0400, Mike Small wrote:

    Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:

    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.
    [snip]

    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?

    Yes. From the console, at login as root, via "su - root" from an
    unprivileged session logged in at the console, and via "su - root" from
    an unprivileged session, logged in via ssh. In all cases, the attempt at
    root access (via login or su) was denied.

    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.

    I appreciate the concern. It looks like I'm protected, but I will look
    into the intricacies of pam further, and ensure (to the best of my
    abilities) that the system is secure.

    Thanks for the advice and concern.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Henrik Carlqvist@Henrik.Carlqvist@deadspam.com to alt.os.linux.slackware on Mon Nov 2 06:14:58 2026
    From Newsgroup: alt.os.linux.slackware

    On Wed, 28 Oct 2026 21:11:43 +0000, Lew Pitcher wrote:
    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.

    My guess is that this is not because of PAM but because no password has
    been set for the root account.

    regards Henrik
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Henrik Carlqvist@Henrik.Carlqvist@deadspam.com to alt.os.linux.slackware on Mon Nov 2 06:22:39 2026
    From Newsgroup: alt.os.linux.slackware

    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.

    regards Henrik
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Mon Nov 2 14:16:05 2026
    From Newsgroup: alt.os.linux.slackware

    On Mon, 02 Nov 2026 06:22:39 +0000, Henrik Carlqvist wrote:

    Sorry about my previous reply which I wrote before relizing that the
    thread had more posts and was already solved...

    No problem. Any help is good help; I keep track of suggestions, so that
    /next time/, I have a better idea of what to look for, and what to fix.

    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?

    I wouldn't know; this isn't an "install from bare metal", and I don't use
    the Slackware recommended UPGRADE process

    The standard UPGRADE doc tells you to upgrade everything, and install everything new. That's the easy way, but (IMHO) it leaves a lot of cruft
    on the system.

    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.

    So, I have scripts that build a custom upgradepkg/installpkg(/removepkg)
    path to get from one release to another. It takes longer than the standard UPGRADE process, but I avoid installing things that I don't need, and it
    forces me to recognize /which/ packages I'm installing or upgrading. I've
    used this process, in one form or another, since Slackware 7 or 8.

    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.

    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.

    At least, for me, the exercise is as much about learning the tools as it
    is about installing or upgrading a running installation.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Henrik Carlqvist@Henrik.Carlqvist@deadspam.com to alt.os.linux.slackware on Tue Nov 3 06:53:46 2026
    From Newsgroup: alt.os.linux.slackware

    On Mon, 02 Nov 2026 14:16:05 +0000, Lew Pitcher wrote:
    For instance, I don't have any need for Samba as I don't have any
    MSWindows systems.

    As I usually add qemu to my Slackware installations and mostly use qemu
    with user mode networking (no root privileges needed), I like that qemu
    is able to use samba with user mode networking to share files from the
    host OS to ghe guest OS. Smbd is then run on the host OS with the
    privileges of the normal user which started qemu. Within the emulated
    guest operating system, different users, including root might do what
    they want with any files or directories on the cifs mount, but in
    practice, even root will get a "permission denied" if trying to access
    some file that the normal user does not have access to on the host
    computer.

    Not all operating systems have support for mounting smb/cifs shares, I
    have been able to work around that problem by starting two instances of
    qemu connected by a socket network. One instance acts as an NFS proxy,
    running Linux, mounting the hosts file system with cifs and running a userspace NFS daemon ( https://github.com/unfs3/unfs3/ ) to share the
    hosts files with the guest OS that does not have support for smb/cifs.

    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.

    Yes, one nice thing with Slackware is that it is really easy to customize
    in different ways. We have both chosen to customize the installation
    process.

    regards Henrik
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kaukasoina3dore73js4@kaukasoina3dore73js4@sci.fi (Petri Kaukasoina) to alt.os.linux.slackware on Tue Nov 3 08:21:14 2026
    From Newsgroup: alt.os.linux.slackware

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Tue Nov 3 14:45:26 2026
    From Newsgroup: alt.os.linux.slackware

    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
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Small@smallm@panix.com to alt.os.linux.slackware on Thu Nov 5 23:25:35 2026
    From Newsgroup: alt.os.linux.slackware

    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:

    {2640}smallm% readelf -d /usr/lib64/libavformat.so.58.76.100 | grep NEEDED
    0x0000000000000001 (NEEDED) Shared library: [libavcodec.so.58]
    0x0000000000000001 (NEEDED) Shared library: [libavutil.so.56]
    0x0000000000000001 (NEEDED) Shared library: [libm.so.6]
    0x0000000000000001 (NEEDED) Shared library: [libxml2.so.2]
    0x0000000000000001 (NEEDED) Shared library: [libbz2.so.1]
    0x0000000000000001 (NEEDED) Shared library: [libbluray.so.2]
    0x0000000000000001 (NEEDED) Shared library: [libz.so.1]
    0x0000000000000001 (NEEDED) Shared library: [libgnutls.so.30]
    0x0000000000000001 (NEEDED) Shared library: [libssh.so.4]
    0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
    0x0000000000000001 (NEEDED) Shared library: [libc.so.6]

    (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.)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lew Pitcher@lew.pitcher@digitalfreehold.ca to alt.os.linux.slackware on Fri Nov 6 12:46:21 2026
    From Newsgroup: alt.os.linux.slackware

    On Thu, 05 Nov 2026 23:25:35 -0500, Mike Small wrote:

    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.

    Yes, I've had that pleasure before. Long before this upgrade, I built ffmpeg from source for my previous Slackware installs. I even went so far as to
    build it for a variety of the optional, unsupplied conversions (after
    acquiring and installing those conversions as source code).


    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:

    Good to know. I'll keep that technique in mind, for when I upgrade my other systems.

    [snip]


    (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.)

    Aye, there's the rub.

    Thanks for the help and advice. I appreciate it.
    --
    Lew Pitcher
    "In Skills We Trust"
    Not LLM output - I'm just like this.
    --- Synchronet 3.22a-Linux NewsLink 1.2