-\versionid $Id: gs.but,v 1.9 2004/10/24 16:24:58 jacob Exp $
-
\C{gs} Getting started with PuTTY
This chapter gives a quick guide to the simplest types of
\H{gs-insecure} \ii{Starting a session}
-When you start PuTTY, you will see a dialog box. This dialog box
+When you start PuTTY, you will see a \i{dialog box}. This dialog box
allows you to control everything PuTTY can do. See \k{config} for
details of all the things you can control.
To start the simplest kind of session, all you need to do is to
enter a few basic parameters.
-In the \q{Host Name} box, enter the Internet host name of the server
+In the \q{Host Name} box, enter the Internet \i{host name} of the server
you want to connect to. You should have been told this by the
provider of your login account.
-Now select a login \i{protocol} to use, from the \q{Protocol}
+Now select a login \i{protocol} to use, from the \q{Connection type}
buttons. For a login session, you should select \i{Telnet},
\i{Rlogin} or \i{SSH}. See \k{which-one} for a description of the
differences between the three protocols, and advice on which one to
use. The fourth protocol, \I{raw protocol}\e{Raw}, is not used for
interactive login sessions; you would usually use this for debugging
-other Internet services (see \k{using-rawprot}).
+other Internet services (see \k{using-rawprot}). The fifth option,
+\e{Serial}, is used for connecting to a local serial line, and works
+somewhat differently: see \k{using-serial} for more information on
+this.
When you change the selected protocol, the number in the \q{Port}
box will change. This is normal: it happens because the various
\q{Open} button at the bottom of the dialog box, and PuTTY will
begin trying to connect you to the server.
-\H{gs-hostkey} \i{Verifying the host key} (SSH only)
+\H{gs-hostkey} \ii{Verifying the host key} (SSH only)
If you are not using the \i{SSH} protocol, you can skip this
section.
expecting, PuTTY can warn you that the server may have been switched
and that a spoofing attack might be in progress.
-PuTTY records the host key for each server you connect to, in the
-Windows \i{Registry}. Every time you connect to a server, it checks
-that the host key presented by the server is the same host key as it
-was the last time you connected. If it is not, you will see a
-warning, and you will have the chance to abandon your connection
-before you type any private information (such as a password) into
-it.
+PuTTY \I{host key cache}records the host key for each server you
+connect to, in the Windows \i{Registry}. Every time you connect to a
+server, it checks that the host key presented by the server is the
+same host key as it was the last time you connected. If it is not,
+you will see a warning, and you will have the chance to abandon your
+connection before you type any private information (such as a
+password) into it.
However, when you connect to a server you have not connected to
before, PuTTY has no way of telling whether the host key is the
unlikely, so you might choose to trust the key without checking it.
If you are connecting across a hostile network (such as the
Internet), you should check with your system administrator, perhaps
-by telephone or in person. (Some modern servers have more than one
+by telephone or in person. (Many servers have more than one
host key. If the system administrator sends you more than one
-fingerprint, you should make sure the one PuTTY shows you is on the
-list, but it doesn't matter which one it is.)
+\I{host key fingerprint}fingerprint, you should make sure the one
+PuTTY shows you is on the list, but it doesn't matter which one it is.)
+
+See \k{config-ssh-hostkey} for advanced options for managing host keys.
\# FIXME: this is all very fine but of course in practice the world
doesn't work that way. Ask the team if they have any good ideas for
After you log in to the server, what happens next is up to the
server! Most servers will print some sort of login message and then
-present a \i{prompt}, at which you can type commands which the
+present a \i{prompt}, at which you can type
+\I{commands on the server}commands which the
server will carry out. Some servers will offer you on-line help;
others might not. If you are in doubt about what to do next, consult
your system administrator.
projects / PuTTY.git / blobdiff