I would like to disable or change the MOTD shown on SSH login on a per-group/per-user basis. This question on SuperUser has an answer stating that I can use Match
blocks in sshd_config
. However, man sshd_config
states:
Match
...
Only a subset of keywords may be used on the lines following a
Match keyword. Available keywords are AcceptEnv,
AllowAgentForwarding, AllowGroups, AllowTcpForwarding,
AllowUsers, AuthenticationMethods, AuthorizedKeysCommand,
AuthorizedKeysCommandUser, AuthorizedKeysFile,
AuthorizedPrincipalsFile, Banner, ChrootDirectory, DenyGroups,
DenyUsers, ForceCommand, GatewayPorts, GSSAPIAuthentication,
HostbasedAuthentication, HostbasedUsesNameFromPacketOnly,
KbdInteractiveAuthentication, KerberosAuthentication,
MaxAuthTries, MaxSessions, PasswordAuthentication,
PermitEmptyPasswords, PermitOpen, PermitRootLogin, PermitTTY,
PermitTunnel, PubkeyAuthentication, RekeyLimit,
RhostsRSAAuthentication, RSAAuthentication, X11DisplayOffset,
X11Forwarding and X11UseLocalHost.
And I can't see anything related to MOTD in that list. And indeed, trying to use that suggestion causes sshd
to fail to start because of incorrect configuration.
So, can I do this? If so, how? From the SSH configuration or by altering whatever generates/prints the MOTD?
Altering files in /etc/update-motd.d
isn't useful, since, according to man update-motd
:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8)
as the root user at each login, and this information is concatenated in
/var/run/motd.
(I tested this out with a script that did echo $USER
. I got a root
in my MOTD.)
That leaves PAM configuration. I imagine it might be possible to disable pam_motd
on a per-group/user basis, but I am not sure how to do it. The last option would be to disable pam_motd
altogether, and use pam_exec
, but I really hope it doesn't come to that.
Match
directive withPrintMotd
. Another approach could be define your own script with custom user/group output in/etc/update-motd.d
, did you consider this?11-custom
script and disable some of the others.HUSHLOGIN_FILE
directive in/etc/login.defs
?session optional pam_exec.so seteuid /path/to/script
in this context I guess PAM_USER variable value should be right.