-\versionid $Id: gs.but,v 1.8 2004/09/17 14:26:39 jacob Exp $
+\define{versionidgs} \versionid $Id$
\C{gs} Getting started with PuTTY
\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.
\c The server's host key is not cached in the registry. You
\c have no guarantee that the server is the computer you
\c think it is.
-\c The server's key fingerprint is:
+\c The server's rsa2 key fingerprint is:
\c ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a
\c If you trust this host, hit Yes to add the key to
\c PuTTY's cache and carry on connecting.
Internet), you should check with your system administrator, perhaps
by telephone or in person. (Some modern 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.)
\# 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
If you are using SSH, be careful not to type your username wrongly,
because you will not have a chance to correct it after you press
-Return. This is an unfortunate feature of the SSH protocol: it does
-not allow you to make two login attempts using \i{different
-usernames}. If you type your username wrongly, you must close PuTTY
-and start again.
+Return; many SSH servers do not permit you to make two login attempts
+using \i{different usernames}. If you type your username wrongly, you
+must close PuTTY and start again.
If your password is refused but you are sure you have typed it
correctly, check that Caps Lock is not enabled. Many login servers,
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 / u / mdw / putty / blobdiff