]> git.ipfire.org Git - people/ms/putty.git/blame - doc/intro.but
Add search to connection list box.
[people/ms/putty.git] / doc / intro.but
CommitLineData
1c1af145 1\define{versionidintro} \versionid $Id$
2
3\C{intro} Introduction to PuTTY
4
5PuTTY is a free SSH, Telnet and Rlogin client for 32-bit Windows
6systems.
7
8\H{you-what} What are SSH, Telnet and Rlogin?
9
10If you already know what SSH, Telnet and Rlogin are, you can safely
11skip on to the next section.
12
13SSH, Telnet and Rlogin are three ways of doing the same thing:
14logging in to a multi-user computer from another computer, over a
15network.
16
17Multi-user operating systems, such as Unix and VMS, usually present
18a \i{command-line interface} to the user, much like the \q{\i{Command
19Prompt}} or \q{\i{MS-DOS Prompt}} in Windows. The system prints a
20prompt, and you type commands which the system will obey.
21
22Using this type of interface, there is no need for you to be sitting
23at the same machine you are typing commands to. The commands, and
24responses, can be sent over a network, so you can sit at one
25computer and give commands to another one, or even to more than one.
26
27SSH, Telnet and Rlogin are \i\e{network protocols} that allow you to
28do this. On the computer you sit at, you run a \i\e{client}, which
29makes a network connection to the other computer (the \i\e{server}).
30The network connection carries your keystrokes and commands from the
31client to the server, and carries the server's responses back to
32you.
33
34These protocols can also be used for other types of keyboard-based
35interactive session. In particular, there are a lot of bulletin
36boards, \i{talker systems} and \i{MUDs} (Multi-User Dungeons) which support
37access using Telnet. There are even a few that support SSH.
38
39You might want to use SSH, Telnet or Rlogin if:
40
41\b you have an account on a Unix or VMS system which you want to be
42able to access from somewhere else
43
44\b your Internet Service Provider provides you with a login account
45on a \i{web server}. (This might also be known as a \i\e{shell account}.
46A \e{shell} is the program that runs on the server and interprets
47your commands for you.)
48
49\b you want to use a \i{bulletin board system}, talker or MUD which can
50be accessed using Telnet.
51
52You probably do \e{not} want to use SSH, Telnet or Rlogin if:
53
54\b you only use Windows. Windows computers have their own
55ways of networking between themselves, and unless you are doing
56something fairly unusual, you will not need to use any of these
57remote login protocols.
58
59\H{which-one} How do SSH, Telnet and Rlogin differ?
60
61This list summarises some of the \i{differences between SSH, Telnet
62and Rlogin}.
63
64\b SSH (which stands for \q{\i{secure shell}}) is a recently designed,
65high-security protocol. It uses strong cryptography to protect your
66connection against eavesdropping, hijacking and other attacks. Telnet
67and Rlogin are both older protocols offering minimal security.
68
69\b SSH and Rlogin both allow you to \I{passwordless login}log in to the
70server without having to type a password. (Rlogin's method of doing this is
71insecure, and can allow an attacker to access your account on the
72server. SSH's method is much more secure, and typically breaking the
73security requires the attacker to have gained access to your actual
74client machine.)
75
76\b SSH allows you to connect to the server and automatically send a
77command, so that the server will run that command and then
78disconnect. So you can use it in automated processing.
79
80The Internet is a hostile environment and security is everybody's
81responsibility. If you are connecting across the open Internet, then
82we recommend you use SSH. If the server you want to connect to
83doesn't support SSH, it might be worth trying to persuade the
84administrator to install it.
85
86If your client and server are both behind the same (good) firewall,
87it is more likely to be safe to use Telnet or Rlogin, but we still
88recommend you use SSH.