cool, thats what I want. But its not using the key ssh key that I created that doesn't use a password.
Ultimately what I'm trying to do is connect to the remote backup host with two different keys. One key I want to be asked for a password and will be the way that I normally connect to the remote host. The other key I want to use only for backup with rsync and thus shouldn't have a password. I'll be restricting the access of the key that doesn't have a password with a script called validate-rsync by placing it in the ~/.ssh/id_dsa_nullkey file.
command="~/validate-rsync" ssh-dss AAAAB3Nza
Here's the code in validate-rsync script
case "$SSH_ORIGINAL_COMMAND" in
The script basically disconnects you from the server if you try to do anything other than rsync. This script will always be run when the key that doesn't require a password is used. This will hopefully keep things fairly secure.
The process I'm trying to duplicate is documented in this article: <http://troy.jdmz.net/rsync/index.html>
I still can't figure out why ssh will accept the identity file normally, but when ssh is used in conjunction with rsync it won't.