From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Sep 5 15:40:06 2008 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96A791065691 for ; Fri, 5 Sep 2008 15:40:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 864398FC15 for ; Fri, 5 Sep 2008 15:40:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m85Fe6SH090128 for ; Fri, 5 Sep 2008 15:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m85Fe6js090127; Fri, 5 Sep 2008 15:40:06 GMT (envelope-from gnats) Date: Fri, 5 Sep 2008 15:40:06 GMT Message-Id: <200809051540.m85Fe6js090127@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Michael Cc: Subject: Re: ports/126867: security/sshguard-pf 1.1 fails to detect attempted logins X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michael List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 15:40:06 -0000 The following reply was made to PR ports/126867; it has been noted by GNATS. From: Michael To: Mij Cc: bug-followup@FreeBSD.org Subject: Re: ports/126867: security/sshguard-pf 1.1 fails to detect attempted logins Date: Fri, 05 Sep 2008 17:08:50 +0200 Plain vanilla standard FreeBSD install (6.3-RELEASE and 7.0-RELEASE). There is no more context, the system logs only a single line: Sep 5 17:06:17 server sshd[71127]: error: PAM: authentication error for xyz from 10.1.1.1 This is basically what sshguard 1.0 was looking for. What's your uname -a? Also, by the way, because there is only one line of log, as a bonus syslogd agregates the error messages (last line repeated n times) which is something sshguard also doesn't handle. Mij wrote: > The PAM log entry you report follows a failed login attempt, but in turn > should be followed by > SSHD's own log entry, that looks like > > Sep 4 20:25:46 voodoo sshd[19972]: Failed keyboard-interactive/pam for > invalid user usrn from 1.2.3.4 port 51196 ssh2 > > this latter is what sshguard is sensitive to. > If you examine the context around that line in your auth.log, what does > it look like?