Man page for apt-get sshpass Command
This tutorial shows the man page for man sshpass in linux.
Open terminal with 'su' access and type the command as shown below:
Result of the Command Execution shown below:
SSHPASS(1) Sshpass User Manual SSHPASS(1)
sshpass noninteractive ssh password provider
sshpass [ ffilename| dnum| ppassword| e] [options] command arguments
This manual page documents the sshpass command.
sshpass is a utility designed for running ssh using the mode referred
to as "keyboard interactive" password authentication, but in non inter
ssh uses direct TTY access to make sure that the password is indeed
issued by an interactive keyboard user. Sshpass runs ssh in a dedicated
tty, fooling it into thinking it is getting the password from an inter
The command to run is specified after sshpass' own options. Typically
it will be "ssh" with arguments, but it can just as well be any other
command. The password prompt used by ssh is, however, currently hard
coded into sshpass.
If not option is given, sshpass reads the password from the standard
input. The user may give at most one alternative source for the pass
The password is given on the command line. Please note the sec
tion titled "SECURITY CONSIDERATIONS".
The password is the first line of the file filename.
number is a file descriptor inherited by sshpass from the run
ner. 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 insis
tance 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 pro
vides 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 pass
word, 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.
As with any other program, sshpass returns 0 on success. In case of
failure, the following return codes are used:
1 Invalid command line argument
2 Conflicting arguments given
3 General runtime error
4 Unrecognized response from ssh (parse error)
5 Invalid/incorrect password
6 Host public key is unknown. sshpass exits without confirming the
In addition, ssh might be complaining about a man in the middle attack.
This complaint does not go to the tty. In other words, even with ssh
pass, the error message from ssh is printed to standard error. In such
a case ssh's return code is reported back. This is typically an unimag
inative (and non informative) "255" for all error cases.
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 .
To do the same from a bourne shell script in a marginally less exposed
SSHPASS=12345 rsync rsh='sshpass e ssh l test' host.exam
Sshpass is in its infancy at the moment. As such, bugs are highly pos
sible. In particular, if the password is read from stdin (no password
option at all), it is possible that some of the input aimed to be
passed to ssh will be read by sshpass and lost.
Lingnu Open Source Consulting October 17, 2008 SSHPASS(1)