SSH Experts

[Chrisl_2]

Hi all. On my hp systems, I have created passwordless ssh logins thru the following simple procedure.
1. have the remote user generate keys:
ssh-keygen -t rsa
this creates id_rsa and id_rsa.pub files
2. copy id_rsa.pub to my box
3. add id_rsa.pub to my authorized_keys file
done - works great
Problem - on a remote SUN I have the user run
ssh-keygen -t rsa. It creates id_rsa_2048_a and id_rsa_2048_a.pub. I copy the pub key over to my box and add it to authorized_keys. I can't connect. The format of the public key is different in that is actually looks like it is contained in an email. Should I edit the key in authorized_keys to make it look format wise like the HP generated keys?

TIA

[Florian Heigl (new acc)]

No,

first of all check both SSH keys are version2 ssh keys - then and only then they should look the same and be compatible.

I had the very same issue on my Tru64 box which still used SSHv1 - I wouldn't even have noticed without the issues. :)

[Chrisl_2]

according to man ssh-keygen the -t rsa generates a version 2 protocol.

[Peter Nikitka]

Hi,

generally it would help if you tell the OS-versions of HPs and SUNs.

You can get more and more verbose output when doing
ssh -v host
ssh -vv host
ssh -vvv host

This should give sufficent output to analyze the problem.

mfG Peter

[Chrisl_2]

ok, I figured this out. The commercial ssh and openssh generate the public key in different formats. To change formats, run ssh-keygen -i -f >> authorized_keys. Normally, you would just cat pubkey >>authorized_keys.

chris

[Chrisl_2]

see thread