From 63e0c66739764cc2efa2dbe197af6cf9ec0e1c60 Mon Sep 17 00:00:00 2001 From: Lars Brinkhoff Date: Thu, 4 Apr 2019 15:48:56 +0200 Subject: [PATCH] Documentation for SUPDUP. --- doc/config.but | 56 ++++++++++++++++++++++++++++++++++++++++++------ doc/faq.but | 4 ++-- doc/index.but | 14 ++++++------ doc/intro.but | 36 +++++++++++++++---------------- doc/man-putt.but | 6 +++--- doc/using.but | 26 ++++++++++++++++++++-- 6 files changed, 103 insertions(+), 39 deletions(-) diff --git a/doc/config.but b/doc/config.but index 355ef8bc..4ecf618c 100644 --- a/doc/config.but +++ b/doc/config.but @@ -29,14 +29,16 @@ network connection. \lcont{ \b See \k{which-one} for a summary of the -differences between the network remote login protocols SSH, Telnet and -Rlogin. +differences between the network remote login protocols SSH, Telnet, +Rlogin, and SUPDUP. \b See \k{using-rawprot} for an explanation of \q{raw} connections. \b See \k{using-serial} for information about using a serial line. +\b See \k{using-supdup} for information about using SUPDUP. + \b The \q{Bare ssh-connection} option in the \q{Connection type} box is experimental, for specialist uses, and servers for it are not widely available. @@ -44,11 +46,11 @@ widely available. } \b The \q{Port} box lets you specify which \i{port number} on the -server to connect to. If you select Telnet, Rlogin, or SSH, this box -will be filled in automatically to the usual value, and you will -only need to change it if you have an unusual server. If you select -Raw mode, you will almost certainly need to fill in the \q{Port} box -yourself. +server to connect to. If you select Telnet, Rlogin, SUPDUP, or SSH, +this box will be filled in automatically to the usual value, and you +will only need to change it if you have an unusual server. If you +select Raw mode, you will almost certainly need to fill in the +\q{Port} box yourself. If you select \q{Serial} from the \q{Connection type} radio buttons, the \q{Host Name} and \q{Port} boxes are replaced by \q{Serial line} @@ -2217,6 +2219,46 @@ PuTTY should claim you have, in case it doesn't match your \i{Windows user name} (or in case you didn't bother to set up a Windows user name). +\H{config-supdup} The SUPDUP panel + +The \i{SUPDUP} panel allows you to configure options that only apply +to SUPDUP sessions. + +\S{supdup-location} \q{Location string} + +In SUPDUP, the client sends a piece of text of its choice to the +server giving the user's location. This is typically displayed in +lists of logged-in users. + +By default, PuTTY just defaults this to "The Internet". If you want +your location to show up as something more specific, you can configure +it here. + +\S{supdup-ascii} \q{Extended ASCII Character set} + +This declares what kind of character set extension your terminal +supports. If the server supports it, it will send text using that +character set. \q{None} means the standard 95 printable ASCII +characters. \q{ITS} means ASCII extended with printable characters in +the control character range. This character set is documented in the +SUPDUP protocol definition. \q{WAITS} is similar to \q{ITS} but uses +some alternative characters in the extended set: most prominently, it +will display arrows instead of \c{^} and \c{_}, and \c{\}} instead of +\c{~}. \q{ITS} extended ASCII is used by ITS and Lisp machines, +whilst \q{WAITS} is only used by the WAITS operating system from the +Stanford AI Laboratory. + +\S{supdup-more} \q{**MORE** processing} + +When **MORE** processing is enabled, the server causes output to pause +at the bottom of the screen, until a space is typed. + +\S{supdup-scroll} \q{Terminal scrolling} + +This controls whether the terminal will perform scrolling then the +cursor goes below the last line, or if the cursor will return to the +first line. + \H{config-ssh} The SSH panel The \i{SSH} panel allows you to configure options that only apply to diff --git a/doc/faq.but b/doc/faq.but index 8977703d..fcadaa0e 100644 --- a/doc/faq.but +++ b/doc/faq.but @@ -7,8 +7,8 @@ appendix in the manual. \S{faq-what}{Question} What is PuTTY? -PuTTY is a client program for the SSH, Telnet and Rlogin network -protocols. +PuTTY is a client program for the SSH, Telnet, Rlogin, and SUPDUP +network protocols. These protocols are all used to run a remote session on a computer, over a network. PuTTY implements the client end of that session: the diff --git a/doc/index.but b/doc/index.but index da6d083a..29acf109 100644 --- a/doc/index.but +++ b/doc/index.but @@ -40,18 +40,18 @@ \IM{different usernames}{changes of username} login names, different \IM{different usernames}{changes of username} account names, different -\IM{differences between SSH, Telnet and Rlogin} differences between +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} differences between SSH, Telnet and Rlogin -\IM{differences between SSH, Telnet and Rlogin} protocols, +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} protocols, differences between -\IM{differences between SSH, Telnet and Rlogin} SSH, differences +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} SSH, differences from Telnet and Rlogin -\IM{differences between SSH, Telnet and Rlogin} Telnet, differences +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} Telnet, differences from SSH and Rlogin -\IM{differences between SSH, Telnet and Rlogin} Rlogin, differences +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} Rlogin, differences from SSH and Telnet -\IM{differences between SSH, Telnet and Rlogin} selecting a protocol -\IM{differences between SSH, Telnet and Rlogin} choosing a protocol +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} selecting a protocol +\IM{differences between SSH, Telnet, Rlogin and SUPDUP} choosing a protocol \IM{MUD}{MUDs} MUDs diff --git a/doc/intro.but b/doc/intro.but index 5d4c3f76..ad85ae49 100644 --- a/doc/intro.but +++ b/doc/intro.but @@ -1,14 +1,14 @@ \C{intro} Introduction to PuTTY -PuTTY is a free SSH, Telnet and Rlogin client for Windows +PuTTY is a free SSH, Telnet, Rlogin and SUPDUP client for Windows systems. -\H{you-what} What are SSH, Telnet and Rlogin? +\H{you-what} What are SSH, Telnet, Rlogin and SUPDUP? -If you already know what SSH, Telnet and Rlogin are, you can safely -skip on to the next section. +If you already know what SSH, Telnet, Rlogin and SUPDUP are, you can +safely skip on to the next section. -SSH, Telnet and Rlogin are three ways of doing the same thing: +SSH, Telnet, Rlogin and SUPDUP are four ways of doing the same thing: logging in to a multi-user computer from another computer, over a network. @@ -22,19 +22,19 @@ at the same machine you are typing commands to. The commands, and responses, can be sent over a network, so you can sit at one computer and give commands to another one, or even to more than one. -SSH, Telnet and Rlogin are \i\e{network protocols} that allow you to -do this. On the computer you sit at, you run a \i\e{client}, which -makes a network connection to the other computer (the \i\e{server}). -The network connection carries your keystrokes and commands from the -client to the server, and carries the server's responses back to -you. +SSH, Telnet, Rlogin and SUPDUP are \i\e{network protocols} that allow +you to do this. On the computer you sit at, you run a \i\e{client}, +which makes a network connection to the other computer (the +\i\e{server}). The network connection carries your keystrokes and +commands from the client to the server, and carries the server's +responses back to you. These protocols can also be used for other types of keyboard-based interactive session. In particular, there are a lot of bulletin boards, \i{talker systems} and \i{MUDs} (Multi-User Dungeons) which support access using Telnet. There are even a few that support SSH. -You might want to use SSH, Telnet or Rlogin if: +You might want to use SSH, Telnet, Rlogin or SUPDUP if: \b you have an account on a Unix or VMS system which you want to be able to access from somewhere else @@ -47,22 +47,22 @@ your commands for you.) \b you want to use a \i{bulletin board system}, talker or MUD which can be accessed using Telnet. -You probably do \e{not} want to use SSH, Telnet or Rlogin if: +You probably do \e{not} want to use SSH, Telnet, Rlogin, or SUPDUP if: \b you only use Windows. Windows computers have their own ways of networking between themselves, and unless you are doing something fairly unusual, you will not need to use any of these remote login protocols. -\H{which-one} How do SSH, Telnet and Rlogin differ? +\H{which-one} How do SSH, Telnet, Rlogin and SUPDUP differ? -This list summarises some of the \i{differences between SSH, Telnet -and Rlogin}. +This list summarises some of the \i{differences between SSH, Telnet, +Rlogin and SUPDUP}. \b SSH (which stands for \q{\i{secure shell}}) is a recently designed, high-security protocol. It uses strong cryptography to protect your -connection against eavesdropping, hijacking and other attacks. Telnet -and Rlogin are both older protocols offering minimal security. +connection against eavesdropping, hijacking and other attacks. Telnet, +Rlogin and SUPDUP are all older protocols offering minimal security. \b SSH and Rlogin both allow you to \I{passwordless login}log in to the server without having to type a password. (Rlogin's method of doing this is diff --git a/doc/man-putt.but b/doc/man-putt.but index cb7cca47..45dfd50f 100644 --- a/doc/man-putt.but +++ b/doc/man-putt.but @@ -4,7 +4,7 @@ \S{putty-manpage-name} NAME -\cw{putty} - GUI SSH, Telnet and Rlogin client for X +\cw{putty} - GUI SSH, Telnet, Rlogin and SUPDUP client for X \S{putty-manpage-synopsis} SYNOPSIS @@ -13,8 +13,8 @@ \S{putty-manpage-description} DESCRIPTION -\cw{putty} is a graphical SSH, Telnet and Rlogin client for X. It is -a direct port of the Windows SSH client of the same name. +\cw{putty} is a graphical SSH, Telnet, Rlogin and SUPDUP client for +X. It is a direct port of the Windows SSH client of the same name. \S{putty-manpage-options} OPTIONS diff --git a/doc/using.but b/doc/using.but index 82a9033a..a56abc8b 100644 --- a/doc/using.but +++ b/doc/using.but @@ -582,6 +582,27 @@ connection to notify the other that the connection is finished. Therefore, PuTTY in serial mode will remain connected until you close the window using the close button. +\H{using-supdup} Connecting using the SUPDUP protocol + +PuTTY can use the SUPDUP protocol to connect to a server. SUPDUP is a +login protocol used mainly by PDP-10 and Lisp machines during the +period 1975-1990. Like Telnet and Rlogin, it is unsecured, so modern +systems almost never support it. + +To make a connection of this type, select \q{SUPDUP} from the +\q{Connection type} radio buttons on the \q{Session} panel (see +\k{config-hostname}). For further configuration options (character +set, more processing, scrolling), you can use the \q{SUPDUP} +configuration panel (see \k{config-supdup}). + +The SUPDUP protocol does not support changing the terminal dimensions, +so this capability is disabled during a SUPDUP session. + +SUPDUP provides no well defined means for one end of the connection to +notify the other that the connection is finished. Therefore, PuTTY in +SUPDUP mode will remain connected until you close the window using the +close button. + \H{using-cmdline} The PuTTY command line PuTTY can be made to do various things without user intervention by @@ -782,8 +803,9 @@ security. If you possibly can, we recommend you set up public-key authentication instead. See \k{pubkey} for details. Note that the \c{-pw} option only works when you are using the SSH -protocol. Due to fundamental limitations of Telnet and Rlogin, these -protocols do not support automated password authentication. +protocol. Due to fundamental limitations of Telnet, Rlogin, and +SUPDUP, these protocols do not support automated password +authentication. \S2{using-cmdline-agentauth} \i\c{-agent} and \i\c{-noagent}: control use of Pageant for authentication