Background info:
Local machine : Linux, /bin/bash
Remote machine (for the user used for ssh) : SunOs, /bin/ksh
(so we have different OS, different Shells)
My problem :
From the local host i execute
So, as you can see I want to open a ssh session on a remote machine and a want to shift a variable there also (in my case variable $var ). From what I know I can only do that by using the syntax : ssh user@machine " command " , so I used double quotes to describe the commands which I wanna execute via ssh. So, from my example you can see that I can shift the $var variable on the remote session, but I cannot create and/or call (?) another variable $var2 .
If I use ' ' (simple quotes) instead of " " . I can create the variable $var2 , but I cannot shift the variable $var :| .
I tried the same thing when the remote machine was Linux with /bin/sh shell for the user used for ssh. The results are the same, so I don't think it is an issue of different OS or different shells
Any ideas?
P.S. : i dont want to use workarounds such as declare $var in a file, scp the file on the remote host and source it there.
I am trying to search and remove files from a list of servers. I want to find every occurence of this file on each machine and then remove it. If I execute the find command on the remote machine I would like to be able to pipe the output to xargs and remove the file. Does anyone know hat would be... (1 Reply)
Hi!
I have two solaris 10 machines(say 10.1.1.1,10.1.1.2). i have installed rsync on 10.1.1.2,
10.1.1.1:::
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
-bash-3.00$ ssh 10.1.1.2 "echo $PATH"
Password:... (4 Replies)
For a few days now I have been experiencing issues when trying to SSH into 1 of my machine. I get the following output when running 'ssh -vvv':
server1:/home/mymadq> ssh -l root -vvv server2
OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config... (3 Replies)
Hi all,
Really hope someone can help me, i have been trying lots of things and just cant seem to nail it - and for something that seems straight forward....
Anyway, scenario is I need to log onto a second machine (remote server) from main workstation. Once logged in I need to run a batch... (2 Replies)
Hi All,
i have two machines like x and y . my requirement is i should connect to machine Y from x through ssh connection . and do some operation such as copy and move and delete files in Y machine .
i tried with this code but it is doing in machine x only . and i need to exit from Y when... (1 Reply)
Hi Folks,
I want to create VNC session on the Remote RHEL machine on which ssh access is denied. Is there any way so that I can create VNC session without ssh access. Let me know all possible ways! (1 Reply)
how to use ssh to run shell script on a remote machine?
ssh user@remote sh ./script.unx
i ran the above command
./script.unx HAS NOHUP COMMAND IN ITS BODY, I AM GETTING ERROR AS NOHUP NOT FOUND...
i tried to run that script from remote server, its working fine
do ineed to set... (6 Replies)
I want to SSH to 192.168.1.15 Server from my machine, my ip was 192.168.1.99
Source Destination was UP, with IP 192.168.1.15.
This is LAN Network there are 30 Machine's Connected to the network and working fine, I'm Playing around the local machine's because I need to apply the same rules in... (2 Replies)
How to execute a script in remote machine through ssh
I have a script test.sh which does some backup activity in remote machine. Wanted to keep backup also in remote machine.
ssh -l username <remote machine> "commands to be exceuted as ; separted"
but how to put the script in the place of... (5 Replies)
Hello I am writing a script in a local machine, i am using ssh, here i am not able to using back ticks & input file to while loop. here is my script
ssh -q server1
a=`ps -ef | grep ccms | awk {print $1}`
b=`ps -ef | grep mss | awk {print $1}`
# above lines are not working, so i redirected... (12 Replies)
Discussion started by: nanz143
12 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