> > Do your ssh and sshd versions match? > > I have a slink machine with sshd 1.2.26 and a woody machine with sshd > version OpenSSH-1.2.3 and ssh version OpenSSH-1.2.3. All login attempts > are made from the woody machine (OpenSSH). Connects to the old ssh > daemon on the slink machine work, connects to the matching OpenSSH > daemon on the woody machine work not. >
Well now, that's a bit confucius .. > > If you have the files under ~/.ssh/ set up properly, you shouldn't > > even be prompted for the password -- a passphrase, maybe. > > Exactly. That's the behavior I want to achieve. I've done this using two different approaches. Both involve copying ~/.ssh/identity.pub from one machine and adding it to ~/.ssh/authorized_keys on the other machine. (It looks like you're using SSH protocol version 1; the files to be copied will be slightly different for version 2.) The first, discouraged, approach is to just hit "Enter" for the passphrase (i.e. set up a null passphrase) when running ssh-keygen (do this before you copy the identity.pub). The second, "official" approach is to use ssh-agent and ssh-keygen (see their manpages) to prompt you for your passphrase only once, and then "export" it to your environment so that subsequent ssh invocations "know" what it is. In my case this is accomplished by putting SSH_ASKPASS=/cs/local/bin/ssh-askpass ; export SSH_ASKPASS eval `ssh-agent -s` /usr/opt/ssh/bin/ssh-add $HOME/.ssh/identity $HOME/.ssh/id_dsa < /dev/null in my ~/.xinitrc. -chris
