From nobody Thu Jan 25 08:49:52 2024 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TLDzP5bcGz586FM for ; Thu, 25 Jan 2024 08:49:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TLDzP48phz47gL for ; Thu, 25 Jan 2024 08:49:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1706172593; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=U9/ak1IwPWj6dTBQI2NfX0PZpE9j2a963StTRCjTYIM=; b=hAmkpoZinWhmYjcPXCjW0nCNGlEjVY12KyDZOfaKWJA7z/uZqggN1NbPupjg3nvMsNJfGR 7K3HswhfiNKBtss8HV4RAdY6yNex4ZQ094dlPlNNOF8c9wi3oe0g5zZb09R40S/Z5bUmwC 8wSpF1EFEMN77/e8QsHx4jTXIY15qZG94MrDsfyDAtE7LJ9hit450lKm8vqSSFaAX+Sygk OXHvcsZq80GWTqyconeFANX5ZSZlD9b9dMpRQlCC8ezP4JnEKQvh/+d9mUpX0ulbtehqmN ar+FXC58f+JSQskHdbNmUzJ7yLx7Ax8N2X25fQ88O654FpKoivaOXD6Ky/hR4A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1706172593; a=rsa-sha256; cv=none; b=j1B6ZO0GSCTZaKPLTceq5wH2iz/fKmkmfG6eiGCiyRi524ftXtTra/tqpCw9f/yfOKhvYl kx+DiUyM5sQJeDdDEeQA6J1UFkxoCg6VyLaAtddIWnnXygWmoXORXVep+57u0AYIMPz4vu oKJD/AtvnHL8fNAokWrJyCJaO4wTppTYKuicDNxbqG6bk03dnTgZoSqrwusVz1pUu2NG2n Y7tKMeL+VdV26fHF6E36vQX3jcW/oy3z7wyBZ89Byo5Hghe4LY5PXGfAJtUeAjxwJ9gZ0j adAp0oHLLj1UuQ2NocTQv7cqtgJQf4WCmMtwVcCfMW06UBRHxt3jSED4my7upA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4TLDzP3DZRzrZX for ; Thu, 25 Jan 2024 08:49:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 40P8nred065720 for ; Thu, 25 Jan 2024 08:49:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 40P8nrlX065718 for bugs@FreeBSD.org; Thu, 25 Jan 2024 08:49:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270928] Blacklistd does not handle SSHD failed logins Date: Thu, 25 Jan 2024 08:49:52 +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: 13.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bc979@lafn.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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 List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270928 --- Comment #4 from bc979@lafn.org --- I find this quite strange. A test tonight using FBSD 14 shows that a bad s= sh login does get blocked. However, I can find no change anywhere in the code that would have fixed the issue. bug #26459 precedes my original report.= =20 Blacklistd.c still shows that BL_BADUSER is ignored. I can't find any chan= ge to sshd. It still appears to issue BL_BADUSER. The only difference in my testing is that currently I have passwords disabl= ed.=20 Only publickey authentication is used. Passwords were used at the time the= PR was filed. --=20 You are receiving this mail because: You are the assignee for the bug.=