So, SSHD couldn't leave well enough alone, so now we have a new "sshd-session" line in AUTH instead of just "sshd". So Fail2ban doesn't see it at all. So of course your daily security reports are full of failed logins again.
Good news, you can fix it, grab this file from github: https://raw.githubusercontent.com/fail2ban/fail2ban/refs/heads/master/config/filter.d/sshd.conf
Stick that in the /usr/local/etc/fail2ban/filter.d folder and go on with your day.
Not using Fail2ban, okay, ignore this.
(please don't take just my word for all this, your server is your responsibility) (but this does fix this silly issue)
Good news, you can fix it, grab this file from github: https://raw.githubusercontent.com/fail2ban/fail2ban/refs/heads/master/config/filter.d/sshd.conf
Stick that in the /usr/local/etc/fail2ban/filter.d folder and go on with your day.
Not using Fail2ban, okay, ignore this.
(please don't take just my word for all this, your server is your responsibility) (but this does fix this silly issue)