Hi All,
Language like C,Java can interact with database..and can use database information .. can a shall script do this?
if yes thn plz guide me.....
thankx (7 Replies)
Hello,
I have a simple expect script I use to ssh to a workstation. I then pass control over to the user with interact.
This script works fine on my HP and Mac, but on my Linux Desktop, I get a problem where the terminal hangs when ever I execute a command in the interact session that requires a... (0 Replies)
Hello - My requirement is like this...
I have flat file which is sitting in windows server... My shell script is running in unix box. Shell script loads the flat file into oracle through sqlloader. So script needs to pickup the flat file from windows box.
I need to refer windows location in... (8 Replies)
Hello all!
I have a C program that runs on a loop, prompting the user for input until it is exited. I want to create a shell script that can run this program and provide input. How can I do this? I have investigated 'expect' and piping to stdin, but haven't had any success. Any help is... (2 Replies)
So, I have an expect script (let's call it expect.exp) that takes 3 arguments. It logs into a remote server, runs a set of commands, then hands control over to the user by the "interact" command. If I call this script from the command line, it works properly.
Now I'd like to apply this script... (2 Replies)
Hi
I'm working on an Expect script that is supposed to log-into a remote server and run some steps and exit. In the script I first spawn a 'ssh' session to the server and then after logging in I 'send' all the necessary steps ( with a '\r' at the end, so that they get automatically executed the... (3 Replies)
Hi,
Is it possible to have a script to interact with webpages. I want to create a script that logs a user into a specific site, and is able to get/post information.
Would anyone give me instructions on how it's should be done, and where I can find information on starting it out.
I know... (2 Replies)
I have a long running ksh script that I need to run with "nohup" in the backgound which is all well and good but at the very start of the script it needes to output to the screen to query the user and accept a response before continuing.
Any thoughts on how to accomplish this other than... (11 Replies)
Hello All,
I am writing an Expect Script to execute some commands over ssh then exit the script.
The script works just fine if I automate everything and assuming the correct password was entered.
So this Expect Script gets executed from a Bash script... From the Bash script I pass along an... (0 Replies)
Hi Guys,
Further to my post yesterday I have got round the issue of not being able to use expect by using one of our unix machines to have the script running instead of the jumpbox itself. However my issue is I now have an extra bit it the script which is shh to the jumpbox which requires a ras... (1 Reply)
Discussion started by: mutley2202
1 Replies
LEARN ABOUT DEBIAN
sshpass
SSHPASS(1) Sshpass User Manual SSHPASS(1)NAME
sshpass - noninteractive ssh password provider
SYNOPSIS
sshpass [-ffilename|-dnum|-ppassword|-e] [options] command arguments
DESCRIPTION
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-
interactive mode.
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 interactive user.
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 hardcoded into sshpass.
Options
If no option is given, sshpass reads the password from the standard input. The user may give at most one alternative source for the pass-
word:
-ppassword
The password is given on the command line. Please note the section titled "SECURITY CONSIDERATIONS".
-ffilename
The password is the first line of the file filename.
-dnumber
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".
SECURITY CONSIDERATIONS
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 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 a minimal attempt to hide the password, but such attempts are doomed to 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.
RETURN VALUES
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 new key.
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
sshpass, 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
unimaginative (and non-informative) "255" for all error cases.
EXAMPLES
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 way:
SSHPASS=12345 rsync --rsh='sshpass -e ssh -l test' host.example.com:path .
BUGS
Sshpass is in its infancy at the moment. As such, bugs are highly possible. 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.
Sshpass utilizes the pty(7) interface to control the TTY for ssh. This interface, at least on Linux, has a misfeature where if no slave
file descriptors are open, the master pty returns EIO. This is the normal behavior, except a slave pty may be born at any point by a pro-
gram opening /dev/tty. This makes it impossible to reliably wait for events without consuming 100% of the CPU.
Over the various versions different approaches were attempted at solving this problem. Any given version of sshpass is released with the
belief that it is working, but experience has shown that these things do, occasionally, break. This happened with OpenSSH version 5.6. As
of this writing, it is believed that sshpass is, again, working properly.
Lingnu Open Source Consulting August 6, 2011 SSHPASS(1)