From owner-freebsd-questions@FreeBSD.ORG Sat Jun 14 18:15:53 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 739481065676 for ; Sat, 14 Jun 2008 18:15:53 +0000 (UTC) (envelope-from prad@towardsfreedom.com) Received: from pd2mo3so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7EE8FC14 for ; Sat, 14 Jun 2008 18:15:53 +0000 (UTC) (envelope-from prad@towardsfreedom.com) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K2G0048ITE1GGE0@l-daemon> for freebsd-questions@freebsd.org; Sat, 14 Jun 2008 12:15:37 -0600 (MDT) Received: from pn2ml2so.prod.shaw.ca ([10.0.121.146]) by pd3mr2so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K2G0086TTE16520@pd3mr2so.prod.shaw.ca> for freebsd-questions@freebsd.org; Sat, 14 Jun 2008 12:15:37 -0600 (MDT) Received: from gom.home ([70.67.160.176]) by l-daemon (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K2G002CETDZMW00@l-daemon> for freebsd-questions@freebsd.org; Sat, 14 Jun 2008 12:15:37 -0600 (MDT) Received: from gom.home (localhost [127.0.0.1]) by gom.home (Postfix) with ESMTP id 559C4B839 for ; Sat, 14 Jun 2008 11:15:28 -0700 (PDT) Date: Sat, 14 Jun 2008 11:15:28 -0700 From: prad In-reply-to: <200806141802.m5EI27GF020260@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Message-id: <20080614111528.5ac7f765@gom.home> MIME-version: 1.0 X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit References: <200806141802.m5EI27GF020260@dc.cis.okstate.edu> Subject: Re: ssh Public Keys Suddenly Stopped working for one account. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2008 18:15:53 -0000 On Sat, 14 Jun 2008 13:02:07 -0500 Martin McCormick wrote: > All other accounts on this same system with public keys > from their remote partners still work fine. > > The ownership and permissions look right on the account > directory. > how about on the client computer? for instance, id_rsa is supposed to be 600. the ownership should be set for the account on .ssh and authorized_keys. > Does this sound familiar and what else am I missing? > we had only one problem getting a mac to log in which was strange. the client generated the id_rsa.pub and id_rsa keys. it wouldn't work - and apparently all the permissions were set correctly at both ends. so we did the whole thing from scratch again - and this time it worked. conclusion: the system is picky about the rsa key. :D :D -- In friendship, prad ... with you on your journey Towards Freedom http://www.towardsfreedom.com (website) Information, Inspiration, Imagination - truly a site for soaring I's