doktor5000 wrote:Hmmm, that is interesting, I'll try to reproduce.
That issue is on an uptodate mga7 system, and sshd_config is also pretty default ?
The issue appears to be related to the date of an update so I presume the update is responsible.
sshd_config is not default; it is old and has evolved over time as required. I last changed it in November as I was updating my config to disallow DSA authentication and to allow rsa, ecdsa, and ed25519 keys. No other changes in a long time, and logging worked for awhile after this change.
I had to reboot the system this morning. I was hoping that the reboot would return my logging, but no joy.
One difference I spotted is my account section is different then yours in /etc/pam.d/system-auth - you only have pam_deny there.
[doktor5000@Mageia7VM ~]$ sudo cat /etc/pam.d/system-auth
#%PAM-1.0
auth required pam_env.so
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
account required pam_unix.so
password required pam_cracklib.so try_first_pass retry=3 minlen=4 dcredit=0 ucredit=0
password sufficient pam_unix.so try_first_pass use_authtok nullok sha512 shadow
password required pam_deny.so
session optional pam_keyinit.so revoke
session required pam_limits.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
-session optional pam_systemd.so
session required pam_unix.so
There is a file in my /etc/pam.d directory titled system-auth.rpmnew and when I diff it with the running system-auth file, I see that it matches yours. It could be that some systemd update has made the newer configuration mandatory. So I have swapped the files so that the rpmnew file is in use, restarted saslauthd, and I will see what happens.