From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Sep 6 10:10:04 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 4F8351065680 for ; Sat, 6 Sep 2008 10:10:04 +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 44A3D8FC1A for ; Sat, 6 Sep 2008 10:10:04 +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 m86AA3dh021674 for ; Sat, 6 Sep 2008 10:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m86AA3YL021673; Sat, 6 Sep 2008 10:10:03 GMT (envelope-from gnats) Date: Sat, 6 Sep 2008 10:10:03 GMT Message-Id: <200809061010.m86AA3YL021673@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: Sat, 06 Sep 2008 10:10:04 -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: Sat, 06 Sep 2008 12:04:11 +0200 No, I'm talking about auth.log. Seriously. What about trying it on your own on a fresh install? Mij wrote: > > On 5 Sep 2008, at 17:08, Michael wrote: > >> 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. > > The fact you say there is only a single line and "the system logs" make > me think you're considering /var/log/messages, > there authentication messages do not appear. What about > /var/log/auth.log (or any other destination you set for auth.info)? > > >> >> >> 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? >> >