NetBSD Problem Report #58368

From www@netbsd.org  Tue Jun 25 13:20:14 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 991BE1A923A
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 25 Jun 2024 13:20:14 +0000 (UTC)
Message-Id: <20240625132013.BB8F21A923C@mollari.NetBSD.org>
Date: Tue, 25 Jun 2024 13:20:13 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: sshd blocklistd integration doesn't make blocking reasons clear
X-Send-Pr-Version: www-1.0

>Number:         58368
>Category:       bin
>Synopsis:       sshd blocklistd integration doesn't make blocking reasons clear
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 25 13:25:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10, 9
>Organization:
The NetBSD FoundConnection timed out
>Environment:
>Description:
When sshd decides to ask blocklistd to consider blocking an address, it should be associated with a clear log message saying what happened that led it to this decision.

But it's not -- the paths to pfilter_notify in sshd, where it calls into blocklistd, are not clearly associated with log messages that can be diagnosed.
>How-To-Repeat:
pore over /var/log/authlog trying to find why a legitimate user keeps getting blocked
>Fix:
Make sure there is a clear log message near every call to pfilter_notify.

Home	PR Database Search