[u/mdw/putty] / doc / intro.but

\versionid $Id: intro.but,v 1.4 2001/11/25 16:57:45 simon Exp $

\C{intro} Introduction to PuTTY

PuTTY is a free SSH, Telnet and Rlogin client for 32-bit Windows
systems.

\H{you-what} What are SSH, Telnet and Rlogin?

If you already know what SSH, Telnet and Rlogin are, you can safely
skip on to the next section.

SSH, Telnet and Rlogin are three ways of doing the same thing:
logging in to a multi-user computer from another computer, over a
network.

Multi-user operating systems, such as Unix and VMS, usually present
a command-line interface to the user, much like the \q{Command
Prompt} or \q{MS-DOS Prompt} in Windows. The system prints a prompt,
and you type commands which the system will obey.

Using this type of interface, there is no need for you to be sitting
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 \e{network protocols} that allow you to
do this. On the computer you sit at, you run a \e{client}, which
makes a network connection to the other computer (the \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, talker systems and 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:

\b you have an account on a Unix or VMS system which you want to be
able to access from somewhere else

\b your Internet Service Provider provides you with a login account
on a web server. (This might also be known as a \e{shell account}.
A \e{shell} is the program that runs on the server and interprets
your commands for you.)

\b you want to use a 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:

\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?

This list summarises some of the differences between SSH, Telnet and
Rlogin.

\b SSH 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.

\b Telnet allows you to pass some settings on to the server, such as
environment variables. (These control various aspects of the
server's behaviour. You can usually set them by entering commands
into the server once you're connected, but it's easier to have
Telnet do it automatically.) SSH and Rlogin do not support this.
However, most modern Telnet servers don't allow it either, because
it has been a constant source of security problems.

\b SSH and Rlogin both allow you to log in to the server without
having to type a password. (Rlogin's method of doing this is
insecure, and can allow an attacker to access your account on the
server. SSH's method is much more secure, and typically breaking the
security requires the attacker to have gained access to your actual
client machine.)

\b SSH allows you to connect to the server and automatically send a
command, so that the server will run that command and then
disconnect. So you can use it in automated processing.

The Internet is a hostile environment and security is everybody's
responsibility. If you are connecting across the open Internet, then
we recommend you use SSH. If the server you want to connect to
doesn't support SSH, it might be worth trying to persuade the
administrator to install it.

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