After upgrading one of my systems from Bookworm to Trixie, I found that the SHELLINABOX application no longer printed the MOTD when logging in.
Digging into the details of this situation, I discovered that SIAB (was) switched from one PAM service to another, non-existent service:
Bookworm:Trixie:In other words, in Bookworm the "login" template in PAM is used, while in Trixie the "remote" template is used instead.
I "fixed" the MOTD problem by creating a "remote" service entry in the /etc/pam.d/ directory (just a copy of the "login" service entry);
the SIAB login now prints the MOTD as expected.
As nothing has been changed in SIAB (and because I could not find anything in SIAB to change that would explain or fix this behavior),
I'm assuming that something in PAM has changed, or the way PAM is invoked has changed, but what?
Any thoughts here?
Digging into the details of this situation, I discovered that SIAB (was) switched from one PAM service to another, non-existent service:
Bookworm:
Code:
[tod] pi-bookworm login[15787]: pam_unix(login:session): session opened for user rpi(uid=1000) by SHELLINABOX(uid=0)Code:
[tod] pi-trixie login: pam_unix(remote:session): session opened for user rpi(uid=1000) by pi-trixie(uid=0)I "fixed" the MOTD problem by creating a "remote" service entry in the /etc/pam.d/ directory (just a copy of the "login" service entry);
the SIAB login now prints the MOTD as expected.
As nothing has been changed in SIAB (and because I could not find anything in SIAB to change that would explain or fix this behavior),
I'm assuming that something in PAM has changed, or the way PAM is invoked has changed, but what?
Any thoughts here?
Statistics: Posted by MARKPR — Sun Nov 23, 2025 4:51 am — Replies 0 — Views 43