SSH remote client question

My default Suse 8.2 is using OpenSSH. I am generating ssh2 key pairs. Does it matter what the remote server I am trying to connect to is running or can I place my public keys into any server side version? Reason I ask, is the remote server I am trying to connect to is running SSH 3.2.x (is what I get after running ssh -V) and nothing I do seems to get me past typing in passwords

I can log in just fine using username and password, but would like to get this key pair setup so password is not needed

TIA

There has been a flaw in the openssl library for quite some time (at least enough time so some big vendors used it for their ssh servers). It didn´t permit ssh2 keys that use rsa2 encryption. This was my recent problem with rh7.3 and the last security updates. I changed to "blowfish" encryption instead and it worked like a charm. [source: putty documentation]

You can only use ssh2 keys with a server that supports ssh2 protocol. But even if supported, it can be disabled too. (Usually you disable ssh1, not v2, so this should not apply)

Did you check if the server allows pk auth at all? This has to be enabled in /etc/ssh/sshd_config (or where ever your os distributor put your config files)

Also, the key has to be in the format that this server expects. If the server is running the (commercial) SSH, you need to find a program that converts between OpenSSH and SSH key format. (it should come with either of them. if not, search and download "puttygen")

[edit]
Another idea: sometimes the file has to be called "~/.ssh/authorized_keys2" for ssh2 keys...
[/edit]

Hmm good idea I need to look at the remote server for that. I know my client and the remote server supports .ssh2, its probably something in the config files. We use -t dsa as well so rsa is not an issue. See what happens on my Suse box I run ssh-keygen -b 1024 -t dsa, and it generates the pk and places into ~/.ssh, while normally .ssh has meant ssh or ssh1 in the past I know for sure its a ssh2 pk because of the content of the key files. So on the remote server I have tried both ~/.ssh2/authorization and ~/.ssh/authorized_key and _key2a with no luck. Really odd.

I think it´s authorized_keys (plural because you can concatenate several keys in it)