Date: Fri, 10 Jun 2022 17:20:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264599] blacklistd: message too short/no message errors Message-ID: <bug-264599-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264599 Bug ID: 264599 Summary: blacklistd: message too short/no message errors Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: jlduran@gmail.com After upgrading a public-facing SSH server, error messages have started to = spam dmesg logs: blacklistd: message too short 144 blacklistd: no message (No such file or directory) Filing this as a bug to track it. In the meantime, I have done this horrible thing: --- crypto/openssh/auth.c +++ crypto/openssh/auth.c @@ -555,7 +555,7 @@ getpwnamallow(struct ssh *ssh, const char *user) aix_restoreauthdb(); #endif if (pw =3D=3D NULL) { - BLACKLIST_NOTIFY(ssh, BLACKLIST_BAD_USER, user); + BLACKLIST_NOTIFY(ssh, BLACKLIST_BAD_USER, "user"); logit("Invalid user %.100s from %.100s port %d", user, ssh_remote_ipaddr(ssh), ssh_remote_port(ssh)); #ifdef CUSTOM_FAILED_LOGIN --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264599-227>