X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/fe8abbf463f798f37ee4f43b3b85583a80fbddf4..7bd029472d96162f71f61df67baedc00fc0bb1a8:/doc/config.but diff --git a/doc/config.but b/doc/config.but index 4bf4c251..e4fd8192 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.57 2003/03/05 22:07:40 simon Exp $ +\versionid $Id: config.but,v 1.63 2003/04/26 13:22:25 simon Exp $ \C{config} Configuring PuTTY @@ -89,6 +89,13 @@ Each saved session is independent of the Default Settings configuration. If you change your preferences and update Default Settings, you must also update every saved session separately. +Saved sessions are stored in the Registry, at the location + +\c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions + +If you need to store them in a file, you could try the method +described in \k{config-file}. + \S{config-closeonexit} \q{Close Window on Exit} \cfg{winhelp-topic}{session.coe} @@ -769,6 +776,26 @@ commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to those server commands. +\S{config-features-qtitle} Disabling remote window title querying + +\cfg{winhelp-topic}{features.qtitle} + +PuTTY can optionally provide the xterm service of allowing server +applications to find out the local window title. This feature is +disabled by default, but you can turn it on if you really want it. + +NOTE that this feature is a \e{potential security hazard}. If a +malicious application can write data to your terminal (for example, +if you merely \c{cat} a file owned by someone else on the server +machine), it can change your window title (unless you have disabled +this as mentioned in \k{config-features-retitle}) and then use this +service to have the new window title sent back to the server as if +typed at the keyboard. This allows an attacker to fake keypresses +and potentially cause your server-side applications to do things you +didn't want. Therefore this feature is disabled by default, and we +recommend you do not turn it on unless you \e{really} know what you +are doing. + \S{config-features-dbackspace} Disabling destructive backspace \cfg{winhelp-topic}{features.dbackspace} @@ -856,6 +883,22 @@ terminal contents. You can disable this behaviour by turning off screen revert when you press a key, by turning on \q{Reset scrollback on keypress}. +\S{config-erasetoscrollback} \q{Push erased text into scrollback} + +\cfg{winhelp-topic}{window.erased} + +When this option is enabled, the contents of the terminal screen +will be pushed into the scrollback when a server-side application +clears the screen, so that your scrollback will contain a better +record of what was on your screen in the past. + +If the application switches to the alternate screen (see +\k{config-features-altscreen} for more about this), then the +contents of the primary screen will be visible in the scrollback +until the application switches back again. + +This option is enabled by default. + \H{config-appearance} The Appearance panel The Appearance configuration panel allows you to control aspects of @@ -1109,15 +1152,20 @@ characters \cfg{winhelp-topic}{selection.linedraw} By default, when you copy and paste a piece of the PuTTY screen that -contains VT100 line and box drawing characters, PuTTY will translate -them into the \q{poor man's} line-drawing characters \c{+}, \c{-} -and \c{|}. The checkbox \q{Don't translate line drawing chars} -disables this feature, so line-drawing characters will be pasted as -if they were in the normal character set. This will typically mean -they come out mostly as \c{q} and \c{x}, with a scattering of -\c{jklmntuvw} at the corners. This might be useful if you were -trying to recreate the same box layout in another program, for -example. +contains VT100 line and box drawing characters, PuTTY will paste +them in the form they appear on the screen: either Unicode line +drawing code points, or the \q{poor man's} line-drawing characters +\c{+}, \c{-} and \c{|}. The checkbox \q{Paste VT100 line drawing +chars as lqqqk} disables this feature, so line-drawing characters +will be pasted as the ASCII characters that were printed to produce +them. This will typically mean they come out mostly as \c{q} and +\c{x}, with a scattering of \c{jklmntuvw} at the corners. This might +be useful if you were trying to recreate the same box layout in +another program, for example. + +Note that this option only applies to line-drawing characters which +\e{were} printed by using the VT100 mechanism. Line-drawing +characters displayed using Unicode will paste as Unicode always. \S{config-rtfpaste} Pasting in Rich Text Format @@ -1962,7 +2010,8 @@ To add a port forwarding: \b Set one of the \q{Local} or \q{Remote} radio buttons, depending on whether you want to forward a local port to a remote destination (\q{Local}) or forward a remote port to a local destination -(\q{Remote}). +(\q{Remote}). Alternatively, select \q{Dynamic} if you want PuTTY to +provide a local SOCKS proxy on a local port. \b Enter a source port number into the \q{Source port} box. For local forwardings, PuTTY will listen on this port of your PC. For @@ -1970,10 +2019,12 @@ remote forwardings, your SSH server will listen on this port of the remote machine. Note that most servers will not allow you to listen on port numbers less than 1024. -\b Enter a hostname and port number separated by a colon, in the -\q{Destination} box. Connections received on the source port will be -directed to this destination. For example, to connect to a POP-3 -server, you might enter \c{popserver.example.com:110}. +\b If you have selected \q{Local} or \q{Remote} (this step is not +needed with \q{Dynamic}), enter a hostname and port number separated +by a colon, in the \q{Destination} box. Connections received on the +source port will be directed to this destination. For example, to +connect to a POP-3 server, you might enter +\c{popserver.example.com:110}. \b Click the \q{Add} button. Your forwarding details should appear in the list box. @@ -2007,7 +2058,7 @@ controls in the Tunnels panel to change this: \b The \q{Local ports accept connections from other hosts} option allows you to set up local-to-remote port forwardings in such a way that machines other than your client PC can connect to the forwarded -port. +port. (This also applies to dynamic SOCKS forwarding.) \b The \q{Remote ports do the same} option does the same thing for remote-to-local port forwardings (so that machines other than the