SSH authentication problems

[dictum9]

Help me solve this riddle,

I try to ssh from source to target. Source is a Solaris 10 box running Sun_SSH_1.1, SSH protocols 1.5/2.0, target machine is hpux 11.0 running OpenSSH_3.0p1, SSH protocols 1.5/2.0

After trying to authenticate, it just closes the connection:

ssh -v -v -v target

debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /.ssh/identity
debug3: no such identity: /.ssh/identity
debug1: Trying private key: /.ssh/id_rsa
debug3: no such identity: /.ssh/id_rsa
debug1: Trying public key: /.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
Connection closed by target
debug1: Calling cleanup 0x34204(0x0)

I haven't tried to exchange the public keys, I don't really want to do that,

Interestingly, /opt/ssh directory doesn't even exist, and there is no ssdh_config file anywhere on the system. Should I create it, and why is it absent?

However, the really interesting thing is I can ssh to that machine from another hp-ux machine running 11.23 and OpenSSH 4.2.
So it seems the target doesn't like that particular Sun box, why is that? Incompatible ssh versions?

[Steven E. Protter · Accepted solution]

Shalom,

You might find that having two versions closer to each other will help. Openssh 4.2 was very flawed on HP-UX and may require and upgrade. This could be the entire problem.

To operate properly openssh MUST have an sshd_config file. Copy one from a normal working system, restart the daemon and try again.

SEP

[Pupil_1]

it could be that /opt/ssh might not be the default installation path in Solaris 10.

i guess, inetadm is the command that you will have to use to restart sshd in Solaris 10

[dictum9]

OpenSSH 4.2 is not involved, only
Sun_SSH_1.1 ----> OpenSSH_3.0p1

[IT_2007]

you need to make sure that sshd is configured on Sun solaris since you are initiating ssh from it.

Also you can try to login locally using ssh whether you can login or not.

$ssh -vvv localhost

[dictum9]

No no no. I have _no_ problems ssh'ing from this Sun box anywhere else _except_ for this particular HP machihe which doesn't like this particular Sun box.

Fact 1: I can ssh to this HP from any other machine except for Sun

Fact 2: I can ssh from Sun to any other machine except for that HP

They both work with other machines except they cannot talk to each other, what does that mean, version incompatibility?

Should I upgrade the ssh which came on Sun with OpenSSH??

[IT_2007]

Fact 1: I can ssh to this HP from any other machine except for Sun

Fact 2: I can ssh from Sun to any other machine except for that HP

They both work with other machines except they cannot talk to each other, what does that mean, version incompatibility?

Should I upgrade the ssh which came on Sun with OpenSSH??
================================
Then definitely you have version incompatibility. You need to upgrade ssh on HP so that you can talk to Sun Solaris server using ssh.

[Arunvijai_4]

Hi ETC,

It is always better to run 4.x when it comes to OpenSSH. It doesn't matter to be a Sun or HP.

-Arun

[dictum9]

Where can I get 4.2 so I can swinstall it?

I presume I can save the .ssh directory and then just put it back so I don't have to regenerate the keys? I am not sure at this point if the old keys are needed.

[dictum9]

OK, I understand a global install will not affect indivial .ssh directories.. still the question about key compatibility remains.

[Arunvijai_4]

Hi ETC,

For HP-UX, http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA

For Solaris

http://www.sunfreeware.com/

-Arun