mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-07-02 03:52:49 -05:00
Tweaks to SUPDUP documentation.
Including noting that it can't be used with Plink, and better indexing.
This commit is contained in:
@ -1,14 +1,14 @@
|
||||
\C{intro} Introduction to PuTTY
|
||||
|
||||
PuTTY is a free SSH, Telnet, Rlogin and SUPDUP client for Windows
|
||||
PuTTY is a free SSH, Telnet, Rlogin, and SUPDUP client for Windows
|
||||
systems.
|
||||
|
||||
\H{you-what} What are SSH, Telnet, Rlogin and SUPDUP?
|
||||
\H{you-what} What are SSH, Telnet, Rlogin, and SUPDUP?
|
||||
|
||||
If you already know what SSH, Telnet, Rlogin and SUPDUP are, you can
|
||||
If you already know what SSH, Telnet, Rlogin, and SUPDUP are, you can
|
||||
safely skip on to the next section.
|
||||
|
||||
SSH, Telnet, Rlogin and SUPDUP are four 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,7 +22,7 @@ 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, Rlogin and SUPDUP are \i\e{network protocols} that allow
|
||||
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
|
||||
@ -34,7 +34,7 @@ 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, Rlogin or SUPDUP 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
|
||||
@ -54,15 +54,15 @@ 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, Rlogin and SUPDUP differ?
|
||||
\H{which-one} How do SSH, Telnet, Rlogin, and SUPDUP differ?
|
||||
|
||||
This list summarises some of the \i{differences between SSH, Telnet,
|
||||
Rlogin and SUPDUP}.
|
||||
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,
|
||||
Rlogin and SUPDUP are all older protocols offering minimal security.
|
||||
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
|
||||
@ -82,5 +82,5 @@ doesn't support SSH, it might be worth trying to persuade the
|
||||
administrator to install it.
|
||||
|
||||
If your client and server are both behind the same (good) firewall,
|
||||
it is more likely to be safe to use Telnet or Rlogin, but we still
|
||||
recommend you use SSH.
|
||||
it is more likely to be safe to use Telnet, Rlogin, or SUPDUP, but we
|
||||
still recommend you use SSH.
|
||||
|
Reference in New Issue
Block a user