cancel
Showing results for 
Search instead for 
Did you mean: 

ssh to ssh2

Cara Rollins
Advisor

ssh to ssh2

i am setting up an ssh connection between two servers. server a has ssh - server b has ssh2. i have set up the authorized keys for both servers, but server b, running ssh cannot connect to server a running ssh2. Although, server a can connect to server b. Does anyone know what the issue may be? I have already combed through the ssd.conf files.
Happiness lies in the joy of acheivement and the thrill of creative effort.
6 REPLIES
Steven Schweda
Honored Contributor

Re: ssh to ssh2

Have you tried "ssh -v"?

OS and/or ssh versions on these systems? The
key file formats on Solaris may be different,
for example.
Cara Rollins
Advisor

Re: ssh to ssh2

Here is the debug output. I've removed any server specific info such home directories, IP and server names.


OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data /usr/local/etc/ssh_config
debug1: Connecting to SERVER1[IP] port 22.
debug1: Connection established.
debug1: identity file /path/.ssh/id_rsa type 1
debug1: identity file /path/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version 3.2.0 SSH Secure Shell Tru64 UNIX
debug1: no match: 3.2.0 SSH Secure Shell Tru64 UNIX
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'server' is known and matches the DSA host key.
debug1: Found key in /path/.ssh/known_hosts:15
debug1: ssh_dss_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: hostbased,publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /path/.ssh/id_rsa
debug1: Authentications that can continue: hostbased,publickey,password
debug1: Trying private key: /path/.ssh/id_dsa
debug1: Next authentication method: password
Happiness lies in the joy of acheivement and the thrill of creative effort.
Cara Rollins
Advisor

Re: ssh to ssh2

I am sshing from version
OpenSSH_3.8.1p1, OpenSSL 0.9.7d

to version
OpenSSH_4.2p1, OpenSSL 0.9.7d
Happiness lies in the joy of acheivement and the thrill of creative effort.
Cara Rollins
Advisor

Re: ssh to ssh2

Also, they are both TRU64 5.1 (not A or B)
Happiness lies in the joy of acheivement and the thrill of creative effort.
Steven Schweda
Honored Contributor

Re: ssh to ssh2

I don't have any OpenSSH installed here
(Tru64 V5.1B, "ssh -V" says "ssh: SSH Secure
Shell Tru64 UNIX 3.2.0"), but it looks as if
the keys are being rejected.

Did you make the key files on one system and
copy them to the other?

If you make key files on the system where
you didn't do it before, do their formats
look like the first ones?

Compare with the "-v" output going the other
way?

Wait for helpful advice from someone who
actually knows something?
Kasper Hedensted
Trusted Contributor

Re: ssh to ssh2

Hi,

It seems like you are running Tru64 SSH2 on one server
(...remote software version 3.2.0 SSH Secure Shell Tru64 UNIX...)

Do you have installed OpenSSH on both servers ?

If so can you try and use the OpenSSH's "ssh" command to connect from one system to the other ?

The command might be located here "/usr/local/bin/ssh"

Otherwise if you want to use Tru64 SSH2 "ssh" command you may need to set your ~/.ssh2/identification with the correct private key like this "IdKey name-of-your-private-key" and put your private key in ~/.ssh2

Cheers,
Kasper