Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Feb 2001 17:43:39 +0200
From:      Peter Pentchev <roam@orbitel.bg>
To:        security@FreeBSD.org
Subject:   [OT] ssh.com SSH 2.0.13 - OpenSSH interoperability problem
Message-ID:  <20010222174339.F440@ringworld.oblivion.bg>

next in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010222174339.F440>