X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/37ca32ed18b3e104c1056713f5112b90c6547e89..c725e24c2ffb016d5a86654f8612cf8c6e33e346:/doc/config.but diff --git a/doc/config.but b/doc/config.but index 37c959cc..768610af 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.52 2003/01/27 23:03:30 simon Exp $ +\versionid $Id: config.but,v 1.59 2003/03/07 09:03:11 simon Exp $ \C{config} Configuring PuTTY @@ -622,10 +622,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 +638,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} @@ -856,6 +856,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 +899,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 +934,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} @@ -1497,7 +1513,7 @@ and your SOCKS 4 server cannot deal with it, this might be why. If your proxy requires authentication, you can enter a username and a password in the \q{Username} and \q{Password} boxes. -Authentication is not supported for all forms of proxy: +Authentication is not fully supported for all forms of proxy: \b Username and password authentication is supported for HTTP proxies and SOCKS 5 proxies. @@ -1531,7 +1547,7 @@ password you specify. To get a literal \c{%} sign, enter \c{%%}. If the Telnet proxy server prompts for a username and password before commands can be sent, you can use a command such as: -\c %user\\n%pass\\nconnect %host %port\\n +\c %user\n%pass\nconnect %host %port\n This will send your username and password as the first two lines to the proxy, followed by a command to connect to the desired host and @@ -2124,7 +2140,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}. @@ -2172,6 +2188,24 @@ workaround, you need to enable it manually. This is an SSH2-specific bug. +\S{config-ssh-bug-pksessid2} \q{Misuses the session ID in PK auth} + +\cfg{winhelp-topic}{ssh.bugs.pksessid2} + +Versions below 2.3 of OpenSSH require SSH2 public-key authentication +to be done slightly differently: the data to be signed by the client +contains the session ID formatted in a different way. If public-key +authentication mysteriously does not work but the Event Log (see +\k{using-eventlog}) thinks it has successfully sent a signature, it +might be worth enabling the workaround for this bug to see if it +helps. + +If this bug is detected, PuTTY will sign data in the way OpenSSH +expects. If this bug is enabled when talking to a correct server, +SSH2 public-key authentication will fail. + +This is an SSH2-specific bug. + \H{config-file} Storing configuration in a file PuTTY does not currently support storing its configuration in a file