As you want to do this from a Windows box using PuTTY, you need to look at Plink. This is a tool called from the Windows shell (DOS Prompt) and can be used like ssh. It is especially useful for running a ssh command on a remote *nix server from a Windows PowerShell or batch script.
It should already be installed as part of the default PuTTY installation, or it can be downloaded from the PuTTY website as a standalone executable.
Can you help me with the setup / syntax of the same ? I have Plink on my windows box. I need to upload a file to unix server X using Winscp command line and the use Plink to execute a script x.sh on the same unix server X.
So I am just looking for having to execute a single command .cmd from windows to do the above jobs for me.
---------- Post updated at 04:18 AM ---------- Previous update was at 03:53 AM ----------
I tried the below command but strangely it fails.
When i execute the same mv command from Putty after login in it succeeds.
the command in local_script.sh is
The only difference i saw which may not be concerning here is that loggin throught putty asked me for the password of user1 twice while plink command via windows asked for the password just once.
hi unix guru's
i am new to unix shell programming.
i found a trouble in executing a script(bali.ksh) which is available on serverA with username xyza, this script contains sqlplus command to retrive the data from the database available on other serverC.
Now i need to run the above script... (4 Replies)
Hi All,
I want to execute some commands on unix machine from the mac machne. I have two options for doing so, I am confused which is the best way of doing. Here are two options.
Requirement:
Execute command on the remote server machine. Commands to be executed itself contain arguments to be... (0 Replies)
Hi everyone
I intend to trigger a script from one machine say mc1 that actually excutes on different machine say mc2 and redirect the logs to that machine mc2.
I tried to use nohup <nfs location of machine >/script.sh > <nfs location of machine >/script.log 2>&1 &
nfs location of... (2 Replies)
Hi,
I need to login into remote server and execute a shell script over there.
As of now i am making use of ssh command
ssh primUser@135.254.242.2 sh /poll.sh
I am logging in as primUser but unless i change the user to root the script execution on the remote machine is not possible.
... (5 Replies)
All, I need to write an unix shell script which inserts some records into a file located in remote servers.
* Get the input from the user and insert according the first row. It should be in ascending order.
123451,XA,ABA
123452,XB,ABB
123453,XC,ABC
123455,XE,ABE
123456,XF,ABF
123458,XG,ABG... (2 Replies)
We have a few machines which share the same directory. How can I execute the same script under that directory in different machine while I am using mine? (1 Reply)
Recently, I need to generate a lot of files from a few master files. In fact, if I relogin to the server machine, my operating would be much faster. My question is this: Can I write a script in which the current path can be automatically saved and relogin to the server to execute my command in the... (0 Replies)
Hi All,
We have 2 servers A and B.
B is having a sctipt called b.sh in path /home/dev/scripts.
Now my requirement is i want to execute b.sh from server A.
Kindly help me. (3 Replies)
I want to execute a shell script(set of commands) on remote machine and that script takes input from text file(local machine). Please refer below:
ssh user@hostname 'bash -s'< ./test.sh file.txt
But i got the error file.txt doesn't exist.
Can anyone help me on this.
Content of test.sh:
... (2 Replies)
I have a script in local server
cd /home/dell/work/BOP/testdir
./processchk po (here processchk is a script & po is passed as an argument)
Now I want to execute this script from remote server
ssh $username@$hostname "cd /home/dell/work/BOP/testdir; ./processchk po"
But Its getting error... (9 Replies)
Discussion started by: manohar2013
9 Replies
LEARN ABOUT REDHAT
ssh-agent
SSH-AGENT(1) BSD General Commands Manual SSH-AGENT(1)NAME
ssh-agent -- authentication agent
SYNOPSIS
ssh-agent [-a bind_address] [-c | -s] [-d] [command [args ...]]
ssh-agent [-c | -s] -k
DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). The idea is that ssh-agent is started in the
beginning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Through use
of environment variables the agent can be located and automatically used for authentication when logging in to other machines using ssh(1).
The options are as follows:
-a bind_address
Bind the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.<ppid>.
-c Generate C-shell commands on stdout. This is the default if SHELL looks like it's a csh style of shell.
-s Generate Bourne shell commands on stdout. This is the default if SHELL does not look like it's a csh style of shell.
-k Kill the current agent (given by the SSH_AGENT_PID environment variable).
-d Debug mode. When this option is specified ssh-agent will not fork.
If a commandline is given, this is executed as a subprocess of the agent. When the command dies, so does the agent.
The agent initially does not have any private keys. Keys are added using ssh-add(1). When executed without arguments, ssh-add(1) adds the
files $HOME/.ssh/id_rsa, $HOME/.ssh/id_dsa and $HOME/.ssh/identity. If the identity has a passphrase, ssh-add(1) asks for the passphrase
(using a small X11 application if running under X11, or from the terminal if running without X). It then sends the identity to the agent.
Several identities can be stored in the agent; the agent can automatically use any of these identities. ssh-add -l displays the identities
currently held by the agent.
The idea is that the agent is run in the user's local PC, laptop, or terminal. Authentication data need not be stored on any other machine,
and authentication passphrases never go over the network. However, the connection to the agent is forwarded over SSH remote logins, and the
user can thus use the privileges given by the identities anywhere in the network in a secure way.
There are two main ways to get an agent setup: Either the agent starts a new subcommand into which some environment variables are exported,
or the agent prints the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the calling shell.
Later ssh(1) looks at these variables and uses them to establish a connection to the agent.
The agent will never send a private key over its request channel. Instead, operations that require a private key will be performed by the
agent, and the result will be returned to the requester. This way, private keys are not exposed to clients using the agent.
A unix-domain socket is created and the name of this socket is stored in the SSH_AUTH_SOCK environment variable. The socket is made accessi-
ble only to the current user. This method is easily abused by root or another instance of the same user.
The SSH_AGENT_PID environment variable holds the agent's process ID.
The agent exits automatically when the command given on the command line terminates.
FILES
$HOME/.ssh/identity
Contains the protocol version 1 RSA authentication identity of the user.
$HOME/.ssh/id_dsa
Contains the protocol version 2 DSA authentication identity of the user.
$HOME/.ssh/id_rsa
Contains the protocol version 2 RSA authentication identity of the user.
/tmp/ssh-XXXXXXXX/agent.<ppid>
Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner.
The sockets should get automatically removed when the agent exits.
AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. Markus Friedl contributed the support for SSH
protocol versions 1.5 and 2.0.
SEE ALSO ssh(1), ssh-add(1), ssh-keygen(1), sshd(8)BSD September 25, 1999 BSD