Add VC++ Project files for PuTTY DLL without exported functions.

[ffftp/ffftp.git] / putty / DOC / PAGEANT.BUT

\define{versionidpageant} \versionid $Id: pageant.but 6610 2006-03-14 11:21:59Z jacob $\r
\r
\C{pageant} Using \i{Pageant} for authentication\r
\r
\cfg{winhelp-topic}{pageant.general}\r
\r
Pageant is an SSH \i{authentication agent}. It holds your \i{private key}s\r
in memory, already decoded, so that you can use them often\r
\I{passwordless login}without needing to type a \i{passphrase}.\r
\r
\H{pageant-start} Getting started with Pageant\r
\r
Before you run Pageant, you need to have a private key in \c{*.\i{PPK}}\r
format. See \k{pubkey} to find out how to generate and use one.\r
\r
When you run Pageant, it will put an icon of a computer wearing a\r
hat into the \ii{System tray}. It will then sit and do nothing, until you\r
load a private key into it.\r
\r
If you click the Pageant icon with the right mouse button, you will\r
see a menu. Select \q{View Keys} from this menu. The Pageant main\r
window will appear. (You can also bring this window up by\r
double-clicking on the Pageant icon.)\r
\r
The Pageant window contains a list box. This shows the private keys\r
Pageant is holding. When you start Pageant, it has no keys, so the\r
list box will be empty. After you add one or more keys, they will\r
show up in the list box.\r
\r
To add a key to Pageant, press the \q{Add Key} button. Pageant will\r
bring up a file dialog, labelled \q{Select Private Key File}. Find\r
your private key file in this dialog, and press \q{Open}.\r
\r
Pageant will now load the private key. If the key is protected by a\r
passphrase, Pageant will ask you to type the passphrase. When the\r
key has been loaded, it will appear in the list in the Pageant\r
window.\r
\r
Now start PuTTY and open an SSH session to a site that accepts your\r
key. PuTTY will notice that Pageant is running, retrieve the key\r
automatically from Pageant, and use it to authenticate. You can now\r
open as many PuTTY sessions as you like without having to type your\r
passphrase again.\r
\r
(PuTTY can be configured not to try to use Pageant, but it will try\r
by default. See \k{config-ssh-tryagent} and\r
\k{using-cmdline-agentauth} for more information.)\r
\r
When you want to shut down Pageant, click the right button on the\r
Pageant icon in the System tray, and select \q{Exit} from the menu.\r
Closing the Pageant main window does \e{not} shut down Pageant.\r
\r
\H{pageant-mainwin} The Pageant main window\r
\r
The Pageant main window appears when you left-click on the Pageant\r
system tray icon, or alternatively right-click and select \q{View\r
Keys} from the menu. You can use it to keep track of what keys are\r
currently loaded into Pageant, and to add new ones or remove the\r
existing keys.\r
\r
\S{pageant-mainwin-keylist} The key list box\r
\r
\cfg{winhelp-topic}{pageant.keylist}\r
\r
The large list box in the Pageant main window lists the private keys\r
that are currently loaded into Pageant. The list might look\r
something like this:\r
\r
\c ssh1    1024 22:c3:68:3b:09:41:36:c3:39:83:91:ae:71:b2:0f:04 k1\r
\c ssh-rsa 1023 74:63:08:82:95:75:e1:7c:33:31:bb:cb:00:c0:89:8b k2\r
\r
For each key, the list box will tell you:\r
\r
\b The type of the key. Currently, this can be \c{ssh1} (an RSA key\r
for use with the SSH-1 protocol), \c{ssh-rsa} (an RSA key for use\r
with the SSH-2 protocol), or \c{ssh-dss} (a DSA key for use with\r
the SSH-2 protocol).\r
\r
\b The size (in bits) of the key.\r
\r
\b The \I{key fingerprint}fingerprint for the public key. This should be\r
the same fingerprint given by PuTTYgen, and (hopefully) also the same\r
fingerprint shown by remote utilities such as \i\c{ssh-keygen} when\r
applied to your \c{authorized_keys} file.\r
\r
\b The comment attached to the key.\r
\r
\S{pageant-mainwin-addkey} The \q{Add Key} button\r
\r
\cfg{winhelp-topic}{pageant.addkey}\r
\r
To add a key to Pageant by reading it out of a local disk file,\r
press the \q{Add Key} button in the Pageant main window, or\r
alternatively right-click on the Pageant icon in the system tray and\r
select \q{Add Key} from there.\r
\r
Pageant will bring up a file dialog, labelled \q{Select Private Key\r
File}. Find your private key file in this dialog, and press\r
\q{Open}. If you want to add more than one key at once, you can\r
select multiple files using Shift-click (to select several adjacent\r
files) or Ctrl-click (to select non-adjacent files).\r
\r
Pageant will now load the private key(s). If a key is protected by a\r
passphrase, Pageant will ask you to type the passphrase.\r
\r
(This is not the only way to add a private key to Pageant. You can\r
also add one from a remote system by using agent forwarding; see\r
\k{pageant-forward} for details.)\r
\r
\S{pageant-mainwin-remkey} The \q{Remove Key} button\r
\r
\cfg{winhelp-topic}{pageant.remkey}\r
\r
If you need to remove a key from Pageant, select that key in the\r
list box, and press the \q{Remove Key} button. Pageant will remove\r
the key from its memory.\r
\r
You can apply this to keys you added using the \q{Add Key} button,\r
or to keys you added remotely using agent forwarding (see\r
\k{pageant-forward}); it makes no difference.\r
\r
\H{pageant-cmdline} The Pageant command line\r
\r
Pageant can be made to do things automatically when it starts up, by\r
\I{command-line arguments}specifying instructions on its command line.\r
If you're starting Pageant from the Windows GUI, you can arrange this\r
by editing the properties of the \i{Windows shortcut} that it was\r
started from.\r
\r
If Pageant is already running, invoking it again with the options\r
below causes actions to be performed with the existing instance, not a\r
new one.\r
\r
\S{pageant-cmdline-loadkey} Making Pageant automatically load keys\r
on startup\r
\r
Pageant can automatically load one or more private keys when it\r
starts up, if you provide them on the Pageant command line. Your\r
command line might then look like:\r
\r
\c C:\PuTTY\pageant.exe d:\main.ppk d:\secondary.ppk\r
\r
If the keys are stored encrypted, Pageant will request the\r
passphrases on startup.\r
\r
If Pageant is already running, this syntax loads keys into the\r
existing Pageant.\r
\r
\S{pageant-cmdline-command} Making Pageant run another program\r
\r
You can arrange for Pageant to start another program once it has\r
initialised itself and loaded any keys specified on its command\r
line. This program (perhaps a PuTTY, or a WinCVS making use of\r
Plink, or whatever) will then be able to use the keys Pageant has\r
loaded.\r
\r
You do this by specifying the \I{-c-pageant}\c{-c} option followed\r
by the command, like this:\r
\r
\c C:\PuTTY\pageant.exe d:\main.ppk -c C:\PuTTY\putty.exe\r
\r
\H{pageant-forward} Using \i{agent forwarding}\r
\r
Agent forwarding is a mechanism that allows applications on your SSH\r
server machine to talk to the agent on your client machine.\r
\r
Note that at present, agent forwarding in SSH-2 is only available\r
when your SSH server is \i{OpenSSH}. The \i\cw{ssh.com} server uses a\r
different agent protocol, which PuTTY does not yet support.\r
\r
To enable agent forwarding, first start Pageant. Then set up a PuTTY\r
SSH session in which \q{Allow agent forwarding} is enabled (see\r
\k{config-ssh-agentfwd}). Open the session as normal. (Alternatively,\r
you can use the \c{-A} command line option; see\r
\k{using-cmdline-agent} for details.)\r
\r
If this has worked, your applications on the server should now have\r
access to a Unix domain socket which the SSH server will forward\r
back to PuTTY, and PuTTY will forward on to the agent. To check that\r
this has actually happened, you can try this command on Unix server\r
machines:\r
\r
\c unixbox:~$ echo $SSH_AUTH_SOCK\r
\c /tmp/ssh-XXNP18Jz/agent.28794\r
\c unixbox:~$\r
\r
If the result line comes up blank, agent forwarding has not been\r
enabled at all.\r
\r
Now if you run \c{ssh} on the server and use it to connect through\r
to another server that accepts one of the keys in Pageant, you\r
should be able to log in without a password:\r
\r
\c unixbox:~$ ssh -v otherunixbox\r
\c [...]\r
\c debug: next auth method to try is publickey\r
\c debug: userauth_pubkey_agent: trying agent key my-putty-key\r
\c debug: ssh-userauth2 successful: method publickey\r
\c [...]\r
\r
If you enable agent forwarding on \e{that} SSH connection as well\r
(see the manual for your server-side SSH client to find out how to\r
do this), your authentication keys will still be available on the\r
next machine you connect to - two SSH connections away from where\r
they're actually stored.\r
\r
In addition, if you have a private key on one of the SSH servers,\r
you can send it all the way back to Pageant using the local\r
\i\c{ssh-add} command:\r
\r
\c unixbox:~$ ssh-add ~/.ssh/id_rsa\r
\c Need passphrase for /home/fred/.ssh/id_rsa\r
\c Enter passphrase for /home/fred/.ssh/id_rsa:\r
\c Identity added: /home/fred/.ssh/id_rsa (/home/simon/.ssh/id_rsa)\r
\c unixbox:~$\r
\r
and then it's available to every machine that has agent forwarding\r
available (not just the ones downstream of the place you added it).\r
\r
\H{pageant-security} Security considerations\r
\r
\I{security risk}Using Pageant for public-key authentication gives you the\r
convenience of being able to open multiple SSH sessions without\r
having to type a passphrase every time, but also gives you the\r
security benefit of never storing a decrypted private key on disk.\r
Many people feel this is a good compromise between security and\r
convenience.\r
\r
It \e{is} a compromise, however. Holding your decrypted private keys\r
in Pageant is better than storing them in easy-to-find disk files,\r
but still less secure than not storing them anywhere at all. This is\r
for two reasons:\r
\r
\b Windows unfortunately provides no way to protect pieces of memory\r
from being written to the system \i{swap file}. So if Pageant is holding\r
your private keys for a long period of time, it's possible that\r
decrypted private key data may be written to the system swap file,\r
and an attacker who gained access to your hard disk later on might\r
be able to recover that data. (However, if you stored an unencrypted\r
key in a disk file they would \e{certainly} be able to recover it.)\r
\r
\b Although, like most modern operating systems, Windows prevents\r
programs from accidentally accessing one another's memory space, it\r
does allow programs to access one another's memory space\r
deliberately, for special purposes such as debugging. This means\r
that if you allow a virus, trojan, or other malicious program on to\r
your Windows system while Pageant is running, it could access the\r
memory of the Pageant process, extract your decrypted authentication\r
keys, and send them back to its master.\r
\r
Similarly, use of agent \e{forwarding} is a security improvement on\r
other methods of one-touch authentication, but not perfect. Holding\r
your keys in Pageant on your Windows box has a security advantage\r
over holding them on the remote server machine itself (either in an\r
agent or just unencrypted on disk), because if the server machine\r
ever sees your unencrypted private key then the sysadmin or anyone\r
who cracks the machine can steal the keys and pretend to be you for\r
as long as they want.\r
\r
However, the sysadmin of the server machine can always pretend to be\r
you \e{on that machine}. So if you forward your agent to a server\r
machine, then the sysadmin of that machine can access the forwarded\r
agent connection and request signatures from your private keys, and\r
can therefore log in to other machines as you. They can only do this\r
to a limited extent - when the agent forwarding disappears they lose\r
the ability - but using Pageant doesn't actually \e{prevent} the\r
sysadmin (or hackers) on the server from doing this.\r
\r
Therefore, if you don't trust the sysadmin of a server machine, you\r
should \e{never} use agent forwarding to that machine. (Of course\r
you also shouldn't store private keys on that machine, type\r
passphrases into it, or log into other machines from it in any way\r
at all; Pageant is hardly unique in this respect.)\r