X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/739c28d05a5e17c231e56db2f18145281f885158..7fcdebd3060d3ff2f7f5e366f3a7167beb4da9ba:/doc/config.but diff --git a/doc/config.but b/doc/config.but index 625d5231..fa70a09b 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.55 2003/02/05 09:05:35 simon Exp $ +\versionid $Id: config.but,v 1.62 2003/04/12 08:59:06 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} @@ -622,10 +629,14 @@ on a terminal bell: the server can send as many Control-G characters as it likes and nothing at all will happen. -\b \q{Play Windows Default Sound} is the default setting. It causes -the Windows \q{Default Beep} sound to be played. To change what this -sound is, or to test it if nothing seems to be happening, use the -Sound configurer in the Windows Control Panel. +\b \q{Make default system alert sound} is the default setting. It +causes the Windows \q{Default Beep} sound to be played. To change +what this sound is, or to test it if nothing seems to be happening, +use the Sound configurer in the Windows Control Panel. + +\b \q{Visual bell} is a silent alternative to a beeping computer. In +this mode, when the server sends a Control-G, the whole PuTTY window +will flash white for a fraction of a second. \b \q{Play a custom sound file} allows you to specify a particular sound file to be used by PuTTY alone, or even by a particular @@ -634,10 +645,6 @@ beeps from any other beeps on the system. If you select this option, you will also need to enter the name of your sound file in the edit control \q{Custom sound file to play as a bell}. -\b \q{Visual bell} is a silent alternative to a beeping computer. In -this mode, when the server sends a Control-G, the whole PuTTY window -will flash white for a fraction of a second. - \S{config-belltaskbar} \q{Taskbar/caption indication on bell} \cfg{winhelp-topic}{bell.taskbar} @@ -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 @@ -883,32 +926,6 @@ offered a choice from all the fixed-width fonts installed on the system. (VT100-style terminal handling can only deal with fixed- width fonts.) -\S{config-title} Controlling the window title - -\cfg{winhelp-topic}{appearance.title} - -The \q{Window title} edit box allows you to set the title of the -PuTTY window. By default the window title will contain the host name -followed by \q{PuTTY}, for example \c{server1.example.com - PuTTY}. -If you want a different window title, this is where to set it. - -PuTTY allows the server to send \c{xterm} control sequences which -modify the title of the window in mid-session. There is also an -\c{xterm} sequence to modify the title of the window's \e{icon}. -This makes sense in a windowing system where the window becomes an -icon when minimised, such as Windows 3.1 or most X Window System -setups; but in the Windows 95-like user interface it isn't as -applicable. - -By default, PuTTY only uses the server-supplied \e{window} title, and -ignores the icon title entirely. If for some reason you want to see -both titles, check the box marked \q{Separate window and icon titles}. -If you do this, PuTTY's window title and Taskbar caption will -change into the server-supplied icon title if you minimise the PuTTY -window, and change back to the server-supplied window title if you -restore it. (If the server has not bothered to supply a window or -icon title, none of this will happen.) - \S{config-mouseptr} \q{Hide mouse pointer when typing in window} \cfg{winhelp-topic}{appearance.hidemouse} @@ -944,6 +961,32 @@ it to zero, or increase it further. The Behaviour configuration panel allows you to control aspects of the behaviour of PuTTY's window. +\S{config-title} Controlling the window title + +\cfg{winhelp-topic}{appearance.title} + +The \q{Window title} edit box allows you to set the title of the +PuTTY window. By default the window title will contain the host name +followed by \q{PuTTY}, for example \c{server1.example.com - PuTTY}. +If you want a different window title, this is where to set it. + +PuTTY allows the server to send \c{xterm} control sequences which +modify the title of the window in mid-session. There is also an +\c{xterm} sequence to modify the title of the window's \e{icon}. +This makes sense in a windowing system where the window becomes an +icon when minimised, such as Windows 3.1 or most X Window System +setups; but in the Windows 95-like user interface it isn't as +applicable. + +By default, PuTTY only uses the server-supplied \e{window} title, and +ignores the icon title entirely. If for some reason you want to see +both titles, check the box marked \q{Separate window and icon titles}. +If you do this, PuTTY's window title and Taskbar caption will +change into the server-supplied icon title if you minimise the PuTTY +window, and change back to the server-supplied window title if you +restore it. (If the server has not bothered to supply a window or +icon title, none of this will happen.) + \S{config-warnonclose} \q{Warn before closing window} \cfg{winhelp-topic}{behaviour.closewarn} @@ -1962,7 +2005,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 +2014,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 +2053,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 @@ -2124,7 +2170,7 @@ This is an SSH2-specific bug. \cfg{winhelp-topic}{ssh.bugs.derivekey2} -Versions below 2.1.0 of the SSH server software from \cw{ssh.com} +Versions below 2.0.11 of the SSH server software from \cw{ssh.com} compute the keys for the session encryption incorrectly. This problem can cause various error messages, such as \q{Incoming packet was garbled on decryption}, or possibly even \q{Out of memory}.