From owner-freebsd-bugs@freebsd.org  Thu Jun 23 01:41:29 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 140E6B72789
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 23 Jun 2016 01:41:29 +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 03FF11AFC
 for <freebsd-bugs@FreeBSD.org>; Thu, 23 Jun 2016 01:41:29 +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 u5N1fSTH092966
 for <freebsd-bugs@FreeBSD.org>; Thu, 23 Jun 2016 01:41:28 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 01:41:29 +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: <bug-210479-8-lYknhTPtt4@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 01:41:29 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210479

--- Comment #3 from Glen Barber <gjb@FreeBSD.org> ---
(In reply to lidl from comment #2)
> The debug logging is expected.
>=20

I think this makes auditdistd(8) unhappy.

> I'm unclear by your comment about delays - delays due to the error state,=
 or
> delay due to the extra syslog statements.
>=20
> In timing of a simple 'ssh hostname df \> /dev/null', I get the same
> wall-clock time, regardless of blacklistd running on the remote host.
> (I do see the debug messages in the debug.log on the remote host.)
>=20
> Can you quantify the delays you're seeing?

Between head and stable/10, I see an increase in responsiveness.
 gjb@nucleus:~ % time ssh ref10-amd64.freebsd.org exit
 0.010u 0.010s 0:01.14 1.7%      192+148k 4+0io 0pf+0w

 gjb@nucleus:~ % time ssh ref11-amd64.freebsd.org exit
 0.020u 0.000s 0:01.55 1.2%      96+74k 4+1io 0pf+0w

The only "known" difference is the addition of blacklistd(8).

In either case, I think the debug.log spam is a bit overkill, especially for
machines without large /var directories (embedded systems, etc.).

--=20
You are receiving this mail because:
You are the assignee for the bug.=