From owner-freebsd-security Mon Jan 8 16:33:29 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.interactivate.com (unknown [63.141.73.15]) by hub.freebsd.org (Postfix) with ESMTP id 8768A37B401 for ; Mon, 8 Jan 2001 16:33:09 -0800 (PST) Received: from interactivate.com ([63.141.73.10]) by mail.interactivate.com (8.11.1/8.11.1) with ESMTP id f090sgg92382; Mon, 8 Jan 2001 16:54:42 -0800 (PST) (envelope-from larry@interactivate.com) Message-ID: <3A5A5B85.183EE454@interactivate.com> Date: Mon, 08 Jan 2001 16:29:57 -0800 From: Lawrence Sica Organization: Interactivate, Inc X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Scott Reber Cc: freebsd-security@FreeBSD.ORG Subject: Re: ssh config assistance References: <4.3.2.7.2.20010108173133.00aeb380@netdepot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Scott Reber wrote: > > If this should be posted to questions instead, I apologize in advance. > > I am setting up my first FreeBSD 4.2R box. I am trying, with no success, > to connect using ssh via a Windows F-Secure client using public keys. I am > able to use ssh2 with a password, but not public key. This same client has > been used in the past to access several boxes that were already set up and > using ssh1 with public key. > > While I have read man sshd, man ssh_keygen and checked out openssh.org. I > think I followed the instructions, but I am still unable to make this work. > > I am running 4.2R clean out of the box. I've tried creating > ~/.ssh/authorized_keys2 and copying the clients' public key into it > but to no avail. > it should be in the authorized_keys file not authorized_keys2. also make sure the host is known to the box, if the host is unknown it will not work as strict checking is on by default if i recall. look in the ~/.ssh/known_hosts file for the host. --Larry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message