From owner-freebsd-questions@FreeBSD.ORG Sun Nov 21 00:54:39 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB5DB16A4CE for ; Sun, 21 Nov 2004 00:54:39 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1BD43D2D for ; Sun, 21 Nov 2004 00:54:39 +0000 (GMT) (envelope-from georgiev@vt.edu) Received: from bburg.bg ([151.199.126.93]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041121005438.YBAG4719.out006.verizon.net@bburg.bg>; Sat, 20 Nov 2004 18:54:38 -0600 From: Ivan Georgiev To: Rob Date: Sat, 20 Nov 2004 19:54:37 -0500 User-Agent: KMail/1.7.1 References: <200411201921.27880.georgiev@vt.edu> <419FE682.6050807@yahoo.com> In-Reply-To: <419FE682.6050807@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411201954.37691.georgiev@vt.edu> X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [151.199.126.93] at Sat, 20 Nov 2004 18:54:38 -0600 cc: FreeBSD Subject: Re: NEW: cannot ssh to my computer X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 00:54:40 -0000 On Saturday 20 November 2004 07:51 pm, Rob wrote: > Ivan Georgiev wrote: > > Hello, > > > > Please excuse my re-posting of the same problem but, simply, I have no > > clue how to fix my account. Below you can see the previous postings. What > > puzzles me is that if I create a new user this user can connect trough > > ssh with no problems. Only my account is rejected. > > As far as I know, ssh stores the user's ssh files in ~/.ssh/. > How about moving this .ssh out of the way by "mv .ssh ssh_copy" > and try again? If that solves your problem, you should inspect > the files in that ssh directory. > > Rob. I already did that, i.e. removed my ~/.ssh directory and tried again. Unfortunately this didn't solve the problem. Ivan