Date: Thu, 23 Jun 2016 02:05:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210479] blacklistd(8) and sshd(8) causes login delays and syslog(8) spam Message-ID: <bug-210479-8-k1iARzhqBI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210479-8@https.bugs.freebsd.org/bugzilla/> References: <bug-210479-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210479 --- Comment #9 from lidl@pix.net --- (In reply to Glen Barber from comment #6) How is sshd supposed to know that blacklistd is enabled but not functioning properly? I suppose I could make the bl_init() code in the blacklist library stat() t= he pidfile for the blacklistd daemon, and if not found, not log the message...= =20 But that's pretty fragile and would break if someone moves the pidfile to a different location... The other, much more intrusive, thing would be to add another flag to sshd = (and the other daemons) to specify that blacklist signaling should be used (and = only complain in that configuration, if the connection to the daemon fails). --=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-210479-8-k1iARzhqBI>