?_ˆ–ÿÿÿÿ·š/&;)L4ÿÿOÿÿÿ6Õ²„á²³ƒ'‰ Ⳅq (~¦„^‡ 0tW…[ìe|…Æ y2\†Œ„ &lφW úµÛ†•ƒ 1E½Š>€¨;‹ F{€sÅvˇ ÄÛ¶ Êh–Œ†g v– è8–€´—§Â<û— "»‰Ù¢È ØÆs¦Ì -¥™¦^dÞå¨äƒ5ij(wÑJ¶ ƒoÅsº+‚„G6½ ‚o¿¿>†WÝŒÁg€ Ê6ÊÄ¿×TÇV y÷OÉ/ÚfùÌ€ L%¥Ík†]úÍ;€ /PYÏÀØdbψ çÑ ÷ù0Ô·‰Øk—ÕŒ‘E¹Öž„@ÏØÿ€¾þ^Ù >ŠcÜ¢ƒ óWâÜÕ.ÀàÍ‚¶ÖãaVSæÐ š§žè>¾¿í=ˆ«ßŽïj†@ËÞï •Ü.ó ½T¯ó9„õ/ˆ'wúûÂÝéàý£Y … L;B:Š €ç¡:V…ý@ŠneÇA… /§øA|‡}§B‚îCÖ qýF÷ ·kJ"‡—[K2Š‰§L‰!wƒùN)xƒùN yƒùNþzƒùN{ƒùN„!|ƒùNÜ€!}ƒùN]‡!~ƒùN×"ƒùN†"€ƒùN˜ˆ¢ƒùNË"£ƒùN#¤ƒùNQ #¥ƒùNzƒ#¦ƒùNx‡#§ƒùN7$¨ƒùN9$©ƒùNY$ªƒùNî$«ƒùNú "̓ùN%ƒ$΃ùNõ„$σùN®†$ЃùN&%уùN%ÒƒùNy%ÓƒùN;%ÔƒùNW€%ÕƒùN …%ÖƒùN€$øƒùNü‡%ùƒùNdˆ%úƒùNÕ&ûƒùN&üƒùN&ýƒùN&þƒùNy„&ÿƒùNG‡&„ùN ‰&„ùN‡%#„ùN\'$„ùNï'%„ùNõ'&„ùN ''„ùN'(„ùNB‚')„ùNqƒ'*„ùN…'+„ùN[‡',„ùNL'N„ùNp(O„ùNÊ(P„ùN&(Q„ùNV (R„ùN€(S„ùN(T„ùN‚(U„ùNÒ…(V„ùNr†(W„ùN+‰'y„ùN)z„ùN0){„ùN@ƒ)|„ùN¹‡)}„ùN¨Š)~„ùNž*„ùN˜*€„ùN*„ùN€*‚„ùNoˆ(¤„ùNÎ…*¥„ùN!‡*¦„ùN¥‰*§„ùN+¨„ùNp+©„ùN¼+ª„ùNð +«„ùNF‚+¬„ùN„+­„ùN„*Ï„ùNÚ,ЄùNÛ,Ñ„ùNz,Ò„ùN€,Ó„ùNo,Ô„ùNj„,Õ„ùNJ†,Ö„ùN/ˆ,ׄùN@-Ø„ùN„Š+ú„ùNüû„ùNtü„ùN—ý„ùNS€þ„ùNýƒÿ„ùN£…ùNÒ…ùNFƒ…ùN†…ùN°ŠùNQƒ.±ŠùN0/²ŠùN£/³ŠùN¨‡/´ŠùNš0µŠùNù0¶ŠùNq0·ŠùN€0¸ŠùN2‚0¹ŠùN#.äŠùN”‚03ŒùNÍ-4ŒùNú-5ŒùN -6ŒùNùƒ-7ŒùNÌ„-8ŒùNÝ…-9ŒùN?‡-:ŒùNˆ-;ŒùN».<ŒùN¬-xÄùNyÄùN ‚zÄùN†…{ÄùNJˆ|ÄùN}ÄùN€~ÄùNñÄùN­€ÄùN" ÄùNe£ÄùN¦ƒ¤ÄùNû…¥ÄùNl¦ÄùNF§ÄùNÿ†¨ÄùNZˆ©ÄùNÀªÄùN™«ÄùN¬ÄùNœ€ÎÄùNG‚ÏÄùN€ƒÐÄùNÄ„ÑÄùN<ˆÒÄùNÌÓÄùNûÔÄùNçÕÄùNLÖÄùN€×ÄùN€ùÄùNƒúÄùN¡„ûÄùNh†üÄùNøýÄùN„ þÄùN ÿÄùN÷ ÅùN¸ ÅùN{‡ ÅùNã$ÅùNÉŠ %ÅùNž€xPÿÿ&ÅùN¥'ÅùN>(ÅùNYƒ)ÅùN«*ÅùNãˆ+ÅùNS,ÅùN-ÅùNc OÅùNPÅùN¿QÅùNƒRÅùN­„SÅùN<ˆTÅùN¸UÅùNƒƒVÅùNy„WÅùNQ…XÅùNízÅùN{ÅùN¥|ÅùNw}ÅùN¸~ÅùN(ÅùN €ÅùNÅùNÞ…‚ÅùNq†ƒÅùNÕ‡¥ÅùN¦ÅùN® §ÅùNˆ„¨ÅùN¿…©ÅùN®‡ªÅùN–«ÅùN€ ¬ÅùNˆ­ÅùNЂ®ÅùNÐÅùNÉ…ÑÅùN ˆÒÅùNÓÅùNòÔÅùN0ÕÅùNqÖÅùN ‡×ÅùNÓ‡ØÅùNxˆÙÅùNçƒûÅùN}üÅùNì‚ýÅùNωþÅùN‹ÿÅùNuÆùNú„ÆùN+‰ÆùN®ŠÆùNBÆùNŸ, ÛTJ‚´åU> ïÜ7YÈ6çY½ï´•ZŠ ¥ÙZ ƒ&áÝ\XÚÙI_²‰¢ ²`‚‰dî:a‘䀅aO „QÜc …80«f3 !êøÂkN‰ eHmÓ€ *͈s& ¥àÌsM E@ÁvΆ z?Öw°x²zml{Þ}N Õ‚Þ}„ ô&ÅùN ¾µhArialCourier NewTimes New Roman/&;)F24ÿÿ'ÿÿÿÿCVSPATHPSCPPSFTPPlinkSecure iXplorerWildcards WinCVS$batch files(console window,recursive4scripts8statistics<timestamp@MD˜ˆ­„S€ƒq†—Þ…Q…)†­„S€¸†w¥]Tl!QQÑ=  #CB("btn_about","&About","About()") CB("btn_up","&Up","Contents()")BrowseButtons()PuTTY User Manual°This manual is copyright 2001-2002 Simon Tatham. All rights reserved. You may distribute this documentation under the MIT licence. See appendix C for the licence text in full.g^ÿÿÿÿ FÿÿÿÿR1uÿÿÿÿŸR‰ÇContentsDB("btn_up")7 ‰# €(€€‚ÿPuTTY User Manual¿šRH% €5€˜€‚ÿPuTTY is a free (MIT-licensed) Win32 Telnet and SSH client. This manual documents PuTTY, and its companion utilities PSCP, Plink, Pageant and PuTTYgen.ß´‰'+ $€i€˜€ãäŠùN‰‚ÿThis manual is copyright 2001-2002 Simon Tatham. All rights reserved. You may distribute this documentation under the MIT licence. See appendix C for the licence text in full.V'H}/ .€N€ãÆùN€€€‰‚ÿChapter 1: Introduction to PuTTY[,'Ø/ .€X€ãýÅùN€€€‰‚ÿChapter 2: Getting started with PuTTYL}$/ .€:€ãÆùN€€€‰‚ÿChapter 3: Using PuTTYR#Øv/ .€F€ãûÄùN€€€‰‚ÿChapter 4: Configuring PuTTYf7$Ü/ .€n€ãQÅùN€€€‰‚ÿChapter 5: Using PSCP to transfer files securelyg8vC/ .€p€ã‚ÅùN€€€‰‚ÿChapter 6: Using PSFTP to transfer files securelym>Ü°/ .€|€ãü„ùN€€€‰‚ÿChapter 7: Using the command-line connection tool Plinki:C/ .€t€ãxƒùN€€€‰‚ÿChapter 8: Using public keys for SSH authenticationa2°z/ .€d€ã80«f€€€‰‚ÿChapter 9: Using Pageant for authenticationW(Ñ/ .€P€ã¤ƒùN€€€‰‚ÿChapter 10: Common error messagesKz/ .€8€ãÓƒùN€€€‰‚ÿAppendix A: PuTTY FAQ\-Ñx/ .€Z€ã:ŒùN€€€‰‚ÿAppendix B: Feedback and bug reportingO Ç/ .€@€ãäŠùN€€€‰‚ÿAppendix C: PuTTY Licence{JxB1‰}BËChapter 1: Introduction to PuTTYCBB("btn_up","JI(`',`Top')");EB("btn_up")N%Ç) "€J€€€€‚ÿChapter 1: Introduction to PuTTYpLB$ €˜€˜€‚ÿPuTTY is a free SSH, Telnet and Rlogin client for 32-bit Windows systems.c4c/ .€h€ãûÅùN€€€‰‚ÿSection 1.1: What are SSH, Telnet and Rlogin?h9Ë/ .€r€ãüÅùN€€€‰‚ÿSection 1.2: How do SSH, Telnet and Rlogin differ?Ž]cY 1‹ Ÿì‚Y ´ DSection 1.1: What are SSH, Telnet and Rlogin?CBB("btn_up","JI(`',`t00000000')");EB("btn_up")[2Ë´ ) "€d€€€€‚ÿSection 1.1: What are SSH, Telnet and Rlogin?‡cY ; $ €Æ€˜€‚ÿ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 ‘Command Prompt’ or ‘MS-DOS Prompt’ in Windows. The system prints a prompt, and you type commands which the system will obey.0 ì 9 % €€˜€‚ÿ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.…N ¾7 <€€˜€€€€€€€‚ÿSSH, Telnet and Rlogin are network protocols that allow you to do this. On the computer you sit at, you run a client, which makes a network connection to the other computer (the server). The network connection carries your keystrokes and commands from the client to the server, and carries the server's responses back to you.*9 @% € €˜€‚ÿ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.¾ @ËV2¾b@$ €d€˜€‚ÿYou might want to use SSH, Telnet or Rlogin if:–i @ø@- *€Ò€T˜‘€8‚€ƒ€‚ÿ•you have an account on a Unix or VMS system which you want to be able to access from somewhere elseßb@B: B€¿€T˜‘€8‚€ƒ€€€€€‚ÿ•your Internet Service Provider provides you with a login account on a web server. (This might also be known as a shell account. A shell is the program that runs on the server and interprets your commands for you.)`ø@žB- *€À€T˜‘€8‚€ƒ€‚ÿ•you want to use a bulletin board system, talker or MUD which can be accessed using Telnet.h>BC* $€|€˜€€€‚ÿYou probably do not want to use SSH, Telnet or Rlogin if:ÔžBD. *€©€T˜‘€8‚€ƒ€‚ÿ•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.“bC›D11}ω›DûDÌLSection 1.2: How do SSH, Telnet and Rlogin differ?CBB("btn_up","JI(`',`t00000000')");EB("btn_up")`7DûD) "€n€€€€‚ÿSection 1.2: How do SSH, Telnet and Rlogin differ?sO›DnE$ €ž€˜€‚ÿThis list summarises some of the differences between SSH, Telnet and Rlogin.êûD†F. *€Õ€T˜‘€8‚€ƒ€‚ÿ•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.ë½nEqH. *€{€T˜‘€8‚€ƒ€‚ÿ•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.Š\†FûI. *€¹€T˜‘€8‚€ƒ€‚ÿ•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.)æ¸qHáJ. *€q€T˜‘€8‚€ƒ€‚ÿ•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.H#ûI)L% €G€˜€‚ÿ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.£áJÌL$ €þ€˜€‚ÿ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.€O)LLM1ì‚‹LMŸMÍOChapter 2: Getting started with PuTTYCBB("btn_up","JI(`',`Top')");EB("btn_up")S*ÌLŸM) "€T€€€€‚ÿChapter 2: Getting started with PuTTY‡cLM&N$ €Æ€˜€‚ÿThis chapter gives a quick guide to the simplest types of interactive login session using PuTTY.U&ŸM{N/ .€L€ãþÅùN€€€‰‚ÿSection 2.1: Starting a sessiond5&NßN/ .€j€ãÿÅùN€€€‰‚ÿSection 2.2: Verifying the Host Key (SSH only)M{N,O/ .€<€ãÆùN€€€‰‚ÿSection 2.3: Logging InS$ßNO/ .€H€ãÆùN€€€‰‚ÿSection 2.4: After Logging InN,OÍO/ .€>€ãÆùN€€€‰‚ÿSection 2.5: Logging Out€OOY€1ŽωuY€¦€ç‡SeÍOY€ÍOction 2.1: Starting a sessionCBB("btn_up","JI(`',`t00000003')");EB("btn_up")M$ÍO¦€) "€H€€€€‚ÿSection 2.1: Starting a sessionܱY€‚+ $€c€˜€ãûÄùN‰‚ÿWhen you start PuTTY, you will see a dialog box. This dialog box allows you to control everything PuTTY can do. See chapter 4 for details of all the things you can control.ɤ¦€K‚% €I€˜€‚ÿYou don't usually need to change most of the configuration options. To start the simplest kind of session, all you need to do is to enter a few basic parameters.È£‚ƒ% €G€˜€‚ÿIn the ‘Host Name’ box, enter the Internet host name of the server you want to connect to. You should have been told this by the provider of your login account.°K‚Ä1 0€ÿ€˜€ãüÅùN‰€€‚ÿNow select a login protocol to use, from the ‘Protocol’ buttons. For a login session, you should select Telnet, Rlogin or SSH. See section 1.2 for a description of the differences between the three protocols, and advice on which one to use. The fourth protocol, Raw, is not used for interactive login sessions; you would usually use this for debugging other Internet services.øƒà†% €ñ€˜€‚ÿWhen you change the selected protocol, the number in the ‘Port’ box will change. This is normal: it happens because the various login services are usually provided on different network ports by the server machine. Most servers will use the standard port numbers, so you will not need to change the port setting. If your server provides login services on a non-standard port, your system administrator should have told you which one. (For example, many MUDs run Telnet service on a port other than 23.)âÄç‡% €Å€˜€‚ÿOnce you have filled in the ‘Host Name’, ‘Protocol’, and possibly ‘Port’ settings, you are ready to connect. Press the ‘Open’ button at the bottom of the dialog box, and PuTTY will begin trying to connect you to the server.^à†vˆ1» ‹ú„vˆÒˆ=ÆSection 2.2: Verifying the Host Key (SSH only)CBB("btn_up","JI(`',`t00000003')");EB("btn_up")\3ç‡Òˆ) "€f€€€€‚ÿSection 2.2: Verifying the Host Key (SSH only)hDvˆ:‰$ €ˆ€˜€‚ÿIf you are not using the SSH protocol, you can skip this section.£҈݉$ €þ€˜€‚ÿIf you are using SSH to connect to a server for the first time, you will probably see a message looking something like this:^;:‰;Š# €v€€‚ÿThe server's host key is not cached in the registry. You[8݉–Š# €p€€‚ÿhave no guarantee that the server is the computer you2;ŠÈŠ# €€€‚ÿthink it is.F#–Š‹# €F€€‚ÿThe server's key fingerprint is:b?ÈŠp‹# €~€€‚ÿssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5aW4‹Ç‹# €h€€‚ÿIf you trust this host, hit Yes to add the key toL)p‹Œ# €R€€‚ÿPuTTY's cache and carry on connecting.[8Ç‹nŒ# €p€€‚ÿIf you want to carry on connecting just once, withoutJ'Œ¸Œ# €N€€‚ÿadding the key to the cache, hit No.^;nŒ# €v€€‚ÿIf you do not trust this host, hit Cancel to abandon the2¸ŒH$ €€˜€‚ÿconnection.Ϥ+ $€I€˜€€€‚ÿThis is a feature of the SSH protocol. It is designed to protect you against a network attack known as spoofing: secretly redirecting your connection to a different computer, so that you send your password to the wrong machine. Using this technique, an attacker would be able to learn the password that guards your login account, and could then log in as if they were you and use the account for their own purposes.±†HÔÀ+ $€ €˜€€€‚ÿTo prevent this attack, each server has a unique identifying code, called a host key. These keys are created in a way that prevents one server from forging another server's key. So if youÔÀç‡ connect to a server and it sends you a different host key from the one you were 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 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 right one or not. So it gives the warning shown above, and asks you whether you want to trust this host key or not.›v‡Â=Æ% €í€˜€‚ÿWhether or not to trust the host key is your choice. If you are connecting within a company network, you might feel that all the network users are on the same side and spoofing attacks are 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 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.)xG¢ÃµÆ1Éu+‰µÆúÆ~ËSection 2.3: Logging InCBB("btn_up","JI(`',`t00000003')");EB("btn_up")E=ÆúÆ) "€8€€€€‚ÿSection 2.3: Logging In·’µÆ±È% €%€˜€‚ÿAfter you have connected, and perhaps verified the server's host key, you will be asked to log in, probably using a username and a password. Your system administrator should have provided you with these. Enter the username and the password, and the server should grant you access and begin your session. If you have mistyped your password, most servers will give you several chances to get it right.}XúÆ.Ê% €±€˜€‚ÿ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 different usernames. If you type your username wrongly, you must close PuTTY and start again.P+±È~Ë% €W€˜€‚ÿIf your password is refused but you are sure you have typed it correctly, check that Caps Lock is not enabled. Many login servers, particularly Unix computers, treat upper case and lower case as different when checking your password; so if Caps Lock is on, your password will probably be refused.~M.ÊüË1Ñú„®ŠüËGÌÍÍSection 2.4: After Logging InCBB("btn_up","JI(`',`t00000003')");EB("btn_up")K"~ËGÌ) "€D€€€€‚ÿSection 2.4: After Logging In†aüËÍÍ% €Ã€˜€‚ÿ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 prompt, at which you can type 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.yHGÌFÎ1$+‰B FÎŒÎySection 2.5: Logging OutCBB("btn_up","JI(`',`t00000003')");EB("btn_up")FÍÍŒÎ) "€:€€€€‚ÿSection 2.5: Logging Outq@FÎ 1 0€€˜€€€€€‚ÿWhen you have finished your session, you should log out by typing the server's own logout command. This might vary between servers; if in doubt, try logout or exit, or consult a manual or your system administrator. When the server processes your logout command, the PuTTY window should close itself automatically.ŒÎ ÍÍmBŒÎy+ $€…€˜€€€‚ÿYou can close a PuTTY session using the Close button in the window border, but this might confuse the server - a bit like hanging up a telephone unexpectedly in the middle of a conversation. We recommend you do not do this unless the server has stopped responding to you and you cannot close the window any other way.q@ ê1À®Še ê.ªChapter 3: Using PuTTYCBB("btn_up","JI(`',`Top')");EB("btn_up")Dy.) "€6€€€€‚ÿChapter 3: Using PuTTYá¶ê+ $€m€˜€ãûÄùN‰‚ÿThis chapter provides a general introduction to some more advanced features of PuTTY. For extreme detail and reference purposes, chapter 4 is likely to contain more information.V'.e/ .€N€ãÄùN€€€‰‚ÿSection 3.1: During your sessionf7Ë/ .€n€ã¬ÄùN€€€‰‚ÿSection 3.2: Creating a log file of your sessionl=e7/ .€z€ã£ÄùN€€€‰‚ÿSection 3.3: Altering your character set configuration^/Ë•/ .€^€ã¤ÄùN€€€‰‚ÿSection 3.4: Using X11 forwarding in SSH_07ô/ .€`€ã¥ÄùN€€€‰‚ÿSection 3.5: Using port forwarding in SSH].•Q/ .€\€ã¦ÄùN€€€‰‚ÿSection 3.6: Making raw TCP connectionsY*ôª/ .€T€ã§ÄùN€€€‰‚ÿSection 3.7: The PuTTY command linePQ+1|B +y§Section 3.1: During your sessionCBB("btn_up","JI(`',`t00000009')");EB("btn_up")N%ªy) "€J€€€€‚ÿSection 3.1: During your sessionú+˜% €õ€˜€‚ÿA lot of PuTTY's complexity and features are in the configuration panel. Once you have worked your way through that and started a session, things should be reasonably simple after that. Nevertheless, there are a few more useful features available.].yõ/ .€\€ãxÄùN€€€‰‚ÿSection 3.1.1: Copying and pasting text^/˜S/ .€^€ãyÄùN€€€‰‚ÿSection 3.1.2: Scrolling the screen backT%õ§/ .€J€ãzÄùN€€€‰‚ÿSection 3.1.3: The System menuˆWS/ 1? e ‚ / „ zDSection 3.1.1: Copying and pasting textCBB("btn_up","JI(`',`t00000010')");EB("btn_up")U,§„ ) "€X€€€€‚ÿSection 3.1.1: Copying and pasting text¹”/ = % €)€˜€‚ÿOften in a PuTTY session you will find text on your terminal screen which you want to type in again. Like most other terminal emulators, PuTTY allows you to copy and paste the text rather than having to type it again. Also, copy and paste uses the Windows clipboard, so that you can paste (for example) URLs into a web browser, or paste from a word processor or spreadsheet into your terminal session.Õ„ = + $€«€˜€€€‚ÿPuTTY's copy and paste works entirely with the mouse. In order to copy text to the clipboard, you just click the left mouse button in the terminal window, and drag to select text. When you let go of the button, the text is automatically copied to the clipboard. You do not need to press Ctrl-C or Ctrl-Ins; in fact, if you do press Ctrl-C, PuTTY will send a Ctrl-C character down your session to the server where it will probably cause a process to be interrupted.ŠY= Ç1 0€³€˜€ãÙ“§.‰€€‚ÿPasting is done using the right button (or the middle mouse button, if you have a three-button mouse and have set it up; see section 4.11.3). When you click the right mouse button, PuTTY will read whatever is in the Windows Clipboard and paste it into your session, exactly as if it had been typed at the keyboard. (Therefore, be careful of pasting formatted text into an editor that does automatic indenting; you may find that the spaces pasted from the clipboard plus the spaces added by the editor add up to too many spaces and ruin the formatting. There is nothing PuTTY can do about this.)·†= ŠA1 0€ €˜€ãý@‰€€‚ÿIf you ÇŠA§double-click the left mouse button, PuTTY will select a whole word. If you double-click, hold down the second click, and drag the mouse, PuTTY will select a sequence of whole words. (You can adjust precisely what PuTTY considers to be part of a word; see section 4.11.6.) If you triple-click, or triple-click and drag, then PuTTY will select a whole line or sequence of lines.j?ÇôB+ $€€˜€ã ·kJ‰‚ÿIf you want to select a rectangular region instead of selecting to the end of each line, you can do this by holding down Alt when you make your selection. (You can also configure rectangular selection to be the default, and then holding down Alt gives the normal behaviour instead. See section 4.11.5 for details.)†aŠAzD% €Ã€˜€‚ÿIf you have a middle mouse button, then you can use it to adjust an existing selection if you selected something slightly wrong. (If you have configured the middle mouse button to paste, then the right mouse button does this instead.) Click the button on the screen, and you can pick up the nearest end of the selection and drag it to somewhere else.‰XôBE1„†… EYE‡HSection 3.1.2: Scrolling the screen backCBB("btn_up","JI(`',`t00000010')");EB("btn_up")V-zDYE) "€Z€€€€‚ÿSection 3.1.2: Scrolling the screen backkFEÄF% €€˜€‚ÿPuTTY keeps track of text that has scrolled up off the top of the terminal. So if something appears on the screen that you want to read, but it scrolls too fast and it's gone by the time you try to look for it, you can use the scrollbar on the right side of the window to look back up the session history and find it again.åÀYE©G% €€˜€‚ÿAs well as using the scrollbar, you can also page the scrollback up and down by pressing Shift-PgUp and Shift-PgDn. These are still available if you configure the scrollbar to be invisible.Þ³ÄF‡H+ $€g€˜€ã¨;‹‰‚ÿBy default the last 200 lines scrolled off the top are preserved for you to look at. You can increase (or decrease) this value using the configuration box; see section 4.7.3.N©GI1Q ‚JˆIRIWMSection 3.1.3: The System menuCBB("btn_up","JI(`',`t00000010')");EB("btn_up")L#‡HRI) "€F€€€€‚ÿSection 3.1.3: The System menuñIhJ% €ã€˜€‚ÿIf you click the left mouse button on the icon in the top left corner of PuTTY's window, or click the right mouse button on the title bar, you will see the standard Windows system menu containing items like Minimise, Move, Size and Close.·’RIK% €%€˜€‚ÿPuTTY's system menu contains extra program features in addition to the Windows standard options. These extra menu commands are described below.Z+hJyK/ .€V€ã{ÄùN€€€‰‚ÿSection 3.1.3.1: The PuTTY Event Log\-KÕK/ .€Z€ã|ÄùN€€€‰‚ÿSection 3.1.3.2: Starting new sessionse6yK:L/ .€l€ã}ÄùN€€€‰‚ÿSection 3.1.3.3: Changing your session settings\-ÕK–L/ .€Z€ã~ÄùN€€€‰‚ÿSection 3.1.3.4: Copy All to Clipboardj;:LM/ .€v€ãÄùN€€€‰‚ÿSection 3.1.3.5: Clearing and resetting the terminalW(–LWM/ .€P€ã€ÄùN€€€‰‚ÿSection 3.1.3.6: Full screen mode…TMÜM1¶†…ÜM.Nž€Section 3.1.3.1: The PuTTY Event LogCBB("btn_up","JI(`',`t00000013')");EB("btn_up")R)WM.N) "€R€€€€‚ÿSection 3.1.3.1: The PuTTY Event LogW2ÜM…O% €e€˜€‚ÿIf you choose ‘Event Log’ from the system menu, a small window will pop up in which PuTTY logs significant events during the connection. Most of the events in the log will probably take place during session startup, but a few can occur at any point in the session, and one or two occur right at the end. è.Nž€% €Ñ€˜€‚ÿYou can use the mouse to select one or more lines of the Event Log, and hit the Copy …Ož€WMbutton to copy them to the clipboard. If you are reporting a bug, it's often useful to paste the contents of the Event Log into your bug report.‡V…O%1\Jˆ€%y„Section 3.1.3.2: Starting new sessionsCBB("btn_up","JI(`',`t00000013')");EB("btn_up")T+ž€y) "€V€€€€‚ÿSection 3.1.3.2: Starting new sessionsmI%æ$ €’€˜€‚ÿPuTTY's system menu provides some shortcut ways to start new sessions:§zy‚- *€ô€T˜‘€8‚€ƒ€‚ÿ•Selecting ‘New Session’ will start a completely new instance of PuTTY, and bring up the configuration box as normal.×æ’ƒ. *€¯€T˜‘€8‚€ƒ€‚ÿ•Selecting ‘Duplicate Session’ will start a session with precisely the same options as your current one - connecting to the same host using the same protocol, with all the same terminal settings and everything.ﻂ„4 6€w€T˜‘€8‚€ƒ€ã}§B‰‚ÿ•The ‘Saved Sessions’ submenu gives you quick access to any sets of stored session details you have previously saved. See section 4.1.2 for details of how to create saved sessions._’ƒ…1äñ…n…õ‡Section 3.1.3.3: Changing your session settingsCBB("btn_up","JI(`',`t00000013')");EB("btn_up")]4„n…) "€h€€€€‚ÿSection 3.1.3.3: Changing your session settingsO*…½†% €U€˜€‚ÿIf you select ‘Change Settings’ from the system menu, PuTTY will display a cut-down version of its initial configuration box. This allows you to adjust most properties of your current session. You can change the terminal size, the font, the actions of various keypresses, the colours, and so on.8n…õ‡% €'€˜€‚ÿSome of the options that are available in the main configuration box are not shown in the cut-down Change Settings box. These are usually options which don't make sense to change in the middle of a session (for example, you can't switch from SSH to Telnet in mid-session).‡V½†|ˆ1 €­|ˆЈ†‰Section 3.1.3.4: Copy All to ClipboardCBB("btn_up","JI(`',`t00000013')");EB("btn_up")T+õ‡Ј) "€V€€€€‚ÿSection 3.1.3.4: Copy All to Clipboard¶‘|ˆ†‰% €#€˜€‚ÿThis system menu option provides a convenient way to copy the whole contents of the terminal screen and scrollback to the clipboard in one go.•dЈŠ1èñ" Š}ŠŽSection 3.1.3.5: Clearing and resetting the terminalCBB("btn_up","JI(`',`t00000013')");EB("btn_up")b9†‰}Š) "€r€€€€‚ÿSection 3.1.3.5: Clearing and resetting the terminaløÓŠuŒ% €§€˜€‚ÿThe ‘Clear Scrollback’ option on the system menu tells PuTTY to discard all the lines of text that have been kept after they scrolled off the top of the screen. This might be useful, for example, if you displayed sensitive information and wanted to make sure nobody could look over your shoulder and see it. (Note that this only prevents a casual user from using the scrollbar to view the information; the text is not guaranteed not to still be in PuTTY's memory.)Ži}ŠŽ% €Ó€˜€‚ÿThe ‘Reset Terminal’ option causes a full reset of the terminal emulation. A VT-series terminal is a complex piece of software and can easily get into a state where all the text printed becomes unreadable. (This can happen, for example, if you accidentally output a binary file to your terminal.) If this happens, selecting Reset Terminal should sort it out.‚QuŒ…Ž1»­œ€…ŽÔŽLÁSection 3.1.3.6: Full screen modeCBB("btn_up","JI(`',`t00000013')");EB("btn_up")O&ŽÔŽ) "€L€€€€‚ÿSection 3.1.3.6: Full screen mode¥z…Ž…À+ $€õ€˜€ã¨;‹‰‚ÿIf you find the title bar on a maximised window to be ugly or distracting, you can select Full Screen mode to maximise PuTTY ‘even more’. When you select this, PuTTY will expand to fill the whole screen and its borders, title bar and scrollbar will disappeÔŽ…ÀŽar. (You can configure the scrollbar not to disappear in full-screen mode if you want to keep it; see section 4.7.3.)ǜԎLÁ+ $€9€˜€€€‚ÿWhen you are in full-screen mode, you can still access the system menu if you click the left mouse button in the extreme top left corner of the screen.‘`…ÀÝÁ1§" ¦ƒÝÁ;„ÅSection 3.2: Creating a log file of your sessionCBB("btn_up","JI(`',`t00000009')");EB("btn_up")^5LÁ;Â) "€j€€€€‚ÿSection 3.2: Creating a log file of your sessionÂÝÁýÂ% €;€˜€‚ÿFor some purposes you may find you want to log everything that appears on your screen. You can do this using the ‘Logging’ panel in the configuration box.+;Â(Å% € €˜€‚ÿTo begin a session log, select ‘Change Settings’ from the system menu and go to the Logging panel. Enter a log file name, and select a logging mode. (You can log all session output including the terminal control sequences, or you can just log the printable text. It depends what you want the log for.) Click ‘Apply’ and your log will be started. Later on, you can go back to the Logging panel and select ‘Logging turned off completely’ to stop logging; then PuTTY will close the log file and you can safely read it.\2ý„Å* $€d€˜€ã¢ ²`‰‚ÿSee section 4.2 for more details and options.—f(ÅÆ1Îœ€û…ÆÆéÈSection 3.3: Altering your character set configurationCBB("btn_up","JI(`',`t00000009')");EB("btn_up")d;„ÅÆ) "€v€€€€‚ÿSection 3.3: Altering your character set configurationVÆÈ+ $€­€˜€€€‚ÿIf you find that special characters (accented characters, for example) are not being displayed correctly in your PuTTY session, it may be that PuTTY is interpreting the characters sent by the server according to the wrong character set. There are a lot of different character sets available, so it's entirely possible for this to happen.éÄÆéÈ% €‰€˜€‚ÿIf you click ‘Change Settings’ and look at the ‘Translation’ panel, you should see a large number of character sets which you can select. Now all you need is to find out which of them you want!‰XÈrÉ1㦃lrÉÈÉaSection 3.4: Using X11 forwarding in SSHCBB("btn_up","JI(`',`t00000009')");EB("btn_up")V-éÈÈÉ) "€Z€€€€‚ÿSection 3.4: Using X11 forwarding in SSHCrÉ Ë% €=€˜€‚ÿThe SSH protocol has the ability to securely forward X Window System applications over your encrypted SSH connection, so that you can run an application on the SSH server machine and have it put its windows up on your local machine without sending any X network traffic in the clear.5ÈÉ@Ì% €!€˜€‚ÿIn order to use this feature, you will need an X display server for your Windows machine, such as X-Win32 or Exceed. This will probably install itself as display number 0 on your local machine; if it doesn't, the manual for the X server should tell you what it does do.f5 ˦Í1 0€k€˜€ãwÑJ¶‰€€‚ÿYou should then tick the ‘Enable X11 forwarding’ box in the Tunnels panel (see section 4.19.1) before starting your SSH session. The ‘X display location’ box reads localhost:0 by default, which is the usual display location where your X server will be installed. If that needs changing, then change it. õ@ÌÆÎ+ $€ë€˜€ã{ÄùN‰‚ÿNow you should be able to log in to the SSH server as normal. To check that X forwarding has been successfully negotiated during connection startup, you can check the PuTTY Event Log (see section 3.1.3.1). It should say something like this:S0¦ÍÏ# €`€€‚ÿ2001-12-05 17:22:01 Requesting X11 forwardingQ-ÆÎjÏ$ €Z€˜€‚ÿ2001-12-05 17:22:02 X11 forwarding enabledîÃÏd+ $€‡€˜€€€‚ÿIf the remote system is Unix or Unix-like, you should also be able to see that the DISPLAY environment vjÏdéÈariable has been set to point at display 10 or above on the SSH server machine itself:C jϧ# €@€€‚ÿfred@unixbox:~$ echo $DISPLAY3dÚ$ €€˜€‚ÿunixbox:10.0ª…§„% € €˜€‚ÿIf this works, you should then be able to run X applications in the remote session and have them display their windows on your PC.ݸÚa% €q€˜€‚ÿNote that if your PC X server requires authentication to connect, then PuTTY cannot currently support it. If this is a problem for you, you should mail the authors and give details.ŠY„ë1ôû…FëBëASection 3.5: Using port forwarding in SSHCBB("btn_up","JI(`',`t00000009')");EB("btn_up")W.aB) "€\€€€€‚ÿSection 3.5: Using port forwarding in SSHoJë±% €•€˜€‚ÿThe SSH protocol has the ability to forward arbitrary network connections over your encrypted SSH connection, to avoid the network traffic being sent in clear. For example, you could use this to connect from your home computer to a POP-3 server on a remote machine without your POP-3 password being visible to network sniffers.”pBE$ €à€˜€‚ÿIn order to use port forwarding to connect from your local machine to a port on a remote server, you need to:Ó¥±. *€K€T˜‘€8‚€ƒ€‚ÿ•Choose a port number on your local machine where PuTTY should listen for incoming connections. There are likely to be plenty of unused port numbers above 3000.§mE¿: B€Û€T˜‘€8‚€ƒ€ãíˆÆ#‰€€‚ÿ•Now, before you start your SSH connection, go to the Tunnels panel (see section 4.19.2). Make sure the ‘Local’ radio button is set. Enter the local port number into the ‘Source port’ box. Enter the destination host name and port number into the ‘Destination’ box, separated by a colon (for example, popserver.example.com:110 to connect to a POP-3 server).‘dP- *€È€T˜‘€8‚€ƒ€‚ÿ•Now click the ‘Add’ button. The details of your port forwarding should appear in the list box.µŠ¿ + $€€˜€ã{ÄùN‰‚ÿNow start your session and log in. (Port forwarding will not be enabled until after you have logged in; otherwise it would be easy to perform completely anonymous network attacks, and gain access to anyone's virtual private network). To check that PuTTY has set up the port forwarding correctly, you can look at the PuTTY Event Log (see section 3.1.3.1). It should say something like this:W4P\ # €h€€‚ÿ2001-12-05 17:22:10 Local port 3110 forwarding toI% ¥ $ €J€˜€‚ÿ popserver.example.com:110Á\ f 1 0€!€˜€€€€€‚ÿNow if you connect to the source port number on your local PC, you should find that it answers you exactly as if it were the service running on the destination machine. So in this example, you could then configure an e-mail client to use localhost:3110 as a POP-3 server instead of popserver.example.com:110. (Of course, the forwarding will stop happening when your PuTTY session closes down.)綥 M1 0€m€˜€€€€€‚ÿYou can also forward ports in the other direction: arrange for a particular port number on the server machine to be forwarded back to your PC as a connection to a service on your PC or near it. To do this, just select the ‘Remote’ radio button instead of the ‘Local’ one. The ‘Source port’ box will now specify a port number on the server (note that most servers will not allow you to use port numbers under 1024 for this purpose).úf l% €õ€˜€‚ÿThe source port for a forwarded connection usually does not accept connections from any machine except the SSH client or server machine itself (for local and remote forwardings respectively). There are controls in the Tunnels panel to change this:ÿÑMw@. *€£€T˜‘€8‚€ƒ€‚ÿ•The ‘Local ports accept connections from other hosts’ option allows you to set up local-to-remote lw@aport forwardings in such a way that machines other than your client PC can connect to the forwarded port.tFlëA. *€€T˜‘€8‚€ƒ€‚ÿ•The ‘Remote ports do the same’ option does the same thing for remote-to-local port forwardings (so that machines other than the SSH server machine can connect to the forwarded port.) Note that this feature is only available in the SSH 2 protocol, and not all SSH 2 servers support it (OpenSSH 3.0 does not, for example).ˆWw@sB1”lÿ†sBÈBISection 3.6: Making raw TCP connectionsCBB("btn_up","JI(`',`t00000009')");EB("btn_up")U,ëAÈB) "€X€€€€‚ÿSection 3.6: Making raw TCP connectionsE sB D% €A€˜€‚ÿA lot of Internet protocols are composed of commands and responses in plain text. For example, SMTP (the protocol used to transfer e-mail), NNTP (the protocol used to transfer Usenet news), and HTTP (the protocol used to serve Web pages) all consist of commands in readable plain text.ÀÈBÍE1 0€€˜€€€€€‚ÿSometimes it can be useful to connect directly to one of these services and speak the protocol ‘by hand’, by typing protocol commands and watching the responses. On Unix machines, you can do this using the system's telnet command to connect to the right port number. For example, telnet mailserver.example.com 25 might enable you to talk directly to the SMTP service running on a mail server.ó DÀG1 0€…€˜€€€€€‚ÿAlthough the Unix telnet program provides this functionality, the protocol being used is not really Telnet. Really there is no actual protocol at all; the bytes sent down the connection are exactly the ones you type, and the bytes shown on the screen are exactly the ones sent by the server. Unix telnet will attempt to detect or guess whether the service it is talking to is a real Telnet service or not; PuTTY prefers to be told for certain.GÍEI+ $€9€˜€ã-¥™¦‰‚ÿIn order to make a debugging connection to a service of this type, you simply select the fourth protocol name, ‘Raw’, from the ‘Protocol’ buttons in the ‘Session’ configuration panel. (See section 4.1.1.) You can then enter a host name and a port number, and make the connection.„SÀG‹I16FZˆ‹IÜIÁKSection 3.7: The PuTTY command lineCBB("btn_up","JI(`',`t00000009')");EB("btn_up")Q(IÜI) "€P€€€€‚ÿSection 3.7: The PuTTY command lineɤ‹I¥J% €I€˜€‚ÿPuTTY can be made to do various things without user intervention by supplying command-line arguments (e.g., from a command prompt window, or a Windows shortcut).m>ÜIK/ .€|€ã¨ÄùN€€€‰‚ÿSection 3.7.1: Starting a session from the command lineM¥J_K/ .€<€ã©ÄùN€€€‰‚ÿSection 3.7.2: -cleanupb3KÁK/ .€f€ãªÄùN€€€‰‚ÿSection 3.7.3: Standard command-line options˜g_KYL1Éÿ†ÀYL¾LJSection 3.7.1: Starting a session from the command lineCBB("btn_up","JI(`',`t00000025')");EB("btn_up")e<ÁK¾L) "€x€€€€‚ÿSection 3.7.1: Starting a session from the command line…aYLCM$ €Â€˜€‚ÿThese options allow you to bypass the configuration window and launch straight into a session.]3¾L M* $€f€˜€€€‚ÿTo start a connection to a server called host:^:CMþM$ €t€˜€‚ÿputty.exe [-ssh | -telnet | -rlogin | -raw] [user@]host&ï M$O7 <€ß€˜€ã}§B‰€€ã×ÄùN‰‚ÿIf this syntax is used, settings are taken from the Default Settings (see section 4.1.2); user overrides these settings if supplied. Also, you can specify a protocol, which will override the default protocol (see section 3.7.3.2).À›þM €% €7€˜€‚ÿFor telnet sessions, the following alternative syntax is supported (this makes PuTTY suitable for use as a URL handler for telnet URLs in web browsers):$O €ÁKF"$OR€$ €D€˜€‚ÿputty.exe telnet://host[:port]/³} €6 <€ú€˜€€€€€ã«ÄùN‰‚ÿIn order to start an existing saved session called sessionname, use the -load option (described in section 3.7.3.1).E!R€J$ €B€˜€‚ÿputty.exe -load "session name"xGÂ1-Zˆ™Â‚ï‚Section 3.7.2: -cleanupCBB("btn_up","JI(`',`t00000025')");EB("btn_up")EJ‚) "€8€€€€‚ÿSection 3.7.2: -cleanupè½Âï‚+ $€{€˜€€€‚ÿIf invoked with the -cleanup option, rather than running as normal, PuTTY will remove its registry entries and random seed file from the local machine (after confirming with the user).\‚|ƒ1¹À|ƒÖƒ5‹Section 3.7.3: Standard command-line optionsCBB("btn_up","JI(`',`t00000025')");EB("btn_up")Z1ï‚Öƒ) "€b€€€€‚ÿSection 3.7.3: Standard command-line options5|ƒ …% €!€˜€‚ÿPuTTY and its associated tools support a range of command-line options, most of which are consistent across all the tools. This section lists the available options in all tools. Options which are specific to a particular tool are covered in the chapter about that tool.f4Öƒq…2 4€h€ã«ÄùN€€€€‰‚ÿSection 3.7.3.1: -load: load a saved session•Q …†D X€¢€ã×ÄùN€€€€€€€€€€‰‚ÿSection 3.7.3.2: Selecting a protocol: -ssh, -telnet, -rlogin, -rawa/q…g†2 4€^€ãÎÄùN€€€€‰‚ÿSection 3.7.3.3: -v: increase verbosityc1†ʆ2 4€b€ãÏÄùN€€€€‰‚ÿSection 3.7.3.4: -l: specify a login nameu=g†?‡8 @€z€ãÐÄùN€€€€€€‰‚ÿSection 3.7.3.5: -L and -R: set up port forwardingszHʆ¹‡2 4€€ãÑÄùN€€€€‰‚ÿSection 3.7.3.6: -m: read a remote command or script from a filed2?‡ˆ2 4€d€ãÒÄùN€€€€‰‚ÿSection 3.7.3.7: -P: specify a port numberb0¹‡ˆ2 4€`€ãÓÄùN€€€€‰‚ÿSection 3.7.3.8: -pw: specify a passwordv>ˆõˆ8 @€|€ãÔÄùN€€€€€€‰‚ÿSection 3.7.3.9: -A and -a: control agent forwardingu=ˆj‰8 @€z€ãÕÄùN€€€€€€‰‚ÿSection 3.7.3.10: -X and -x: control X11 forwardingIõˆë‰8 @€’€ãÖÄùN€€€€€€‰‚ÿSection 3.7.3.11: -t and -T: control pseudo-terminal allocationb0j‰MŠ2 4€`€ãÅùN€€€€‰‚ÿSection 3.7.3.12: -C: enable compression~Fë‰ËŠ8 @€Œ€ãùÄùN€€€€€€‰‚ÿSection 3.7.3.13: -1 and -2: specify an SSH protocol versionj8MŠ5‹2 4€p€ãúÄùN€€€€‰‚ÿSection 3.7.3.14: -i: specify an SSH private key\ËŠ‹1ž™€‹ ŒlÀSection 3.7.3.1: -load: load a saved sessionCBB("btn_up","JI(`',`t00000028')");EB("btn_up")^25‹ Œ, (€d€€€€€‚ÿSection 3.7.3.1: -load: load a saved session+‹K+ $€€˜€€€‚ÿThe -load option causes PuTTY to load configuration details out of a saved session. If these details include a host name, then this option is all you need to make PuTTY start a session (although Plink still requires an explicitly specified host name).lH Œ·$ €€˜€‚ÿYou need double quotes around the session name if it contains spaces.¼—KsŽ% €/€˜€‚ÿIf you want to create a Windows shortcut to start a PuTTY saved session, this is the option you should use: your shortcut should call something likeN*·ÁŽ$ €T€˜€‚ÿd:\path\to\putty.exe -load "my session"ŸbsŽlÀ= H€Å€˜€€€€€€€€€‚ÿ(Note that PuTTY itself supports an alternative form of this option, for backwards compatibility. If you execute putty @sessionname it will have the same effect as putty -load "sessionname". With the @ form, no double quotes are required, and the @ ÁŽlÀ5‹sign must be the very first thing on the command line. This form of the option is deprecated.)¤sÁŽÁ1¸G‚ÁÁÈÄSection 3.7.3.2: Selecting a protocol: -ssh, -telnet, -rlogin, -rawCBB("btn_up","JI(`',`t00000028')");EB("btn_up")OlÀÁ> L€ž€€€€€€€€€€€‚ÿSection 3.7.3.2: Selecting a protocol: -ssh, -telnet, -rlogin, -raw{WÁÂ$ €®€˜€‚ÿTo choose which protocol you want to connect with, you can use one of these options:U%ÁmÂ0 0€J€T˜‘€8‚€ƒ€€‚ÿ•-ssh selects the SSH protocol.[+ÂÈÂ0 0€V€T˜‘€8‚€ƒ€€‚ÿ•-telnet selects the Telnet protocol.[+mÂ#Ã0 0€V€T˜‘€8‚€ƒ€€‚ÿ•-rlogin selects the Rlogin protocol.U%ÈÂxÃ0 0€J€T˜‘€8‚€ƒ€€‚ÿ•-raw selects the raw protocol.™u#ÃÄ$ €ê€˜€‚ÿThese options are not available in the file transfer tools PSCP and PSFTP (which only work with the SSH protocol).·ŒxÃÈÄ+ $€€˜€ã-¥™¦‰‚ÿThese options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1).ˆWÄPÅ1€€ƒ PÅ©ÅàÆSection 3.7.3.3: -v: increase verbosityCBB("btn_up","JI(`',`t00000028')");EB("btn_up")Y-ÈÄ©Å, (€Z€€€€€‚ÿSection 3.7.3.3: -v: increase verbosity7 PÅàÆ+ $€€˜€€€‚ÿMost of the PuTTY tools can be made to tell you more about what they are doing by supplying the -v option. If you are having trouble when making a connection, or you're simply curious, you can turn this switch on and hope to find out more about what is happening.ŠY©ÅjÇ1ÌG‚Ä„!jÇÅÇ6ÉSection 3.7.3.4: -l: specify a login nameCBB("btn_up","JI(`',`t00000028')");EB("btn_up")[/àÆÅÇ, (€^€€€€€‚ÿSection 3.7.3.4: -l: specify a login nameº‰jÇÈ1 0€€˜€€€€€‚ÿYou can specify the user name to log in as on the remote server using the -l option. For example, plink login.example.com -l fred.·ŒÅÇ6É+ $€€˜€ã„õ‰‚ÿThese options are equivalent to the username selection box in the Connection panel of the PuTTY configuration box (see section 4.13.2).”cÈÊÉ1€ƒ<ˆ"ÊÉ7ÊÜÎSection 3.7.3.5: -L and -R: set up port forwardingsCBB("btn_up","JI(`',`t00000028')");EB("btn_up")m;6É7Ê2 4€v€€€€€€€‚ÿSection 3.7.3.5: -L and -R: set up port forwardings ÚÊÉBË1 0€µ€˜€ãíˆÆ#‰€€‚ÿAs well as setting up port forwardings in the PuTTY configuration (see section 4.19.2), you can also set up forwardings on the command line. The command-line options work just like the ones in Unix ssh programs.»7ÊýË+ $€!€˜€€€‚ÿTo forward a local port (say 5110) to a remote destination (say popserver.example.com port 110), you can write something like one of these:]:BËZÌ# €t€€‚ÿputty -L 5110:popserver.example.com:110 -load mysessionX4ý˲Ì$ €h€˜€‚ÿplink mysession -L 5110:popserver.example.com:110‘aZÌCÍ0 0€Â€˜€€€€€‚ÿAnd to forward a remote port to a local destination, just use the -R option instead of -L:a>²Ì¤Í# €|€€‚ÿputty -R 5023:mytelnetserver.myhouse.org:23 -load mysession\8CÍÎ$ €p€˜€‚ÿplink mysession -R 5023:mytelnetserver.myhouse.org:23kA¤ÍkÎ* $€‚€˜€ã¥ÄùN‰‚ÿFor general information on port forwarding, see section 3.5.qMÎÜÎ$ €š€˜€‚ÿThese options are not available in the file transfer tools PSCP and PSFTP.¡pkÎ}Ï1™Ä„Ì#}Ï 3Section 3.7.3.6: -m: read a remote command or script from a fileCBB("btn_up","JI(`',`t00000028')");EB("btn_up")rFÜÎ , (€Œ€€€€€‚ÿSection 3.7.3.6: -m: read a remote command or script from a file}Ï Üι‚}ÏÅ7 <€€˜€€€ãóWâ܉€€‚ÿThe -m option performs a similar function to the ‘Remote command’ box in the SSH panel of the PuTTY configuration box (see section 4.17.1). However, the -m option expects to be given a file name, and it will read a command from that file. On most Unix systems, you can even put multiple lines in this file and execute more than one command in sequence, or a whole shell script.nJ 3$ €”€˜€‚ÿThis option is not available in the file transfer tools PSCP and PSFTP.‹Zž1#<ˆû$¾áSection 3.7.3.7: -P: specify a port numberCBB("btn_up","JI(`',`t00000028')");EB("btn_up")\03, (€`€€€€€‚ÿSection 3.7.3.7: -P: specify a port numberΣ¾è+ $€G€˜€€€‚ÿThe -P option is used to specify the port number to connect to. If you have a Telnet server running on port 9696 of a machine instead of port 23, for example:E"-# €D€€‚ÿputty -telnet -P 9696 host.nameF"ès$ €D€˜€‚ÿplink -telnet -P 9696 host.name·Œ-*+ $€€˜€€€‚ÿ(Note that this option is more useful in Plink than in PuTTY, because in PuTTY you can write putty -telnet host.name 9696 in any case.)·Œsá+ $€€˜€ã-¥™¦‰‚ÿThese options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1).‰X*j1tÌç%jÄÞSection 3.7.3.8: -pw: specify a passwordCBB("btn_up","JI(`',`t00000028')");EB("btn_up")Z.áÄ, (€\€€€€€‚ÿSection 3.7.3.8: -pw: specify a password+újï1 0€õ€˜€€€ãxƒùN‰‚ÿA simple way to automate a remote login is to supply your password on the command line. This is not recommended for reasons of security. If you possibly can, we recommend you set up public-key authentication instead. See chapter 8 for details.ïÄÄÞ+ $€‰€˜€€€‚ÿNote that the -pw option only works when you are using the SSH protocol. Due to fundamental limitations of Telnet and Rlogin, these protocols do not support automated password authentication.•dïs 1NûL&s á Á Section 3.7.3.9: -A and -a: control agent forwardingCBB("btn_up","JI(`',`t00000028')");EB("btn_up")n<Þá 2 4€x€€€€€€€‚ÿSection 3.7.3.9: -A and -a: control agent forwarding±€s ’ 1 0€€˜€€€€€‚ÿThe -A option turns on SSH agent forwarding, and -a turns it off. These options are only meaningful if you are using SSH. Óá œ 7 <€§€˜€ã80«f‰ã¢ƒùN‰ã£ƒùN‰‚ÿSee chapter 9 for general information on Pageant, and section 9.4 for information on agent forwarding. Note that there is a security risk involved with enabling this option; see section 9.5 for details.´‰’ P + $€€˜€ãÊ6Êĉ‚ÿThese options are equivalent to the agent forwarding checkbox in the Auth panel of the PuTTY configuration box (see section 4.18.3).qMœ Á $ €š€˜€‚ÿThese options are not available in the file transfer tools PSCP and PSFTP.”cP U 1§ç€'U   @Section 3.7.3.10: -X and -x: control X11 forwardingCBB("btn_up","JI(`',`t00000028')");EB("btn_up")m;Á  2 4€v€€€€€€€‚ÿSection 3.7.3.10: -X and -x: control X11 forwarding²U t1 0€€˜€€€€€‚ÿThe -X option turns on X11 forwarding in SSH, and -x turns it off. These options are only meaningful if you are using SSH.b8 Ö* $€p€˜€ã¤ÄùN‰‚ÿFor information on X11 forwarding, see section 3.4.µŠt‹+ $€€˜€ãwÑJ¶‰‚ÿThese options are equivalent to the X11 forwarding checkbox in the Tunnels panel of the PuTTY configuration box (see section 4.19.1).qMÖ @$ €š€˜€‚ÿThese options are not available in the file transfer tools PSCP and PSFTP.‹ @Á  o‹¬@1•Lã(¬@%AACSection 3.7.3.11: -t and -T: control pseudo-terminal allocationCBB("btn_up","JI(`',`t00000028')");EB("btn_up")yG @%A2 4€Ž€€€€€€€‚ÿSection 3.7.3.11: -t and -T: control pseudo-terminal allocation浬@ B1 0€k€˜€€€€€‚ÿThe -t option ensures PuTTY attempts to allocate a pseudo-terminal at the server, and -T stops it from allocating one. These options are only meaningful if you are using SSH.Åš%AÐB+ $€5€˜€ãçщ‚ÿThese options are equivalent to the ‘Don't allocate a pseudo-terminal’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.17.2).qM BAC$ €š€˜€‚ÿThese options are not available in the file transfer tools PSCP and PSFTP.‰XÐBÊC1¹€ƒ)ÊC$DƒESection 3.7.3.12: -C: enable compressionCBB("btn_up","JI(`',`t00000028')");EB("btn_up")Z.AC$D, (€\€€€€€‚ÿSection 3.7.3.12: -C: enable compression«€ÊCÏD+ $€€˜€€€‚ÿThe -C option enables compression of the data sent across the network. This option is only meaningful if you are using SSH.´‰$DƒE+ $€€˜€ãN§µ‰‚ÿThis option is equivalent to the ‘Enable compression’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.17.3).lÏD F1ã¡„* F–F5HSection 3.7.3.13: -1 and -2: specify an SSH protocol versionCBB("btn_up","JI(`',`t00000028')");EB("btn_up")vDƒE–F2 4€ˆ€€€€€€€‚ÿSection 3.7.3.13: -1 and -2: specify an SSH protocol versionÄ“ FZG1 0€'€˜€€€€€‚ÿThe -1 and -2 options force PuTTY to use version 1 or version 2 of the SSH protocol. These options are only meaningful if you are using SSH.Û°–F5H+ $€a€˜€ã, ÛT‰‚ÿThese options are equivalent to selecting your preferred SSH protocol version as ‘1 only’ or ‘2 only’ in the SSH panel of the PuTTY configuration box (see section 4.17.4).‘`ZGÆH1sƒh†+ÆH(I9KSection 3.7.3.14: -i: specify an SSH private keyCBB("btn_up","JI(`',`t00000028')");EB("btn_up")b65H(I, (€l€€€€€‚ÿSection 3.7.3.14: -i: specify an SSH private keyݲÆHJ+ $€e€˜€€€‚ÿThe -i option allows you to specify the name of a private key file which PuTTY will use to authenticate with the server. This option is only meaningful if you are using SSH.sI(IxJ* $€’€˜€ãxƒùN‰‚ÿFor general information on public-key authentication, see chapter 8.Á–J9K+ $€-€˜€ã„@Ï؉‚ÿThis option is equivalent to the ‘Private key file for authentication’ box in the Auth panel of the PuTTY configuration box (see section 4.18.5).wFxJ°K1›¡„ø,°KúKg„Chapter 4: Configuring PuTTYCBB("btn_up","JI(`',`Top')");EB("btn_up")J!9KúK) "€B€€€€‚ÿChapter 4: Configuring PuTTYeA°K_L$ €‚€˜€‚ÿThis chapter describes all the configuration options in PuTTY.ïÊúKNM% €•€˜€‚ÿPuTTY is configured using the control panel that comes up before you start a session. Some options can also be changed in the middle of a session, by selecting ‘Change Settings’ from the window menu.T%_L¢M/ .€J€ãüÄùN€€€‰‚ÿSection 4.1: The Session panelT%NMöM/ .€J€ã¢ ²`€€€‰‚ÿSection 4.2: The Logging panelU&¢MKN/ .€L€ãýÄùN€€€‰‚ÿSection 4.3: The Terminal panelU&öM N/ .€L€ãþÄùN€€€‰‚ÿSection 4.4: The Keyboard panelQ"KNñN/ .€D€ãÿÄùN€€€‰‚ÿSection 4.5: The Bell panelU& NFO/ .€L€ãÅùN€€€‰‚ÿSection 4.6: The Features panelS$ñN™O/ .€H€ãÅùN€€€‰‚ÿSection 4.7: The Window panelW(FO €/ .€P€ã-ÅùN€€€‰‚ÿSection 4.8: The Appearance panel™O €9KV'™Ob€/ .€N€ã$ÅùN€€€‰‚ÿSection 4.9: The Behaviour panelY* €»€/ .€T€ã%ÅùN€€€‰‚ÿSection 4.10: The Translation panelW(b€/ .€P€ã&ÅùN€€€‰‚ÿSection 4.11: The Selection panelU&»€g/ .€L€ã'ÅùN€€€‰‚ÿSection 4.12: The Colours panelX)¿/ .€R€ã(ÅùN€€€‰‚ÿSection 4.13: The Connection panelS$g‚/ .€H€ãg v–€€€‰‚ÿSection 4.14: The Proxy panelT%¿f‚/ .€J€ã)ÅùN€€€‰‚ÿSection 4.15: The Telnet panelT%‚º‚/ .€J€ã*ÅùN€€€‰‚ÿSection 4.16: The Rlogin panelQ"f‚ ƒ/ .€D€ã+ÅùN€€€‰‚ÿSection 4.17: The SSH panelR#º‚]ƒ/ .€F€ã,ÅùN€€€‰‚ÿSection 4.18: The Auth panelU& ƒ²ƒ/ .€L€ãXÅùN€€€‰‚ÿSection 4.19: The Tunnels panelR#]ƒ„/ .€F€ãOÅùN€€€‰‚ÿSection 4.20: The Bugs panelc4²ƒg„/ .€h€ãPÅùN€€€‰‚ÿSection 4.21: Storing configuration in a fileN„æ„1Ah†^-æ„2…'‡Section 4.1: The Session panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")L#g„2…) "€F€€€€‚ÿSection 4.1: The Session panelÙ´æ„ †% €i€˜€‚ÿThe Session configuration panel contains the basic options you need to specify in order to open a session at all, and also allows you to save your settings to be reloaded later.Z+2…e†/ .€V€ã-¥™¦€€€‰‚ÿSection 4.1.1: The host name sectiong8 †̆/ .€p€ã}§B€€€‰‚ÿSection 4.1.2: Loading and storing saved sessions[,e†'‡/ .€X€ã«ßŽï€€€‰‚ÿSection 4.1.3: ‘Close Window on Exit’…T̆¬‡1ˆø.¬‡þ‡4ŒSection 4.1.1: The host name sectionCBB("btn_up","JI(`',`t00000044')");EB("btn_up")R)'‡þ‡) "€R€€€€‚ÿSection 4.1.1: The host name sectionѬ¬‡ψ% €Y€˜€‚ÿThe top box on the Session panel, labelled ‘Specify your connection by host name’, contains the details that need to be filled in before PuTTY can open a session at all.›nþ‡j‰- *€Ü€T˜‘€8‚€ƒ€‚ÿ•The ‘Host Name’ box is where you type the name, or the IP address, of the server you want to connect to.6ψ Š4 6€€T˜‘€8‚€ƒ€ãüÅùN‰‚ÿ•The ‘Protocol’ radio buttons let you choose what type of connection you want to make: a raw connection, a Telnet connection, an rlogin connection or an SSH connection. (See section 1.2 for a summary of the differences between SSH, Telnet and rlogin.)”`j‰4Œ4 6€Á€T˜‘€8‚€ƒ€ã¦ÄùN‰‚ÿ•The ‘Port’ box lets you specify which port number on the server to connect to. If you select Telnet, Rlogin, or SSH, this box will be filled in automatically to the usual value, and you will only need to change it if you have an unusual server. If you select Raw mode (see section 3.6), you will almost certainly need to fill in the ‘Port’ box.’a ŠÆŒ1ì ^j†/ÆŒ%ÉÇSection 4.1.2: Loading and storing saved sessionsCBB("btn_up","JI(`',`t00000044')");EB("btn_up")_64Œ%) "€l€€€€‚ÿSection 4.1.2: Loading and storing saved sessions¯„ƌԎ+ $€ €˜€€€‚ÿThe next part of the Session configuration panel allows you to save your preferred PuTTY options so they will appear automatically the next time you start PuTTY. It also allows you to create saved sessions, which contain a full set of configuration options plus a host name and protocol. A saved session contains all the information PuTTY needs to start exactly the session you want.!ó% À. *€ç€T˜‘€8‚€ƒ€‚ÿ•To save your default settings: first set up the settings the way you want them saved. Then come back to the Session panel. Select the ‘Default Settings’ entry in the saved sessions list, with a single click. Then press the ‘Save’ button.ÔŽ À4Œ äÔŽÁ% €É€˜€‚ÿNote that PuTTY does not allow you to save a host name into the Default Settings entry. This ensures that when PuTTY is started up, the host name box is always empty, so a user can always just type in a host name and connect.̧ ÀáÁ% €O€˜€‚ÿIf there is a specific host you want to store the details of how to connect to, you should create a saved session, which will be separate from the Default Settings.¥wÁ†Ã. *€ï€T˜‘€8‚€ƒ€‚ÿ•To save a session: first go through the rest of the configuration box setting up all the options you want. Then come back to the Session panel. Enter a name for the saved session in the ‘Saved Sessions’ input box. (The server name is often a good choice for a saved session name.) Then press the ‘Save’ button. Your saved session name should now appear in the list box.ë½áÁqÄ. *€{€T˜‘€8‚€ƒ€‚ÿ•To reload a saved session: single-click to select the session name in the list box, and then press the ‘Load’ button. Your saved settings should all appear in the configuration panel.C†Ã´Å. *€+€T˜‘€8‚€ƒ€‚ÿ•To modify a saved session: first load it as described above. Then make the changes you want. Come back to the Session panel, single-click to select the session name in the list box, and press the ‘Save’ button. The new settings will be saved over the top of the old ones.Š]qÄ>Æ- *€º€T˜‘€8‚€ƒ€‚ÿ•To start a saved session immediately: double-click on the session name in the list box.ª}´ÅèÆ- *€ú€T˜‘€8‚€ƒ€‚ÿ•To delete a saved session: single-click to select the session name in the list box, and then press the ‘Delete’ button.á¼>ÆÉÇ% €y€˜€‚ÿEach saved session is independent of the Default Settings configuration. If you change your preferences and update Default Settings, you must also update every saved session separately.†UèÆOÈ1‹‚‰0OÈ¢ÈÚËSection 4.1.3: ‘Close Window on Exit’CBB("btn_up","JI(`',`t00000044')");EB("btn_up")S*ÉÇ¢È) "€T€€€€‚ÿSection 4.1.3: ‘Close Window on Exit’gBOÈ Ê% €…€˜€‚ÿFinally in the Session panel, there is an option labelled ‘Close Window on Exit’. This controls whether the PuTTY session window disappears as soon as the session inside it terminates. If you are likely to want to copy and paste text out of the session after it has terminated, you should arrange this option to be off.Ѭ¢ÈÚË% €Y€˜€‚ÿ‘Close Window On Exit’ has three settings. ‘Always’ means always close the window on exit; ‘Never’ means never close on exit (always leave the window open). The third setting, and the default one, is ‘Only on clean exit’. In this mode, a session which terminates normally will cause its window to close, but one which is aborted unexpectedly by network trouble or a confusing message from the server will leave the window up.N ÊYÌ1¯j† 1YÌ¥ÌSection 4.2: The Logging panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")L#ÚË¥Ì) "€F€€€€‚ÿSection 4.2: The Logging panel©„YÌNÍ% € €˜€‚ÿThe Logging configuration panel allows you to save log files of your PuTTY sessions, for debugging, analysis or future reference.“o¥ÌáÍ$ €Þ€˜€‚ÿThe main option is a radio-button set that specifies whether PuTTY will log anything at all. The options are¥xN͆Î- *€ð€T˜‘€8‚€ƒ€‚ÿ•‘Logging turned off completely’. This is the default option; in this mode PuTTY will not create a log file at all.²„áÍD. *€ €T˜‘€8‚€ƒ€‚ÿ•‘Log printable output only’. In this mode, a log file will be created and written to, but only printable text will be saved into it. The various terminal control codes that are typically sent down an interactive session alongside the printable text will be omitted. This might be a useful mode if you want to read a log file in †ÎDÚËa text editor and hope to be able to make sense of it.Þ†ÎV4 6€½€T˜‘€8‚€ƒ€€€‚ÿ•‘Log all session output’. In this mode, everything sent by the server into your terminal session is logged. If you view the log file in a text editor, therefore, you may well find it full of strange control characters. This is a particularly useful mode if you are experiencing problems with PuTTY's terminal handling: you can record everything that went to the terminal, so that someone else can replay the session later in slow motion and watch to see what went wrong.úÆDP4 6€€T˜‘€8‚€ƒ€€€‚ÿ•‘Log SSH packet data’. In this mode (which is only used by SSH connections), the SSH message packets sent over the encrypted connection are written to the log file. You might need this to debug a network-level problem, or more likely to send to the PuTTY authors as part of a bug report. BE WARNED that if you log in using a password, the password will appear in the log file, so be sure to edit it out before sending the log file to anyone else!T%V¤/ .€J€ãÄÛ¶€€€‰‚ÿSection 4.2.1: ‘Log file name’pAP/ .€‚€ãmT$%€€€‰‚ÿSection 4.2.2: ‘What to do if the log file already exists’‚Q¤–1@‚‰p2–âÖ Section 4.2.1: ‘Log file name’CBB("btn_up","JI(`',`logging.main')");EB("btn_up")L#â) "€F€€€€‚ÿSection 4.2.1: ‘Log file name’F!–(% €C€˜€‚ÿIn this edit box you enter the name of the file you want to log the session to. The ‘Browse’ button will let you look around your file system to find the right place to put the file; or if you already know exactly where you want it to go, you can just type a pathname into the edit box.èâ;+ $€Ñ€˜€€€‚ÿThere are a few special features in this box. If you use the & character in the file name box, PuTTY will insert details of the current session in the name of the file it actually opens. The precise replacements it will do are:o?(ª0 0€~€T˜‘€8‚€ƒ€€‚ÿ•&Y will be replaced by the current year, as four digits.o?; 0 0€~€T˜‘€8‚€ƒ€€‚ÿ•&M will be replaced by the current month, as two digits.zJª“ 0 0€”€T˜‘€8‚€ƒ€€‚ÿ•&D will be replaced by the current day of the month, as two digits.‹[  0 0€¶€T˜‘€8‚€ƒ€€‚ÿ•&T will be replaced by the current time, as six digits (HHMMSS) with no punctuation.rB“  0 0€„€T˜‘€8‚€ƒ€€‚ÿ•&H will be replaced by the host name you are connecting to.¡w 1 * $€î€˜€€€‚ÿFor example, if you enter the host name c:\puttylogs\log-&h-&y&m&d-&t.dat, you will end up with files looking likeQ. ‚ # €\€€‚ÿlog-server1.example.com-20010528-110859.datT01 Ö $ €`€˜€‚ÿlog-unixbox.somewhere.org-20010611-221001.datžm‚ t 1h „ 3t Ü ÜSection 4.2.2: ‘What to do if the log file already exists’CBB("btn_up","JI(`',`logging.main')");EB("btn_up")h?Ö Ü ) "€~€€€€‚ÿSection 4.2.2: ‘What to do if the log file already exists’Õt Ü+ $€«€˜€€€‚ÿThis control allows you to specify what PuTTY should do if it tries to start writing to a log file and it finds the file already exists. You might want to automatically destroy the existing log file and start a new one with the same name. Alternatively, you might want to open the existing log file and add data to the end of it. Finally (the default option), you might not want to have any automatic behaviour, but to ask the user every time the problem comes up.€OÜ \1!p£4\©‰CSection 4.3: The Terminal panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")M$Ü©) "€H€€€€‚ÿSection 4.3: The Terminal panelŠf\?@$ €Ì€˜€‚ÿThe Terminal configuration panel allows you to con©?@Ütrol the behaviour of PuTTY's terminal emulation.b3©¡@/ .€f€ãÝéàý€€€‰‚ÿSection 4.3.1: ‘Auto wrap mode initially on’c4?@A/ .€h€ã€ç¡:€€€‰‚ÿSection 4.3.2: ‘DEC Origin Mode initially on’^/¡@bA/ .€^€ã—[K€€€‰‚ÿSection 4.3.3: ‘Implicit CR in every LF’l=AÎA/ .€z€ãØÆs¦€€€‰‚ÿSection 4.3.4: ‘Use background colour to erase screen’[,bA)B/ .€X€ãL;B:€€€‰‚ÿSection 4.3.5: ‘Enable blinking text’W(ÎA€B/ .€P€ã•Ü.ó€€€‰‚ÿSection 4.3.6: ‘Answerback to ^E’Q")BÑB/ .€D€ãl{Þ}€€€‰‚ÿSection 4.3.7: ‘Local echo’Y*€B*C/ .€T€ãÕ‚Þ}€€€‰‚ÿSection 4.3.8: ‘Local line editing’_0ÑB‰C/ .€`€ãá²³ƒ€€€‰‚ÿSection 4.3.9: Remote-controlled printing\*CD1{„ V…5DpD‘HSection 4.3.1: ‘Auto wrap mode initially on’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")Z1‰CpD) "€b€€€€‚ÿSection 4.3.1: ‘Auto wrap mode initially on’švD E$ €ì€˜€‚ÿAuto wrap mode controls what happens when text printed in a PuTTY window reaches the right-hand edge of the window.Y4pDcF% €i€˜€‚ÿWith auto wrap mode on, if a long line of text reaches the right-hand edge, it will wrap over on to the next line so you can still see all the text. With auto wrap mode off, the cursor will stay at the right-hand edge of the screen, and all the characters in the line will be printed on top of each other.Ϫ E2G% €U€˜€‚ÿIf you are running a full-screen application and you occasionally find the screen scrolling up when it looks as if it shouldn't, you could try turning this option off._.cF‘H1 0€]€˜€€€ãÄùN‰‚ÿAuto wrap mode can be turned on and off by control sequences sent by the server. This configuration option only controls the default state. If you modify this option in mid-session using ‘Change Settings’, you will need to reset the terminal (see section 3.1.3.5) before the change takes effect.Ž]2GI1É£2Š6IzIèNSection 4.3.2: ‘DEC Origin Mode initially on’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")[2‘HzI) "€d€€€€‚ÿSection 4.3.2: ‘DEC Origin Mode initially on’¢~IJ$ €ü€˜€‚ÿDEC Origin Mode is a minor option which controls how PuTTY interprets cursor-position control sequences sent by the server.W2zIsK% €e€˜€‚ÿThe server can send a control sequence that restricts the scrolling region of the display. For example, in an editor, the server might reserve a line at the top of the screen and a line at the bottom, and might send a control sequence that causes scrolling operations to affect only the remaining lines.ýØJpL% €±€˜€‚ÿWith DEC Origin Mode on, cursor coordinates are counted from the top of the scrolling region. With it turned off, cursor coordinates are counted from the top of the whole screen regardless of the scrolling region.ósKˆM% €ç€˜€‚ÿIt is unlikely you would need to change this option, but if you find a full-screen application is displaying pieces of text in what looks like the wrong part of the screen, you could try turning DEC Origin Mode on to see whether that helps.`/pLèN1 0€_€˜€€€ãÄùN‰‚ÿDEC Origin Mode can be turned on and off by control sequences sent by the server. This configuration option only controls the default state. If you modify this option in mid-session using ‘Change Settings’, you will need to reset the terminal (see section 3.1.3.5) before the change takes effect.‰XˆMqO1eV…Ì 7qOÇOâƒSection 4.3.3: ‘Implicit CR in every LF’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")V-èNÇO) "€Z€€€€‚ÿSection 4.3.3: ‘Implicit CR in every LF’&qOù€% €€˜€‚ÿMost servers send tÇOù€èNwo control characters, CR and LF, to start a new line of the screen. The CR character makes the cursor return to the left-hand side of the screen. The LF character makes the cursor move one line down (and might make the screen scroll).ñÌÇOê% €™€˜€‚ÿSome servers only send LF, and expect the terminal to move the cursor over to the left automatically. If you come across a server that does this, you will see a stepped effect on the screen, like this:8ù€"‚# €*€€‚ÿFirst line of textC êe‚# €@€€‚ÿ Second lineN*"‚³‚$ €T€˜€‚ÿ Third line•qe‚Hƒ$ €â€˜€‚ÿIf this happens to you, try enabling the ‘Implicit CR in every LF’ option, and things might go back to normal:8³‚€ƒ# €*€€‚ÿFirst line of text1Hƒ±ƒ# €€€‚ÿSecond line1 €ƒâƒ$ €€˜€‚ÿThird line—f±ƒy„1’2ŠŠ 8y„Ý„ ‰Section 4.3.4: ‘Use background colour to erase screen’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")d;âƒÝ„) "€v€€€€‚ÿSection 4.3.4: ‘Use background colour to erase screen’_4y„<†+ $€i€˜€€€‚ÿNot all terminals agree on what colour to turn the screen when the server sends a ‘clear screen’ sequence. Some terminals believe the screen should always be cleared to the default background colour. Others believe the screen should be cleared to whatever the server has selected as a background colour.•qÝ„ц$ €â€˜€‚ÿThere exist applications that expect both kinds of behaviour. Therefore, PuTTY can be configured to do either.Ò§<†£‡+ $€O€˜€€€‚ÿWith this option disabled, screen clearing is always done in the default background colour. With this option enabled, it is done in the current background colour.h7ц ‰1 0€o€˜€€€ãÄùN‰‚ÿBackground-colour erase can be turned on and off by control sequences sent by the server. This configuration option only controls the default state. If you modify this option in mid-session using ‘Change Settings’, you will need to reset the terminal (see section 3.1.3.5) before the change takes effect.†U£‡‘‰1)Ì  9‘‰ä‰ºŒSection 4.3.5: ‘Enable blinking text’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")S* ‰ä‰) "€T€€€€‚ÿSection 4.3.5: ‘Enable blinking text’¼—‘‰ Š% €/€˜€‚ÿThe server can ask PuTTY to display text that blinks on and off. This is very distracting, so PuTTY allows you to turn blinking text off completely.¼—ä‰\‹% €/€˜€‚ÿWhen blinking text is disabled and the server attempts to make some text blink, PuTTY will instead display the text with a bolded background colour.^- ŠºŒ1 0€[€˜€€€ãÄùN‰‚ÿBlinking text can be turned on and off by control sequences sent by the server. This configuration option only controls the default state. If you modify this option in mid-session using ‘Change Settings’, you will need to reset the terminal (see section 3.1.3.5) before the change takes effect.‚Q\‹<1†Š N :<‹ÎÁSection 4.3.6: ‘Answerback to ^E’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")O&ºŒ‹) "€L€€€€‚ÿSection 4.3.6: ‘Answerback to ^E’À›<KŽ% €7€˜€‚ÿThis option controls what PuTTY will send back to the server if the server sends it the ^E enquiry character. Normally it just sends the string ‘PuTTY’.‹À% €;€˜€‚ÿIf you accidentally write the contents of a binary file to your terminal, you will probably find that it contains more than one ^E character, and as a result your next command line will probably read ‘PuTTYPuTTYPuTTY...’ as if you had typed the answerback string multiple times at the keyboard. If you set the answerback string to be empty, this problem should go away, but doing so might cause otheKŽÀºŒr problems. ÚKŽ$Á1 0€µ€˜€€€ã6Õ‰‚ÿNote that this is not the feature of PuTTY which the server will typically use to determine your terminal type. That feature is the ‘Terminal-type string’ in the Connection panel; see section 4.13.1 for details.ªtÀÎÁ6 <€è€˜€€€€€€€‚ÿYou can include control characters in the answerback string using ^C notation. (Use ^~ to get a literal ^.)|K$ÁJÂ1G „ ;J“‘ÅSection 4.3.7: ‘Local echo’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")I ÎÁ“Â) "€@€€€€‚ÿSection 4.3.7: ‘Local echo’1JÂÄÃ1 0€€˜€€€€€‚ÿWith local echo disabled, characters you type into the PuTTY window are not echoed in the window by PuTTY. They are simply sent to the server. (The server might choose to echo them back to you; this can't be controlled from the PuTTY control panel.)ͨ“‘Å% €Q€˜€‚ÿSome types of session need local echo, and many do not. In its default mode, PuTTY will automatically attempt to deduce whether or not local echo is appropriate for the session you are working in. If you find it has made the wrong decision, you can use this configuration option to override its choice: you can force local echo to be turned on, or force it to be turned off, instead of relying on the automatic detection.„SÄÃÆ1ÓN '‰ <ÆfÆèËSection 4.3.8: ‘Local line editing’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")Q(‘ÅfÆ) "€P€€€€‚ÿSection 4.3.8: ‘Local line editing’™uÆÿÆ$ €ê€˜€‚ÿNormally, every character you type into the PuTTY window is sent immediately to the server the moment you type it.Z5fÆYÈ% €k€˜€‚ÿIf you enable local line editing, this changes. PuTTY will let you edit a whole line at a time locally, and the line will only be sent to the server when you press Return. If you make a mistake, you can use the Backspace key to correct it before you press Return, and the server will never see the mistake.ªÿÆÊ+ $€ÿ€˜€ãl{Þ}‰‚ÿSince it is hard to edit a line locally without being able to see it, local line editing is mostly used in conjunction with local echo (section 4.3.7). This makes it ideal for use in raw mode or when connecting to MUDs or talkers. (Although some more advanced MUDs do occasionally turn local line editing on and turn local echo off, in order to accept a password from the user.)åÀYÈèË% €€˜€‚ÿSome types of session need local line editing, and many do not. In its default mode, PuTTY will automatically attempt to deduce whether or not local line editing is appropriate for the session you are working in. If you find it has made the wrong decision, you can use this configuration option to override its choice: you can force local line editing to be turned on, or force it to be turned off, instead of relying on the automatic detection.ŠYÊrÌ1,„  =rÌÉ̪Section 4.3.9: Remote-controlled printingCBB("btn_up","JI(`',`t00000045')");EB("btn_up")W.èËÉÌ) "€\€€€€‚ÿSection 4.3.9: Remote-controlled printingÆ¡rÌÍ% €C€˜€‚ÿA lot of VT100-compatible terminals support printing under control of the remote server. PuTTY supports this feature as well, but it is turned off by default.ÈÉÌWÏ+ $€;€˜€€€‚ÿTo enable remote-controlled printing, choose a printer from the ‘Printer to send ANSI printer output to’ drop-down list box. This should allow you to select from all the printers you have installed drivers for on your computer. Alternatively, you can type the network name of a networked printer (for example, \\printserver\printer1) even if you haven't already installed a driver for it on your own machine.;Íž+ $€!€˜€€€‚ÿWhen the remote server attempts to print some data, PuTTY will send that data to the printer raw - without translating it, WÏžèËattempting to format it, or doing anything else to it. It is up to you to ensure your remote server knows what type of printer it is talking to.e@WÏ% €€˜€‚ÿSince PuTTY sends data to the printer raw, it cannot offer options such as portrait versus landscape, print quality, or paper tray selection. All these things would be done by your PC printer driver (which PuTTY bypasses); if you need them done, you will have to find a way to configure your remote server to do them.§‚žª% €€˜€‚ÿTo disable remote printing again, choose ‘None (printing disabled)’ from the printer selection list. This is the default state.€O*1)'‰ & >*wSSection 4.4: The Keyboard panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")M$ªw) "€H€€€€‚ÿSection 4.4: The Keyboard panel…a*ü$ €Â€˜€‚ÿThe Keyboard configuration panel allows you to control the behaviour of the keyboard in PuTTY.m>wi/ .€|€ã*͈s€€€‰‚ÿSection 4.4.1: Changing the action of the Backspace keyqBüÚ/ .€„€ã»‰Ù¢€€€‰‚ÿSection 4.4.2: Changing the action of the Home and End keysxIiR/ .€’€ãVS怀€‰‚ÿSection 4.4.3: Changing the action of the function keys and keypadm>Ú¿/ .€|€ãneÇA€€€‰‚ÿSection 4.4.4: Controlling Application Cursor Keys modeh9R'/ .€r€ã(~¦„€€€‰‚ÿSection 4.4.5: Controlling Application Keypad mode^/¿…/ .€^€ã½–\!€€€‰‚ÿSection 4.4.6: Using NetHack keypad moded5'é/ .€j€ãqýF€€€‰‚ÿSection 4.4.7: Enabling a DEC-like Compose keyj;…S/ .€v€ã¥àÌs€€€‰‚ÿSection 4.4.8: ‘Control-Alt is different from AltGr’˜géë1FÂ È ?ëP1 Section 4.4.1: Changing the action of the Backspace keyCBB("btn_up","JI(`',`t00000046')");EB("btn_up")e<SP) "€x€€€€‚ÿSection 4.4.1: Changing the action of the Backspace keyˆcëØ % €Ç€˜€‚ÿSome terminals believe that the Backspace key should send the same thing to the server as Control-H (ASCII code 8). Other terminals believe that the Backspace key should send ASCII code 127 (usually known as Control-?) so that it can be distinguished from Control-H. This option allows you to choose which code PuTTY generates when you press Backspace.g<P? + $€y€˜€€€‚ÿIf you are connecting to a Unix system, you will probably find that the Unix stty command lets you configure which the server expects to see, so you might not need to change which one PuTTY generates. On other systems, the server's expectation might be fixed and you might have no choice but to configure PuTTY.òÇØ 1 + $€€˜€€€‚ÿIf you do have the choice, we recommend configuring PuTTY to generate Control-? and configuring the server to expect it, because that allows applications such as emacs to use Control-H for help.œk? Í 1Ç& Ð @Í 6 ”Section 4.4.2: Changing the action of the Home and End keysCBB("btn_up","JI(`',`t00000046')");EB("btn_up")i@1 6 ) "€€€€€€‚ÿSection 4.4.2: Changing the action of the Home and End keysÊŸÍ + $€?€˜€€€‚ÿThe Unix terminal emulator rxvt disagrees with the rest of the world about what character sequences should be sent to the server by the Home and End keys.ë¥6 ëF Z€K€˜€€€€€€€€€€€€‚ÿxterm, and other terminals, send ESC [1~ for the Home key, and ESC [4~ for the End key. rxvt sends ESC [H for the Home key and ESC [Ow for the End key.©„”% € €˜€‚ÿIf you find an application on which the Home and End keys aren't working, you could try switching this option to see if it helps.£rëC@1È … AC@³@[GSection 4.4.3: Changing the action of the function keys and”C@” keypadCBB("btn_up","JI(`',`t00000046')");EB("btn_up")pG”³@) "€Ž€€€€‚ÿSection 4.4.3: Changing the action of the function keys and keypad[C@2A$ €¶€˜€‚ÿThis option affects the function keys (F1 to F12) and the top row of the numeric keypad.õµ³@'B@ N€k€T˜‘€8‚€ƒ€€€€€€€‚ÿ•In the default mode, labelled ESC [n~, the function keys generate sequences like ESC [11~, ESC [12~ and so on. This matches the general behaviour of Digital's terminals.Øž2AÿB: B€=€T˜‘€8‚€ƒ€€€€€‚ÿ•In Linux mode, F6 to F12 behave just like the default mode, but F1 to F5 generate ESC [[A through to ESC [[E. This mimics the Linux virtual console. Ë'B D@ N€—€T˜‘€8‚€ƒ€€€€€€€‚ÿ•In Xterm R6 mode, F5 to F12 behave like the default mode, but F1 to F4 generate ESC OP through to ESC OS, which are the sequences produced by the top row of the keypad on Digital's terminals.×ÿBáD: B€;€T˜‘€8‚€ƒ€€€€€‚ÿ•In VT400 mode, all the function keys behave like the default mode, but the actual top row of the numeric keypad generates ESC OP through to ESC OS.‚L DcE6 <€˜€T˜‘€8‚€ƒ€€€€‚ÿ•In VT100+ mode, the function keys generate ESC OP through to ESC O[}áDàF^ Š€?€T˜‘€8‚€ƒ€€€€€€€€€€€€€€€€€‚ÿ•In SCO mode, the function keys F1 to F12 generate ESC [M through to ESC [X. Together with shift, they generate ESC [Y through to ESC [j. With control they generate ESC [k through to ESC [v, and with shift and control together they generate ESC [w through to ESC [{.{WcE[G$ €®€˜€‚ÿIf you don't know what any of this means, you probably don't need to fiddle with it.˜gàFóG1ôÐ ^‡ BóGXHçJSection 4.4.4: Controlling Application Cursor Keys modeCBB("btn_up","JI(`',`t00000046')");EB("btn_up")e<[GXH) "€x€€€€‚ÿSection 4.4.4: Controlling Application Cursor Keys mode+îóGƒI= H€Ý€˜€€€€€€€€€‚ÿApplication Cursor Keys mode is a way for the server to change the control sequences sent by the arrow keys. In normal mode, the arrow keys send ESC [A through to ESC [D. In application mode, they send ESC OA through to ESC OD.»–XH>J% €-€˜€‚ÿApplication Cursor Keys mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the initial state.©ƒIçJ* $€þ€˜€ãMD™‰‚ÿYou can also disable application cursor keys mode completely, using the ‘Features’ configuration panel; see section 4.6.1.“b>JzK1… z CzKÚK°€Section 4.4.5: Controlling Application Keypad modeCBB("btn_up","JI(`',`t00000046')");EB("btn_up")`7çJÚK) "€n€€€€‚ÿSection 4.4.5: Controlling Application Keypad mode…azK_L$ €Â€˜€‚ÿApplication Keypad mode is a way for the server to change the behaviour of the numeric keypad.à»ÚK?M% €w€˜€‚ÿIn normal mode, the keypad behaves like a normal Windows keypad: with NumLock on, the number keys generate numbers, and with NumLock off they act like the arrow keys and Home, End etc.Ô©_LN+ $€S€˜€€€‚ÿIn application mode, all the keypad keys send special control sequences, including Num Lock. Num Lock stops behaving like Num Lock and becomes another function key.ï?M'O% €ß€˜€‚ÿDepending on which version of Windows you run, you may find the Num Lock light still flashes on and off every time you press Num Lock, even when application mode is active and Num Lock is acting like a function key. This is unavoidable.¶‘N €% €#€˜€‚ÿApplication keypad mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the initial state.'O €çJ¤z'O°€* $€ô€˜€ãMD™‰‚ÿYou can also disable application keypad mode completely, using the ‘Features’ configuration panel; see section 4.6.1.‰X €91K^‡ ÷ D9„„Section 4.4.6: Using NetHack keypad modeCBB("btn_up","JI(`',`t00000046')");EB("btn_up")V-°€) "€Z€€€€‚ÿSection 4.4.6: Using NetHack keypad mode°‹9?‚% €€˜€‚ÿPuTTY has a special mode for playing NetHack. You can enable it by selecting ‘NetHack’ in the ‘Initial state of numeric keypad’ control.Ä“ƒ1 0€'€˜€€€€€‚ÿIn this mode, the numeric keypad keys 1-9 generate the NetHack movement commands (hjklyubn). The 5 key generates the . command (do nothing).Ö?‚„+ $€­€˜€€€‚ÿBetter still, pressing Shift with the keypad keys generates the capital forms of the commands (HJKLYUBN), which tells NetHack to keep moving you in the same direction until you encounter something interesting.€\ƒ„„$ €¸€˜€‚ÿFor some reason, this feature only works properly when Num Lock is on. We don't know why.^„…1Éz M E…o…܇Section 4.4.7: Enabling a DEC-like Compose keyCBB("btn_up","JI(`',`t00000046')");EB("btn_up")\3„„o…) "€f€€€€‚ÿSection 4.4.7: Enabling a DEC-like Compose key…`…ô†% €Á€˜€‚ÿDEC terminals have a Compose key, which provides an easy-to-remember way of typing accented characters. You press Compose and then type two more characters. The two characters are ‘combined’ to produce an accented character. The choices of character are designed to be easy to remember; for example, composing ‘e’ and ‘`’ produces the ‘è’ character.èÃo…܇% €‡€˜€‚ÿIf your keyboard has a Windows Application key, it acts as a Compose key in PuTTY. Alternatively, if you enable the ‘AltGr acts as Compose key’ option, the AltGr key will become a Compose key.•dô†qˆ1y÷ ÷ FqˆÓˆêŒSection 4.4.8: ‘Control-Alt is different from AltGr’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")b9܇Óˆ) "€r€€€€‚ÿSection 4.4.8: ‘Control-Alt is different from AltGr’íÈqˆÀ‰% €‘€˜€‚ÿSome old keyboards do not have an AltGr key, which can make it difficult to type some characters. PuTTY can be configured to treat the key combination Ctrl + Left Alt the same way as the AltGr key.º‰Óˆz‹1 0€€˜€€€€€‚ÿBy default, this checkbox is checked, and the key combination Ctrl + Left Alt does something completely different. PuTTY's usual handling of the left Alt key is to prefix the Escape (Control-[) character to whatever character sequence the rest of the keypress would generate. For example, Alt-A generates Escape followed by a. So Alt-Ctrl-A would generate Escape, followed by Control-A.·’À‰1Œ% €%€˜€‚ÿIf you uncheck this box, Ctrl-Alt will become a synonym for AltGr, so you can use it to type extra graphic characters if your keyboard has any.¹Žz‹êŒ+ $€€˜€ãqýF‰‚ÿ(However, Ctrl-Alt will never act as a Compose key, regardless of the setting of ‘AltGr acts as Compose key’ described in section 4.4.7.)|K1Œf1;M ;€ Gf¯­ÀSection 4.5: The Bell panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")I ꌯ) "€@€€€€‚ÿSection 4.5: The Bell panelif<Ž$ €Ò€˜€‚ÿThe Bell panel controls the terminal bell feature: the server's ability to cause PuTTY to beep at you.6¯r% €#€˜€‚ÿIn the default configuration, when the server sends the character with ASCII code 7 (Control-G), PuTTY will play the Windows Default Beep sound. This is not always what you want the terminal bell feature to do; the Bell panel allows you to configure alternative actions.\-<ŽÎ/ .€Z€ã]úÍ€€€‰‚ÿSection 4.5.1: ‘Set the style of bell’i:rCÀ/ .€t€ãy2\†€€€‰‚ÿSÎCÀêŒection 4.5.2: ‘Taskbar/caption indication on bell’j;έÀ/ .€v€ãsÅv€€€‰‚ÿSection 4.5.3: ‘Control the bell overload behaviour’‡VCÀ4Á1V÷ Œ„ H4ÁˆÁŠÆSection 4.5.1: ‘Set the style of bell’CBB("btn_up","JI(`',`t00000047')");EB("btn_up")T+­ÀˆÁ) "€V€€€€‚ÿSection 4.5.1: ‘Set the style of bell’[4ÁÂ$ €¶€˜€‚ÿThis control allows you to select various different actions to occur on a terminal bell:ÍŸˆÁÔÂ. *€?€T˜‘€8‚€ƒ€‚ÿ•Selecting ‘None’ disables the bell completely. In this mode, the server can send as many Control-G characters as it likes and nothing at all will happen.&øÂúÃ. *€ñ€T˜‘€8‚€ƒ€‚ÿ•‘Play Windows Default Sound’ is the default setting. It causes the Windows ‘Default Beep’ sound to be played. To change what this sound is, or to test it if nothing seems to be happening, use the Sound configurer in the Windows Control Panel.«}ÔÂ¥Å. *€û€T˜‘€8‚€ƒ€‚ÿ•‘Play a custom sound file’ allows you to specify a particular sound file to be used by PuTTY alone, or even by a particular individual PuTTY session. This allows you to distinguish your PuTTY beeps from any other beeps on the system. If you select this option, you will also need to enter the name of your sound file in the edit control ‘Custom sound file to play as a bell’.å·úÊÆ. *€o€T˜‘€8‚€ƒ€‚ÿ•‘Visual bell’ is a silent alternative to a beeping computer. In this mode, when the server sends a Control-G, the whole PuTTY window will flash white for a fraction of a second.”c¥ÅÇ1ú;€ ˇ IÇÇËSection 4.5.2: ‘Taskbar/caption indication on bell’CBB("btn_up","JI(`',`t00000047')");EB("btn_up")a8ŠÆÇ) "€p€€€€‚ÿSection 4.5.2: ‘Taskbar/caption indication on bell’¾™Ç=È% €3€˜€‚ÿThis feature controls what happens to the PuTTY window's entry in the Windows Taskbar if a bell occurs while the window does not have the input focus.a=ÇžÈ$ €z€˜€‚ÿIn the default state (‘Disabled’) nothing unusual happens.Ü·=ÈzÊ% €o€˜€‚ÿIf you select ‘Steady’, then when a bell occurs and the window is not in focus, the window's Taskbar entry and its title bar will change colour to let you know that PuTTY session is asking for your attention. The change of colour will persist until you select the window, so you can leave several PuTTY windows minimised in your terminal, go away from your keyboard, and be sure not to have missed any important beeps when you get back.žzžÈË$ €ô€˜€‚ÿ‘Flashing’ is even more eye-catching: the Taskbar entry will continuously flash on and off until you select the window.•dzÊ­Ë1Œ„ ¸ J­ËÌVSection 4.5.3: ‘Control the bell overload behaviour’CBB("btn_up","JI(`',`t00000047')");EB("btn_up")b9ËÌ) "€r€€€€‚ÿSection 4.5.3: ‘Control the bell overload behaviour’ܱ­ËëÍ+ $€c€˜€€€‚ÿA common user error in a terminal session is to accidentally run the Unix command cat (or equivalent) on an inappropriate file type, such as an executable, image file, or ZIP file. This produces a huge stream of non-text characters sent to the terminal, which typically includes a lot of bell characters. As a result of this the terminal often doesn't stop beeping for ten minutes, and everybody else in the office gets annoyed.]8ÌT% €q€˜€‚ÿTo try to avoid this behaviour, or any other cause of excessive beeping, PuTTY includes a bell overload management feature. In the default configuration, receiving more than five bell characters in a two-second period will cause the overload feature to activate. Once the overload feature is active, further bells will have no effect at all, so the rest of your binary file will be sent to the screen in silence. After a period of five seconds during which no further bells are received, the oveëÍTËrload feature will turn itself off again and bells will be re-enabled.«†ëÍÿ% € €˜€‚ÿIf you want this feature completely disabled, you can turn it off using the checkbox ‘Bell is temporarily disabled when over-used’.W2TV% €e€˜€‚ÿAlternatively, if you like the bell overload feature but don't agree with the settings, you can configure the details: how many bells constitute an overload, how short a time period they have to arrive in to do so, and how much silent time is required before the overload feature will deactivate itself.€OÿÖ1éˇ ß KÖ#¿Section 4.6: The Features panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")M$V#) "€H€€€€‚ÿSection 4.6: The Features panel÷ÒÖ% €¥€˜€‚ÿPuTTY's terminal emulation is very highly featured, and can do a lot of things under remote server control. Some of these features can cause problems due to buggy or strangely configured server applications.«†#Å% € €˜€‚ÿThe Features configuration panel allows you to disable some of PuTTY's more advanced terminal features, in case they cause trouble.qB6/ .€„€ãMD™€€€‰‚ÿSection 4.6.1: Disabling application keypad and cursor keysr=Ũ5 :€z€ãⳄ€€€€€‰‚ÿSection 4.6.2: Disabling xterm-style mouse reportingg86/ .€p€ãï´•Z€€€‰‚ÿSection 4.6.3: Disabling remote terminal resizingpA¨/ .€‚€ãÚfùÌ€€€‰‚ÿSection 4.6.4: Disabling switching to the alternate screenk<ê/ .€x€ãÂdY7€€€‰‚ÿSection 4.6.5: Disabling remote window title changingd5N/ .€j€ã>ŠcÜ€€€‰‚ÿSection 4.6.6: Disabling destructive backspaceqBê¿/ .€„€ã}q:€€€‰‚ÿSection 4.6.7: Disabling remote character set configurationœkN[1ì¸ q L[ÄG Section 4.6.1: Disabling application keypad and cursor keysCBB("btn_up","JI(`',`t00000048')");EB("btn_up")i@¿Ä) "€€€€€€‚ÿSection 4.6.1: Disabling application keypad and cursor keysƒR[G 1 0€¥€˜€ã(~¦„‰ãneÇA‰‚ÿApplication keypad mode (see section 4.4.5) and application cursor keys mode (see section 4.4.4) alter the behaviour of the keypad and cursor keys. Some applications enable these modes but then do not deal correctly with the modified keys. You can force these modes to be permanently disabled no matter what the server tries to do.•dÄÜ 1Õß Š MÜ F ±Section 4.6.2: Disabling xterm-style mouse reportingCBB("btn_up","JI(`',`t00000048')");EB("btn_up")j;G F / .€v€€€€€€‚ÿSection 4.6.2: Disabling xterm-style mouse reporting`)Ü ¦ 7 <€S€˜€€€€€€€‚ÿPuTTY allows the server to send control codes that let it take over the mouse and use it for purposes other than copy and paste. Applications which use this feature include the text-mode web browser links, the Usenet newsreader trn version 4, and the file manager mc (Midnight Commander).óÈF ™ + $€‘€˜€€€‚ÿIf you find this feature inconvenient, you can disable it using the ‘Disable xterm-style mouse reporting’ control. With this box ticked, the mouse will always do copy and paste in the normal way.í¦ ±+ $€Û€˜€ã.Àà‰‚ÿNote that even if the application takes over the mouse, you can still manage PuTTY's copy and paste by holding down the Shift key while you select and paste, unless you have deliberately turned this feature off (see section 4.11.4).’a™ C1lq € NC¢»@Section 4.6.3: Disabling remote terminal resizingCBB("btn_up","JI(`',`t00000048')");EB("btn_up")_6±¢) "€l€€€€‚ÿSection 4.6.3: Disabling remote terminal resizing èC»@% €Ñ€˜€‚ÿPuTTY has the ability to change the terminal's size and ¢»@±position in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to those server commands.›j¢VA1Š ‚ OVA¾AYDSection 4.6.4: Disabling switching to the alternate screenCBB("btn_up","JI(`',`t00000048')");EB("btn_up")h?»@¾A) "€~€€€€‚ÿSection 4.6.4: Disabling switching to the alternate screen»–VAyC% €-€˜€‚ÿMany terminals, including PuTTY, support an ‘alternate screen’. This is the same size as the ordinary terminal screen, but separate. Typically a screen-based program such as a text editor might switch the terminal to the alternate screen before starting up. Then at the end of the run, it switches back to the primary screen, and you see the screen contents just as they were before starting the editor.໾AYD% €w€˜€‚ÿSome people prefer this not to happen. If you want your editor to run in the same screen as the rest of your terminal activity, you can disable the alternate screen feature completely.–eyCïD1`€ ¢ƒ PïDREOFSection 4.6.5: Disabling remote window title changingCBB("btn_up","JI(`',`t00000048')");EB("btn_up")c:YDRE) "€t€€€€‚ÿSection 4.6.5: Disabling remote window title changingýØïDOF% €±€˜€‚ÿPuTTY has the ability to change the window title in response to commands from the server. If you find PuTTY is doing this unexpectedly or inconveniently, you can tell PuTTY not to respond to those server commands.^REÞF1ê‚ >… QÞF:GÈHSection 4.6.6: Disabling destructive backspaceCBB("btn_up","JI(`',`t00000048')");EB("btn_up")\3OF:G) "€f€€€€‚ÿSection 4.6.6: Disabling destructive backspaceŽiÞFÈH% €Ó€˜€‚ÿNormally, when PuTTY receives character 127 (^?) from the server, it will perform a ‘destructive backspace’: move the cursor one space left and delete the character under it. This can apparently cause problems in some applications, so PuTTY provides the ability to configure character 127 to perform a normal backspace (without deleting a character) instead.œk:GdI1°¢ƒ {‡ RdIÍILSection 4.6.7: Disabling remote character set configurationCBB("btn_up","JI(`',`t00000048')");EB("btn_up")i@ÈHÍI) "€€€€€€‚ÿSection 4.6.7: Disabling remote character set configuration\7dI)K% €o€˜€‚ÿPuTTY has the ability to change its character set configuration in response to commands from the server. Some programs send these commands unexpectedly or inconveniently. In particular, BitchX (an IRC client) seems to have a habit of reconfiguring the character set to something other than the user intended.ëÆÍIL% €€˜€‚ÿIf you find that accented characters are not showing up the way you expect them to, particularly if you're running BitchX, you could try disabling the remote character set configuration commands.~M)K’L1ñ>… ’ˆ S’LÝLƒNSection 4.7: The Window panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")K"LÝL) "€D€€€€‚ÿSection 4.7: The Window panelxT’LUM$ €¨€˜€‚ÿThe Window configuration panel allows you to control aspects of the PuTTY window.i:ÝL¾M/ .€t€ã ï´ €€€‰‚ÿSection 4.7.1: Setting the size of the PuTTY windowj;UM(N/ .€v€ã„G6½€€€‰‚ÿSection 4.7.2: What to do when the window is resized[,¾MƒN/ .€X€ã¨;‹€€€‰‚ÿSection 4.7.3: Controlling scrollback”c(NO1({‡ TOxOK€Section 4.7.1: Setting the size of the PuTTY windowCBB("btn_up","JI(`',`t00000049')");EB("btn_up")a8ƒNxO) "€p€€€€‚ÿSection 4.7.1: Setting the size of the PuTTY windowÇ¢OK€% €E€˜€‚ÿThe ‘Rows’ and ‘Columns’ boxes let you set the PuTTY window to a precise size. Of course you can axOK€ƒNlso drag the window to a new size while a session is running.•dxOà€1n’ˆ  Uà€BN†Section 4.7.2: What to do when the window is resizedCBB("btn_up","JI(`',`t00000049')");EB("btn_up")b9K€B) "€r€€€€‚ÿSection 4.7.2: What to do when the window is resized†bà€È$ €Ä€˜€‚ÿThese options allow you to control what happens when the user tries to resize the PuTTY window.gCB/‚$ €†€˜€‚ÿWhen you resize the PuTTY window, one of four things can happen:e8È”‚- *€p€T˜‘€8‚€ƒ€‚ÿ•Nothing (if you have completely disabled resizes).‘d/‚%ƒ- *€È€T˜‘€8‚€ƒ€‚ÿ•The font size can stay the same and the number of rows and columns in the terminal can change.’e”‚·ƒ- *€Ê€T˜‘€8‚€ƒ€‚ÿ•The number of rows and columns in the terminal can stay the same, and the font size can change.÷Ã%ƒ®„4 6€‡€T˜‘€8‚€ƒ€€€‚ÿ•You can allow PuTTY to change either the terminal size or the font size. In this mode it will change the terminal size most of the time, but enlarge the font when you maximise the window. {·ƒN†% €÷€˜€‚ÿYou can control which of these happens using the ‘Lock terminal size against resizing’ and ‘Lock font size against resizing’ options. If you lock both, the window will refuse to be resized at all. If you lock just the terminal size, the font size will change when you resize the window. If you lock just the font size, the terminal size will change when you resize the window.†U®„Ô†1ã c VÔ†'‡·ŠSection 4.7.3: Controlling scrollbackCBB("btn_up","JI(`',`t00000049')");EB("btn_up")S*N†'‡) "€T€€€€‚ÿSection 4.7.3: Controlling scrollback§}Ô†·* $€ú€˜€ãyÄùN‰‚ÿThese options let you configure the way PuTTY keeps text after it scrolls off the top of the screen (see section 3.1.2).oJ'‡=‰% €•€˜€‚ÿThe ‘Lines of scrollback’ box lets you configure how many lines of text PuTTY keeps. The ‘Display scrollbar’ options allow you to hide the scrollbar (although you can still view the scrollback using Shift-PgUp and Shift-PgDn). You can separately configure whether the scrollbar is shown in full-screen mode and in normal modes.zU··Š% €«€˜€‚ÿIf you are viewing part of the scrollback when the server sends more text to PuTTY, the screen will revert to showing the current terminal contents. You can disable this behaviour by turning off ‘Reset scrollback on display activity’. You can also make the screen revert when you press a key, by turning on ‘Reset scrollback on keypress’.‚Q=‰9‹1ï  W9‹ˆ‹(ŽSection 4.8: The Appearance panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")O&·Šˆ‹) "€L€€€€‚ÿSection 4.8: The Appearance panelŒh9‹Œ$ €Ð€˜€‚ÿThe Appearance configuration panel allows you to control aspects of the appearance of PuTTY's window.m>ˆ‹Œ/ .€|€ã¾þ^Ù€€€‰‚ÿSection 4.8.1: Controlling the appearance of the cursoruFŒöŒ/ .€Œ€ãWÝŒÁ€€€‰‚ÿSection 4.8.2: Controlling the font used in the terminal windowa2ŒW/ .€d€ãìe|…€€€‰‚ÿSection 4.8.3: Controlling the window titleo@öŒÆ/ .€€€ã{ÍH+€€€‰‚ÿSection 4.8.4: ‘Hide mouse pointer when typing in window’b3W(Ž/ .€f€ãØdbÏ€€€‰‚ÿSection 4.8.5: Controlling the window border˜gÆÀŽ1öc g€ XÀŽ%ÂÀSection 4.8.1: Controlling the appearance of the cursorCBB("btn_up","JI(`',`t00000050')");EB("btn_up")e<(Ž%) "€x€€€€‚ÿSection 4.8.1: Controlling the appearance of the cursoráÀŽ7À% €Ã€˜€‚ÿThe ‘Cursor appearance’ option lets you configure the cursor to be a block, an underline, or a vertical line. A block cursor becomes an empty box when the window loses focus; an und%7À(Žerline or a vertical line becomes dotted.‹g%ÂÀ$ €Î€˜€‚ÿThe ‘Cursor blinks’ option makes the cursor blink on and off. This works in any of the cursor modes. o7ÀbÁ1­ Æ YbÁÏÁÃSection 4.8.2: Controlling the font used in the terminal windowCBB("btn_up","JI(`',`t00000050')");EB("btn_up")mDÂÀÏÁ) "€ˆ€€€€‚ÿSection 4.8.2: Controlling the font used in the terminal window@bÁÃ% €7€˜€‚ÿThis option allows you to choose what font, in what size, the PuTTY terminal window uses to display the text in the session. You will be offered a choice from all the fixed-width fonts installed on the system. (VT100-style terminal handling can only deal with fixed- width fonts.)Œ[ÏÁ›Ã1-g€ h† Z›ÃôÃÈÈSection 4.8.3: Controlling the window titleCBB("btn_up","JI(`',`t00000050')");EB("btn_up")Y0ÃôÃ) "€`€€€€‚ÿSection 4.8.3: Controlling the window title0›Ã$Å+ $€ €˜€€€‚ÿThe ‘Window title’ edit box allows you to set the title of the PuTTY window. By default the window title will contain the host name followed by ‘PuTTY’, for example server1.example.com - PuTTY. If you want a different window title, this is where to set it.¤môÃÈÈ7 <€Û€˜€€€€€€€‚ÿPuTTY allows the server to send xterm control sequences which modify the title of the window in mid-session. There is also an xterm sequence to modify the title of the window's icon. This makes sense in a windowing system where the window becomes an icon when minimised, such as Windows 3.1 or most X Window System setups; but in the Windows 95-like user interface it isn't as applicable. By default PuTTY's window title and Taskbar caption will change into the server-supplied icon title if you minimise the PuTTY window, and change back to the server-supplied window title if you restore it. (If the server has not bothered to supply a window or icon title, none of this will happen.) By checking the box marked ‘Avoid ever using icon title’, you can arrange that PuTTY will always display the window title, and completely ignore any icon titles the server sends it.ši$ÅbÉ1Æ ˆ [bÉÉÉtËSection 4.8.4: ‘Hide mouse pointer when typing in window’CBB("btn_up","JI(`',`t00000050')");EB("btn_up")g>ÈÈÉÉ) "€|€€€€‚ÿSection 4.8.4: ‘Hide mouse pointer when typing in window’. bÉ÷Ê% €€˜€‚ÿIf you enable this option, the mouse pointer will disappear if the PuTTY window is selected and you press a key. This way, it will not obscure any of the text in the window while you work in your session. As soon as you move the mouse, the pointer will reappear.}YÉÉtË$ €²€˜€‚ÿThis option is disabled by default, so the mouse pointer remains visible at all times.\÷ÊÌ1Xh† ÉŠ \Ì[ÌYÏSection 4.8.5: Controlling the window borderCBB("btn_up","JI(`',`t00000050')");EB("btn_up")Z1tË[Ì) "€b€€€€‚ÿSection 4.8.5: Controlling the window borderxTÌÓÌ$ €¨€˜€‚ÿPuTTY allows you to configure the appearance of the window border to some extent.tO[ÌGÎ% €Ÿ€˜€‚ÿThe checkbox marked ‘Sunken-edge border’ changes the appearance of the window border to something more like a DOS box: the inside edge of the border is highlighted as if it sank down to meet the surface inside the window. This makes the border a little bit thicker as well. It's hard to describe well. Try it and see if you like it.íÓÌYÏ% €Û€˜€‚ÿYou can also configure a completely blank gap between the text in the window and the border, using the ‘Gap between text and window edge’ control. By default this is set at one pixel. You can reduce it to zero, or increase it further.PGÎ 1)ˆ Â] Z5Section 4.9: The Behaviour panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")YÏ YÏN%YÏZ) "€J€€€€‚ÿSection 4.9: The Behaviour panelŠf ä$ €Ì€˜€‚ÿThe Behaviour configuration panel allows you to control aspects of the behaviour of PuTTY's window.a2ZE/ .€d€ã'wúû€€€‰‚ÿSection 4.9.1: ‘Warn before closing window’^/ä£/ .€^€ã0tW…€€€‰‚ÿSection 4.9.2: ‘Window closes on ALT-F4’g8E / .€p€ã°x²z€€€‰‚ÿSection 4.9.3: ‘System menu appears on ALT-Space’g8£q/ .€p€ã‚Ú±€€€‰‚ÿSection 4.9.4: ‘System menu appears on Alt alone’e6 Ö/ .€l€ãdî:a€€€‰‚ÿSection 4.9.5: ‘Ensure window is always on top’_0q5/ .€`€ãz?Öw€€€‰‚ÿSection 4.9.6: ‘Full screen on Alt-Enter’Œ[ÖÁ1 ÉŠ [^ÁÌSection 4.9.1: ‘Warn before closing window’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")Y05) "€`€€€€‚ÿSection 4.9.1: ‘Warn before closing window’!üÁ;% €ù€˜€‚ÿIf you press the Close button in a PuTTY window that contains a running session, PuTTY will put up a warning window asking if you really meant to close the window. A window whose session has already terminated can always be closed without a warning.‘mÌ$ €Ú€˜€‚ÿIf you want to be able to close a window quickly, you can disable the ‘Warn before closing window’ option.‰X;U1fÂm_U«»Section 4.9.2: ‘Window closes on ALT-F4’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")V-Ì«) "€Z€€€€‚ÿSection 4.9.2: ‘Window closes on ALT-F4’åU»+ $€Ë€˜€ã'wúû‰‚ÿBy default, pressing ALT-F4 causes the window to close (or a warning box to appear; see section 4.9.1). If you disable the ‘Window closes on ALT-F4’ option, then pressing ALT-F4 will simply send a key sequence to the server.’a«M1•[‰`M¬â Section 4.9.3: ‘System menu appears on ALT-Space’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")_6»¬) "€l€€€€‚ÿSection 4.9.3: ‘System menu appears on ALT-Space’×M® + $€¯€˜€€€‚ÿIf this option is enabled, then pressing ALT-Space will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing ALT-Space will just send ESC SPACE to the server.4¬â % €€˜€‚ÿSome accessibility programs for Windows may need this option enabling to be able to control PuTTY's window successfully. For instance, Dragon NaturallySpeaking requires it both to open the system menu via voice, and to close, minimise, maximise and restore the window.’a® t 1Vm‘at Ó Ê Section 4.9.4: ‘System menu appears on Alt alone’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")_6â Ó ) "€l€€€€‚ÿSection 4.9.4: ‘System menu appears on Alt alone’÷Òt Ê % €¥€˜€‚ÿIf this option is enabled, then pressing and releasing ALT will bring up the PuTTY window's menu, like clicking on the top left corner. If it is disabled, then pressing and releasing ALT will have no effect._Ó Z 1Ö‰bZ · 0Section 4.9.5: ‘Ensure window is always on top’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")]4Ê · ) "€h€€€€‚ÿSection 4.9.5: ‘Ensure window is always on top’yUZ 0$ €ª€˜€‚ÿIf this option is enabled, the PuTTY window will stay on top of all other windows.ŠY· º1í‘ž€cºÕ@Section 4.9.6: ‘Full screen on Alt-Enter’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")W.0) "€\€€€€‚ÿSection 4.9.6: ‘Full screen on Alt-Enter’ͨº @% €Q€˜€‚ÿIf this option is enabled, then pressing Alt-Enter will cause the PuTTY window to become full-screen. Pressing Alt-Enter again will restore the previous window size. @0ÉžÕ@+ $€=€˜€ã€ÄùN‰‚ÿThe full-screen feature is also available from the System menu, even when it is configured not to be available on the Alt-Enter key. See section 3.1.3.6.„S @YA1h+‚dYAªAÁCSection 4.10: The Translation panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")Q(Õ@ªA) "€P€€€€‚ÿSection 4.10: The Translation panelϪYAyB% €U€˜€‚ÿThe Translation configuration panel allows you to control the translation between the character set understood by the server and the character set understood by PuTTY.k<ªAäB/ .€x€ãoÅsº€€€‰‚ÿSection 4.10.1: Controlling character set translationi:yBMC/ .€t€ã¾¿í€€€‰‚ÿSection 4.10.2: ‘Caps Lock acts as Cyrillic switch’tEäBÁC/ .€Š€ã÷ù0Ô€€€‰‚ÿSection 4.10.3: Controlling display of line drawing characters–eMCWD1‹ž€=ˆeWDºDâKSection 4.10.1: Controlling character set translationCBB("btn_up","JI(`',`t00000052')");EB("btn_up")c:ÁCºD) "€t€€€€‚ÿSection 4.10.1: Controlling character set translationã¾WDE% €}€˜€‚ÿDuring an interactive session, PuTTY receives a stream of 8-bit bytes from the server, and in order to display them on the screen it needs to know what character set to interpret them in.d?ºDG% €€˜€‚ÿThere are a lot of character sets to choose from. The ‘Received data assumed to be in which character set’ option lets you select one. By default PuTTY will attempt to choose a character set that is right for your locale as reported by Windows; if it gets it wrong, you can select a different one using this control.H$EIG$ €H€˜€‚ÿA few notable character sets are:½GH. *€€T˜‘€8‚€ƒ€‚ÿ•The ISO-8859 series are all standard character sets that include various accented characters appropriate for different sets of languages.ÒIGI. *€¥€T˜‘€8‚€ƒ€‚ÿ•The Win125x series are defined by Microsoft, for similar purposes. In particular Win1252 is almost equivalent to ISO-8859-1, but contains a few extra characters such as matched quotes and the Euro symbol.¤wHªI- *€î€T˜‘€8‚€ƒ€‚ÿ•If you want the old IBM PC character set with block graphics and line-drawing characters, you can select ‘CP437’.*üIÔJ. *€ù€T˜‘€8‚€ƒ€‚ÿ•PuTTY also supports Unicode mode, in which the data coming from the server is interpreted as being in the UTF-8 encoding of Unicode. If you select ‘UTF-8’ as a character set you can use this mode. Not all server-side applications will support it.ãªIâK+ $€Ç€˜€€€‚ÿIf you need support for a numeric code page which is not listed in the drop-down list, such as code page 866, then you should be able to enter its name manually (CP866 for example) in the list box and get the right result.”cÔJvL1ì+‚·‰fvL×LbNSection 4.10.2: ‘Caps Lock acts as Cyrillic switch’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")a8âK×L) "€p€€€€‚ÿSection 4.10.2: ‘Caps Lock acts as Cyrillic switch’ýØvLÔM% €±€˜€‚ÿThis feature allows you to switch between a US/UK keyboard layout and a Cyrillic keyboard layout by using the Caps Lock key, if you need to type (for example) Russian and English side by side in the same document.Žj×LbN$ €Ô€˜€‚ÿCurrently this feature is not expected to work properly if your native keyboard layout is not US or UK.ŸnÔMO1k=ˆ¥gOmOx†Section 4.10.3: Controlling display of line drawing charactersCBB("btn_up","JI(`',`t00000052')");EB("btn_up")lCbNmO) "€†€€€€‚ÿSection 4.10.3: Controlling display of line drawing characters]8OÖ€% €q€˜€‚ÿVT100-series terminals allow the server to send control sequences that shift temporarily into a separate charmOÖ€bNacter set for drawing lines and boxes. PuTTY has a variety of ways to support this capability. In general you should probably try lots of options until you find one that your particular font supports.¯mO…‚. *€€T˜‘€8‚€ƒ€‚ÿ•‘Font has XWindows encoding’ is for use with fonts that have a special encoding, where the lowest 32 character positions (below the ASCII printable range) contain the line-drawing characters. This is unlikely to be the case with any standard Windows font; it will probably only apply to custom-built fonts or fonts that have been automatically converted from the X Window System./Ö€´ƒ. *€€T˜‘€8‚€ƒ€‚ÿ•‘Use font in both ANSI and OEM modes’ tries to use the same font in two different character sets, to obtain a wider range of characters. This doesn't always work; some fonts claim to be a different size depending on which character set you try to use.©|…‚]„- *€ø€T˜‘€8‚€ƒ€‚ÿ•‘Use font in OEM mode only’ is more reliable than that, but can miss out other characters from the main character set.@ú´ƒ…F Z€õ€T˜‘€8‚€ƒ€€€€€€€€€‚ÿ•‘Poor man's line drawing’ assumes that the font cannot generate the line and box characters at all, so it will use the +, - and | characters to draw approximations to boxes. You should use this option if none of the other options works.Û­]„x†. *€[€T˜‘€8‚€ƒ€‚ÿ•‘Unicode mode’ tries to use the box characters that are present in Unicode. For good Unicode-supporting fonts this is probably the most reliable and functional option.‚Q…ú†1N·‰Œhú†I‡HŠSection 4.11: The Selection panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")O&x†I‡) "€L€€€€‚ÿSection 4.11: The Selection panel]ú†ʇ$ €º€˜€‚ÿThe Selection panel allows you to control the way copy and paste work in the PuTTY window.xII‡Bˆ/ .€’€ãØk—Õ€€€‰‚ÿSection 4.11.1: Controlling the pasting of line drawing charactersa2ʇ£ˆ/ .€d€ã@ËÞ€‰‚ÿSection 4.11.2: Pasting in Rich Text Formato@Bˆ‰/ .€€€ãÙ“§.€€€‰‚ÿSection 4.11.3: Changing the actions of the mouse buttonsrC£ˆ„‰/ .€†€ã.Àà€€€‰‚ÿSection 4.11.4: ‘Shift overrides application's use of mouse’\-‰à‰/ .€Z€ã ·kJ€€€‰‚ÿSection 4.11.5: Default selection modeh9„‰HŠ/ .€r€ãý@€€€‰‚ÿSection 4.11.6: Configuring word-by-word selection£rà‰ëŠ1¥ iëŠ[‹íSection 4.11.1: Controlling the pasting of line drawing charactersCBB("btn_up","JI(`',`t00000053')");EB("btn_up")pGHŠ[‹) "€Ž€€€€‚ÿSection 4.11.1: Controlling the pasting of line drawing characters’IëŠíI `€“€˜€€€€€€€€€€€€€‚ÿBy default, when you copy and paste a piece of the PuTTY screen that contains VT100 line and box drawing characters, PuTTY will translate them into the ‘poor man's’ line-drawing characters +, - and |. The checkbox ‘Don't translate line drawing chars’ disables this feature, so line-drawing characters will be pasted as if they were in the normal character set. This will typically mean they come out mostly as q and x, with a scattering of jklmntuvw at the corners. This might be useful if you were trying to recreate the same box layout in another program, for example.Œ[[‹yŽ1«ŒH€jyŽÒŽ0ÁSection 4.11.2: Pasting in Rich Text FormatCBB("btn_up","JI(`',`t00000053')");EB("btn_up")Y0íÒŽ) "€`€€€€‚ÿSection 4.11.2: Pasting in Rich Text FormatæÁyŽÄÀ% €ƒ€˜€‚ÿIf you enable ‘Paste to clipboard in RTF as well as plain text’, PuTTY will write formatting information to the clipboard as well as the actual text you copy. Currently the only effect of this will be that if you paste into (say) a word processor, the text will apÒŽÄÀípear in the word processor in the same font PuTTY was using to display it. In future it is likely that other formatting information (bold, underline, colours) will be copied as well.lHÒŽ0Á$ €€˜€‚ÿThis option can easily be inconvenient, so by default it is disabled.šiÄÀÊÁ15 Í‚kÊÁ1ÂÿÄSection 4.11.3: Changing the actions of the mouse buttonsCBB("btn_up","JI(`',`t00000053')");EB("btn_up")g>0Á1Â) "€|€€€€‚ÿSection 4.11.3: Changing the actions of the mouse buttons,ÊÁ]Ã+ $€€˜€€€‚ÿPuTTY's copy and paste mechanism is modelled on the Unix xterm application. The X Window System uses a three-button mouse, and the convention is that the left button selects, the right button extends an existing selection, and the middle button pastes.à¯1Â=Ä1 0€_€˜€€€€€‚ÿWindows typically only has two mouse buttons, so in PuTTY's default configuration, the right button pastes, and the middle button (if you have one) extends a selection.—]ÃÿÄ+ $€/€˜€€€‚ÿIf you have a three-button mouse and you are already used to the xterm arrangement, you can select it using the ‘Action of mouse buttons’ control.l=ÄœÅ1*H€"‡lœÅÆÆÊSection 4.11.4: ‘Shift overrides application's use of mouse’CBB("btn_up","JI(`',`t00000053')");EB("btn_up")jAÿÄÆ) "€‚€€€€‚ÿSection 4.11.4: ‘Shift overrides application's use of mouse’`)œÅfÇ7 <€S€˜€€€€€€€‚ÿPuTTY allows the server to send control codes that let it take over the mouse and use it for purposes other than copy and paste. Applications which use this feature include the text-mode web browser links, the Usenet newsreader trn version 4, and the file manager mc (Midnight Commander).úÕÆ`È% €«€˜€‚ÿWhen running one of these applications, pressing the mouse buttons no longer performs copy and paste. If you do need to copy and paste, you can still do so if you hold down Shift while you do your mouse clicks.¨ƒfÇÊ% €€˜€‚ÿHowever, it is possible in theory for applications to even detect and make use of Shift + mouse clicks. We don't know of any applications that do this, but in case someone ever writes one, unchecking the ‘Shift overrides application's use of mouse’ checkbox will cause Shift + mouse clicks to go to the server as well (so that mouse-driven copy and paste will be completely disabled).¾“`ÈÆÊ+ $€'€˜€ãⳄ‰‚ÿIf you want to prevent the application from taking over the mouse at all, you can do this using the Features control panel; see section 4.6.2.‡VÊMË1lÍ‚ŠmMˡ˹ÎSection 4.11.5: Default selection modeCBB("btn_up","JI(`',`t00000053')");EB("btn_up")T+ÆÊ¡Ë) "€V€€€€‚ÿSection 4.11.5: Default selection modeïÄMËÍ+ $€‰€˜€ãxÄùN‰‚ÿAs described in section 3.1.1, PuTTY has two modes of selecting text to be copied to the clipboard. In the default mode (‘Normal’), dragging the mouse from point A to point B selects to the end of the line containing A, all the lines in between, and from the very beginning of the line containing B. In the other mode (‘Rectangular block’), dragging the mouse between two points defines a rectangle, and everything within that rectangle is copied.)þ¡Ë¹Î+ $€ý€˜€€€‚ÿNormally, you have to hold down Alt while dragging the mouse to select a rectangular block. Using the ‘Default selection mode’ control, you can set rectangular selection as the default, and then you have to hold down Alt to get the normal behaviour.“bÍLÏ1ï"‡>nLϬÏGSection 4.11.6: Configuring word-by-word selectionCBB("btn_up","JI(`',`t00000053')");EB("btn_up")`7¹Î¬Ï) "€n€€€€‚ÿSection 4.11.6: Configuring word-by-word selectionÔ¯LÏŒ% €_€˜€‚ÿPuTTY will select a word at a time in the term¬ÏŒ¹Îinal window if you double-click to begin the drag. This panel allows you to control precisely what is considered to be a word.F¬ÏÒ+ $€7€˜€€€‚ÿEach character is given a class, which is a small number (typically 0, 1 or 2). PuTTY considers a single word to be any number of adjacent characters in the same class. So by modifying the assignment of characters to classes, you can modify the word-by-word selection behaviour._;Œ1$ €v€˜€‚ÿIn the default configuration, the character classes are:g:Ò˜- *€t€T˜‘€8‚€ƒ€‚ÿ•Class 0 contains white space and control characters.U(1í- *€P€T˜‘€8‚€ƒ€‚ÿ•Class 1 contains most punctuation.»˜¨. *€€T˜‘€8‚€ƒ€‚ÿ•Class 2 contains letters, numbers and a few pieces of punctuation (the double quote, minus sign, period, forward slash and underscore).ºíb+ $€€˜€€€‚ÿSo, for example, if you assign the @ symbol into character class 2, you will be able to select an e-mail address with just a double click.س¨:% €g€˜€‚ÿIn order to adjust these assignments, you start by selecting a group of characters in the list box. Then enter a class number in the edit box below, and press the ‘Set’ button.ª…bä% € €˜€‚ÿThis mechanism currently only covers ASCII characters, because it isn't feasible to expand the list to cover the whole of Unicode.c2:G1 0€e€˜€€€ãÄùN‰‚ÿCharacter class definitions can be modified by control sequences sent by the server. This configuration option only controls the default state. If you modify this option in mid-session using ‘Change Settings’, you will need to reset the terminal (see section 3.1.3.5) before the change takes effect.€OäÇ1ôŠXoÇ» Section 4.12: The Colours panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")M$G) "€H€€€€‚ÿSection 4.12: The Colours paneleAÇy$ €‚€˜€‚ÿThe Colours panel allows you to control PuTTY's use of colour.i:â/ .€t€ã&áÝ\€€€‰‚ÿSection 4.12.1: ‘Bolded text is a different colour’g8yI / .€p€ãˆ))€€€‰‚ÿSection 4.12.2: ‘Attempt to use logical palettes’rCâ» / .€†€ã×TÇ€€€‰‚ÿSection 4.12.3: Adjusting the colours in the terminal window”cI O 1Ú>¿pO ° ) Section 4.12.1: ‘Bolded text is a different colour’CBB("btn_up","JI(`',`t00000054')");EB("btn_up")a8» ° ) "€p€€€€‚ÿSection 4.12.1: ‘Bolded text is a different colour’(O Ø % €€˜€‚ÿWhen the server sends a control sequence indicating that some text should be displayed in bold, PuTTY can handle this two ways. It can either change the font for a bold version, or use the same font in a brighter colour. This control lets you choose which.Q,° ) % €Y€˜€‚ÿBy default the box is checked, so non-bold text is displayed in light grey and bold text is displayed in bright white (and similarly in other colours). If you uncheck the box, bold and non-bold text will be displayed in the same colour, and instead the font will change to indicate the difference.’aØ » 1 XV q» ÅSection 4.12.2: ‘Attempt to use logical palettes’CBB("btn_up","JI(`',`t00000054')");EB("btn_up")_6) ) "€l€€€€‚ÿSection 4.12.2: ‘Attempt to use logical palettes’éÄ» % €‰€˜€‚ÿLogical palettes are a mechanism by which a Windows application running on an 8-bit colour display can select precisely the colours it wants instead of going with the Windows standard defaults.ÂÅ% €;€˜€‚ÿIf you are not getting the colours you ask for on an 8-bit display, you can try enabling this option. However, be warned that it's never worked very well.ln@1Ì¿Yƒrn@Ø@:DSection 4.Ån@Å12.3: Adjusting the colours in the terminal windowCBB("btn_up","JI(`',`t00000054')");EB("btn_up")jAÅØ@) "€‚€€€€‚ÿSection 4.12.3: Adjusting the colours in the terminal windowÕ°n@­B% €a€˜€‚ÿThe main colour control allows you to specify exactly what colours things should be displayed in. To modify one of the PuTTY colours, use the list box to select which colour you want to modify. The RGB values for that colour will appear on the right-hand side of the list box. Now, if you press the ‘Modify’ button, you will be presented with a colour selector, in which you can choose a new colour to go in place of the old one.hØ@:D% €Ñ€˜€‚ÿPuTTY allows you to set the cursor colour, the default foreground and background, and the precise shades of all the ANSI configurable colours (black, red, green, yellow, blue, magenta, cyan, and white). In addition, if you have selected ‘Bolded text is a different colour’, you can also modify the precise shades used for the bold versions of these colours.ƒR­B½D1bV ²„s½D EGSection 4.13: The Connection panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")P':D E) "€N€€€€‚ÿSection 4.13: The Connection panel‹g½D˜E$ €Î€˜€‚ÿThe Connection panel allows you to configure options that apply to more than one type of connection.\- EôE/ .€Z€ã6Õ€€€‰‚ÿSection 4.13.1: ‘Terminal-type string’[,˜EOF/ .€X€ã„õ€€€‰‚ÿSection 4.13.2: ‘Auto-login username’o@ôE¾F/ .€€€ãêøÂk€€€‰‚ÿSection 4.13.3: Using keepalives to prevent disconnectiona2OFG/ .€d€ãäMåN) "€|€€€€‚ÿSection 4.13.3: Using keepalives to prevent disconnectionÇ¢~N¬O% €E€˜€‚ÿIf you find your sessions are closing unexpectedly (‘Connection reset by peer’) after they have been idle for a while, you might want to try using this option.\åN9% €¹€˜€‚ÿSome network routers and firewalls need to kee¬O9äMp track of all connections through them. Usually, these firewalls will assume a connection is dead if no data is transferred in either direction after a certain time interval. This can cause PuTTY sessions to be unexpectedly closed by the firewall if no traffic is seen in the session for some time.ã¬OAƒ% €Ç€˜€‚ÿThe keepalive option (‘Seconds between keepalives’) allows you to configure PuTTY to send data through the session at regular intervals, in a way that does not disrupt the actual terminal session. If you find your firewall is cutting idle connections off, you can try entering a non-zero value in this field. The value is measured in seconds; so, for example, if your firewall cuts connections off after ten minutes then you might want to enter 300 seconds (5 minutes) in the box.ƒX9ć+ $€±€˜€€€‚ÿNote that keepalives are not always helpful. They help if you have a firewall which drops your connection after an idle period; but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem - neither endpoint will notice that anything was wrong. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. Keepalives can make this sort of problem worse, because they increase the probability that PuTTY will attempt to send data during a break in connectivity. Therefore, you might find they help connection loss, or you might find they make it worse, depending on what kind of network problems you have between you and the server.—sAƒ[ˆ$ €æ€˜€‚ÿKeepalives are only supported in Telnet and SSH; the Rlogin and Raw protocols offer no way of implementing them.޳ć9‰+ $€g€˜€ã‚îC‰‚ÿNote that if you are using SSH1 and the server has a bug that makes it unable to deal with SSH1 ignore messages (see section 4.20.1), enabling keepalives will have no effect.Œ[[ˆʼn10N‰ wʼnŠõ‹Section 4.13.4: ‘Disable Nagle's algorithm’CBB("btn_up","JI(`',`t00000055')");EB("btn_up")Y09‰Š) "€`€€€€‚ÿSection 4.13.4: ‘Disable Nagle's algorithm’…`ʼn£‹% €Á€˜€‚ÿNagle's algorithm is a detail of TCP/IP implementations that tries to minimise the number of small data packets sent down a network connection. With Nagle's algorithm enabled, PuTTY's bandwidth usage will be slightly more efficient; with it disabled, you may find you get a faster response to your keystrokes when connecting to some types of server.R.Šõ‹$ €\€˜€‚ÿThe Nagle algorithm is disabled by default.~M£‹sŒ1ªa€xsŒ¾Œ)ÀSection 4.14: The Proxy panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")K"õ‹¾Œ) "€D€€€€‚ÿSection 4.14: The Proxy panel\1sŒŽ+ $€c€˜€ã¥ÄùN‰‚ÿThe Proxy panel allows you to configure PuTTY to use various types of proxy in order to make its network connections. The settings in this panel affect the primary network connection forming your PuTTY session, but also any extra connections made as a result of SSH port forwarding (see section 3.5).\-¾ŒvŽ/ .€Z€ãè8–€€€‰‚ÿSection 4.14.1: Setting the proxy typerCŽèŽ/ .€†€ã ¥ÙZ€€€‰‚ÿSection 4.14.2: Excluding parts of the network from proxying[,vŽC/ .€X€ãÊh–€€€‰‚ÿSection 4.14.3: Username and passwordi:莬/ .€t€ã]½v€€€‰‚ÿSection 4.14.4: Specifying the Telnet proxy commandqBC)À/ .€„€ãŠnm €€€‰‚ÿSection 4.14.5: Selecting the ver¬)Àõ‹sion of the SOCKS protocolˆW¬±À1î  ƒy±ÀÁŸÄSection 4.14.1: Setting the proxy typeCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")T+)ÀÁ) "€V€€€€‚ÿSection 4.14.1: Setting the proxy typeôϱÀùÁ% €Ÿ€˜€‚ÿThe ‘Proxy type’ radio buttons allow you to configure what type of proxy you want PuTTY to use for its network connections. The default setting is ‘None’; in this mode no proxy is used for any connection.Æ’Á¿Â4 6€%€T˜‘€8‚€ƒ€€€‚ÿ•Selecting ‘HTTP’ allows you to proxy your connections through a web server supporting the HTTP CONNECT command, as documented in RFC 2817.TùÁ@Ã- *€¨€T˜‘€8‚€ƒ€‚ÿ•Selecting ‘SOCKS’ allows you to proxy your connections through a SOCKS server._+¿ÂŸÄ4 6€W€T˜‘€8‚€ƒ€€€‚ÿ•Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as connect myhost.com 22 to connect through to an external host. Selecting ‘Telnet’ allows you to tell PuTTY to use this type of proxy.žm@Ã=Å1Ø€Œ†z=ŧÅÊSection 4.14.2: Excluding parts of the network from proxyingCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")jAŸÄ§Å) "€‚€€€€‚ÿSection 4.14.2: Excluding parts of the network from proxying“n=Å:Ç% €Ý€˜€‚ÿTypically you will only need to use a proxy to connect to non-local parts of your network; for example, your proxy might be required for connections outside your company's internal network. In the ‘Exclude Hosts/IPs’ box you can enter ranges of IP addresses, or ranges of DNS names, for which PuTTY will avoid using the proxy and make a direct connection instead.îçÅ(È+ $€‡€˜€€€‚ÿThe ‘Exclude Hosts/IPs’ box may contain more than one exclusion range, separated by commas. Each range can be an IP address or a DNS name, with a * character allowing wildcards. For example:4:Ç\È$ € €˜€‚ÿ*.example.comwM(ÈÓÈ* $€š€˜€€€‚ÿThis excludes any host with a name ending in .example.com from proxying.3\ÈÉ$ €€˜€‚ÿ192.168.88.*xTÓÈ~É$ €¨€˜€‚ÿThis excludes any host with an IP address starting with 192.168.88 from proxying.AÉ¿É$ €:€˜€‚ÿ192.168.88.*,*.example.comV2~ÉÊ$ €d€˜€‚ÿThis excludes both of the above ranges at once.‡V¿ÉœÊ1³ ƒGˆ{œÊïÊOÍSection 4.14.3: Username and passwordCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")S*ÊïÊ) "€T€€€€‚ÿSection 4.14.3: Username and passwordyœÊŒË$ €ò€˜€‚ÿIf your proxy requires authentication, you can enter a username and a password in the ‘Username’ and ‘Password’ boxes.^:ïÊêË$ €t€˜€‚ÿAuthentication is not supported for all forms of proxy:Š]ŒËtÌ- *€º€T˜‘€8‚€ƒ€‚ÿ•Username and password authentication is supported for HTTP proxies and SOCKS 5 proxies.xKêËìÌ- *€–€T˜‘€8‚€ƒ€‚ÿ•SOCKS 4 can use the ‘Username’ field, but does not support passwords.c6tÌOÍ- *€l€T˜‘€8‚€ƒ€‚ÿ•Authentication is meaningless in Telnet proxies.•dìÌäÍ1˜Œ†¡|äÍEΈ Section 4.14.4: Specifying the Telnet proxy commandCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")a8OÍEÎ) "€p€€€€‚ÿSection 4.14.4: Specifying the Telnet proxy commandêäÍZÏ+ $€Õ€˜€€€‚ÿIf you are using the Telnet proxy type, the usual command required by the firewall's Telnet server is connect, followed by a host name and a port number. If your proxy needs a different command, you can enter an alternative here.DûEΪ I `€÷€˜€€€€€€€€€€€€€‚ÿIn this string, you can use \n to represent a new-line, \r to represent a carriage returZϪ OÍn, \t to represent a tab character, and \x followed by two hex digits to represent any other character. \\ is used to encode the \ character itself.Þ¡Zψ = H€C€˜€€€€€€€€€‚ÿAlso, the special strings %host and %port will be replaced by the host name and port number you want to connect to. To get a literal % sign, enter %%.lª % 1XGˆ«}% Ž } Section 4.14.5: Selecting the version of the SOCKS protocolCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")i@ˆ Ž ) "€€€€€€‚ÿSection 4.14.5: Selecting the version of the SOCKS protocolïÊ% } % €•€˜€‚ÿSOCKS servers exist in two versions: version 5 (RFC 1928) and the earlier version 4. The ‘SOCKS Version’ radio buttons allow you to select which one to use, if you have selected the SOCKS proxy type.NŽ ü 1Z¡ž~ü H V Section 4.15: The Telnet panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")L#} H ) "€F€€€€‚ÿSection 4.15: The Telnet panel{Wü à $ €®€˜€‚ÿThe Telnet panel allows you to configure options that only apply to Telnet sessions.].H  / .€\€ã‘E¹Ö€€€‰‚ÿSection 4.15.1: ‘Terminal-speed string’qBà ‘ / .€„€ã/PYÏ€€€‰‚ÿSection 4.15.2: Setting environment variables on the serveri:  ú / .€t€ã¶Ö　€‰‚ÿSection 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’qB‘ k / .€„€ãF{€€€‰‚ÿSection 4.15.4: Passive and active Telnet negotiation modesuFú à / .€Œ€ãìA/€€€‰‚ÿSection 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’vGk V / .€Ž€ã‚o¿¿€€€‰‚ÿSection 4.15.6: ‘Return key sends telnet New Line instead of ^M’ˆWà Þ 1p«ÀÞ 3 N Section 4.15.1: ‘Terminal-speed string’CBB("btn_up","JI(`',`t00000056')");EB("btn_up")U,V 3 ) "€X€€€€‚ÿSection 4.15.1: ‘Terminal-speed string’öÞ N % €í€˜€‚ÿTelnet allows the client to send a text string that describes the terminal speed. PuTTY lets you configure this, in case you find the server is reacting badly to the default value. (I'm not aware of any servers that do have a problem with it.)œk3 ê 1ža€ê S þ Section 4.15.2: Setting environment variables on the serverCBB("btn_up","JI(`',`t00000056')");EB("btn_up")i@N S ) "€€€€€€‚ÿSection 4.15.2: Setting environment variables on the serverzUê Í % €«€˜€‚ÿThe Telnet protocol also provides a means for the client to pass environment variables to the server. Many Telnet servers have stopped supporting this feature due to security flaws, but PuTTY still supports it for the benefit of any servers which have found other ways around the security problems than just disabling the whole mechanism.1 S þ % €€˜€‚ÿTo add an environment variable to the list transmitted down the connection, you enter the variable name in the ‘Variable’ box, enter its value in the ‘Value’ box, and press the ‘Add’ button. To remove one from the list, select it in the list box and press ‘Remove’.”cÍ ’ 1üÀ€’ ó šB Section 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’CBB("btn_up","JI(`',`t00000056')");EB("btn_up")a8þ ó ) "€p€€€€‚ÿSection 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’Y4’ L % €i€˜€‚ÿThe original Telnet mechanism for passing environment variables was badly specified. At the time the standard (RFC 1408) was written, BSD telnet implementations were already supporting the feature, and the intention of the standard was to describe the behaviour the BSD implementations were already using.‘ló é@ % €Ù€˜€‚ÿSadly there was a typing error in the standard when it was issued, and two vital function codes were specified the wrong way round. BSD implemL é@ þ entations did not change, and the standard was not corrected. Therefore, it's possible you might find either BSD or RFC-compliant implementations out there. This switch allows you to choose which one PuTTY claims to be.±€L šB 1 0€€˜€€€€€‚ÿThe problem was solved by issuing a second standard, defining a new Telnet mechanism called NEW_ENVIRON, which behaved exactly like the original OLD_ENVIRON but was not encumbered by existing implementations. Most Telnet servers now support this, and it's unambiguous. This feature should only be needed if you have trouble passing environment variables to quite an old server.œké@ 6C 1¸a…‚6C ŸC îG Section 4.15.4: Passive and active Telnet negotiation modesCBB("btn_up","JI(`',`t00000056')");EB("btn_up")i@šB ŸC ) "€€€€€€‚ÿSection 4.15.4: Passive and active Telnet negotiation modesÕª6C tD + $€U€˜€€€‚ÿIn a Telnet connection, there are two types of data passed between the client and the server: actual text, and negotiations about which Telnet extra features to use.^:ŸC ÒD $ €t€˜€‚ÿPuTTY can use two different strategies for negotiation:‘^tD cE 3 6€¼€T˜‘€8‚€ƒ€€€‚ÿ•In active mode, PuTTY starts to send negotiations as soon as the connection is opened.•bÒD øE 3 6€Ä€T˜‘€8‚€ƒ€€€‚ÿ•In passive mode, PuTTY will wait to negotiate until it sees a negotiation from the server.ä¿cE ÜF % €€˜€‚ÿThe obvious disadvantage of passive mode is that if the server is also operating in a passive mode, then negotiation will never begin at all. For this reason PuTTY defaults to active mode.íøE îG % €Û€˜€‚ÿHowever, sometimes passive mode is required in order to successfully get through certain types of firewall and Telnet proxy server. If you have confusing trouble with a firewall, you could try enabling passive mode to see if it helps. oÜF ŽH 1|€>†ƒŽH ûH J Section 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’CBB("btn_up","JI(`',`t00000056')");EB("btn_up")mDîG ûH ) "€ˆ€€€€‚ÿSection 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’êŽH J % €Õ€˜€‚ÿIf this box is checked, the Backspace key on the keyboard will send the Telnet special backspace code, and Control-C will send the Telnet special interrupt code. You probably shouldn't enable this unless you know what you're doing.¡pûH «J 1…㈄«J K ÃM Section 4.15.6: ‘Return key sends telnet New Line instead of ^M’CBB("btn_up","JI(`',`t00000056')");EB("btn_up")nE J K ) "€Š€€€€‚ÿSection 4.15.6: ‘Return key sends telnet New Line instead of ^M’V1«J oL % €c€˜€‚ÿUnlike most other remote login protocols, the Telnet protocol has a special ‘new line’ code that is not the same as the usual line endings of Control-M or Control-J. By default, PuTTY sends the Telnet New Line code when you press Return, instead of sending Control-M as it does in most other protocols.T/K ÃM % €_€˜€‚ÿMost Unix-style Telnet servers don't mind whether they receive Telnet New Line or Control-M; some servers do expect New Line, and some servers prefer to see ^M. If you are seeing surprising behaviour when you press Return in a Telnet session, you might try turning this option off to see if it helps.NoL BN 1z>†²‰…BN ŽN ¼O Section 4.16: The Rlogin panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")L#ÃM ŽN ) "€F€€€€‚ÿSection 4.16: The Rlogin panel{WBN O $ €®€˜€‚ÿThe Rlogin panel allows you to configure options that only apply to Rlogin sessions.].ŽN fO / .€\€ãÚÙI_€€€‰‚ÿSection 4.16.1: ‘Terminal-speed string’V' O ¼O / .€N€ãy÷OÉ€€€‰‚ÿSection 4.16.2: ‘Local username’ˆWfO P€ 1}ãˆ/†P€ ¥€ Í Section 4.16.1: ‘Te¼O P€ ¼O rminal-speed string’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")U,¼O ¥€ ) "€X€€€€‚ÿSection 4.16.1: ‘Terminal-speed string’(P€ Í % €€˜€‚ÿLike Telnet, Rlogin allows the client to send a text string that describes the terminal speed. PuTTY lets you configure this, in case you find the server is reacting badly to the default value. (I'm not aware of any servers that do have a problem with it.)P¥€ N‚ 1²‰S‡N‚ œ‚ _‰ Section 4.16.2: ‘Local username’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")N%Í œ‚ ) "€J€€€€‚ÿSection 4.16.2: ‘Local username’è«N‚ „„ = H€W€˜€€€€€€€€€‚ÿRlogin allows an automated (password-free) form of login by means of a file called .rhosts on the server. You put a line in your .rhosts file saying something like jbloggs@pc1.example.com, and then when you make an Rlogin connection the client transmits the username of the user running the Rlogin client. The server checks the username and hostname against .rhosts, and if they match it does not ask for a password.ôÏœ‚ x† % €Ÿ€˜€‚ÿThis only works because Unix systems contain a safeguard to stop a user from pretending to be another user in an Rlogin connection. Rlogin connections have to come from port numbers below 1024, and Unix systems prohibit this to unprivileged processes; so when the server sees a connection from a low-numbered port, it assumes the client end of the connection is held by a privileged (and therefore trusted) process, so it believes the claim of who the user is.󶄄 kˆ = H€m€˜€€€€€€€€€‚ÿWindows does not have this restriction: any user can initiate an outgoing connection from a low-numbered port. Hence, the Rlogin .rhosts mechanism is completely useless for securely distinguishing several different users on a Windows machine. If you have a .rhosts entry pointing at a Windows PC, you should assume that anyone using that PC can spoof your username in an Rlogin connection and access your account on the server.ôÏx† _‰ % €Ÿ€˜€‚ÿThe ‘Local username’ control allows you to specify what user name PuTTY should claim you have, in case it doesn't match your Windows user name (or in case you didn't bother to set up a Windows user name).|Kkˆ Û‰ 1º/ÕˆÛ‰ $Š •Œ Section 4.17: The SSH panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")I _‰ $Š ) "€@€€€€‚ÿSection 4.17: The SSH paneluQÛ‰ ™Š $ €¢€˜€‚ÿThe SSH panel allows you to configure options that only apply to SSH sessions.pA$Š ‹ / .€‚€ãóWâÜ€€€‰‚ÿSection 4.17.1: Executing a specific command on the serverh9™Š q‹ / .€r€ãçÑ€€€‰‚ÿSection 4.17.2: ‘Don't allocate a pseudo-terminal’Z+ ‹ Ë‹ / .€V€ãN§µ€€€‰‚ÿSection 4.17.3: ‘Enable compression’f7q‹ 1Œ / .€n€ã, ÛT€€€‰‚ÿSection 4.17.4: ‘Preferred SSH protocol version’d5Ë‹ •Œ / .€j€ãdÞ娀€€‰‚ÿSection 4.17.5: Encryption algorithm selection›j1Œ 0 1~S ‰0 ˜ ®Ž Section 4.17.1: Executing a specific command on the serverCBB("btn_up","JI(`',`t00000058')");EB("btn_up")h?•Œ ˜ ) "€~€€€€‚ÿSection 4.17.1: Executing a specific command on the serverñ0 ®Ž % €ã€˜€‚ÿIn SSH, you don't have to run a general shell session on the server. Instead, you can choose to run a single specific command (such as a mail user agent, for example). If you want to do this, enter the command in the ‘Remote command’ box.“b˜ A 1ÊÕ倊A ¡  Section 4.17.2: ‘Don't allocate a pseudo-terminal’CBB("btn_up","JI(`',`t00000058')");EB("btn_up")`7®Ž ¡ ) "€n€€€€‚ÿSection 4.17.2: ‘Don't allocate a pseudo-terminal’T)A Á + $€S€˜€€€‚ÿWhen connecting to a Unix system, most interactive ¡ Á ®Ž shell sessions are run in a pseudo-terminal, which allows the Unix system to pretend it's talking to a real physical terminal device but allows the SSH server to catch all the data coming from that fake device and send it back to the client.å¡  1 0€Ë€˜€€€ãü„ùN‰‚ÿOccasionally you might find you have a need to run a session not in a pseudo-terminal. In PuTTY, this is generally only useful for very specialist purposes; although in Plink (see chapter 7) it is the usual way of working.…TÁ œÂ 1³ J‚‹œÂ î OÄ Section 4.17.3: ‘Enable compression’CBB("btn_up","JI(`',`t00000058')");EB("btn_up")R) î ) "€R€€€€‚ÿSection 4.17.3: ‘Enable compression’a<œÂ OÄ % €y€˜€‚ÿThis enables data compression in the SSH connection: data sent by the server is compressed before sending, and decompressed at the client end. Likewise, data sent by PuTTY to the server is compressed first and the server decompresses it at the other end. This can help make the most of a low-bandwidth connection.‘`î àÄ 1Qå€äƒŒàÄ >Å 1Ç Section 4.17.4: ‘Preferred SSH protocol version’CBB("btn_up","JI(`',`t00000058')");EB("btn_up")^5OÄ >Å ) "€j€€€€‚ÿSection 4.17.4: ‘Preferred SSH protocol version’„`àÄ ÂÅ $ €À€˜€‚ÿThis allows you to select whether you would like to use SSH protocol version 1 or version 2. #>Å åÅ ! €€˜‚ÿ“oÂÅ xÆ $ €Þ€˜€‚ÿPuTTY will attempt to use protocol 1 if the server you connect to does not offer protocol 2, and vice versa.¹”åÅ 1Ç % €)€˜€‚ÿIf you select ‘1 only’ or ‘2 only’ here, PuTTY will only connect if the server you connect to offers the SSH protocol version you have specified.^xÆ ÀÇ 1!J‚ÀÇ È Section 4.17.5: Encryption algorithm selectionCBB("btn_up","JI(`',`t00000058')");EB("btn_up")\31Ç È ) "€f€€€€‚ÿSection 4.17.5: Encryption algorithm selectionÅ ÀÇ áÉ % €A€˜€‚ÿPuTTY supports a variety of different encryption algorithms, and allows you to choose which one you prefer to use. You can do this by dragging the algorithms up and down in the list box (or moving them using the Up and Down buttons) to specify a preference order. When you make an SSH connection, PuTTY will search down the list from the top until it finds an algorithm supported by the server, and then use that.¡}È ‚Ê $ €ú€˜€‚ÿIf the algorithm PuTTY finds is below the ‘warn below here’ line, you will see a warning box when you make the connection:N+áÉ ÐÊ # €V€€‚ÿThe first cipher supported by the serverR/‚Ê "Ë # €^€€‚ÿis single-DES, which is below the configured8ÐÊ ZË # €*€€‚ÿwarning threshold.T0"Ë ®Ë $ €`€˜€‚ÿDo you want to continue with this connection?tOZË "Í % €Ÿ€˜€‚ÿThis warns you that the first available encryption is not a very secure one. Typically you would put the ‘warn below here’ line between the encryptions you consider secure and the ones you consider substandard. By default, PuTTY supplies a preference order intended to reflect a reasonable preference in terms of security and speed.A®Ë cÎ % €9€˜€‚ÿIn SSH-2, the encryption algorithm is negotiated independently for each direction of the connection, although PuTTY does not support separate configuration of the preference orders. As a result you may get two warnings similar to the one above, possibly with different encryptions.~Y"Í % €³€˜€‚ÿSingle-DES is not supported natively in the SSH 2 draft protocol standards. One or two server implementations do support it, by a non-standard name. PuTTY can use single-DES to interoperate with these servers if you enable the ‘Enable non-standard single-DES in SSH 2’ option; by default this is disabled and PuTTY will stick to the standard.cÎ 1Ç }LcÎ ‰ 1ß䃧Ž‰ Ó h Section 4.18: The Auth panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")J! Ó ) "€B€€€€‚ÿSection 4.18: The Auth panelvR‰ I $ €¤€˜€‚ÿThe Auth panel allows you to configure authentication options for SSH sessions.pAÓ ¹ / .€‚€ã´—€€€‰‚ÿSection 4.18.1: ‘Attempt TIS or CryptoCard authentication’sDI , / .€ˆ€ãâ¢K!€€€‰‚ÿSection 4.18.2: ‘Attempt keyboard-interactive authentication’^/¹ Š / .€^€ãÊ6ÊÄ€€€‰‚ÿSection 4.18.3: ‘Allow agent forwarding’sD, ý / .€ˆ€ãU €€€‰‚ÿSection 4.18.4: ‘Allow attempted changes of username in SSH2’k<Š h / .€x€ã„@ÏØ€€€‰‚ÿSection 4.18.5: ‘Private key file for authentication’›jý  1jž k m Section 4.18.1: ‘Attempt TIS or CryptoCard authentication’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")h?h k ) "€~€€€€‚ÿSection 4.18.1: ‘Attempt TIS or CryptoCard authentication’T/ ¿ % €_€˜€‚ÿTIS and CryptoCard authentication are simple challenge/response forms of authentication available in SSH protocol version 1 only. You might use them if you were using S/Key one-time passwords, for example, or if you had a physical security token that generated responses to authentication challenges.®‰k m % €€˜€‚ÿWith this switch enabled, PuTTY will attempt these forms of authentication if the server is willing to try them. You will be presented with a challenge string (which will be different every time) and must supply the correct response in order to log in. If your server supports this, you should talk to your system administrator about precisely what form these challenges and responses take.žm¿  1“§¿  v ž Section 4.18.2: ‘Attempt keyboard-interactive authentication’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")kBm v ) "€„€€€€‚ÿSection 4.18.2: ‘Attempt keyboard-interactive authentication’‡b  ý % €Å€˜€‚ÿThe SSH 2 equivalent of TIS authentication is called ‘keyboard-interactive’. It is a flexible authentication method using an arbitrary sequence of requests and responses; so it is not only useful for challenge/response mechanisms such as S/Key, but it can also be used for (for example) asking the user for a new password when the old one has expired.¡}v ž $ €ú€˜€‚ÿPuTTY leaves this option enabled by default, but supplies a switch to turn it off in case you should have trouble with it.‰Xý ' 1(žb‘' } O Section 4.18.3: ‘Allow agent forwarding’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")V-ž } ) "€Z€€€€‚ÿSection 4.18.3: ‘Allow agent forwarding’È£' E % €G€˜€‚ÿThis option allows the SSH server to open forwarded connections back to your local copy of Pageant. If you are not running Pageant, this option will do nothing. Ó} O 7 <€§€˜€ã80«f‰ã¢ƒùN‰ã£ƒùN‰‚ÿSee chapter 9 for general information on Pageant, and section 9.4 for information on agent forwarding. Note that there is a security risk involved with enabling this option; see section 9.5 for details.žmE í 1]¿ÿ€’í X VB Section 4.18.4: ‘Allow attempted changes of username in SSH2’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")kBO X ) "€„€€€€‚ÿSection 4.18.4: ‘Allow attempted changes of username in SSH2’Üí Y % €¹€˜€‚ÿIn the SSH 1 protocol, it is impossible to change username after failing to authenticate. So if you mis-type your username at the PuTTY ‘login as:’ prompt, you will not be able to change it except by restarting PuTTY.Í¢X 2A + $€E€˜€€€‚ÿThe SSH 2 protocol does allow changes of username, in principle, but does not make it mandatory for SSH 2 servers to acceY 2A O pt them. In particular, OpenSSH does not accept a change of username; once you have sent one username, it will reject attempts to try to authenticate as another user. (Depending on the version of OpenSSH, it may quietly return failure for all login attempts, or it may send an error message.)$ÿY VB % €ÿ€˜€‚ÿFor this reason, PuTTY will by default not prompt you for your username more than once, in case the server complains. If you know your server can cope with it, you can enable the ‘Allow attempted changes of username’ option to modify PuTTY's behaviour.–e2A ìB 1Bbí“ìB OC .D Section 4.18.5: ‘Private key file for authentication’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")c:VB OC ) "€t€€€€‚ÿSection 4.18.5: ‘Private key file for authentication’ß´ìB .D + $€i€˜€ãxƒùN‰‚ÿThis box is where you enter the name of your private key file if you are using public key authentication. See chapter 8 for information about public key authentication in SSH.€OOC ®D 1ùÿ€ ƒ”®D ûD §F Section 4.19: The Tunnels panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")M$.D ûD ) "€H€€€€‚ÿSection 4.19: The Tunnels panell®D ‹E $ €Ø€˜€‚ÿThe Tunnels panel allows you to configure tunnelling of other connection types through an SSH connection.T%ûD ßE / .€J€ãwÑJ¶€€€‰‚ÿSection 4.19.1: X11 forwardingU&‹E 4F / .€L€ãíˆÆ#€€€‰‚ÿSection 4.19.2: Port forwardingsDßE §F / .€ˆ€ãÈ6çY€€€‰‚ÿSection 4.19.3: Controlling the visibility of forwarded portsN4F &G 1¼í+…•&G rG âI Section 4.19.1: X11 forwardingCBB("btn_up","JI(`',`t00000060')");EB("btn_up")L#§F rG ) "€F€€€€‚ÿSection 4.19.1: X11 forwardingÇ¢&G 9H % €E€˜€‚ÿIf your server lets you run X Window System applications, X11 forwarding allows you to securely give those applications access to a local X display on your PC.@rG yI % €7€˜€‚ÿTo enable X11 forwarding, check the ‘Enable X11 forwarding’ box. If your X display is not the primary display on your local machine (which it almost certainly will be unless you have deliberately arranged otherwise), you need to enter its location in the ‘X display location’ box.i?9H âI * $€~€˜€ã¤ÄùN‰‚ÿSee section 3.4 for more information about X11 forwarding.€OyI bJ 1ö ƒ½–bJ ¯J d Section 4.19.2: Port forwardingCBB("btn_up","JI(`',`t00000060')");EB("btn_up")M$âI ¯J ) "€H€€€€‚ÿSection 4.19.2: Port forwardingÙ®bJ ˆK + $€]€˜€ã¥ÄùN‰‚ÿPort forwarding allows you to tunnel other types of network connection down an SSH session. See section 3.5 for a general discussion of port forwarding and how it works.ܯJ ‰L % €¹€˜€‚ÿThe port forwarding section in the Tunnels panel shows a list of all the port forwardings that PuTTY will try to set up when it connects to the server. By default no port forwardings are set up, so this list is empty.@ˆK ÉL $ €8€˜€‚ÿTo add a port forwarding:ùˉL ÂM . *€—€T˜‘€8‚€ƒ€‚ÿ•Set one of the ‘Local’ or ‘Remote’ radio buttons, depending on whether you want to forward a local port to a remote destination (‘Local’) or forward a remote port to a local destination (‘Remote’).X*ÉL O . *€U€T˜‘€8‚€ƒ€‚ÿ•Enter a source port number into the ‘Source port’ box. For local forwardings, PuTTY will listen on this port of your PC. For remote forwardings, your SSH server will listen on this port of the remote machine. Note that most servers will not allow you to listen on port numbers less than 1024.0üÂM V€ 4 6€ù€T˜‘€8‚€ƒ€€€‚ÿ•Enter a hostname and port number separated by a colon, in the ‘Destination’ box. Connections received on the source port will be directed to this destination. For example, toO V€ âI connect to a POP-3 server, you might enter popserver.example.com:110.TO ×€ - *€¨€T˜‘€8‚€ƒ€‚ÿ•Click the ‘Add’ button. Your forwarding details should appear in the list box.iV€ d $ €Ò€˜€‚ÿTo remove a port forwarding, simply select its details in the list box, and click the ‘Remove’ button.žm×€ ‚ 1ý+…—‚ m‚ ÿ… Section 4.19.3: Controlling the visibility of forwarded portsCBB("btn_up","JI(`',`t00000060')");EB("btn_up")kBd m‚ ) "€„€€€€‚ÿSection 4.19.3: Controlling the visibility of forwarded portsú‚ Œƒ % €õ€˜€‚ÿThe source port for a forwarded connection usually does not accept connections from any machine except the SSH client or server machine itself (for local and remote forwardings respectively). There are controls in the Tunnels panel to change this:ÿÑm‚ ‹„ . *€£€T˜‘€8‚€ƒ€‚ÿ•The ‘Local ports accept connections from other hosts’ option allows you to set up local-to-remote port forwardings in such a way that machines other than your client PC can connect to the forwarded port.tFŒƒ ÿ… . *€€T˜‘€8‚€ƒ€‚ÿ•The ‘Remote ports do the same’ option does the same thing for remote-to-local port forwardings (so that machines other than the SSH server machine can connect to the forwarded port.) Note that this feature is only available in the SSH 2 protocol, and not all SSH 2 servers support it (OpenSSH 3.0 does not, for example).}L‹„ |† 14½Ö ˜|† Ɔ °Ž Section 4.20: The Bugs panelCBB("btn_up","JI(`',`t00000043')");EB("btn_up")J!ÿ… Ɔ ) "€B€€€€‚ÿSection 4.20: The Bugs panelã¾|† ©‡ % €}€˜€‚ÿNot all SSH servers work properly. Various existing servers have bugs in them, which can make it impossible for a client to talk to them unless it knows about the bug and works around it.îÉƆ —‰ % €“€˜€‚ÿSince most servers announce their software version number at the beginning of the SSH connection, PuTTY will attempt to detect which bugs it can expect to see in the server and automatically enable workarounds. However, sometimes it will make mistakes; if the server has been deliberately configured to conceal its version number, or if the server is a version which PuTTY's bug database does not know about, then PuTTY will not know what bugs to expect.°‹©‡ GŠ % €€˜€‚ÿThe Bugs panel allows you to manually configure the bugs PuTTY expects to see in the server. Each bug can be configured in three states:m@—‰ ´Š - *€€€T˜‘€8‚€ƒ€‚ÿ•‘Off’: PuTTY will assume the server does not have the bug.p=GŠ $‹ 3 6€z€T˜‘€8‚€ƒ€€€‚ÿ•‘On’: PuTTY will assume the server does have the bug.©|´Š Í‹ - *€ø€T˜‘€8‚€ƒ€‚ÿ•‘Auto’: PuTTY will use the server's version number announcement to try to guess whether or not the server has the bug.f7$‹ 3Œ / .€n€ã‚îC€€€‰‚ÿSection 4.20.1: ‘Chokes on SSH1 ignore messages’l=Í‹ ŸŒ / .€z€ã=0€€€‰‚ÿSection 4.20.2: ‘Refuses all SSH1 password camouflage’i:3Œ  / .€t€ã‚-‘€€€‰‚ÿSection 4.20.3: ‘Chokes on SSH1 RSA authentication’b3ŸŒ j / .€f€ã‚µQ€€€‰‚ÿSection 4.20.4: ‘Miscomputes SSH2 HMAC keys’h9 Ò / .€r€ãïÜ7Y€€€‰‚ÿSection 4.20.5: ‘Miscomputes SSH2 encryption keys’o@j AŽ / .€€€ãš§žè€€€‰‚ÿSection 4.20.6: ‘Requires padding on SSH2 RSA signatures’o@Ò °Ž / .€€€ã½T¯ó€€€‰‚ÿSection 4.20.7: ‘Chokes on Diffie-Hellman group exchange’‘`AŽ A 1š‚™A Ÿ çà Section 4.20.1: ‘Chokes on SSH1 ignore messages’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")^5°Ž Ÿ ) "€j€€€€‚ÿSection 4.20.1: ‘Chokes on SSH1 ignore messages’é¾A ”Á + $€}€˜€ãêøÂk‰‚ÿAn ignore message (SSH_MSG_IGNORE) is a message in thŸ ”Á °Ž e SSH protocol which can be sent from the client to the server, or from the server to the client, at any time. Either side is required to ignore the message whenever it receives it. PuTTY uses ignore messages to hide the password packet in SSH1, so that a listener cannot tell the length of the user's password; it also uses ignore messages for connection keepalives (see section 4.13.3).ѦŸ eà + $€M€˜€ã=0‰‚ÿIf this bug is detected, PuTTY will stop using ignore messages. This means that keepalives will stop working, and PuTTY will have to fall back to a secondary defence against SSH1 password-length eavesdropping. See section 4.20.2. If this bug is enabled when talking to a correct server, the session will succeed, but keepalives will not work and the session might be more vulnerable to eavesdroppers than it could be.‚^”Á çà $ €¼€˜€‚ÿThis is an SSH1-specific bug. No known SSH2 server fails to deal with SSH2 ignore messages.—feà ~Ä 1¾Ö †š~Ä âÄ <É Section 4.20.2: ‘Refuses all SSH1 password camouflage’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")d;çà âÄ ) "€v€€€€‚ÿSection 4.20.2: ‘Refuses all SSH1 password camouflage’`/~Ä BÇ 1 0€_€˜€ã‚îC‰€€‚ÿWhen talking to an SSH1 server which cannot deal with ignore messages (see section 4.20.1), PuTTY will attempt to disguise the length of the user's password by sending additional padding within the password packet. This is technically a violation of the SSH1 specification, and so PuTTY will only do it when it cannot use standards-compliant ignore messages as camouflage. In this sense, for a server to refuse to accept a padded password packet is not really a bug, but it does make life inconvenient if the server can also not handle ignore messages.ŠeâÄ ÌÈ % €Ë€˜€‚ÿIf this ‘bug’ is detected, PuTTY will have no choice but to send the user's password with no form of camouflage, so that an eavesdropping user will be easily able to find out the exact length of the password. If this bug is enabled when talking to a correct server, the session will succeed, but will be more vulnerable to eavesdroppers than it could be.pLBÇ <É $ €˜€˜€‚ÿThis is an SSH1-specific bug. SSH2 is secure against this type of attack.”cÌÈ ÐÉ 1Ö‚^ˆ›ÐÉ 1Ê ¦Ì Section 4.20.3: ‘Chokes on SSH1 RSA authentication’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")a8<É 1Ê ) "€p€€€€‚ÿSection 4.20.3: ‘Chokes on SSH1 RSA authentication’6ÐÉ gË % €#€˜€‚ÿSome SSH1 servers cannot deal with RSA authentication messages at all. If Pageant is running and contains any SSH1 keys, PuTTY will normally automatically try RSA authentication before falling back to passwords, so these servers will crash when they see the RSA attempt.ûÖ1Ê bÌ % €­€˜€‚ÿIf this bug is detected, PuTTY will go straight to password authentication. If this bug is enabled when talking to a correct server, the session will succeed, but of course RSA authentication will be impossible.D gË ¦Ì $ €@€˜€‚ÿThis is an SSH1-specific bug.\bÌ 3Í 1솜3Í Í + Section 4.20.4: ‘Miscomputes SSH2 HMAC keys’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")Z1¦Ì Í ) "€b€€€€‚ÿSection 4.20.4: ‘Miscomputes SSH2 HMAC keys’H3Í ÕÎ + $€;€˜€€€‚ÿVersions 2.3.0 and below of the SSH server software from ssh.com compute the keys for their HMAC message authentication codes incorrectly. A typical symptom of this problem is that PuTTY dies unexpectedly at the beginning of the session, saying ‘Incorrect MAC received on packet’.áÍ ÛÏ % €Ã€˜€‚ÿIf this bug is detected, PuTTY will compute its HMAC keys in the same way as the buggy server, so that communication will still be possible. If this bug is enabled when talking to a correct server, communication will fail.D ÕÎ + $ €@€˜€‚ÿÛÏ + ¦Ì This is an SSH2-specific bug.“bÛÏ ¾ 1Û^ˆ>¾  ™ Section 4.20.5: ‘Miscomputes SSH2 encryption keys’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")`7+  ) "€n€€€€‚ÿSection 4.20.5: ‘Miscomputes SSH2 encryption keys’+¾ I + $€€˜€€€‚ÿVersions below 2.1.0 of the SSH server software from ssh.com compute the keys for the session encryption incorrectly. This problem can cause various error messages, such as ‘Incoming packet was garbled on decryption’, or possibly even ‘Out of memory’. ç U % €Ï€˜€‚ÿIf this bug is detected, PuTTY will compute its encryption keys in the same way as the buggy server, so that communication will still be possible. If this bug is enabled when talking to a correct server, communication will fail.D I ™ $ €@€˜€‚ÿThis is an SSH2-specific bug.šiU 3 1’9ž3 š Å Section 4.20.6: ‘Requires padding on SSH2 RSA signatures’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")g>™ š ) "€|€€€€‚ÿSection 4.20.6: ‘Requires padding on SSH2 RSA signatures’¡|3 ; % €ù€˜€‚ÿVersions below 3.3 of OpenSSH require SSH2 RSA signatures to be padded with zero bytes to the same length as the RSA key modulus. The SSH2 draft specification says that an unpadded signature MUST be accepted, so this is a bug. A typical symptom of this problem is that PuTTY mysteriously fails RSA authentication once in every few hundred attempts, and falls back to passwords.F!š  % €C€˜€‚ÿIf this bug is detected, PuTTY will pad its signatures in the way OpenSSH expects. If this bug is enabled when talking to a correct server, it is likely that no damage will be done, since correct servers usually still accept padded signatures because they're used to talking to OpenSSH.D ; Å $ €@€˜€‚ÿThis is an SSH2-specific bug.ši _ 1#>¿Ÿ_ Æ ‚ Section 4.20.7: ‘Chokes on Diffie-Hellman group exchange’CBB("btn_up","JI(`',`t00000061')");EB("btn_up")g>Å Æ ) "€|€€€€‚ÿSection 4.20.7: ‘Chokes on Diffie-Hellman group exchange’d?_ * % €€˜€‚ÿWe have anecdotal evidence that some SSH servers claim to be able to perform Diffie-Hellman group exchange, but fail to actually do so when PuTTY tries to. If your SSH2 sessions spontaneously close immediately after opening the PuTTY window, it might be worth enabling the workaround for this bug to see if it helps.éÆ > + $€Ó€˜€€€‚ÿWe have no hard evidence that any specific version of specific server software reliably demonstrates this bug. Therefore, PuTTY will never assume a server has this bug; if you want the workaround, you need to enable it manually.D * ‚ $ €@€˜€‚ÿThis is an SSH2-specific bug.Ž]>  1 9ƒ  k %E Section 4.21: Storing configuration in a fileCBB("btn_up","JI(`',`t00000043')");EB("btn_up")[2‚ k ) "€d€€€€‚ÿSection 4.21: Storing configuration in a fileÅ  0 % €A€˜€‚ÿPuTTY does not currently support storing its configuration in a file instead of the Registry. However, you can work around this with a couple of batch files.Nk ¯ 1 0€€˜€€€€€‚ÿYou will need a file called (say) PUTTY.BAT which imports the contents of a file into the Registry, then runs PuTTY, exports the contents of the Registry back into the file, and deletes the Registry entries. This can all be done using the Regedit command line options, so it's all automatic. Here is what you need in PUTTY.BAT:/ 0 Þ # €€€‚ÿ@ECHO OFF:¯  # €.€€‚ÿregedit /s putty.reg=Þ U # €4€€‚ÿregedit /s puttyrnd.reg8  # €*€€‚ÿstart /w putty.exejGU @ # €Ž€€‚ÿregedit /e puttynew.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTY @ ‚ A M@ # €<€€‚ÿcopy puttynew.reg putty.reg6 @ ƒ@ # €&€€‚ÿdel puttynew.reg>M@ Á@ $ €4€˜€‚ÿregedit /s puttydel.reg1úƒ@ òA 7 <€õ€˜€€€€€€€‚ÿThis batch file needs two auxiliary files: PUTTYRND.REG which sets up an initial safe location for the PUTTY.RND random seed file, and PUTTYDEL.REG which destroys everything in the Registry once it's been successfully saved back to the file.DÁ@ 6B * $€4€˜€€€‚ÿHere is PUTTYDEL.REG:. òA dB # €€€‚ÿREGEDIT4'6B ‹B # €€€‚ÿ V2dB áB $ €d€˜€‚ÿ[-HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]T*‹B 5C * $€T€˜€€€‚ÿHere is an example PUTTYRND.REG file:. áB cC # €€€‚ÿREGEDIT4'5C ŠC # €€€‚ÿ T1cC ÞC # €b€€‚ÿ[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]D ŠC "D $ €@€˜€‚ÿ"RandSeedFile"="a:\putty.rnd"ØÞC %E + $€±€˜€€€‚ÿYou should replace a:\putty.rnd with the location where you want to store your random number data. If the aim is to carry around PuTTY and its settings on one floppy, you probably want to store it on the floppy.‹Z"D °E 1°¿­„¡°E F `H Chapter 5: Using PSCP to transfer files securelyCBB("btn_up","JI(`',`Top')");EB("btn_up")^5%E F ) "€j€€€€‚ÿChapter 5: Using PSCP to transfer files securelyŸ{°E ­F $ €ö€˜€‚ÿPSCP, the PuTTY Secure Copy client, is a tool for transferring files securely between computers using an SSH connection.Ä™F qG + $€3€˜€ã‚ÅùN‰‚ÿIf you have an SSH 2 server, you might prefer PSFTP (see chapter 6) for interactive use. PSFTP does not in general work with SSH 1 servers, however.P!­F ÁG / .€B€ãRÅùN€€€‰‚ÿSection 5.1: Starting PSCPMqG H / .€<€ãSÅùN€€€‰‚ÿSection 5.2: PSCP UsageR#ÁG `H / .€F€ãÅùN€€€‰‚ÿSection 5.3: Secure iXplorer{JH ÛH 1iƒ<ˆ¢ÛH #I DM Section 5.1: Starting PSCPCBB("btn_up","JI(`',`t00000063')");EB("btn_up")H`H #I ) "€>€€€€‚ÿSection 5.1: Starting PSCPƒ^ÛH ¦J % €½€˜€‚ÿPSCP is a command line application. This means that you cannot just double-click on its icon to run it and instead you have to bring up a console window. With Windows 95, 98, and ME, this is called an ‘MS-DOS Prompt’ and with Windows NT and 2000 it is called a ‘Command Prompt’. It should be available from the Programs section of your Start Menu.ð¿#I –K 1 0€€˜€€€€€‚ÿTo start PSCP it will need either to be on your PATH or in your current directory. To add the directory containing PSCP to your PATH environment variable, type into the console window:Q-¦J çK $ €Z€˜€‚ÿset PATH=C:\path\to\putty\directory;%PATH%]&–K DM 7 <€M€˜€€€€€€€‚ÿThis will only work for the lifetime of that particular console window. To set your PATH more permanently on Windows NT, use the Environment tab of the System Control Panel. On Windows 95, 98, and ME, you will need to edit your AUTOEXEC.BAT to include a set command like the one above.xGçK ¼M 1 ­„¸£¼M N Û† Section 5.2: PSCP UsageCBB("btn_up","JI(`',`t00000063')");EB("btn_up")EDM N ) "€8€€€€‚ÿSection 5.2: PSCP UsageÕ¼M O + $€«€˜€€€‚ÿOnce you've got a console window to type into, you can just type pscp on its own to bring up a usage message. This tells you the version of PSCP you're using, and gives you a brief summary of how to use PSCP:8N 9O # €*€€‚ÿZ:\owendadmin>pscp>O wO # €6€€‚ÿPuTTY Secure Copy client29O ©O # €€€‚ÿRelease 0.53U2wO € # €d€€‚ÿUsage: pscp [options] [user@]host:source target©O € DM a>©O m€ # €|€€‚ÿ pscp [options] source [source...] [user@]host:targetR/ € ¿€ # €^€€‚ÿ pscp [options] -ls user@host:filespec. m€ í€ # €€€‚ÿOptions:J'¿€ 7 # €N€€‚ÿ -p preserve file attributesN+í€ … # €V€€‚ÿ -q quiet, don't show statisticsN+7 Ó # €V€€‚ÿ -r copy directories recursivelyG$… ‚ # €H€€‚ÿ -v show verbose messagesX5Ó r‚ # €j€€‚ÿ -load sessname Load settings from saved sessionK(‚ ½‚ # €P€€‚ÿ -P port connect to specified portQ.r‚ ƒ # €\€€‚ÿ -l user connect with specified usernameO,½‚ ]ƒ # €X€€‚ÿ -pw passw login with specified password^;ƒ »ƒ # €v€€‚ÿ -1 -2 force use of particular SSH protocol versionD!]ƒ ÿƒ # €B€€‚ÿ -C enable compressionU2»ƒ T„ # €d€€‚ÿ -i key private key file for authenticationQ.ÿƒ ¥„ # €\€€‚ÿ -batch disable all interactive promptsZ6T„ ÿ„ $ €l€˜€‚ÿ -unsafe allow server-side wildcards (DANGEROUS)‚X¥„ … * $€°€˜€€€‚ÿ(PSCP's interface is much like the Unix scp command, if you're familiar with that.)O ÿ„ Ð… / .€@€ãTÅùN€€€‰‚ÿSection 5.2.1: The basicsL… † / .€:€ãzÅùN€€€‰‚ÿSection 5.2.2: OptionsQ"Ð… m† / .€D€ãÅùN€€€‰‚ÿSection 5.2.3: Return valuen?† Û† / .€~€ã€ÅùN€€€‰‚ÿSection 5.2.4: Using public key authentication with PSCPzIm† U‡ 1ž<ˆƒƒ¤U‡ œ‡ ÿÅ Section 5.2.1: The basicsCBB("btn_up","JI(`',`t00000065')");EB("btn_up")GÛ† œ‡ ) "€<€€€€‚ÿSection 5.2.1: The basicsS/U‡ ï‡ $ €^€˜€‚ÿTo receive (a) file(s) from a remote server:O+œ‡ >ˆ $ €V€˜€‚ÿpscp [options] [user@]host:source targetÆ‰ï‡ ‰ = H€€˜€€€€€€€€€‚ÿSo to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type:a=>ˆ e‰ $ €z€˜€‚ÿpscp fred@example.com:/etc/hosts c:\temp\example-hosts.txtN*‰ ³‰ $ €T€˜€‚ÿTo send (a) file(s) to a remote server:[7e‰ Š $ €n€˜€‚ÿpscp [options] source [source...] [user@]host:targetГ³‰ ÞŠ = H€'€˜€€€€€€€€€‚ÿSo to copy the local file c:\documents\csh-whynot.txt to the server example.com as user fred to the file /tmp/csh-whynot you would type:hDŠ F‹ $ €ˆ€˜€‚ÿpscp c:\documents\csh-whynot.txt fred@example.com:/tmp/csh-whynotwSÞŠ ½‹ $ €¦€˜€‚ÿYou can use wildcards to transfer multiple files in either direction, like this:W4F‹ Œ # €h€€‚ÿpscp c:\documents\*.doc fred@example.com:docfilesQ-½‹ eŒ $ €Z€˜€‚ÿpscp fred@example.com:source/*.c c:\sourcelŒ õŒ $ €Ø€˜€‚ÿHowever, in the second case (using a wildcard for multiple remote files) you may see a warning like this:gDeŒ \ # €ˆ€€‚ÿwarning: remote host tried to write to a file called 'terminal.c'U2õŒ ± # €d€€‚ÿ when we requested a file called '*.c'.jG\ Ž # €Ž€€‚ÿ If this is a wildcard, consider upgrading to SSH 2 or usingpL± ‹Ž $ €˜€˜€‚ÿ the '-unsafe' option. Renaming of this file has been disallowed.ŠMŽ !Á = H€›€˜€€€€€€€€€‚ÿThis is due to a fundamental insecurity in the old-style SCP protocol: the client sends the wildcard string (*.c) to the server, and the server sends back a sequence of file names that match the wildcard pattern. However, there is nothing to stop the server sending back a different pattern and writing over‹Ž !Á Û† one of your other files: if you request *.c, the server might send back the file name AUTOEXEC.BAT and install a virus for you. Since the wildcard matching rules are decided by the server, the client cannot reliably verify that the filenames sent back match the pattern.Þ‹Ž $ % €½€˜€‚ÿPSCP will attempt to use the newer SFTP protocol (part of SSH 2) where possible, which does not suffer from this security flaw. If you are talking to an SSH 2 server which supports SFTP, you will never see this warning.­‚!Á Ñ + $€€˜€€€‚ÿIf you really need to use a server-side wildcard with an SSH 1 server, you can use the -unsafe command line option with PSCP:Y5$ *à $ €j€˜€‚ÿpscp -unsafe fred@example.com:source/*.c c:\source¥zÑ ÏÄ + $€õ€˜€€€‚ÿThis will suppress the warning message and the file transfer will happen. However, you should be aware that by using this option you are giving the server the ability to write to any file in the target directory, so you should only use this option if you trust the server administrator not to be malicious (and not to let the server machine be cracked by malicious people).K*à Å / .€8€ãUÅùN€€€‰‚ÿSection 5.2.1.1: userKÏÄ eÅ / .€8€ãVÅùN€€€‰‚ÿSection 5.2.1.2: hostMÅ ²Å / .€<€ãWÅùN€€€‰‚ÿSection 5.2.1.3: sourceMeÅ ÿÅ / .€<€ãƒÅùN€€€‰‚ÿSection 5.2.1.4: targetvE²Å uÆ 1J¸y„¥uÆ ¸Æ ¿Ç Section 5.2.1.1: userCBB("btn_up","JI(`',`t00000066')");EB("btn_up")CÿÅ ¸Æ ) "€4€€€€‚ÿSection 5.2.1.1: userÜuÆ ¿Ç + $€¹€˜€€€‚ÿThe login name on the remote server. If this is omitted, and host is a PuTTY saved session, PSCP will use any username specified by that saved session. Otherwise, PSCP will attempt to use the local Windows username.vE¸Æ 5È 1&ƒƒQ…¦5È xÈ [É Section 5.2.1.2: hostCBB("btn_up","JI(`',`t00000066')");EB("btn_up")C¿Ç xÈ ) "€4€€€€‚ÿSection 5.2.1.2: hostã¾5È [É % €}€˜€‚ÿThe name of the remote server, or the name of an existing PuTTY saved session. In the latter case, the session's settings for hostname, port number, cipher type and username will be used.xGxÈ ÓÉ 1!y„Õ‡§ÓÉ Ê ôÌ Section 5.2.1.3: sourceCBB("btn_up","JI(`',`t00000066')");EB("btn_up")E[É Ê ) "€8€€€€‚ÿSection 5.2.1.3: sourceÂyÓÉ ÚË I `€ó€˜€€€€€€€€€€€€€‚ÿOne or more source files. Wildcards are allowed. The syntax of wildcards depends on the system to which they apply, so if you are copying from a Windows system to a UNIX system, you should use Windows wildcard syntax (e.g. *.*), but if you are copying from a UNIX system to a Windows system, you would use the wildcard syntax allowed by your UNIX shell (e.g. *).ïÊ ôÌ + $€ß€˜€€€‚ÿIf the source is a remote server and you do not specify a full pathname (in UNIX, a pathname beginning with a / (slash) character), what you specify as a source will be interpreted relative to your home directory on the remote server.xGÚË lÍ 1ôQ…¨lÍ ±Í l Section 5.2.1.4: targetCBB("btn_up","JI(`',`t00000066')");EB("btn_up")EôÌ ±Í ) "€8€€€€‚ÿSection 5.2.1.4: targetãlÍ ¿Î + $€Ç€˜€€€‚ÿThe filename or directory to put the file(s). When copying from a remote server to a local host, you may wish simply to place the file(s) in the current directory. To do this, you should specify a target of .. For example:O+±Í Ï $ €V€˜€‚ÿpscp fred@example.com:/home/tom/.emacs .|R¿Î ŠÏ * $€¤€˜€€€‚ÿ...would copy /home/tom/.emacs on the remote server to the current directory.Ö«Ï l + $€W€˜€€€‚ÿAs with the source parameter, if the target is on a remote server and isŠÏ l ôÌ not a full path name, it is interpreted relative to your home directory on the remote server.wFŠÏ ã 1 Õ‡¥©ã ' ì Section 5.2.2: OptionsCBB("btn_up","JI(`',`t00000065')");EB("btn_up")Dl ' ) "€6€€€€‚ÿSection 5.2.2: Options*ÿã Q + $€ÿ€˜€ãªÄùN‰‚ÿPSCP accepts all the general command line options supported by the PuTTY tools, except the ones which make no sense in a file transfer utility. See section 3.7.3 for a description of these options. (The ones not supported by PSCP are clearly marked.)˜t' é $ €è€˜€‚ÿPSCP also supports some of its own options. The following sections describe PSCP's specific command-line options.\8Q E $ €p€˜€‚ÿThese are the command line options that PSCP accepts.f4é « 2 4€h€ã{ÅùN€€€€‰‚ÿSection 5.2.2.1: -p preserve file attributesj8E  2 4€p€ã|ÅùN€€€€‰‚ÿSection 5.2.2.2: -q quiet, don't show statisticsl:«  2 4€t€ã}ÅùN€€€€‰‚ÿSection 5.2.2.3: -r copies directories recursivelyk9 ì 2 4€r€ã~ÅùN€€€€‰‚ÿSection 5.2.2.4: -batch avoid interactive prompts\ y 1)wªy × ¢ Section 5.2.2.1: -p preserve file attributesCBB("btn_up","JI(`',`t00000071')");EB("btn_up")^2ì × , (€d€€€€€‚ÿSection 5.2.2.1: -p preserve file attributesË y ¢ + $€A€˜€€€‚ÿBy default, files copied with PSCP are timestamped with the date and time they were copied. The -p option preserves the original timestamp on copied files.‘`× 3 1ॸ«3 •  Section 5.2.2.2: -q quiet, don't show statisticsCBB("btn_up","JI(`',`t00000071')");EB("btn_up")b6¢ • , (€l€€€€€‚ÿSection 5.2.2.2: -q quiet, don't show statisticsyU3  $ €ª€˜€‚ÿBy default, PSCP displays a meter displaying the progress of the current transfer:tP• ‚ $ € €˜€‚ÿmibs.tar | 168 kB | 84.0 kB/s | ETA: 00:00:13 | 13%‘f  + $€Í€˜€€€‚ÿThe fields in this display are (from left to right), filename, size (in kilobytes) of file transferred so far, estimate of how fast the file is being transferred (in kilobytes per second), estimated time that the transfer will be complete, and percentage of the file so far transferred. The -q option to PSCP suppresses the printing of these statistics.“b‚ ¦ 1Çw(¬¦ m Section 5.2.2.3: -r copies directories recursivelyCBB("btn_up","JI(`',`t00000071')");EB("btn_up")d8 , (€p€€€€€‚ÿSection 5.2.2.3: -r copies directories recursivelyc8¦ m + $€q€˜€€€‚ÿBy default, PSCP will only copy files. Any directories you specify to copy will be skipped, as will their contents. The -r option tells PSCP to descend into any directories you specify, and to copy them and their contents. This allows you to use PSCP to transfer whole directory structures between machines.’a ÿ 1v¸ ­ÿ b u Section 5.2.2.4: -batch avoid interactive promptsCBB("btn_up","JI(`',`t00000071')");EB("btn_up")c7m b , (€n€€€€€‚ÿSection 5.2.2.4: -batch avoid interactive prompts; ÿ  1 0€€˜€€€ãÿÅùN‰‚ÿIf you use the -batch option, PSCP will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next.Ø­b u + $€[€˜€€€‚ÿThis may help PSCP's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang.|K @ 1¢(® @ U@ ®A Section 5.2.3: Return valueCBB("btn_up","JI(`',`t00000065')");EB("btn_up")u @ u I u U@ ) "€@€€€€‚ÿSection 5.2.3: Return valueÊŸ @ A + $€?€˜€€€‚ÿPSCP returns an ERRORLEVEL of zero (success) only if the files were correctly transferred. You can test for this in a batch file, using code such as this:AU@ `A # €<€€‚ÿpscp file*.* user@hostname:N*A ®A $ €T€˜€‚ÿif errorlevel 1 echo There was an error™h`A GB 1§ Þ…¯GB ­B îH Section 5.2.4: Using public key authentication with PSCPCBB("btn_up","JI(`',`t00000065')");EB("btn_up")f=®A ­B ) "€z€€€€‚ÿSection 5.2.4: Using public key authentication with PSCP˜tGB EC $ €è€˜€‚ÿLike PuTTY, PSCP can authenticate using a public key instead of a password. There are three ways you can do this.œr­B áC * $€ä€˜€ãVÅùN‰‚ÿFirstly, PSCP can use PuTTY saved sessions in place of hostnames (see section 5.2.1.2). So you would do this:ÜEC ýD @ N€¹€T˜‘€8‚€ƒ€ã}§B‰ã„@Ï؉ã„õ‰‚ÿ•Run PuTTY, and create a PuTTY saved session (see section 4.1.2) which specifies your private key file (see section 4.18.5). You will probably also want to specify a username to log in as (see section 4.13.2).ò¸áC ïE : B€q€T˜‘€8‚€ƒ€€€€€‚ÿ•In PSCP, you can now use the name of the session instead of a hostname: type pscp sessionname:file localfile, where sessionname is replaced by the name of your saved session.Ã’ýD ²F 1 0€%€˜€€€ãúÄùN‰‚ÿSecondly, you can supply the name of a private key file on the command line, with the -i option. See section 3.7.3.14 for more information.¤zïE VG * $€ô€˜€ã80«f‰‚ÿThirdly, PSCP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this:tG²F ÊG - *€Ž€T˜‘€8‚€ƒ€‚ÿ•Ensure Pageant is running, and has your private key stored in it.¬VG vH - *€þ€T˜‘€8‚€ƒ€‚ÿ•Specify a user and host name to PSCP as normal. PSCP will automatically detect Pageant and try to use the keys within it.xNÊG îH * $€œ€˜€ãxƒùN‰‚ÿFor more general information on public-key authentication, see chapter 8.}LvH kI 1àq†°kI µI KJ Section 5.3: Secure iXplorerCBB("btn_up","JI(`',`t00000063')");EB("btn_up")J!îH µI ) "€B€€€€‚ÿSection 5.3: Secure iXplorer–rkI KJ $ €ä€˜€‚ÿLars Gunnarson has written a graphical interface for PSCP. You can get it from his web site, at www.i-tree.org.Œ[µI ×J 1Þ…±×J 6K € Chapter 6: Using PSFTP to transfer files securelyCBB("btn_up","JI(`',`Top')");EB("btn_up")_6KJ 6K ) "€l€€€€‚ÿChapter 6: Using PSFTP to transfer files securely™u×J ÏK $ €ê€˜€‚ÿPSFTP, the PuTTY SFTP client, is a tool for transferring files securely between computers using an SSH connection.U16K $L $ €b€˜€‚ÿPSFTP differs from PSCP in the following ways:êÏK O € / .€|€ãû„ùN€€€‰‚ÿSection 6.3: Using public key authentication with PSFTPoO € KJ |KoO ˆ€ 1ûq†²ˆ€ Ñ€ ƒ‰ Section 6.1: Starting PSFTPCBB("btn_up","JI(`',`t00000079')");EB("btn_up")I € Ñ€ ) "€@€€€€‚ÿSection 6.1: Starting PSFTP6ˆ€ ‚ 1 0€ €˜€€€€€‚ÿThe usual way to start PSFTP is from a command prompt, much like PSCP. To do this, it will need either to be on your PATH or in your current directory. To add the directory containing PSFTP to your PATH environment variable, type into the console window:Q-Ñ€ X‚ $ €Z€˜€‚ÿset PATH=C:\path\to\putty\directory;%PATH%œx‚ ô‚ $ €ð€˜€‚ÿUnlike PSCP, however, PSFTP has no complex command-line syntax; you just specify a host name and perhaps a user name:?X‚ 3ƒ $ €6€˜€‚ÿpsftp server.example.com1 ô‚ dƒ $ €€˜€‚ÿor perhapsD 3ƒ ¨ƒ $ €@€˜€‚ÿpsftp fred@server.example.comõÊdƒ „ + $€•€˜€€€‚ÿAlternatively, if you just type psftp on its own (or double-click the PSFTP icon in the Windows GUI), you will see the PSFTP prompt, and a message telling you PSFTP has not connected to any server:/ ¨ƒ Ì„ # €€€‚ÿC:\>psftpc@„ /… # €€€€‚ÿpsftp: no hostname specified; use "open host.name" to connect- Ì„ \… $ €€˜€‚ÿpsftp>m/… ù… 0 0€Ú€˜€€€€€‚ÿAt this point you can type open server.example.com or open fred@server.example.com to start a session.,\… %‡ + $€€˜€ãªÄùN‰‚ÿPSFTP accepts all the general command line options supported by the PuTTY tools, except the ones which make no sense in a file transfer utility. See section 3.7.3 for a description of these options. (The ones not supported by PSFTP are clearly marked.)švù… ¿‡ $ €ì€˜€‚ÿPSFTP also supports some of its own options. The following sections describe PSFTP's specific command-line options.uC%‡ 4ˆ 2 4€†€ã¥ÅùN€€€€‰‚ÿSection 6.1.1: -b: specify a file containing batch commandstB¿‡ ¨ˆ 2 4€„€ã¦ÅùN€€€€‰‚ÿSection 6.1.2: -bc: display batch commands as they are runq?4ˆ ‰ 2 4€~€ã§ÅùN€€€€‰‚ÿSection 6.1.3: -be: continue batch processing on errorsj8¨ˆ ƒ‰ 2 4€p€ã¨ÅùN€€€€‰‚ÿSection 6.1.4: -batch: avoid interactive promptsœk‰ Š 1j® ³Š ŒŠ ‰ Section 6.1.1: -b: specify a file containing batch commandsCBB("btn_up","JI(`',`t00000080')");EB("btn_up")mAƒ‰ ŒŠ , (€‚€€€€€‚ÿSection 6.1.1: -b: specify a file containing batch commands¡}Š -‹ $ €ú€˜€‚ÿIn normal operation, PSFTP is an interactive program which displays a command line and accepts commands from the keyboard.~MŒŠ «Œ 1 0€›€˜€€€€€‚ÿIf you need to do automated tasks with PSFTP, you would probably prefer to specify a set of commands in advance and have them executed automatically. The -b option allows you to do this. You use it with a file name containing batch commands. For example, you might create a file called myscript.scr containing lines like this:=-‹ èŒ # €4€€‚ÿcd /home/ftp/users/jeff8«Œ # €*€€‚ÿdel jam-old.tar.gzC èŒ c # €@€€‚ÿren jam.tar.gz jam-old.tar.gz4 — # €"€€‚ÿput jam.tar.gz:c Ñ # €.€€‚ÿchmod a+r jam.tar.gz+— ü $ €€˜€‚ÿquitR.Ñ NŽ $ €\€˜€‚ÿand then you could run the script by typingJ&ü ˜Ž $ €L€˜€‚ÿpsftp user@hostname -b myscript.scrñÀNŽ ‰ 1 0€€˜€€€ã§ÅùN‰‚ÿWhen you run a batch script in this way, PSFTP will abort the script if any command fails to complete successfully. To change this behaviour, you can use the -be option (section 6.1.3).›j˜Ž 0À 1ˆ„´0À œÀ ±Ç Section 6.1.2: -bc: display batch commands as they are runCBB("btn_up‰ 0À ‰ ","JI(`',`t00000080')");EB("btn_up")l@‰ œÀ , (€€€€€€€‚ÿSection 6.1.2: -bc: display batch commands as they are runá0À ®Á 1 0€Ã€˜€€€€€‚ÿThe -bc option alters what PSFTP displays while processing a batch script. With the -bc option, PSFTP will display prompts and commands just as if the commands had been typed at the keyboard. So instead of seeing this::œÀ èÁ # €.€€‚ÿSent username "fred"L)®Á 4 # €R€€‚ÿRemote working directory is /home/fredF#èÁ z # €F€€‚ÿListing directory /home/fred/lib_<4 Ù # €x€€‚ÿdrwxrwsr-x 4 fred fred 1024 Sep 6 10:42 .`=z 9à # €z€€‚ÿdrwxr-sr-x 25 fred fred 2048 Dec 14 09:36 ..a>Ù šÃ # €|€€‚ÿdrwxrwsr-x 3 fred fred 1024 Apr 17 2000 jeddA9à þà # €‚€€‚ÿlrwxrwxrwx 1 fred fred 24 Apr 17 2000 timberb>šÃ `Ä $ €|€˜€‚ÿdrwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn:þà šÄ $ €,€˜€‚ÿyou might see this::`Ä ÔÄ # €.€€‚ÿSent username "fred"L)šÄ Å # €R€€‚ÿRemote working directory is /home/fred4ÔÄ TÅ # €"€€‚ÿpsftp> dir libF# Å šÅ # €F€€‚ÿListing directory /home/fred/lib_<TÅ ùÅ # €x€€‚ÿdrwxrwsr-x 4 fred fred 1024 Sep 6 10:42 .`=šÅ YÆ # €z€€‚ÿdrwxr-sr-x 25 fred fred 2048 Dec 14 09:36 ..a>ùÅ ºÆ # €|€€‚ÿdrwxrwsr-x 3 fred fred 1024 Apr 17 2000 jeddAYÆ Ç # €‚€€‚ÿlrwxrwxrwx 1 fred fred 24 Apr 17 2000 timbera>ºÆ Ç # €|€€‚ÿdrwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn2Ç ±Ç $ €€˜€‚ÿpsftp> quit˜gÇ IÈ 1«® ¿…µIÈ ²È ôÉ Section 6.1.3: -be: continue batch processing on errorsCBB("btn_up","JI(`',`t00000080')");EB("btn_up")i=±Ç ²È , (€z€€€€€‚ÿSection 6.1.3: -be: continue batch processing on errors£IÈ UÉ $ €þ€˜€‚ÿWhen running a batch file, this option causes PSFTP to continue processing even if a command fails to complete successfully.Ÿ{²È ôÉ $ €ö€˜€‚ÿYou might want this to happen if you wanted to delete a file and didn't care if it was already not present, for example.‘`UÉ …Ê 1wˆ„®‡¶…Ê çÊ üÌ Section 6.1.4: -batch: avoid interactive promptsCBB("btn_up","JI(`',`t00000080')");EB("btn_up")b6ôÉ çÊ , (€l€€€€€‚ÿSection 6.1.4: -batch: avoid interactive prompts< …Ê #Ì 1 0€€˜€€€ãÿÅùN‰‚ÿIf you use the -batch option, PSFTP will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next.Ù®çÊ üÌ + $€]€˜€€€‚ÿThis may help PSFTP's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang.{J#Ì wÍ 1Ï¿…–·wÍ ¿Í e Section 6.2: Running PSFTPCBB("btn_up","JI(`',`t00000079')");EB("btn_up")HüÌ ¿Í ) "€>€€€€‚ÿSection 6.2: Running PSFTPä¹wÍ £Î + $€s€˜€€€‚ÿOnce you have started your PSFTP session, you will see a psftp> prompt. You can now type commands to perform file-transfer functions. This section lists all the available commands.m>¿Í Ï / .€|€ãªÅùN€€€‰‚ÿSection 6.2.1: General quoting rules for PSFTP commandsn9£Î ~Ï 5 :€r€ã«ÅùN€€€€€‰‚ÿSection 6.2.2: The open command: start a sessiono:Ï 5 :€t€ã¬ÅùN€€€€€‰‚ÿSection 6.2.3: The quit command: end your session~Ï üÌ t?~Ï € 5 :€~€ã­ÅùN€€€€€‰‚ÿSection 6.2.4: The help command: get quick online help“X  ; F€°€ãÙÅùN€€€€€€€‰‚ÿSection 6.2.5: The cd and pwd commands: changing the remote working directory”Y€ § ; F€²€ãÐÅùN€€€€€€€‰‚ÿSection 6.2.6: The lcd and lpwd commands: changing the local working directoryzE ! 5 :€Š€ãÑÅùN€€€€€‰‚ÿSection 6.2.7: The get command: fetch a file from the serverwB§ ˜ 5 :€„€ãÒÅùN€€€€€‰‚ÿSection 6.2.8: The put command: send a file to the serverŠO! " ; F€ž€ãÓÅùN€€€€€€€‰‚ÿSection 6.2.9: The reget and reput commands: resuming file transfersp;˜ ’ 5 :€v€ãÔÅùN€€€€€‰‚ÿSection 6.2.10: The dir command: list remote filesƒN"  5 :€œ€ãÕÅùN€€€€€‰‚ÿSection 6.2.11: The chmod command: change permissions on remote filesr=’ ‡ 5 :€z€ãÖÅùN€€€€€‰‚ÿSection 6.2.12: The del command: delete remote fileszE  5 :€Š€ã×ÅùN€€€€€‰‚ÿSection 6.2.13: The mkdir command: create remote directorieszE‡ { 5 :€Š€ãØÅùN€€€€€‰‚ÿSection 6.2.14: The rmdir command: remove remote directoriesr= í 5 :€z€ã…ùN€€€€€‰‚ÿSection 6.2.15: The ren command: rename remote filesxC{ e 5 :€†€ãú„ùN€€€€€‰‚ÿSection 6.2.16: The ! command: run a local Windows command˜gí ý 1u®‡€ ¸ý b r Section 6.2.1: General quoting rules for PSFTP commandsCBB("btn_up","JI(`',`t00000085')");EB("btn_up")e<e b ) "€x€€€€‚ÿSection 6.2.1: General quoting rules for PSFTP commands„Gý æ = H€€˜€€€€€€€€€‚ÿMost PSFTP commands are considered by the PSFTP command interpreter as a sequence of words, separated by spaces. For example, the command ren oldfilename newfilename splits up into three words: ren (the command name), oldfilename (the name of the file to be renamed), and newfilename (the new name to give the file).þÓb ä + $€§€˜€€€‚ÿSometimes you will need to specify file names that contain spaces. In order to do this, you can surround the file name with double quotes. This works equally well for local file names and remote file names:fBæ J $ €„€˜€‚ÿpsftp> get "spacey file name.txt" "save it under this name.txt"á¼ä + % €y€˜€‚ÿThe double quotes themselves will not appear as part of the file names; they are removed by PSFTP and their only effect is to stop the spaces inside them from acting as word separators.!öJ L + $€í€˜€€€‚ÿIf you need to use a double quote (on some types of remote system, such as Unix, you are allowed to use double quotes in file names), you can do this by doubling it. This works both inside and outside double quotes. For example, this commandY5+ ¥ $ €j€˜€‚ÿpsftp> ren ""this"" "a file with ""quotes"" in it"ä³L ‰ 1 0€g€˜€€€€€‚ÿwill take a file whose current name is "this" (with a double quote character at the beginning and the end) and rename it to a file whose name is a file with "quotes" in it.鸥 r 1 0€q€˜€€€ãú„ùN‰‚ÿ(The one exception to the PSFTP quoting rules is the ! command, which passes its command line straight to Windows without splitting it up into words at all. See section 6.2.16.)‘`‰  1_–ˆ¹ i nB Section 6.2.2: The open command: start a sessionCBB("btn_up","JI(`',`t00000085')");EB("btn_up")f7r i / .€n€€€€€€‚ÿSection 6.2.2: The open command: start a sessionÞ Š@ 7 <€½€˜€€€€€€€‚ÿIf you started PSFTP by double-clicking in the GUI, or just by typing psftp at the command lii Š@ r ne, you will need to open a connection to an SFTP server before you can issue any other commands (except help and quit).´ƒi >A 1 0€€˜€€€€€‚ÿTo create a connection, type open host.name, or if you need to specify a user name as well you can type open user@host.name.0Š@ nB + $€ €˜€€€‚ÿOnce you have issued this command, you will not be able to issue it again, even if the command fails (for example, if you mistype the host name or the connection times out). So if the connection is not opened successfully, PSFTP will terminate immediately.’a>A C 1Ò€ ЂºC gC ÒD Section 6.2.3: The quit command: end your sessionCBB("btn_up","JI(`',`t00000085')");EB("btn_up")g8nB gC / .€p€€€€€€‚ÿSection 6.2.3: The quit command: end your sessionåºC LD + $€u€˜€€€‚ÿWhen you have finished your session, type the command quit to terminate PSFTP and return to the command line (or just close the PSFTP console window if you started it from the GUI).†VgC ÒD 0 0€¬€˜€€€€€‚ÿYou can also use the bye and exit commands, which have exactly the same effect.—fLD iE 1¡ˆçƒ»iE ÕE G Section 6.2.4: The help command: get quick online helpCBB("btn_up","JI(`',`t00000085')");EB("btn_up")l=ÒD ÕE / .€z€€€€€€‚ÿSection 6.2.4: The help command: get quick online helpxNiE MF * $€œ€˜€€€‚ÿIf you type help, PSFTP will give a short list of the available commands.½ŒÕE G 1 0€€˜€€€€€‚ÿIf you type help with a command name - for example, help get - then PSFTP will give a short piece of help on that particular command.®}MF ¸G 1xЂÉ…¼¸G CH 0J Section 6.2.5: The cd and pwd commands: changing the remote working directoryCBB("btn_up","JI(`',`t00000085')");EB("btn_up")‹V G CH 5 :€¬€€€€€€€€‚ÿSection 6.2.5: The cd and pwd commands: changing the remote working directory> ¸G I 1 0€€˜€€€€€‚ÿPSFTP maintains a notion of your ‘working directory’ on the server. This is the default directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will look for filename.dat in your remote working directory on the server.¯CH 0J 0 0€þ€˜€€€€€‚ÿTo change your remote working directory, use the cd command. To display your current remote working directory, type pwd.¯~I ßJ 1Úçƒ ˆ½ßJ kK ¹M Section 6.2.6: The lcd and lpwd commands: changing the local working directoryCBB("btn_up","JI(`',`t00000085')");EB("btn_up")ŒW0J kK 5 :€®€€€€€€€€‚ÿSection 6.2.6: The lcd and lpwd commands: changing the local working directoryŸnßJ M 1 0€Ý€˜€€€€€‚ÿAs well as having a working directory on the remote server, PSFTP also has a working directory on your local machine (just like any other Windows process). This is the default local directory that other commands will operate on. For example, if you type get filename.dat then PSFTP will save the resulting file as filename.dat in your local working directory.¯kK ¹M 0 0€þ€˜€€€€€‚ÿTo change your local working directory, use the lcd command. To display your current local working directory, type lpwd.l M VN 1É…¾VN ÈN — Section 6.2.7: The get command: fetch a file from the serverCBB("btn_up","JI(`',`t00000085')");EB("btn_up")rC¹M ÈN / .€†€€€€€€‚ÿSection 6.2.7: The get command: fetch a file from the server‰_VN QO * $€¾€˜€€€‚ÿTo download a file from the server and store it on your local PC, you use the get command.`<ÈN ±O $ €x€˜€‚ÿIn its simplest form, you just use this with a file name:5QO € $ €"€˜€‚ÿget myfile.dat±O € ¹M –r±O ¢€ $ €ä€˜€‚ÿIf you want to store the file locally under a different name, specify the local file name after the remote one:A € 〠$ €:€˜€‚ÿget myfile.dat newname.dat´ƒ¢€ — 1 0€€˜€€€€€‚ÿThis will fetch the file on the server called myfile.dat, but will save it to your local machine under the name newname.dat.ši〠1‚ 1ù ˆò¿1‚  ‚ *… Section 6.2.8: The put command: send a file to the serverCBB("btn_up","JI(`',`t00000085')");EB("btn_up")o@—  ‚ / .€€€€€€€€‚ÿSection 6.2.8: The put command: send a file to the serverzP1‚ ƒ * $€ €˜€€€‚ÿTo upload a file to the server from your local PC, you use the put command.`< ‚ zƒ $ €x€˜€‚ÿIn its simplest form, you just use this with a file name:5ƒ ¯ƒ $ €"€˜€‚ÿput myfile.dat—szƒ F„ $ €æ€˜€‚ÿIf you want to store the file remotely under a different name, specify the remote file name after the local one:A¯ƒ ‡„ $ €:€˜€‚ÿput myfile.dat newname.dat£sF„ *… 0 0€æ€˜€€€€€‚ÿThis will send the local file called myfile.dat, but will store it on the server under the name newname.dat.¥t‡„ Ï… 130ÀÏ… Q† ‰ Section 6.2.9: The reget and reput commands: resuming file transfersCBB("btn_up","JI(`',`t00000085')");EB("btn_up")‚M*… Q† 5 :€š€€€€€€€€‚ÿSection 6.2.9: The reget and reput commands: resuming file transfers¢eÏ… ó‡ = H€Ë€˜€€€€€€€€€‚ÿIf a file transfer fails half way through, and you end up with half the file stored on your disk, you can resume the file transfer using the reget and reput commands. These work exactly like the get and put commands, but they check for the presence of the half-written destination file and start transferring from where the last attempt left off.–ZQ† ‰ˆ < H€´€˜€€€€€€€€€‚ÿThe syntax of reget and reput is exactly the same as the syntax of get and put:6ó‡ ¿ˆ # €&€€‚ÿreget myfile.datC‰ˆ ‰ $ €>€˜€‚ÿreget myfile.dat newname.dat“b¿ˆ •‰ 1;òqÁ•‰ ý‰ Ћ Section 6.2.10: The dir command: list remote filesCBB("btn_up","JI(`',`t00000085')");EB("btn_up")h9‰ ý‰ / .€r€€€€€€‚ÿSection 6.2.10: The dir command: list remote filesqG•‰ nŠ * $€Ž€˜€€€‚ÿTo list the files in your remote working directory, just type dir.”jý‰ ‹ * $€Ô€˜€€€‚ÿYou can also list the contents of a different directory by typing dir followed by the directory name:4nŠ 6‹ # €"€€‚ÿdir /home/fred2‹ h‹ $ €€˜€‚ÿdir sourcesh86‹ Ћ 0 0€p€˜€€€€€‚ÿThe ls command works exactly the same way as dir.¦uh‹ vŒ 1A 0 ‡ÂvŒ ñŒ ÃÉ Section 6.2.11: The chmod command: change permissions on remote filesCBB("btn_up","JI(`',`t00000085')");EB("btn_up"){LЋ ñŒ / .€˜€€€€€€‚ÿSection 6.2.11: The chmod command: change permissions on remote filesצvŒ È 1 0€M€˜€€€€€‚ÿPSFTP allows you to modify the file permissions on files on the server. You do this using the chmod command, which works very much like the Unix chmod command.ÕžñŒ Ž 7 <€=€˜€€€€€€€‚ÿThe basic syntax is chmod modes file, where modes represents a modification to the file permissions, and file is the filename to modify. For example:BÈ ßŽ # €>€€‚ÿchmod go-rwx,u+w privatefile:Ž  # €.€€‚ÿchmod a+r publicfile:ߎ S $ €,€˜€‚ÿchmod 640 groupfile1 À + $€ €˜€€€‚ÿThe modes parameter can be a set of octal digits in the Unix style. (If you don't know what this means, you probably don't wantS À Ћ to be using it!) Alternatively, it can be a list of permission modifications, separated by commas. Each modification consists of:4îS ÄÁ F Z€Ý€T˜‘€8‚€ƒ€€€€€€€€€‚ÿ•The people affected by the modification. This can be u (the owning user), g (members of the owning group), or o (everybody else - ‘others’), or some combination of those. It can also be a (‘all’) to affect everybody at once.ŒSÀ P 9 B€¦€T˜‘€8‚€ƒ€€€€€‚ÿ•A + or - sign, indicating whether permissions are to be added or removed.EÄÁ •Ã @ N€ €T˜‘€8‚€ƒ€€€€€€€‚ÿ•The actual permissions being added or removed. These can be r (permission to read the file), w (permission to write to the file), and x (permission to execute the file, or in the case of a directory, permission to access files within the directory).F"P Ûà $ €D€˜€‚ÿSo the above examples would do:*ð•Ã Å : B€á€T˜‘€8‚€ƒ€€€€€‚ÿ•The first example: go-rwx removes read, write and execute permissions for members of the owning group and everybody else (so the only permissions left are the ones for the file owner). u+w adds write permission for the file owner.vCÛà {Å 3 6€†€T˜‘€8‚€ƒ€€€‚ÿ•The second example: a+r adds read permission for everybody.«†Å &Æ % € €˜€‚ÿIn addition to all this, there are a few extra special cases for Unix systems. On non-Unix systems these are unlikely to be useful:üÂ{Å "Ç : B€…€T˜‘€8‚€ƒ€€€€€‚ÿ•You can specify u+s and u-s to add or remove the Unix set-user-ID bit. This is typically only useful for special purposes; refer to your Unix documentation if you're not sure about it.e+&Æ ‡È : B€W€T˜‘€8‚€ƒ€€€€€‚ÿ•You can specify g+s and g-s to add or remove the Unix set-group-ID bit. On a file, this works similarly to the set-user-ID bit (see your Unix documentation again); on a directory it ensures that files created in the directory are accessible by members of the group that owns the directory.<ü"Ç ÃÉ @ N€ù€T˜‘€8‚€ƒ€€€€€€€‚ÿ•You can specify +t and -t to add or remove the Unix ‘sticky bit’. When applied to a directory, this means that the owner of a file in that directory can delete the file (whereas normally only the owner of the directory would be allowed to).•d‡È XÊ 1vqÓ‡ÃXÊ ÂÊ ÎË Section 6.2.12: The del command: delete remote filesCBB("btn_up","JI(`',`t00000085')");EB("btn_up")j;ÃÉ ÂÊ / .€v€€€€€€‚ÿSection 6.2.12: The del command: delete remote filesnDXÊ 0Ë * $€ˆ€˜€€€‚ÿTo delete a file on the server, type del and then the filename:6ÂÊ fË $ €$€˜€‚ÿdel oldfile.dath80Ë ÎË 0 0€p€˜€€€€€‚ÿThe rm command works exactly the same way as del.lfË kÌ 1" ‡xˆÄkÌ ÝÌ Í Section 6.2.13: The mkdir command: create remote directoriesCBB("btn_up","JI(`',`t00000085')");EB("btn_up")rCÎË ÝÌ / .€†€€€€€€‚ÿSection 6.2.13: The mkdir command: create remote directories{QkÌ XÍ * $€¢€˜€€€‚ÿTo create a directory on the server, type mkdir and then the directory name:5ÝÌ Í $ €"€˜€‚ÿmkdir newstufflXÍ *Î 1ÚÓ‡Å*Î œÎ Section 6.2.14: The rmdir command: remove remote directoriesCBB("btn_up","JI(`',`t00000085')");EB("btn_up")rCÍ œÎ / .€†€€€€€€‚ÿSection 6.2.14: The rmdir command: remove remote directories{Q*Î Ï * $€¢€˜€€€‚ÿTo remove a directory on the server, type rmdir and then the directory name:5œÎ LÏ $ €"€˜€‚ÿrmdir oldstuff¸“Ï % €'€˜€‚ÿMost SFTP servers will probably refuse to remove a directory if the directory has anything in it, so you will need to delete the contents firsLÏ Í t.•dLÏ ¥1¯xˆüÆ¥TSection 6.2.15: The ren command: rename remote filesCBB("btn_up","JI(`',`t00000085')");EB("btn_up")j;/ .€v€€€€€€‚ÿSection 6.2.15: The ren command: rename remote filesf¥Ÿ* $€Ì€˜€€€‚ÿTo rename a file on the server, type ren, then the current file name, and then the new file name::Ù$ €,€˜€‚ÿren oldfile newname{EŸT6 <€Š€˜€€€€€€€‚ÿThe rename and mv commands work exactly the same way as ren.›jÙï1ttÇï_cSection 6.2.16: The ! command: run a local Windows commandCBB("btn_up","JI(`',`t00000085')");EB("btn_up")pAT_/ .€‚€€€€€€‚ÿSection 6.2.16: The ! command: run a local Windows commandj3ïÉ7 <€g€˜€€€ãªÅùN‰€€‚ÿYou can run local Windows commands using the ! command. This is the only PSFTP command that is not subject to the command quoting rules given in section 6.2.1. If any command line begins with the ! character, then the rest of the line will be passed straight to Windows without further translation.©„_r% € €˜€‚ÿFor example, if you want to move an existing copy of a file out of the way before downloading an updated version, you might type:G$ɹ# €H€€‚ÿpsftp> !ren myfile.dat myfile.bak<rõ$ €0€˜€‚ÿpsftp> get myfile.datnD¹c* $€ˆ€˜€€€‚ÿusing the Windows ren command to rename files on your local PC.˜gõû1½ü—Èû`¸ Section 6.3: Using public key authentication with PSFTPCBB("btn_up","JI(`',`t00000079')");EB("btn_up")e<c`) "€x€€€€‚ÿSection 6.3: Using public key authentication with PSFTP—sû÷$ €æ€˜€‚ÿLike PuTTY, PSFTP can authenticate using a public key instead of a password. There are two ways you can do this.[`v$ €¶€˜€‚ÿFirstly, PSFTP can use PuTTY saved sessions in place of hostnames. So you might do this:Ü÷’ @ N€¹€T˜‘€8‚€ƒ€ã}§B‰ã„@Ï؉ã„õ‰‚ÿ•Run PuTTY, and create a PuTTY saved session (see section 4.1.2) which specifies your private key file (see section 4.18.5). You will probably also want to specify a username to log in as (see section 4.13.2).å«vw : B€W€T˜‘€8‚€ƒ€€€€€‚ÿ•In PSFTP, you can now use the name of the session instead of a hostname: type psftp sessionname, where sessionname is replaced by the name of your saved session.¦|’  * $€ø€˜€ã80«f‰‚ÿSecondly, PSFTP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this:tGw ‘ - *€Ž€T˜‘€8‚€ƒ€‚ÿ•Ensure Pageant is running, and has your private key stored in it.¯ @ . *€€T˜‘€8‚€ƒ€‚ÿ•Specify a user and host name to PSFTP as normal. PSFTP will automatically detect Pageant and try to use the keys within it.xN‘ ¸ * $€œ€˜€ãxƒùN‰‚ÿFor more general information on public-key authentication, see chapter 8.’a@ J 1‡tS€ÉJ ¯ Ý@Chapter 7: Using the command-line connection tool PlinkCBB("btn_up","JI(`',`Top')");EB("btn_up")e<¸ ¯ ) "€x€€€€‚ÿChapter 7: Using the command-line connection tool PlinkàµJ + $€k€˜€€€‚ÿPlink (PuTTY Link) is a command-line connection tool similar to UNIX ssh. It is mostly used for automated operations, such as making CVS access a repository on a remote server.‰e¯ $ €Ê€˜€‚ÿPlink is probably not what you want if you want to run an interactive session in a console window.Q"i/ .€D€ãý„ùN€€€‰‚ÿSection 7.1: Starting PlinkN·/ .€>€ãþ„ùN€€€‰‚ÿSection 7.2: Using Plinki:i,@/ .€t€ã…ùN€€€‰‚ÿSection 7.3: Using Pli·,@¸ nk in batch files and scriptsW(·ƒ@/ .€P€ã€ƒùN€€€‰‚ÿSection 7.4: Using Plink with CVSZ+,@Ý@/ .€V€ãwƒùN€€€‰‚ÿSection 7.5: Using Plink with WinCVS|Kƒ@YA1Š—ýƒÊYA¢AãESection 7.1: Starting PlinkCBB("btn_up","JI(`',`t00000103')");EB("btn_up")I Ý@¢A) "€@€€€€‚ÿSection 7.1: Starting Plink\YA#C% €¹€˜€‚ÿPlink is a command line application. This means that you cannot just double-click on its icon to run it and instead you have to bring up a console window. In Windows 95, 98, and ME, this is called an ‘MS-DOS Prompt’, and in Windows NT and 2000 it is called a ‘Command Prompt’. It should be available from the Programs section of your Start Menu.Û¢A5D7 <€·€˜€€€€€€€‚ÿIn order to use Plink, the file plink.exe will need either to be on your PATH or in your current directory. To add the directory containing Plink to your PATH environment variable, type into the console window:Q-#C†D$ €Z€˜€‚ÿset PATH=C:\path\to\putty\directory;%PATH%]&5DãE7 <€M€˜€€€€€€€‚ÿThis will only work for the lifetime of that particular console window. To set your PATH more permanently on Windows NT, use the Environment tab of the System Control Panel. On Windows 95, 98, and ME, you will need to edit your AUTOEXEC.BAT to include a set command like the one above.yH†D\F1Ñ S€£Ë\F¢F<Section 7.2: Using PlinkCBB("btn_up","JI(`',`t00000103')");EB("btn_up")FãE¢F) "€:€€€€‚ÿSection 7.2: Using Plinkl\F2G$ €Ø€˜€‚ÿThis section describes the basics of how to use Plink for interactive logins and for automated processes.Ø¢F5H+ $€±€˜€€€‚ÿOnce you've got a console window to type into, you can just type plink on its own to bring up a usage message. This tells you the version of Plink you're using, and gives you a brief summary of how to use Plink:52GjH# €$€€‚ÿZ:\sysosd>plinkQ.5H»H# €\€€‚ÿPuTTY Link: command-line connection utility2jHíH# €€€‚ÿRelease 0.53R/»H?I# €^€€‚ÿUsage: plink [options] [user@]host [command]\9íH›I# €r€€‚ÿ ("host" can also be a PuTTY saved session name). ?IÉI# €€€‚ÿOptions:G$›IJ# €H€€‚ÿ -v show verbose messagesX5ÉIhJ# €j€€‚ÿ -load sessname Load settings from saved sessionAJ©J# €<€€‚ÿ -ssh -telnet -rlogin -rawb?hJ K# €~€€‚ÿ force use of a particular protocol (default SSH)K(©JVK# €P€€‚ÿ -P port connect to specified portQ. K§K# €\€€‚ÿ -l user connect with specified usernameR/VKùK# €^€€‚ÿ -m file read remote command(s) from fileQ.§KJL# €\€€‚ÿ -batch disable all interactive promptsZ7ùK¤L# €n€€‚ÿThe following options only apply to SSH connections:O,JLóL# €X€€‚ÿ -pw passw login with specified passwordgD¤LZM# €ˆ€€‚ÿ -L listen-port:host:port Forward local port to remote addressgDóLÁM# €ˆ€€‚ÿ -R listen-port:host:port Forward remote port to local addressQ.ZMN# €\€€‚ÿ -X -x enable / disable X11 forwardingS0ÁMeN# €`€€‚ÿ -A -a enable / disable agent forwardingQ.N¶N# €\€€‚ÿ -t -T enable / disable pty allocationZ7eNO# €n€€‚ÿ -1 -2 force use of particular protocol versionD!¶NTO# €B€€‚ÿ -C enable compressionV2OªO$ €d€˜€‚ÿ -i key private key file for authenticationS/TO €$ €^€˜€‚ÿOnce this works, you are ready to use Plink.ªO €ãEg8ªOs€/ .€p€ãÿ„ùN€€€‰‚ÿSection 7.2.1: Using Plink for interactive loginsj; €Ý€/ .€v€ã…ùN€€€‰‚ÿSection 7.2.2: Using Plink for automated connections_0s€</ .€`€ã…ùN€€€‰‚ÿSection 7.2.3: Plink command line options’aÝ€Î1ýƒÒÌÎ-‚[‰Section 7.2.1: Using Plink for interactive loginsCBB("btn_up","JI(`',`t00000105')");EB("btn_up")_6<-‚) "€l€€€€‚ÿSection 7.2.1: Using Plink for interactive logins’hο‚* $€Ð€˜€€€‚ÿTo make a simple interactive connection to a remote server, just type plink and then the host name:G$-‚ƒ# €H€€‚ÿZ:\sysosd>plink login.example.com&¿‚,ƒ# €€€‚ÿM*ƒyƒ# €T€€‚ÿDebian GNU/Linux 2.2 flunky.example.com4,ƒ­ƒ$ € €˜€‚ÿflunky login:Ü·yƒ‰…% €o€˜€‚ÿYou should then be able to log in as normal and run a session. The output sent by the server will be written straight to your command prompt window, which will most likely not interpret terminal control codes in the way the server expects it to. So if you run any full-screen applications, for example, you can expect to see strange characters appearing in your window. Interactive connections like this are not the main point of Plink.䧭ƒm†= H€O€˜€€€€€€€€€‚ÿIn order to connect with a different protocol, you can give the command line options -ssh, -telnet, -rlogin or -raw. To make an SSH connection, for example:L)‰…¹†# €R€€‚ÿZ:\sysosd>plink -ssh login.example.com0 m†é†$ €€˜€‚ÿlogin as:ô¹†ˆ% €é€˜€‚ÿIf you have already set up a PuTTY saved session, then instead of supplying a host name, you can give the saved session name. This allows you to use public-key authentication, specify a user name, and use most of the other features of PuTTY:D!é†Fˆ# €B€€‚ÿZ:\sysosd>plink my-ssh-session:ˆ€ˆ# €.€€‚ÿSent username "fred"R/FˆÒˆ# €^€€‚ÿAuthenticating with public key "fred@winbox"T1€ˆ&‰# €b€€‚ÿLast login: Thu Dec 6 19:25:33 2001 from :0.05Òˆ[‰$ €"€˜€‚ÿfred@flunky:~$•d&‰ð‰1ø £FƒÍð‰RŠôÅSection 7.2.2: Using Plink for automated connectionsCBB("btn_up","JI(`',`t00000105')");EB("btn_up")b9[‰RŠ) "€r€€€€‚ÿSection 7.2.2: Using Plink for automated connectionsÛð‰X‹+ $€·€˜€€€‚ÿMore typically Plink is used with the SSH protocol, to enable you to talk directly to a program running on the server. To do this you have to ensure Plink is using the SSH protocol. You can do this in several ways:u<RŠÍ‹9 B€x€T˜‘€8‚€ƒ€€€ãÿ„ùN‰‚ÿ•Use the -ssh option as described in section 7.2.1.®€X‹{Œ. *€€T˜‘€8‚€ƒ€‚ÿ•Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies the protocol as SSH.‡NÍ‹9 B€œ€T˜‘€8‚€ƒ€€€€€‚ÿ•Set the Windows environment variable PLINK_PROTOCOL to the word ssh.Ù´{ŒÛ% €i€˜€‚ÿUsually Plink is not invoked directly by a user, but run automatically by another process. Therefore you typically do not want Plink to prompt you for a user name or a password.X43Ž$ €h€˜€‚ÿTo avoid being prompted for a user name, you can:®uÛáŽ9 B€ê€T˜‘€8‚€ƒ€€€€€‚ÿ•Use the -l option to specify a user name on the command line. For example, plink login.example.com -l fred.Ñ3Ž²4 6€;€T˜‘€8‚€ƒ€ã„õ‰‚ÿ•Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies the username to log in as (see section 4.13.2).×áŽÀÀ+ $€¯€˜€ãxƒùN‰‚ÿTo avoid being prompted for a pass²ÀÀ[‰word, you should almost certainly set up public-key authentication. (See chapter 8 for a general introduction to public-key authentication.) Again, you can do this in two ways: ì²àÁ4 6€Ù€T˜‘€8‚€ƒ€ã„@Ï؉‚ÿ•Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies a private key file (see section 4.18.5). For this to work without prompting, your private key will need to have no passphrase.ƒPÀÀcÂ3 6€ €T˜‘€8‚€ƒ€ã80«f‰‚ÿ•Store the private key in Pageant. See chapter 9 for further information.¾™àÁ!Ã% €3€˜€‚ÿOnce you have done all this, you should be able to run a remote command on the SSH server machine and have it execute automatically with no prompting:a>c‚Ã# €|€€‚ÿZ:\sysosd>plink login.example.com -l fred echo hello, world2!ôÃ# €€€‚ÿhello, world&‚ÃÚÃ# €€€‚ÿ1 ´Ã Ä$ €€˜€‚ÿZ:\sysosd>nJÚÃyÄ$ €”€˜€‚ÿOr, if you have set up a saved session with all the connection details:Q. ÄÊÄ# €\€€‚ÿZ:\sysosd>plink mysession echo hello, world2yÄüÄ# €€€‚ÿhello, world&ÊÄ"Å# €€€‚ÿ1 üÄSÅ$ €€˜€‚ÿZ:\sysosd>¡}"ÅôÅ$ €ú€˜€‚ÿThen you can set up other programs to run this Plink command and talk to it as if it were a process on the server machine.ŠYSÅ~Æ1rÒ†Î~ÆÕÆðÉSection 7.2.3: Plink command line optionsCBB("btn_up","JI(`',`t00000105')");EB("btn_up")W.ôÅÕÆ) "€\€€€€‚ÿSection 7.2.3: Plink command line options¶‹~Æ‹Ç+ $€€˜€ãªÄùN‰‚ÿPlink accepts all the general command line options supported by the PuTTY tools. See section 3.7.3 for a description of these options.ŒUÕÆÉ7 <€«€˜€€€€€ãÿÅùN‰‚ÿIn addition to this, Plink accepts one other option: the -batch option. If you use the -batch option, Plink will never give an interactive prompt while establishing the connection. If the server's host key is invalid, for example (see section 2.2), then the connection will simply be abandoned instead of asking you what to do next.Ù®‹ÇðÉ+ $€]€˜€€€‚ÿThis may help Plink's behaviour when it is used in automated scripts: using -batch, if something goes wrong at connection time, the batch job will fail rather than hang.”cÉ„Ê1{Fƒ˜ˆÏ„ÊåÊÿÍSection 7.3: Using Plink in batch files and scriptsCBB("btn_up","JI(`',`t00000103')");EB("btn_up")a8ðÉåÊ) "€p€€€€‚ÿSection 7.3: Using Plink in batch files and scripts4 „ÊÌ+ $€€˜€ã…ùN‰‚ÿOnce you have set up Plink to be able to log in to a remote server without any interactive prompting (see section 7.2.2), you can use it for lots of scripting and batch purposes. For example, to start a backup on a remote machine, you might use a command like:T0åÊmÌ$ €`€˜€‚ÿplink root@myserver /etc/backups/do-backup.sh{WÌèÌ$ €®€˜€‚ÿOr perhaps you want to fetch all system log lines relating to a particular web area:lHmÌTÍ$ €€˜€‚ÿplink mysession grep /~fjbloggs/ /var/log/httpd/access.log > fredlogs«†èÌÿÍ% € €˜€‚ÿAny non-interactive command you could usefully run on the server command line, you can run in a batch file using Plink in this way.‚QTÍÎ1††)ÐÎÐÎSection 7.4: Using Plink with CVSCBB("btn_up","JI(`',`t00000103')");EB("btn_up")O&ÿÍÐÎ) "€L€€€€‚ÿSection 7.4: Using Plink with CVS‰_ÎYÏ* $€¾€˜€€€‚ÿTo use Plink with CVS, you need to set the environment variable CVS_RSH to point to Plink:E!ÐΞÏ$ €B€˜€‚ÿset CVS_RSH=\path\to\plink.exe¯„YÏY+ $€ €˜€ã…ùN‰‚ÿYou also need to arrange to be able to connect to a režÏYÿÍmote host without any interactive prompts, as described in section 7.2.2.U1žÏ®$ €b€˜€‚ÿYou should then be able to run CVS as follows:a=Y$ €z€˜€‚ÿcvs -d :ext:user@sessionname:/path/to/repository co module¨ƒ®·% €€˜€‚ÿIf you specified a username in your saved session, you don't even need to specify the ‘user’ part of this, and you can just say:\8$ €p€˜€‚ÿcvs -d :ext:sessionname:/path/to/repository co module…T·˜1*˜ˆ јêÂSection 7.5: Using Plink with WinCVSCBB("btn_up","JI(`',`t00000103')");EB("btn_up")R)ê) "€R€€€€‚ÿSection 7.5: Using Plink with WinCVSÇœ˜±+ $€9€˜€ã…ùN‰‚ÿPlink can also be used with WinCVS. Firstly, arrange for Plink to be able to connect to a remote host non-interactively, as described in section 7.2.2.d-ê7 <€[€˜€€€€€€€‚ÿThen, in WinCVS, bring up the ‘Preferences’ dialogue box from the Admin menu, and switch to the ‘Ports’ tab. Tick the box there labelled ‘Check for an alternate rsh name’ and in the text entry field to the right enter the full path to plink.exe. Select ‘OK’ on the ‘Preferences’ dialogue box.Ÿu±´* $€ê€˜€ã€ƒùN‰‚ÿNext, select ‘Command Line’ from the WinCVS ‘Admin’ menu, and type a CVS command as in section 7.4, for example:^:$ €t€˜€‚ÿcvs -d :ext:user@hostname:/path/to/repository co moduleL(´^$ €P€˜€‚ÿor (if you're using a saved session):a=¿$ €z€˜€‚ÿcvs -d :ext:user@sessionname:/path/to/repository co moduleÞ^Â% €½€˜€‚ÿSelect the folder you want to check out to with the ‘Change Folder’ button, and click ‘OK’ to check out your module. Once you've got modules checked out, WinCVS will happily invoke plink from the GUI for CVS operations.Ž]¿P1§)þÒPÿÿÿÿ÷ Chapter 8: Using public keys for SSH authenticationCBB("btn_up","JI(`',`Top')");EB("btn_up")a8±) "€p€€€€‚ÿChapter 8: Using public keys for SSH authenticationn?P / .€~€ãyƒùN€€€‰‚ÿSection 8.1: Public key authentication - an introductionj;±‰ / .€v€ãL%¥Í€€€‰‚ÿSection 8.2: Using PuTTYgen, the PuTTY key generatorn? ÷ / .€~€ã{ƒùN€€€‰‚ÿSection 8.3: Getting ready for public key authentication™h‰  1Å k†Ó ö aHSection 8.1: Public key authentication - an introductionCBB("btn_up","JI(`',`t00000112')");EB("btn_up")f=÷ ö ) "€z€€€€‚ÿSection 8.1: Public key authentication - an introductionåÀ Û % €€˜€‚ÿPublic key authentication is an alternative means of identifying yourself to a login server, instead of typing a password. It is more secure and more flexible, but more difficult to set up.‰Xö d 1 0€±€˜€€€ãÿÅùN‰‚ÿIn conventional password authentication, you prove you are who you claim to be by proving that you know the correct password. The only way to prove you know the password is to tell the server what you think the password is. This means that if the server has been hacked, or spoofed (see section 2.2), an attacker can learn your password.ï¾Û S1 0€}€˜€€€€€‚ÿPublic key authentication solves this problem. You generate a key pair, consisting of a public key (which everybody is allowed to know) and a private key (which you keep secret and do not give to anybody). The private key is able to generate signatures. A signature created using your private key cannot be forged by anybody who does not have that key; but anybody who has your public key can verify that a particular signature is genuine. åd iA% €Ë€˜€‚ÿSo you generate a key pair on your own computer, and you copy the public key to the server. Then, when the server asks you to prove whoSiA÷  you are, PuTTY can generate a signature using your private key. The server can verify that signature (since it has your public key) and allow you to log in. Now if the server is hacked or spoofed, the attacker does not gain your private key or password; they only gain one signature. And signatures cannot be re-used, so they have gained nothing.ëS…C1 0€×€˜€€€€€‚ÿThere is a problem with this: if your private key is stored unprotected on your own computer, then anybody who gains access to that will be able to generate signatures as if they were you. So they will be able to log in to your server under your account. For this reason, your private key is usually encrypted when it is stored on your local machine, using a passphrase of your choice. In order to generate a signature, PuTTY must decrypt the key, so you have to type your passphrase.·†iAK[L/ .€|€ã&lφ€€€‰‚ÿSection 8.2.3: Selecting the size (strength) of the keyZ+îKµL/ .€V€ã1E½Š€€€‰‚ÿSection 8.2.4: The ‘Generate’ button^/[LM/ .€^€ã„QÜc€€€‰‚ÿSection 8.2.5: The ‘Key fingerprint’ boxc4µLvM/ .€h€ã/§øA€€€‰‚ÿSection 8.2.6: Setting a comment for your keyf7MÜM/ .€n€ãB'ó6€€€‰‚ÿSection 8.2.7: Setting a passphrase for your keyk<vMGN/ .€x€ã䀅a€€€‰‚ÿSection 8.2.8: Saving your private key to a disk filej;ÜM±N/ .€v€ã´åU€€€‰‚ÿSection 8.2.9: Saving your public key to a disk filexIGN)O/ .€’€ã eHm€€€‰‚ÿSection 8.2.10: ‘Public key for pasting into authorized_keys file’].±N†O/ .€\€ãúµÛ†€€€‰‚ÿSection 8.2.11: Reloading a private keypA)O €/ .€‚€ãE@Áv€€€‰‚ÿSection 8.2.12: Dealing with private keys in other formats†O €aH‹Z†O—€1±k†(Õ—€è€H‡Section 8.2.1: Generating a new keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")Q( €è€) "€P€€€€‚ÿSection 8.2.1: Generating a new key­ˆ—€•% €€˜€‚ÿThis is a general outline of the procedure for generating a new key pair. The following sections describe the process in more detail.ó¹è€ˆ‚: B€s€T˜‘€8‚€ƒ€ã5ij‰ã&lφ‰‚ÿ•First, you need to select which type of key you want to generate, and also select the strength of the key. This is described in more detail in section 8.2.2 and section 8.2.3.j•%ƒ3 6€Ô€T˜‘€8‚€ƒ€ã1E½Š‰‚ÿ•Then press the ‘Generate’ button, to actually generate the key. Section 8.2.4 describes this step.¬sˆ‚у9 B€æ€T˜‘€8‚€ƒ€ã/§øA‰ãB'ó6‰‚ÿ•Once you have generated the key, select a comment field (section 8.2.6) and a passphrase (section 8.2.7).¦s%ƒw„3 6€æ€T˜‘€8‚€ƒ€ã䀅a‰‚ÿ•Now you're ready to save the private key to disk; press the ‘Save private key’ button. (See section 8.2.8).Øу††7 <€±€˜€ã eHm‰ã´åU‰ãúµÛ†‰‚ÿYour key pair is now ready for use. You may also want to copy the public key to your server, either by copying it out of the ‘Public key for pasting into authorized_keys file’ box (see section 8.2.10), or by using the ‘Save public key’ button (section 8.2.9). However, you don't need to do this immediately; if you want, you can load the private key back into PuTTYgen later (see section 8.2.11) and the public key will be available for copying and pasting again.—w„H‡+ $€/€˜ã{ƒùN€‰‚ÿsection 8.3 describes the typical process of configuring PuTTY to attempt public-key authentication, and configuring your SSH server to accept it._††؇1£W Ö؇.ˆ{ŽSection 8.2.2: Selecting the type of keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")V-H‡.ˆ) "€Z€€€€‚ÿSection 8.2.2: Selecting the type of keyµØ‡ãˆ% €!€˜€‚ÿBefore generating a public key using PuTTYgen, you need to select which type of key you need. PuTTYgen currently supports three types of key:^1.ˆA‰- *€b€T˜‘€8‚€ƒ€‚ÿ•An RSA key for use with the SSH 1 protocol.^1㈟‰- *€b€T˜‘€8‚€ƒ€‚ÿ•An RSA key for use with the SSH 2 protocol.]0A‰ü‰- *€`€T˜‘€8‚€ƒ€‚ÿ•A DSA key for use with the SSH 2 protocol.ѬŸ‰ÍŠ% €Y€˜€‚ÿThe SSH 1 protocol only supports RSA keys; if you will be connecting using the SSH 1 protocol, you must select the first key type or your key will be completely useless.Œhü‰Y‹$ €Ð€˜€‚ÿThe SSH 2 protocol supports more than one key type. The two types supported by PuTTY are RSA and DSA.êÍŠt1 0€Õ€˜€€€€€‚ÿThe PuTTY developers strongly recommend you use RSA. DSA has an intrinsic weakness which makes it very easy to create a signature which contains enough information to give away the private key! This would allow an attacker to pretend to be you for any number of future sessions. PuTTY's implementation has taken very careful precautions to avoid this weakness, but we cannot be 100% certain we have managed it, and if you have the choice we strongly recommend using RSA keys instead.âY‹{Ž% €Å€˜€‚ÿIf you really need to connect to an SSH server which only supports DSA, then you probably have no choice but to use DSA. If you do use DSA, we recommend you do not use the same key to authenticate with more than one server.Ÿnt1Q(>€×wÀSection 8.2.3: Selecting the size (strength) of the keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")e<{Ž) "€x€€€€‚ÿSection 8.2.3: Selecting the size (strength) of the keyŠfÀ$ €Ì€˜€‚ÿThe ‘Number of bits’ input box allows you to choose the strength of the key PuTTYgen will geÀ{Žnerate.b>wÀ$ €|€˜€‚ÿCurrently 1024 bits should be sufficient for most purposes.Œ[ÀÁ1‘W  …ØÁUÁ”ÆSection 8.2.4: The ‘Generate’ buttonCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")R)wÀUÁ) "€R€€€€‚ÿSection 8.2.4: The ‘Generate’ buttonÓ®Á(Â% €]€˜€‚ÿOnce you have chosen the type of key you want, and the strength of the key, press the ‘Generate’ button and PuTTYgen will begin the process of actually generating the key.'üUÁOÄ+ $€ù€˜€€€‚ÿFirst, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don't need to wave the mouse in particularly imaginative patterns (although it can't hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position.¸“(ÂÆ% €'€˜€‚ÿWhen the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take.iOÄ”Æ$ €Ò€˜€‚ÿWhen the key generation is complete, a new set of controls will appear in the window to indicate this._Æ$Ç1ô>€|‡Ù$ÇzÇÊSection 8.2.5: The ‘Key fingerprint’ boxCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")V-”ÆzÇ) "€Z€€€€‚ÿSection 8.2.5: The ‘Key fingerprint’ boxá¶$Ç[È+ $€m€˜€€€‚ÿThe ‘Key fingerprint’ box shows you a fingerprint value for the generated key. This is derived cryptographically from the public key value, so it doesn't need to be kept secret.½ŒzÇÊ1 0€€˜€ã‰§L‰€€‚ÿThe fingerprint value is intended to be cryptographically secure, in the sense that it is computationally infeasible for someone to invent a second key with the same fingerprint, or to find a key with a particular fingerprint. So some utilities, such as the Pageant key list box (see section 9.2.1) and the Unix ssh-add utility, will list key fingerprints rather than the whole public key.•d[È­Ê1î …ÀŠÚ­ÊË›ÎSection 8.2.6: Setting a comment for your keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")[2ÊË) "€d€€€€‚ÿSection 8.2.6: Setting a comment for your key@­ÊHÌ+ $€+€˜€€€‚ÿIf you have more than one key and use them for different purposes, you don't need to memorise the key fingerprints in order to tell them apart. PuTTY allows you to enter a comment for your key, which will be displayed whenever PuTTY or Pageant asks you for the passphrase.; ˃Í1 0€€˜€€€€€‚ÿThe default comment format, if you don't specify one, contains the key type and the date of generation, such as rsa-key-20011212. Another commonly used approach is to use your name and the name of the computer the key will be used on, such as simon@simons-pc.óHÌ›Î% €ç€˜€‚ÿTo alter the key comment, just type your comment text into the ‘Key comment’ box before saving the private key. If you want to change the comment later, you can load the private key back into PuTTYgen, change the comment, and save it again.˜gƒÍ3Ï1– |‡O Û3Ï‘ÏÕSection 8.2.7: Setting a passphrase for your keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")^5›Î‘Ï) "€j€€€€‚ÿSection 8.2.7: Setting a passphrase for your keyë3Ï­% €×€˜€‚ÿThe ‘Key passphrase’ and ‘Confirm passphrase’ boxes allow you to choose a‘Ï­›Î passphrase for your key. The passphrase will be used to encrypt the key on disk, so you will not be able to use the key without first entering the passphrase.ݸ‘ÏŠ% €q€˜€‚ÿWhen you save the key, PuTTY will check that the ‘Key passphrase’ and ‘Confirm passphrase’ boxes both contain exactly the same passphrase, and will refuse to save the key otherwise.úÉ­„1 0€“€˜€€€ã80«f‰‚ÿIf you leave the passphrase fields blank, the key will be saved unencrypted. You should not do this without good reason; if you do, your private key file on disk will be all an attacker needs to gain access to any machine configured to accept that key. If you want to be able to log in without having to type a passphrase every time, you should consider using Pageant (chapter 9) so that your decrypted key is only held in memory rather than on disk.rAŠö1 0€ƒ€˜€€€€€‚ÿUnder special circumstances you may genuinely need to use a key with no passphrase; for example, if you need to run an automated batch script that needs to make an SSH connection, you can't be there to type the passphrase. In this case we recommend you generate a special key for each specific batch script (or whatever) that needs one, and on the server side you should arrange that each key is restricted so that it can only be used for that specific purpose. The documentation for your SSH server should explain how to do this (it will probably vary between servers).wL„m+ $€™€˜€€€‚ÿChoosing a good passphrase is difficult. Just as you shouldn't use a dictionary word as a password because it's easy for an attacker to run through a whole dictionary, you should not use a song lyric, quotation or other well-known sentence as a passphrase. DiceWare (www.diceware.com) recommends using at least five words each generated randomly by rolling five dice, which gives over 2^64 possible passphrases and is probably not a bad scheme. If you want your passphrase to make grammatical sense, this cuts down the possibilities a lot and you should use a longer one as a result.hAöÕ' €‚€˜€€‚ÿDo not forget your passphrase. There is no way to recover it.lmr 1’ÀŠ> Ür Õ  Section 8.2.8: Saving your private key to a disk fileCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")c:ÕÕ ) "€t€€€€‚ÿSection 8.2.8: Saving your private key to a disk fileŸ{r t $ €ö€˜€‚ÿOnce you have generated a key, set a comment field and set a passphrase, you are ready to save your private key to disk.Ì§Õ @ % €O€˜€‚ÿPress the ‘Save private key’ button. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press ‘Save’.Ä“t  1 0€'€˜€ã„@Ï؉ãÂ<û—‰‚ÿThis file is the one you will need to tell PuTTY to use for authentication (see section 4.18.5) or tell Pageant to load (see section 9.2.2).œk@   1½O Ó€ Ý   iASection 8.2.9: Saving your public key to a disk fileCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")b9  ) "€r€€€€‚ÿSection 8.2.9: Saving your public key to a disk fileb1  d1 0€c€˜€€€ã eHm‰‚ÿThe SSH 2 protocol drafts specify a standard format for storing public keys on disk. Some SSH servers (such as ssh.com's) require a public key in this format in order to accept authentication with the corresponding private key. (Others, such as OpenSSH, use a different format; see section 8.2.10.) è q% €Ñ€˜€‚ÿTo save your public key in the SSH 2 standard format, press the ‘Save public key’ button in PuTTYgen. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press ‘Save’.ôÉdq@+ $€“€˜€ã{ƒùN‰‚ÿYou will then probably want to copy the public key file to your SSH server machine. See section 8.qq@ 3 for general instructions on configuring public-key authentication once you have generated a key.øÓqiA% €§€˜€‚ÿIf you use this option with an SSH 1 key, the file PuTTYgen saves will contain exactly the same text that appears in the ‘Public key for pasting’ box. This is the only existing standard for SSH 1 public keys.ªyq@B1_> •ƒ ÞBƒBrESection 8.2.10: ‘Public key for pasting into authorized_keys file’CBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")pGiAƒB) "€Ž€€€€‚ÿSection 8.2.10: ‘Public key for pasting into authorized_keys file’åÀBhC% €€˜€‚ÿAll SSH 1 servers require your public key to be given to it in a one-line format before it will accept authentication with your private key. The OpenSSH server also requires this for SSH 2.kFƒBÓD% €€˜€‚ÿThe ‘Public key for pasting into authorized_keys file’ gives the public-key data in the correct one-line format. Typically you will want to select the entire contents of the box using the mouse, press Ctrl+C to copy it to the clipboard, and then paste the data into a PuTTY session which is already connected to the server.ŸuhCrE* $€ê€˜€ã{ƒùN‰‚ÿSee section 8.3 for general instructions on configuring public-key authentication once you have generated a key.^ÓDF1×Ó€ Ά ßFVFØISection 8.2.11: Reloading a private keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")U,rEVF) "€X€€€€‚ÿSection 8.2.11: Reloading a private keyöÑFLG% €£€˜€‚ÿPuTTYgen allows you to load an existing private key file into memory. If you do this, you can then change the passphrase and comment before saving it again; you can also make extra copies of the public key.jEVF¶H% €‹€˜€‚ÿTo load an existing key, press the ‘Load’ button. PuTTYgen will put up a dialog box where you can browse around the file system and find your key file. Once you select the file, PuTTYgen will ask you for a passphrase (if necessary) and will then display the key details in the same way as if it had just generated the key."÷LGØI+ $€ï€˜€ãE@Áv‰‚ÿIf you use the Load command to load a foreign key format, it will work, but you will see a message box warning you that the key you have loaded is not a PuTTY native key. See section 8.2.12 for information about importing foreign key formats.¢q¶HzJ1•ƒ „!àzJâJŒSection 8.2.12: Dealing with private keys in other formatsCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")h?ØIâJ) "€~€€€€‚ÿSection 8.2.12: Dealing with private keys in other formatsézJöK+ $€Ó€˜€€€‚ÿMost SSH1 clients use a standard format for storing private keys on disk. PuTTY uses this format as well; so if you have generated an SSH1 private key using OpenSSH or ssh.com's client, you can use it with PuTTY, and vice versa.ûÐâJñL+ $€¡€˜€€€‚ÿHowever, SSH2 private keys have no standard format. OpenSSH and ssh.com have different formats, and PuTTY's is different again. So a key generated with one client cannot immediately be used with another.Q öKBO1 0€A€˜€€€€€‚ÿUsing the ‘Import’ command from the ‘Conversions’ menu, PuTTYgen can load SSH2 private keys in OpenSSH's format and ssh.com's format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key so that you can use it with PuTTY. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since OpenSSH's SSH2 key format contains no space for a comment and ssh.com's default comment format is long and verbose.•dñLã€1 0€É€˜€€€ã䀅a‰‚ÿPuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the ‘Export’ options from the ‘ConvBOã€ØIersions’ menu. Exporting a key works exactly like saving it (see section 8.2.8) - you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase.©„BOŒ% € €˜€‚ÿNote that since only SSH2 keys come in different formats, the export options are not available if you have generated an SSH1 key.™hã€%‚14 Ά 3 !á%‚‹‚YŽSection 8.3: Getting ready for public key authenticationCBB("btn_up","JI(`',`t00000112')");EB("btn_up")f=Œ‹‚) "€z€€€€‚ÿSection 8.3: Getting ready for public key authenticationø%‚¨ƒ% €ñ€˜€‚ÿConnect to your SSH server using PuTTY with the SSH protocol. When the connection succeeds you will be prompted for your user name and password to login. Once logged in, you must configure the server to accept your public key for authentication:r,‹‚†F Z€Y€T˜‘€8‚€ƒ€€€€€ã eHm‰€€‚ÿ•If your server is using the SSH 1 protocol, you should change into the .ssh directory and open the file authorized_keys with your favourite editor. (You may have to create this file if this is the first key you have put in it). Then switch to the PuTTYgen window, select all of the text in the ‘Public key for pasting into authorized_keys file’ box (see section 8.2.10), and copy it to the clipboard (Ctrl+C). Then, switch back to the PuTTY window and insert the data into the open file, making sure it ends up all on one line. Save the file.Y¨ƒs‡: B€?€T˜‘€8‚€ƒ€€€€€‚ÿ•If your server is OpenSSH and is using the SSH 2 protocol, you should follow the same instructions, except that in earlier versions of OpenSSH 2 the file might be called authorized_keys2. (In modern versions the same authorized_keys file is used for both SSH 1 and SSH 2 keys.)牆Z‰^ Š€€T˜‘€8‚€ƒ€€€€€ã´åU‰€€€€€€€€€€‚ÿ•If your server is ssh.com's SSH 2 product, you need to save a public key file from PuTTYgen (see section 8.2.9), and copy that into the .ssh2 directory on the server. Then you should go into that .ssh2 directory, and edit (or create) a file called authorization. In this file you should put a line like Key mykey.pub, with mykey.pub replaced by the name of your key file.Ts‡Û‰- *€¨€T˜‘€8‚€ƒ€‚ÿ•For other SSH server software, you should refer to the manual for that server.9üZ‰‹= H€ù€˜€€€€€€€€€‚ÿYou may also need to ensure that your home directory, your .ssh directory, and any other files involved (such as authorized_keys, authorized_keys2 or authorization) are not group-writable. You can typically do this by using a command such as\8Û‰p‹$ €p€˜€‚ÿchmod g-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keysýÒ‹mŒ+ $€¥€˜€€€‚ÿYour server should now be configured to accept authentication using your private key. Now you need to configure PuTTY to attempt authentication using your private key. You can do this in any of three ways:‹Xp‹øŒ3 6€°€T˜‘€8‚€ƒ€ã„@Ï؉‚ÿ•Select the private key in PuTTY's configuration. See section 4.18.5 for details.¡hmŒ™9 B€Ð€T˜‘€8‚€ƒ€€€ãúÄùN‰‚ÿ•Specify the key file on the command line with the -i option. See section 3.7.3.14 for details.ÀŒøŒYŽ4 6€€T˜‘€8‚€ƒ€ã80«f‰‚ÿ•Load the private key into Pageant (see chapter 9). In this case PuTTY will automatically try to use it for authentication if it can.†U™ߎ1ë„!Ü€!âߎ8ÖÁChapter 9: Using Pageant for authenticationCBB("btn_up","JI(`',`Top')");EB("btn_up")Y0YŽ8) "€`€€€€‚ÿChapter 9: Using Pageant for authentication˦ߎÀ% €M€˜€‚ÿPageant is an SSH authentication agent. It holds your private keys in memory, already decoded, so that you can use them often without needing to type a passphrase8ÀYŽ._08nÀ/ .€`€ã|ƒùN€€€‰‚ÿSection 9.1: Getting started with PageantZ+ÀÈÀ/ .€V€ã}ƒùN€€€‰‚ÿSection 9.2: The Pageant main window[,nÀ#Á/ .€X€ã~ƒùN€€€‰‚ÿSection 9.3: The Pageant command lineY*ÈÀ|Á/ .€T€ã¢ƒùN€€€‰‚ÿSection 9.4: Using agent forwardingZ+#ÁÖÁ/ .€V€ã£ƒùN€€€‰‚ÿSection 9.5: Security considerations_|ÁfÂ1Ý3 !]‡!ãf½ÂCÊSection 9.1: Getting started with PageantCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")W.ÖÁ½Â) "€\€€€€‚ÿSection 9.1: Getting started with PageantsfÂZÃ* $€æ€˜€ãxƒùN‰‚ÿBefore you run Pageant, you need to have a private key. See chapter 8 to find out how to generate and use one.Ê¥½Â$Ä% €K€˜€‚ÿWhen you run Pageant, it will put an icon of a computer wearing a hat into the System tray. It will then sit and do nothing, until you load a private key into it. æZÃ/Å% €Í€˜€‚ÿIf you click the Pageant icon with the right mouse button, you will see a menu. Select ‘View Keys’ from this menu. The Pageant main window will appear. (You can also bring this window up by double-clicking on the Pageant icon.) ä$Ä8Æ% €É€˜€‚ÿThe Pageant window contains a list box. This shows the private keys Pageant is holding. When you start Pageant, it has no keys, so the list box will be empty. After you add one or more keys, they will show up in the list box.â½/ÅÇ% €{€˜€‚ÿTo add a key to Pageant, press the ‘Add Key’ button. Pageant will bring up a file dialog, labelled ‘Select Private Key File’. Find your private key file in this dialog, and press ‘Open’.ôÏ8ÆÈ% €Ÿ€˜€‚ÿPageant will now load the private key. If the key is protected by a passphrase, Pageant will ask you to type the passphrase. When the key has been loaded, it will appear in the list in the Pageant window.F!ÇTÉ% €C€˜€‚ÿNow start PuTTY and open an SSH session to a site that accepts your key. PuTTY will notice that Pageant is running, retrieve the key automatically from Pageant, and use it to authenticate. You can now open as many PuTTY sessions as you like without having to type your passphrase again.ïÄÈCÊ+ $€‰€˜€€€‚ÿWhen you want to shut down Pageant, click the right button on the Pageant icon in the System tray, and select ‘Exit’ from the menu. Closing the Pageant main window does not shut down Pageant.‹ZTÉÎÊ1™Ü€!‰!äÎÊ ËgÍSection 9.2: The Pageant main windowCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")R)CÊ Ë) "€R€€€€‚ÿSection 9.2: The Pageant main window=ÎÊ]Ì% €1€˜€‚ÿThe Pageant main window appears when you left-click on the Pageant system tray icon, or alternatively right-click and select ‘View Keys’ from the menu. You can use it to keep track of what keys are currently loaded into Pageant, and to add new ones or remove the existing keys.U& ˲Ì/ .€L€ã‰§L€€€‰‚ÿSection 9.2.1: The key list boxY*]Ì Í/ .€T€ãÂ<û—€€€‰‚ÿSection 9.2.2: The ‘Add Key’ button\-²ÌgÍ/ .€Z€ã :0-€€€‰‚ÿSection 9.2.3: The ‘Remove Key’ button€O ÍçÍ1]‡! "åçÍ4ÎSection 9.2.1: The key list boxCBB("btn_up","JI(`',`t00000117')");EB("btn_up")M$gÍ4Î) "€H€€€€‚ÿSection 9.2.1: The key list box½˜çÍñÎ% €1€˜€‚ÿThe large list box in the Pageant main window lists the private keys that are currently loaded into Pageant. The list might look something like this:jG4Î[Ï# €Ž€€‚ÿssh1 1024 22:c3:68:3b:09:41:36:c3:39:83:91:ae:71:b2:0f:04 key1kGñÎÆÏ$ €Ž€˜€‚ÿssh-rsa 1023 74:63:08:82:95:75:e1:7c:33:31:bb:cb:00:c0:89:8b key2P,[Ï"$ €X€˜€‚ÿFor each key, the lisÆÏ"gÍt box will tell you:ÛÆÏ=@ N€·€T˜‘€8‚€ƒ€€€€€€€‚ÿ•The type of the key. Currently, this can be ssh1 (an RSA key for use with the SSH v1 protocol), ssh-rsa (an RSA key for use with the SSH v2 protocol), or ssh-dss (a DSA key for use with the SSH v2 protocol).Q$"Ž- *€H€T˜‘€8‚€ƒ€‚ÿ•The size (in bits) of the key. æ=®: B€Í€T˜‘€8‚€ƒ€€€€€‚ÿ•The fingerprint for the public key. This should be the same fingerprint given by PuTTYgen, and (hopefully) also the same fingerprint shown by remote utilities such as ssh-keygen when applied to your authorized_keys file.S&Ž- *€L€T˜‘€8‚€ƒ€‚ÿ•The comment attached to the key.„S®…1"‰!j"æ…Ö§Section 9.2.2: The ‘Add Key’ buttonCBB("btn_up","JI(`',`t00000117')");EB("btn_up")Q(Ö) "€P€€€€‚ÿSection 9.2.2: The ‘Add Key’ buttonÞ…Ù% €½€˜€‚ÿTo add a key to Pageant by reading it out of a local disk file, press the ‘Add Key’ button in the Pageant main window, or alternatively right-click on the Pageant icon in the system tray and select ‘Add Key’ from there.\7Ö5% €o€˜€‚ÿPageant will bring up a file dialog, labelled ‘Select Private Key File’. Find your private key file in this dialog, and press ‘Open’. If you want to add more than one key at once, you can select multiple files using Shift-click (to select several adjacent files) or Ctrl-click (to select non-adjacent files).¥€ÙÚ% €€˜€‚ÿPageant will now load the private key(s). If a key is protected by a passphrase, Pageant will ask you to type the passphrase.Í¢5§+ $€E€˜€ã¢ƒùN‰‚ÿ(This is not the only way to add a private key to Pageant. You can also add one from a remote system by using agent forwarding; see section 9.4 for details.)‡VÚ.1æ "×"ç.‚ Section 9.2.3: The ‘Remove Key’ buttonCBB("btn_up","JI(`',`t00000117')");EB("btn_up")T+§‚) "€V€€€€‚ÿSection 9.2.3: The ‘Remove Key’ buttonÂ.D % €;€˜€‚ÿIf you need to remove a key from Pageant, select that key in the list box, and press the ‘Remove Key’ button. Pageant will remove the key from its memory.Ð¥‚ + $€K€˜€ã¢ƒùN‰‚ÿYou can apply this to keys you added using the ‘Add Key’ button, or to keys you added remotely using agent forwarding (see section 9.4); it makes no difference.Œ[D   1[j"†"è  ó û Section 9.3: The Pageant command lineCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")S* ó ) "€T€€€€‚ÿSection 9.3: The Pageant command line+   % € €˜€‚ÿPageant can be made to do things automatically when it starts up, by specifying instructions on its command line. If you're starting Pageant from the Windows GUI, you can arrange this by editing the properties of the Windows shortcut that it was started from.vGó ” / .€Ž€ãƒùN€€€‰‚ÿSection 9.3.1: Making Pageant automatically load keys on startupg8 û / .€p€ã«ƒùN€€€‰‚ÿSection 9.3.2: Making Pageant run another program¡p” œ 1 ×"ú "éœ  ¦Section 9.3.1: Making Pageant automatically load keys on startupCBB("btn_up","JI(`',`t00000118')");EB("btn_up")nEû  ) "€Š€€€€‚ÿSection 9.3.1: Making Pageant automatically load keys on startup˦œ Õ% €M€˜€‚ÿPageant can automatically load one or more private keys when it starts up, if you provide them on the Pageant command line. Your command line might then look like:X4 -$ €h€˜€‚ÿC:\PuTTY\pageant.exe d:\main.key d:\secondary.keyyUÕ¦$ €ª€˜€‚ÿIf the keys are stored encrypted, Pageant will request the passphrases on startup.’a-D@1g†"Ë"êD@£@«BSection 9.3.2: Making Pageant run another¦D@¦ programCBB("btn_up","JI(`',`t00000118')");EB("btn_up")_6¦£@) "€l€€€€‚ÿSection 9.3.2: Making Pageant run another program1 D@ÔA% €€˜€‚ÿYou can arrange for Pageant to start another program once it has initialised itself and loaded any keys specified on its command line. This program (perhaps a PuTTY, or a WinCVS making use of Plink, or whatever) will then be able to use the keys Pageant has loaded.zP£@NB* $€ €˜€€€‚ÿYou do this by specifying the -c option followed by the command, like this:]9ÔA«B$ €r€˜€‚ÿC:\PuTTY\pageant.exe d:\main.key -c C:\PuTTY\putty.exeŠYNB5C1- ú "#ë5C†Cn€Section 9.4: Using agent forwardingCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")Q(«B†C) "€P€€€€‚ÿSection 9.4: Using agent forwarding¨ƒ5C.D% €€˜€‚ÿAgent forwarding is a mechanism that allows applications on your SSH server machine to talk to the agent on your client machine.džCõE7 <€!€˜€€€€€€€‚ÿNote that at present, agent forwarding in SSH2 is only available when your SSH server is OpenSSH. The ssh.com server uses a different agent protocol which they have not published. If you would like PuTTY to be able to support agent forwarding to an ssh.com server, please write to ssh.com and explain to them that they are hurting themselves and their users by keeping their protocol secret.I.D>G7 <€%€˜€ãÊ6Êĉ€€ãÔÄùN‰‚ÿTo enable agent forwarding, first start Pageant. Then set up a PuTTY SSH session in which ‘Allow agent forwarding’ is enabled (see section 4.18.3). Open the session as normal. (Alternatively, you can use the -A command line option; see section 3.7.3.9 for details.)?õE}H% €5€˜€‚ÿIf this has worked, your applications on the server should now have access to a Unix domain socket which the SSH server will forward back to PuTTY, and PuTTY will forward on to the agent. To check that this has actually happened, you can try this command on Unix server machines:D!>GÁH# €B€€‚ÿunixbox:~$ echo $SSH_AUTH_SOCKC }HI# €@€€‚ÿ/tmp/ssh-XXNP18Jz/agent.287941 ÁH5I$ €€˜€‚ÿunixbox:~$wSI¬I$ €¦€˜€‚ÿIf the result line comes up blank, agent forwarding has not been enabled at all.Ú¯5I†J+ $€_€˜€€€‚ÿNow if you run ssh on the server and use it to connect through to another server that accepts one of the keys in Pageant, you should be able to log in without a password:D!¬IÊJ# €B€€‚ÿunixbox:~$ ssh -v otherunixbox+†JõJ# €€€‚ÿ[...]Q.ÊJFK# €\€€‚ÿdebug: next auth method to try is publickeya>õJ§K# €|€€‚ÿdebug: userauth_pubkey_agent: trying agent key my-putty-keyW4FKþK# €h€€‚ÿdebug: ssh-userauth2 successful: method publickey,§K*L$ €€˜€‚ÿ[...]M"þKwM+ $€E€˜€€€‚ÿIf you enable agent forwarding on that SSH connection as well (see the manual for your server-side SSH client to find out how to do this), your authentication keys will still be available on the next machine you connect to - two SSH connections away from where they're actually stored.¾“*L5N+ $€'€˜€€€‚ÿIn addition, if you have a private key on one of the SSH servers, you can send it all the way back to Pageant using the local ssh-add command:F#wM{N# €F€€‚ÿunixbox:~$ ssh-add ~/.ssh/id_rsaP-5NËN# €Z€€‚ÿNeed passphrase for /home/fred/.ssh/id_rsaR/{NO# €^€€‚ÿEnter passphrase for /home/fred/.ssh/id_rsa:fCËNƒO# €†€€‚ÿIdentity added: /home/fred/.ssh/id_rsa (/home/simon/.ssh/id_rsa)1 O´O$ €€˜€‚ÿunixbox:~$®‰ƒOn€% €€˜€‚ÿand then it's available to every machi´On€«Bne that has agent forwarding available (not just the ones downstream of the place you added it).‹Z´Où€1³ Ë"Q #ìù€K¬Section 9.5: Security considerationsCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")R)n€K) "€R€€€€‚ÿSection 9.5: Security considerationspKù€»‚% €—€˜€‚ÿUsing Pageant for public-key authentication gives you the convenience of being able to open multiple SSH sessions without having to type a passphrase every time, but also gives you the security benefit of never storing a decrypted private key on disk. Many people feel this is a good compromise between security and convenience. ÞKă+ $€½€˜€€€‚ÿIt is a compromise, however. Holding your decrypted private keys in Pageant is better than storing them in easy-to-find disk files, but still less secure than not storing them anywhere at all. This is for two reasons: Ù»‚Ñ…4 6€³€T˜‘€8‚€ƒ€€€‚ÿ•Windows unfortunately provides no way to protect pieces of memory from being written to the system swap file. So if Pageant is holding your private keys for a long period of time, it's possible that decrypted private key data may be written to the system swap file, and an attacker who gained access to your hard disk later on might be able to recover that data. (However, if you stored an unencrypted key in a disk file they would certainly be able to recover it.)#õăô‡. *€ë€T˜‘€8‚€ƒ€‚ÿ•Although, like most modern operating systems, Windows prevents programs from accidentally accessing one another's memory space, it does allow programs to access one another's memory space deliberately, for special purposes such as debugging. This means that if you allow a virus, trojan, or other malicious program on to your Windows system while Pageant is running, it could access the memory of the Pageant process, extract your decrypted authentication keys, and send them back to its master.íÑ… Š+ $€Û€˜€€€‚ÿSimilarly, use of agent forwarding is a security improvement on other methods of one-touch authentication, but not perfect. Holding your keys in Pageant on your Windows box has a security advantage over holding them on the remote server machine itself (either in an agent or just unencrypted on disk), because if the server machine ever sees your unencrypted private key then the sysadmin or anyone who cracks the machine can steal the keys and pretend to be you for as long as they want.= ô‡IŒ1 0€€˜€€€€€‚ÿHowever, the sysadmin of the server machine can always pretend to be you on that machine. So if you forward your agent to a server machine, then the sysadmin of that machine can access the forwarded agent connection and request signatures from your public keys, and can therefore log in to other machines as you. They can only do this to a limited extent - when the agent forwarding disappears they lose the ability - but using Pageant doesn't actually prevent the sysadmin (or hackers) on the server from doing this.c8 Š¬+ $€q€˜€€€‚ÿTherefore, if you don't trust the sysadmin of a server machine, you should never use agent forwarding to that machine. (Of course you also shouldn't store private keys on that machine, type passphrases into it, or log into other machines from it in any way at all; Pageant is hardly unique in this respect.)|KIŒ(Ž1T#zƒ#í(ŽwŽˆÆChapter 10: Common error messagesCBB("btn_up","JI(`',`Top')");EB("btn_up")O&¬wŽ) "€L€€€€‚ÿChapter 10: Common error messagesº•(Ž1% €+€˜€‚ÿThis chapter lists a number of common error messages which PuTTY and its associated tools can produce, and explains what they mean in more detail.n=wŽ«À1 0€{€˜€€€ã:ŒùN‰‚ÿWe do not attempt to list all error messages here: there are many which should never occur, and some which should be self-explanatory. If you get an error 1«À¬message which is not listed in this chapter and which you don't understand, report it to us as a bug (see appendix B) and we will add documentation for it.yJ1$Á/ .€”€ã¥ƒùN€€€‰‚ÿSection 10.1: ‘The server's host key is not cached in the registry’j;«ÀŽÁ/ .€v€ã¦ƒùN€€€‰‚ÿSection 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’g8$ÁõÁ/ .€p€ã§ƒùN€€€‰‚ÿSection 10.3: ‘Out of space for port forwardings’œmŽÁ‘Â/ .€Ú€ã¨ƒùN€€€‰‚ÿSection 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’S$õÁäÂ/ .€H€ã©ƒùN€€€‰‚ÿSection 10.5: ‘Out of memory’zK‘Â^Ã/ .€–€ãªƒùN€€€‰‚ÿSection 10.6: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’tEäÂÒÃ/ .€Š€ãÖƒùN€€€‰‚ÿSection 10.7: ‘Server refused our public key’ or ‘Key refused’Œ]^Ã^Ä/ .€º€ã̓ùN€€€‰‚ÿSection 10.8: ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’o@ÒÃÍÄ/ .€€€ã΃ùN€€€‰‚ÿSection 10.9: ‘Incoming packet was garbled on decryption’o@^Ä<Å/ .€€€ãσùN€€€‰‚ÿSection 10.10: ‘Authentication failed at PuTTY X11 proxy’vGÍIJÅ/ .€Ž€ãЃùN€€€‰‚ÿSection 10.11: ‘Network error: Software caused connection abort’n?<Å Æ/ .€~€ãуùN€€€‰‚ÿSection 10.12: ‘Network error: Connection reset by peer’h9²ÅˆÆ/ .€r€ãÒƒùN€€€‰‚ÿSection 10.13: ‘Network error: Connection refused’¤s Æ,Ç1ÆQ #x‡#î,ÇÇòËSection 10.1: ‘The server's host key is not cached in the registry’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")qHˆÆÇ) "€€€€€‚ÿSection 10.1: ‘The server's host key is not cached in the registry’-,ÇÊÈ% €€˜€‚ÿThis error message occurs when PuTTY connects to a new SSH server. Every server identifies itself by means of a host key; once PuTTY knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine.ðÇßÉ% €á€˜€‚ÿIf you see this message, it means that PuTTY has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator.²‡ÊÈ‘Ë+ $€€˜€€€‚ÿIf you see this message and you know that your installation of PuTTY has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH 2 with a server you have only used SSH 1 with before, you will see this message again. You should verify the correctness of the key as before.a7ßÉòË* $€n€˜€ãÿÅùN‰‚ÿSee section 2.2 for more information on host keys.•d‘ˇÌ1@zƒ#7$ï‡ÌéÌÓSection 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")b9òËéÌ) "€r€€€€‚ÿSection 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’ê‡ÌþÍ+ $€Õ€˜€€€‚ÿThis message, followed by ‘The server's host key does not match the one PuTTY has cached in the registry’, means that PuTTY has connected to the SSH server before, knows what its host key should be, but has found a different one.béÌ‹Ï+ $€Å€˜€€€‚ÿThis may mean that a malicious attacker has replaced your server with a different one, or has redirected your network connection to their own machine. On the other hand, it may simply mean that the administrator of your server has accidentally changed the key while upgrading the SSH software; this shouldn't happen but it is unfortunately possible.Û¶þÍr% €m€˜€‚ÿYou should contact your server's administrator and see whether they expect the ‹ÏròËhost key to have changed. If so, verify the new host key in the same way as you would if it was new.a7‹ÏÓ* $€n€˜€ãÿÅùN‰‚ÿSee section 2.2 for more information on host keys.’are1ux‡#9$ðeÄÚSection 10.3: ‘Out of space for port forwardings’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")_6ÓÄ) "€l€€€€‚ÿSection 10.3: ‘Out of space for port forwardings’. eò% €€˜€‚ÿPuTTY has a fixed-size buffer which it uses to store the details of all port forwardings you have set up in an SSH session. If you specify too many port forwardings on the PuTTY or Plink command line and this buffer becomes full, you will see this error message.èÃÄÚ% €‡€˜€‚ÿWe need to fix this (fixed-size buffers are almost always a mistake) but we haven't got round to it. If you actually have trouble with this, let us know and we'll move it up our priority list.Ç–ò¡1—7$Y$ñ¡58Section 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")”kÚ5) "€Ö€€€€‚ÿSection 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’œx¡Ñ$ €ð€˜€‚ÿThis occurs when the SSH server does not offer any ciphers which you have configured PuTTY to consider strong enough.g=58* $€z€˜€ãdÞ娉‚ÿSee section 4.17.5 for more information on this message.~MѶ1j9$î$ò¶ Section 10.5: ‘Out of memory’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")K"8) "€D€€€€‚ÿSection 10.5: ‘Out of memory’¡v¶¢+ $€í€˜€€€‚ÿThis occurs when PuTTY tries to allocate more memory than the system can give it. This may happen for genuine reasons: if the computer really has run out of memory, or if you have configured an extremely large number of lines of scrollback in your terminal. PuTTY is not able to recover from running out of memory; it will terminate immediately after giving this error. ä« % €É€˜€‚ÿHowever, this error can also occur when memory is not running out at all, because PuTTY receives data in the wrong format. In SSH 2 and also in SFTP, the server sends the length of each message before the message itself; so PuTTY will receive the length, try to allocate space for the message, and then receive the rest of the message. If the length PuTTY receives is garbage, it will try to allocate a ridiculous amount of memory, and will terminate with an ‘Out of memory’ error.Ô¢° 1 0€©€˜€ã€„ùN‰ãØ„ùN‰‚ÿThis can happen in SSH 2, if PuTTY and the server have not enabled encryption in the same way (see question A.6.6 in the FAQ). Some versions of OpenSSH have a knownq problem with this: see question A.6.18.pE«  + $€‹€˜€ã„ùN‰‚ÿThis can also happen in PSCP or PSFTP, if your login scripts on the server generate output: the client program will be expecting an SFTP message starting with a length, and if it receives some text from your login scripts instead it will try to interpret them as a message length. See question A.6.7 for details of this.¥t° Å 1Y$€$óÅ 7 @Section 10.6: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")rI 7) "€’€€€€‚ÿSection 10.6: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’֥Š 1 0€K€˜€€€ã:ŒùN‰‚ÿAny error beginning with the word ‘Internal’ should never occur. If it does, there is a bug in PuTTY by definition; please see appendix B and report it to us.Ç¢7 @% €E€˜€‚ÿSimilarly, any error message starting with ‘Assertion failed’ is a bug in PuTTY. Please report it to us, and include the exact text from the error message box.  @ Ÿn «@1Éî$%ƒ$ô«@AtDSection 10.7: ‘Server refused our public key’ or ‘Key refused’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")lC @A) "€†€€€€‚ÿSection 10.7: ‘Server refused our public key’ or ‘Key refused’Ë «@âA+ $€A€˜€ã{ÄùN‰‚ÿVarious forms of this error are printed in the PuTTY window, or written to the PuTTY Event Log (see section 3.1.3.1) when trying public-key authentication.>A C% €3€˜€‚ÿIf you see one of these messages, it means that PuTTY has sent a public key to the server and offered to authenticate with it, and the server has refused to accept authentication. This usually means that the server is not configured to accept this key to authenticate this user.T)âAtD+ $€S€˜€€€‚ÿThis is almost certainly not a problem with PuTTY. If you see this type of message, the first thing you should do is check your server configuration carefully. Also, read the PuTTY Event Log; the server may have sent diagnostic messages explaining exactly what problem it had with your setup.·† C+E1H€$õ„$õ+E¯EsGSection 10.8: ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")„[tD¯E) "€¶€€€€‚ÿSection 10.8: ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’8+EçF% €'€˜€‚ÿThis error occurs when PuTTY decrypts an SSH packet and its checksum is not correct. This probably means something has gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client or in the server.Œb¯EsG* $€Ä€˜€ãØ„ùN‰‚ÿA known server problem which can cause this error is described in question A.6.18 in the FAQ.šiçF H11%ƒ$®†$ö HtH>JSection 10.9: ‘Incoming packet was garbled on decryption’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")g>sGtH) "€|€€€€‚ÿSection 10.9: ‘Incoming packet was garbled on decryption’> H²I% €3€˜€‚ÿThis error occurs when PuTTY decrypts an SSH packet and the decrypted data makes no sense. This probably means something has gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client or in the server.ŒbtH>J* $€Ä€˜€ãØ„ùN‰‚ÿA known server problem which can cause this error is described in question A.6.18 in the FAQ.ši²IØJ1èõ„$&%÷ØJ?KÌSection 10.10: ‘Authentication failed at PuTTY X11 proxy’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")g>>J?K) "€|€€€€‚ÿSection 10.10: ‘Authentication failed at PuTTY X11 proxy’ѬØJL% €Y€˜€‚ÿThis error is reported when PuTTY is doing X forwarding. It is sent back to the X application running on the SSH server, which will usually report the error to the user. ß?KN+ $€¿€˜€ã¤ÄùN‰‚ÿWhen PuTTY enables X forwarding (see section 3.4) it creates a virtual X display running on the SSH server. This display requires authentication to connect to it (this is how PuTTY prevents other users on your server machine from connecting through the PuTTY proxy to your real X display). PuTTY also sends the server the details it needs to enable clients to connect, and the server should put this mechanism in place automatically, so your X applications should just work.ILo€+ $€=€˜€€€‚ÿA common reason why people see this message is because they used SSH to log in as one user (let's say ‘fred’), and then used the Unix su command to become another user (typically ‘root’). The original user, ‘fred’, has access to the X authentication data provided by the SSH server, and can run X applications which are forwarded over the SSH connection. However, the second user (‘root’) does not automatically have the authentication dataNo€>J passed on to it, so attempting to run an X application as that user often fails with this error.]&NÌ7 <€M€˜€€€€€€€‚ÿIf this happens, it is not a problem with PuTTY. You need to arrange for your X authentication data to be passed from the user you logged in as to the user you used su to become. How you do this depends on your particular system; in fact many modern versions of su do it automatically.¡po€m‚1¢®†$%øm‚Û‚†Section 10.11: ‘Network error: Software caused connection abort’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")nEÌÛ‚) "€Š€€€€‚ÿSection 10.11: ‘Network error: Software caused connection abort’b>m‚=ƒ$ €|€˜€‚ÿIn modern versions of PuTTY, you should not see this error.4Û‚q„% €€˜€‚ÿWindows's documentation about this error condition is not very good, but as far as we can tell, this error occurs when PuTTY is listening on a port, another program makes a connection to that port, but closes the connection so fast that PuTTY has no time to answer it.ï=ƒ‹…+ $€ß€˜€ã¥ÄùN‰‚ÿPuTTY only ever listens on a port when it is doing local-to-remote port forwarding (see section 3.5); and if an incoming connection on that port receives this error, PuTTY should simply close the connection and continue without error.„`q„†$ €À€˜€‚ÿIf you see this error in PuTTY 0.53 or above, we would welcome a report of the circumstances.™h‹…¨†1ñ&%y%ù¨†‡™‰Section 10.12: ‘Network error: Connection reset by peer’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")f=†‡) "€z€€€€‚ÿSection 10.12: ‘Network error: Connection reset by peer’)¨†7ˆ% € €˜€‚ÿThis error occurs when the machines at each end of a network connection lose track of the state of the connection between them. For example, you might see it if your SSH server crashes, and manages to reboot fully before you next attempt to send data to it.b1‡™‰1 0€c€˜€ã§„ùN‰ãêøÂk‰‚ÿHowever, the most common reason to see this message is if you are connecting through a firewall or a NAT router which has timed the connection out. See question A.6.12 in the FAQ for more details. You may be able to improve the situation by using keepalives; see section 4.13.3 for details on this.“b7ˆ,Š15%;%ú,ŠŒŠaŒSection 10.13: ‘Network error: Connection refused’CBB("btn_up","JI(`',`t00000123')");EB("btn_up")`7™‰ŒŠ) "€n€€€€‚ÿSection 10.13: ‘Network error: Connection refused’ùÔ,Š…‹% €©€˜€‚ÿThis error means that the network connection PuTTY tried to make to your server was rejected by the server. Usually this happens because the server does not provide the service which PuTTY is trying to access.Ü·ŒŠaŒ% €o€˜€‚ÿCheck that you are connecting with the correct protocol (SSH, Telnet or Rlogin), and check that the port number is correct. If that fails, consult the administrator of your server.p?…‹ÑŒ1øy%W€%ûÑŒÕÀAppendix A: PuTTY FAQCBB("btn_up","JI(`',`Top')");EB("btn_up")CaŒ) "€4€€€€‚ÿAppendix A: PuTTY FAQƒ_ÑŒ—$ €¾€˜€‚ÿThis FAQ is published on the PuTTY web site, and also provided as an appendix in the manual.^/õ/ .€^€ãÔƒùN€€€‰‚ÿSection A.1: Features supported in PuTTYc4—XŽ/ .€h€ã„ùN€€€‰‚ÿSection A.2: Ports to other operating systemsd5õ¼Ž/ .€j€ã(„ùN€€€‰‚ÿSection A.3: Embedding PuTTY in other programs_0XŽ/ .€`€ãW„ùN€€€‰‚ÿSection A.4: Details of PuTTY's operationR#¼Žm/ .€F€ãP„ùN€€€‰‚ÿSection A.5: HOWTO questionsR#¿/ .€F€ãz„ùN€€€‰‚ÿSection A.6: TroubleshootingU&m À/ .€L€ãЄùN€€€‰‚ÿSection A.7: S¿ ÀaŒecurity questions[,¿{À/ .€X€ãÕ„ùN€€€‰‚ÿSection A.8: Administrative questionsZ+ ÀÕÀ/ .€V€ã6ŒùN€€€‰‚ÿSection A.9: Miscellaneous questions‰X{À^Á1Û;% …%ü^Á´Á9ÉSection A.1: Features supported in PuTTYCBB("btn_up","JI(`',`t00000137')");EB("btn_up")V-ÕÀ´Á) "€Z€€€€‚ÿSection A.1: Features supported in PuTTY¬‡^Á`Â% €€˜€‚ÿIn general, if you want to know if PuTTY supports a particular feature, you should look for it on the PuTTY web site. In particular:O´Á¯Ã4 6€7€T˜‘€8‚€ƒ€€€‚ÿ•try the changes page, and see if you can find the feature on there. If a feature is listed there, it's been implemented. If it's listed as a change made since the latest version, it should be available in the development snapshots, in which case testing will be very welcome.´€`ÂcÄ4 6€€T˜‘€8‚€ƒ€€€‚ÿ•try the Wishlist page, and see if you can find the feature there. If it's on there, it probably hasn't been implemented.`1¯ÃÃÄ/ .€b€ãÕƒùN€€€‰‚ÿQuestion A.1.1: Does PuTTY support SSH v2?”_cÄWÅ5 :€¾€ã„ùN€€€€€‰‚ÿQuestion A.1.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?`1ÃÄ·Å/ .€b€ãøƒùN€€€‰‚ÿQuestion A.1.3: Does PuTTY support SSH v1?d5WÅÆ/ .€j€ãùƒùN€€€‰‚ÿQuestion A.1.4: Does PuTTY support local echo?}N·Å˜Æ/ .€œ€ãúƒùN€€€‰‚ÿQuestion A.1.5: Does PuTTY support storing its settings in a disk file?zKÆÇ/ .€–€ãûƒùN€€€‰‚ÿQuestion A.1.6: Does PuTTY support full-screen mode, like a DOS box? q˜Æ²Ç/ .€â€ãüƒùN€€€‰‚ÿQuestion A.1.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?ƒTÇ5È/ .€¨€ãýƒùN€€€‰‚ÿQuestion A.1.8: Is there an option to turn off the annoying host key prompts?Ž_²ÇÃÈ/ .€¾€ãþƒùN€€€‰‚ÿQuestion A.1.9: Will you write an SSH server for the PuTTY suite, to go with the client?vG5È9É/ .€Ž€ãÿƒùN€€€‰‚ÿQuestion A.1.10: Can PSCP or PSFTP transfer files in ASCII mode?‹ZÃÈÄÉ1ôW€%‡%ýÄÉʸËQuestion A.1.1: Does PuTTY support SSH v2?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")X/9ÉÊ) "€^€€€€‚ÿQuestion A.1.1: Does PuTTY support SSH v2?'öÄÉCË1 0€í€˜€€€€€‚ÿYes. SSH v2 support has been available in PuTTY since version 0.50. However, currently the default SSH protocol is v1; to select SSH v2 if your server supports both, go to the SSH panel and change the Preferred SSH protocol version option.uQʸË$ €¢€˜€‚ÿPublic key authentication (both RSA and DSA) in SSH v2 is new in version 0.52.·†CËoÌ1@ …%ü‡%þoÌû̯ÍQuestion A.1.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")Œ]¸ËûÌ/ .€º€€€€€€‚ÿQuestion A.1.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?´‰o̯Í+ $€€˜€€€‚ÿVersion 0.52 doesn't, but in the latest development snapshots PuTTYgen can load and save both OpenSSH and ssh.com private key files.‹ZûÌ:Î1µ‡%dˆ%ÿ:Î’ÎïÎQuestion A.1.3: Does PuTTY support SSH v1?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")X/¯Í’Î) "€^€€€€‚ÿQuestion A.1.3: Does PuTTY support SSH v1?]9:ÎïÎ$ €r€˜€‚ÿYes. SSH 1 support has always been available in PuTTY.^’Î~Ï1·ü‡%Õ&~ÏÚÏAQuestion A.1.4: Does PuTTY support local echo?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")\3ïÎÚÏ) "€f€€€€‚ÿQuestion A.1.4: Does PuTTY support local echo?[7~ÏA$ €n€˜€‚ÿYÚÏAïÎes. Version 0.52 has proper support for local echo.ÕÚÏA+ $€«€˜€€€‚ÿIn version 0.51 and before, local echo could not be separated from local line editing (where you type a line of text locally, and it is not sent to the server until you press Return, so you have the chance to edit it and correct mistakes before the server sees it). New in version 0.52, local echo and local line editing are separate options, and by default PuTTY will try to determine automatically whether to enable them or not, based on which protocol you have selected and also based on hints from the server. If you have a problem with PuTTY's default choice, you can force each option to be enabled or disabled as you choose. The controls are in the Terminal panel, in the section marked ‘Line discipline options’.¨wAé1 dˆ%&é^ôQuestion A.1.5: Does PuTTY support storing its settings in a disk file?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")uLA^) "€˜€€€€‚ÿQuestion A.1.5: Does PuTTY support storing its settings in a disk file?–léô* $€Ø€˜€ãPÅùN‰‚ÿNot at present, although section 4.21 in the documentation gives a method of achieving the same effect.¥t^™1ÄÕ&&™ ]Question A.1.6: Does PuTTY support full-screen mode, like a DOS box?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")rIô ) "€’€€€€‚ÿQuestion A.1.6: Does PuTTY support full-screen mode, like a DOS box?R.™]$ €\€˜€‚ÿYes; this is a new feature in version 0.52.Ëš (1Ì&&(Àô Question A.1.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")˜o]À) "€Þ€€€€‚ÿQuestion A.1.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?6(ö$ €$€˜€‚ÿNo, it doesn't.ÿÚÀõ% €µ€˜€‚ÿRemembering your password is a bad plan for obvious security reasons: anyone who gains access to your machine while you're away from your desk can find out the remembered password, and use it, abuse it or change it.¼‘ö± + $€#€˜€€€‚ÿIn addition, it's not even possible for PuTTY to automatically send your password in a Telnet session, because Telnet doesn't give the client software any indication of which part of the login process is the password prompt. PuTTY would have to guess, by looking for words like ‘password’ in the session data; and if your login program is written in something other than English, this won't work.Cõô + $€1€˜€ãxƒùN‰‚ÿIn SSH, remembering your password would be possible in theory, but there doesn't seem to be much point since SSH supports public key authentication, which is more flexible and more secure. See chapter 8 in the documentation for a full discussion of public key authentication.®}± ¢ 1&y„&¢  çDQuestion A.1.8: Is there an option to turn off the annoying host key prompts?CBB("btn_up","JI(`',`t00000138')");EB("btn_up"){Rô  ) "€¤€€€€‚ÿQuestion A.1.8: Is there an option to turn off the annoying host key prompts?”p¢ ± $ €à€˜€‚ÿNo, there isn't. And there won't be. Even if you write it yourself and send us the patch, we won't accept it.3  @+ $€€˜€€€‚ÿThose annoying host key prompts are the whole point of SSH. Without them, all the cryptographic technology SSH uses to secure your session is doing nothing more than making an attacker's job slightly harder; instead of sitting between you and the server with a packet sniffer, the attacker must actually subvert a router and start modifying the packets going back and forth. But that's not all that much harder than just sniffing; and without host key checking, it will go completely undetected by client or server.±  @ô ªs± ¶B7 <€ç€˜€€€€€€€‚ÿHost key checking is your guarantee that the encryption you put on your data at the client end is the same encryption taken off the data at the server end; it's your guarantee that it hasn't been removed and replaced somewhere on the way. Host key checking makes the attacker's job astronomically hard, compared to packet sniffing, and even compared to subverting a router. Instead of applying a little intelligence and keeping an eye on Bugtraq, the attacker must now perform a brute-force attack against at least one military-strength cipher. That insignificant host key prompt really does make that much difference.1 @çD+ $€ €˜€€€‚ÿIf you're having a specific problem with host key checking - perhaps you want an automated batch job to make use of PSCP or Plink, and the interactive host key prompt is hanging the batch process - then the right way to fix it is to add the correct host key to the Registry in advance. That way, you retain the important feature of host key checking: the right key will be accepted and the wrong ones will not. Adding an option to turn host key checking off completely is the wrong solution and we will not do it.¹ˆ¶B E1A&G‡& E&FáHQuestion A.1.9: Will you write an SSH server for the PuTTY suite, to go with the client?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")†]çD&F) "€º€€€€‚ÿQuestion A.1.9: Will you write an SSH server for the PuTTY suite, to go with the client?% EKG% €€˜€‚ÿNo. The only reason we might want to would be if we could easily re-use existing code and significantly cut down the effort. We don't believe this is the case; there just isn't enough common ground between an SSH client and server to make it worthwhile.–q&FáH% €ã€˜€‚ÿIf someone else wants to use bits of PuTTY in the process of writing a Windows SSH server, they'd be perfectly welcome to of course, but I really can't see it being a lot less effort for us to do that than it would be for us to write a server from the ground up. We don't have time, and we don't have motivation. The code is available if anyone else wants to try it.¡pKG‚I16y„& ‰&‚IðI¸KQuestion A.1.10: Can PSCP or PSFTP transfer files in ASCII mode?CBB("btn_up","JI(`',`t00000138')");EB("btn_up")nEáHðI) "€Š€€€€‚ÿQuestion A.1.10: Can PSCP or PSFTP transfer files in ASCII mode?Ô¯‚IÄJ% €_€˜€‚ÿUnfortunately not. This is a limitation of the file transfer protocols: the SCP and SFTP protocols have no notion of transferring a file in anything other than binary mode.ôÏðI¸K% €Ÿ€˜€‚ÿSFTP is designed to be extensible, so it's possible that an extension might be proposed at some later date that implements ASCII transfer. But the PuTTY team can't do anything about it until that happens.Ž]ÄJFL1¸G‡&L'FL¡L ƒSection A.2: Ports to other operating systemsCBB("btn_up","JI(`',`t00000137')");EB("btn_up")[2¸K¡L) "€d€€€€‚ÿSection A.2: Ports to other operating systems=FLÞM% €1€˜€‚ÿThe eventual goal is for PuTTY to be a multi-platform program, able to run on at least Windows, MacOS and Unix. Whether this will actually ever happen I have no idea, but it is the plan. A Mac port has been started, but is only half-finished and currently not moving very fast.º•¡L¤€% €+€˜€‚ÿPorting will become easier once PuTTY has a generalised porting layer, drawing a clear line between platform-dependent and platform-independent code. The general intention is for this porting layer to evolve naturally as part of the process of doing the first port. One particularly nasty part of this will be separating the many configuration options into platform-dependent and platform-independent ones; for example, the options controlling when the Windows System menu appears will be pretty much meaningÞM¤€¸Kless under X11 or perhaps other windowing systems, whereas Telnet Passive Mode is universal and shouldn't need to be specified once for each platform.`1ÞM/ .€b€ã,„ùN€€€‰‚ÿQuestion A.2.1: What ports of PuTTY exist?uF¤€y/ .€Œ€ã#„ùN€€€‰‚ÿQuestion A.2.2: Will there be a port to Windows CE or PocketPC?e6Þ/ .€l€ã$„ùN€€€‰‚ÿQuestion A.2.3: Is there a port to Windows 3.1?f7yD‚/ .€n€ã%„ùN€€€‰‚ÿQuestion A.2.4: Will there be a port to the Mac?c4Þ§‚/ .€h€ã&„ùN€€€‰‚ÿQuestion A.2.5: Will there be a port to Unix?c4D‚ ƒ/ .€h€ã'„ùN€€€‰‚ÿQuestion A.2.6: Will there be a port to EPOC?‹Z§‚•ƒ1º ‰&\'•ƒíƒO†Question A.2.1: What ports of PuTTY exist?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")X/ ƒíƒ) "€^€€€€‚ÿQuestion A.2.1: What ports of PuTTY exist?¸“•ƒ¥„% €'€˜€‚ÿCurrently, PuTTY only runs on full Win32 systems. This includes Windows 95, 98, and ME, and it includes Windows NT, Windows 2000 and Windows XP.Ñšíƒv…7 <€5€˜€€€ã#„ùN‰ã$„ùN‰‚ÿIt does not include Windows CE (see question A.2.2), and it does not quite include the Win32s environment under Windows 3.1 (see question A.2.3).Ù´¥„O†% €i€˜€‚ÿWe do not have ports for any other systems at the present time. If anyone told you we had a Unix port, or an iPaq port, or any other port of PuTTY, they were mistaken. We don't. ov…ï†1L'ï' ï†\‡ôˆQuestion A.2.2: Will there be a port to Windows CE or PocketPC?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")mDO†\‡) "€ˆ€€€€‚ÿQuestion A.2.2: Will there be a port to Windows CE or PocketPC?÷Òï†Sˆ% €¥€˜€‚ÿProbably not in the particularly near future. Despite sharing large parts of the Windows API, in practice WinCE doesn't appear to be significantly easier to port to than a totally different operating system.¡}\‡ôˆ$ €ú€˜€‚ÿHowever, PuTTY on portable devices would clearly be a useful thing, so in the long term I hope there will be a WinCE port._Sˆ„‰1£\'õ' „‰á‰'Question A.2.3: Is there a port to Windows 3.1?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")]4ôˆá‰) "€h€€€€‚ÿQuestion A.2.3: Is there a port to Windows 3.1?Ü„‰èŠ+ $€¹€˜€€€‚ÿPuTTY is a 32-bit application from the ground up, so it won't run on Windows 3.1 as a native 16-bit program; and it would be very hard to port it to do so, because of Windows 3.1's vile memory allocation mechanisms.«†á‰“Œ% € €˜€‚ÿHowever, it is possible in theory to compile the existing PuTTY source in such a way that it will run under Win32s (an extension to Windows 3.1 to let you run 32-bit programs). In order to do this you'll need the right kind of C compiler - modern versions of Visual C at least have stopped being backwards compatible to Win32s. Also, the last time we tried this it didn't work very well.”pèŠ'$ €à€˜€‚ÿIf you're interested in running PuTTY under Windows 3.1, help and testing in this area would be very welcome!‘`“Œ¸1kï' ' ¸Ž#Question A.2.4: Will there be a port to the Mac?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")^5'Ž) "€j€€€€‚ÿQuestion A.2.4: Will there be a port to the Mac? è¸#% €Ñ€˜€‚ÿA Mac port was started once and is half-finished, but development has been static for some time and the main PuTTY code has moved on, so it's not clear how quickly development would resume even if developer effort were available.Ž]Ž±1¨õ'' ±ÀeÁQuestion A.2.5: Will there be a port to Unix?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")[2#À) "€d€€€€‚ÿQuestion A.2.5: Will there be a por±À#t to Unix?M±eÁ1 0€9€˜€€€€€‚ÿI hope so, if only so that I can have an xterm-like program that supports exactly the same terminal emulation as PuTTY. If and when we do do a Unix port, it will have a local-terminal back end so it can be used like an xterm, rather than only being usable as a network utility.Ž]ÀóÁ1z 'B‚' óÁNÂmÃQuestion A.2.6: Will there be a port to EPOC?CBB("btn_up","JI(`',`t00000149')");EB("btn_up")[2eÁNÂ) "€d€€€€‚ÿQuestion A.2.6: Will there be a port to EPOC?ôóÁmÃ+ $€é€˜€€€‚ÿI hope so, but given that ports aren't really progressing very fast even on systems the developers do already know how to program for, it might be a long time before any of us get round to learning a new system and doing the port for that.^NÂüÃ1å'qƒ'üÃÿÿÿÿáÅSection A.3: Embedding PuTTY in other programsCBB("btn_up","JI(`',`t00000137')");EB("btn_up")\3mÃXÄ) "€f€€€€‚ÿSection A.3: Embedding PuTTY in other programssDüÃËÄ/ .€ˆ€ã)„ùN€€€‰‚ÿQuestion A.3.1: Is the SSH or Telnet code available as a DLL?†WXÄQÅ/ .€®€ã*„ùN€€€‰‚ÿQuestion A.3.2: Is the SSH or Telnet code available as a Visual Basic component?aËÄáÅ/ .€Â€ã+„ùN€€€‰‚ÿQuestion A.3.3: How can I use PuTTY to make an SSH connection from within another program?žmQÅÆ1B‚'…'ÆêÆšÈQuestion A.3.1: Is the SSH or Telnet code available as a DLL?CBB("btn_up","JI(`',`t00000156')");EB("btn_up")kBáÅêÆ) "€„€€€€‚ÿQuestion A.3.1: Is the SSH or Telnet code available as a DLL? åÆôÇ% €Ë€˜€‚ÿNo, it isn't. It would take a reasonable amount of rewriting for this to be possible, and since the PuTTY project itself doesn't believe in DLLs (they make installation more error-prone) none of us has taken the time to do it.¦êÆšÈ% €€˜€‚ÿMost of the code cleanup work would be a good thing to happen in general, so if anyone feels like helping, we wouldn't say no.±€ôÇKÉ1µqƒ'[‡'KÉÉÉÌQuestion A.3.2: Is the SSH or Telnet code available as a Visual Basic component?CBB("btn_up","JI(`',`t00000156')");EB("btn_up")~UšÈÉÉ) "€ª€€€€‚ÿQuestion A.3.2: Is the SSH or Telnet code available as a Visual Basic component?U0KÉË% €a€˜€‚ÿNo, it isn't. None of the PuTTY team uses Visual Basic, and none of us has any particular need to make SSH connections from a Visual Basic application. In addition, all the preliminary work to turn it into a DLL would be necessary first; and furthermore, we don't even know how to write VB components.â½ÉÉÌ% €{€˜€‚ÿIf someone offers to do some of this work for us, we might consider it, but unless that happens I can't see VB integration being anywhere other than the very bottom of our priority list.»ŠË»Ì1B…'+‰'»ÌCÍýÎQuestion A.3.3: How can I use PuTTY to make an SSH connection from within another program?CBB("btn_up","JI(`',`t00000156')");EB("btn_up")ˆ_ÌCÍ) "€¾€€€€‚ÿQuestion A.3.3: How can I use PuTTY to make an SSH connection from within another program?d?»Ì§Î% €€˜€‚ÿProbably your best bet is to use Plink, the command-line connection tool. If you can start Plink as a second Windows process, and arrange for your primary process to be able to send data to the Plink process, and receive data from it, through pipes, then you should be able to make SSH connections from your program.V2CÍýÎ$ €d€˜€‚ÿThis is what CVS for Windows does, for example.ŠY§Î‡Ï1%[‡'p(‡ÏÿÿÿÿÚSection A.4: Details of PuTTY's operationCBB("btn_up","JI(`',`t00000137')");EB("btn_up")W.ýÎ ) "€\€€€€‚ÿSection A.4: Details of PuTTY's operation‡Ï ýÎh9‡Ït/ .€r€ãN„ùN€€€‰‚ÿQuestion A.4.1: What terminal type does PuTTY use?f7 Ú/ .€n€ãO„ùN€€€‰‚ÿQuestion A.4.2: Where does PuTTY store its data?“btm1+‰'Ê(mÍ‚Question A.4.1: What terminal type does PuTTY use?CBB("btn_up","JI(`',`t00000160')");EB("btn_up")`7ÚÍ) "€n€€€€‚ÿQuestion A.4.1: What terminal type does PuTTY use?rHm?* $€€˜€€€‚ÿFor most purposes, PuTTY can be considered to be an xterm terminal.QÍ7 <€5€˜€€€€€€€‚ÿPuTTY also supports some terminal control sequences not supported by the real xterm: notably the Linux console sequences that reconfigure the colour palette, and the title bar control sequences used by DECterm (which are different from the xterm ones; PuTTY supports both).òÁ?‚1 0€ƒ€˜€€€€€‚ÿBy default, PuTTY announces its terminal type to the server as xterm. If you have a problem with this, you can reconfigure it to say something else; vt220 might help if you have trouble.‘`1Rp(&(qe Question A.4.2: Where does PuTTY store its data?CBB("btn_up","JI(`',`t00000160')");EB("btn_up")^5‚q) "€j€€€€‚ÿQuestion A.4.2: Where does PuTTY store its data?iþ$ €Ò€˜€‚ÿPuTTY stores most of its data (saved sessions, SSH host keys) in the Registry. The precise location isS/qQ$ €^€˜€‚ÿHKEY_CURRENT_USER\Software\SimonTatham\PuTTY£sþô0 0€æ€˜€€€€€‚ÿand within that area, saved sessions are stored under Sessions while host keys are stored under SshHostKeys.àQ 1 0€Á€˜€€€€€‚ÿPuTTY also requires a random number seed file, to improve the unpredictability of randomly chosen data needed as part of the SSH cryptography. This is stored by default in your Windows home directory (%HOMEDRIVE%\%HOMEPATH%), or in the actual Windows directory (such as C:\WINDOWS) if the home directory doesn't exist, for example if you're using Win95. If you want to change the location of the random number seed file, you can put your chosen pathname in the Registry, at`<ôe $ €x€˜€‚ÿHKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile}L â 1ÒÊ(V (â ÿÿÿÿ´Section A.5: HOWTO questionsCBB("btn_up","JI(`',`t00000137')");EB("btn_up")J!e , ) "€B€€€€‚ÿSection A.5: HOWTO questionsn?â š / .€~€ãQ„ùN€€€‰‚ÿQuestion A.5.1: How can I make PuTTY start up maximised?—h, 1 / .€Ð€ãR„ùN€€€‰‚ÿQuestion A.5.2: How can I create a Windows shortcut to start a particular saved session directly?„Uš µ / .€ª€ãS„ùN€€€‰‚ÿQuestion A.5.3: How can I start an SSH session straight from the command line?‹\1 @ / .€¸€ãT„ùN€€€‰‚ÿQuestion A.5.4: How do I copy and paste between PuTTY and other Windows applications?”eµ Ô / .€Ê€ãU„ùN€€€‰‚ÿQuestion A.5.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.®@ ‚ / .€þ€ãV„ùN€€€‰‚ÿQuestion A.5.6: How do I use all PuTTY's features (public keys, port forwarding, SSH v2, etc.) in PSCP, PSFTP and Plink?²‚Ô 40 .€€ã‚„ùN€€€‰‚ÿQuestion A.5.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.€Q‚ ´/ .€¢€ãy„ùN€€€‰‚ÿQuestion A.5.8: How do I use PSCP to copy a file whose name has spaces in?™h4M1Ú&(€(M³3@Question A.5.1: How can I make PuTTY start up maximised?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")f=´³) "€z€€€€‚ÿQuestion A.5.1: How can I make PuTTY start up maximised?tPM3@$ € €˜€‚ÿCreate a Windows shortcut to start PuTTY³3@´ from, and set it as ‘Run Maximized’.‘³õ@1†V ((õ@„A{BQuestion A.5.2: How can I create a Windows shortcut to start a particular saved session directly?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")f3@„A) "€Ì€€€€‚ÿQuestion A.5.2: How can I create a Windows shortcut to start a particular saved session directly?®ƒõ@2B+ $€€˜€€€‚ÿTo run a PuTTY session saved under the name ‘mysession’, create a Windows shortcut that invokes PuTTY with a command line likeI%„A{B$ €J€˜€‚ÿ\path\name\to\putty.exe @mysession¯~2B*C1]€(‚(*C¦C‡DQuestion A.5.3: How can I start an SSH session straight from the command line?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")|S{B¦C) "€¦€€€€‚ÿQuestion A.5.3: How can I start an SSH session straight from the command line?á°*C‡D1 0€a€˜€€€ãR„ùN‰‚ÿUse the command line putty -ssh host.name. Alternatively, create a saved session that specifies the SSH protocol, and start the saved session as shown in question A.5.2.¶…¦C=E1d(Ò…(=EÀE¡IQuestion A.5.4: How do I copy and paste between PuTTY and other Windows applications?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")ƒZ‡DÀE) "€´€€€€‚ÿQuestion A.5.4: How do I copy and paste between PuTTY and other Windows applications?*ù=EêG1 0€ó€˜€€€€€‚ÿCopy and paste works similarly to the X Window System. You use the left mouse button to select text in the PuTTY window. The act of selection automatically copies the text to the clipboard: there is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact, pressing Ctrl-C will send a Ctrl-C character to the other end of your connection (just like it does the rest of the time), which may have unpleasant effects. The only thing you need to do, to copy text to the clipboard, is to select it.gBÀEQI% €…€˜€‚ÿTo paste the clipboard contents into a PuTTY window, by default you click the right mouse button. If you have a three-button mouse and are used to X applications, you can configure pasting to be done by the middle button instead, but this is not the default because most Windows users don't have a middle button at all.P,êG¡I$ €X€˜€‚ÿYou can also paste by pressing Shift-Ins.¿ŽQI`J1í‚(r†(`JìJMKQuestion A.5.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.CBB("btn_up","JI(`',`t00000163')");EB("btn_up")Œc¡IìJ) "€Æ€€€€‚ÿQuestion A.5.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.a=`JMK$ €z€˜€‚ÿThis is a new feature in version 0.52. You should upgrade.Ù¨ìJ&L1KÒ…(oˆ(&LÌLqNQuestion A.5.6: How do I use all PuTTY's features (public keys, port forwarding, SSH v2, etc.) in PSCP, PSFTP and Plink?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")¦}MKÌL) "€ú€€€€‚ÿQuestion A.5.6: How do I use all PuTTY's features (public keys, port forwarding, SSH v2, etc.) in PSCP, PSFTP and Plink?¥€&LqN% €€˜€‚ÿThe command-line tools are currently rather short of command line options to enable this sort of thing. However, you can use most of PuTTY's features if you create a PuTTY saved session, and then use the name of the saved session on the command line in place of a hostname. This works for PSCP, PSFTP and Plink (but don't expect port forwarding in the file transfer applications!).Ü«ÌLMO1þr†()MO €`Question A.5.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.CBB("btn_up","JI(`',`t00000163')");EB("btn_up")ª€qN €* "€€€€€‚ÿQuestion A.5.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.MO €qN¶‘MO€% €#€˜€‚ÿPSCP is a command-line application, not a GUI application. If you run it without arguments, it will simply print a help message and terminate.žt €`* $€è€˜€ãQÅùN‰‚ÿTo use PSCP properly, run it from a Command Prompt window. See chapter 5 in the documentation for more details.«z€ ‚1zoˆ(0) ‚ƒ‚…‰Question A.5.8: How do I use PSCP to copy a file whose name has spaces in?CBB("btn_up","JI(`',`t00000163')");EB("btn_up")xO`ƒ‚) "€ž€€€€‚ÿQuestion A.5.8: How do I use PSCP to copy a file whose name has spaces in?Ы ‚Sƒ% €W€˜€‚ÿIf PSCP is using the traditional SCP protocol, this is confusing. If you're specifying a file at the local end, you just use one set of quotes as you would normally do:R/ƒ‚¥ƒ# €^€€‚ÿpscp "local filename with spaces" user@host:Y5Sƒþƒ$ €j€˜€‚ÿpscp user@host:myfile "local filename with spaces"Ÿu¥ƒ„* $€ê€˜€€€‚ÿBut if the filename you're specifying is on the remote side, you have to use backslashes and two sets of quotes:eBþƒ…# €„€€‚ÿpscp user@host:"\"remote filename with spaces\"" local_filenamefB„h…$ €„€˜€‚ÿpscp local_filename user@host:"\"remote filename with spaces\""ï…‚†+ $€ß€˜€€€‚ÿWorse still, in a remote-to-local copy you have to specify the local file name explicitly, otherwise PSCP will complain that they don't match (unless you specified the -unsafe option). The following command will give an error message:F#h…Ȇ# €F€€‚ÿc:\>pscp user@host:"\"oo er\"" .b?‚†*‡# €~€€‚ÿwarning: remote host tried to write to a file called 'oo er'Z6Ȇ„‡$ €l€˜€‚ÿ when we requested a file called '"oo er"'.`<*‡ä‡$ €x€˜€‚ÿInstead, you need to specify the local file name in full:M)„‡1ˆ$ €R€˜€‚ÿc:\>pscp user@host:"\"oo er\"" "oo er"ͨä‡þˆ% €Q€˜€‚ÿIf PSCP is using the newer SFTP protocol, none of this is a problem, and all filenames with spaces in are specified using a single pair of quotes in the obvious way:B1ˆ@‰# €>€€‚ÿpscp "local file" user@host:E!þˆ…‰$ €B€˜€‚ÿpscp user@host:"remote file" .}L@‰Š1ÿ )@ƒ)Šÿÿÿÿ ÅSection A.6: TroubleshootingCBB("btn_up","JI(`',`t00000137')");EB("btn_up")J!…‰LŠ) "€B€€€€‚ÿSection A.6: TroubleshootingvGŠŠ/ .€Ž€ã{„ùN€€€‰‚ÿQuestion A.6.1: Why do I see ‘Incorrect MAC received on packet’?Œ]LŠN‹/ .€º€ã|„ùN€€€‰‚ÿQuestion A.6.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?žoŠì‹/ .€Þ€ã}„ùN€€€‰‚ÿQuestion A.6.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.€KN‹lŒ5 :€–€ã~„ùN€€€€€‰‚ÿQuestion A.6.4: Plink on Windows 95 says it can't find WS2_32.DLL.—hì‹/ .€Ð€ã„ùN€€€‰‚ÿQuestion A.6.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.™jlŒœ/ .€Ô€ã€„ùN€€€‰‚ÿQuestion A.6.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.šk6Ž/ .€Ö€ã„ùN€€€‰‚ÿQuestion A.6.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.qBœ§Ž/ .€„€ã­„ùN€€€‰‚ÿSection A.6.8: PSFTP transfers files much slower than PSCP.Ÿp6ŽF/ .€à€ã¤„ùN€€€‰‚ÿQuestion A.6.9: When I run full-colour applications, I see areas of black space where colour ought to be.}N§ŽÃ/ .€œ€ã¥„ùN€€€‰‚ÿQuestion A.6.10: When I change some terminal settings, nothing happens.zKFIÀ/ .€–€ã¦„ùN€€€‰‚ÿQuestion A.6ÃIÀ…‰.11: I can't type characters that require the AltGr key.Œ]ÃÕÀ/ .€º€ã§„ùN€€€‰‚ÿQuestion A.6.12: My PuTTY sessions unexpectedly close after they are idle for a while.¦wIÀ{Á/ .€î€ã¨„ùN€€€‰‚ÿQuestion A.6.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.”_ÕÀÂ5 :€¾€ã©„ùN€€€€€‰‚ÿQuestion A.6.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.–a{Á¥Â5 :€Â€ãª„ùN€€€€€‰‚ÿQuestion A.6.15: When I cat a binary file, my window title changes to a nonsense string.‰ZÂ.Ã/ .€´€ã«„ùN€€€‰‚ÿQuestion A.6.16: My keyboard stops working once PuTTY displays the password prompt.—h¥ÂÅÃ/ .€Ð€ã¬„ùN€€€‰‚ÿQuestion A.6.17: One or more function keys don't do what I expected in a server-side application.£t.ÃhÄ/ .€è€ãØ„ùN€€€‰‚ÿQuestion A.6.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.¥vÅà Å/ .€ì€ãÏ„ùN€€€‰‚ÿQuestion A.6.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?¡phÄ®Å1<0)¹‡)®ÅÆêÊQuestion A.6.1: Why do I see ‘Incorrect MAC received on packet’?CBB("btn_up","JI(`',`t00000172')");EB("btn_up")nE ÅÆ) "€Š€€€€‚ÿQuestion A.6.1: Why do I see ‘Incorrect MAC received on packet’?€U®ÅœÇ+ $€«€˜€€€‚ÿThis is due to a bug in old SSH 2 servers distributed by ssh.com. Version 2.3.0 and below of their SSH 2 server constructs Message Authentication Codes in the wrong way, and expects the client to construct them in the same wrong way. PuTTY constructs the MACs correctly by default, and hence these old servers will fail to work with it.AÆÝÈ% €9€˜€‚ÿIf you are using PuTTY version 0.52 or better, this should work automatically: PuTTY should detect the buggy servers from their version number announcement, and automatically start to construct its MACs in the same incorrect manner as they do, so it will be able to work with them.;œÇÊ% €-€˜€‚ÿIf you are using PuTTY version 0.51 or below, you can enable the workaround by going to the SSH panel and ticking the box labelled ‘Imitate SSH 2 MAC bug’. It's possible that you might have to do this with 0.52 as well, if a buggy server exists that PuTTY doesn't know about.Ò­ÝÈêÊ% €[€˜€‚ÿIn this context MAC stands for Message Authentication Code. It's a cryptographic term, and it has nothing at all to do with Ethernet MAC (Media Access Control) addresses.·†Ê¡Ë1“@ƒ)¨Š) ¡Ë%Ì4ÏQuestion A.6.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?CBB("btn_up","JI(`',`t00000172')");EB("btn_up")„[êÊ%Ì) "€¶€€€€‚ÿQuestion A.6.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?Û¶¡ËÍ% €m€˜€‚ÿThis happens because PSCP was expecting to see data from the server that was part of the PSCP protocol exchange, and instead it saw data that it couldn't make any sense of at all.c2%ÌcÎ1 0€e€˜€€€€€‚ÿThis almost always happens because the startup scripts in your account on the server machine are generating output. This is impossible for PSCP, or any other SCP client, to work around. You should never use startup files (.bashrc, .cshrc and so on) which generate output in non-interactive sessions.ѬÍ4Ï% €Y€˜€‚ÿThis is not actually a PuTTY problem. If PSCP fails in this way, then all other SCP clients are likely to fail in exactly the same way. The problem is at the server end.ɘcÎ 1"¹‡)ž*! ¢.Question A.6.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")4Ï 4Ï–m4Ï¢) "€Ú€€€€‚ÿQuestion A.6.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal._; $ €v€˜€‚ÿThat isn't how you're supposed to use the Colours panel.-ö¢.7 <€í€˜€€€€€€€‚ÿDuring the course of a session, PuTTY potentially uses all the colours listed in the Colours panel. It's not a question of using only one of them and you choosing which one; PuTTY will use them all. The purpose of the Colours panel is to let you adjust the appearance of all the colours. So to change the colour of the cursor, for example, you would select ‘Cursor Colour’, press the ‘Modify’ button, and select a new colour from the dialog box that appeared. Similarly, if you want your session to appear in green, you should select ‘Default Foreground’ and press ‘Modify’. Clicking on ‘ANSI Green’ won't turn your session green; it will only allow you to adjust the shade of green used when PuTTY is instructed by the server to display green text.£rÑ1¹¨Š)˜*"ÑIŠQuestion A.6.4: Plink on Windows 95 says it can't find WS2_32.DLL.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")xI.I/ .€’€€€€€€‚ÿQuestion A.6.4: Plink on Windows 95 says it can't find WS2_32.DLL.ëÑY% €×€˜€‚ÿPlink requires the extended Windows network library, WinSock version 2. This is installed as standard on Windows 98 and above, and on Windows NT, and even on later versions of Windows 95; but early Win95 installations don't have it.[IØ$ €¶€˜€‚ÿIn order to use Plink on these systems, you will need to download the WinSock 2 upgrade:iFYA# €Œ€€‚ÿhttp://www.microsoft.com/windows95/downloads/contents/wuadmintools/I%ØŠ$ €J€˜€‚ÿ s_wunetworkingtools/w95sockets2/‘AL1ñž**#LÛ= Question A.6.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")fŠÛ) "€Ì€€€€‚ÿQuestion A.6.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.ÙLß + $€³€˜€€€‚ÿThis is a bug in all versions of PuTTY up to and including 0.51. SSH v2 servers from ssh.com will require the key exchange to be repeated one hour after the start of the connection, and PuTTY will get this wrong.^:Û= $ €t€˜€‚ÿUpgrade to version 0.52 and the problem should go away.Ä“ß  1"˜*€*$ ’ /@Question A.6.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")‘h= ’ ) "€Ð€€€€‚ÿQuestion A.6.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.¦ 8 % €€˜€‚ÿIf this happens just while the connection is starting up, this often indicates that for some reason the client and server have failed to establish a session encryption key. Somehow, they have performed calculations that should have given each of them the same key, but have ended up with different keys; so data encrypted by one and decrypted by the other looks like random garbage.ìÁ’ $+ $€ƒ€˜€€€‚ÿThis causes an ‘out of memory’ error because the first encrypted data PuTTY expects to see is the length of an SSH message. Normally this will be something well under 100 bytes. If the decryption has failed, PuTTY will see a completely random length in the region of two gigabytes, and will try to allocate enough memory to store this non-existent message. This will immediately lead to it thinking it doesn't have enough memory, and panicking.ÿÚ8 /@% €µ€˜€‚ÿIf this happens to you, it is quite likely to still be a PuTTY bug and you should report it (although it might be a bug in your SSH server instead); but it doesn't necessarily mean y$/@= ou've actually run out of memory.Å”$ô@1Ä*„*%ô@†A¸EQuestion A.6.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")’i/@†A) "€Ò€€€€‚ÿQuestion A.6.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.£xô@)C+ $€ñ€˜€ã€„ùN‰‚ÿThis is almost always caused by your login scripts on the server generating output. PSCP or PSFTP will receive that output when they were expecting to see the start of a file transfer protocol, and they will attempt to interpret the output as file-transfer protocol. This will usually lead to an ‘out of memory’ error for much the same reasons as given in question A.6.6.-ü†AVD1 0€ù€˜€€€€€‚ÿThis is a setup problem in your account on your server, not a PSCP/PSFTP bug. Your login scripts should never generate output during non-interactive sessions; secure file transfer is not the only form of remote access that will break if they do.b%)C¸E= H€K€˜€€€€€€€€€‚ÿOn Unix, a simple fix is to ensure that all the parts of your login script that might generate output are in .profile (if you use a Bourne shell derivative) or .login (if you use a C shell). Putting them in more general files such as .bashrc or .cshrc is liable to lead to problems.œkVDTF1€*Î…*&TF½FnHSection A.6.8: PSFTP transfers files much slower than PSCP.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")i@¸E½F) "€€€€€€‚ÿSection A.6.8: PSFTP transfers files much slower than PSCP.±ŒTFnH% €€˜€‚ÿWe believe this is because the SFTP and SSH2 protocols are less efficient at bulk data transfer than SCP and SSH1, because every block of data transferred requires an acknowledgment from the far end. It would in theory be possible to queue several blocks of data to get round this speed problem, but as yet we haven't done the coding. If you really want this fixed, feel free to offer to help.Ê™½F8I1§„*!‡*'8IÏIßJQuestion A.6.9: When I run full-colour applications, I see areas of black space where colour ought to be.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")—nnHÏI) "€Ü€€€€‚ÿQuestion A.6.9: When I run full-colour applications, I see areas of black space where colour ought to be.å8IßJ+ $€Ë€˜€ã¥„ùN‰‚ÿYou almost certainly need to enable the ‘Use background colour to erase screen’ setting in the Terminal panel. Note that if you do this in mid-session, it won't take effect until you reset the terminal (see question A.6.10).¨wÏI‡K1ýÎ…*¥‰*(‡KüK„NQuestion A.6.10: When I change some terminal settings, nothing happens.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")uLßJüK) "€˜€€€€‚ÿQuestion A.6.10: When I change some terminal settings, nothing happens.¤y‡K M+ $€ó€˜€€€‚ÿSome of the terminal options (notably Auto Wrap and background-colour screen erase) actually represent the default setting, rather than the currently active setting. The server can send sequences that modify these options in mid-session, but when the terminal is reset (by server action, or by you choosing ‘Reset Terminal’ from the System menu) the defaults are restored.ä¿üK„N% €€˜€‚ÿIf you want to change one of these options in the middle of a session, you will find that the change does not immediately take effect. It will only take effect once you reset the terminal.¥t M)O1â!‡*+))O›O€Question A.6.11: I can't type characters that require the AltGr key.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")rI„N›O) "€’€€€€‚ÿQuestion A.6.11: I can't type characters that require the AltGr key.pL)O€$ €˜€˜€‚ÿIn PuTTY version 0.51, the AltGr key was broken. Upgrade to vers›O€„Nion 0.52.·†›O΀1¥‰*p+*΀Rè„Question A.6.12: My PuTTY sessions unexpectedly close after they are idle for a while.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")„[€R) "€¶€€€€‚ÿQuestion A.6.12: My PuTTY sessions unexpectedly close after they are idle for a while.C΀•‚% €=€˜€‚ÿSome types of firewall, and almost any router doing Network Address Translation (NAT, also known as IP masquerading), will forget about a connection through them if the connection does nothing for too long. This will cause the connection to be rudely cut off when contact is resumed.óR³ƒ+ $€ç€˜€€€‚ÿYou can try to combat this by telling PuTTY to send keepalives: packets of data which have no effect on the actual session, but which reassure the router or firewall that the network connection is still active and worth remembering about.5•‚è„1 0€ €˜€€€ãêøÂk‰‚ÿKeepalives don't solve everything, unfortunately; although they cause greater robustness against this sort of router, they can also cause a loss of robustness against network dropouts. See section 4.13.3 in the documentation for more discussion of this.Ñ ³ƒ¹…1Ý+¼++¹…W†–ŠQuestion A.6.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")žuè„W†) "€ê€€€€‚ÿQuestion A.6.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.ëƹ…B‡% €€˜€‚ÿThis is a Windows problem, not a PuTTY problem. The timeout value can't be set on per application or per session basis. To increase the TCP timeout globally, you need to tinker with the Registry.fBW†¨‡$ €„€˜€‚ÿOn Windows 95, 98 or ME, the registry key you need to change is_<B‡ˆ# €x€€‚ÿHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\=¨‡Dˆ$ €2€˜€‚ÿ MSTCP\MaxDataRetriesb>ˆ¦ˆ$ €|€˜€‚ÿ(it must be of type DWORD in Win95, or String in Win98/ME).Q-Dˆ÷ˆ$ €Z€˜€‚ÿOn Windows NT or 2000, the registry key isa>¦ˆX‰# €|€€‚ÿHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\M)÷ˆ¥‰$ €R€˜€‚ÿ Parameters\TcpMaxDataRetransmissionsD X‰é‰$ €@€˜€‚ÿand it must be of type DWORD.­ˆ¥‰–Š% €€˜€‚ÿSet the key's value to something like 10. This will cause Windows to try harder to keep connections alive instead of abandoning them.·†é‰M‹1Ýp+ð +,M‹Ù‹*Question A.6.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")Œ]–ŠÙ‹/ .€º€€€€€€‚ÿQuestion A.6.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.;M‹Œ$ €.€˜€‚ÿDon't do that, then.×Ù‹Ž+ $€¯€˜€€€‚ÿThis is designed behaviour; when PuTTY receives the character Control-E from the remote server, it interprets it as a request to identify itself, and so it sends back the string ‘PuTTY’ as if that string had been entered at the keyboard. Control-E should only be sent by programs that are prepared to deal with the response. Writing a binary file to your terminal is likely to output many Control-E characters, and cause this behaviour. Don't do it. It's a bad plan.éŒ*+ $€Ó€˜€ã•Ü.ó‰‚ÿTo mitigate the effects, you could configure the answerback string to be empty (see section 4.3.6); but writing binary files to your terminal is likely to cause various other unpleasant behaviour, so this is only a small remedy.¹ˆŽ À1¾¼+F‚+- ÀšÀÊÂQuestion A.6.15: When I cat a binary file, my window title changes to a nonsense string.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")* À*Ž_*šÀ/ .€¾€€€€€€‚ÿQuestion A.6.15: When I cat a binary file, my window title changes to a nonsense string.; ÀÕÀ$ €.€˜€‚ÿDon't do that, then.õКÀÊÂ% €¡€˜€‚ÿIt is designed behaviour that PuTTY should have the ability to adjust the window title on instructions from the server. Normally the control sequence that does this should only be sent deliberately, by programs that know what they are doing and intend to put meaningful text in the window title. Writing a binary file to your terminal runs the risk of sending the same control sequence by accident, and cause unexpected changes in the window title. Don't do it.´ƒÕÀ~Ã18ð +„+.~ÃÿöÅQuestion A.6.16: My keyboard stops working once PuTTY displays the password prompt.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")XÊÂÿÃ) "€°€€€€‚ÿQuestion A.6.16: My keyboard stops working once PuTTY displays the password prompt.¦~Ã¥Ä% €€˜€‚ÿNo, it doesn't. PuTTY just doesn't display the password you type, so that someone looking at your screen can't see what it is.æÿöÅ+ $€Í€˜€€€‚ÿUnlike the Windows login prompts, PuTTY doesn't display the password as a row of asterisks either. This is so that someone looking at your screen can't even tell how long your password is, which might be valuable information.‘¥ÄxÆ1‘F‚+„Š+/xÆÇ ÎQuestion A.6.17: One or more function keys don't do what I expected in a server-side application.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")f¶ÅÇ) "€Ì€€€€‚ÿQuestion A.6.17: One or more function keys don't do what I expected in a server-side application.©„xÆ°Ç% € €˜€‚ÿIf you've already tried all the relevant options in the PuTTY Keyboard panel, you may need to mail the PuTTY maintainers and ask.@ÇðÈ+ $€+€˜€€€‚ÿIt is not usually helpful just to tell us which application, which server operating system, and which key isn't working; in order to replicate the problem we would need to have a copy of every operating system, and every application, that anyone has ever complained about.“h°ÇƒÊ+ $€Ñ€˜€€€‚ÿPuTTY responds to function key presses by sending a sequence of control characters to the server. If a function key isn't doing what you expect, it's likely that the character sequence your application is expecting to receive is not the same as the one PuTTY is sending. Therefore what we really need to know is what sequence the application is expecting.À}ðÈCÍC T€û€˜€€€€€€€€€€€‚ÿThe simplest way to investigate this is to find some other terminal environment, in which that function key does work; and then investigate what sequence the function key is sending in that situation. One reasonably easy way to do this on a Unix system is to type the command cat, and then press the function key. This is likely to produce output of the form ^[[11~. You can also do this in PuTTY, to find out what sequence the function key is producing in that. Then you can mail the PuTTY maintainers and tell us ‘I wanted the F1 key to send ^[[11~, but instead it's sending ^[OP, can this be done?’, or something similar.Æ›ƒÊ Î+ $€7€˜€ã:ŒùN‰‚ÿYou should still read the Feedback page on the PuTTY website (also provided as appendix B in the manual), and follow the guidelines contained in that.ÎCÍ×Î1É„+Ú,0×ÎrϬQuestion A.6.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.CBB("btn_up","JI(`',`t00000172')");EB("btn_up")›r ÎrÏ) "€ä€€€€‚ÿQuestion A.6.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.ߺ×Î]% €u€˜€‚ÿThere is a known problem when OpenSSH has been built against an incorrect version of OpenSSL; the quick rÏ] Îworkaround is to configure PuTTY to use SSH protocol 2 and the Blowfish cipher.lHrÏÉ$ €€˜€‚ÿFor more details and OpenSSH patches, see bug 138 in the OpenSSH BTS.ߺ]¨% €u€˜€‚ÿThis is not a PuTTY-specific problem; if you try to connect with another client you'll likely have similar problems. (Although PuTTY's default cipher differs from many other clients.)kDÉ' €ˆ€˜€€‚ÿOpenSSH 3.1p1: configurations known to be broken (and symptoms):²„¨Å. *€ €T˜‘€8‚€ƒ€‚ÿ•SSH 2 with AES cipher (PuTTY says "Assertion failed! Expression: (len & 15) == 0" in sshaes.c, or "Out of memory", or crashes)rE7- *€Š€T˜‘€8‚€ƒ€‚ÿ•SSH 2 with 3DES (PuTTY says "Incorrect MAC received on packet")vIÅ­- *€’€T˜‘€8‚€ƒ€‚ÿ•SSH 1 with Blowfish (PuTTY says "Incorrect CRC received on packet")B7ï- *€*€T˜‘€8‚€ƒ€‚ÿ•SSH 1 with 3DESèÀ­×( €€˜€€‚ÿOpenSSH 3.4p1: as of 3.4p1, only the problem with SSH 1 and Blowfish remains. Rebuild your server, apply the patch linked to from bug 138 above, or use another cipher (e.g., 3DES) instead.Õ­ï¬( €[€˜€€‚ÿOther versions: we occasionally get reports of the same symptom and workarounds with older versions of OpenSSH, although it's not clear the underlying cause is the same.П×|1z„Š+Û,1|öQuestion A.6.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?CBB("btn_up","JI(`',`t00000172')");EB("btn_up")t¬) "€è€€€€‚ÿQuestion A.6.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?"ý|;% €û€˜€‚ÿIt's likely that you've generated an SSH protocol 2 key with PuTTYgen, but you're trying to use it in an SSH 1 connection. SSH1 and SSH2 keys have different formats, and (at least in 0.52) PuTTY's reporting of a key in the wrong format isn't optimal.»ö+ $€!€˜€ãÕƒùN‰‚ÿTo connect using SSH 2 to a server that supports both versions, you need to change the configuration from the default (see question A.1.1).€O;v 1ŠÚ,z,2v ÿÿÿÿ Section A.7: Security questionsCBB("btn_up","JI(`',`t00000137')");EB("btn_up")M$öà ) "€H€€€€‚ÿSection A.7: Security questions„Uv G / .€ª€ãÑ„ùN€€€‰‚ÿQuestion A.7.1: Is it safe for me to download PuTTY and use it on a public PC?…Và Ì / .€¬€ãÒ„ùN€€€‰‚ÿQuestion A.7.2: What does PuTTY leave on a system? How can I clean up after it?˜iG d / .€Ò€ãÓ„ùN€€€‰‚ÿQuestion A.7.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?œgÌ  5 :€Î€ãÔ„ùN€€€€€‰‚ÿQuestion A.7.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?¯~d ¯ 1(Û,€,3¯ +  @Question A.7.1: Is it safe for me to download PuTTY and use it on a public PC?CBB("btn_up","JI(`',`t00000192')");EB("btn_up")|S + ) "€¦€€€€‚ÿQuestion A.7.1: Is it safe for me to download PuTTY and use it on a public PC?³ˆ¯ Þ+ $€€˜€€€‚ÿIt depends on whether you trust that PC. If you don't trust the public PC, don't use PuTTY on it, and don't use any other software you plan to type passwords into either. It might be watching your keystrokes, or it might tamper with the PuTTY binary you download. There is no program safe enough that you can run it on an actively malicious PC and get away with typing passwords into it.ùÔ+  @% €©€˜€‚ÿIf you do trust the PC, then it's probably OK to use PuTTY on it (but if you don't trust the network, then the PuTTY download might be tampered with, so it would be better to carry PuTTY with you on a floppy).Þ @ °Þ¼@1Éz,o,4¼@9A…BQuestion A.7.2: What does PuTTY leave on a system? How can I clean up after it?CBB("btn_up","JI(`',`t00000192')");EB("btn_up")}T @9A) "€¨€€€€‚ÿQuestion A.7.2: What does PuTTY leave on a system? How can I clean up after it?L¼@…B1 0€7€˜€ãO„ùN‰€€‚ÿPuTTY will leave some Registry entries, and a random seed file, on the PC (see question A.4.2). If you are using PuTTY on a public PC, or somebody else's PC, you might want to clean these up when you leave. You can do that automatically, by running the command putty -cleanup.Ã’9AHC1t€,j„,5HCØC¼FQuestion A.7.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?CBB("btn_up","JI(`',`t00000192')");EB("btn_up")g…BØC) "€Î€€€€‚ÿQuestion A.7.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?]2HC5E+ $€e€˜€€€‚ÿDSA has a major weakness if badly implemented: it relies on a random number generator to far too great an extent. If the random number generator produces a number an attacker can predict, the DSA private key is exposed - meaning that the attacker can log in as you on all systems that accept that key.‡bØC¼F% €Å€˜€‚ÿThe PuTTY policy changed because the developers were informed of ways to implement DSA which do not suffer nearly as badly from this weakness, and indeed which don't need to rely on random numbers at all. For this reason we now believe PuTTY's DSA implementation is probably OK. However, if you have the choice, we still recommend you use RSA instead.¿Ž5E{G1:o,J†,6{GHµIQuestion A.7.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?CBB("btn_up","JI(`',`t00000192')");EB("btn_up")”e¼FH/ .€Ê€€€€€€‚ÿQuestion A.7.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?¦{{GµI+ $€÷€˜€€€‚ÿUnfortunately not. The VirtualLock() function in the Windows API doesn't do a proper job: it may prevent small pieces of a process's memory from being paged to disk while the process is running, but it doesn't stop the process's memory as a whole from being swapped completely out to disk when the process is long-term inactive. And Pageant spends most of its time inactive.†UH;J1(j„,/ˆ,7;JÿÿÿÿcMSection A.8: Administrative questionsCBB("btn_up","JI(`',`t00000137')");EB("btn_up")S*µIŽJ) "€T€€€€‚ÿSection A.8: Administrative questions|M;J K/ .€š€ãÖ„ùN€€€‰‚ÿQuestion A.8.1: Would you like me to register you a nicer domain name?}NŽJ‡K/ .€œ€ãׄùN€€€‰‚ÿQuestion A.8.2: Would you like free web hosting for the PuTTY web site?n? KõK/ .€~€ã<ŒùN€€€‰‚ÿQuestion A.8.3: Why don't you move PuTTY to SourceForge?{L‡KpL/ .€˜€ã3ŒùN€€€‰‚ÿQuestion A.8.4: Why can't I subscribe to the putty-bugs mailing list?‡XõK÷L/ .€°€ã4ŒùN€€€‰‚ÿQuestion A.8.5: If putty-bugs isn't a general-subscription mailing list, what is?l=pLcM