1 .\" $OpenBSD: ssh-agent.1,v 1.49 2009/10/22 15:02:12 sobrado Exp $
3 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5 .\" All rights reserved
7 .\" As far as I am concerned, the code I have written for this software
8 .\" can be used freely for any purpose. Any derived versions of this
9 .\" software must be clearly marked as such, and if the derived work is
10 .\" incompatible with the protocol description in the RFC file, it must be
11 .\" called by a name other than "ssh" or "Secure Shell".
13 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
14 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
15 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
17 .\" Redistribution and use in source and binary forms, with or without
18 .\" modification, are permitted provided that the following conditions
20 .\" 1. Redistributions of source code must retain the above copyright
21 .\" notice, this list of conditions and the following disclaimer.
22 .\" 2. Redistributions in binary form must reproduce the above copyright
23 .\" notice, this list of conditions and the following disclaimer in the
24 .\" documentation and/or other materials provided with the distribution.
26 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
27 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
28 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
29 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
30 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
31 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
32 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
33 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
34 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
35 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
37 .Dd $Mdocdate: October 22 2009 $
42 .Nd authentication agent
47 .Op Fl a Ar bind_address
49 .Op Ar command Op Ar arg ...
55 is a program to hold private keys used for public key authentication
59 is started in the beginning of an X-session or a login session, and
60 all other windows or programs are started as clients to the ssh-agent
62 Through use of environment variables the agent can be located
63 and automatically used for authentication when logging in to other
67 The options are as follows:
69 .It Fl a Ar bind_address
75 .Pa /tmp/ssh-XXXXXXXXXX/agent.\*(Ltppid\*(Gt .
77 Generate C-shell commands on
79 This is the default if
81 looks like it's a csh style of shell.
84 When this option is specified
88 Kill the current agent (given by the
90 environment variable).
92 Generate Bourne shell commands on
94 This is the default if
96 does not look like it's a csh style of shell.
98 Set a default value for the maximum lifetime of identities added to the agent.
99 The lifetime may be specified in seconds or in a time format specified in
101 A lifetime specified for an identity with
103 overrides this value.
104 Without this option the default maximum lifetime is forever.
107 If a commandline is given, this is executed as a subprocess of the agent.
108 When the command dies, so does the agent.
110 The agent initially does not have any private keys.
113 When executed without arguments,
119 .Pa ~/.ssh/identity .
120 If the identity has a passphrase,
122 asks for the passphrase (using a small X11 application if running
123 under X11, or from the terminal if running without X).
124 It then sends the identity to the agent.
125 Several identities can be stored in the
126 agent; the agent can automatically use any of these identities.
128 displays the identities currently held by the agent.
130 The idea is that the agent is run in the user's local PC, laptop, or
132 Authentication data need not be stored on any other
133 machine, and authentication passphrases never go over the network.
134 However, the connection to the agent is forwarded over SSH
135 remote logins, and the user can thus use the privileges given by the
136 identities anywhere in the network in a secure way.
138 There are two main ways to get an agent set up:
139 The first is that the agent starts a new subcommand into which some environment
140 variables are exported, eg
141 .Cm ssh-agent xterm & .
142 The second is that the agent prints the needed shell commands (either
146 syntax can be generated) which can be evaluated in the calling shell, eg
147 .Cm eval `ssh-agent -s`
148 for Bourne-type shells such as
153 .Cm eval `ssh-agent -c`
160 looks at these variables and uses them to establish a connection to the agent.
162 The agent will never send a private key over its request channel.
163 Instead, operations that require a private key will be performed
164 by the agent, and the result will be returned to the requester.
165 This way, private keys are not exposed to clients using the agent.
169 socket is created and the name of this socket is stored in the
173 The socket is made accessible only to the current user.
174 This method is easily abused by root or another instance of the same
179 environment variable holds the agent's process ID.
181 The agent exits automatically when the command given on the command
185 .It Pa ~/.ssh/identity
186 Contains the protocol version 1 RSA authentication identity of the user.
188 Contains the protocol version 2 DSA authentication identity of the user.
190 Contains the protocol version 2 RSA authentication identity of the user.
191 .It Pa /tmp/ssh-XXXXXXXXXX/agent.\*(Ltppid\*(Gt
193 sockets used to contain the connection to the authentication agent.
194 These sockets should only be readable by the owner.
195 The sockets should get automatically removed when the agent exits.
203 OpenSSH is a derivative of the original and free
204 ssh 1.2.12 release by Tatu Ylonen.
205 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
206 Theo de Raadt and Dug Song
207 removed many bugs, re-added newer features and
209 Markus Friedl contributed the support for SSH
210 protocol versions 1.5 and 2.0.