Hi All, I'm on Fedora Core 5. I followed the RSYNC "How-To" by Falko, and setup my users and keys on two different servers. Now, when I get to the last step, I am asked for a password for the user at the site I am trying to mirror. I searched around the forum, and found a couple possible answers: http://www.howtoforge.com/forums/showthread.php?t=6224&page=2&highlight=rsync+asks+password I used an idea from a user suggested on the second page. He/She suggested putting a comma after the final "pty" in the "command..." programming that is added to "authorized keys". Also, this user suggested putting the "ssh...[key]" on its own line. I did this as well... When I returned to attempt another automatic transfer, I was asked for a password again... Here is the output of my command request, from the "mirror" server attempting to automatically login into my main server: ** Note, I specified a different folder for the backup on the mirror server on purpose, noted below as "rsyncbm" ** Note, the keys were generated using 1024 bits, not 2048, since for some reason Fedora would not allow 2048 creation. Code: [root@BACKUP ~]# rsync -avz --delete --exclude=**/stats --exclude=**/error --exclude=**/files/pictures -e "ssh -vi /root/rsync/mirror-rsync-key" email@example.com:/home/www/ /home/rsyncbm/ OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to me.com [64.x.x.52] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/rsync/mirror-rsync-key type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 debug1: match: OpenSSH_4.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'me.com' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Offering public key: /root/rsync/mirror-rsync-key debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: password firstname.lastname@example.org's password: My guess is that there is a system configuration for authentications?