• pam_securetty deprecated?

    From jayjwa@jayjwa@atr2.ath.cx.invalid to alt.os.linux.slackware on Fri Oct 30 09:55:01 2026
    From Newsgroup: alt.os.linux.slackware


    Context: Slackware Current, as of a couple days ago. This message in the Changelog as per Sat Oct 24 23:50:58 UTC 2026:

    a/util-linux-2.42.4-x86_64-2.txz: Rebuilt.
    /etc/pam.d/login: don't use pam_securetty.so here. It's been deprecated for
    some time now, and it blocks root from logging in on KMSCON unless the pts
    devices are added to /etc/securetty. We'd rather not do that as it could
    expose network daemons to root login attempts.

    Changelog as per Sun Oct 25 21:45:47 UTC 2026:

    a/util-linux-2.42.4-x86_64-4.txz: Rebuilt.
    /etc/pam.d/remote: restore pam_securetty.so here.
    Thanks to Petri Kaukasoina.

    Given these, I have three questions:
    1. Is pam_securetty truely deprecated? I see nothing in its man page
    about this and I could find no link online. Given the amount of fluff in
    search engines, this might be the reason. Can I get a link to this?

    2. Does pam_securetty in /etc/pam.d/remote really do anything? This is
    my /etc/securetty:
    # This file defines which devices root can log in on.

    # These are the ttys on the physical console:
    console
    tty1
    tty2
    tty3
    tty4
    tty5
    tty6

    No remote connection would ever match any of those, so why have
    pam_securetty in /etc/pam.d/remote? When I telnet in (local LAN), the
    tty is /dev/pts/13 . Can someone explain this and its workings?

    3. What calls, or is supposed to call, /etc/pam.d/remote?
    --
    PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
    "The Internet should always be the Wild West!"
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kaukasoina3dore73js4@kaukasoina3dore73js4@sci.fi (Petri Kaukasoina) to alt.os.linux.slackware on Sun Nov 1 16:37:39 2026
    From Newsgroup: alt.os.linux.slackware

    jayjwa <jayjwa@atr2.ath.cx.invalid> wrote:
    2. Does pam_securetty in /etc/pam.d/remote really do anything? This is
    my /etc/securetty:
    ...
    No remote connection would ever match any of those, so why have
    pam_securetty in /etc/pam.d/remote? When I telnet in (local LAN), the
    tty is /dev/pts/13 . Can someone explain this and its workings?

    Because you have not added pts/13 in /etc/securetty, you can't log in as
    root via telnet.

    3. What calls, or is supposed to call, /etc/pam.d/remote?

    login -h
    --- Synchronet 3.22a-Linux NewsLink 1.2