Pete Harlan wrote:
When you say the work machine has ssh and ssh2 installed, do you mean
openssh version 2 and non-free ssh2, or is the ssh something else?
In any case, the nonfree ssh2 uses a different format for the dsa keys
than the openssh version does, so you can't just blindly copy the key
over. Specifically, the nonfree version breaks the key up into
multiple lines like a PGP key, while the free version puts it all on
one line.
With some massage to the public key generated on a nonfree system, I
was able to make it look like the keys generated on the free system
and thereby let the nonfree ssh2 system log into our free system.
I haven't tried the other way around.
HTH,
--Pete
Hi. Thanks for the response. I am using openssh (ssh2.9p2), and logging
into a remote server which has the non-free ssh2. I can only login using
a ssh1 public key. Interestingly, I also have to specify "-1" when I am
connecting or it will unsuccesfully try to connect with the ssh2
protocol. Perhaps it's something I have to edit something in my
/etc/ssh/ssh_config so that the when I generate a dsa_id or rsa_id key
locally in ~/.ssh/ and transfer it over to the remote server as
authorized_keys2, then the authentication will be recognized and I will
get some kind of passphrase prompt. Or should I create a local
~/.ssh/configuration file with something in it to show that I want to
connect with a dsa key and to check authorized_keys2 rather than
authorized_keys?
I can also use ssh-agent and ssh-add to connect with the ssh1 protocol
as well, but no dice with openssh (2?)rsa or dsa keys. Am I missing
something, or is this as some have suggested a compatibility problem for
the time being??
Thanks,
Glen
