Date: 23-11-05 16:45
Sure thing. Let's say you are connecting from foo@bar to foo@baz.
Use ssh-keygen on bar as the foo user to create an ssh key first - I use 512 bit dsa keys, but you can do whatever you please:
foo@bar$ ssh-keygen -b 512 -t dsa
ssh-keygen will prompt you for the location to store the key, you can go ahead and let it go to /home/foo/.ssh/id_dsa. Do not enter a passphrase. If you provide a passphrase, then you'll have to interactively provide it each time you use the key.
Once you have done this, you will have two new files in foo@bar's .ssh folder - id_dsa and id_dsa.pub. On baz, create a file in /home/foo/.ssh named 'authorized_keys', and make it readable and writeable only by foo. Copy the contents of the id_dsa.pub key made by foo@bar into this file. Be very careful about cut'n'paste here - id_dsa.pub will be a one line file but in most editors it will wrap over several lines, and cutting and pasting from an editor may insert extra line breaks that shouldn't be present.
Now foo@bar can make an ssh connection to foo@baz without providing a password. This includes scp and sftp.
Post Edited (24-11-05 08:17)