SECURITY NOTE: There is a reason openssh insists that passwords be typed interactively. Passwords are harder to store securely and to pass around securely between programs. If you
Install sshpass in debian
#aptitude install sshpass
This will complete the installation
sshpass [options] command arguments
If not option is given, sshpass reads the password from the standard input. The user may give at most one alternative source for the password:
-p password -- The password is given on the command line. Please note the section titled “SECURITY CONSIDERATIONS".
-f filename -- The password is the first line of the file filename.
-d number -- number is a file descriptor inherited by sshpass from the runner. The password is read from the open file descriptor.
-e -- The password is taken from the environment variable “SSHPASS".
First and foremost, users of sshpass should realize that ssh’s insistance on only getting the password interactively is not without reason. It is close to impossible to securely store the password, and users of sshpass should consider whether ssh’s public key authentication provides the same end-user experience, while involving less hassle and being more secure.
The -p option should be considered the least secure of all of sshpass’s options. All system users can see the password in the command line with a simple “ps” command. Sshpass makes no attempt to hide the password, as such attempts create race conditions without actually solving the problem. Users of sshpass are encouraged to use one of the other password passing techniques, which are all more secure.
In particular, people writing programs that are meant to communicate the password programatically are encouraged to use an anonymous pipe and pass the pipe’s reading end to sshpass using the -d option.
1) Run rsync over SSH using password authentication, passing the password on the command line:
rsync --rsh=’sshpass -p 12345 ssh -l test’ host.example.com:path
2)sshpass -p [yourpassword] ssh [yourusername]@[host]