How can I rsync without prompt for password, without using public key authentication?
Clash Royale CLAN TAG#URR8PPP
up vote
33
down vote
favorite
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:
- I understand that this is a bad idea from security aspect
- I must use only
rsync
, can't use other software - I can't use key-based authentication
- I've already read many SE question, e.g.:
how-to-pass-password-for-rsync-ssh-command @ stackoverflow.com
rsync-cron-job-with-a-password @ superuser.com
how-to-setup-rsync-without-password-with-ssh-on-unix-linux @ superuser.com
In other words, I need to have the RSYNC_PASSWORD
approach working! :-)
ssh rsync password
add a comment |
up vote
33
down vote
favorite
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:
- I understand that this is a bad idea from security aspect
- I must use only
rsync
, can't use other software - I can't use key-based authentication
- I've already read many SE question, e.g.:
how-to-pass-password-for-rsync-ssh-command @ stackoverflow.com
rsync-cron-job-with-a-password @ superuser.com
how-to-setup-rsync-without-password-with-ssh-on-unix-linux @ superuser.com
In other words, I need to have the RSYNC_PASSWORD
approach working! :-)
ssh rsync password
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41
add a comment |
up vote
33
down vote
favorite
up vote
33
down vote
favorite
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:
- I understand that this is a bad idea from security aspect
- I must use only
rsync
, can't use other software - I can't use key-based authentication
- I've already read many SE question, e.g.:
how-to-pass-password-for-rsync-ssh-command @ stackoverflow.com
rsync-cron-job-with-a-password @ superuser.com
how-to-setup-rsync-without-password-with-ssh-on-unix-linux @ superuser.com
In other words, I need to have the RSYNC_PASSWORD
approach working! :-)
ssh rsync password
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:
- I understand that this is a bad idea from security aspect
- I must use only
rsync
, can't use other software - I can't use key-based authentication
- I've already read many SE question, e.g.:
how-to-pass-password-for-rsync-ssh-command @ stackoverflow.com
rsync-cron-job-with-a-password @ superuser.com
how-to-setup-rsync-without-password-with-ssh-on-unix-linux @ superuser.com
In other words, I need to have the RSYNC_PASSWORD
approach working! :-)
ssh rsync password
ssh rsync password
edited Nov 21 at 16:17
Bash bros
1
1
asked Jan 29 '14 at 18:55
Dor
77161625
77161625
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41
add a comment |
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41
add a comment |
4 Answers
4
active
oldest
votes
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.
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
add a comment |
up vote
45
down vote
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
|
show 2 more comments
up vote
14
down vote
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
add a comment |
up vote
11
down vote
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
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
add a comment |
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.
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
add a comment |
up vote
13
down vote
accepted
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.
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.
answered Jan 29 '14 at 19:43
brm
76156
76156
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
add a comment |
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
a quicky way to run an rsync server is with s3.amazonaws.com/skaperen/rsend
– Skaperen
Mar 22 '15 at 13:54
add a comment |
up vote
45
down vote
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
|
show 2 more comments
up vote
45
down vote
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
|
show 2 more comments
up vote
45
down vote
up vote
45
down vote
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.
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.
edited Jul 14 at 21:14
answered Jan 29 '14 at 20:23
Graeme
24.7k46296
24.7k46296
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
|
show 2 more comments
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
2
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
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
Super handy.. been searching for an approach to this for a while. Thank you.
– Isaac Gregson
Feb 26 '16 at 18:55
4
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
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
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
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
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
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
|
show 2 more comments
up vote
14
down vote
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
add a comment |
up vote
14
down vote
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
add a comment |
up vote
14
down vote
up vote
14
down vote
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!
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!
answered Dec 23 '14 at 20:04
Eddie
24427
24427
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
add a comment |
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
1
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
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
add a comment |
up vote
11
down vote
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
add a comment |
up vote
11
down vote
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
add a comment |
up vote
11
down vote
up vote
11
down vote
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.
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.
edited Nov 21 at 15:38
answered Feb 22 '15 at 13:22
Arunas Bartisius
28626
28626
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
add a comment |
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
3
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
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
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
This answer makes the most sense
– AJ Meyghani
Sep 7 '16 at 18:13
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f111526%2fhow-can-i-rsync-without-prompt-for-password-without-using-public-key-authentica%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
have you enable rsync daemon on remote server ?
– Rahul Patil
Jan 29 '14 at 19:41