From owner-freebsd-security Thu Feb 22 7:45:49 2001 Delivered-To: freebsd-security@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id EFD5C37B699 for ; Thu, 22 Feb 2001 07:45:37 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 6265 invoked by uid 1000); 22 Feb 2001 15:43:39 -0000 Date: Thu, 22 Feb 2001 17:43:39 +0200 From: Peter Pentchev To: security@FreeBSD.org Subject: [OT] ssh.com SSH 2.0.13 - OpenSSH interoperability problem Message-ID: <20010222174339.F440@ringworld.oblivion.bg> Mail-Followup-To: security@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, so I'll admit that I might not have been RTFM'ing enough, but.. Are OpenSSH and ssh.com's SSH DSA public keys compatible? I have a public key, generated by OpenSSH's ssh-keygen -d, and it works fine when connecting to an OpenSSH server. However, with an ssh.com's SSH server, I have the following in my ~/.ssh2/authorization file: Key /home/roam/.ssh/authorized_keys2 ..and /home/roam/.ssh/authorized_keys2 is the public portion of the key (one line, starting with ssh-dss, ending with roam@ringworld.oblivion.bg) And yet.. debug: authentications that can continue: publickey,password debug: next auth method to try is publickey debug: try pubkey: /usr/home/roam/.ssh/id_dsa debug: read DSA private key done debug: sig size 20 20 debug: datafellows debug: we sent a publickey packet, wait for reply debug: authentications that can continue: publickey,password ..and it asks me for a password. Is there something more I need to do? G'luck, Peter -- This would easier understand fewer had omitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message