10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
let me know to create a new partition on ncr unix with vxfs filesystem (0 Replies)
Discussion started by: venikathir
0 Replies
2. IP Networking
I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem.
Description:
There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent.
I see where the... (0 Replies)
Discussion started by: broberts
0 Replies
3. UNIX for Advanced & Expert Users
Dear all
I'm trying to virtualize NCR on UBUNTU host .
I need a help ,I'm new to UNIX world .
If any one ca send me step by step guide , I'll appreciate this very much .
Thanks (3 Replies)
Discussion started by: semerouk
3 Replies
4. IP Networking
Hi,
I am new to Net-snmp and I am trying to build upon the template .c and .h files, generated by the mib2c tool, for the agent development. Can somebody guide me on how to build upon the functions generated by mib2c tool or provide a sample code for an agent.
Thanks (0 Replies)
Discussion started by: tisha
0 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I'm reading net-snmp, using Unix (Solaries) and C language ...
- I can manipulate variable (managed object) declared in agent, but the manager can't see that ... it only see the initialization and the value which it ulters using snmpset ...
Ex:
Agent:
static int ... (0 Replies)
Discussion started by: zainab
0 Replies
6. Filesystems, Disks and Memory
Hi, I am new to the UNIX operating system and would realy appreciate some answers to these problems.
I have a unix box (Actually several of them throughout the different locations) that have NCR MP-RAS 3.02.x.x (with multiuser and possibly security packages installed.)
Originally they had 2gb... (4 Replies)
Discussion started by: ad7_98
4 Replies
7. Solaris
Hi,
I am trying to apply the steps in the below link:
http://manageengine.adventnet.com/products/applications_manager/help/appendix/snmp-agent-discovery.html#solaris
but I couldn't continue with the step number 2 ... what is the path of C compiler.
export PATH=<gcc path>:$PATH
... (3 Replies)
Discussion started by: adel8483
3 Replies
8. Solaris
:confused: :confused:
I have a subagent that registers to snmpd on Solaris 8. One of the queries this subagent handles can take an exceptionally long time (it can be on the order of ~30 seconds).
When this query is sent to the processor via SNMP, the subagent is being dropped from the... (1 Reply)
Discussion started by: jalburger
1 Replies
9. IP Networking
Hi,
I am really new in linux and SNMP.
I have a SNMP agent in Linux (net-snmp). I have my MIB
in the /usr/share/mibs directory, and I didn't manage to understand where and how do I put the values of the fields in the MIB? The values are static, so the agent need to return the same value in... (0 Replies)
Discussion started by: linuxbegginer
0 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I'm having these errors when using xntpd on ncr unix.
synchronisation lost
Feb 25 09:10:14 in.xntpd: Previous time adjustment didn't complete
Can anyone help me on this. Is it an issue with the time delay as the reference time servers are on different sites and the ping response is... (0 Replies)
Discussion started by: bert.n
0 Replies
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