+++ /dev/null
-\define{versionidgs} \versionid $Id: gs.but 6815 2006-08-28 10:35:12Z simon $\r
-\r
-\C{gs} Getting started with PuTTY\r
-\r
-This chapter gives a quick guide to the simplest types of\r
-interactive login session using PuTTY.\r
-\r
-\H{gs-insecure} \ii{Starting a session}\r
-\r
-When you start PuTTY, you will see a \i{dialog box}. This dialog box\r
-allows you to control everything PuTTY can do. See \k{config} for\r
-details of all the things you can control.\r
-\r
-You don't usually need to change most of the configuration options.\r
-To start the simplest kind of session, all you need to do is to\r
-enter a few basic parameters.\r
-\r
-In the \q{Host Name} box, enter the Internet \i{host name} of the server\r
-you want to connect to. You should have been told this by the\r
-provider of your login account.\r
-\r
-Now select a login \i{protocol} to use, from the \q{Connection type}\r
-buttons. For a login session, you should select \i{Telnet},\r
-\i{Rlogin} or \i{SSH}. See \k{which-one} for a description of the\r
-differences between the three protocols, and advice on which one to\r
-use. The fourth protocol, \I{raw protocol}\e{Raw}, is not used for\r
-interactive login sessions; you would usually use this for debugging\r
-other Internet services (see \k{using-rawprot}). The fifth option,\r
-\e{Serial}, is used for connecting to a local serial line, and works\r
-somewhat differently: see \k{using-serial} for more information on\r
-this.\r
-\r
-When you change the selected protocol, the number in the \q{Port}\r
-box will change. This is normal: it happens because the various\r
-login services are usually provided on different network ports by\r
-the server machine. Most servers will use the standard port numbers,\r
-so you will not need to change the port setting. If your server\r
-provides login services on a non-standard port, your system\r
-administrator should have told you which one. (For example, many\r
-\i{MUDs} run Telnet service on a port other than 23.)\r
-\r
-Once you have filled in the \q{Host Name}, \q{Protocol}, and\r
-possibly \q{Port} settings, you are ready to connect. Press the\r
-\q{Open} button at the bottom of the dialog box, and PuTTY will\r
-begin trying to connect you to the server.\r
-\r
-\H{gs-hostkey} \ii{Verifying the host key} (SSH only)\r
-\r
-If you are not using the \i{SSH} protocol, you can skip this\r
-section.\r
-\r
-If you are using SSH to connect to a server for the first time, you\r
-will probably see a message looking something like this:\r
-\r
-\c The server's host key is not cached in the registry. You\r
-\c have no guarantee that the server is the computer you\r
-\c think it is.\r
-\c The server's rsa2 key fingerprint is:\r
-\c ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a\r
-\c If you trust this host, hit Yes to add the key to\r
-\c PuTTY's cache and carry on connecting.\r
-\c If you want to carry on connecting just once, without\r
-\c adding the key to the cache, hit No.\r
-\c If you do not trust this host, hit Cancel to abandon the\r
-\c connection.\r
-\r
-This is a feature of the SSH protocol. It is designed to protect you\r
-against a network attack known as \i\e{spoofing}: secretly\r
-redirecting your connection to a different computer, so that you\r
-send your password to the wrong machine. Using this technique, an\r
-attacker would be able to learn the password that guards your login\r
-account, and could then log in as if they were you and use the\r
-account for their own purposes.\r
-\r
-To prevent this attack, each server has a unique identifying code,\r
-called a \e{host key}. These keys are created in a way that prevents\r
-one server from forging another server's key. So if you connect to a\r
-server and it sends you a different host key from the one you were\r
-expecting, PuTTY can warn you that the server may have been switched\r
-and that a spoofing attack might be in progress.\r
-\r
-PuTTY records the host key for each server you connect to, in the\r
-Windows \i{Registry}. Every time you connect to a server, it checks\r
-that the host key presented by the server is the same host key as it\r
-was the last time you connected. If it is not, you will see a\r
-warning, and you will have the chance to abandon your connection\r
-before you type any private information (such as a password) into\r
-it.\r
-\r
-However, when you connect to a server you have not connected to\r
-before, PuTTY has no way of telling whether the host key is the\r
-right one or not. So it gives the warning shown above, and asks you\r
-whether you want to \I{trusting host keys}trust this host key or\r
-not.\r
-\r
-Whether or not to trust the host key is your choice. If you are\r
-connecting within a company network, you might feel that all the\r
-network users are on the same side and spoofing attacks are\r
-unlikely, so you might choose to trust the key without checking it.\r
-If you are connecting across a hostile network (such as the\r
-Internet), you should check with your system administrator, perhaps\r
-by telephone or in person. (Some modern servers have more than one\r
-host key. If the system administrator sends you more than one\r
-\I{host key fingerprint}fingerprint, you should make sure the one\r
-PuTTY shows you is on the list, but it doesn't matter which one it is.)\r
-\r
-\# FIXME: this is all very fine but of course in practice the world\r
-doesn't work that way. Ask the team if they have any good ideas for\r
-changes to this section!\r
-\r
-\H{gs-login} \ii{Logging in}\r
-\r
-After you have connected, and perhaps verified the server's host\r
-key, you will be asked to log in, probably using a \i{username} and\r
-a \i{password}. Your system administrator should have provided you\r
-with these. Enter the username and the password, and the server\r
-should grant you access and begin your session. If you have\r
-\I{mistyping a password}mistyped your password, most servers will\r
-give you several chances to get it right.\r
-\r
-If you are using SSH, be careful not to type your username wrongly,\r
-because you will not have a chance to correct it after you press\r
-Return; many SSH servers do not permit you to make two login attempts\r
-using \i{different usernames}. If you type your username wrongly, you\r
-must close PuTTY and start again.\r
-\r
-If your password is refused but you are sure you have typed it\r
-correctly, check that Caps Lock is not enabled. Many login servers,\r
-particularly Unix computers, treat upper case and lower case as\r
-different when checking your password; so if Caps Lock is on, your\r
-password will probably be refused.\r
-\r
-\H{gs-session} After logging in\r
-\r
-After you log in to the server, what happens next is up to the\r
-server! Most servers will print some sort of login message and then\r
-present a \i{prompt}, at which you can type\r
-\I{commands on the server}commands which the\r
-server will carry out. Some servers will offer you on-line help;\r
-others might not. If you are in doubt about what to do next, consult\r
-your system administrator.\r
-\r
-\H{gs-logout} \ii{Logging out}\r
-\r
-When you have finished your session, you should log out by typing\r
-the server's own logout command. This might vary between servers; if\r
-in doubt, try \c{logout} or \c{exit}, or consult a manual or your\r
-system administrator. When the server processes your logout command,\r
-the PuTTY window should close itself automatically.\r
-\r
-You \e{can} close a PuTTY session using the \i{Close button} in the\r
-window border, but this might confuse the server - a bit like\r
-hanging up a telephone unexpectedly in the middle of a conversation.\r
-We recommend you do not do this unless the server has stopped\r
-responding to you and you cannot close the window any other way.\r
OSDN Git Service
