On Mon, 4 Nov 2002, Steven J. Yellin wrote: > Did you put the ssh2 public keywork (id_rsa.pub) into a file > ~/.ssh/authorized_keys2 on the other computer? Are both computers using > openssh? If so, maybe one of their configuration files makes ssh1 the > default. To make sure ssh2 is what's used, try logging on with "ssh -2 > <username@computer>". To make ssh1 work without a password, make a ssh1 > keypair and copy identity.pub to the other computer's > ~/.ssh/authorized_keys (not authorized_keys2). Note that although I said > the ssh2 public key goes in the remote computer's ~/.ssh/authorized_keys2, > which works for me, the documentation claims it should be > ~/.ssh/authorized_keys. Maybe it would work if you went with the > documentation. In any case, all this can be messed up if the > /etc/ssh/ssh_config or sshd_config files are changed from the default. > For example /etc/ssh/sshd_config could have AuthorizedKeysFile set to > a non-default value. And the default PubkeyAuthentication is "yes"; > if it has been set to "no" on the remote computer, the method I > described won't work. > I don't think there's any problem with the two servers using > different passwords for the same user name. So long as you use the > method I described, the password should be irrelevant.
I think it is more likely that there is a permission problem on one of the config files. Either on the server or on the client. 'ssh -v' will help pin it down on the client, and var/log/secure will help on the server. -- Arend _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
