Running Commands on a Remote Linux Server over SSH
Hello,
I'm trying to create a ksh script to ssh to a remote server, enter the password and a couple commands. For security reasons I have changed the login, password and ip in my example.
Code:
#!/bin/ksh
ssh -t -t username@12.5.5.3 << EOF
password
cd bin
pwd
EOF
When I run it. It stalls at the password prompt and it will only continue when I manually enter it. I see the errors are produced due it entering the info too quickly. Is there a way for it to accept the password via script and then wait a certain amount of time before executing the commands? Also need it to exit the remote server when it completes. Any help is much appreciated, thanks.
Example results:
Code:
# /home/test/testscript.ksh
username@12.5.5.3's password: <----STALLS HERE. ONLY PROCEEDS WHEN I ENTER THE PASSWORD MANUALLY.
password
cd bin
pwd
[username@remoteserver ~]$ password
[1] 27729
-bash: pas: command not found
-bash: sword: command not found
[1]+ Exit 127 pas
[username@remoteserver ~]$ cd bin
[username@remoteserver bin]$ pwd
/home/user/bin
[username@remoteserver bin]$ <----STOPS AND STILL ON REMOTE SERVER.
mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why?
AHHHH!!
I have been connecting to the server with the line: ssh userid@website.com
The remote server accepts my password; logs me in with ssh; posts a lovely welcome message AND closes the session. Is this a "term... (0 Replies)
I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config.
I am not sure if I can do this with BASH scripting.
I have set up password less login by adding my public key to authorized_keys file, it works.
I am a little... (1 Reply)
I have a script that I'm trying to use that will check for files on a remote machine and if there is files copy the files, modify the perm on the copied files, and then delete the files off of the remote server. Right now I need to get the correct syntax so the the remote commands still interpret... (4 Replies)
So I have a script which performs some basic commands on another server via ssh. It works great, no issues at all. Let's call this "Script A"
BUT, this working script is to be executed remotely from a different UNIX script on another server, also by ssh. Let's call this "Script B".
When... (1 Reply)
I'm working on a script (mostly for practice) to simplify a task I have to do every now and then. I have a cluster with 6 servers on it, each server has a directory with a set of files called *.pid and *.mpid. Each file contains the pid of a process that may or may not be running on that server.... (3 Replies)
I have some commands which need to be executed in remote machine.
I have Linux Server from where I need to connect to Solaris server using ssh and then declare some variable over there and run some commands. I don't want to call a script which is present in Solaris server from Linux server... (7 Replies)
so i want to monitor a variety of things on hundreds of servers. the old process was to have an agent running on each one of these servers.
but now i'm looking to see if its possible to have agentless monitoring. the only other straight forward option other than having an agent on the hosts, is... (2 Replies)
ssh XXXXX@XXXXX'. $HOME/.profile 2>/dev/null;cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME; adcmctl.sh start "apps${AppsPass}" || cd $ADMIN_SCRIPTS_HOME; adcmctl.sh start "apps${AppsPass}"'
As per our business requirement we should be able to execute the above two commands seprated with or ( || )... (4 Replies)
Hi,
I need to run a script located in a directory on remote server by using ssh authentication from my local unix server. Can anyone help me in this.
I have tried the below command. It worked for echo command but when i tried to open a file using cat command it is showing "cat: cannot open... (6 Replies)
Hi,
I am trying to run commands on a list of servers that I can ssh to and just want to know if there is a 'cleaner' way of doing this.
At the moment, I am doing as below. Is there a way that I can escape the double quote differently? If a use a single quote to enclose the commands that I... (1 Reply)
Discussion started by: newbie_01
1 Replies
LEARN ABOUT MOJAVE
ssh-copy-id
SSH-COPY-ID(1) BSD General Commands Manual SSH-COPY-ID(1)NAME
ssh-copy-id -- use locally available keys to authorise logins on a remote machine
SYNOPSIS
ssh-copy-id [-f] [-n] [-i [identity_file]] [-p port] [-o ssh_option] [user@]hostname
ssh-copy-id -h | -?
DESCRIPTION
ssh-copy-id is a script that uses ssh(1) to log into a remote machine (presumably using a login password, so password authentication should
be enabled, unless you've done some clever use of multiple identities). It assembles a list of one or more fingerprints (as described below)
and tries to log in with each key, to see if any of them are already installed (of course, if you are not using ssh-agent(1) this may result
in you being repeatedly prompted for pass-phrases). It then assembles a list of those that failed to log in, and using ssh, enables logins
with those keys on the remote server. By default it adds the keys by appending them to the remote user's ~/.ssh/authorized_keys (creating
the file, and directory, if necessary). It is also capable of detecting if the remote system is a NetScreen, and using its 'set ssh pka-dsa
key ...' command instead.
The options are as follows:
-i identity_file
Use only the key(s) contained in identity_file (rather than looking for identities via ssh-add(1) or in the default_ID_file). If the
filename does not end in .pub this is added. If the filename is omitted, the default_ID_file is used.
Note that this can be used to ensure that the keys copied have the comment one prefers and/or extra options applied, by ensuring that
the key file has these set as preferred before the copy is attempted.
-f Forced mode: doesn't check if the keys are present on the remote server. This means that it does not need the private key. Of
course, this can result in more than one copy of the key being installed on the remote system.
-n do a dry-run. Instead of installing keys on the remote system simply prints the key(s) that would have been installed.
-h, -? Print Usage summary
-p port, -o ssh_option
These two options are simply passed through untouched, along with their argument, to allow one to set the port or other ssh(1)
options, respectively.
Rather than specifying these as command line options, it is often better to use (per-host) settings in ssh(1)'s configuration file:
ssh_config(5).
Default behaviour without -i, is to check if 'ssh-add -L' provides any output, and if so those keys are used. Note that this results in the
comment on the key being the filename that was given to ssh-add(1) when the key was loaded into your ssh-agent(1) rather than the comment
contained in that file, which is a bit of a shame. Otherwise, if ssh-add(1) provides no keys contents of the default_ID_file will be used.
The default_ID_file is the most recent file that matches: ~/.ssh/id*.pub, (excluding those that match ~/.ssh/*-cert.pub) so if you create a
key that is not the one you want ssh-copy-id to use, just use touch(1) on your preferred key's .pub file to reinstate it as the most recent.
EXAMPLES
If you have already installed keys from one system on a lot of remote hosts, and you then create a new key, on a new client machine, say, it
can be difficult to keep track of which systems on which you've installed the new key. One way of dealing with this is to load both the new
key and old key(s) into your ssh-agent(1). Load the new key first, without the -c option, then load one or more old keys into the agent,
possibly by ssh-ing to the client machine that has that old key, using the -A option to allow agent forwarding:
user@newclient$ ssh-add
user@newclient$ ssh -A old.client
user@oldl$ ssh-add -c
... prompt for pass-phrase ...
user@old$ logoff
user@newclient$ ssh someserver
now, if the new key is installed on the server, you'll be allowed in unprompted, whereas if you only have the old key(s) enabled, you'll be
asked for confirmation, which is your cue to log back out and run
user@newclient$ ssh-copy-id -i someserver
The reason you might want to specify the -i option in this case is to ensure that the comment on the installed key is the one from the .pub
file, rather than just the filename that was loaded into you agent. It also ensures that only the id you intended is installed, rather than
all the keys that you have in your ssh-agent(1). Of course, you can specify another id, or use the contents of the ssh-agent(1) as you pre-
fer.
Having mentioned ssh-add(1)'s -c option, you might consider using this whenever using agent forwarding to avoid your key being hijacked, but
it is much better to instead use ssh(1)'s ProxyCommand and -W option, to bounce through remote servers while always doing direct end-to-end
authentication. This way the middle hop(s) don't get access to your ssh-agent(1). A web search for 'ssh proxycommand nc' should prove
enlightening (N.B. the modern approach is to use the -W option, rather than nc(1)).
SEE ALSO ssh(1), ssh-agent(1), sshd(8)BSD June 17, 2010 BSD