From owner-freebsd-questions@FreeBSD.ORG Thu Aug 30 17:08:20 2007 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 08FC616A417 for ; Thu, 30 Aug 2007 17:08:20 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from crackmonkey.us (crackmonkey.us [70.58.166.197]) by mx1.freebsd.org (Postfix) with ESMTP id D252C13C4A5 for ; Thu, 30 Aug 2007 17:08:19 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from tarani-bosatsu.dreamtrack.dnsalias.com (cpc1-swin7-0-0-cust216.brhm.cable.ntl.com [::ffff:86.18.88.217]) (AUTH: PLAIN fatman, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by crackmonkey.us with esmtp; Thu, 30 Aug 2007 11:08:07 -0600 id 0018800B.46D6F97C.00000F93 Message-ID: <46D6F8D8.7000901@crackmonkey.us> Date: Thu, 30 Aug 2007 18:05:28 +0100 From: Adam J Richardson User-Agent: Thunderbird 2.0.0.6 (X11/20070830) MIME-Version: 1.0 To: Laszlo Nagy References: <46D6EAB4.5060501@shopzeus.com> <46D6ECEA.5090107@crackmonkey.us> <46D6F712.8070905@shopzeus.com> In-Reply-To: <46D6F712.8070905@shopzeus.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: ssh2 login with public key - not working 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: Thu, 30 Aug 2007 17:08:20 -0000 Laszlo Nagy wrote: > Well, I have other users using public keys for logging in so the sshd > config must be correct. > This is the only user that doesn't work. I can login by typing in the > password but I need to login automatically. > > Best, > > Laszlo Well, then perhaps the user is wrongly configured. IIRC, you need to have the file ~/.ssh/authorized_users with your public key in it, so sshd can match it to the private key when you log in. If the file's there on the server, perhaps the client end is misconfigured. Apparently there's no way to feed the key to SSH via command line, you have to be using some sort of key agent. Which is highly annoying IMO, but then you can always use PuTTY instead of ssh. HtH, Adam J Richardson