10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: Y.balakrishna
4 Replies
2. Shell Programming and Scripting
Hi,
i want to write script where it will login into 50 hosts and if login is successful it print message "login to host1 is
successful" if not it should print message "Not able to login to host1". once connection to the host is succesful it should fire df command to check filesystem if df is... (3 Replies)
Discussion started by: amru8810
3 Replies
3. Shell Programming and Scripting
Hi,
I'm tryin to write a script that will collect information about a remote servers, put them into variables and print them to screen.
# /usr/bin/bash
ls $1 > /dev/null 2>/dev/null
if
then
echo "$1 is file"
for server in $(cat $1)
do
# echo $server
... (5 Replies)
Discussion started by: moshesa
5 Replies
4. 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
5. Shell Programming and Scripting
So, HostB has a SSH trust via pre-shared keys from HostA.
HostA> ssh HostB hostname
HostB
HostA> ssh HostB echo `hostname`
HostA
HostA> ssh HostB 'echo `hostname`'
`hostname`
HostA> ssh HostB "echo `hostname`"
HostA
HostA> ssh HostB echo $PS1
user@HostA:$PWD
HostA> ssh HostB... (12 Replies)
Discussion started by: Wrathe
12 Replies
6. Shell Programming and Scripting
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)
Discussion started by: jcalisi
4 Replies
7. Solaris
I edited my /etc/default/login file and commented the line:
# If CONSOLE is set, root can only login on that device.
# Comment this line out to allow remote login by root.
#
#CONSOLE=/dev/console
I still cant login thru telnet or ssh.
What else do i have to do to be able to login... (14 Replies)
Discussion started by: BG_JrAdmin
14 Replies
8. Shell Programming and Scripting
Hi ,
I need to login to remotemachines through ssh and move some logfiles to my localmachine. My servername,username and password will be store in the .profile file. can any one please help me in this?
This will be a cronjob so Password can't be enter at run time.
Thanks in advance
Subin (5 Replies)
Discussion started by: subin_bala
5 Replies
9. Solaris
Hi ,
I have SunBlade 150 Workstation (Solaris 9), I installed the OS again then when I try to login to any server using ( Options > Remote Login > Enter Host Name)
after I entered any host name nothing happened just white page for 2 or 3 mintues then the login screen reseted to the local... (4 Replies)
Discussion started by: adel8483
4 Replies
10. UNIX for Advanced & Expert Users
Hi:
I have been given the responsibility of administering AIX 3.1 machine in my lab recently. And, I am having trouble logging on to the machine using SSH through windous systems. Thus, now no one is able to access it!!
The following error message is displayed when I tried to login:
"The... (3 Replies)
Discussion started by: pdepa
3 Replies
ssh-agent(1) User Commands 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). ssh-agent is often started at the beginning of a
login session. 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). See the System Administra-
tion Guide: Security Services.
If a command line 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), which sends the identity to the agent. Several identi-
ties can be stored in the agent; the agent can automatically use any of these identities. Use the -l option in ssh-add(1) to display the
identities currently held by the agent.
The agent is run in the user's local host. Authentication data need not be stored on any other machine, and authentication passphrases
never go over the network. However, if the connection to the agent is forwarded over SSH remote logins, the user can 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 you let the agent start a new subcommand into which some environment variables are
exported, or you let the agent print the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the
calling shell. Later, use ssh(1) to look at these variables and use them to establish a connection to the agent.
A unix-domain socket is created (/tmp/ssh-XXXXXXXX/agent.pid) and the name of this socket is stored in the SSH_AUTH_SOCK environment vari-
able. The socket is made accessible 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 PID.
The agent exits automatically when the command given on the command line terminates.
OPTIONS
The following options are supported:
-a bind_address Binds the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.pid.
-c Generates C-shell commands on stdout. This is the default if SHELL indicates that it is a csh style of shell.
-d Debug mode. When this option is specified, ssh-agent will not fork.
-k Kills the current agent (given by the SSH_AGENT_PID environment variable).
-s Generates Bourne shell commands on stdout. This is the default if SHELL does not indicate that it is a csh style of
shell.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/tmp/ssh-XXXXXXXX/agent.pid
Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The
sockets are removed when the agent exits.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsshu |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(1M), attributes(5)
System Administration Guide: Security Services
SunOS 5.11 17 Nov 2008 ssh-agent(1)