From owner-freebsd-bugs@freebsd.org Thu Jun 23 02:10:51 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4680CB72FEE for ; Thu, 23 Jun 2016 02:10:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3694A29BB for ; Thu, 23 Jun 2016 02:10:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5N2AoGV009056 for ; Thu, 23 Jun 2016 02:10:51 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Thu, 23 Jun 2016 02:10:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: gjb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2016 02:10:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210479 --- Comment #10 from Glen Barber --- (In reply to lidl from comment #9) > (In reply to Glen Barber from comment #6) >=20 > How is sshd supposed to know that blacklistd is enabled but not functioni= ng > properly? >=20 This is why I added DES (and wanted to add you) to the PR. :-) I honestly don't know the answer. I'm still trying to gather more information, in any case. > I suppose I could make the bl_init() code in the blacklist library stat() > the pidfile for the blacklistd daemon, and if not found, not log the > message... But that's pretty fragile and would break if someone moves the > pidfile to a different location... >=20 Agreed on the fragile nature of this. I think this is not a "critical" thi= ng to worry about for 11.0-RELEASE, but it was something I observed as of rece= nt. > 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). I think this is far too intrusive, to be honest. --=20 You are receiving this mail because: You are the assignee for the bug.=