I need to execute rsync, without it prompting me for password.

I've seen in rsync manpage that it doesn't allow specifying the password as command line argument.
But I noticed that it allows specifying the password via the variable RSYNC_PASSWORD.

So I've tried exporting the variable, but rsync keeps asking me for password.

export RSYNC_PASSWORD="abcdef"
rsync root@1.2.3.4:/abc /def

What am I doing wrong?

Please consider:

In other words, I need to have the RSYNC_PASSWORD approach working! :-)

  • have you enable rsync daemon on remote server ? – Rahul Patil Jan 29 '14 at 19:41
up vote 13 down vote accepted

This password environment variable appears only to be used when using the rsync protocol:

rsync rsync://username@1.2.3.4:/abc /def

For this to work, you need to run rsync as a daemon as well (--daemon option), which is often done using inetd.conf.

When using this protocol, abc should correspond to a target defined in /etc/rsyncd.conf. The user name should be present in a auth users line for this target, and a password file should be specified with the secrets file option.

It is this secrets file that contains mappings between user names and passwords in the following format:

username:password

And it is this password that you can specify using the RSYNC_PASSWORD environment variable.

If the rsync daemon isn't running on the target machine, and you don't care about exposing passwords to everyone on the local machine (Why shouldn't someone use passwords in the command line?), you can use sshpass:

 sshpass -p "password" rsync root@1.2.3.4:/abc /def

Note the space at the start of the command, in the bash shell this will stop the command (and the password) from being stored in the history. I don't recommend using the RSYNC_PASSWORD variable unless absolutely necessary (as per a previous edit to this answer), I recommend suppressing history storage or at least clearing history after. In addition, you can use tput reset to clear your terminal history.

  • 2
    Why would you suggest adding password clear text on a command, that's bad linux admin 101. – Eddie Mar 22 '15 at 12:34
  • Super handy.. been searching for an approach to this for a while. Thank you. – Isaac Gregson Feb 26 '16 at 18:55
  • 4
    While this is bad to add the password as clear text, this is currently the only reasonably simple way to this. – Weston Ganger Jun 24 '16 at 16:34
  • 12
    you can always do something like this: sshpass -p $(cat passFile) .. to hide clear pass in bash history,, and chmod 400 on passFile to secure it – Kresimir Pendic Jan 2 '17 at 16:27
  • 1
    I know that this is old, but for the sake of newer readers, please quote the password — passwords can contain special characters and spaces. -p "$RSYNC_PASSWORD" – Paddy Landau Jul 14 at 15:54

You can use standard ssh identities to do passwordless login. This is handled by default if you have a ~/.ssh/id_rsa or the like, but you can also hardcode your own path to the private key of an authroized keypair.

This allows batching/scripting without exposing passwords, and the public key can be remove from the target server if the private key is ever comprimised.

rsync -e"ssh -i /path/to/privateKey" -avR $sourcedir ${ruser}@${rhost}:~/${rdir}/

You can also add arugments like -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null to not force remote host key verification. !Caution - that opens up man in the middle attacks and is general bad practice!

  • 1
    This is especially useful if you're using the new Bash shell for Windows 10. I was wondering why rsync wasn't working passwordlessly. I realized it was using the ~/.ssh folder inside the shell (where rsync lives). Once I used -e to point to the key inside /mnt/c/Users/MyUsername/.ssh, it worked as expected. (Thanks. :D) – Toby Deshane Oct 25 '16 at 14:06

Very useful for scripting is to use --password-file command line option.

  • Create empty file called rsync_pass
  • write in password to this file (nothing more)
  • chmod 600 rsync_pass
  • rsync $args --password-file=rsync_pass user@rsynchost::/share localdirectory

This can be used for scripting and allows to be more secure that just exporting password to system variable.

  • 3
    Note to reader: this also requires an rsync daemon running on the server. I really was hoping that ssh keys would be sufficient for passwordless rsync. – user7000 Nov 2 '15 at 7:01
  • IMHO this is the only correct way to do it if one doesn't want to use ssh. – maxf130 May 8 '16 at 9:51
  • This answer makes the most sense – AJ Meyghani Sep 7 '16 at 18:13

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.