From owner-freebsd-current@FreeBSD.ORG Thu Mar 31 02:40:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66B6116A4CE for ; Thu, 31 Mar 2005 02:40:56 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CABD43D2F for ; Thu, 31 Mar 2005 02:40:56 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 344FA72DDD; Wed, 30 Mar 2005 18:40:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2F6F672DD9; Wed, 30 Mar 2005 18:40:56 -0800 (PST) Date: Wed, 30 Mar 2005 18:40:56 -0800 (PST) From: Doug White To: Mike Jakubik In-Reply-To: <3971.172.16.0.199.1112209024.squirrel@wettoast.dyndns.org> Message-ID: <20050330183953.U68982@carver.gumbysoft.com> References: <3971.172.16.0.199.1112209024.squirrel@wettoast.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: weird ssh errors in security run X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 02:40:56 -0000 On Wed, 30 Mar 2005, Mike Jakubik wrote: > Hello, > > This is what i found in my daily security run: > > --- > login failures: > Mar 29 00:10:04 fbsd sshd[96361]: fatal: stat(/dev/#C:223:0x0) failed: No > such file > or directory > Mar 29 00:10:04 fbsd sshd[96361]: error: chown /dev/#C:223:0x0 0 0 failed: > No such > file or directory > Mar 29 00:10:04 fbsd sshd[96361]: error: chmod /dev/#C:223:0x0 0666 > failed: No such > file or directory > Mar 29 00:10:55 fbsd login: 5 LOGIN FAILURES ON #C:232:0x0 > Mar 29 00:10:55 fbsd login: 5 LOGIN FAILURES ON #C:232:0x0, root > --- > > 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Mon Mar 28 23:53:00 EST 2005 you need to rebuild ssh, which should be happening if you are following the instructions on how to build -current from src/UPDATING. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org