X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/48b7c4b2ffea56387468d064a501506ea89ee0e3..f85e6f6edb2c9415bc10bd2015479d72ea8c5ae2:/doc/config.but diff --git a/doc/config.but b/doc/config.but index f52d9fab..1dc0ad45 100644 --- a/doc/config.but +++ b/doc/config.but @@ -1,4 +1,4 @@ -\versionid $Id: config.but,v 1.60 2003/04/05 11:52:42 simon Exp $ +\versionid $Id: config.but,v 1.66 2003/06/25 15:52:29 jacob 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} @@ -1125,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 @@ -1425,8 +1457,8 @@ connection. web server supporting the HTTP \cw{CONNECT} command, as documented in \W{http://www.ietf.org/rfc/rfc2817.txt}{RFC 2817}. -\b Selecting \q{SOCKS} allows you to proxy your connections through -a SOCKS server. +\b Selecting \q{SOCKS 4} or \q{SOCKS 5} allows you to proxy your +connections through a SOCKS server. \b Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine @@ -1555,15 +1587,6 @@ port. Note that if you do not include the \c{%user} or \c{%pass} tokens in the Telnet command, then the \q{Username} and \q{Password} configuration fields will be ignored. -\S{config-proxy-socksver} Selecting the version of the SOCKS protocol - -\cfg{winhelp-topic}{proxy.socksver} - -SOCKS servers exist in two versions: version 5 -(\W{http://www.ietf.org/rfc/rfc1928.txt}{RFC 1928}) and the earlier -version 4. The \q{SOCKS Version} radio buttons allow you to select -which one to use, if you have selected the SOCKS proxy type. - \H{config-telnet} The Telnet panel The Telnet panel allows you to configure options that only apply to @@ -1781,6 +1804,16 @@ you make an SSH connection, PuTTY will search down the list from the top until it finds an algorithm supported by the server, and then use that. +PuTTY currently supports the following algorithms: + +\b AES (Rijndael) - 256, 192, or 128-bit CBC (SSH-2 only) + +\b Blowfish - 128-bit CBC + +\b Triple-DES - 168-bit CBC + +\b Single-DES - 56-bit CBC (see below for SSH-2) + If the algorithm PuTTY finds is below the \q{warn below here} line, you will see a warning box when you make the connection: @@ -2226,7 +2259,7 @@ line options, so it's all automatic. Here is what you need in \c regedit /s putty.reg \c regedit /s puttyrnd.reg \c start /w putty.exe -\c regedit /e puttynew.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTY +\c regedit /ea puttynew.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTY \c copy puttynew.reg putty.reg \c del puttynew.reg \c regedit /s puttydel.reg