From owner-freebsd-security Tue Aug 28 18:45: 5 2001 Delivered-To: freebsd-security@freebsd.org Received: from rfnj.org (rfnj.org [216.239.237.194]) by hub.freebsd.org (Postfix) with ESMTP id E424D37B41A for ; Tue, 28 Aug 2001 18:44:44 -0700 (PDT) (envelope-from all@biosys.net) Received: from megalomaniac.biosys.net (megalomaniac.rfnj.org [216.239.237.200]) by rfnj.org (Postfix) with ESMTP id D187A1385C; Tue, 28 Aug 2001 21:44:34 +0000 (GMT) Message-Id: <5.1.0.14.0.20010828214142.00c4af38@rfnj.org> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 28 Aug 2001 21:44:40 -0400 To: Peter Pentchev From: Allen Landsidel Subject: Re: [OT] ssh client Cc: freebsd-security@freebsd.org In-Reply-To: <20010828174726.A568@ringworld.oblivion.bg> References: <001f01c12fc6$4c975220$0901a8c0@system> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 17:47 8/28/2001 +0300, you wrote: >..and does it understand OpenSSH's DSA keys? >Last I checked it did not.. This may be news to you but OpenSSH is the weirdo here, which is why few if any other clients support it. It uses it's own key format, not the SSH2 format. Just do the following to convert your OpenSSH key to a SSH2 key for use on normal, standard clients: ssh-keygen -xf openssh.format.key > ssh2.format.key Your file names will of course vary. About five minutes searching google and another 30 seconds reading the ssh-keygen manpage could have saved a lot of frustration and wasted time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message