On Thu, 2002-09-19 at 21:44, Richard Ibbotson wrote: > Okay. Had a bit more of a play with it. I've copied over the > /etc/ssh/ssh_host_dsa_key and ssh_host_rsa_key to the /etc/ssh folder > on the SuSE machine from the Debian box. You didn't want to do that :-) > I find that I still have to type in the password when I am asked for > it on the Debian console. What do I need to do to get the Debian box > or the SuSE box to understand what it is that I want both of them to > do ? You need to copy across your personal keys. Having run ssh-keygen (if you didn't before, making sure you don't put a passphrase on the keys :) you will find in .ssh/ : alex@rendezvous:~$ ls .ssh id_dsa identity identity.pub known_hosts id_dsa.pub known_hosts is just a list of hosts you've connected to. id_dsa is a SSH2 key (the .pub is the public version) and identity is the SSH1 key (again, .pub the public version). You need to copy the .pub version of your SSH1/2 key into the authorized_keys file in .ssh/ on the server you wish to connect to. So usually, it's just copying across identity.pub to the server you want to connect to, renaming it to authorized_keys, and then trying to connect again. Debian defaults to v2, I think SuSE defaults to v1. But you can select the version, i.e., to connect with v1: ssh -1 server -l user Cheers, Alex.
Attachment:
signature.asc
Description: This is a digitally signed message part