X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fusing.but;h=dc0d6b9b4a691194347eb2e0463d5418047c28e1;hb=15386cbe927fc85ac2fed0bb47704645c4b67dad;hp=feb42454e66508e545a7648e2d04765725aced94;hpb=8ba3e8ce772b0a772faa2ff8fa353b03723653b1;p=PuTTY.git diff --git a/doc/using.but b/doc/using.but index feb42454..dc0d6b9b 100644 --- a/doc/using.but +++ b/doc/using.but @@ -121,6 +121,9 @@ and hit the Copy button to copy them to the \i{clipboard}. If you are reporting a bug, it's often useful to paste the contents of the Event Log into your bug report. +(The Event Log is not the same as the facility to create a log file +of your session; that's described in \k{using-logging}.) + \S2{using-specials} \ii{Special commands} Depending on the protocol used for the current session, there may be @@ -198,6 +201,28 @@ resets associated timers and counters). For more information about repeat key exchanges, see \k{config-ssh-kex-rekey}. } +\b \I{host key cache}Cache new host key type + +\lcont{ +Only available in SSH-2. This submenu appears only if the server has +host keys of a type that PuTTY doesn't already have cached, and so +won't use. Selecting a key here will allow PuTTY to use that key now +and in future: PuTTY will do key here will cause a fresh key-exchange +with the selected key, and immediately add that key to PuTTY's +permanent cache (relying on the host key used at the start of the +connection to cross-certify the new key). That key will be used for +the rest of the current session; it may not actually be used for +future sessions. + +Normally, PuTTY will carry on using a host key it already knows, even +if the server offers key formats that PuTTY would otherwise prefer, +to avoid host key prompts. As a result, if you've been using a server +for some years, you may still be using an older key than a new user +would use, due to server upgrades in the meantime. The SSH protocol +unfortunately does not have organised facilities for host key migration +and rollover, but this allows you to manually upgrade. +} + \b \I{Break, SSH special command}Break \lcont{ @@ -316,8 +341,9 @@ If you find that special characters (\i{accented characters}, for example, or \i{line-drawing characters}) are not being displayed correctly in your PuTTY session, it may be that PuTTY is interpreting the characters sent by the server according to the wrong \e{character -set}. There are a lot of different character sets available, so it's -entirely possible for this to happen. +set}. There are a lot of different character sets available, and no +good way for PuTTY to know which to use, so it's entirely possible +for this to happen. If you click \q{Change Settings} and look at the \q{Translation} panel, you should see a large number of character sets which you can @@ -368,12 +394,12 @@ For more options relating to X11 forwarding, see \k{config-ssh-x11}. \H{using-port-forwarding} Using \i{port forwarding} in SSH -The SSH protocol has the ability to forward arbitrary \i{network -connection}s over your encrypted SSH connection, to avoid the network -traffic being sent in clear. For example, you could use this to -connect from your home computer to a \i{POP-3} server on a remote -machine without your POP-3 password being visible to network -sniffers. +The SSH protocol has the ability to forward arbitrary \I{network +connection}network (TCP) connections over your encrypted SSH +connection, to avoid the network traffic being sent in clear. For +example, you could use this to connect from your home computer to a +\i{POP-3} server on a remote machine without your POP-3 password being +visible to network sniffers. In order to use port forwarding to \I{local port forwarding}connect from your local machine to a port on a remote server, you need to: @@ -894,6 +920,10 @@ The \c{-i} option allows you to specify the name of a private key file in \c{*.\i{PPK}} format which PuTTY will use to authenticate with the server. This option is only meaningful if you are using SSH. +If you are using Pageant, you can also specify a \e{public} key file +(in RFC 4716 or OpenSSH format) to identify a specific key file to use. +(This won't work if you're not running Pageant, of course.) + For general information on \i{public-key authentication}, see \k{pubkey}. @@ -904,22 +934,22 @@ authentication} box in the Auth panel of the PuTTY configuration box \S2{using-cmdline-loghost} \i\c{-loghost}: specify a \i{logical host name} -This option overrides PuTTY's normal SSH host key caching policy by -telling it the name of the host you expect your connection to end up -at (in cases where this differs from the location PuTTY thinks it's -connecting to). It can be a plain host name, or a host name followed -by a colon and a port number. See \k{config-loghost} for more detail -on this. +This option overrides PuTTY's normal SSH \I{host key cache}host key +caching policy by telling it the name of the host you expect your +connection to end up at (in cases where this differs from the location +PuTTY thinks it's connecting to). It can be a plain host name, or a +host name followed by a colon and a port number. See +\k{config-loghost} for more detail on this. \S2{using-cmdline-hostkey} \i\c{-hostkey}: \I{manually configuring host keys}manually specify an expected host key -This option overrides PuTTY's normal SSH host key caching policy by -telling it exactly what host key to expect, which can be useful if the -normal automatic host key store in the Registry is unavailable. The -argument to this option should be either a host key fingerprint, or an -SSH-2 public key blob. See \k{config-ssh-kex-manual-hostkeys} for more -information. +This option overrides PuTTY's normal SSH \I{host key cache}host key +caching policy by telling it exactly what host key to expect, which +can be useful if the normal automatic host key store in the Registry +is unavailable. The argument to this option should be either a host key +fingerprint, or an SSH-2 public key blob. See +\k{config-ssh-kex-manual-hostkeys} for more information. You can specify this option more than once if you want to configure more than one key to be accepted. @@ -953,3 +983,20 @@ DSR/DTR. For example, \cq{-sercfg 19200,8,n,1,N} denotes a baud rate of 19200, 8 data bits, no parity, 1 stop bit and no flow control. + +\S2{using-cmdline-sshlog} \i\c{-sessionlog}, \i\c{-sshlog}, +\i\c{-sshrawlog}: specify session logging + +These options cause the PuTTY network tools to write out a \i{log +file}. Each of them expects a file name as an argument, e.g. +\cq{-sshlog putty.log} causes an SSH packet log to be written to a +file called \cq{putty.log}. The three different options select +different logging modes, all available from the GUI too: + +\b \c{-sessionlog} selects \q{All session output} logging mode. + +\b \c{-sshlog} selects \q{SSH packets} logging mode. + +\b \c{-sshrawlog} selects \q{SSH packets and raw data} logging mode. + +For more information on logging configuration, see \k{config-logging}.