From owner-freebsd-bugs@freebsd.org  Thu Jun 23 02:05:54 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 8C5DCB72EED
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 23 Jun 2016 02:05:54 +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 7C69228D9
 for <freebsd-bugs@FreeBSD.org>; Thu, 23 Jun 2016 02:05:54 +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 u5N25snt085216
 for <freebsd-bugs@FreeBSD.org>; Thu, 23 Jun 2016 02:05:54 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:05:54 +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: lidl@pix.net
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: <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/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2016 02:05:54 -0000

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.=