10 More Discussions You Might Find Interesting
1. AIX
Is there a way that I can remotely control a user's ssh session so I can see what they are doing and walk them through the problem they are having on my AIX based application? (2 Replies)
Discussion started by: De@nneG
2 Replies
2. Shell Programming and Scripting
Hi there,
I'm trying to run a script remotely on a server in a particular directory named after hostname which already exists, my login session gets killed as soon as I run the below command. Not sure what is wrong, is there a better way to do it ?
Note: I can also use nohup command to run... (14 Replies)
Discussion started by: mbak
14 Replies
3. Shell Programming and Scripting
Hi everyone, after about 2 days of scratching my head on this one, I'm finally ready to punt this and ask for some actual help. Here's the situation. We have 1 server, that runs multiple VM's. To gain access to those VM's we ssh from host01 to the other vm hosts. For example when we first log... (4 Replies)
Discussion started by: Lost in Cyberia
4 Replies
4. Shell Programming and Scripting
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.
#!/bin/ksh
ssh -t -t username@12.5.5.3 << EOF
password
cd bin
pwd
EOF
When I run it. It... (5 Replies)
Discussion started by: seekryts15
5 Replies
5. AIX
Hi Admins,
Just a small question - Can we have multiple session for single user on HMC.
e.g. Can I have a terminal session (via IE ) and command line (ssh) at same time ??
I am not sure whether it will impact HMC system or not. So want to make sure.
let me know folks.
Thanks (3 Replies)
Discussion started by: snchaudhari2
3 Replies
6. Solaris
how to login with ssh to remote system with out applying the remote root/user password
with rlogin we can ujse .rhosts file
but with ssh howits possible
plz guide (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
7. Red Hat
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)
Discussion started by: jaapar
3 Replies
8. Shell Programming and Scripting
Hi All,
I want to login to CVS using terminal. I am executing the following command in the terminal :-
export CVSROOT=: pserver:ags_rd@istcvs.corp.apple.com:/istcvs/CVSHOME
cvs login
But i get the following error :
Afreens-iMac:buildTest Afreen$ export CVSROOT=:... (3 Replies)
Discussion started by: Afreen
3 Replies
9. Shell Programming and Scripting
hi all ,
i need the command for remote login in to another terminal, came accross by using "tty" command. please suggest and help me out in this.
Regrds
Sridhar. (1 Reply)
Discussion started by: Sridhar_dev
1 Replies
10. Solaris
hi all
How to reconnect to a disconnected remote ssh session on solaris 10
is there any way (4 Replies)
Discussion started by: h@foorsa.biz
4 Replies
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 [-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.
-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)).
ENVIRONMENT
SSH_COPY_ID_LEGACY
If the SSH_COPY_ID_LEGACY environment variable is set, the ssh-copy-id is run in a legacy mode. In this mode, the ssh-copy-id doesn't
check an existence of a private key and doesn't do remote checks of the remote server versions or if public keys are already
installed.
SEE ALSO
ssh(1), ssh-agent(1), sshd(8)
BSD
June 17, 2010 BSD