?_Nţ˙˙˙˙}/&;)L4˙˙^˙˙˙6ՁƒᲳƒŮ âł„đ… (~Ś„ź 0tW…:‰ěe|…á‚y2\†V &lφ4ƒ!úľŰ† ‰"1E˝ŠĄ†!¨;‹ ‡ F{ęˆsĹv• ÄŰś,‚Ęh–Jg v– č8– ´—( Â<ű—ó$ť‰Ů˘ˆ† ŘĆsŚ -Ľ™Ś‚dŢ娓8&°!‰5Äłb!wŃJśoĹsşú„G6˝ď‚ ‚ożżÚW݌Á/Ę6ĘÄل×TÇe y÷OÉ}ÚfůĚč L%ĽÍdŒ ]úÍšŠ /PYĎńŘdbĎ.çŃ7…÷ů0Ԟ…Řk—Ő‘EšÖπ„@ĎŘ;Šžţ^ŮŤk ZÜp>ŠcÜ% óWâÜ„.Ŕŕ€śÖ㒄VS搈 š§žč~ˆžżí$„ŤßŽď:@ËŢďX•Ü.óm‡ ˝TŻó „ő—†'wúűĄ‡ÝéŕýĐ Y ˆ-ЄůN݈-фůN÷.҄ůNC.ӄůNw.ԄůN€.ՄůNż.քůN>ˆ.ׄůN”/؄ůNC…-ú„ůNj‡ű„ůNfˆü„ůNxý„ůN›ţ„ůNż˙„ůN.‚…ůNL‰…ůN/…ůNş„…ůN2†°ŠůNę0ąŠůN€0˛ŠůNԅ0łŠůN܆0´ŠůNî‡0ľŠůNQ‰0śŠůN1ˇŠůNy1¸ŠůNá1šŠůN˝0ۊůN‰1܊ůNš 2݊ůNć‡2ފůN§3ߊůN3ŕŠůNa 3áŠůNxƒ3âŠůNđ…3ăŠůN"ˆ3äŠůNü1‹ůN„ˆ33ŒůNł/4ŒůNR /5ŒůN\‚/6ŒůN˃/7ŒůNƆ/8ŒůNŚˆ/9ŒůN0:ŒůN00;ŒůNœ0<ŒůN•/xÄůNyÄůNR…zÄůNwˆ{ÄůN(|ÄůNk}ÄůNŤ~ÄůN+ÄůNœ€ÄůNX ÄůNeŁÄůNĽƒ¤ÄůNŻ†ĽÄůN‰ŚÄůNߧÄůNŒ‹¨ÄůNŢŠÄůN9ŞÄůNŤÄůNfŹÄůNiÎÄůNá†ĎÄůNĐÄůN9ŃÄůN}ŇÄůN)ÓÄůNA ÔÄůN˙ŐÄůNëƒÖÄůNP†_˙˙×ÄůNDƒůÄůNúÄůN7űÄůNžüÄůN—ýÄůN €ţÄůNŚˆ˙ÄůN‚€ ĹůN}ˆ ĹůNű€ ĹůNˆ$ĹůN&%ĹůNí€&ĹůN!'ĹůNş(ĹůN)ĹůNÁ*ĹůN7 +ĹůN,ĹůN…‚-ĹůNƀ OĹůNPĹůNöŠQĹůNIRĹůN8SĹůNă‚TĹůNr†UĹůNVĹůNîWĹůNä‚XĹůNzĹůN@†{ĹůNgˆ|ĹůNß}ĹůNą~ĹůNňĹůNb€ĹůNPĹůNW‚ĹůN&„ƒĹůNźƒĽĹůNRˆŚĹůN,§ĹůNɨĹůN‹‚ŠĹůNƒŞĹůNą…ŤĹůNĐŹĹůNş­ĹůNW ŽĹůNš„ĐĹůN_‚ŃĹůNA„ŇĹůN…†ÓĹůN†ˆÔĹůNPŐĹůNŽÖĹůNĎ×ĹůNĄŘĹůN…ŮĹůNHűĹůN}üĹůNě‚ýĹůNωţĹůN‹˙ĹůNuĆůNú„ĆůN+‰ĆůNŽŠĆůNBĆůNŸî4ŐTŠ , ŰTáˆł—U´ĺUZ‚"ďÜ7Y?†Č6çYr‡ﴕZ ‰ ĽŮZƒ&áÝ\ÄÚŮI_N˘ ˛`Rdî:a$䀅aA€"„QÜcp‹!80Ťf/…#ęřÂkś‡ eHmH†"*͈sć‚ ĽŕĚsӄ E@Áv<#z?Öw­°x˛zl{Ţ} ՂŢ}Č ô×ÄůN žľhArialCourier NewTimes New Roman/&;)F24˙˙'˙˙˙˙CVSPATHPSCPPSFTPPlinkSecure iXplorerWildcards WinCVS$batch files(console window,recursive4scripts8statistics<timestamp@MD– ă‚Rˆż8š„›&„źƒé _‰ă‚żň_‰ąß]Tl! Ę+@  #CB("btn_about","&About","About()") CB("btn_up","&Up","Contents()")BrowseButtons()PuTTY User Manual°This manual is copyright 2001-2004 Simon Tatham. All rights reserved. You may distribute this documentation under the MIT licence. See appendix C for the licence text in full.-ƒ$ƒ˙˙˙˙ 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-2004 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€ăRĹů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€ă{ƒů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.c4c/ .€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.[8NjnŒ# €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 linePQ+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 eR… / „ @FSection 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.óÂ= <@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.2). (Pressing Shift-Ins, or selecting ‘Paste’ from the Ctrl+right-click context menu, have the same effect.) 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 formatti= <@§ng. There is nothing PuTTY can do about this.)ˇ†= óA1 0€ €˜€ăý@‰€€‚˙If you 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.5.) If you triple-click, or triple-click and drag, then PuTTY will select a whole line or sequence of lines.j?<@]C+ $€€˜€ă ˇ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.4 for details.)†aóAăD% €Ă€˜€‚˙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.],]C@F1 0€Y€˜€ăâł„‰ă.Ŕŕ‰‚˙It's possible for the server to ask to handle mouse clicks in the PuTTY window itself. If this happens, the mouse cursor will turn into an arrow, and copy and paste will only work if you hold down Shift. See section 4.6.2 and section 4.11.3 for details of this feature and how to configure it.‰XăDÉF1Ăwˆ ÉFGŒJSection 3.1.2: Scrolling the screen backCBB("btn_up","JI(`',`t00000010')");EB("btn_up")V-@FG) "€Z€€€€‚˙Section 3.1.2: Scrolling the screen backkFÉFŠH% €€˜€‚˙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.$˙GŽI% €˙€˜€‚˙As well as using the scrollbar, you can also page the scrollback up and down by pressing Shift-PgUp and Shift-PgDn. You can scroll a line at a time using Ctrl-PgUp and Ctrl-PgDn. These are still available if you configure the scrollbar to be invisible.ŢłŠHŒJ+ $€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ŽI K1fR…( KWK}€Section 3.1.3: The System menuCBB("btn_up","JI(`',`t00000010')");EB("btn_up")L#ŒJWK) "€F€€€€‚˙Section 3.1.3: The System menuń KmL% €ă€˜€‚˙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.ˇ’WK$M% €%€˜€‚˙PuTTY's system menu contains extra program features in addition to the Windows standard options. These extra menu commands are described below.ž™mLâM% €3€˜€‚˙(These options are also available in a context menu brought up by holding Ctrl and clicking with the right mouse button anywhere in the PuTTY window.)Z+$M…:†/ .€|€ăŠÄůN€€€‰‚˙Section 3.7.1: Starting a session from the command lineMͅ‡†/ .€<€ăŞÄůN€€€‰‚˙Section 3.7.2: -cleanupb3:†é†/ .€f€ăŤÄůN€€€‰‚˙Section 3.7.3: Standard command-line options˜g‡†‡1Éލ‡ć‡JŒSection 3.7.1: Starting a session from the command lineCBB("btn_up","JI(`',`t00000026')");EB("btn_up")e<é†ć‡) "€x€€€€‚˙Section 3.7.1: Starting a session from the command line…a‡kˆ$ €Â€˜€‚˙These options allow you to bypass the configuration window and launch straight into a session.]3ć‡Ȉ* $€f€˜€€€‚˙To start a connection to a server called host:^:kˆ&‰$ €t€˜€‚˙putty.exe [-ssh | -telnet | -rlogin | -raw] [user@]host&ďȈLŠ7 <€ß€˜€ă}§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).Ŕ›&‰ ‹% €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):F"LŠR‹$ €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-9fŒďSection 3.7.2: -cleanupCBB("btn_up","JI(`',`t00000026')");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ōDƒ|Ž֎MĆSection 3.7.3: Standard command-line optionsCBB("btn_up","JI(`',`t00000026')");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 t֎Ŕďhat tool.f4֎}Ŕ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/}ŔsÁ2 4€^€ăĎÄůN€€€€‰‚˙Section 3.7.3.3: -v: increase verbosityc1ÁÖÁ2 4€b€ăĐÄůN€€€€‰‚˙Section 3.7.3.4: -l: specify a login nameCsÁWÂ> L€†€ăŃÄůN€€€€€€€€‰‚˙Section 3.7.3.5: -L, -R and -D: set up port forwardingszHÖÁŃÂ2 4€€ăŇÄůN€€€€‰‚˙Section 3.7.3.6: -m: read a remote command or script from a filed2WÂ5Ă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>5Ă Ä8 @€|€ăŐÄůN€€€€€€‰‚˙Section 3.7.3.9: -A and -a: control agent forwardingu=—Ă‚Ä8 @€z€ăÖÄůN€€€€€€‰‚˙Section 3.7.3.10: -X and -x: control X11 forwardingI ÄĹ8 @€’€ăĹůN€€€€€€‰‚˙Section 3.7.3.11: -t and -T: control pseudo-terminal allocationb0‚ÄeĹ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 versionj8eĹMĆ2 4€p€ăűÄůN€€€€‰‚˙Section 3.7.3.14: -i: specify an SSH private key\ăĹÚĆ1žfá†ÚĆ8ÇxËSection 3.7.3.1: -load: load a saved sessionCBB("btn_up","JI(`',`t00000029')");EB("btn_up")^2MĆ8Ç, (€d€€€€€‚˙Section 3.7.3.1: -load: load a saved session+ÚĆcČ+ $€€˜€€€‚˙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).lH8ÇĎČ$ €€˜€‚˙You need double quotes around the session name if it contains spaces.ź—cČ‹É% €/€˜€‚˙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"Ÿb‹ÉxË= 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 @ sign must be the very first thing on the command line. This form of the option is deprecated.)¤sŮÉĚ1¸Dƒ ĚŠĚ Section 3.7.3.2: Selecting a protocol: -ssh, -telnet, -rlogin, -rawCBB("btn_up","JI(`',`t00000029')");EB("btn_up")OxËŠĚ> 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%ŠĚyÍ0 0€J€T˜‘€8‚€ƒ€€‚˙•-ssh selects the SSH protocol.[+$ÍÔÍ0 0€V€T˜‘€8‚€ƒ€€‚˙•-telnet selects the Telnet protocol.[+yÍ/Î0 0€V€T˜‘€8‚€ƒ€€‚˙•-rlogin selects the Rlogin protocol.U%ÔÍ„Î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).ˇŒ„Î + $€€˜€ă-Ľ™Ś‰‚˙These options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1).Ď xˈWĎ”1á†9!”í$Section 3.7.3.3: -v: increase verbosityCBB("btn_up","JI(`',`t00000029')");EB("btn_up")Y- í, (€Z€€€€€‚˙Section 3.7.3.3: -v: increase verbosity7 ”$+ $€€˜€€€‚˙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íŽ1Ě}"Ž zSection 3.7.3.4: -l: specify a login nameCBB("btn_up","JI(`',`t00000029')");EB("btn_up")[/$ , (€^€€€€€‚˙Section 3.7.3.4: -l: specify a login nameş‰ŽĂ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.ˇŒ z+ $€€˜€ă„ő‰‚˙These options are equivalent to the username selection box in the Connection panel of the PuTTY configuration box (see section 4.13.2).˜gĂ1ă9)#‹ő Section 3.7.3.5: -L, -R and -D: set up port forwardingsCBB("btn_up","JI(`',`t00000029')");EB("btn_up")yAz‹8 @€‚€€€€€€€€€‚˙Section 3.7.3.5: -L, -R and -D: set up port forwardings Ú–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.ť‹Q+ $€!€˜€€€‚˙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:]:–Ž# €t€€‚˙putty -L 5110:popserver.example.com:110 -load mysessionX4Q$ €h€˜€‚˙plink mysession -L 5110:popserver.example.com:110]Ž“0 0€ş€˜€€€€€‚˙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\8“P $ €p€˜€‚˙plink mysession -R 5023:mytelnetserver.myhouse.org:23€\ôĐ $ €¸€˜€‚˙To specify an IP address for the listening end of the tunnel, prepend it to the argument:P,P  $ €X€˜€‚˙plink -L 127.0.0.5:23:localhost:23 myhostľŠĐ Ő + $€€˜€€€‚˙To set up SOCKS-based dynamic port forwarding on a local port, use the -D option. For this one you only have to pass the port number:D  $ €@€˜€‚˙putty -D 4096 -load mysessionkAŐ „ * $€‚€˜€ăŚÄů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.Ąp„ – 1Ÿ}A $–  5Section 3.7.3.6: -m: read a remote command or script from a fileCBB("btn_up","JI(`',`t00000029')");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 local 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 5$ €”€˜€‚˙This option is not available in the file transfer tools PSCP and PSFTP.‹ZÇŔ1#)˙%Ŕ(@ďBSection 3.7.3.7: -P: specify a port numberCBB("btn_up","JI(`',`t00000029')");EB("btn_up")\05(@, (€`€€€€€‚˙Section 3.7.3.7: Ŕ(@5-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"(@;A# €D€€‚˙putty -telnet -P 9696 host.nameF"ö@A$ €D€˜€‚˙plink -telnet -P 9696 host.nameˇŒ;A8B+ $€€˜€€€‚˙(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.)ˇŒAďB+ $€€˜€ă-Ľ™Ś‰‚˙These options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1).‰X8BxC1tA ëƒ&xCŇCěESection 3.7.3.8: -pw: specify a passwordCBB("btn_up","JI(`',`t00000029')");EB("btn_up")Z.ďBŇC, (€\€€€€€‚˙Section 3.7.3.8: -pw: specify a password+úxCýD1 0€ő€˜€€€ă{ƒů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.ďÄŇCěE+ $€‰€˜€€€‚˙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ýDF1N˙P†'FďFĎISection 3.7.3.9: -A and -a: control agent forwardingCBB("btn_up","JI(`',`t00000029')");EB("btn_up")n<ěEďF2 4€x€€€€€€€‚˙Section 3.7.3.9: -A and -a: control agent forwardingą€F G1 0€€˜€€€€€‚˙The -A option turns on SSH agent forwarding, and -a turns it off. These options are only meaningful if you are using SSH. ÓďFŞH7 <€§€˜€ă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.´‰ G^I+ $€€˜€ăĘ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ŞHĎI$ €š€˜€‚˙These options are not available in the file transfer tools PSCP and PSFTP.”c^IcJ1§ëƒˆ(cJĐJ MSection 3.7.3.10: -X and -x: control X11 forwardingCBB("btn_up","JI(`',`t00000029')");EB("btn_up")m;ĎIĐJ2 4€v€€€€€€€‚˙Section 3.7.3.10: -X and -x: control X11 forwarding˛cJ‚K1 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ĐJäK* $€p€˜€ăĽÄůN‰‚˙For information on X11 forwarding, see section 3.4.ľŠ‚K™L+ $€€˜€ă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äK M$ €š€˜€‚˙These options are not available in the file transfer tools PSCP and PSFTP. o™LŞM1•P†)ŞM#NK€Section 3.7.3.11: -t and -T: control pseudo-terminal allocationCBB("btn_up","JI(`',`t00000029')");EB("btn_up")yG M#N2 4€Ž€€€€€€€‚˙Section 3.7.3.11: -t and -T: control pseudo-terminal allocation澪M O1 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.Ś#NÎO+ $€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 OK€$ €š€˜€‚˙These optionsÎOK€ M are not available in the file transfer tools PSCP and PSFTP.‰XÎOԀ1šˆ7*Ԁ.‚Section 3.7.3.12: -C: enable compressionCBB("btn_up","JI(`',`t00000029')");EB("btn_up")Z.K€., (€\€€€€€‚˙Section 3.7.3.12: -C: enable compressionŤ€Ô€ف+ $€€˜€€€‚˙The -C option enables compression of the data sent across the network. This option is only meaningful if you are using SSH.´‰.‚+ $€€˜€ă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ف*ƒ1ž+*ƒ ƒ?…Section 3.7.3.13: -1 and -2: specify an SSH protocol versionCBB("btn_up","JI(`',`t00000029')");EB("btn_up")vD‚ ƒ2 4€ˆ€€€€€€€‚˙Section 3.7.3.13: -1 and -2: specify an SSH protocol versionē*ƒd„1 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.Ű° ƒ?…+ $€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).‘`d„Ѕ1‹7—,Ѕ2†[ˆSection 3.7.3.14: -i: specify an SSH private keyCBB("btn_up","JI(`',`t00000029')");EB("btn_up")b6?…2†, (€l€€€€€‚˙Section 3.7.3.14: -i: specify an SSH private keyőÄЅ'‡1 0€‰€˜€€€€€‚˙The -i option allows you to specify the name of a private key file in *.PPK format which PuTTY will use to authenticate with the server. This option is only meaningful if you are using SSH.sI2†š‡* $€’€˜€ă{ƒůN‰‚˙For general information on public-key authentication, see chapter 8.Á–'‡[ˆ+ $€-€˜€ă„@Ď؉‚˙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).wFš‡҈1›ž €-҈‰yÁChapter 4: Configuring PuTTYCBB("btn_up","JI(`',`Top')");EB("btn_up")J![ˆ‰) "€B€€€€‚˙Chapter 4: Configuring PuTTYeA҈‰$ €‚€˜€‚˙This chapter describes all the configuration options in PuTTY.ďʉpŠ% €•€˜€‚˙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%‰Ċ/ .€J€ăýÄůN€€€‰‚˙Section 4.1: The Session panelT%pŠ‹/ .€J€ă˘ ˛`€€€‰‚˙Section 4.2: The Logging panelU&Ċm‹/ .€L€ăţÄůN€€€‰‚˙Section 4.3: The Terminal panelU&‹‹/ .€L€ă˙ÄůN€€€‰‚˙Section 4.4: The Keyboard panelQ"m‹Œ/ .€D€ăĹůN€€€‰‚˙Section 4.5: The Bell panelU&‹hŒ/ .€L€ăĹůN€€€‰‚˙Section 4.6: The Features panelS$ŒťŒ/ .€H€ă-ĹůN€€€‰‚˙Section 4.7: The Window panelW(hŒ/ .€P€ă$ĹůN€€€‰‚˙Section 4.8: The Appearance panelV'ťŒh/ .€N€ă%ĹůN€€€‰‚˙Section 4.9: The Behaviour panelY*Á/ .€T€ă&ĹůN€€€‰‚˙Section 4.10: The Translation panelW(hŽ/ .€P€ă'ĹůN€€€‰‚˙Section 4.11: The Selection panelU&ÁmŽ/ .€L€ă(ĹůN€€€‰‚˙Section 4.12: The Colours panelX)ŽŎ/ .€R€ă)ĹůN€€€‰‚˙Section 4.13: The Connection panelS$mŽ/ .€H€ăg v–€€€‰‚˙Section 4.14: The Proxy panelT%Ŏl/ .€J€ă*ĹůN€€€‰‚˙Section 4.15: The Telnet panelT%Ŕ/ .€J€ă+ĹůN€€€‰‚˙Section 4.16: The Rlogin panelQ"lŔ/ .€D€ă,ĹůN€€€‰‚˙Section 4.17: ŔŔ[ˆThe SSH panelR#ŔoŔ/ .€F€ăXĹůN€€€‰‚˙Section 4.18: The Auth panelU&ŔÄŔ/ .€L€ăOĹůN€€€‰‚˙Section 4.19: The Tunnels panelR#oŔÁ/ .€F€ăPĹůN€€€‰‚˙Section 4.20: The Bugs panelc4ÄŔyÁ/ .€h€ăQĹůN€€€‰‚˙Section 4.21: Storing configuration in a fileNÁřÁ1A—‚.řÁDÂ9ÄSection 4.1: The Session panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")L#yÁDÂ) "€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+DÂwĂ/ .€V€ă-Ľ™Ś€€€‰‚˙Section 4.1.1: The host name sectiong8ĂŢĂ/ .€p€ă}§B€€€‰‚˙Section 4.1.2: Loading and storing saved sessions[,wĂ9Ä/ .€X€ăŤßŽď€€€‰‚˙Section 4.1.3: ‘Close Window on Exit’…TŢĂžÄ1ˆ €Ť…/žÄĹFÉSection 4.1.1: The host name sectionCBB("btn_up","JI(`',`t00000045')");EB("btn_up")R)9ÄĹ) "€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Ĺ|Ć- *€Ü€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.)”`|ĆFÉ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˛ÇŘÉ10 ‚:0ŘÉ7ĘSection 4.1.2: Loading and storing saved sessionsCBB("btn_up","JI(`',`t00000045')");EB("btn_up")_6FÉ7Ę) "€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.!ó7ĘÍ. *€ç€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. äćËÎ% €É€˜€‚˙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 Ü΍FÉgood choice for a saved session name.) Then press the ‘Save’ button. Your saved session name should now appear in the list box.ë˝ÜÎx. *€{€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.Š]xE- *€ş€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.áźEĐ% €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.a=ď1$ €z€˜€‚˙Saved sessions are stored in the Registry, at the location\8Ѝ$ €p€˜€‚˙HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions‡]1* $€ş€˜€ăQĹůN‰‚˙If you need to store them in a file, you could try the method described in section 4.21.†Uš1‹Ť…R1ší% Section 4.1.3: ‘Close Window on Exit’CBB("btn_up","JI(`',`t00000045')");EB("btn_up")S*í) "€T€€€€‚˙Section 4.1.3: ‘Close Window on Exit’gBšT% €…€˜€‚˙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.NT¤ 1Ż:,‚2¤ đ _CSection 4.2: The Logging panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")L#% đ ) "€F€€€€‚˙Section 4.2: The Logging panelŠ„¤ ™ % € €˜€‚˙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Ľx™ Ń - *€đ€T˜‘€8‚€ƒ€‚˙•‘Logging turned off completely’. This is the default option; in this mode PuTTY will not create a log file at all.˛„, ƒ. *€ €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 a text editor and hope to be able to make sense of it.ŢŃ Ą@4 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.úĆƒ›B4 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%Ą@ďB/ .€J€ăÄŰś€€€‰‚˙Section 4.2.1: ‘Log file name’pA›B_C/ .€‚€ămT$%€€€‰‚˙Section 4.2.2: ‘What to do if the log file already exists’‚QďBáC1@R’†3áC-D!JSection 4.2.1: ‘Log file name’CBB("btn_up","JI(`',`logging.main')");EB("btn_up")L#_C-D) "€F€€€€‚˙Section 4.2.1: ‘Log file name’F!áCsE% €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.č-D†F+ $€Ń€˜€€€‚˙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?sEőF0 0€~€T˜‘€8‚€ƒ€€‚˙•&Y will be replaced by the current year, as four digits.o?†FdG0 0€~€T˜‘€8‚€ƒ€€‚˙•&M will be replaced by the current month, as two digits.zJőFŢG0 0€”€T˜‘€8‚€ƒ€€‚˙•&D will be replaced by the current day of the month, as two digits.‹[dGiH0 0€ś€T˜‘€8‚€ƒ€€‚˙•&T will be replaced by the current time, as six digits (HHMMSS) with no punctuation.rBŢGŰH0 0€„€T˜‘€8‚€ƒ€€‚˙•&H will be replaced by the host name you are connecting to.ĄwiH|I* $€î€˜€€€‚˙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.ŰHÍI# €\€€‚˙log-server1.example.com-20010528-110859.datT0|I!J$ €`€˜€‚˙log-unixbox.somewhere.org-20010611-221001.datžmÍIżJ1h,‚Śˆ4żJ'K'MSection 4.2.2: ‘What to do if the log file already exists’CBB("btn_up","JI(`',`logging.main')");EB("btn_up")h?!J'K) "€~€€€€‚˙Section 4.2.2: ‘What to do if the log file already exists’ŐżJ'M+ $€Ť€˜€€€‚˙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'K§M1!’†Đ 5§MôMԁSection 4.3: The Terminal panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")M$'MôM) "€H€€€€‚˙Section 4.3: The Terminal panelŠf§M~N$ €Ě€˜€‚˙The Terminal configuration panel allows you to control the behaviour of PuTTY's terminal emulation.b3ôMŕN/ .€f€ăÝéŕý€€€‰‚˙Section 4.3.1: ‘Auto wrap mode initially on’c4~NCO/ .€h€ă€çĄ:€€€‰‚˙Section 4.3.2: ‘DEC Origin Mode initially on’^/ŕNĄO/ .€^€ă—[K€€€‰‚˙Section 4.3.3: ‘Implicit CR in every LF’l=CO€/ .€z€ăŘĆsŚ€€€‰‚˙Section 4.3.4: ‘Use background colour to eraĄO€'Mse screen’[,ĄOt€/ .€X€ăL;B:€€€‰‚˙Section 4.3.5: ‘Enable blinking text’W(€ˀ/ .€P€ă•Ü.󀀀‰‚˙Section 4.3.6: ‘Answerback to ^E’Q"t€/ .€D€ăl{Ţ}€€€‰‚˙Section 4.3.7: ‘Local echo’Y*ˀu/ .€T€ăՂŢ}€€€‰‚˙Section 4.3.8: ‘Local line editing’_0ԁ/ .€`€ăᲳƒ€€€‰‚˙Section 4.3.9: Remote-controlled printing\ua‚1Śˆ˜ 6a‚ť‚ń†Section 4.3.1: ‘Auto wrap mode initially on’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")Z1ԁť‚) "€b€€€€‚˙Section 4.3.1: ‘Auto wrap mode initially on’šva‚Uƒ$ €ě€˜€‚˙Auto wrap mode controls what happens when text printed in a PuTTY window reaches the right-hand edge of the window.Y4ť‚Ž„% €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.ĎŞUƒ}…% €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.tCŽ„ń†1 0€‡€˜€€€ă€ÄůN‰‚˙Auto wrap mode can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately.Ž]}…‡1ŢĐ ‰ 7‡ڇ]Section 4.3.2: ‘DEC Origin Mode initially on’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")[2ń†ڇ) "€d€€€€‚˙Section 4.3.2: ‘DEC Origin Mode initially on’˘~‡|ˆ$ €ü€˜€‚˙DEC Origin Mode is a minor option which controls how PuTTY interprets cursor-position control sequences sent by the server.W2ڇӉ% €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.ýŘ|ˆЊ% €ą€˜€‚˙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.óӉč‹% €ç€˜€‚˙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.uDЊ]1 0€‰€˜€€€ă€ÄůN‰‚˙DEC Origin Mode can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately.‰Xč‹ć1e˜  8ć<ŽWÂSection 4.3.3: ‘Implicit CR in every LF’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")V-]<Ž) "€Z€€€€‚˙Section 4.3.3: ‘Implicit CR in every LF’&ćb% €€˜€‚˙Most servers send two 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).ńĚ<Ž_Ŕ% €™€˜€‚˙Some servers only send LF, and expect the terminal to move the cursor over to the left automatically. If you come acrossb_Ŕ] a server that does this, you will see a stepped effect on the screen, like this:8b—Ŕ# €*€€‚˙First line of textC _ŔÚŔ# €@€€‚˙ Second lineN*—Ŕ(Á$ €T€˜€‚˙ Third line•qÚŔ˝Á$ €â€˜€‚˙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 text1˝Á&Â# €€€‚˙Second line1 őÁWÂ$ €€˜€‚˙Third line—f&ÂîÂ1§‰ ӄ 9îÂRĂ•ÇSection 4.3.4: ‘Use background colour to erase screen’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")d;WÂRĂ) "€v€€€€‚˙Section 4.3.4: ‘Use background colour to erase screen’_4îÂąÄ+ $€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.•qRĂFĹ$ €â€˜€‚˙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.}LFĹ•Ç1 0€™€˜€€€ă€ÄůN‰‚˙Background-colour erase can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately.†UĆČ1> m‡ :ČnČYËSection 4.3.5: ‘Enable blinking text’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")S*•ÇnČ) "€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.ź—nČćÉ% €/€˜€‚˙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.sB*ÉYË1 0€…€˜€€€ă€ÄůN‰‚˙Blinking text can be turned on and off by control sequences sent by the server. This configuration option controls the default state, which will be restored when you reset the terminal (see section 3.1.3.6). However, if you modify this option in mid-session using ‘Change Settings’, it will take effect immediately.‚QćÉŰË1†ӄ ;ŰË*ĚmSection 4.3.6: ‘Answerback to ^E’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")O&YË*Ě) "€L€€€€‚˙Section 4.3.6: ‘Answerback to ^E’Ŕ›ŰËęĚ% €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 other problems. Úę̡Ď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ŹÎm6 <€č€˜€€€€€€€‚˙You can include coˇĎmYËntrol characters in the answerback string using ^C notation. (Use ^~ to get a literal ^.)|KˇĎé1Gm‡ Č <é20Section 4.3.7: ‘Local echo’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")I m2) "€@€€€€‚˙Section 4.3.7: ‘Local echo’1éc1 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.)ͨ20% €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.„Sc´1Ó Ů =´‡ Section 4.3.8: ‘Local line editing’CBB("btn_up","JI(`',`t00000046')");EB("btn_up")Q(0) "€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.Z5ř% €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.)ĺŔř‡ % €€˜€‚˙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˘ 1,Č ‚€ > h IASection 4.3.9: Remote-controlled printingCBB("btn_up","JI(`',`t00000046')");EB("btn_up")W.‡ h ) "€\€€€€‚˙Section 4.3.9: Remote-controlled printingĆĄ . % €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.ȝh ö + $€;€˜€€€‚˙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.;. 1+ $€!€˜€€€‚˙When the remote server attempts to print some data, PuTTY will send that data to the printer raw - without translating it, 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@ö ˘@% €€˜€‚˙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 d1˘@‡ one 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.§‚1IA% €€˜€‚˙To disable remote printing again, choose ‘None (printing disabled)’ from the printer selection list. This is the default state.€O˘@ÉA1)Ů ć‚ ?ÉABňESection 4.4: The Keyboard panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")M$IAB) "€H€€€€‚˙Section 4.4: The Keyboard panel…aÉA›B$ €Â€˜€‚˙The Keyboard configuration panel allows you to control the behaviour of the keyboard in PuTTY.m>BC/ .€|€ă*͈s€€€‰‚˙Section 4.4.1: Changing the action of the Backspace keyqB›ByC/ .€„€ăť‰Ů˘€€€‰‚˙Section 4.4.2: Changing the action of the Home and End keysxICńC/ .€’€ăVS怀€‰‚˙Section 4.4.3: Changing the action of the function keys and keypadm>yC^D/ .€|€ăneÇA€€€‰‚˙Section 4.4.4: Controlling Application Cursor Keys modeh9ńCĆD/ .€r€ă(~Ś„€€€‰‚˙Section 4.4.5: Controlling Application Keypad mode^/^D$E/ .€^€ă˝–\!€€€‰‚˙Section 4.4.6: Using NetHack keypad moded5ĆDˆE/ .€j€ăqýF€€€‰‚˙Section 4.4.7: Enabling a DEC-like Compose keyj;$EňE/ .€v€ăĽŕĚs€€€‰‚˙Section 4.4.8: ‘Control-Alt is different from AltGr’˜gˆEŠF1F‚€ ˆ† @ŠFďFĐJSection 4.4.1: Changing the action of the Backspace keyCBB("btn_up","JI(`',`t00000047')");EB("btn_up")e<ňEďF) "€x€€€€‚˙Section 4.4.1: Changing the action of the Backspace keyˆcŠFwH% €Ç€˜€‚˙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<ďFŢI+ $€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.ňÇwHĐJ+ $€€˜€€€‚˙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ŢIlK1Çć‚ ˆ AlKŐK3NSection 4.4.2: Changing the action of the Home and End keysCBB("btn_up","JI(`',`t00000047')");EB("btn_up")i@ĐJŐK) "€€€€€€‚˙Section 4.4.2: Changing the action of the Home and End keysʟlKŸL+ $€?€˜€€€‚˙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.ëĽŐKŠMF 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.Š„ŸL3N% € €˜€‚˙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ŠMÖN1ˆ† } BÖNFO5†Section 4.4.3: Changing the action of the function keys and keypadCBB("btn_up","JI(`',`t00000047')");EB("btn_up")pG3NFO) "€Ž€€€€‚˙Section 4.4.3: Changing the action of the function keys and keypad[ÖN €$ €ś€˜€‚˙This option affects the function keys (F1 to F12) and the top row of the numeric keypad.FO €3NőľFO@ 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.؞ €ف: 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. ˁä‚@ 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€;€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ä‚=„6 <€˜€T˜‘€8‚€ƒ€€€€‚˙•In VT100+ mode, the function keys generate ESC OP through to ESC O[}ťƒş…^ Š€?€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 [{.{W=„5†$ €Ž€˜€‚˙If you don't know what any of this means, you probably don't need to fiddle with it.˜gş…͆1ôˆ ź C͆2‡Á‰Section 4.4.4: Controlling Application Cursor Keys modeCBB("btn_up","JI(`',`t00000047')");EB("btn_up")e<5†2‡) "€x€€€€‚˙Section 4.4.4: Controlling Application Cursor Keys mode+î͆]ˆ= 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.ť–2‡‰% €-€˜€‚˙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.Š]ˆÁ‰* $€ţ€˜€ăMD™‰‚˙You can also disable application cursor keys mode completely, using the ‘Features’ configuration panel; see section 4.6.1.“b‰TŠ1} ˛ DTŠ´Š[Section 4.4.5: Controlling Application Keypad modeCBB("btn_up","JI(`',`t00000047')");EB("btn_up")`7Á‰´Š) "€n€€€€‚˙Section 4.4.5: Controlling Application Keypad mode…aTŠ9‹$ €Â€˜€‚˙Application Keypad mode is a way for the server to change the behaviour of the numeric keypad.ŕť´ŠŒ% €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.ÔŠ9‹íŒ+ $€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.ďŒŽ% €ß€˜€‚˙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.ś‘íŒˇŽ% €#€˜€‚˙Application keypad mode can be turned on and off by the server, depending on the application. PuTTY allows you to configure the initial state.¤zŽ[* $€ô€˜€ăMD™‰‚˙You can also disable application keypad mode completely, using the ‘Features’ configuration panel; see section 4.6.1.‰XˇŽ Ŕ1Kź }‚ E ŔbŔWĂSection 4.4.6: Using NetHack keypad modeCBB("btn_up","JI(`',`t00000047')");EB("btn_up")[ Ŕ[V-[bŔ) "€Z€€€€‚˙Section 4.4.6: Using NetHack keypad mode°‹ ŔÁ% €€˜€‚˙PuTTY has a special mode for playing NetHack. You can enable it by selecting ‘NetHack’ in the ‘Initial state of numeric keypad’ control.ēbŔÖÁ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.€\ÖÁWĂ$ €¸€˜€‚˙For some reason, this feature only works properly when Num Lock is on. We don't know why.^×ÂćĂ1ɲ ӄ FćĂBÄŻĆSection 4.4.7: Enabling a DEC-like Compose keyCBB("btn_up","JI(`',`t00000047')");EB("btn_up")\3WĂBÄ) "€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.čĂBÄŻĆ% €‡€˜€‚˙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ÇĹDÇ1y}‚ }ˆ GDÇŚÇ˝ËSection 4.4.8: ‘Control-Alt is different from AltGr’CBB("btn_up","JI(`',`t00000047')");EB("btn_up")b9ŻĆŚÇ) "€r€€€€‚˙Section 4.4.8: ‘Control-Alt is different from AltGr’íČDÇ“Č% €‘€˜€‚˙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.ş‰ŚÇMĘ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.ˇ’“ČË% €%€˜€‚˙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.šŽMĘ˝Ë+ $€€˜€ă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.)|KË9Ě1;ӄ šŠ H9Ě‚ĚtĎSection 4.5: The Bell panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")I ˝Ë‚Ě) "€@€€€€‚˙Section 4.5: The Bell paneli9ĚÍ$ €Ň€˜€‚˙The Bell panel controls the terminal bell feature: the server's ability to cause PuTTY to beep at you.6‚ĚEÎ% €#€˜€‚˙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:EÎ Ď/ .€t€ăy2\†€€€‰‚˙Section 4.5.2: ‘Taskbar/caption indication on bell’j;ĄÎtĎ/ .€v€ăsĹv€€€‰‚˙Section 4.5.3: ‘Control the bell overload behaviour’‡V Ď 1[}ˆ V I `gSection 4.5.1: ‘Set the style of bell’CBB("btn_up","JI(`',`t00000048')");EB("btn_up")tĎ tĎT+tĎ`) "€V€€€€‚˙Section 4.5.1: ‘Set the style of bell’[ ß$ €ś€˜€‚˙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‚€ƒ€‚˙•‘Make default system alert 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.塏ź. *€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.Ť}×g. *€ű€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’.”cźű1úšŠ • Jű\ő Section 4.5.2: ‘Taskbar/caption indication on bell’CBB("btn_up","JI(`',`t00000048')");EB("btn_up")a8g\) "€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.ܡW % €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.•dW Š 1˝V ű€ KŠ ě SBSection 4.5.3: ‘Control the bell overload behaviour’CBB("btn_up","JI(`',`t00000048')");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ě %% €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 overload 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’.W2%3A% €e€˜€‚˙AlternativĐ3Aő ely, 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. űĐSB% €÷€˜€‚˙Bell overload mode is always deactivated by any keypress in the terminal. This means it can respond to large unexpected streams of data, but does not interfere with ordinary command-line activities that generate beeps (such as filename completion).€O3AÓB1T• ^„ LÓB C'HSection 4.6: The Features panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")M$SB C) "€H€€€€‚˙Section 4.6: The Features panel÷ŇÓBD% €Ľ€˜€‚˙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.Ť† CÂD% € €˜€‚˙The Features configuration panel allows you to disable some of PuTTY's more advanced terminal features, in case they cause trouble.qBD3E/ .€„€ăMD™€€€‰‚˙Section 4.6.1: Disabling application keypad and cursor keysr=ÂDĽE5 :€z€ăâł„€€€€€‰‚˙Section 4.6.2: Disabling xterm-style mouse reportingg83E F/ .€p€ăﴕZ€€€‰‚˙Section 4.6.3: Disabling remote terminal resizingpAĽE|F/ .€‚€ăÚfů̀€€‰‚˙Section 4.6.4: Disabling switching to the alternate screenk< FçF/ .€x€ăÂdY7€€€‰‚˙Section 4.6.5: Disabling remote window title changingk<|FRG/ .€x€ăî4ŐT€€€‰‚˙Section 4.6.6: Disabling remote window title queryingd5çFśG/ .€j€ă>Šc܀€€‰‚˙Section 4.6.7: Disabling destructive backspaceqBRG'H/ .€„€ă}q:€€€‰‚˙Section 4.6.8: Disabling remote character set configurationœkśGĂH1ěű€ đ… MĂH,IŻJSection 4.6.1: Disabling application keypad and cursor keysCBB("btn_up","JI(`',`t00000049')");EB("btn_up")i@'H,I) "€€€€€€‚˙Section 4.6.1: Disabling application keypad and cursor keysƒRĂHŻJ1 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,IDK1Ő^„ ‰ NDKŽKOSection 4.6.2: Disabling xterm-style mouse reportingCBB("btn_up","JI(`',`t00000049')");EB("btn_up")j;ŻJŽK/ .€v€€€€€€‚˙Section 4.6.2: Disabling xterm-style mouse reporting`)DKM7 <€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).óČŽKN+ $€‘€˜€€€‚˙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.íMO+ $€Ű€˜€ă.Ŕŕ‰‚˙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.3).’aNŤO1lđ… č OŤO€#Section 4.6.3: Disabling remote terminal resizingCBB("btn_up","JI(`',`t00000049')");EB("btn_up")_6O€) "€l€€€€‚˙Section 4.6.3: Disabling remote terminal ŤO€Oresizing čŤO#% €Ń€˜€‚˙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€ž1 ‰ x Pž&‚Á„Section 4.6.4: Disabling switching to the alternate screenCBB("btn_up","JI(`',`t00000049')");EB("btn_up")h?#&‚) "€~€€€€‚˙Section 4.6.4: Disabling switching to the alternate screenť–žáƒ% €-€˜€‚˙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.ŕť&‚Á„% €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.–eáƒW…1`č Š QW…ş…ˇ†Section 4.6.5: Disabling remote window title changingCBB("btn_up","JI(`',`t00000049')");EB("btn_up")c:Á„ş…) "€t€€€€‚˙Section 4.6.5: Disabling remote window title changingýŘW…ˇ†% €ą€˜€‚˙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.–eş…M‡1&x % RM‡°‡s‹Section 4.6.6: Disabling remote window title queryingCBB("btn_up","JI(`',`t00000049')");EB("btn_up")c:ˇ†°‡) "€t€€€€‚˙Section 4.6.6: Disabling remote window title queryingíČM‡ˆ% €‘€˜€‚˙PuTTY can optionally provide the xterm service of allowing server applications to find out the local window title. This feature is disabled by default, but you can turn it on if you really want it.Ö™°‡s‹= H€3€˜€€€€€ăÂdY7‰€€‚˙NOTE that this feature is a potential security hazard. If a malicious application can write data to your terminal (for example, if you merely cat a file owned by someone else on the server machine), it can change your window title (unless you have disabled this as mentioned in section 4.6.5) and then use this service to have the new window title sent back to the server as if typed at the keyboard. This allows an attacker to fake keypresses and potentially cause your server-side applications to do things you didn't want. Therefore this feature is disabled by default, and we recommend you do not turn it on unless you really know what you are doing.^ˆŒ1ęŠ Á SŒ^ŒěSection 4.6.7: Disabling destructive backspaceCBB("btn_up","JI(`',`t00000049')");EB("btn_up")\3s‹^Œ) "€f€€€€‚˙Section 4.6.7: Disabling destructive backspaceŽiŒě% €Ó€˜€‚˙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^ŒˆŽ1°% ƀ TˆŽńŽDÁSection 4.6.8: Disabling remote character set configurationCBB("btn_up","JI(`',`t00000049')");EB("btn_up")i@ěńŽ) "€€€€€€‚˙Section 4.6.8: Disabling remote character set configuration\7ˆŽYŔ% €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ńŽYŔě reconfiguring the character set to something other than the user intended.ëĆńŽDÁ% €€˜€‚˙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.~MYŔÂÁ1XÁ ‚ UÂÁ ÂÄSection 4.7: The Window panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")K"DÁ Â) "€D€€€€‚˙Section 4.7: The Window panelxTÂÁ…Â$ €¨€˜€‚˙The Window configuration panel allows you to control aspects of the PuTTY window.i: ÂîÂ/ .€t€ă ď´ €€€‰‚˙Section 4.7.1: Setting the size of the PuTTY windowj;…ÂXĂ/ .€v€ă„G6˝€€€‰‚˙Section 4.7.2: What to do when the window is resized[,îÂłĂ/ .€X€ă¨;‹€€€‰‚˙Section 4.7.3: Controlling scrollbackg8XĂÄ/ .€p€ă^¨ÝM€€€‰‚˙Section 4.7.4: ‘Push erased text into scrollback’”cłĂŽÄ1(ƀ ď‚ VŽÄĹÖĹSection 4.7.1: Setting the size of the PuTTY windowCBB("btn_up","JI(`',`t00000050')");EB("btn_up")a8ÄĹ) "€p€€€€‚˙Section 4.7.1: Setting the size of the PuTTY windowǢŽÄÖĹ% €E€˜€‚˙The ‘Rows’ and ‘Columns’ boxes let you set the PuTTY window to a precise size. Of course you can also drag the window to a new size while a session is running.•dĹkĆ1n‚ ‡ WkĆÍĆŮËSection 4.7.2: What to do when the window is resizedCBB("btn_up","JI(`',`t00000050')");EB("btn_up")b9ÖĹÍĆ) "€r€€€€‚˙Section 4.7.2: What to do when the window is resized†bkĆSÇ$ €Ä€˜€‚˙These options allow you to control what happens when the user tries to resize the PuTTY window.gCÍĆşÇ$ €†€˜€‚˙When you resize the PuTTY window, one of four things can happen:e8SÇČ- *€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ČBÉ- *€Ę€T˜‘€8‚€ƒ€‚˙•The number of rows and columns in the terminal can stay the same, and the font size can change.÷Ă°Č9Ę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. {BÉŮË% €÷€˜€‚˙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.†U9Ę_Ě1ăď‚ X_̲ĚNSection 4.7.3: Controlling scrollbackCBB("btn_up","JI(`',`t00000050')");EB("btn_up")S*Ů˲Ě) "€T€€€€‚˙Section 4.7.3: Controlling scrollback§}_ĚYÍ* $€ú€˜€ă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.zUYÍN% €Ť€˜€‚˙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 wheČÎNŮËn you press a key, by turning on ‘Reset scrollback on keypress’.’aČÎŕ1Ă ‡ &Yŕ?ŁSection 4.7.4: ‘Push erased text into scrollback’CBB("btn_up","JI(`',`t00000050')");EB("btn_up")_6N?) "€l€€€€‚˙Section 4.7.4: ‘Push erased text into scrollback’őŕY% €ë€˜€‚˙When this option is enabled, the contents of the terminal screen will be pushed into the scrollback when a server-side application clears the screen, so that your scrollback will contain a better record of what was on your screen in the past.Ö?Z+ $€­€˜€ăÚfů̉‚˙If the application switches to the alternate screen (see section 4.6.4 for more about this), then the contents of the primary screen will be visible in the scrollback until the application switches back again.I%YŁ$ €J€˜€‚˙This option is enabled by default.‚QZ%1ŽŤZ%tłSection 4.8: The Appearance panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")O&Łt) "€L€€€€‚˙Section 4.8: The Appearance panelŒh%$ €Đ€˜€‚˙The Appearance configuration panel allows you to control aspects of the appearance of PuTTY's window.m>tm/ .€|€ăžţ^ـ€€‰‚˙Section 4.8.1: Controlling the appearance of the cursoruFâ/ .€Œ€ăW݌Á€€€‰‚˙Section 4.8.2: Controlling the font used in the terminal windowo@mQ/ .€€€ă{ÍH+€€€‰‚˙Section 4.8.3: ‘Hide mouse pointer when typing in window’b3âł/ .€f€ăŘdbπ€€‰‚˙Section 4.8.4: Controlling the window border˜gQK1ö&/[K°A Section 4.8.1: Controlling the appearance of the cursorCBB("btn_up","JI(`',`t00000051')");EB("btn_up")e<ł°) "€x€€€€‚˙Section 4.8.1: Controlling the appearance of the cursoráKś% €Ă€˜€‚˙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 underline or a vertical line becomes dotted.‹g°A $ €Î€˜€‚˙The ‘Cursor blinks’ option makes the cursor blink on and off. This works in any of the cursor modes. ośá 1­ŤŽ\á N Ž Section 4.8.2: Controlling the font used in the terminal windowCBB("btn_up","JI(`',`t00000051')");EB("btn_up")mDA N ) "€ˆ€€€€‚˙Section 4.8.2: Controlling the font used in the terminal window@á Ž % €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.)šiN ( 1/.](  :Section 4.8.3: ‘Hide mouse pointer when typing in window’CBB("btn_up","JI(`',`t00000051')");EB("btn_up")g>Ž  ) "€|€€€€‚˙Section 4.8.3: ‘Hide mouse pointer when typing in window’. ( ˝ % €€˜€‚˙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 :$ €˛€˜€‚˙This option is disabled by default, so the mouse pointer remains visible at all times.\˝ Ç1XŽí€^Ç!+BSection 4.8.4: Controlling the window borderCBB("btn_up","JI(`',`t00000051')");EB("btn_up")Z1:!) "€b€€€€‚˙Section 4.8.4: Controlling the window borderxTÇ™$ €¨€˜€‚˙PuTTY allows you to configure the appearance of the window border to some extent.tO!A% €Ÿ€˜€‚˙The checkbox marked ‘Sunken-edge border’ changes the appearance o™A:f 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.í™+B% €Ű€˜€‚˙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.PAŹB1Š.á‚_ŹBúB6FSection 4.9: The Behaviour panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")N%+BúB) "€J€€€€‚˙Section 4.9: The Behaviour panelŠfŹB„C$ €Ě€˜€‚˙The Behaviour configuration panel allows you to control aspects of the behaviour of PuTTY's window.a2úBĺC/ .€d€ăěe|…€€€‰‚˙Section 4.9.1: Controlling the window titlea2„CFD/ .€d€ă'wúű€€€‰‚˙Section 4.9.2: ‘Warn before closing window’^/ĺC¤D/ .€^€ă0tW…€€€‰‚˙Section 4.9.3: ‘Window closes on ALT-F4’g8FD E/ .€p€ă°x˛z€€€‰‚˙Section 4.9.4: ‘System menu appears on ALT-Space’g8¤DrE/ .€p€ă‚Úą€€€‰‚˙Section 4.9.5: ‘System menu appears on Alt alone’e6 E×E/ .€l€ădî:a€€€‰‚˙Section 4.9.6: ‘Ensure window is always on top’_0rE6F/ .€`€ăz?Öw€€€‰‚˙Section 4.9.7: ‘Full screen on Alt-Enter’Œ[×EÂF1v퀥‡`ÂFG8LSection 4.9.1: Controlling the window titleCBB("btn_up","JI(`',`t00000052')");EB("btn_up")Y06FG) "€`€€€€‚˙Section 4.9.1: Controlling the window title0ÂFKH+ $€ €˜€€€‚˙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.čGJ7 <€€˜€€€€€€€‚˙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.)ţKH8L+ $€ý€˜€€€‚˙By default, PuTTY only uses the server-supplied window title, and ignores the icon title entirely. If for some reason you want to see both titles, check the box marked ‘Separate window and icon titles’. If you do this, 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.)Œ[JÄL1 á‚:‰aÄLMĎNSection 4.9.2: ‘Warn before closing window’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")Y08LM) "€`€€€€‚˙Section 4.9.2: ‘Warn before closing window’!üÄL>N% €ů€˜€‚˙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.‘mMĎN$ €Ú€˜€‚˙If you want to be able to close a window quickly, you can disable the ‘Warn before closing window’ option.‰X>NXO1fĄ‡bXOŽOʀSection 4.9.3: ‘Window closes on ALT-F4’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")V-ĎNŽO) "€Z€€€€‚˙Section 4.9.3: ‘Window closes on ALT-F4’ĺXOʀ+ $€Ë€˜€ă'wúű‰‚˙By default, pressing ALT-F4 causes theŽOʀĎN window to close (or a warning box to appear; see section 4.9.2). If you disable the ‘Window closes on ALT-F4’ option, then pressing ALT-F4 will simply send a key sequence to the server.’aŽO\1•:‰c\ťńƒSection 4.9.4: ‘System menu appears on ALT-Space’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")_6ʀť) "€l€€€€‚˙Section 4.9.4: ‘System menu appears on ALT-Space’×\˝‚+ $€Ż€˜€€€‚˙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˝‚ƒ„1V$dƒ„â„مSection 4.9.5: ‘System menu appears on Alt alone’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")_6ńƒâ„) "€l€€€€‚˙Section 4.9.5: ‘System menu appears on Alt alone’÷҃„م% €Ľ€˜€‚˙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._â„i†1Ö­ei†Ɔ?‡Section 4.9.6: ‘Ensure window is always on top’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")]4مƆ) "€h€€€€‚˙Section 4.9.6: ‘Ensure window is always on top’yUi†?‡$ €Ş€˜€‚˙If this option is enabled, the PuTTY window will stay on top of all other windows.ŠYƆɇ1í$!fɇ ˆś‰Section 4.9.7: ‘Full screen on Alt-Enter’CBB("btn_up","JI(`',`t00000052')");EB("btn_up")W.?‡ ˆ) "€\€€€€‚˙Section 4.9.7: ‘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.ɞ ˆś‰+ $€=€˜€ăŹÄů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.7.„Síˆ:Š1ă­úg:Š‹ŠSection 4.10: The Translation panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")Q(ś‰‹Š) "€P€€€€‚˙Section 4.10: The Translation panelĎŞ:ŠZ‹% €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<‹Šŋ/ .€x€ăoĹsş€€€‰‚˙Section 4.10.1: Controlling character set translationi:Z‹.Œ/ .€t€ăžżí€€€‰‚˙Section 4.10.2: ‘Caps Lock acts as Cyrillic switch’tEŋ˘Œ/ .€Š€ă÷ů0Ԁ€€‰‚˙Section 4.10.3: Controlling display of line drawing characters{L.Œ/ .€˜€ăŘk—Ő€€€‰‚˙Section 4.10.4: Controlling copy and paste of line drawing characters–e˘Œł1Ô!$„hłŽ“ĹSection 4.10.1: Controlling character set translationCBB("btn_up","JI(`',`t00000053')");EB("btn_up")c:Ž) "€t€€€€‚˙Section 4.10.1: Controlling character set translationăžłůŽ% €}€˜€‚˙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?ŽiŔ% €€˜€‚˙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 růŽiŔeported by Windows; if it gets it wrong, you can select a different one using this control.H$ůŽąŔ$ €H€˜€‚˙A few notable character sets are:˝iŔnÁ. *€€T˜‘€8‚€ƒ€‚˙•The ISO-8859 series are all standard character sets that include various accented characters appropriate for different sets of languages.ŇąŔnÂ. *€Ľ€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.¤wnÁĂ- *€î€T˜‘€8‚€ƒ€‚˙•If you want the old IBM PC character set with block graphics and line-drawing characters, you can select ‘CP437’.*ünÂ<Ä. *€ů€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.W,Ă“Ĺ+ $€Y€˜€€€‚˙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 can try entering its name manually (CP866 for example) in the list box. If the underlying version of Windows has the appropriate translation table installed, PuTTY will use it.”c<Ä'Ć1ěúž…i'ĆˆĆČSection 4.10.2: ‘Caps Lock acts as Cyrillic switch’CBB("btn_up","JI(`',`t00000053')");EB("btn_up")a8“ĹˆĆ) "€p€€€€‚˙Section 4.10.2: ‘Caps Lock acts as Cyrillic switch’ýŘ'Ć…Ç% €ą€˜€‚˙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ˆĆČ$ €Ô€˜€‚˙Currently this feature is not expected to work properly if your native keyboard layout is not US or UK.Ÿn…DzČ1k$„j˛ČÉ)Section 4.10.3: Controlling display of line drawing charactersCBB("btn_up","JI(`',`t00000053')");EB("btn_up")lCČÉ) "€†€€€€‚˙Section 4.10.3: Controlling display of line drawing characters]8˛Č{Ę% €q€˜€‚˙VT100-series terminals allow the server to send control sequences that shift temporarily into a separate character 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.ŻÉ*Ě. *€€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./{ĘYÍ. *€€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.@úYÍBĎ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.Ű­Î). *€[€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 reliBĎ)Čable and functional option.ŚuBĎĎ1Wž…şkĎB&Section 4.10.4: Controlling copy and paste of line drawing charactersCBB("btn_up","JI(`',`t00000053')");EB("btn_up")sJ)B) "€”€€€€‚˙Section 4.10.4: Controlling copy and paste of line drawing charactersřŻĎ:I `€_€˜€€€€€€€€€€€€€‚˙By default, when you copy and paste a piece of the PuTTY screen that contains VT100 line and box drawing characters, PuTTY will paste them in the form they appear on the screen: either Unicode line drawing code points, or the ‘poor man's’ line-drawing characters +, - and |. The checkbox ‘Copy and paste VT100 line drawing chars as lqqqk’ disables this feature, so line-drawing characters will be pasted as the ASCII characters that were printed to produce them. 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.ěÁB&+ $€ƒ€˜€€€‚˙Note that this option only applies to line-drawing characters which were printed by using the VT100 mechanism. Line-drawing characters displayed using Unicode will paste as Unicode always.‚Q:¨1ÖXl¨÷~Section 4.11: The Selection panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")O&&÷) "€L€€€€‚˙Section 4.11: The Selection panel]¨x$ €ş€˜€‚˙The Selection panel allows you to control the way copy and paste work in the PuTTY window.a2÷Ů/ .€d€ă@ËŢ€‰‚˙Section 4.11.1: Pasting in Rich Text Formato@xH/ .€€€ăٓ§.€€€‰‚˙Section 4.11.2: Changing the actions of the mouse buttonsrCŮş/ .€†€ă.Ŕŕ€€€‰‚˙Section 4.11.3: ‘Shift overrides application's use of mouse’\-H/ .€Z€ă ˇkJ€€€‰‚˙Section 4.11.4: Default selection modeh9ş~/ .€r€ăý@€€€‰‚˙Section 4.11.5: Configuring word-by-word selectionŒ[ 1Ťş‘m c ľ Section 4.11.1: Pasting in Rich Text FormatCBB("btn_up","JI(`',`t00000054')");EB("btn_up")Y0~c ) "€`€€€€‚˙Section 4.11.1: Pasting in Rich Text FormatćÁ I % €ƒ€˜€‚˙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 appear 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.lHc ľ $ €€˜€‚˙This option can easily be inconvenient, so by default it is disabled.šiI O 1“X€nO ś î@Section 4.11.2: Changing the actions of the mouse buttonsCBB("btn_up","JI(`',`t00000054')");EB("btn_up")g>ľ ś ) "€|€€€€‚˙Section 4.11.2: Changing the actions of the mouse buttons7 O í + $€€˜€€€‚˙PuTTY's copy and paste mechanism is by default 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 0€u€˜€€€€€‚˙Windows often only has two mouse buttons, so in PuTTY's default configuration (‘Compromise’), 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.H#Řî@% €G€˜€‚˙Alternatively, with the ‘Windows’ option selected, the middle bušî@ľ tton extends, and the right button brings up a context menu (on which one of the options is ‘Paste’). (This context menu is always available by holding down Ctrl and right-clicking, regardless of the setting of this option.)lš‹A1*‘U„o‹AőAľFSection 4.11.3: ‘Shift overrides application's use of mouse’CBB("btn_up","JI(`',`t00000054')");EB("btn_up")jAî@őA) "€‚€€€€‚˙Section 4.11.3: ‘Shift overrides application's use of mouse’`)‹AUC7 <€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).úŐőAOD% €Ť€˜€‚˙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.¨ƒUC÷E% €€˜€‚˙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).ž“ODľF+ $€'€˜€ăâł„‰‚˙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÷EBÍCÎ) "€|€€€€‚˙Section 4.13.3: Using keepalives to prevent disconnectionǢÜÍ Ď% €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.\CΗ % €š€˜€‚˙Some network routers and firewalls need to keep 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 t Ď— BÍime interval. This can cause PuTTY sessions to be unexpectedly closed by the firewall if no traffic is seen in the session for some time.ă ĎŸ % €Ç€˜€‚˙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.ƒX— " + $€ą€˜€€€‚˙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.—sŸ š $ €ć€˜€‚˙Keepalives are only supported in Telnet and SSH; the Rlogin and Raw protocols offer no way of implementing them.Ţł" — + $€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.Œ[š # 10ś‡ {# | S Section 4.13.4: ‘Disable Nagle's algorithm’CBB("btn_up","JI(`',`t00000056')");EB("btn_up")Y0— | ) "€`€€€€‚˙Section 4.13.4: ‘Disable Nagle's algorithm’…`#  % €Á€˜€‚˙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.| S $ €\€˜€‚˙The Nagle algorithm is disabled by default.~M Ń 1Ąa |Ń  r Section 4.14: The Proxy panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")K"S  ) "€D€€€€‚˙Section 4.14: The Proxy panel\1Ń x + $€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).\- Ô / .€Z€ăč8–€€€‰‚˙Section 4.14.1: Setting the proxy typerCx F / .€†€ă ĽŮZ€€€‰‚˙Section 4.14.2: Excluding parts of the network from proxyingh9Ô Ž / .€r€ă“8&°€€€‰‚˙Section 4.14.3: Name resolution when using a proxy[,F  / .€X€ăĘh–€€€‰‚˙Section 4.14.4: Username and passwordi:Ž r / .€t€ă]˝v€€€‰‚˙Section 4.14.5: Specifying the Telnet proxy commandˆW  @ 1ý ƒ} @ `@ D Section 4.14.1: Setting the proxy typeCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")r @ r T+r `@ ) "€V€€€€‚˙Section 4.14.1: Setting the proxy typeôĎ @ TA % €Ÿ€˜€‚˙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.ƒ`@ B 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.cTA ŞB - *€Ć€T˜‘€8‚€ƒ€‚˙•Selecting ‘SOCKS 4’ or ‘SOCKS 5’ allows you to proxy your connections through a SOCKS server._+B D 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ŞB §D 1´ !‰~§D E [L Section 4.14.2: Excluding parts of the network from proxyingCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")jA D E ) "€‚€€€€‚˙Section 4.14.2: Excluding parts of the network from proxying“n§D ¤F % €Ý€˜€‚˙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.îĂE ’G + $€‡€˜€€€‚˙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¤F ĆG $ € €˜€‚˙*.example.comwM’G =H * $€š€˜€€€‚˙This excludes any host with a name ending in .example.com from proxying.3ĆG pH $ €€˜€‚˙192.168.88.*xT=H čH $ €¨€˜€‚˙This excludes any host with an IP address starting with 192.168.88 from proxying.ApH )I $ €:€˜€‚˙192.168.88.*,*.example.comV2čH I $ €d€˜€‚˙This excludes both of the above ranges at once.tI)I óJ + $€“€˜€€€‚˙Connections to the local host (the host name localhost, and any loopback IP address) are never proxied, even if the proxy exclude list does not explicitly contain them. It is very unlikely that this behaviour would ever cause problems, but if it does you can change it by enabling ‘Consider proxying local host connections’.h=I [L + $€{€˜€ă“8&°‰‚˙Note that if you are doing DNS at the proxy (see section 4.14.3), you should make sure that your proxy exclusion settings do not depend on knowing the IP address of a host. If the name is passed on to the proxy without PuTTY looking it up, it will never know the IP address and cannot check it against your list.”cóJ ďL 18ƒJďL OM 3ƒ Section 4.14.3: Name resolution when using a proxyCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")`7[L OM ) "€n€€€€‚˙Section 4.14.3: Name resolution when using a proxyâ˝ďL 1N % €{€˜€‚˙If you are using a proxy to access a private network, it can make a difference whether DNS name resolution is performed by PuTTY itself (on the client machine) or performed by the proxy.^9OM O % €s€˜€‚˙The ‘Do DNS name lookup at proxy end’ configuration option allows you to control this. If you set it to ‘No’, PuTTY will always do its own DNS, and will always pass an IP address to the proxy. If you set it to ‘Yes’, PuTTY will always pass host names straight to the proxy without trying to look them up first.ţŮ1N ™€ % €ł€˜€‚˙If you set this option to ‘Auto’ (the default), PuTTY will do something it O ™€ [L considers appropriate for each type of proxy. Telnet and HTTP proxies will have host names passed straight to them; SOCKS proxies will not.h=O ‚ + $€{€˜€ă ĽŮZ‰‚˙Note that if you are doing DNS at the proxy, you should make sure that your proxy exclusion settings (see section 4.14.2) do not depend on knowing the IP address of a host. If the name is passed on to the proxy without PuTTY looking it up, it will never know the IP address and cannot check it against your list.2 ™€ 3ƒ % €€˜€‚˙The original SOCKS 4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS 4A) which does support it, but not all SOCKS 4 servers provide this extension. If you enable proxy DNS and your SOCKS 4 server cannot deal with it, this might be why.‡V‚ şƒ 1ű!‰G€şƒ „ ľ† Section 4.14.4: Username and passwordCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")S*3ƒ „ ) "€T€€€€‚˙Section 4.14.4: Username and passwordyşƒ Ş„ $ €ň€˜€‚˙If your proxy requires authentication, you can enter a username and a password in the ‘Username’ and ‘Password’ boxes.d@ „ … $ €€€˜€‚˙Authentication is not fully supported for all forms of proxy:Š]Ş„ ˜… - *€ş€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.Ľr˜… ľ† 3 6€ä€T˜‘€8‚€ƒ€ă]˝v‰‚˙•You can specify a way to include a username and password in the Telnet proxy command (see section 4.14.5).•d† J‡ 1OJ7 J‡ Ť‡ ™ Section 4.14.5: Specifying the Telnet proxy commandCBB("btn_up","JI(`',`proxy.main')");EB("btn_up")a8ľ† Ť‡ ) "€p€€€€‚˙Section 4.14.5: Specifying the Telnet proxy commandęJ‡ Ŕˆ + $€Ő€˜€€€‚˙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űŤ‡ Š I `€÷€˜€€€€€€€€€€€€€‚˙In this string, you can use \n to represent a new-line, \r to represent a carriage return, \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.KŔˆ O‹ I `€€˜€€€€€€€€€€€€€‚˙Also, the special strings %host and %port will be replaced by the host name and port number you want to connect to. The strings %user and %pass will be replaced by the proxy username and password you specify. To get a literal % sign, enter %%.Ą}Š đ‹ $ €ú€˜€‚˙If the Telnet proxy server prompts for a username and password before commands can be sent, you can use a command such as:J&O‹ :Œ $ €L€˜€‚˙%user\n%pass\nconnect %host %port\n_.đ‹ ™ 1 0€]€˜€€€€€‚˙This will send your username and password as the first two lines to the proxy, followed by a command to connect to the desired host and port. Note that if you do not include the %user or %pass tokens in the Telnet command, then the ‘Username’ and ‘Password’ configuration fields will be ignored.N:Œ Ž 1ZGπ‚Ž dŽ ~Á Section 4.15: The Telnet panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")L#™ dŽ ) "€F€€€€‚˙Section 4.15: The Telnet panel{WŽ ߎ $ €Ž€˜€‚˙The Telnet panel allows you to configure options that only apply to Telnet sessions.].dŽ < / .€\€ă‘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­ “Ŕ / .€„€ăF{€€€‰‚˙Section 4.15.4: Passive and active Telnet negotiation modesuF"Ŕ Á / .€Œ€ăěA/€€€‰‚˙Section 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’vG“Ŕ ~Á / .€Ž€ă‚ożż€€€‰‚˙Section 4.15.6: ‘Return key sends telnet New Line instead of ^M’ˆWÁ  1p7 ńƒ [ vĂ Section 4.15.1: ‘Terminal-speed string’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")U,~Á [ ) "€X€€€€‚˙Section 4.15.1: ‘Terminal-speed string’ö vĂ % €í€˜€‚˙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.)œk[ Ä 1π’„„Ä {Ä &Ç Section 4.15.2: Setting environment variables on the serverCBB("btn_up","JI(`',`t00000057')");EB("btn_up")i@vĂ {Ä ) "€€€€€€‚˙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 {Ä &Ç % €€˜€‚˙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üńęˆ…şÇ Č śĚ Section 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")a8&Ç Č ) "€p€€€€‚˙Section 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’Y4şÇ tÉ % €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 implementations 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.ą€tÉ śĚ 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Ë RÍ 1¸’„Ź†RÍ ťÍ  Section 4.15.4: Passive and active Telnet negotiation modesCBB("btn_up","JI(`',`t00000057')");EB("btn_up")i@śĚ ťÍ ) "€€€€€€‚˙Section 4.15.4: Passive and active Telnet negotiation modesŐŞRÍ Î + $€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.^:ťÍ îÎ $ €t€˜€‚˙PuTTY can use two different strategies for negotiation:‘^Î Ď 3 6€ź€T˜‘€8‚€ƒ€€€‚˙•In active mode, PuTTY starts to send negotiations as soon as the connection is opened.•bîÎ 3 6€Ä€T˜‘€8‚€ƒ€€€‚˙•In passive mode, PuTTY will wait to negotiate until it sees a negotiatioĎ śĚ n from the server.äżĎ  % €€˜€‚˙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.í  % €Ű€˜€‚˙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 ś 1|ęˆÚ‡ś # 2 Section 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")mD # ) "€ˆ€€€€‚˙Section 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’ęś 2 % €Ő€˜€‚˙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# Ó 1ŹˆÓ A ë Section 4.15.6: ‘Return key sends telnet New Line instead of ^M’CBB("btn_up","JI(`',`t00000057')");EB("btn_up")nE2 A ) "€Š€€€€‚˙Section 4.15.6: ‘Return key sends telnet New Line instead of ^M’V1Ó — % €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/A ë % €_€˜€‚˙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.N— j 1zÚN‰j ś ä Section 4.16: The Rlogin panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")L#ë ś ) "€F€€€€‚˙Section 4.16: The Rlogin panel{Wj 1 $ €Ž€˜€‚˙The Rlogin panel allows you to configure options that only apply to Rlogin sessions.].ś Ž / .€\€ăÚŮI_€€€‰‚˙Section 4.16.1: ‘Terminal-speed string’V'1 ä / .€N€ăy÷Oɀ€€‰‚˙Section 4.16.2: ‘Local username’ˆWŽ l 1}}Šl Á é Section 4.16.1: ‘Terminal-speed string’CBB("btn_up","JI(`',`t00000058')");EB("btn_up")U,ä Á ) "€X€€€€‚˙Section 4.16.1: ‘Terminal-speed string’(l é % €€˜€‚˙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Á j 1N…‚‹j ¸ ‡C Section 4.16.2: ‘Local username’CBB("btn_up","JI(`',`t00000058')");EB("btn_up")N%é ¸ ) "€J€€€€‚˙Section 4.16.2: ‘Local username’čŤj   = 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.ôϸ  @ % €Ÿ€˜€‚˙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.óś  “B = 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.ôĎ @ ‡C % €Ÿ€˜€‚˙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).|K“B D 1ş}„ŒD LD ˝F Section 4.17: The SSH panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")I ‡C LD ) "€@€€€€‚˙Section 4.17: The SSH paneluQD ÁD $ €˘€˜€‚˙The SSH panel allows you to configure options that only apply to SSH sessions.pALD 1E / .€‚€ăóWâ܀€€‰‚˙Section 4.17.1: Executing a specific command on the serverh9ÁD ™E / .€r€ăçр€€‰‚˙Section 4.17.2: ‘Don't allocate a pseudo-terminal’Z+1E óE / .€V€ăN§ľ€€€‰‚˙Section 4.17.3: ‘Enable compression’f7™E YF / .€n€ă, ŰT€€€‰‚˙Section 4.17.4: ‘Preferred SSH protocol version’d5óE ˝F / .€j€ădŢ娀€€‰‚˙Section 4.17.5: Encryption algorithm selection›jYF XG 1~…‚7…XG ŔG ÖH Section 4.17.1: Executing a specific command on the serverCBB("btn_up","JI(`',`t00000059')");EB("btn_up")h?˝F ŔG ) "€~€€€€‚˙Section 4.17.1: Executing a specific command on the serverńXG ÖH % €ă€˜€‚˙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ŔG iI 1Ę„|‡ŽiI ÉI 3L Section 4.17.2: ‘Don't allocate a pseudo-terminal’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")`7ÖH ÉI ) "€n€€€€‚˙Section 4.17.2: ‘Don't allocate a pseudo-terminal’T)iI K + $€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.ĺÉI 3L 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.…TK ¸L 1ł7…ሏ¸L M kN Section 4.17.3: ‘Enable compression’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")R)3L M ) "€R€€€€‚˙Section 4.17.3: ‘Enable compression’a<¸L kN % €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.‘` M üN 1Q|‡üN ZO Y Section 4.17.4: ‘Preferred SSH protocol version’CBB("btn_up","JI(`',`t00000059')");EB("btn_up")^5kN ZO ) "€j€€€€‚˙Section 4.17.4: ‘Preferred SSH protocol version’„`üN ŢO $ €Ŕ€˜€‚˙This allows you to select whether you would like to use SSH protocol version 1 or version 2. #ZO € ! €€˜‚˙ŢO € kN “oŢO  € $ €Ţ€˜€‚˙PuTTY will attempt to use protocol 1 if the server you connect to does not offer protocol 2, and vice versa.š” € Y % €)€˜€‚˙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.^ € č 1Ä áˆ‘č D‚ Ź‹ Section 4.17.5: Encryption algorithm selectionCBB("btn_up","JI(`',`t00000059')");EB("btn_up")\3Y D‚ ) "€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.Y5D‚ b„ $ €j€˜€‚˙PuTTY currently supports the following algorithms:i< „ ˄ - *€x€T˜‘€8‚€ƒ€‚˙•AES (Rijndael) - 256, 192, or 128-bit CBC (SSH-2 only)Ib„ … - *€8€T˜‘€8‚€ƒ€‚˙•Blowfish - 128-bit CBCK˄ _… - *€<€T˜‘€8‚€ƒ€‚˙•Triple-DES - 168-bit CBC`3… ż… - *€f€T˜‘€8‚€ƒ€‚˙•Single-DES - 56-bit CBC (see below for SSH-2)Ą}_… `† $ €ú€˜€‚˙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Ž† 8‡ # €*€€‚˙warning threshold.T0‡ Œ‡ $ €`€˜€‚˙Do you want to continue with this connection?tO8‡ ‰ % €Ÿ€˜€‚˙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Œ‡ AŠ % €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.kF‰ Ź‹ % €€˜€‚˙Single-DES is not recommended in the SSH 2 draft protocol standards, but one or two server implementations do support it. PuTTY can use single-DES to interoperate with these servers if you enable the ‘Enable legacy use of single-DES in SSH 2’ option; by default this is disabled and PuTTY will stick to recommended ciphers.}LAŠ )Œ 1ß( ’)Œ sŒ  Section 4.18: The Auth panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")J!Ź‹ sŒ ) "€B€€€€‚˙Section 4.18: The Auth panelvR)Œ éŒ $ €¤€˜€‚˙The Auth panel allows you to configure authentication options for SSH sessions.pAsŒ Y / .€‚€ă´—€€€‰‚˙Section 4.18.1: ‘Attempt TIS or CryptoCard authentication’sDéŒ Ě / .€ˆ€ăâ˘K!€€€‰‚˙Section 4.18.2: ‘Attempt keyboard-interactive authentication’^/Y *Ž / .€^€ăĘ6ĘĀ€€‰‚˙Section 4.18.3: ‘Allow agent forwarding’sD̍ Ž / .€ˆ€ăU €€€‰‚˙Section 4.18.4: ‘Allow attempted changes of username in SSH2’k<*Ž  / .€x€ă„@Ď؀€€‰‚˙Section 4.18.5: ‘Private key file for authentication’›jŽ Ł 1j¸‚“Ł Ŕ Ă Section 4.18.1: ‘Attempt TIS or CryptoCard authentication’CBB("btn_up","JI(`',`t00000060')");EB("btn_up")h? Ŕ ) "€~€€€€‚˙Section 4.18.1: ‘Attempt TIS or CryptoCard authenŁ Ŕ  tication’T/Ł kÁ % €_€˜€‚˙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.Ž‰Ŕ Ă % €€˜€‚˙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.žmkÁ ˇĂ 1“( ل”ˇĂ "Ä JĆ Section 4.18.2: ‘Attempt keyboard-interactive authentication’CBB("btn_up","JI(`',`t00000060')");EB("btn_up")kBĂ "Ä ) "€„€€€€‚˙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.Ą}"Ä JĆ $ €ú€˜€‚˙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(¸‚|†•ÓĆ )Ç űČ Section 4.18.3: ‘Allow agent forwarding’CBB("btn_up","JI(`',`t00000060')");EB("btn_up")V-JĆ )Ç ) "€Z€€€€‚˙Section 4.18.3: ‘Allow agent forwarding’ČŁÓĆ ńÇ % €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. Ó)Ç űČ 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.žmńÇ ™É 1]ل;Š–™É Ę öÍ Section 4.18.4: ‘Allow attempted changes of username in SSH2’CBB("btn_up","JI(`',`t00000060')");EB("btn_up")kBűČ Ę ) "€„€€€€‚˙Section 4.18.4: ‘Allow attempted changes of username in SSH2’Ü™É Ë % €š€˜€‚˙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.Í˘Ę ŇĚ + $€E€˜€€€‚˙The SSH 2 protocol does allow changes of username, in principle, but does not make it mandatory for SSH 2 servers to accept 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.)$˙Ë öÍ % €˙€˜€‚˙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.–eŇĚ ŒÎ 1Ł|†—ŒÎ ďÎ ; Section 4.18.5: ‘Private key file for authentication’CBB("btn_up","JI(`',`t00000060')");EB("btn_up")c:öÍ ďÎ ) "€t€€€€‚˙Section 4.18.5: ‘Private key file for authentication’ß´ŒÎ ÎĎ + $€i€˜€ă{ƒů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.a7ďÎ ; * $€n€˜€€€‚˙This keÎĎ ; öÍ y must be in PuTTY's native format (*.PPK).€OÎĎ ť 1ů;Š˜ť  ´ Section 4.19: The Tunnels panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")M$;  ) "€H€€€€‚˙Section 4.19: The Tunnels panellť ˜ $ €Ř€˜€‚˙The Tunnels panel allows you to configure tunnelling of other connection types through an SSH connection.T% ě / .€J€ăwŃJś€€€‰‚˙Section 4.19.1: X11 forwardingU&˜ A / .€L€ăíˆĆ#€€€‰‚˙Section 4.19.2: Port forwardingsDě ´ / .€ˆ€ăČ6çY€€€‰‚˙Section 4.19.3: Controlling the visibility of forwarded portsNA 3 1p™3  P Section 4.19.1: X11 forwardingCBB("btn_up","JI(`',`t00000061')");EB("btn_up")L#´  ) "€F€€€€‚˙Section 4.19.1: X11 forwardingǢ3 F % €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.@ † % €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?F ď * $€~€˜€ăĽÄůN‰‚˙See section 3.4 for more information about X11 forwarding.a2† P / .€d€ăk Z܀€€‰‚˙Section 4.19.1.1: Remote X11 authentication’aď â 1¨ l€šâ ; ˘@ Section 4.19.1.1: Remote X11 authenticationCBB("btn_up","JI(`',`ssh.tunnels.x11')");EB("btn_up")Y0P ; ) "€`€€€€‚˙Section 4.19.1.1: Remote X11 authenticationÖąâ  % €c€˜€‚˙If you are using X11 forwarding, the virtual X server created on the SSH server machine will be protected by authorisation data. This data is invented, and checked, by PuTTY.Á–; Ň + $€-€˜€€€‚˙The usual authorisation method used for this is called MIT-MAGIC-COOKIE-1. This is a simple password-style protocol: the X client sends some cookie data to the server, and the server checks that it matches the real cookie. The cookie data is sent over an unencrypted X11 connection; so if you allow a client on a third machine to access the virtual X server, then the cookie will be sent in the clear.Ďž Ą 1 0€=€˜€€€€€‚˙PuTTY offers the alternative protocol XDM-AUTHORIZATION-1. This is a cryptographically authenticated protocol: the data sent by the X client is different every time, and it depends on the IP address and port of the client's end of the connection and is also stamped with the current time. So an eavesdropper who captures an XDM-AUTHORIZATION-1 string cannot immediately re-use it for their own X connection.žtŇ ? * $€č€˜€€€‚˙PuTTY's support for XDM-AUTHORIZATION-1 is a somewhat experimental feature, and may encounter several problems:ż‹Ą ţ 4 6€€T˜‘€8‚€ƒ€€€‚˙•Some X clients probably do not even support XDM-AUTHORIZATION-1, so they will not know what to do with the data PuTTY has provided.,ř? * 4 6€ń€T˜‘€8‚€ƒ€€€‚˙•This authentication mechanism will only work in SSH v2. In SSH v1, the SSH server does not tell the client the source address of a forwarded connection in a machine-readable format, so it's impossible to verify the XDM-AUTHORIZATION-1 data.ʐţ @ : B€!€T˜‘€8‚€ƒ€€€€€‚˙•You may find this feature causes problems with some SSH servers, which will not clean up XDM-AUTHORIZATION-1 data after a session, so that if you then connect to the same server using a client which only does MIT-MAGIC-COOKIE-1 and are allocated the same remote display number, you might find that out-of-date authentication data is still present on your server and your X connections fail.* @ P –l* ˘@ * $€Ř€˜€€€‚˙PuTTY's default is MIT-MAGIC-COOKIE-1. If you change it, you should be sure you know what you're doing.€O @ "A 1ľpr‡›"A oA ×I Section 4.19.2: Port forwardingCBB("btn_up","JI(`',`t00000061')");EB("btn_up")M$˘@ oA ) "€H€€€€‚˙Section 4.19.2: Port forwardingŮŽ"A HB + $€]€˜€ăŚÄů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.ÜoA IC % €š€˜€‚˙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.@HB ‰C $ €8€˜€‚˙To add a port forwarding:b4IC ëD . *€i€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’). Alternatively, select ‘Dynamic’ if you want PuTTY to provide a local SOCKS 4/4A/5 proxy on a local port.X*‰C CF . *€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.ƒOëD ĆG 4 6€Ÿ€T˜‘€8‚€ƒ€€€‚˙•If you have selected ‘Local’ or ‘Remote’ (this step is not needed with ‘Dynamic’), 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, to connect to a POP-3 server, you might enter popserver.example.com:110.TCF GH - *€¨€T˜‘€8‚€ƒ€‚˙•Click the ‘Add’ button. Your forwarding details should appear in the list box.iĆG ÔH $ €Ň€˜€‚˙To remove a port forwarding, simply select its details in the list box, and click the ‘Remove’ button.ŇGH ×I 1 0€Ľ€˜€€€ăŚÄůN‰‚˙In the ‘Source port’ box, you can also optionally enter an IP address to listen on, by specifying (for instance) 127.0.0.5:79. See section 3.5 for more information on how this works and its restrictions.žmÔH uJ 1.l€öŠœuJ ŕJ ŁN Section 4.19.3: Controlling the visibility of forwarded portsCBB("btn_up","JI(`',`t00000061')");EB("btn_up")kB×I ŕJ ) "€„€€€€‚˙Section 4.19.3: Controlling the visibility of forwarded portsúuJ ˙K % €ő€˜€‚˙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:0ŕJ /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. (This also applies to dynamic SOCKS forwarding.)tF˙K ŁN . *€€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/M O 1r‡! O jO ɇ Section 4.20: The Bugs panelCBB("btn_up","JI(`',`t00000044')");EB("btn_up")J!ŁN jO ) "€B€€€€‚˙Section 4.20: The Bugs panelăž O Y€ % €}€˜€‚˙Not all SSH servers work properly. Various existing servers have bugs in them, which can make it impossible for jO Y€ ŁN a client to talk to them unless it knows about the bug and works around it.îÉjO G‚ % €“€˜€‚˙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.°‹Y€ ÷‚ % €€˜€‚˙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@G‚ dƒ - *€€€T˜‘€8‚€ƒ€‚˙•‘Off’: PuTTY will assume the server does not have the bug.p=÷‚ ԃ 3 6€z€T˜‘€8‚€ƒ€€€‚˙•‘On’: PuTTY will assume the server does have the bug.Š|dƒ }„ - *€ř€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ԃ ㄠ/ .€n€ă‚îC€€€‰‚˙Section 4.20.1: ‘Chokes on SSH1 ignore messages’l=}„ O… / .€z€ă=0€€€‰‚˙Section 4.20.2: ‘Refuses all SSH1 password camouflage’i:ㄠ¸… / .€t€ă‚-‘€€€‰‚˙Section 4.20.3: ‘Chokes on SSH1 RSA authentication’b3O… † / .€f€ă‚ľQ€€€‰‚˙Section 4.20.4: ‘Miscomputes SSH2 HMAC keys’h9¸… ‚† / .€r€ăďÜ7Y€€€‰‚˙Section 4.20.5: ‘Miscomputes SSH2 encryption keys’o@† ń† / .€€€ăš§žč€€€‰‚˙Section 4.20.6: ‘Requires padding on SSH2 RSA signatures’o@‚† `‡ / .€€€ă˝TŻó€€€‰‚˙Section 4.20.7: ‘Chokes on Diffie-Hellman group exchange’i:ń† ɇ / .€t€ăUĐ8€€€‰‚˙Section 4.20.8: ‘Misuses the session ID in PK auth’‘``‡ Zˆ 1šöŠ žZˆ ¸ˆ ôŒ Section 4.20.1: ‘Chokes on SSH1 ignore messages’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")^5ɇ ¸ˆ ) "€j€€€€‚˙Section 4.20.1: ‘Chokes on SSH1 ignore messages’éžZˆ ĄŠ + $€}€˜€ăęřÂk‰‚˙An ignore message (SSH_MSG_IGNORE) is a message in the 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).ŃŚ¸ˆ rŒ + $€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.—frŒ ‹ 1ž!ąŸ‹ ď U Section 4.20.2: ‘Refuses all SSH1 password camouflage’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")d;ôŒ ď ) "€v€€€€‚˙Section 4.20.2: ‘Refuses all SSH1 password camouflage’`/‹ [Ŕ 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 dď [Ŕ ôŒ oes 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.pL[Ŕ U $ €˜€˜€‚˙This is an SSH1-specific bug. SSH2 is secure against this type of attack.”cĺÁ é 1Ö đƒ é JĂ żĹ Section 4.20.3: ‘Chokes on SSH1 RSA authentication’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")a8U JĂ ) "€p€€€€‚˙Section 4.20.3: ‘Chokes on SSH1 RSA authentication’6é €Ä % €#€˜€‚˙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.űÖJĂ {Ĺ % €­€˜€‚˙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 €Ä żĹ $ €@€˜€‚˙This is an SSH1-specific bug.\{Ĺ LĆ 1칁?†ĄLĆ ŚĆ 8É Section 4.20.4: ‘Miscomputes SSH2 HMAC keys’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")Z1żĹ ŚĆ ) "€b€€€€‚˙Section 4.20.4: ‘Miscomputes SSH2 HMAC keys’HLĆ îÇ + $€;€˜€€€‚˙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 îÇ 8É $ €@€˜€‚˙This is an SSH2-specific bug.“bôČ ËÉ 1Üđƒ~ˆ˘ËÉ +Ę §Ě Section 4.20.5: ‘Miscomputes SSH2 encryption keys’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")`78É +Ę ) "€n€€€€‚˙Section 4.20.5: ‘Miscomputes SSH2 encryption keys’,ËÉ WË + $€€˜€€€‚˙Versions below 2.0.11 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’. ç+Ę cĚ % €Ď€˜€‚˙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 WË §Ě $ €@€˜€‚˙This is an SSH2-specific bug.šicĚ AÍ 1’?† ŁAÍ ¨Í ß Section 4.20.6: ‘Requires padding on SSH2 RSA signatures’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")g>§Ě ¨Í ) "€|€€€€‚˙Section 4.20.6: ‘Requires padding on SSH2 RSA signatures’Ą|AÍ IĎ % €ů€˜€‚˙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 isIĎ › §Ě likely that no damage will be done, since correct servers usually still accept padded signatures because they're used to talking to OpenSSH.D IĎ ß $ €@€˜€‚˙This is an SSH2-specific bug.ši› y 1#~ˆŚ¤y ŕ œ Section 4.20.7: ‘Chokes on Diffie-Hellman group exchange’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")g>ß ŕ ) "€|€€€€‚˙Section 4.20.7: ‘Chokes on Diffie-Hellman group exchange’d?y 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.éŕ X + $€Ó€˜€€€‚˙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 D œ $ €@€˜€‚˙This is an SSH2-specific bug.”cX 0 1@ IĽ0 ‘ p Section 4.20.8: ‘Misuses the session ID in PK auth’CBB("btn_up","JI(`',`t00000062')");EB("btn_up")a8œ ‘ ) "€p€€€€‚˙Section 4.20.8: ‘Misuses the session ID in PK auth’Çœ0 X + $€9€˜€ă{ÄůN‰‚˙Versions below 2.3 of OpenSSH require SSH2 public-key authentication to be done slightly differently: the data to be signed by the client contains the session ID formatted in a different way. If public-key authentication mysteriously does not work but the Event Log (see section 3.1.3.1) thinks it has successfully sent a signature, it might be worth enabling the workaround for this bug to see if it helps.ÔŻ‘ , % €_€˜€‚˙If this bug is detected, PuTTY will sign data in the way OpenSSH expects. If this bug is enabled when talking to a correct server, SSH2 public-key authentication will fail.D X p $ €@€˜€‚˙This is an SSH2-specific bug.Ž], ţ 1 Ś8Śţ Y B Section 4.21: Storing configuration in a fileCBB("btn_up","JI(`',`t00000044')");EB("btn_up")[2p Y ) "€d€€€€‚˙Section 4.21: Storing configuration in a fileĹ ţ  % €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.NY  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:/  Ě # €€€‚˙@ECHO OFF:  # €.€€‚˙regedit /s putty.reg=Ě C # €4€€‚˙regedit /s puttyrnd.reg8 { # €*€€‚˙start /w putty.exekHC ć # €€€‚˙regedit /ea puttynew.reg HKEY_CURRENT_USER\Software\SimonTatham\PuTTYA{ ' # €<€€‚˙copy puttynew.reg putty.reg6ć ] # €&€€‚˙del puttynew.reg>' › $ €4€˜€‚˙regedit /s puttydel.reg1ú] Ě 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›  * $€4€˜€€€‚˙Here is PUTTYDEL.REG:. Ě > # €€€‚˙REGEDIT4' e # €€€‚˙ V2> ť $ €d€˜€‚˙[-HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]T*e @ * $€T€˜€€€‚˙Here is an example PUTTYRť @ p ND.REG file:. ť I@ # €€€‚˙REGEDIT4'@ p@ # €€€‚˙ T1I@ Ä@ # €b€€‚˙[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY]D p@ A $ €@€˜€‚˙"RandSeedFile"="a:\putty.rnd"ŘÄ@ B + $€ą€˜€€€‚˙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.‹ZA –B 1°Iェ–B ôB FE Chapter 5: Using PSCP to transfer files securelyCBB("btn_up","JI(`',`Top')");EB("btn_up")^5 B ôB ) "€j€€€€‚˙Chapter 5: Using PSCP to transfer files securelyŸ{–B “C $ €ö€˜€‚˙PSCP, the PuTTY Secure Copy client, is a tool for transferring files securely between computers using an SSH connection.ęôB WD + $€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!“C §D / .€B€ăSĹůN€€€‰‚˙Section 5.1: Starting PSCPMWD ôD / .€<€ăTĹůN€€€‰‚˙Section 5.2: PSCP UsageR#§D FE / .€F€ă‚ĹůN€€€‰‚˙Section 5.3: Secure iXplorer{JôD ÁE 1i8r†¨ÁE F *J Section 5.1: Starting PSCPCBB("btn_up","JI(`',`t00000064')");EB("btn_up")HFE F ) "€>€€€€‚˙Section 5.1: Starting PSCPƒ^ÁE ŒG % €˝€˜€‚˙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.đż F |H 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-ŒG ÍH $ €Z€˜€‚˙set PATH=C:\path\to\putty\directory;%PATH%]&|H *J 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ÍH ˘J 1 ă‚Š˘J çJ ك Section 5.2: PSCP UsageCBB("btn_up","JI(`',`t00000064')");EB("btn_up")E*J çJ ) "€8€€€€‚˙Section 5.2: PSCP UsageŐ˘J çK + $€Ť€˜€€€‚˙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:8çJ L # €*€€‚˙Z:\owendadmin>pscp>çK ]L # €6€€‚˙PuTTY Secure Copy client2L L # €€€‚˙Release 0.54U2]L äL # €d€€‚˙Usage: pscp [options] [user@]host:source targeta>L EM # €|€€‚˙ pscp [options] source [source...] [user@]host:targetR/äL —M # €^€€‚˙ pscp [options] -ls user@host:filespec. EM ĹM # €€€‚˙Options:J'—M N # €N€€‚˙ -p preserve file attributesN+ĹM ]N # €V€€‚˙ -q quiet, don't show statisticsN+N ŤN # €V€€‚˙ -r copy directories recursivelyG$]N ňN # €H€€‚˙ -v show verbose messagesX5ŤN JO # €j€€‚˙ -load sessname Load settings from saved sessionK(ňN •O # €P€€‚˙ -P port connect to specified portQ.JO € # €\€€‚˙ -l user connect with specified username•O € *J O,•O [€ # €X€€‚˙ -pw passw login with specified password^; € š€ # €v€€‚˙ -1 -2 force use of particular SSH protocol versionD![€ ý€ # €B€€‚˙ -C enable compressionU2š€ R # €d€€‚˙ -i key private key file for authenticationQ.ý€ Ł # €\€€‚˙ -batch disable all interactive promptsZ6R ý $ €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 ý ΂ / .€@€ăUĹůN€€€‰‚˙Section 5.2.1: The basicsL‚ ƒ / .€:€ă{ĹůN€€€‰‚˙Section 5.2.2: OptionsQ"΂ kƒ / .€D€ă€ĹůN€€€‰‚˙Section 5.2.3: Return valuen?ƒ ك / .€~€ăĹůN€€€‰‚˙Section 5.2.4: Using public key authentication with PSCPzIkƒ S„ 1žr†îŞS„ š„ ý Section 5.2.1: The basicsCBB("btn_up","JI(`',`t00000066')");EB("btn_up")Gك š„ ) "€<€€€€‚˙Section 5.2.1: The basicsS/S„ í„ $ €^€˜€‚˙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=<… c† $ €z€˜€‚˙pscp fred@example.com:/etc/hosts c:\temp\example-hosts.txtN*† ą† $ €T€˜€‚˙To send (a) file(s) to a remote server:[7c† ‡ $ €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 ‡ Dˆ $ €ˆ€˜€‚˙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:W4Dˆ ‰ # €h€€‚˙pscp c:\documents\*.doc fred@example.com:docfilesQ-ťˆ c‰ $ €Z€˜€‚˙pscp fred@example.com:source/*.c c:\sourcel‰ ó‰ $ €Ř€˜€‚˙However, in the second case (using a wildcard for multiple remote files) you may see a warning like this:gDc‰ ZŠ # €ˆ€€‚˙warning: remote host tried to write to a file called 'terminal.c'U2ó‰ ŻŠ # €d€€‚˙ when we requested a file called '*.c'.jGZŠ ‹ # €Ž€€‚˙ 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@examplÏ (Ŕ ك e.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€ăVĹůN€€€‰‚˙Section 5.2.1.1: userKÍÁ c / .€8€ăWĹůN€€€‰‚˙Section 5.2.1.2: hostM °Â / .€<€ăƒĹůN€€€‰‚˙Section 5.2.1.3: sourceMc ý / .€<€ăzĹůN€€€‰‚˙Section 5.2.1.4: targetvE°Â sĂ 1Jä‚ŤsĂ śĂ ˝Ä Section 5.2.1.1: userCBB("btn_up","JI(`',`t00000067')");EB("btn_up")Cý śĂ ) "€4€€€€‚˙Section 5.2.1.1: userÜsĂ ˝Ä + $€š€˜€€€‚˙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śĂ 3Ĺ 1&ƒŹ3Ĺ vĹ YĆ Section 5.2.1.2: hostCBB("btn_up","JI(`',`t00000067')");EB("btn_up")C˝Ä vĹ ) "€4€€€€‚˙Section 5.2.1.2: hostăž3Ĺ YĆ % €}€˜€‚˙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.xGvĹ ŃĆ 1!ä‚@†­ŃĆ Ç ňÉ Section 5.2.1.3: sourceCBB("btn_up","JI(`',`t00000067')");EB("btn_up")EYĆ Ç ) "€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ŘČ jĘ 1ôźƒgˆŽjĘ ŻĘ ^Í Section 5.2.1.4: targetCBB("btn_up","JI(`',`t00000067')");EB("btn_up")EňÉ ŻĘ ) "€8€€€€‚˙Section 5.2.1.4: targetăjĘ ˝Ë + $€Ç€˜€€€‚˙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.ÖŤ Ě ^Í + $€W€˜€€€‚˙As with the source parameter, if the target is on a remote server and is 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(`',`t00000066')");EB("btn_up")D^Í Î ) "€6€€€€‚˙Section 5.2.2: Options*˙ŐÍ CĎ + $€˙€˜€ăŤÄů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.\8CĎ C $ €p€˜€‚˙ŰĎ C ^Í These are the command line options that PSCP accepts.f4ŰĎ Š 2 4€h€ă|ĹůN€€€€‰‚˙Section 5.2.2.1: -p preserve file attributesj8C  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\ w 1)gˆą°w Ő   Section 5.2.2.1: -p preserve file attributesCBB("btn_up","JI(`',`t00000072')");EB("btn_up")^2ę Ő , (€d€€€€€‚˙Section 5.2.2.1: -p preserve file attributesË w   + $€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.‘`Ő 1 1ŕßňą1 “  Section 5.2.2.2: -q quiet, don't show statisticsCBB("btn_up","JI(`',`t00000072')");EB("btn_up")b6  “ , (€l€€€€€‚˙Section 5.2.2.2: -q quiet, don't show statisticsyU1  $ €Ş€˜€‚˙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Çąb˛¤  k Section 5.2.2.3: -r copies directories recursivelyCBB("btn_up","JI(`',`t00000072')");EB("btn_up")d8  , (€p€€€€€‚˙Section 5.2.2.3: -r copies directories recursivelyc8¤ k + $€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ňPłý ` s Section 5.2.2.4: -batch avoid interactive promptsCBB("btn_up","JI(`',`t00000072')");EB("btn_up")c7k ` , (€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.Ř­` s + $€[€˜€€€‚˙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˘bW´ď 8 ‘ Section 5.2.3: Return valueCBB("btn_up","JI(`',`t00000066')");EB("btn_up")I s 8 ) "€@€€€€‚˙Section 5.2.3: Return valueʟď  + $€?€˜€€€‚˙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:A8 C # €<€€‚˙pscp file*.* user@hostname:N* ‘ $ €T€˜€‚˙if errorlevel 1 echo There was an error™hC * 1§P&„ľ*  ÝE Section 5.2.4: Using public key authentication with PSCPCBB("btn_up","JI(`',`t00000066')");EB("btn_up")f=‘  ) "€z€€€€‚˙Section 5.2.4: Using public key authentication with PSCP˜t* 4@ $ €č€˜€‚˙Like PuTTY, PSCP can authenticate using a public key instead of a password. 4@ ‘ There are three ways you can do this.œr Đ@ * $€ä€˜€ăWĹůN‰‚˙Firstly, PSCP can use PuTTY saved sessions in place of hostnames (see section 5.2.1.2). So you would do this:Ü4@ ěA @ 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).ň¸Đ@ ŢB : 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.ÒěA ĄC 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ŢB ED * $€ô€˜€ă80Ťf‰‚˙Thirdly, PSCP will attempt to authenticate using Pageant if Pageant is running (see chapter 9). So you would do this:tGĄC šD - *€Ž€T˜‘€8‚€ƒ€‚˙•Ensure Pageant is running, and has your private key stored in it.ŹED eE - *€ţ€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šD ÝE * $€œ€˜€ă{ƒůN‰‚˙For more general information on public-key authentication, see chapter 8.}LeE ZF 1ŕWš„śZF ¤F :G Section 5.3: Secure iXplorerCBB("btn_up","JI(`',`t00000064')");EB("btn_up")J!ÝE ¤F ) "€B€€€€‚˙Section 5.3: Secure iXplorer–rZF :G $ €ä€˜€‚˙Lars Gunnarson has written a graphical interface for PSCP. You can get it from his web site, at www.i-tree.org.Œ[¤F ĆG 1&„RˆˇĆG %H ËL Chapter 6: Using PSFTP to transfer files securelyCBB("btn_up","JI(`',`Top')");EB("btn_up")_6:G %H ) "€l€€€€‚˙Chapter 6: Using PSFTP to transfer files securely™uĆG žH $ €ę€˜€‚˙PSFTP, the PuTTY SFTP client, is a tool for transferring files securely between computers using an SSH connection.U1%H I $ €b€˜€‚˙PSFTP differs from PSCP in the following ways:ęžH +J . *€Ő€T˜‘€8‚€ƒ€‚˙•PSCP should work on virtually every SSH server. PSFTP uses the new SFTP protocol, which is a feature of SSH 2 only. (PSCP will also use this protocol if it can, but there is an SSH 1 equivalent it can fall back to if it cannot.)’RI ˝K @ N€Ľ€T˜‘€8‚€ƒ€€€€€€€‚˙•PSFTP allows you to run an interactive file transfer session, much like the Windows ftp program. You can list the contents of directories, browse around the file system, issue multiple get and put commands, and eventually log out. By contrast, PSCP is designed to do a single file transfer operation and immediately terminate.Q"+J L / .€D€ăĽĹůN€€€‰‚˙Section 6.1: Starting PSFTPP!˝K ^L / .€B€ăŞĹůN€€€‰‚˙Section 6.2: Running PSFTPm>L ËL / .€|€ăü„ůN€€€‰‚˙Section 6.3: Using public key authentication with PSFTP|K^L GM 1űš„,¸GM M \† Section 6.1: Starting PSFTPCBB("btn_up","JI(`',`t00000080')");EB("btn_up")I ËL M ) "€@€€€€‚˙Section 6.1: Starting PSFTP6GM ĆN 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-M O $ €Z€˜€‚˙set PATH=C:\path\to\putty\directory;%PATH%œxĆN łO $ €đ€˜€‚˙Unlike PSCP, however, PSFTP has no complex command-line syntax; you just specify a host name and perhaps a user name:?O € $ €6€˜€‚˙psftp server.example.comłO € ËL 1 łO =€ $ €€˜€‚˙or perhapsD € € $ €@€˜€‚˙psftp fred@server.example.comőĘ=€ v + $€•€˜€€€‚˙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@v ‚ # €€€€‚˙psftp: no hostname specified; use "open host.name" to connect- Ľ 5‚ $ €€˜€‚˙psftp>m‚ ҂ 0 0€Ú€˜€€€€€‚˙At this point you can type open server.example.com or open fred@server.example.com to start a session.,5‚ ţƒ + $€€˜€ăŤÄů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ţƒ … 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? … ň… 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ň… ř† 1jRˆÉšř† e‡ bŒ Section 6.1.1: -b: specify a file containing batch commandsCBB("btn_up","JI(`',`t00000081')");EB("btn_up")mA\† e‡ , (€‚€€€€€‚˙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.~Me‡ „‰ 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 Á‰ <Š # €@€€‚˙ren jam.tar.gz jam-old.tar.gz4ů‰ pŠ # €"€€‚˙put jam.tar.gz:<Š ŞŠ # €.€€‚˙chmod a+r jam.tar.gz+pŠ Պ $ €€˜€‚˙quitR.ŞŠ '‹ $ €\€˜€‚˙and then you could run the script by typingJ&Պ q‹ $ €L€˜€‚˙psftp user@hostname -b myscript.scrńŔ'‹ bŒ 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).›jq‹ ýŒ 1,‹‚şýŒ i ŠÄ Section 6.1.2: -bc: display batch commands as they are runCBB("btn_up","JI(`',`t00000081')");EB("btn_up")l@bŒ i , (€€€€€€€‚˙Section 6.1.2: -bc: display batch commands as they are runáýŒ {Ž 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::i ľŽ # €.€€‚˙Sent username "fred"L){Ž  # €R€€‚˙Remote working directory is /home/fredF#ľŽ G # €F€€‚˙Listing directory /home/fred/lib_< Ś # €x€€‚˙drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 .`=G Ŕ # €z€€‚˙drwxr-sr-x 25 fred fred 2048 Dec 14 09:3Ś Ŕ bŒ 6 ..a>Ś sŔ # €|€€‚˙drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jeddAŔ ×Ŕ # €‚€€‚˙lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timberb>sŔ 9Á $ €|€˜€‚˙drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn:×Ŕ sÁ $ €,€˜€‚˙you might see this::9Á ­Á # €.€€‚˙Sent username "fred"L)sÁ ůÁ # €R€€‚˙Remote working directory is /home/fred4­Á - # €"€€‚˙psftp> dir libF#ůÁ s # €F€€‚˙Listing directory /home/fred/lib_<- Ň # €x€€‚˙drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 .`=s 2Ă # €z€€‚˙drwxr-sr-x 25 fred fred 2048 Dec 14 09:36 ..a>Ň “Ă # €|€€‚˙drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jeddA2Ă ÷Ă # €‚€€‚˙lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timbera>“Ă XÄ # €|€€‚˙drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn2÷Ă ŠÄ $ €€˜€‚˙psftp> quit˜gXÄ "Ĺ 1ŤÉƒť"Ĺ ‹Ĺ ÍĆ Section 6.1.3: -be: continue batch processing on errorsCBB("btn_up","JI(`',`t00000081')");EB("btn_up")i=ŠÄ ‹Ĺ , (€z€€€€€‚˙Section 6.1.3: -be: continue batch processing on errorsŁ"Ĺ .Ć $ €ţ€˜€‚˙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.‘`.Ć ^Ç 1w‹‚ą…ź^Ç ŔÇ ŐÉ Section 6.1.4: -batch: avoid interactive promptsCBB("btn_up","JI(`',`t00000081')");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üČ PĘ 1ĎƒĐ˝PĘ ˜Ę OSection 6.2: Running PSFTPCBB("btn_up","JI(`',`t00000080')");EB("btn_up")HŐÉ ˜Ę ) "€>€€€€‚˙Section 6.2: Running PSFTPäšPĘ |Ë + $€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|Ë WĚ 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 sessiont?WĚ :Í 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:Í aÎ ; 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 serverwBaÎ RĎ 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 transfersRĎ ŐÉ p;RĎ |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=|q5 :€z€ă×ĹůN€€€€€‰‚˙Section 6.2.12: The del command: delete remote fileszE˙ë5 :€Š€ăŘĹůN€€€€€‰‚˙Section 6.2.13: The mkdir command: create remote directorieszEqe5 :€Š€ă…ůN€€€€€‰‚˙Section 6.2.14: The rmdir command: remove remote directoriesr=ë×5 :€z€ăú„ůN€€€€€‰‚˙Section 6.2.15: The ren command: rename remote filesxCeO5 :€†€ăű„ůN€€€€€‰‚˙Section 6.2.16: The ! command: run a local Windows command˜g×ç1uą…şžçL\ Section 6.2.1: General quoting rules for PSFTP commandsCBB("btn_up","JI(`',`t00000086')");EB("btn_up")e<OL) "€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).ţÓLÎ+ $€§€˜€€€‚˙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Đ4$ €„€˜€‚˙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.!ö46 + $€í€˜€€€‚˙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"äł6 s 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.鸏 \ 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.)‘`s í 1_ĐW żí S LSection 6.2.2: The open command: start a sessionCBB("btn_up","JI(`',`t00000086')");EB("btn_up")f7\ S / .€n€€€€€€‚˙Section 6.2.2: The open command: start a sessionŢí h 7 <€˝€˜€€€€€€€‚˙If you started PSFTP by double-clicking in the GUI, or just by typing psftp at the command line, you will need to open a connection to an SFTP server before you can issue any other commands (except help and quit).´ƒS 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.0h L+ $€ €˜€€€‚˙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 @1ŇşHŔ @s@ŢASection 6.2.3: The quit command: end your sessionCBB("btn_up","JI(`',`t00000086')");EB("btn_up")L @Lg8Ls@/ .€p€€€€€€‚˙Section 6.2.3: The quit command: end your sessionĺş @XA+ $€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).†Vs@ŢA0 0€Ź€˜€€€€€‚˙You can also use the bye and exit commands, which have exactly the same effect.—fXAuB1ĄW _‚ÁuBáBDSection 6.2.4: The help command: get quick online helpCBB("btn_up","JI(`',`t00000086')");EB("btn_up")l=ŢAáB/ .€z€€€€€€‚˙Section 6.2.4: The help command: get quick online helpxNuBYC* $€œ€˜€€€‚˙If you type help, PSFTP will give a short list of the available commands.˝ŒáBD1 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.Ž}YCÄD1xHA„ÂÄDOE ÄDF1 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.ŻOE€˜€‚˙reget myfile.dat newname.dat“bą…‡†1;PĎLJ†ď†ˆSection 6.2.10: The dir command: list remote filesCBB("btn_up","JI(`',`t00000086')");EB("btn_up")h9ô…ď†/ .€r€€€€€€‚˙Section 6.2.10: The dir command: list remote filesqG‡†`‡* $€Ž€˜€€€‚˙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:4`‡(ˆ# €"€€‚˙dir /home/fred2ô‡Zˆ$ €€˜€‚˙dir sourcesh8(ˆˆ0 0€p€˜€€€€€‚˙The ls command works exactly the same way as dir.ŚuZˆh‰1A ŽĄČh‰ă‰ľĆSection 6.2.11: The chmod command: change permissions on remote filesCBB("btn_up","JI(`',`t00000086')");EB("btn_up"){Lˆă‰/ .€˜€€€€€€‚˙Section 6.2.11: The chmod command: change permissions on remote files׌h‰şŠ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:ыEŒ$ €,€˜€‚˙chmod 640 groupfile1 Œv+ $€ €˜€€€‚˙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 want to be using it!) Alternatively, it can be a list of permission modifications, separated by commas. Each modification consists of:4îEŒގ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.ŒSv6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), 6‡Ŕˆand x (permission to execute the file, or in the case of a directory, permission to access files within the directory).F"6ÍŔ$ €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ÍŔmÂ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:üÂmÂÄ: 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+ĂyĹ: 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).•dyĹJÇ1vύ…ÉJÇ´ÇŔČSection 6.2.12: The del command: delete remote filesCBB("btn_up","JI(`',`t00000086')");EB("btn_up")j;ľĆ´Ç/ .€v€€€€€€‚˙Section 6.2.12: The del command: delete remote filesnDJÇ"Č* $€ˆ€˜€€€‚˙To delete a file on the server, type del and then the filename:6´ÇXČ$ €$€˜€‚˙del oldfile.dath8"ČŔČ0 0€p€˜€€€€€‚˙The rm command works exactly the same way as del.lXČ]É1"Ą2†Ę]ÉĎÉĘSection 6.2.13: The mkdir command: create remote directoriesCBB("btn_up","JI(`',`t00000086')");EB("btn_up")rCŔČĎÉ/ .€†€€€€€€‚˙Section 6.2.13: The mkdir command: create remote directories{Q]ÉJĘ* $€˘€˜€€€‚˙To create a directory on the server, type mkdir and then the directory name:5ĎÉĘ$ €"€˜€‚˙mkdir newstufflJĘË1ڍ…j‡ËËŽËöĚSection 6.2.14: The rmdir command: remove remote directoriesCBB("btn_up","JI(`',`t00000086')");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ŽË>Ě$ €"€˜€‚˙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 first.•d>Ě‹Í1Ż2†fˆ̋ÍőÍ:ĎSection 6.2.15: The ren command: rename remote filesCBB("btn_up","JI(`',`t00000086')");EB("btn_up")j;öĚőÍ/ .€v€€€€€€‚˙Section 6.2.15: The ren command: rename remote filesf‹Í…Î* $€Ě€˜€€€‚˙To rename a file on the server, type ren, then the current file name, and then the new file name::őÍżÎ$ €,€˜€‚˙ren oldfile newname{E…Î:Ď6 <€Š€˜€€€€€€€‚˙The rename and mv commands work exactly the same way as ren.›jżÎ 1tj‡xÍ |€Section 6.2.16: The ! command: run a local Windows commandCBB("btn_up","JI(`',`t00000086')");EB("btn_up"):Ď :ĎpA:Ď|/ .€‚€€€€€€‚˙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.Š„|% € €˜€‚˙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<$ €0€˜€‚˙psftp> get myfile.datnDÖ€* $€ˆ€˜€€€‚˙using the Windows ren command to rename files on your local PC.˜g1˝fˆ›Î}Ő Section 6.3: Using public key authentication with PSFTPCBB("btn_up","JI(`',`t00000080')");EB("btn_up")e<€}) "€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.[}“$ €ś€˜€‚˙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).嫓”: 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:tG”Ž- *€Ž€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ŽŐ * $€œ€˜€ă{ƒůN‰‚˙For more general information on public-key authentication, see chapter 8.’a] g 1‡xżĎg Ě î 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ŕľg Ź + $€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Ě 5 $ €Ę€˜€‚˙Plink is probably not what you want if you want to run an interactive session in a console window.Q"Ź † / .€D€ăţ„ůN€€€‰‚˙Section 7.1: Starting PlinkN5 Ô / .€>€ă˙„ůN€€€‰‚˙Section 7.2: Using Plinki:† = / .€t€ăxƒůN€€€‰‚˙Section 7.3: Using Plink in batch files and scriptsW(Ô ” / .€P€ăyƒůN€€€‰‚˙Section 7.4: Using Plink with CVSZ+= î / .€V€ăzƒůN€€€‰‚˙Section 7.5: Using Plink with WinCVS|K” j1Š›.‚ĐjłCSection 7.1: Starting PlinkCBB("btn_up","JI(`',`t00000104')");EB("btn_up")I î ł) "€@€€€€‚˙Section 7.1: Starting Plink\j@@% €š€˜€‚˙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 availł@@î able from the Programs section of your Start Menu.ŰłRA7 <€ˇ€˜€€€€€€€‚˙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-@@ŁA$ €Z€˜€‚˙set PATH=C:\path\to\putty\directory;%PATH%]&RAC7 <€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ŁAyC1? żL‰ŃyCżC¸OSection 7.2: Using PlinkCBB("btn_up","JI(`',`t00000104')");EB("btn_up")FCżC) "€:€€€€‚˙Section 7.2: Using PlinklyCOD$ €Ř€˜€‚˙This section describes the basics of how to use Plink for interactive logins and for automated processes.ŘżCRE+ $€ą€˜€€€‚˙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:5OD‡E# €$€€‚˙Z:\sysosd>plinkQ.REŘE# €\€€‚˙PuTTY Link: command-line connection utility2‡E F# €€€‚˙Release 0.54R/ŘE\F# €^€€‚˙Usage: plink [options] [user@]host [command]\9 F¸F# €r€€‚˙ ("host" can also be a PuTTY saved session name). \FćF# €€€‚˙Options:G$¸F-G# €H€€‚˙ -v show verbose messagesX5ćF…G# €j€€‚˙ -load sessname Load settings from saved sessionA-GĆG# €<€€‚˙ -ssh -telnet -rlogin -rawb?…G(H# €~€€‚˙ force use of a particular protocol (default SSH)K(ĆGsH# €P€€‚˙ -P port connect to specified portQ.(HÄH# €\€€‚˙ -l user connect with specified usernameR/sHI# €^€€‚˙ -m file read remote command(s) from fileQ.ÄHgI# €\€€‚˙ -batch disable all interactive promptsZ7IÁI# €n€€‚˙The following options only apply to SSH connections:O,gIJ# €X€€‚˙ -pw passw login with specified passwordBÁIRJ# €>€€‚˙ -D [listen-IP:]listen-portU2J§J# €d€€‚˙ Dynamic SOCKS-based port forwardingL)RJóJ# €R€€‚˙ -L [listen-IP:]listen-port:host:portV3§JIK# €f€€‚˙ Forward local port to remote addressL)óJ•K# €R€€‚˙ -R [listen-IP:]listen-port:host:portV3IKëK# €f€€‚˙ Forward remote port to local addressQ.•K~M5N$ €|€˜€‚˙ -s remote command is an SSH subsystem (SSH-2 only)S/ÓMˆN$ €^€˜€‚˙Once this works, you are ready to use Plink.g85NďN/ .€p€ă…ůN€€€‰‚˙Section 7.2.1: Using Plink for interactive loginsj;ˆNYO/ .€v€ă…ůN€€€‰‚˙Section 7.2.2: Using Plink for automated connections_0ďN¸O/ .€`€ă…ůN€€€‰‚˙Section 7.2.3: Plink command line options’aYOV€1.‚/ŇV€ľ€ă‡Section 7.2.1: Using Pl¸OV€¸Oink for interactive loginsCBB("btn_up","JI(`',`t00000106')");EB("btn_up")_6¸Oľ€) "€l€€€€‚˙Section 7.2.1: Using Plink for interactive logins’hV€G* $€Đ€˜€€€‚˙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&G´# €€€‚˙M*Ž‚# €T€€‚˙Debian GNU/Linux 2.2 flunky.example.com4´5‚$ € €˜€‚˙flunky login:ܡ‚„% €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.ä§5‚ő„= 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)„A…# €R€€‚˙Z:\sysosd>plink -ssh login.example.com0 ő„q…$ €€˜€‚˙login as:ôA…Š†% €é€˜€‚˙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!q…Ά# €B€€‚˙Z:\sysosd>plink my-ssh-session:Š†‡# €.€€‚˙Sent username "fred"R/ΆZ‡# €^€€‚˙Authenticating with public key "fred@winbox"T1‡Ž‡# €b€€‚˙Last login: Thu Dec 6 19:25:33 2001 from :0.05Z‡ă‡$ €"€˜€‚˙fred@flunky:~$•dŽ‡xˆ1ĎL‰ş„ÓxˆڈSÇSection 7.2.2: Using Plink for automated connectionsCBB("btn_up","JI(`',`t00000106')");EB("btn_up")b9ă‡ڈ) "€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<ڈUŠ9 B€x€T˜‘€8‚€ƒ€€€ă…ůN‰‚˙•Use the -ssh option as described in section 7.2.1.Ž€ŕ‰‹. *€€T˜‘€8‚€ƒ€‚˙•Set up a PuTTY saved session that describes the server you are connecting to, and that also specifies the protocol as SSH.‡NUŠŠ‹9 B€œ€T˜‘€8‚€ƒ€€€€€‚˙•Set the Windows environment variable PLINK_PROTOCOL to the word ssh.Ů´‹cŒ% €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.˙ڊ‹b% €ľ€˜€‚˙Next, you are likely to need to avoid the various interactive prompts Plink can produce. You might be prompted to verify the host key of the server you're connecting to, to enter a user name, or to enter a password.اcŒ:1 0€O€˜€€€ă˙ĹůN‰‚˙To avoid being prompted for the server host key when using Plink for an automated connection, you should first make a manual connection (using either of PuTTY or Plink) to the same server, verify the host key (see section 2.2 for more information), and select Yes to add the host key to the Registry. After that, Plink commands connecting to that server should not give a host key prompt unless the host key changes.X4b’$ €h€˜€‚˙To avoid being prompted for a user name, you can:Žu:LŔ9 B€ę€T˜‘€8‚€ƒ€€€€€‚˙•Use the -l option to specify a user name on the’LŔ㇠command line. For example, plink login.example.com -l fred.ѝ’Á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).×LŔÂ+ $€Ż€˜€ă{ƒůN‰‚˙To avoid being prompted for a password, 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ÂÂĂ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>ÂĂáÄ# €|€€‚˙Z:\sysosd>plink login.example.com -l fred echo hello, world2€ÄĹ# €€€‚˙hello, world&áÄ9Ĺ# €€€‚˙1 ĹjĹ$ €€˜€‚˙Z:\sysosd>nJ9ĹŘĹ$ €”€˜€‚˙Or, if you have set up a saved session with all the connection details:Q.jĹ)Ć# €\€€‚˙Z:\sysosd>plink mysession echo hello, world2ŘĹ[Ć# €€€‚˙hello, world&)ƁĆ# €€€‚˙1 [ƲĆ$ €€˜€‚˙Z:\sysosd>Ą}ĆSÇ$ €ú€˜€‚˙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.ŠY˛ĆÝÇ1‡/e†ÔÝÇ4ČdĘSection 7.2.3: Plink command line optionsCBB("btn_up","JI(`',`t00000106')");EB("btn_up")W.SÇ4Č) "€\€€€€‚˙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.šv4Č„É$ €ě€˜€‚˙Plink also supports some of its own options. The following sections describe Plink's specific command-line options.r@ęČöÉ2 4€€€ă€ƒůN€€€€‰‚˙Section 7.2.3.1: -batch: disable all interactive promptsn<„ÉdĘ2 4€x€ăwƒůN€€€€‰‚˙Section 7.2.3.2: -s: remote command is SSH subsystem™höÉýĘ1ş„\ˆŐýĘgË|ÍSection 7.2.3.1: -batch: disable all interactive promptsCBB("btn_up","JI(`',`t00000109')");EB("btn_up")j>dĘgË, (€|€€€€€‚˙Section 7.2.3.1: -batch: disable all interactive prompts< ýĘŁĚ1 0€€˜€€€ă˙ĹůN‰‚˙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.ŮŽgË|Í+ $€]€˜€€€‚˙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.•dŁĚÎ1~e†_‰ÖÎwΏĎSection 7.2.3.2: -s: remote command is SSH subsystemCBB("btn_up","JI(`',`t00000109')");EB("btn_up")f:|ÍwÎ, (€t€€€€€‚˙Section 7.2.3.2: -s: remote command is SSH subsystem¸Î/Ď+ $€€˜€€€‚˙If you specify the -s option, Plink passes the specified command as the name of an SSH ‘subsystem’ rather than an ordinary command line.`<wΏĎ$ €x€˜€‚˙(This option is only meaningful with the SSH-2 protocol.)”c/Ď/1{\ˆ– ×/ŞSection 7.3: Using Plink in batch files and scriptsCBB("btn_up"Ď/Ď,"JI(`',`t00000104')");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$ €`€˜€‚˙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:lH˙$ €€˜€‚˙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.‚Q˙,1†_‰é Ř,{˛Section 7.4: Using Plink with CVSCBB("btn_up","JI(`',`t00000104')");EB("btn_up")O&Ş{) "€L€€€€‚˙Section 7.4: Using Plink with CVS‰_,* $€ž€˜€€€‚˙To use Plink with CVS, you need to set the environment variable CVS_RSH to point to Plink:E!{I$ €B€˜€‚˙set CVS_RSH=\path\to\plink.exeŻ„ř+ $€ €˜€ă…ůN‰‚˙You also need to arrange to be able to connect to a remote host without any interactive prompts, as described in section 7.2.2.U1IM$ €b€˜€‚˙You should then be able to run CVS as follows:a=řŽ$ €z€˜€‚˙cvs -d :ext:user@sessionname:/path/to/repository co module¨ƒMV% €€˜€‚˙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…TV71*– Í Ů7‰a Section 7.5: Using Plink with WinCVSCBB("btn_up","JI(`',`t00000104')");EB("btn_up")R)˛‰) "€R€€€€‚˙Section 7.5: Using Plink with WinCVSǜ7P + $€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.ŸuP S * $€ę€˜€ăyƒů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(S ý $ €P€˜€‚˙or (if you're using a saved session):a=ą ^ $ €z€˜€‚˙cvs -d :ext:user@sessionname:/path/to/repository co moduleŢý a % €˝€˜€‚˙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.Ž]^ ď 1§é ž Úď ˙˙˙˙–Chapter 8: Using public keys for SSH authenticationCBB("btn_up","JI(`',`Top')");EB("btn_up")a8a P) "€p€€€€‚˙Chapter 8: Using public keys for SSH authenticationn?ď ž/ .€~€ă|ƒůN€€€‰‚˙Section 8.1: Public key authentication - an introductionj;P(/ .€v€ăL%ĽÍ€€€‰‚˙Section 8.2: Using PuTTYgen, the PuTTY key generatorn?ž–/ .€~€ă~ƒůN€€€‰‚˙Section 8.3: Getting ready for public key authentication™h(;@1Ć Í dŒ Ű;@Ą@NSection 8.1: Public key authentication - an introduction–;@–CBB("btn_up","JI(`',`t00000115')");EB("btn_up")f=–Ą@) "€z€€€€‚˙Section 8.1: Public key authentication - an introductionĺŔ;@†A% €€˜€‚˙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Ą@C1 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.AţD1 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. ĺCG% €Ë€˜€‚˙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 who 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.ëţD$I1 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.¸‡GÜL1 0€€˜€€€ă80Ťf‰‚˙This can make public-key authentication less convenient than password authentication: every time you log in to the server, instead of typing a short password, you have to type a longer passphrase. One solution to this is to use an authentication agent, a separate program which holds decrypted private keys and generates signatures on request. PuTTY's authentication agent is called Pageant. When you begin a Windows session, you start Pageant and load your private key into it (typing your passphrase once). For the rest of your session, you can start PuTTY any number of times and Pageant will automatically generate signatures without you having to do anything. When you close your Windows session, Pageant shuts down, without ever having stored your decrypted private key on disk. Many people feel this is a good compromise between security and convenience. See chapter 9 for further details.%ú$IN+ $€ő€˜€ă5Äł‰‚˙There is more than one public-key algorithm available. The most common is RSA, but others exist, notably DSA (otherwise known as DSS), the USA's federal Digital Signature Standard. The key types supported by PuTTY are described in section 8.2.2.•dÜL–N1ž :!ܖNřN˘…Section 8.2: Using PuTTYgen, the PuTTY key generatorCBB("btn_up","JI(`',`t00000115')");EB("btn_up")b9NřN) "€r€€€€‚˙Section 8.2: Using PuTTYgen, the PuTTY key generator ŕ–N€+ $€Á€˜€ă80Ťf‰‚˙PuTTYgen is a key generator. It generates pairs of public and private keys to be used with PuTTY, PSCP, and Plink, as well as the PuTTY authentication agent, Pageant (see chapter 9). PuTTYgen generates RSA and DSA keysřN€N.ÔŻřNă€% €_€˜€‚˙When you run PuTTYgen you will see a window where you have two choices: ‘Generate’, to generate a new public/private key pair, or ‘Load’ to load in an existing private key.Y*€</ .€T€ă}ƒůN€€€‰‚˙Section 8.2.1: Generating a new key^/〚/ .€^€ă5Äł€€€‰‚˙Section 8.2.2: Selecting the type of keym><‚/ .€|€ă&lφ€€€‰‚˙Section 8.2.3: Selecting the size (strength) of the keyZ+ša‚/ .€V€ă1E˝Š€€€‰‚˙Section 8.2.4: The ‘Generate’ button^/‚ż‚/ .€^€ă„QÜc€€€‰‚˙Section 8.2.5: The ‘Key fingerprint’ boxc4a‚"ƒ/ .€h€ă/§řA€€€‰‚˙Section 8.2.6: Setting a comment for your keyf7ż‚ˆƒ/ .€n€ăB'ó6€€€‰‚˙Section 8.2.7: Setting a passphrase for your keyk<"ƒóƒ/ .€x€ă䀅a€€€‰‚˙Section 8.2.8: Saving your private key to a disk filej;ˆƒ]„/ .€v€ă´ĺU€€€‰‚˙Section 8.2.9: Saving your public key to a disk filexIóƒՄ/ .€’€ă eHm€€€‰‚˙Section 8.2.10: ‘Public key for pasting into authorized_keys file’].]„2…/ .€\€ăúľŰ†€€€‰‚˙Section 8.2.11: Reloading a private keypAՄ˘…/ .€‚€ăE@Áv€€€‰‚˙Section 8.2.12: Dealing with private keys in other formats‹Z2…-†1ądŒ b!Ý-†~†ތ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‚€ƒ€ă5Äł‰ă&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ˆg‰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ťˆ Š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).Řg‰Œ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.— Šތ+ $€/€˜ă~ƒůN€‰‚˙section 8.3 describes the typical process of configuring PuTTY to attempt public-key authentication, and configuring your SSH server to accept it._Œn1Ą:!4ƒ!ŢnčÄSection 8.2.2: Selecting the type of keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")V-ތč) "€Z€€€€‚˙Section 8.2.2: Selecting the type of keyłŽnwŽ% €€˜€‚˙Before generating a key pair using PuTTYgen, you need to select which type of key you need. PuTTYgen currently supports three types of key:^1čՎ- *€b€T˜‘€8‚€ƒ€‚˙•An RSA key for use with the SSH 1 protocol.^1wŽ3- *€b€T˜‘€8‚€ƒ€‚˙•An RSA key for use with the SSH 2 protocol.]0Վ- *€`€T˜‘€8‚€ƒ€‚˙•A DSA key for use with the SSH 2 protocol.ŃŹ3mŔ% €Y€˜€‚˙The SSH 1 protocol only supports RSA keys; if you will be connecting usingmŔތ the SSH 1 protocol, you must select the first key type or your key will be completely useless.ŒhůŔ$ €Đ€˜€‚˙The SSH 2 protocol supports more than one key type. The two types supported by PuTTY are RSA and DSA.ęmŔĂ1 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.âůŔÄ% €Ĺ€˜€‚˙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.ŸnĂşÄ1'b!Ą†!ßşÄĹáČ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 generate.b>Ĺ Ć$ €|€˜€‚˙Currently 1024 bits should be sufficient for most purposes.<ŠĹGČ% €/€˜€‚˙Note that an RSA key is generated by finding two primes of half the length requested, and then multiplying them together. For example, if you ask PuTTYgen for a 1024-bit RSA key, it will create two 512-bit primes and multiply them. The result of this multiplication might be 1024 bits long, or it might be only 1023; so you may not get the exact length of key you asked for. This is perfectly normal, and you do not need to worry. The lengths should only ever differ by one, and there is no perceptible drop in security as a result.šv ĆáČ$ €ě€˜€‚˙DSA keys are not created by multiplying primes together, so they should always be exactly the length you asked for.Œ[GČmÉ1‘4ƒ!p‹!ŕmÉżÉţÎSection 8.2.4: The ‘Generate’ buttonCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")R)áČżÉ) "€R€€€€‚˙Section 8.2.4: The ‘Generate’ buttonÓŽmÉ’Ę% €]€˜€‚˙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.'üżÉšĚ+ $€ů€˜€€€‚˙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.¸“’ĘqÎ% €'€˜€‚˙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.išĚţÎ$ €Ň€˜€‚˙When the key generation is complete, a new set of controls will appear in the window to indicate this._qÎŽĎ1ôĄ†!B"áŽĎ ŞSection 8.2.5: The ‘Key fingerprint’ boxCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")V-ţÎ ) "€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.˝Œ Ş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îp‹!†"â?š-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@?Ú+ $€+€˜€€€‚˙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.óÚ-% €ç€˜€‚˙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Ĺ1– B"A€"ăĹ#gASection 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.úÉ3  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 ˙@+ $€™€˜€€€‚˙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 rando|˙@-mly 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|gA' €‚€˜€€‚˙Do not forget your passphrase. There is no way to recover it.l˙@B1†"Z‚"äBgBĆDSection 8.2.8: Saving your private key to a disk fileCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")c:gAgB) "€t€€€€‚˙Section 8.2.8: Saving your private key to a disk fileŸ{BC$ €ö€˜€‚˙Once you have generated a key, set a comment field and set a passphrase, you are ready to save your private key to disk.̧gBŇC% €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’.ô˝CĆD7 <€{€˜€€€ă„@Ď؉ăÂ<ű—‰‚˙This file is in PuTTY's native format (*.PPK); it 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ŇCbE1˝A€"H†"ĺbEÄEJSection 8.2.9: Saving your public key to a disk fileCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")b9ĆDÄE) "€r€€€€‚˙Section 8.2.9: Saving your public key to a disk fileb1bE&G1 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.) čÄE3H% €Ń€˜€‚˙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’.ôÉ&G'I+ $€“€˜€ă~ƒůN‰‚˙You will then probably want to copy the public key file to your SSH server machine. See section 8.3 for general instructions on configuring public-key authentication once you have generated a key.řÓ3HJ% €§€˜€‚˙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.Şy'IÉJ1_Z‚" ‰"ćÉJ9K(NSection 8.2.10: ‘Public key for pasting into authorized_keys file’CBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")pGJ9K) "€Ž€€€€‚˙Section 8.2.10: ‘Public key for pasting into authorized_keys file’ĺŔÉJL% €€˜€‚˙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.kF9K‰M% €€˜€‚˙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.ŸuL(N* $€ę€˜€ă~ƒůN‰‚˙See section 8.3 for general instructions on configuring public-key authentication once you have generated a key.^‰MˇN1×H†"<#çˇN Oš‚Section 8.2.11: Reloading a private keyCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")U,(N O) "€X€€€€‚˙Section 8.2.11: Reloading a private keyöѡN€% €Ł€˜€‚˙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. O€(NjE Ox% €‹€˜€‚˙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."÷€š‚+ $€ď€˜€ă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.˘qx<ƒ1  ‰"P#č<ƒ¤ƒ\ŠSection 8.2.12: Dealing with private keys in other formatsCBB("btn_up","JI(`',`puttygen.general')");EB("btn_up")h?š‚¤ƒ) "€~€€€€‚˙Section 8.2.12: Dealing with private keys in other formatsé<ƒ¸„+ $€Ó€˜€€€‚˙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.űФƒł…+ $€Ą€˜€€€‚˙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.k4¸„ˆ7 <€i€˜€€€€€€€‚˙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 (*.PPK) so that you can use it with the PuTTY suite. 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ł…ł‰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 ‘Conversions’ 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.Š„ˆ\Š% € €˜€‚˙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 <#/…#éőŠ[‹5ÇSection 8.3: Getting ready for public key authenticationCBB("btn_up","JI(`',`t00000115')");EB("btn_up")f=\Š[‹) "€z€€€€‚˙Section 8.3: Getting ready for public key authenticationřőŠxŒ% €ń€˜€‚˙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.YxŒOŔ: 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 saęŽOŔ\Šme authorized_keys file is used for both SSH 1 and SSH 2 keys.)ç‰ęŽ6Â^ Š€€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.TOŔˇÂ- *€¨€T˜‘€8‚€ƒ€‚˙•For other SSH server software, you should refer to the manual for that server.9ü6ÂđĂ= 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ˇÂLÄ$ €p€˜€‚˙chmod g-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keysýŇđĂIĹ+ $€Ľ€˜€€€‚˙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:‹XLÄÔĹ3 6€°€T˜‘€8‚€ƒ€ă„@Ď؉‚˙•Select the private key in PuTTY's configuration. See section 4.18.5 for details.ĄhIĹuĆ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.ŔŒÔĹ5Ç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.†UuĆťÇ1ëP#á†#ęťÇČŚĘChapter 9: Using Pageant for authenticationCBB("btn_up","JI(`',`Top')");EB("btn_up")Y05ÇČ) "€`€€€€‚˙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 passphrase._0Č>É/ .€`€ăƒůN€€€‰‚˙Section 9.1: Getting started with PageantZ+ßČ˜É/ .€V€ăŤƒůN€€€‰‚˙Section 9.2: The Pageant main window[,>ÉóÉ/ .€X€ă˘ƒůN€€€‰‚˙Section 9.3: The Pageant command lineY*˜ÉLĘ/ .€T€ăĽƒůN€€€‰‚˙Section 9.4: Using agent forwardingZ+óÉŚĘ/ .€V€ăŚƒůN€€€‰‚˙Section 9.5: Security considerations_LĘ6Ë1ö/…#´$ë6ˍË8Section 9.1: Getting started with PageantCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")W.ŚĘË) "€\€€€€‚˙Section 9.1: Getting started with Pageantś…6ËCĚ1 0€ €˜€€€ă{ƒůN‰‚˙Before you run Pageant, you need to have a private key in *.PPK format. 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. ćCĚÎ% €Í€˜€‚˙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.) ä Í!Ď% €É€˜€‚˙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’!ĎŚĘ.ôĎ!Ď% €Ÿ€˜€‚˙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!I% €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.ďÄ8+ $€‰€˜€€€‚˙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.‹ZIĂ1™á†#r$ěĂ\Section 9.2: The Pageant main windowCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")R)8) "€R€€€€‚˙Section 9.2: The Pageant main window=ĂR% €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*R/ .€T€ăÂ<ű—€€€‰‚˙Section 9.2.2: The ‘Add Key’ button\-§\/ .€Z€ă :0-€€€‰‚˙Section 9.2.3: The ‘Remove Key’ button€OÜ1´$ó$íÜ)ę Section 9.2.1: The key list boxCBB("btn_up","JI(`',`t00000120')");EB("btn_up")M$\)) "€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:jG)P# €Ž€€‚˙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,P $ €X€˜€‚˙For each key, the list 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$ w - *€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&w ę - *€L€T˜‘€8‚€ƒ€‚˙•The comment attached to the key.„S— n 1"r$€$în ż œ@Section 9.2.2: The ‘Add Key’ buttonCBB("btn_up","JI(`',`t00000120')");EB("btn_up")Q(ę ż ) "€P€€€€‚˙Section 9.2.2: The ‘Add Key’ buttonŢn  % €˝€˜€‚˙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ż % €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.͢œ@+ $€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Ă#A1ćó$m$ď#AwA CSection 9.2.3: The ‘Remove Key’ buttonCBB("btn_up","JI(`',`t00000120')");EB("btn_up")T+œ@wA) "€V€€€€‚˙Section 9.2.3: The ‘Remove Key’ button#A9B% €;€˜€‚˙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.ĐĽwA C+ $€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.Œ[9B•C1[€$ƒ$đ•CčCđESection 9.3: The Pageant command lineCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")S* CčC) "€T€€€€‚˙Section 9.3: The Pageant command line+•CE% € €˜€‚˙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čC‰E/ .€Ž€ăŁƒůN€€€‰‚˙Section 9.3.1: Making Pageant automatically load keys on startupg8EđE/ .€p€ă¤ƒůN€€€‰‚˙Section 9.3.2: Making Pageant run another programĄp‰E‘F1 m$„$ń‘F˙F›HSection 9.3.1: Making Pageant automatically load keys on startupCBB("btn_up","JI(`',`t00000121')");EB("btn_up")nEđE˙F) "€Š€€€€‚˙Section 9.3.1: Making Pageant automatically load keys on startupËŚ‘FĘG% €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˙F"H$ €h€˜€‚˙C:\PuTTY\pageant.exe d:\main.ppk d:\secondary.ppkyUĘG›H$ €Ş€˜€‚˙If the keys are stored encrypted, Pageant will request the passphrases on startup.’a"H-I1gƒ$[†$ň-IŒI”KSection 9.3.2: Making Pageant run another programCBB("btn_up","JI(`',`t00000121')");EB("btn_up")_6›HŒI) "€l€€€€‚˙Section 9.3.2: Making Pageant run another program1 -I˝J% €€˜€‚˙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ŒI7K* $€ €˜€€€‚˙You do this by specifying the -c option followed by the command, like this:]9˝J”K$ €r€˜€‚˙C:\PuTTY\pageant.exe d:\main.ppk -c C:\PuTTY\putty.exeŠY7KL1M „$.%óLoLwˆSection 9.4: Using agent forwardingCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")Q(”KoL) "€P€€€€‚˙Section 9.4: Using agent forwarding¨ƒLM% €€˜€‚˙Agent forwarding is a mechanism that allows applications on your SSH server machine to talk to the agent on your client machine.çźoLţM+ $€y€˜€€€‚˙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 PuTTY does not yet support.IMGO7 <€%€˜€ăĘ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.)?ţM’€% €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,GO’€”K 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!GOր# €B€€‚˙unixbox:~$ echo $SSH_AUTH_SOCKC ’€# €@€€‚˙/tmp/ssh-XXNP18Jz/agent.287941 րJ$ €€˜€‚˙unixbox:~$wSÁ$ €Ś€˜€‚˙If the result line comes up blank, agent forwarding has not been enabled at all.ÚŻ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!Á߂# €B€€‚˙unixbox:~$ ssh -v otherunixbox+›‚ ƒ# €€€‚˙[...]Q.߂[ƒ# €\€€‚˙debug: next auth method to try is publickeya> ƒźƒ# €|€€‚˙debug: userauth_pubkey_agent: trying agent key my-putty-keyW4[ƒ„# €h€€‚˙debug: ssh-userauth2 successful: method publickey,źƒ?„$ €€˜€‚˙[...]M"„Œ…+ $€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.ž“?„J†+ $€'€˜€€€‚˙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#Œ…†# €F€€‚˙unixbox:~$ ssh-add ~/.ssh/id_rsaP-J†ŕ†# €Z€€‚˙Need passphrase for /home/fred/.ssh/id_rsaR/†2‡# €^€€‚˙Enter passphrase for /home/fred/.ssh/id_rsa:fCŕ†˜‡# €†€€‚˙Identity added: /home/fred/.ssh/id_rsa (/home/simon/.ssh/id_rsa)1 2‡ɇ$ €€˜€‚˙unixbox:~$Ž‰˜‡wˆ% €€˜€‚˙and then it's available to every machine that has agent forwarding available (not just the ones downstream of the place you added it).‹Zɇ‰1ł [†$1…%ô‰T‰ÄĹSection 9.5: Security considerationsCBB("btn_up","JI(`',`pageant.general')");EB("btn_up")R)wˆT‰) "€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. ŢT‰͋+ $€˝€˜€€€‚˙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.ڍ Ŕwˆíڍ$Â+ $€Ű€˜€€€‚˙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.=  ŔaÄ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.)|KaÄ@Ć1ć .%&ő@ƏĆ2Chapter 10: Common error messagesCBB("btn_up","JI(`',`Top')");EB("btn_up")O&ÄŏĆ) "€L€€€€‚˙Chapter 10: Common error messagesş•@ĆIÇ% €+€˜€‚˙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=ĆˇČ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 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.yJIÇ0É/ .€”€ă¨ƒů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!’g80ÉĘ/ .€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’š‰ĘVË0 .€€ă̓ůN€€€‰‚˙Section 10.5: ‘Server sent disconnect message type 2 (SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"’S$ĘŠË/ .€H€ă΃ůN€€€‰‚˙Section 10.6: ‘Out of memory’zKVË#Ě/ .€–€ăσůN€€€‰‚˙Section 10.7: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’tEŠË—Ě/ .€Š€ăЃůN€€€‰‚˙Section 10.8: ‘Server refused our public key’ or ‘Key refused’m>#ĚÍ/ .€|€ăуůN€€€‰‚˙Section 10.9: ‘Access denied’, ‘Authentication refused’^—Ě‘Í/ .€ź€ă҃ůN€€€‰‚˙Section 10.10: ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’pAÍÎ/ .€‚€ăӃůN€€€‰‚˙Section 10.11: ‘Incoming packet was garbled on decryption’o@‘ÍpÎ/ .€€€ăԃůN€€€‰‚˙Section 10.12: ‘Authentication failed at PuTTY X11 proxy’vGÎćÎ/ .€Ž€ăՃůN€€€‰‚˙Section 10.13: ‘Network error: Software caused connection abort’n?pÎTĎ/ .€~€ă„ůN€€€‰‚˙Section 10.14: ‘Network error: Connection reset by peer’h9ćÎźĎ/ .€r€ăřƒůN€€€‰‚˙Section 10.15: ‘Network error: Connection refused’j;TĎ2/ .€v€ăůƒůN€€€‰‚˙Section 10.16: ‘NźĎ2ÄĹetwork error: Connection timed out’¤sźĎÖ1Ć1…%ţ&öÖGœSection 10.1: ‘The server's host key is not cached in the registry’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")qH2G) "€€€€€‚˙Section 10.1: ‘The server's host key is not cached in the registry’-Öt% €€˜€‚˙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.đG‰% €á€˜€‚˙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.˛‡t;+ $€€˜€€€‚˙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;11@&p&÷1“q Section 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")b9œ“) "€r€€€€‚˙Section 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’ę1¨+ $€Ő€˜€€€‚˙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“5 + $€Ĺ€˜€€€‚˙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.Űś¨ % €m€˜€‚˙You should contact your server's administrator and see whether they expect the host key to have changed. If so, verify the new host key in the same way as you would if it was new.a75 q * $€n€˜€ă˙ĹůN‰‚˙See section 2.2 for more information on host keys.’a  1uţ&r &ř b x Section 10.3: ‘Out of space for port forwardings’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")_6q b ) "€l€€€€‚˙Section 10.3: ‘Out of space for port forwardings’.   % €€˜€‚˙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.čĂb x % €‡€˜€‚˙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—p&€&ů?Ó @Section 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")”kx Ó) "€Ö€€€€‚˙Section 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’œx?o$ €đ€˜€‚˙This occurs when the SSH server does not offer any ciphers which you have configured PuTTY to consider strong enough.g=Ó @* $€z€˜€ădŢ娉‚˙See section 4.17.5 for more information on this message.o @x ă˛oď@1Ür &‚&úď@ AËCSection 10.5: ‘Server sent disconnect message type 2 (SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")ą‡ @ A* "€€€€€‚˙Section 10.5: ‘Server sent disconnect message type 2 (SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"’+úď@ËC1 0€ő€˜€€€€€‚˙This message is produced by an OpenSSH (or Sun SSH) server if it receives more failed authentication attempts than it is willing to tolerate. This can easily happen if you are using Pageant and have a large number of keys loaded into it. This can be worked around on the server by disabling public-key authentication or (for Sun SSH only) by increasing MaxAuthTries in sshd_config. Neither of these is a really satisfactory solution, and we hope to provide a better one in a future version of PuTTY.~M AID1i€&ˆ&űID”D˛JSection 10.6: ‘Out of memory’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")K"ËC”D) "€D€€€€‚˙Section 10.6: ‘Out of memory’ĄvID5F+ $€í€˜€€€‚˙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. ä”D>H% €É€˜€‚˙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.Ó5FBI1 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.7.6 in the FAQ). Some versions of OpenSSH have a known problem with this: see question A.7.18.pE>H˛J+ $€‹€˜€ăŞ„ů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.7.7 for details of this.ĽtBIWK1‚&Ľ‰&üWKÉKfMSection 10.7: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")rI˛JÉK) "€’€€€€‚˙Section 10.7: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’ÖĽWKŸL1 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.ǢÉKfM% €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ŸLN1Ɉ&)'ýNqNځSection 10.8: ‘Server refused our public key’ or ‘Key refused’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")lCfMqN) "€†€€€€‚˙Section 10.8: ‘Server refused our public key’ or ‘Key refused’Ë NqN†€% €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 aš‰@‹% €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.ĐĽŠŒ+ $€K€˜€ăďÜ7Y‰‚˙If you get this error, one thing you could try would be to fiddle with the setting of ‘Miscomputes SSH2 encryption keys’ on the Bugs panel (see section 4.20.5).’h@‹˘Œ* $€Đ€˜€ăքůN‰‚˙Another known server problem which can cause this error is described in question A.7.18 in the FAQ.šiŒ<1č¸'Dƒ'<Ł0ÄSection 10.12: ‘Authentication failed at PuTTY X11 proxy’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")g>˘ŒŁ) "€|€€€€‚˙Section 10.12: ‘Authentication failed at PuTTY X11 proxy’ŃŹ<tŽ% €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. ߣŠŔ+ $€ż€˜€ăĽÄů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 ctŽŠŔ˘Œlients to connect, and the server should put this mechanism in place automatically, so your X applications should just work.ItŽÓÂ+ $€=€˜€€€‚˙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 data passed on to it, so attempting to run an X application as that user often fails with this error.]&ŠŔ0Ä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.ĄpÓÂŃÄ1œ'm…'ŃÄ?ĹmÇSection 10.13: ‘Network error: Software caused connection abort’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")nE0Ä?Ĺ) "€Š€€€€‚˙Section 10.13: ‘Network error: Software caused connection abort’S.ŃÄ’Ć% €]€˜€‚˙This error occurs when the Windows network code decides that your network connection is dead. For example, it will happen if you pull the network cable out of the back of an Ethernet-connected computer, or if Windows has any other similar reason to believe the entire network has become unreachable.Űś?ĹmÇ% €m€˜€‚˙We are not aware of any reason why this error might occur that would represent a bug in PuTTY. The problem is between you, your Windows system, your network and the remote system.™h’ĆČ1ńDƒ'߇'ČlČ÷ĘSection 10.14: ‘Network error: Connection reset by peer’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")f=mÇlČ) "€z€€€€‚˙Section 10.14: ‘Network error: Connection reset by peer’)Č•É% € €˜€‚˙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.b1lČ÷Ę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.7.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.“b•ÉŠË15m…'Ą‰'ŠËęËżÍSection 10.15: ‘Network error: Connection refused’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")`7÷ĘęË) "€n€€€€‚˙Section 10.15: ‘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.ܡęËżÍ% €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.•dăĚTÎ16߇'(TΜΖSection 10.16: ‘Network error: Connection timed out’CBB("btn_up","JI(`',`t00000126')");EB("btn_up")b9żÍśÎ) "€r€€€€‚˙Section 10.16: ‘Network error: Connection timed out’őTÎĐĎ% €ë€˜€‚˙This error means that the network connection PuTTY tried to make to your server received no response at all from the server. Usually this happens because the server machine is completely isolated from the network, or because it is turned off.ş•śÎ–% €+€˜€‚˙Check thatĐĎ–żÍ you have correctly entered the host name or IP address of your server machine. If that fails, consult the administrator of your server.p?ĐĎ1HĄ‰'%(INAppendix A: PuTTY FAQCBB("btn_up","JI(`',`Top')");EB("btn_up")C–I) "€4€€€€‚˙Appendix A: PuTTY FAQƒ_Ě$ €ž€˜€‚˙This FAQ is published on the PuTTY web site, and also provided as an appendix in the manual.O I/ .€@€ăűƒůN€€€‰‚˙Section A.1: Introduction^/Ěy/ .€^€ăýƒůN€€€‰‚˙Section A.2: Features supported in PuTTYc4Ü/ .€h€ă)„ůN€€€‰‚˙Section A.3: Ports to other operating systemsd5y@/ .€j€ăQ„ůN€€€‰‚˙Section A.4: Embedding PuTTY in other programs_0ÜŸ/ .€`€ăU„ůN€€€‰‚˙Section A.5: Details of PuTTY's operationR#@ń/ .€F€ăy„ůN€€€‰‚˙Section A.6: HOWTO questionsR#ŸC/ .€F€ă­„ůN€€€‰‚˙Section A.7: TroubleshootingU&ń˜/ .€L€ă3ŒůN€€€‰‚˙Section A.8: Security questions[,Có/ .€X€ă8ŒůN€€€‰‚˙Section A.9: Administrative questions[,˜N/ .€X€ă˛ŠůN€€€‰‚˙Section A.10: Miscellaneous questionszIóČ1š(g(Č˙˙˙˙bSection A.1: IntroductionCBB("btn_up","JI(`',`t00000143')");EB("btn_up")GN) "€<€€€€‚˙Section A.1: IntroductionS$Čb/ .€H€ăüƒůN€€€‰‚˙Section A.1.1: What is PuTTY?~Mŕ1s%(C(ŕ+S Section A.1.1: What is PuTTY?CBB("btn_up","JI(`',`t00000144')");EB("btn_up")K"b+) "€D€€€€‚˙Section A.1.1: What is PuTTY?rNŕ$ €œ€˜€‚˙PuTTY is a client program for the SSH, Telnet and Rlogin network protocols.ýŘ+š% €ą€˜€‚˙These protocols are all used to run a remote session on a computer, over a network. PuTTY implements the client end of that session: the end at which the session is displayed, rather than the end at which it runs.š”S % €)€˜€‚˙In really simple terms: you run PuTTY on a Windows machine, and tell it to connect to (for example) a Unix machine. PuTTY opens a window. Then, anything you type into that window is sent straight to the Unix machine, and everything the Unix machine sends back is displayed in the window. So you can work on the Unix machine as if you were sitting at its console, while actually sitting somewhere else.‰XšÜ 1g(ś( Ü 2 ěBSection A.2: Features supported in PuTTYCBB("btn_up","JI(`',`t00000143')");EB("btn_up")V-S 2 ) "€Z€€€€‚˙Section A.2: 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:O2 - 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.ÝŠŢ  4 6€S€T˜‘€8‚€ƒ€€€‚˙•try the Wishlist page, and see if you can find the feature there. If it's on there, and not in the ‘Recently fixed’ section, it probably hasn't been implemented.`1- j/ .€b€ăţƒůN€€€‰‚˙Question A.2.1: Does PuTTY support SSH v2?”_ ţ5 :€ž€ă˙ƒůN€€€€€‰‚˙Question A.2.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?`1j^/ .€b€ă„ůN€€€‰‚˙Question A.2.3: Does PuTTY support SSH v1?d5ţÂ/ .€j€ă,„ůN€€€‰‚˙Question A.2.4: Does PuTTY support local echo?}N^K@/ .€œ€ă#„ůN€€€‰‚˙Question A.2.ÂK@S 5: Does PuTTY support storing its settings in a disk file?zKÂĹ@/ .€–€ă$„ůN€€€‰‚˙Question A.2.6: Does PuTTY support full-screen mode, like a DOS box? qK@eA/ .€â€ă%„ůN€€€‰‚˙Question A.2.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?ƒTĹ@čA/ .€¨€ă&„ůN€€€‰‚˙Question A.2.8: Is there an option to turn off the annoying host key prompts?Ž_eAvB/ .€ž€ă'„ůN€€€‰‚˙Question A.2.9: Will you write an SSH server for the PuTTY suite, to go with the client?vGčAěB/ .€Ž€ă(„ůN€€€‰‚˙Question A.2.10: Can PSCP or PSFTP transfer files in ASCII mode?‹ZvBwC17C(|‚( wCĎCŽDQuestion A.2.1: Does PuTTY support SSH v2?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")X/ěBĎC) "€^€€€€‚˙Question A.2.1: Does PuTTY support SSH v2?jFwC9D$ €Œ€˜€‚˙Yes. SSH v2 support has been available in PuTTY since version 0.50.uQĎCŽD$ €˘€˜€‚˙Public key authentication (both RSA and DSA) in SSH v2 is new in version 0.52.ˇ†9DeE1Dś(fƒ( eEńEŠFQuestion A.2.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")Œ]ŽDńE/ .€ş€€€€€€‚˙Question A.2.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?¸eEŠF+ $€€˜€€€‚˙PuTTY doesn't support this natively, but as of 0.53 PuTTYgen can convert both OpenSSH and ssh.com private key files into PuTTY's format.‹ZńE4G1ľ|‚(΃( 4GŒGéGQuestion A.2.3: Does PuTTY support SSH v1?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")X/ŠFŒG) "€^€€€€‚˙Question A.2.3: Does PuTTY support SSH v1?]94GéG$ €r€˜€‚˙Yes. SSH 1 support has always been available in PuTTY.^ŒGxH1ˇfƒ( ‡( xHÔH/LQuestion A.2.4: Does PuTTY support local echo?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")\3éGÔH) "€f€€€€‚˙Question A.2.4: Does PuTTY support local echo?[7xH/I$ €n€˜€‚˙Yes. Version 0.52 has proper support for local echo.ŐÔH/L+ $€Ť€˜€€€‚˙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’.¨w/I×L1 ΃(Ň(×LLMâMQuestion A.2.5: Does PuTTY support storing its settings in a disk file?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")uL/LLM) "€˜€€€€‚˙Question A.2.5: Does PuTTY support storing its settings in a disk file?–l×LâM* $€Ř€˜€ăQĹůN‰‚˙Not at present, although section 4.21 in the documentation gives a method of achieving the same effect.ĽtLM‡N1Ä ‡(<ˆ(‡NůNKOQuestion A.2.6: Does PuTTY support full-screen mode, like a DOS box?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")rIâMůN) "€’€€€€‚˙Question A.2.6: Does PuTTY support full-screen mode, like a DOS box?R.‡NKO$ €\€˜€‚˙Yes; this is a new feature in version 0.52.˚ůN"€1ĚŇ()"€ş€î„Question A.2.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?CBB("btn_up","JI(`',`t000KO"€KO00146')");EB("btn_up")˜oKOş€) "€Ţ€€€€‚˙Question A.2.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€˜€ă{ƒů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.Ž}Ťƒœ…12 <ˆ(% )œ…†ΎQuestion A.2.8: Is there an option to turn off the annoying host key prompts?CBB("btn_up","JI(`',`t00000146')");EB("btn_up"){R) "€¤€€€€‚˙Question A.2.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Ť†ˆ‹7 <€ç€˜€€€€€€€‚˙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ވš+ $€ €˜€€€‚˙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.ވ‹Ύ7 <€˝€˜€€€€€€€‚˙If you have host keys available in the common known_hosts format, we have a script called kh2reg.py to convert them to a Windows .REG file, which can be installed ahead of time by double-clicking or using REGEDIT.šˆš‡1A)q‚)‡ŔÔÂQuestion A.2.9: Will you write an SSH server for the PuTTY suite, to go with the client?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")†]ΎŔ) "€ş€€€€‚˙Question A.2.9: Will you write an SSH server for the PuTTY suite, to go with ‡ŔΎthe client?%‡>Á% €€˜€‚˙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ŔÔÂ% €ă€˜€‚˙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.Ąp>ÁuĂ1K% )%„)uĂăĂŔĹQuestion A.2.10: Can PSCP or PSFTP transfer files in ASCII mode?CBB("btn_up","JI(`',`t00000146')");EB("btn_up")nEÔÂăĂ) "€Š€€€€‚˙Question A.2.10: Can PSCP or PSFTP transfer files in ASCII mode?9uĂÄ$ €*€˜€‚˙Unfortunately not.îÉăĂ Ĺ% €“€˜€‚˙Until recently, this was a limitation of the file transfer protocols: the SCP and SFTP protocols had no notion of transferring a file in anything other than binary mode. (This is still true of SCP.)ś‘ÄŔĹ% €#€˜€‚˙The current draft protocol spec of SFTP proposes a means of implementing ASCII transfer. At some point PSCP/PSFTP may implement this proposal.Ž] ĹNĆ1Đq‚)i‡)NĆŠĆËSection A.3: Ports to other operating systemsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")[2ŔĹŠĆ) "€d€€€€‚˙Section A.3: Ports to other operating systems—sNĆ@Ç$ €ć€˜€‚˙The eventual goal is for PuTTY to be a multi-platform program, able to run on at least Windows, Mac OS and Unix.}XŠĆ˝Č% €ą€˜€‚˙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 was for this porting layer to evolve naturally as part of the process of doing the first port; a Unix port has now been released and the plan seems to be working so far.`1@ÇÉ/ .€b€ă*„ůN€€€‰‚˙Question A.3.1: What ports of PuTTY exist?^/˝Č{É/ .€^€ă+„ůN€€€‰‚˙Question A.3.2: Is there a port to Unix?uFÉđÉ/ .€Œ€ăW„ůN€€€‰‚˙Question A.3.3: Will there be a port to Windows CE or PocketPC?e6{ÉUĘ/ .€l€ăN„ůN€€€‰‚˙Question A.3.4: Is there a port to Windows 3.1?f7đÉťĘ/ .€n€ăO„ůN€€€‰‚˙Question A.3.5: Will there be a port to the Mac?c4UĘË/ .€h€ăP„ůN€€€‰‚˙Question A.3.6: Will there be a port to EPOC?‹ZťĘŠË1‚%„)Š)ŠËĚ+ĎQuestion A.3.1: What ports of PuTTY exist?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")X/ËĚ) "€^€€€€‚˙Question A.3.1: What ports of PuTTY exist?ݸŠËŢĚ% €q€˜€‚˙Currently, release versions of PuTTY tools only run on full Win32 systems and Unix. ‘Win32’ includes Windows 95, 98, and ME, and it includes Windows NT, Windows 2000 and Windows XP.‡]ĚeÍ* $€ş€˜€ăO„ůN‰‚˙In the development code, a partial port to the Mac OS (see question A.3.5) is under way.ÜĽŢĚAÎ7 <€K€˜€€€ăW„ůN‰ăN„ůN‰‚˙Currently PuTTY does not run on Windows CE (see question A.3.3), and it does not quite run on the Win32s environment under Windows 3.1 (see question A.3.4).ęĹeÍ+Ď% €‹€˜€‚˙We do not have release-quality ports for any other systems at the present time. If anyone told you we had an EPOC port, or an iPaq port, or any other port of PuTTY, they were mistaken. We don't.‰XAδĎ1Ťi‡)Ť*´ĎkQuestion A.3.2: Is there a port to Unix?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")V-+Ď) "€Z€€€€‚˙Question A.3.2: Is there a port ´Ď+Ďto Unix?–r´ĎŹ$ €ä€˜€‚˙As of 0.54, there are Unix ports of most of the traditional PuTTY tools, and also one entirely new application.B+= H€…€˜€€€€€€€€€‚˙If you look at the source release, you should find a unix subdirectory containing Makefile.gtk, which should build you Unix ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also pterm - an xterm-type program which supports the same terminal emulation as PuTTY. We do not yet have a Unix port of Pageant.wSŹ˘$ €Ś€˜€‚˙If you don't have Gtk, you should still be able to build the command-line tools.ɤ+k% €I€˜€‚˙Note that Unix PuTTY has mostly only been tested on Linux so far; portability problems such as BSD-style ptys or different header file requirements are expected. o˘ 1zŠ)×* x…Question A.3.3: Will there be a port to Windows CE or PocketPC?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")mDkx) "€ˆ€€€€‚˙Question A.3.3: Will there be a port to Windows CE or PocketPC? č …% €Ń€˜€‚˙It's currently being worked on, but it's only in its early stages yet, and certainly isn't yet useful. PuTTY on portable devices would clearly be a useful thing, so in the long term I hope it can be brought up to release quality._x1ŁŤ*Ý*r¸ Question A.3.4: Is there a port to Windows 3.1?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")]4…r) "€h€€€€‚˙Question A.3.4: Is there a port to Windows 3.1?Üy+ $€š€˜€€€‚˙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.Ť†r$ % € €˜€‚˙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.”py¸ $ €ŕ€˜€‚˙If you're interested in running PuTTY under Windows 3.1, help and testing in this area would be very welcome!‘`$ I 1 ×*Ż*I § i Question A.3.5: Will there be a port to the Mac?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")^5¸ § ) "€j€€€€‚˙Question A.3.5: Will there be a port to the Mac?I i % €;€˜€‚˙There is a port to the Mac OS in progress. It's just about usable, but has an awful lot of gaps and rough edges that will need cleaning up before release.Ž]§ ÷ 1IÝ*| *÷ R @Question A.3.6: Will there be a port to EPOC?CBB("btn_up","JI(`',`t00000157')");EB("btn_up")[2i R ) "€d€€€€‚˙Question A.3.6: Will there be a port to EPOC?ô÷ q + $€é€˜€€€‚˙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.ϧR @( €O€˜€€‚˙However, some of the work has been done by other people, and a beta port of PuTTY for the Nokia 9200 Communicator series is available from http://www.s2.org/putty/^q Ď1ĺŻ*a€*Ď˙˙˙˙Ŕ@Section A.4: Embedding PuTTY in other programsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")\3@+) "€f€€€€‚˙Section A.4: Embedding PuTTY in other programssDĎž/ .€ˆ€ăR„ůN€€€‰‚˙Question A.4.1: Is the SSH or Telnet code available as a DLL?†W+0@/ .€Ž€ăS„ůN€€€‰‚˙Question A.4.2: Is the SSH or Telnet code availž0@@able as a Visual Basic component?ažŔ@/ .€Â€ăT„ůN€€€‰‚˙Question A.4.3: How can I use PuTTY to make an SSH connection from within another program?žm0@^A1| * ‚*^AÉAyCQuestion A.4.1: Is the SSH or Telnet code available as a DLL?CBB("btn_up","JI(`',`t00000164')");EB("btn_up")kBŔ@ÉA) "€„€€€€‚˙Question A.4.1: Is the SSH or Telnet code available as a DLL? ĺ^AÓB% €Ë€˜€‚˙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.ŚÉAyC% €€˜€‚˙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.ą€ÓB*D1ľa€*K„**D¨DßFQuestion A.4.2: Is the SSH or Telnet code available as a Visual Basic component?CBB("btn_up","JI(`',`t00000164')");EB("btn_up")~UyC¨D) "€Ş€€€€‚˙Question A.4.2: Is the SSH or Telnet code available as a Visual Basic component?U0*DýE% €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.⽨DßF% €{€˜€‚˙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.ťŠýEšG1B ‚*†*šG"HÜIQuestion A.4.3: How can I use PuTTY to make an SSH connection from within another program?CBB("btn_up","JI(`',`t00000164')");EB("btn_up")ˆ_ßF"H) "€ž€€€€‚˙Question A.4.3: How can I use PuTTY to make an SSH connection from within another program?d?šG†I% €€˜€‚˙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.V2"HÜI$ €d€˜€‚˙This is what CVS for Windows does, for example.ŠY†IfJ1%K„*š†*fJ˙˙˙˙‹KSection A.5: Details of PuTTY's operationCBB("btn_up","JI(`',`t00000143')");EB("btn_up")W.ÜI˝J) "€\€€€€‚˙Section A.5: Details of PuTTY's operationh9fJ%K/ .€r€ăV„ůN€€€‰‚˙Question A.5.1: What terminal type does PuTTY use?f7˝J‹K/ .€n€ă‚„ůN€€€‰‚˙Question A.5.2: Where does PuTTY store its data?“b%KL1†*‰* L~L3OQuestion A.5.1: What terminal type does PuTTY use?CBB("btn_up","JI(`',`t00000168')");EB("btn_up")`7‹K~L) "€n€€€€‚˙Question A.5.1: What terminal type does PuTTY use?rHLđL* $€€˜€€€‚˙For most purposes, PuTTY can be considered to be an xterm terminal.Q~LAN7 <€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).ňÁđL3O1 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.‘`ANÄO1Rš†*'+!ÄO.€"„Question A.5.2: Where does PuTTY store its data?CBB("btn_up","JI(`',`t00000168')");EB("btn_up")^53O.€) "€j€€€€‚˙Question A.5.2: ÄO.€3OWhere does PuTTY store its data?iÄOť€$ €Ň€˜€‚˙PuTTY stores most of its data (saved sessions, SSH host keys) in the Registry. The precise location isS/.€$ €^€˜€‚˙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.ŕƒ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`<ą"„$ €x€˜€‚˙HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile}LƒŸ„1Ö‰*Z+"Ÿ„˙˙˙˙u‰Section A.6: HOWTO questionsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")J!"„é„) "€B€€€€‚˙Section A.6: HOWTO questionsn?Ÿ„W…/ .€~€ăz„ůN€€€‰‚˙Question A.6.1: How can I make PuTTY start up maximised?—hé„î…/ .€Đ€ă{„ůN€€€‰‚˙Question A.6.2: How can I create a Windows shortcut to start a particular saved session directly?„UW…r†/ .€Ş€ă|„ůN€€€‰‚˙Question A.6.3: How can I start an SSH session straight from the command line?‹\î…ý†/ .€¸€ă}„ůN€€€‰‚˙Question A.6.4: How do I copy and paste between PuTTY and other Windows applications?”er†‘‡/ .€Ę€ă~„ůN€€€‰‚˙Question A.6.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.˛‚ý†Cˆ0 .€€ă„ůN€€€‰‚˙Question A.6.6: How do I use all PuTTY's features (public keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink?˛‚‘‡őˆ0 .€€ă€„ůN€€€‰‚˙Question A.6.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.€QCˆu‰/ .€˘€ă„ůN€€€‰‚˙Question A.6.8: How do I use PSCP to copy a file whose name has spaces in?™hőˆŠ1Ú'+ç+#ŠtŠčŠQuestion A.6.1: How can I make PuTTY start up maximised?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")f=u‰tŠ) "€z€€€€‚˙Question A.6.1: How can I make PuTTY start up maximised?tPŠčŠ$ € €˜€‚˙Create a Windows shortcut to start PuTTY from, and set it as ‘Run Maximized’.‘tŠŞ‹1"Z+g+$Ş‹9Œ̍Question A.6.2: How can I create a Windows shortcut to start a particular saved session directly?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")fčŠ9Œ) "€Ě€€€€‚˙Question A.6.2: How can I create a Windows shortcut to start a particular saved session directly?ŽƒŞ‹çŒ+ $€€˜€€€‚˙To run a PuTTY session saved under the name ‘mysession’, create a Windows shortcut that invokes PuTTY with a command line likeN*9Œ5$ €T€˜€‚˙\path\name\to\putty.exe -load mysession—mçŒ̍* $€Ú€˜€€€‚˙(Note: prior to 0.53, the syntax was @session. This is now deprecated and may be removed at some point.)Ż~5{Ž1]ç+€+%{Ž÷Ž ŔQuestion A.6.3: How can I start an SSH session straight from the command line?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")|S̍÷Ž) "€Ś€€€€‚˙Question A.6.3: How can I start an SSH session straight from the command line?á°{Ž Ŕ1 0€a€˜€€€ă{„ů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.6.2.÷Ž Ŕ̍ś…÷ŽÂŔ1dg+Áƒ+&ÂŔEÁ&ĹQuestion A.6.4: How do I copy and paste between PuTTY and other Windows applications?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")ƒZ ŔEÁ) "€´€€€€‚˙Question A.6.4: How do I copy and paste between PuTTY and other Windows applications?*ůÂŔoĂ1 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.gBEÁÖÄ% €…€˜€‚˙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,oĂ&Ĺ$ €X€˜€‚˙You can also paste by pressing Shift-Ins.żŽÖÄĺĹ1í€+a„+'ĺĹqĆŇĆQuestion A.6.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.CBB("btn_up","JI(`',`t00000171')");EB("btn_up")Œc&ĹqĆ) "€Ć€€€€‚˙Question A.6.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.a=ĺĹŇĆ$ €z€˜€‚˙This is a new feature in version 0.52. You should upgrade.ÜŤqĆŽÇ1ěÁƒ+چ+(ŽÇXČšĘQuestion A.6.6: How do I use all PuTTY's features (public keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")Ş€ŇĆXČ* "€€€€€‚˙Question A.6.6: How do I use all PuTTY's features (public keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink?˘~ŽÇúČ$ €ü€˜€‚˙Most major features (e.g., public keys, port forwarding) are available through command line options. See the documentation. {XČšĘ% €÷€˜€‚˙Not all features are accessible from the command line yet, although we'd like to fix this. In the meantime, 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!).ÜŤúČvË1ţa„+_ˆ+)vË ĚtÍQuestion A.6.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(`',`t00000171')");EB("btn_up")Ş€šĘ Ě* "€€€€€‚˙Question A.6.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly.ś‘vËÖĚ% €#€˜€‚˙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 ĚtÍ* $€č€˜€ăRĹůN‰‚˙To use PSCP properly, run it from a Command Prompt window. See chapter 5 in the documentation for more details.ŤzÖĚÎ1zچ+Í,*ΗμQuestion A.6.8: How do I use PSCP to copy a file whose name has spaces in?CBB("btn_up","JI(`',`t00000171')");EB("btn_up")xOtÍ—Î) "€ž€€€€‚˙Question A.6.8: How do I use PSCP to copy a file whose name has spaces in?ĐŤÎgĎ% €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:Y5gĎ$ €j€˜€‚˙pscp user@host:myfile "local filenšĎtÍame 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˝ˆ$ €„€˜€‚˙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#ˆč# €F€€‚˙c:\>pscp user@host:"\"oo er\"" .b?˘J# €~€€‚˙warning: remote host tried to write to a file called 'oo er'Z6č¤$ €l€˜€‚˙ when we requested a file called '"oo er"'.`<J$ €x€˜€‚˙Instead, you need to specify the local file name in full:M)¤Q$ €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:BQ`# €>€€‚˙pscp "local file" user@host:E!Ľ$ €B€˜€‚˙pscp user@host:"remote file" .}L`"1  _ˆ+[,+"˙˙˙˙ôASection A.7: TroubleshootingCBB("btn_up","JI(`',`t00000143')");EB("btn_up")J!Ľl) "€B€€€€‚˙Section A.7: TroubleshootingvG"â/ .€Ž€ă¤„ůN€€€‰‚˙Question A.7.1: Why do I see ‘Incorrect MAC received on packet’?Œ]ln/ .€ş€ăĽ„ůN€€€‰‚˙Question A.7.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?žoâ / .€Ţ€ăŚ„ůN€€€‰‚˙Question A.7.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.€KnŒ5 :€–€ă§„ůN€€€€€‰‚˙Question A.7.4: Plink on Windows 95 says it can't find WS2_32.DLL.—h # / .€Đ€ă¨„ůN€€€‰‚˙Question A.7.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.™jŒź / .€Ô€ăŠ„ůN€€€‰‚˙Question A.7.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.šk# V / .€Ö€ăŞ„ůN€€€‰‚˙Question A.7.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.rCź Č / .€†€ăŤ„ůN€€€‰‚˙Question A.7.8: PSFTP transfers files much slower than PSCP.ŸpV g / .€ŕ€ăŹ„ůN€€€‰‚˙Question A.7.9: When I run full-colour applications, I see areas of black space where colour ought to be.}NČ ä / .€œ€ă؄ůN€€€‰‚˙Question A.7.10: When I change some terminal settings, nothing happens.zKg ^ / .€–€ăτůN€€€‰‚˙Question A.7.11: I can't type characters that require the AltGr key.Œ]ä ę / .€ş€ăЄůN€€€‰‚˙Question A.7.12: My PuTTY sessions unexpectedly close after they are idle for a while.Św^  / .€î€ăфůN€€€‰‚˙Question A.7.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.”_ę $5 :€ž€ă҄ůN€€€€€‰‚˙Question A.7.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.–a ş5 :€Â€ăӄůN€€€€€‰‚˙Question A.7.15: When I cat a binary file, my window title changes to a nonsense string.‰Z$C/ .€´€ăԄůN€€€‰‚˙Question A.7.16: My keyboard stops working once PuTTY displays the password prompt.—hş @/ .€Đ€ăՄůN€€€‰‚˙Question A.7.17: One or more function keys don't do what I expected in a server-side application.C @ĽŁtCŻ@/ .€č€ăքůN€€€‰‚˙Question A.7.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.Ľv @TA/ .€ě€ăׄůN€€€‰‚˙Question A.7.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY? qŻ@ôA/ .€â€ă<ŒůN€€€‰‚˙Question A.7.20: When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.ĄpTA•B1šÍ,K†,,•BCNHQuestion A.7.1: Why do I see ‘Incorrect MAC received on packet’?CBB("btn_up","JI(`',`t00000180')");EB("btn_up")nEôAC) "€Š€€€€‚˙Question A.7.1: Why do I see ‘Incorrect MAC received on packet’?ýĚ•BE1 0€™€˜€€€ă҃ůN‰‚˙One possible cause of this that used to be common is a bug in old SSH 2 servers distributed by ssh.com. (This is not the only possible cause; see section 10.10 in the documentation.) 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.ACAF% €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.;E|G% €-€˜€‚˙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.Ň­AFNH% €[€˜€‚˙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.ˇ†|GI1“[,:‰,-I‰I˜LQuestion A.7.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?CBB("btn_up","JI(`',`t00000180')");EB("btn_up")„[NH‰I) "€ś€€€€‚˙Question A.7.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?ŰśIdJ% €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‰IÇK1 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.ŃŹdJ˜L% €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.ɘÇKaM1"K†,-.aM÷MQuestion A.7.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")–m˜L÷M) "€Ú€€€€‚˙Question A.7.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal._;aMVN$ €v€˜€‚˙That isn't how you're supposed to use the Colours panel.-ö÷M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 CVN˜Lolour’, 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.ŁrVN2‚1š:‰,ú-/2‚Ş‚ë„Question A.7.4: Plink on Windows 95 says it can't find WS2_32.DLL.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")xIŞ‚/ .€’€€€€€€‚˙Question A.7.4: Plink on Windows 95 says it can't find WS2_32.DLL.ë2‚şƒ% €×€˜€‚˙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.[Ş‚9„$ €ś€˜€‚˙In order to use Plink on these systems, you will need to download the WinSock 2 upgrade:iFşƒ˘„# €Œ€€‚˙http://www.microsoft.com/windows95/downloads/contents/wuadmintools/I%9„ë„$ €J€˜€‚˙ s_wunetworkingtools/w95sockets2/‘˘„­…1ű-}-0­…<†¨‡Question A.7.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")fë„<†) "€Ě€€€€‚˙Question A.7.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.Ů­…@‡+ $€ł€˜€€€‚˙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.hD<†¨‡$ €ˆ€˜€‚˙Upgrade to version 0.52 or better and the problem should go away.ē@‡lˆ1"ú--1lˆýˆŽQuestion A.7.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")‘h¨‡ýˆ) "€Đ€€€€‚˙Question A.7.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.ŚlˆŁŠ% €€˜€‚˙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.˙ÚŁŠŽ% €ľ€˜€‚˙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 you've actually run out of memory.ŔŒSŽ1Ä}-!‚-2SŽĺŽ#ĂQuestion A.7.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")’iŽĺŽ) "€Ň€€€€‚˙Question A.7.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.ŁxSŽ”Ŕ+ $€ń€˜€ăŠ„ů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.7.6.-üĺŽÁÁ1 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%”Ŕ#Ă= 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.lÁÁŔĂ1-îƒ-3ŔĂ*ÄŰĹQuestion A.7.8: PSFTP transfers files much slower than PSCP.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")jA#Ă*Ä) "€‚€€€€‚˙Question A.7.8: PSFTP transfers files much slower than PSCP.ąŒŔĂŰĹ% €€˜€‚˙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.ʙ*ÄĽĆ1Š!‚-C…-4ĽĆ<ÇNČQuestion A.7.9: When I run full-colour applications, I see areas of black space where colour ought to be.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")—nŰĹ<Ç) "€Ü€€€€‚˙Question A.7.9: When I run full-colour applications, I see areas of black space where colour ought to be.çĽĆNČ+ $€Ď€˜€ă؄ů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 may not take effect until you reset the terminal (see question A.7.10).¨w<ÇöČ1˜îƒ->ˆ-5öČkÉŽĚQuestion A.7.10: When I change some terminal settings, nothing happens.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")uLNČkÉ) "€˜€€€€‚˙Question A.7.10: When I change some terminal settings, nothing happens.¤yöČË+ $€ó€˜€€€‚˙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ÉĚ% €Š€˜€‚˙In versions 0.53b and prior, if you 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.†bËŽĚ$ €Ä€˜€‚˙In version 0.54, the behaviour has changed - changes to these settings take effect immediately.ĽtĚ3Í1ěC…-݈-63ÍĽÍÎQuestion A.7.11: I can't type characters that require the AltGr key.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")rIŽĚĽÍ) "€’€€€€‚˙Question A.7.11: I can't type characters that require the AltGr key.zV3ÍÎ$ €Ź€˜€‚˙In PuTTY version 0.51, the AltGr key was broken. Upgrade to version 0.52 or better.ˇ†ĽÍÖÎ1>ˆ-÷.7ÖÎZĎüQuestion A.7.12: My PuTTY sessions unexpectedly close after they are idle for a while.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")„[ÎZĎ) "€ś€€€€‚˙Question A.7.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 forgeZĎŠÎt 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.óZĎÇ+ $€ç€˜€€€‚˙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Ý݈-C.8ÍkŞQuestion A.7.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")žuük) "€ę€€€€‚˙Question A.7.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.ëĆÍV% €€˜€‚˙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.fBkź$ €„€˜€‚˙On Windows 95, 98 or ME, the registry key you need to change is_<V# €x€€‚˙HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\=źX$ €2€˜€‚˙ MSTCP\MaxDataRetriesb>ş$ €|€˜€‚˙(it must be of type DWORD in Win95, or String in Win98/ME).Q-X $ €Z€˜€‚˙On Windows NT or 2000, the registry key isa>şl# €|€€‚˙HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\M) š$ €R€˜€‚˙ Parameters\TcpMaxDataRetransmissionsD lý$ €@€˜€‚˙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.ˇ†ýa 1Ý÷.w.9a í > Question A.7.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")Œ]Şí / .€ş€€€€€€‚˙Question A.7.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.;a ( $ €.€˜€‚˙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žC.€.:÷ …Á@Question A.7.15: When I cat a binary file, my window title changes to a nonsense string.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")Ž_> …/ .€ž€€€€€€‚˙Question A.7.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.´ƒŔuA18w.ż.;uAöA­CQuestion A.7.16: My keyboard stops working once PuTTY displays the password prompt.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")XÁ@öA) "€°€€€€‚˙Question A.7.16: My keyboard stops working once PuTTY displays the password prompt.ŚuAœB% €€˜€‚˙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.ćöA­C+ $€Í€˜€€€‚˙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.‘œBoD1‘€.>ˆ.<oDţDLQuestion A.7.17: One or more function keys don't do what I expected in a server-side application.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")f­CţD) "€Ě€€€€‚˙Question A.7.17: One or more function keys don't do what I expected in a server-side application.Š„oD§E% € €˜€‚˙If you've already tried all the relevant options in the PuTTY Keyboard panel, you may need to mail the PuTTY maintainers and ask.@ţDçF+ $€+€˜€€€‚˙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§EzH+ $€Ń€˜€€€‚˙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.Ŕ}çF:KC 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.ƛzHL+ $€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.Ν:KÎL1Éż.”/=ÎLiMĽƒQuestion A.7.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")›rLiM) "€ä€€€€‚˙Question A.7.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.ßşÎLHN% €u€˜€‚˙There is a known problem when OpenSSH has been built against an incorrect version of OpenSSL; the quick workaround is to configure PuTTY to use SSH protocol 2 and the Blowfish cipher.lHiM´N$ €€˜€‚˙For more details and OpenSSH patches, see bug 138 in the OpenSSH BTS.ßşHN“O% €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´N €' €ˆ€˜€€‚˙OpenSSH 3.1p1: configurations known to be broken (and symptoms):“O €L˛„“Ož€. *€ €T˜‘€8‚€ƒ€‚˙•SSH 2 with AES cipher (PuTTY says "Assertion failed! Expression: (len & 15) == 0" in sshaes.c, or "Out of memory", or crashes)rE €0- *€Š€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")B0č- *€*€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.ПЂu„1z>ˆ.•/>u„…ď†Question A.7.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?CBB("btn_up","JI(`',`t00000180')");EB("btn_up")tĽƒ…) "€č€€€€‚˙Question A.7.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?"ýu„4†% €ű€˜€‚˙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.2.1).˚4†ş‡1ě”/ł/?ş‡RˆŚ‹Question A.7.20: When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.CBB("btn_up","JI(`',`t00000180')");EB("btn_up")˜oď†Rˆ) "€Ţ€€€€‚˙Question A.7.20: When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.jFş‡źˆ$ €Œ€˜€‚˙A common complaint is that hyphens in man pages show up as a-acute.ůRˆډ% €ó€˜€‚˙With release 8.0, Red Hat appear to have made UTF-8 the default character set. There appears to be no way for terminal emulators such as PuTTY to know this (as far as we know, the appropriate escape sequence to switch into UTF-8 mode isn't sent).༈ëŠ1 0€Á€˜€ăoĹsş‰ă؄ůN‰‚˙A fix is to configure sessions to RH8 systems to use UTF-8 translation - see section 4.10.1 in the documentation. (Note that if you use ‘Change Settings’, changes may not take place immediately - see question A.7.10.)ťÚ‰Ś‹+ $€!€˜€€€‚˙If you really want to change the character set used by the server, the right place is /etc/sysconfig/i18n, but this shouldn't be necessary.€OëŠ&Œ1Š•/R /@&Œ˙˙˙˙°ŽSection A.8: Security questionsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")M$Ś‹sŒ) "€H€€€€‚˙Section A.8: Security questions„U&Œ÷Œ/ .€Ş€ă4ŒůN€€€‰‚˙Question A.8.1: Is it safe for me to download PuTTY and use it on a public PC?…VsŒ|/ .€Ź€ă5ŒůN€€€‰‚˙Question A.8.2: What does PuTTY leave on a system? How can I clean up after it?˜i÷ŒŽ/ .€Ň€ă6ŒůN€€€‰‚˙Question A.8.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?œg|°Ž5 :€Î€ă7ŒůN€€€€€‰‚˙Question A.8.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?Ż~Ž_1(ł/\‚/A_ Ŕ¸ÂQuestion A.8.1: Is it safe for me to download PuTTY and use it on a public PC?CBB("btn_up","JI(`',`t00000201')");EB("btn_up")|S°Ž Ŕ) "€Ś€€€€‚˙Question A.8.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).°żÁhĂ1ÉR /˃/BhĂĺĂ1ĹQuestion A.8.2: What does PuTTY leave on a system? How can I clean up after it?CBB("btn_up","JI(`',`t00000201')");EB("btn_up")}T¸ÂĺĂ) "€¨€€€€‚˙Question A.8.2: What does PuTTY leave on a system? How can I clean up after it?LhĂ1Ĺ1 0€7€˜€ă‚„ůN‰€€‚˙PuTTY will leave some Registry entries, and a random seed file, on the PC (see question A.5.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.ÒĺĂôĹ1t\‚/Ɔ/CôĹ„ĆhÉQuestion A.8.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?CBB("btn_up","JI(`',`t00000201')");EB("btn_up")g1Ĺ„Ć) "€Î€€€€‚˙Question A.8.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?]2ôĹáÇ+ $€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„ĆhÉ% €Ĺ€˜€‚˙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.żŽáÇ'Ę1:˃/Śˆ/D'ĘťĘaĚQuestion A.8.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?CBB("btn_up","JI(`',`t00000201')");EB("btn_up")”ehÉťĘ/ .€Ę€€€€€€‚˙Question A.8.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?Ś{'ĘaĚ+ $€÷€˜€€€‚˙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.†UťĘçĚ1(Ɔ/0EçĚ˙˙˙˙Section A.9: Administrative questionsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")S*aĚ:Í) "€T€€€€‚˙Section A.9: Administrative questions|MçĚśÍ/ .€š€ă9ŒůN€€€‰‚˙Question A.9.1: Would you like me to register you a nicer domain name?}N:Í3Î/ .€œ€ă:ŒůN€€€‰‚˙Question A.9.2: Would you like free web hosting for the PuTTY web site?n?śÍĄÎ/ .€~€ă;ŒůN€€€‰‚˙Question A.9.3: Why don't you move PuTTY to SourceForge?{L3ÎĎ/ .€˜€ăšŠůN€€€‰‚˙Question A.9.4: Why can't I subscribe to the putty-bugs mailing list?‡XĄÎŁĎ/ .€°€ă°ŠůN€€€‰‚˙Question A.9.5: If putty-bugs isn't a general-subscription mailing list, what is?l=Ď/ .€z€ăąŠůN€€€‰‚˙Question A.9.6: How can I donate to PuTTY ŁĎaĚdevelopment?§vŁĎÂ1ŠŚˆ/00FÂ6kQuestion A.9.1: Would you like me to register you a nicer domain name?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")tK6) "€–€€€€‚˙Question A.9.1: Would you like me to register you a nicer domain name?ĘĽÂ% €K€˜€‚˙No, thank you. Even if you can find one (most of them seem to have been registered already, by people who didn't ask whether we actually wanted it before they applied), we're happy with the PuTTY web site being exactly where it is. It's not hard to find (just type ‘putty’ into google.com and we're the first link returned), and we don't believe the administrative hassle of moving the site would be worth the benefit.k@6k+ $€€˜€€€‚˙In addition, if we did want a custom domain name, we would want to run it ourselves, so we knew for certain that it would continue to point where we wanted it, and wouldn't suddenly change or do strange things. Having it registered for us by a third party who we don't even know is not the best way to achieve this.¨w1š0œ0GˆĚQuestion A.9.2: Would you like free web hosting for the PuTTY web site?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")uLkˆ) "€˜€€€€‚˙Question A.9.2: Would you like free web hosting for the PuTTY web site?D Ě$ €@€˜€‚˙We already have some, thanks.™hˆe1ž00˝0HeË# Question A.9.3: Why don't you move PuTTY to SourceForge?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")f=ĚË) "€z€€€€‚˙Question A.9.3: Why don't you move PuTTY to SourceForge?€VeK* $€Ź€˜€ă9ŒůN‰‚˙Partly, because we don't want to move the web site location (see question A.9.1).%Ëp % €€˜€‚˙Also, security reasons. PuTTY is a security product, and as such it is particularly important to guard the code and the web site against unauthorised modifications which might introduce subtle security flaws. Therefore, we prefer that the CVS repository, web site and FTP site remain where they are, under the direct control of system administrators we know and trust personally, rather than being run by a large organisation full of people we've never met and which is known to have had breakins in the past.łŽK# % €€˜€‚˙No offence to SourceForge; I think they do a wonderful job. But they're not ideal for everyone, and in particular they're not ideal for us.Śup É 1œ0ę0IÉ < J Question A.9.4: Why can't I subscribe to the putty-bugs mailing list?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")sJ# < ) "€”€€€€‚˙Question A.9.4: Why can't I subscribe to the putty-bugs mailing list?ăÉ J + $€Ç€˜€€€‚˙Because you're not a member of the PuTTY core development team. The putty-bugs mailing list is not a general newsgroup-like discussion forum; it's a contact address for the core developers, and an internal mailing list for us to discuss things among ourselves. If we opened it up for everybody to subscribe to, it would turn into something more like a newsgroup and we would be completely overwhelmed by the volume of traffic. It's hard enough to keep up with the list as it is.˛< ü 1.˝0€0Jü {6@Question A.9.5: If putty-bugs isn't a general-subscription mailing list, what is?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")VJ {) "€Ź€€€€‚˙Question A.9.5: If putty-bugs isn't a general-subscription mailing list, what is?H$ü Ă$ €H€˜€‚˙There isn't one, that we know of.g<{6@+ $€y€˜€€€‚˙If someone else wants to set up a mailing list or other forum for PuTTY users to help each other with common problems, that would be fine with us, though the PuTTY team would almost certainly not have the time to read it. It's probably better to use the established newsgroĂ6@J up comp.security.ssh for this purpose.—fĂÍ@1ę0ԅ0KÍ@1A]GQuestion A.9.6: How can I donate to PuTTY development?CBB("btn_up","JI(`',`t00000206')");EB("btn_up")d;6@1A) "€v€€€€‚˙Question A.9.6: How can I donate to PuTTY development?Ń Í@C1 0€A€˜€€€€€‚˙Please, please don't feel you have to. PuTTY is completely free software, and not shareware. We think it's very important that everybody who wants to use PuTTY should be able to, whether they have any money or not; so the last thing we would want is for a PuTTY user to feel guilty because they haven't paid us any money. If you want to keep your money, please do keep it. We wouldn't dream of asking for any.đł1AňD= H€g€˜€€€€€€€€€‚˙Having said all that, if you still really want to give us money, we won't argue :-) The easiest way for us to accept donations is if you go to www.e-gold.com, and deposit your donation in account number 174769. Then send us e-mail to let us know you've done so (otherwise we might not notice for months!). Alternatively, if e-gold isn't convenient for you, you can donate to using PayPal (www.paypal.com).kFC]G% €€˜€‚˙Small donations (tens of dollars or tens of euros) will probably be spent on beer or curry, which helps motivate our volunteer team to continue doing this for the world. Larger donations will be spent on something that actually helps development, if we can find anything (perhaps new hardware, or a copy of Windows XP), but if we can't find anything then we'll just distribute the money among the developers. If you want to be sure your donation is going towards something worthwhile, ask us first. If you don't like these terms, feel perfectly free not to donate. We don't mind.†UňDăG1í€0܆0LăG˙˙˙˙ĐISection A.10: Miscellaneous questionsCBB("btn_up","JI(`',`t00000143')");EB("btn_up")S*]G6H) "€T€€€€‚˙Section A.10: Miscellaneous questionswHăG­H/ .€€ăłŠůN€€€‰‚˙Question A.10.1: Is PuTTY a port of OpenSSH, or based on OpenSSH?c46HI/ .€h€ă´ŠůN€€€‰‚˙Question A.10.2: Where can I buy silly putty?^/­HnI/ .€^€ăľŠůN€€€‰‚˙Question A.10.3: What does ‘PuTTY’ mean?b3IĐI/ .€f€ăśŠůN€€€‰‚˙Question A.10.4: How do I pronounce ‘PuTTY’?˘qnIrJ1`ԅ0î‡0MrJáJŇKQuestion A.10.1: Is PuTTY a port of OpenSSH, or based on OpenSSH?CBB("btn_up","JI(`',`t00000213')");EB("btn_up")oFĐIáJ) "€Œ€€€€‚˙Question A.10.1: Is PuTTY a port of OpenSSH, or based on OpenSSH?ńĚrJŇK% €™€˜€‚˙No, it isn't. PuTTY is almost completely composed of code written from scratch for PuTTY. The only code we share with OpenSSH is the detector for SSH1 CRC compensation attacks, written by CORE SDI S.A.Ž]áJ`L1Ű܆0Q‰0N`LťL;NQuestion A.10.2: Where can I buy silly putty?CBB("btn_up","JI(`',`t00000213')");EB("btn_up")[2ŇKťL) "€d€€€€‚˙Question A.10.2: Where can I buy silly putty?‘m`LLM$ €Ú€˜€‚˙You're looking at the wrong web site; the only PuTTY we know about here is the name of a computer program.ďÄťL;N+ $€‰€˜€€€‚˙If you want the kind of putty you can buy as an executive toy, the PuTTY team can personally recommend Thinking Putty, which you can buy from Crazy Aaron's Putty World, at www.puttyworld.com.‰XLMÄN1ˇî‡01OÄNO‡€Question A.10.3: What does ‘PuTTY’ mean?CBB("btn_up","JI(`',`t00000213')");EB("btn_up")V-;NO) "€Z€€€€‚˙Question A.10.3: What does ‘PuTTY’ mean?a6ÄN‡€+ $€m€˜€€€‚˙It's the name of a popular SSH and Telnet client. Any other meaning is in the eye of the beholder. It's been rumoured that ‘PuTTY’ is the antonym of ‘getty’, or that it's the stuff thaO‡€;Nt makes your Windows useful, or that it's a kind of plutonium Teletype. We couldn't possibly comment on such allegations.\O1ĎQ‰0y1PnăQuestion A.10.4: How do I pronounce ‘PuTTY’?CBB("btn_up","JI(`',`t00000213')");EB("btn_up")Z1‡€n) "€b€€€€‚˙Question A.10.4: How do I pronounce ‘PuTTY’?uHă- *€€˜€€€€‚˙Exactly like the English word ‘putty’, which we pronounce /'pVtI/.Pnd‚1ˇ1á1Qd‚¸‚ˆAppendix B: Feedback and bug reportingCBB("btn_up","JI(`',`Top')");EB("btn_up")T+へ‚) "€V€€€€‚˙Appendix B: Feedback and bug reportingĆĄd‚~ƒ% €C€˜€‚˙This is a guide to providing feedback to the PuTTY development team. It is provided as both a web page on the PuTTY site, and an appendix in the PuTTY manual. ḂŠ„+ $€Ă€˜ă¸ŠůN€‰‚˙Section B.1 gives some general guidelines for sending any kind of e-mail to the development team. Following sections give more specific guidelines for particular types of e-mail, such as bug reports and feature requests.U&~ƒ߄/ .€L€ă¸ŠůN€€€‰‚˙Section B.1: General guidelinesQ"Š„0…/ .€D€ăۊůN€€€‰‚˙Section B.2: Reporting bugs\-߄Œ…/ .€Z€ă܊ůN€€€‰‚˙Section B.3: Requesting extra featureswH0…†/ .€€ă݊ůN€€€‰‚˙Section B.4: Requesting features that have already been requestedS$Œ…V†/ .€H€ăފůN€€€‰‚˙Section B.5: Support requests\-†˛†/ .€Z€ăߊůN€€€‰‚˙Section B.6: Web server administration_0V†‡/ .€`€ăŕŠůN€€€‰‚˙Section B.7: Asking permission for things_0˛†p‡/ .€`€ăáŠůN€€€‰‚˙Section B.8: Mirroring the PuTTY web siteY*‡ɇ/ .€T€ăâŠůN€€€‰‚˙Section B.9: Praise and complimentsR#p‡ˆ/ .€F€ăăŠůN€€€‰‚˙Section B.10: E-mail address€Oɇ›ˆ1%y1ü1R›ˆčˆŔŽSection B.1: General guidelinesCBB("btn_up","JI(`',`t00000218')");EB("btn_up")M$ˆčˆ) "€H€€€€‚˙Section B.1: General guidelinesX'›ˆ@Š1 0€O€˜€€€€€‚˙The PuTTY development team gets a lot of mail. If you can possibly solve your own problem by reading the manual, reading the FAQ, reading the web site, asking a fellow user, perhaps posting on the newsgroup comp.security.ssh, or some other means, then it would make our lives much easier.œečˆ܋7 <€Ë€˜€€€ăފůN‰€€‚˙We get so much e-mail that we literally do not have time to answer it all. We regret this, but there's nothing we can do about it. So if you can possibly avoid sending mail to the PuTTY team, we recommend you do so. In particular, support requests (section B.5) are probably better sent to comp.security.ssh or passed to a local expert if possible.Ž‰@ŠŠ% €€˜€‚˙The PuTTY contact email address is a private mailing list containing four or five core developers. Don't be put off by it being a mailing list: if you need to send confidential data as part of a bug report, you can trust the people on the list to respect that confidence. Also, the archives aren't publicly available, so you shouldn't be letting yourself in for any spam by sending us mail.س܋bŽ% €g€˜€‚˙Please use a meaningful subject line on your message. We get a lot of mail, and it's hard to find the message we're looking for if they all have subject lines like ‘PuTTY bug’.^/ŠŔŽ/ .€^€ăäŠůN€€€‰‚˙Section B.1.1: Sending large attachments‰XbŽI1} á1‰1SIŸŇĘSection B.1.1: Sending large attachmentsCBB("btn_up","JI(`',`t00000219')");EB("btn_up")V-ŔŽŸ) "€Z€€€€‚˙Section B.1.1: Sending large attachmentsÝI­Ŕ% €ť€˜€‚˙Since the PuTTY contact address is a mailing list, e-mails Ÿ­ŔŔŽlarger than 40Kb will be held for inspection by the list administrator, and will not be allowed through unless they really appear to be worth their large size.ňÍŸŸÂ% €›€˜€‚˙If you are considering sending any kind of large data file to the PuTTY team, it's almost always a bad idea, or at the very least it would be better to ask us first whether we actually need the file. Alternatively, you could put the file on a web site and just send us the URL; that way, we don't have to download it unless we decide we actually need it, and only one of us needs to download it instead of it being automatically copied to all the developers.ŰŞ­ŔzÄ1 0€U€˜€€€€€‚˙Some people like to send mail in MS Word format. Please don't send us bug reports, or any other mail, as a Word document. Word documents are roughly fifty times larger than writing the same report in plain text. In addition, most of the PuTTY team read their e-mail on Unix machines, so copying the file to a Windows box to run Word is very inconvenient. Not only that, but several of us don't even have a copy of Word!tIŸÂîĆ+ $€“€˜€€€‚˙Some people like to send us screen shots when demonstrating a problem. Please don't do this without checking with us first - we almost never actually need the information in the screen shot. Sending a screen shot of an error box is almost certainly unnecessary when you could just tell us in plain text what the error was. (On some versions of Windows, pressing Ctrl-C when the error box is displayed will copy the text of the message to the clipboard.) Sending a full-screen shot is occasionally useful, but it's probably still wise to check whether we need it before sending it.5řzÄ#Č= H€ń€˜€€€€€€€€€‚˙If you must mail a screen shot, don't send it as a .BMP file. BMPs have no compression and they are much larger than other image formats such as PNG, TIFF and GIF. Convert the file to a properly compressed image format before sending it.đîĆ8É% €á€˜€‚˙Please don't mail us executables, at all. Our mail server blocks all incoming e-mail containing executables, as a defence against the vast numbers of e-mail viruses we receive every day. If you mail us an executable, it will just bounce.ši#ČŇĘ1 0€Ó€˜€€€€€‚˙If you have made a tiny modification to the PuTTY code, please send us a patch to the source code if possible, rather than sending us a huge .ZIP file containing the complete sources plus your modification. If you've only changed 10 lines, we'd prefer to receive a mail that's 30 lines long than one containing multiple megabytes of data we already have.|K8ÉNË1"ü1š 2TNË—Ë|Section B.2: Reporting bugsCBB("btn_up","JI(`',`t00000218')");EB("btn_up")I ŇĘ—Ë) "€@€€€€‚˙Section B.2: Reporting bugsnJNËĚ$ €”€˜€‚˙If you think you have found a bug in PuTTY, your first steps should be:¤p—ËŠÍ4 6€á€T˜‘€8‚€ƒ€€€‚˙•Check the Wishlist page on the PuTTY website, and see if we already know about the problem. If we do, it is almost certainly not necessary to mail us about it, unless you think you have extra information that might be helpful to us in fixing it. (Of course, if we actually need specific extra information about a particular bug, the Wishlist page will say so.)¤wĚMÎ- *€î€T˜‘€8‚€ƒ€‚˙•Check the Change Log on the PuTTY website, and see if we have already fixed the bug in the development snapshots. ŐŠÍVĎ4 6€Ť€T˜‘€8‚€ƒ€ăúƒůN‰‚˙•Check the FAQ on the PuTTY website (also provided as appendix A in the manual), and see if it answers your question. The FAQ lists the most common things which people think are bugs, but which aren't bugs.;MΝ4 6€€T˜‘€8‚€ƒ€€€‚˙•Download the latest development snapshot and see if the problem still happens with that. This really is worth doinVϝŇĘg. As a general rule we aren't very interested in bugs that appear in the release version but not in the development version, because that usually means they are bugs we have already fixed. On the other hand, if you can find a bug in the development version that doesn't appear in the release, that's likely to be a new bug we've introduced since the release and we're definitely interested in it.ľVĎR% €!€˜€‚˙If none of those options solved your problem, and you still need to report a bug to us, it is useful if you include some general information:['­4 6€O€T˜‘€8‚€ƒ€€€‚˙•Tell us what version of PuTTY you are running. To find this out, use the "About PuTTY" option from the System menu. Please do not just tell us ‘I'm running the latest version’; e-mail can be delayed and it may not be obvious which version was the latest at the time you sent the message.ěžR™. *€}€T˜‘€8‚€ƒ€‚˙•Tell us what version of what OS you are running PuTTY on. (If you're running on Windows for Alpha, tell us, or we'll assume you're running on Intel as this is overwhelmingly the case.)‚U­- *€Ş€T˜‘€8‚€ƒ€‚˙•Tell us what protocol you are connecting with: SSH, Telnet, Rlogin or Raw mode.ݙ,4 6€ť€T˜‘€8‚€ƒ€ă{ÄůN‰‚˙•Tell us what kind of server you are connecting to; what OS, and if possible what SSH server (if you're using SSH). You can get some of this information from the PuTTY Event Log (see section 3.1.3.1 in the manual).â<. *€Ĺ€T˜‘€8‚€ƒ€‚˙•Send us the contents of the PuTTY Event Log, unless you have a specific reason not to (for example, if it contains confidential information that you think we should be able to solve your problem without needing to know).óż,/4 6€€T˜‘€8‚€ƒ€€€‚˙•Try to give us as much information as you can to help us see the problem for ourselves. If possible, give us a step-by-step sequence of precise instructions for reproducing the fault.Ţ°< . *€a€T˜‘€8‚€ƒ€‚˙•Don't just tell us that PuTTY ‘does the wrong thing’; tell us exactly and precisely what it did, and also tell us exactly and precisely what you think it should have done instead. Some people tell us PuTTY does the wrong thing, and it turns out that it was doing the right thing and their expectations were wrong. Help to avoid this problem by telling us exactly what you think it should have done, and exactly what it did do.´€/Á 4 6€€T˜‘€8‚€ƒ€€€‚˙•If you think you can, you're welcome to try to fix the problem yourself. A patch to the code which fixes a bug is an excellent addition to a bug report. However, a patch is never a substitute for a good bug report; if your patch is wrong or inappropriate, and you haven't supplied us with full information about the actual bug, then we won't be able to find a better solution.*ó ë 7 <€ç€T˜‘€8‚€ƒ€€€€‚˙•http://www.chiark.greenend.org.uk/~sgtatham/bugs.html is an article on how to report bugs effectively in general. If your bug report is particularly unclear, we may ask you to go away, read this article, and then report the bug again.‘NÁ |C T€€˜€€€€€€€€€€€‚˙It is reasonable to report bugs in PuTTY's documentation, if you think the documentation is unclear or unhelpful. But we do need to be given exact details of what you think the documentation has failed to tell you, or how you think it could be made clearer. If your problem is simply that you don't understand the documentation, we suggest posting to the newsgroup comp.security.ssh and see if someone will explain what you need to know. Then, if you think the documentation could usefully have told you that, send us a bug report and explain how you think we should change it.‡Vë @1 ‰1ć‡2U@c@+ISection B.3: Requesting extra featuresCBB("btn_up","JI(`',`t00000218')");EB("btn_u|@|p")T+|c@) "€V€€€€‚˙Section B.3: Requesting extra features~Z@á@$ €´€˜€‚˙If you want to request a new feature in PuTTY, the very first things you should do are:@ c@!B4 6€€T˜‘€8‚€ƒ€ă݊ůN‰‚˙•Check the Wishlist page on the PuTTY website, and see if your feature is already on the list. If it is, it probably won't achieve very much to repeat the request. (But see section B.4 if you want to persuade us to give your particular feature higher priority.)qCá@’C. *€‡€T˜‘€8‚€ƒ€‚˙•Check the Wishlist and Change Log on the PuTTY website, and see if we have already added your feature in the development snapshots. If it isn't clear, download the latest development snapshot and see if the feature is present. If it is, then it will also be in the next release and there is no need to mail us at all.é!BŚD+ $€Ó€˜€€€‚˙If you can't find your feature in either the development snapshots or the Wishlist, then you probably do need to submit a feature request. Since the PuTTY authors are very busy, it helps if you try to do some of the work for us:´†’CZG. *€ €T˜‘€8‚€ƒ€‚˙•Do as much of the design as you can. Think about ‘corner cases’; think about how your feature interacts with other existing features. Think about the user interface; if you can't come up with a simple and intuitive interface to your feature, you shouldn't be surprised if we can't either. Always imagine whether it's possible for there to be more than one, or less than one, of something you'd assumed there would be one of. (For example, if you were to want PuTTY to put an icon in the System tray rather than the Taskbar, you should think about what happens if there's more than one PuTTY active; how would the user tell which was which?)ŃŁŚD+I. *€G€T˜‘€8‚€ƒ€‚˙•If you can program, it may be worth offering to write the feature yourself and send us a patch. However, it is likely to be helpful if you confer with us first; there may be design issues you haven't thought of, or we may be about to make big changes to the code which your patch would clash with, or something. If you check with the maintainers first, there is a better chance of your code actually being usable.˘qZGÍI19š 2§3VÍI.tC<ĚÍ1Ě"ˆ3˙˙˙˙]ÍbÍóAppendix C: PuTTY LicenceCBB("btn_up","JI(`',`Top')");EB("btn_up")G§ĚbÍ) "€<€€€€‚˙Appendix C: PuTTY LicenceQ-ÍłÍ$ €Z€˜€‚˙PuTTY is copyright 1997-2004 Simon Tatham.ͨbÍ€Î% €Q€˜€‚˙Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, and CORE SDI S.A.ŘłłÍd% €g€˜€‚˙Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit pe€Îd§Ěrsons to whom the Software is furnished to do so, subject to the following conditions:Ś€Î % €€˜€‚˙The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.éÄdó% €‰€˜€‚˙THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.1 ˙˙˙˙1˙˙˙˙˙˙˙˙^˙˙˙˙˙˙˙˙˙˙˙˙/X&X;)Lz ˙˙ ^,˙˙ContentsŸChapter 1: Introduction to PuTTY}Section 1.1: What are SSH, Telnet and Rlogin?ě‚Section 1.2: How do SSH, Telnet and Rlogin differ?ωChapter 2: Getting started with PuTTY‹Section 2.1: Starting a sessionuSection 2.2: Verifying the Host Key (SSH only)ú„Section 2.3: Logging In+‰Section 2.4: After Logging InŽŠSection 2.5: Logging OutBChapter 3: Using PuTTYeSection 3.1: During your sessionSection 3.1.1: Copying and pasting textR…Section 3.1.2: Scrolling the screen backwˆSection 3.1.3: The System menu(Section 3.1.3.1: The PuTTY Event LogkSection 3.1.3.2: Special commandsŤSection 3.1.3.3: Starting new sessions+Section 3.1.3.4: Changing your session settingsœSection 3.1.3.5: Copy All to ClipboardX Section 3.1.3.6: Clearing and resetting the terminaliSection 3.1.3.7: Full screen modeĽƒSection 3.2: Creating a log file of your sessionŻ†Section 3.3: Altering your character set configuration‰Section 3.4: Using X11 forwarding in SSHßSection 3.5: Using port forwarding in SSHŒ‹Section 3.6: Making raw TCP connectionsŢSection 3.7: The PuTTY command line9Section 3.7.1: Starting a session from the command lineSection 3.7.2: -cleanupfSection 3.7.3: Standard command-line optionsDƒSection 3.7.3.1: -load: load a saved sessioná†Section 3.7.3.2: Selecting a protocol: -ssh, -telnet, -rlogin, -rawSection 3.7.3.3: -v: increase verbosity9Section 3.7.3.4: -l: specify a login name}Section 3.7.3.5: -L, -R and -D: set up port forwardings)Section 3.7.3.6: -m: read a remote command or script from a fileA Section 3.7.3.7: -P: specify a port number˙Section 3.7.3.8: -pw: specify a passwordëƒSection 3.7.3.9: -A and -a: control agent forwardingP†Section 3.7.3.10: -X and -x: control X11 forwardingˆSection 3.7.3.11: -t and -T: control pseudo-terminal allocationSection 3.7.3.12: -C: enable compression7Section 3.7.3.13: -1 and -2: specify an SSH protocol version)žSection 3.7.3.14: -i: specify an SSH private key—Chapter 4: Configuring PuTTY €Section 4.1: The Session panel‚Section 4.1.1: The host name sectionŤ…Section 4.1.2: Loading and storing saved sessions:Section 4.1.3: ‘Close Window on Exit’RSection 4.2: The Logging panel,‚Section 4.2.1: ‘Log file name’’†Section 4.2.2: ‘What to do if the log file already exists’ŚˆSection 4.3: The Terminal panelĐ Section 4.3.1: ‘Auto wrap mode initially on’˜ Section 4.3.2: ‘DEC Origin Mode initially on’‰ Section 4.3.3: ‘Implicit CR in every LF’ Section 4.3.4: ‘Use background colour to erase screen’Ó„ Section 4.3.5: ‘Enable blinking text’m‡ Section 4.3.6: ‘Answerback to ^E’ Section 4.3.7: ‘Local echo’Č Section 4.3.8: ‘Local line editing’Ů Section 4.3.9: Remote-controlled printing‚€ Section 4.4: The Keyboard panelć‚ Section 4.4.1: Changing the action of the Backspace keyˆ† Section 4.4.2: Changing the action of the Home and End keysˆ Section 4.4.3: Changing the action of the function keys and keypad} Section 4.4.4: Controlling Application Cursor Keys modeź Section 4.4.5: Controlling Application Keypad mode˛ Section 4.4.6: Using NetHack keypad mode}‚ Section 4.4.7: Enabling a DEC-like Compose keyӄ Section 4.4.8: ‘Control-Alt is different from AltGr’}ˆ Section 4.5: The Bell panelšŠ Section 4.5.1: ‘Set the style of bell’V Section 4.5.2: ‘Taskbar/caption indication on bell’• Section 4.5.3: ‘Control the bell overload behaviour’ű€ Section 4.6: The Features panel^„ Section 4.6.1: Disabling application keypad and cursor keysđ… Section 4.6.2: Disabling xterm-style mouse reporting ‰ Section 4.6.3: Disabling remote terminal resizingč Section 4.6.4: Disabling switching to the alternate screenx Section 4.6.5: Disabling remote window title changingŠ Section 4.6.6: Disabling remote window title querying% Section 4.6.7: Disabling destructive backspaceÁ Section 4.6.8: Disabling remote character set configuration (ƀ Section 4.7: The Window panel‚ Section 4.7.1: Setting the size of the PuTTY windowď‚ Section 4.7.2: What to do when the window is resized ‡ Section 4.7.3: Controlling scrollbackSection 4.7.4: ‘Push erased text into scrollback’&Section 4.8: The Appearance panelŤSection 4.8.1: Controlling the appearance of the cursor/Section 4.8.2: Controlling the font used in the terminal windowŽSection 4.8.3: ‘Hide mouse pointer when typing in window’.Section 4.8.4: Controlling the window borderí€Section 4.9: The Behaviour panelá‚Section 4.9.1: Controlling the window titleĄ‡Section 4.9.2: ‘Warn before closing window’:‰Section 4.9.3: ‘Window closes on ALT-F4’Section 4.9.4: ‘System menu appears on ALT-Space’Section 4.9.5: ‘System menu appears on Alt alone’$Section 4.9.6: ‘Ensure window is always on top’­Section 4.9.7: ‘Full screen on Alt-Enter’!Section 4.10: The Translation panelúSection 4.10.1: Controlling character set translation$„Section 4.10.2: ‘Caps Lock acts as Cyrillic switch’ž…Section 4.10.3: Controlling display of line drawing charactersSection 4.10.4: Controlling copy and paste of line drawing charactersşSection 4.11: The Selection panelXSection 4.11.1: Pasting in Rich Text Format‘Section 4.11.2: Changing the actions of the mouse buttons€Section 4.11.3: ‘Shift overrides application's use of mouse’U„Section 4.11.4: Default selection modeB‡Section 4.11.5: Configuring word-by-word selectionSection 4.12: The Colours panelÄSection 4.12.1: ‘Bolded text is a different colour’+Section 4.12.2: ‘Attempt to use logical palettes’ÂSection 4.12.3: ‘Use system colours’e Section 4.12.4: Adjusting the colours in the terminal windowÁSection 4.13: The Connection panelƒSection 4.13.1: ‘Terminal-type string’—†Section 4.13.2: ‘Auto-login username’ś‡Section 4.13.3: Using keepalives to prevent disconnectionaSection 4.13.4: ‘Disable Nagle's algorithm’ Section 4.14: The Proxy panel1' Section 4.14.1: Setting the proxy typeƒSection 4.14.2: Excluding parts of the network from proxying!‰Section 4.14.3: Name resolution when using a proxyJSection 4.14.4: Username and passwordGSection 4.14.5: Specifying the Telnet proxy command7 Section 4.15: The Telnet panelπSection 4.15.1: ‘Terminal-speed string’ńSection 4.15.2: Setting environment variables on the server’„Section 4.15.3: ‘Handling of OLD_ENVIRON ambiguity’ęˆSection 4.15.4: Passive and active Telnet negotiation modesŹSection 4.15.5: ‘Keyboard sends telnet Backspace and Interrupt’ÚSection 4.15.6: ‘Return key sends telnet New Line instead of ^M’Section 4.16: The Rlogin panelNSection 4.16.1: ‘Terminal-speed string’}Section 4.16.2: ‘Local username’…‚Section 4.17: The SSH panel„Section 4.17.1: Executing a specific command on the server7…Section 4.17.2: ‘Don't allocate a pseudo-terminal’|‡Section 4.17.3: ‘Enable compression’áˆSection 4.17.4: ‘Preferred SSH protocol version’Section 4.17.5: Encryption algorithm selectionSection 4.18: The Auth panel( Section 4.18.1: ‘Attempt TIS or CryptoCard authentication’¸‚Section 4.18.2: ‘Attempt keyboard-interactive authentication’Ů„Section 4.18.3: ‘Allow agent forwarding’|†Section 4.18.4: ‘Allow attempted changes of username in SSH2’;ŠSection 4.18.5: ‘Private key file for authentication’Section 4.19: The Tunnels panelSection 4.19.1: X11 forwardingpSection 4.19.1.1: Remote X11 authenticationl€Section 4.19.2: Port forwardingr‡Section 4.19.3: Controlling the visibility of forwarded portsöŠSection 4.20: The Bugs panel!Section 4.20.1: ‘Chokes on SSH1 ignore messages’ Section 4.20.2: ‘Refuses all SSH1 password camouflage’ąSection 4.20.3: ‘Chokes on SSH1 RSA authentication’đƒSection 4.20.4: ‘Miscomputes SSH2 HMAC keys’?†Section 4.20.5: ‘Miscomputes SSH2 encryption keys’~ˆSection 4.20.6: ‘Requires padding on SSH2 RSA signatures’;' Section 4.20.7: ‘Chokes on Diffie-Hellman group exchange’ŚSection 4.20.8: ‘Misuses the session ID in PK auth’ISection 4.21: Storing configuration in a file8Chapter 5: Using PSCP to transfer files securelyă‚Section 5.1: Starting PSCPr†Section 5.2: PSCP UsageSection 5.2.1: The basicsîSection 5.2.1.1: userä‚Section 5.2.1.2: hostźƒSection 5.2.1.3: source@†Section 5.2.1.4: targetgˆSection 5.2.2: OptionsßSection 5.2.2.1: -p preserve file attributesąSection 5.2.2.2: -q quiet, don't show statisticsňSection 5.2.2.3: -r copies directories recursivelybSection 5.2.2.4: -batch avoid interactive promptsPSection 5.2.3: Return valueWSection 5.2.4: Using public key authentication with PSCP&„Section 5.3: Secure iXplorerš„Chapter 6: Using PSFTP to transfer files securelyRˆSection 6.1: Starting PSFTP,Section 6.1.1: -b: specify a file containing batch commandsÉSection 6.1.2: -bc: display batch commands as they are run‹‚Section 6.1.3: -be: continue batch processing on errorsƒSection 6.1.4: -batch: avoid interactive promptsą…Section 6.2: Running PSFTPĐSection 6.2.1: General quoting rules for PSFTP commandsşSection 6.2.2: The open command: start a sessionW Section 6.2.3: The quit command: end your sessionHSection 6.2.4: The help command: get quick online help_‚Section 6.2.5: The cd and pwd commands: changing the remote working directoryA„Section 6.2.6: The lcd and lpwd commands: changing the local working directory…†Section 6.2.7: The get command: fetch a file from the server†ˆSection 6.2.8: The put command: send a file to the serverPSection 6.2.9: The reget and reput commands: resuming file transfersŽSection 6.2.10: The dir command: list remote filesĎSection 6.2.11: The chmod command: change permissions on remote filesĄSection 6.2.12: The del command: delete remote files…Section 6.2.13: The mkdir command: create remote directories%'2†Section 6.2.14: The rmdir command: remove remote directoriesj‡Section 6.2.15: The ren command: rename remote filesfˆSection 6.2.16: The ! command: run a local Windows commandxSection 6.3: Using public key authentication with PSFTP›Chapter 7: Using the command-line connection tool PlinkżSection 7.1: Starting Plink.‚Section 7.2: Using PlinkL‰Section 7.2.1: Using Plink for interactive logins/Section 7.2.2: Using Plink for automated connectionsş„Section 7.2.3: Plink command line optionse†Section 7.2.3.1: -batch: disable all interactive prompts\ˆSection 7.2.3.2: -s: remote command is SSH subsystem_‰Section 7.3: Using Plink in batch files and scripts– Section 7.4: Using Plink with CVSé Section 7.5: Using Plink with WinCVSÍ Chapter 8: Using public keys for SSH authenticationž Section 8.1: Public key authentication - an introductiondŒ Section 8.2: Using PuTTYgen, the PuTTY key generator:!Section 8.2.1: Generating a new keyb!Section 8.2.2: Selecting the type of key4ƒ!Section 8.2.3: Selecting the size (strength) of the keyĄ†!Section 8.2.4: The ‘Generate’ buttonp‹!Section 8.2.5: The ‘Key fingerprint’ boxB"Section 8.2.6: Setting a comment for your key†"Section 8.2.7: Setting a passphrase for your keyA€"Section 8.2.8: Saving your private key to a disk fileZ‚"Section 8.2.9: Saving your public key to a disk fileH†"Section 8.2.10: ‘Public key for pasting into authorized_keys file’ ‰"Section 8.2.11: Reloading a private key<#Section 8.2.12: Dealing with private keys in other formatsP#Section 8.3: Getting ready for public key authentication/…#Chapter 9: Using Pageant for authenticationá†#Section 9.1: Getting started with Pageant´$Section 9.2: The Pageant main windowr$Section 9.2.1: The key list boxó$Section 9.2.2: The ‘Add Key’ button€$Section 9.2.3: The ‘Remove Key’ buttonm$Section 9.3: The Pageant command lineƒ$Section 9.3.1: Making Pageant automatically load keys on startup$ „$Section 9.3.2: Making Pageant run another program[†$Section 9.4: Using agent forwarding.%Section 9.5: Security considerations1…%Chapter 10: Common error messages&Section 10.1: ‘The server's host key is not cached in the registry’ţ&Section 10.2: ‘WARNING - POTENTIAL SECURITY BREACH!’p&Section 10.3: ‘Out of space for port forwardings’r &Section 10.4: ‘The first cipher supported by the server is ... below the configured warning threshold’€&Section 10.5: ‘Server sent disconnect message type 2 (SSH_DISCONNECT_PROTOCOL_ERROR): "Too many authentication failures for root"’‚&Section 10.6: ‘Out of memory’ˆ&Section 10.7: ‘Internal error’, ‘Internal fault’, ‘Assertion failed’Ľ‰&Section 10.8: ‘Server refused our public key’ or ‘Key refused’)'Section 10.9: ‘Access denied’, ‘Authentication refused’ç'Section 10.10: ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’¸'Section 10.11: ‘Incoming packet was garbled on decryption’'Section 10.12: ‘Authentication failed at PuTTY X11 proxy’Dƒ'Section 10.13: ‘Network error: Software caused connection abort’m…'Section 10.14: ‘Network error: Connection reset by peer’߇'Section 10.15: ‘Network error: Connection refused’Ą‰'Section 10.16: ‘Network error: Connection timed out’(Appendix A: PuTTY FAQ%(Section A.1: Introductiong(Section A.1.1: What is PuTTY?C(Section A.2: Features supported in PuTTYś(Question A.2.1: Does PuTTY support SSH v2?|‚(Question A.2.2: Does PuTTY support reading OpenSSH or ssh.com SSHv2 private key files?fƒ(Question A.2.3: Does PuTTY support SSH v1?΃(Question A.2.4: Does PuTTY support local echo? ‡(Question A.2.5: Does PuTTY support storing its settings in a disk file?Ň(Question A.2.6: Does PuTTY support full-screen mode, like a DOS box?<ˆ(Question A.2.7: Does PuTTY have the ability to remember my password so I don't have to type it every time?)Question A.2.8: Is there an option to turn off the annoying host key prompts?B% )Question A.2.9: Will you write an SSH server for the PuTTY suite, to go with the client?q‚)Question A.2.10: Can PSCP or PSFTP transfer files in ASCII mode?%„)Section A.3: Ports to other operating systemsi‡)Question A.3.1: What ports of PuTTY exist?Š)Question A.3.2: Is there a port to Unix?Ť*Question A.3.3: Will there be a port to Windows CE or PocketPC?×*Question A.3.4: Is there a port to Windows 3.1?Ý*Question A.3.5: Will there be a port to the Mac?Ż*Question A.3.6: Will there be a port to EPOC?| *Section A.4: Embedding PuTTY in other programsa€*Question A.4.1: Is the SSH or Telnet code available as a DLL? ‚*Question A.4.2: Is the SSH or Telnet code available as a Visual Basic component?K„*Question A.4.3: How can I use PuTTY to make an SSH connection from within another program?†*Section A.5: Details of PuTTY's operationš†*Question A.5.1: What terminal type does PuTTY use?‰*Question A.5.2: Where does PuTTY store its data?'+Section A.6: HOWTO questionsZ+Question A.6.1: How can I make PuTTY start up maximised?ç+Question A.6.2: How can I create a Windows shortcut to start a particular saved session directly?g+Question A.6.3: How can I start an SSH session straight from the command line?€+Question A.6.4: How do I copy and paste between PuTTY and other Windows applications?Áƒ+Question A.6.5: How do I use X forwarding and port forwarding? I can't find the Tunnels panel.a„+Question A.6.6: How do I use all PuTTY's features (public keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink?چ+Question A.6.7: How do I use PSCP.EXE? When I double-click it gives me a command prompt window which then closes instantly._ˆ+Question A.6.8: How do I use PSCP to copy a file whose name has spaces in?Í,Section A.7: Troubleshooting[,Question A.7.1: Why do I see ‘Incorrect MAC received on packet’?K†,Question A.7.2: Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?c :‰,Question A.7.3: I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.-Question A.7.4: Plink on Windows 95 says it can't find WS2_32.DLL.ú-Question A.7.5: My PuTTY sessions close after an hour and tell me ‘Server failed host key check’.}-Question A.7.6: After trying to establish an SSH 2 connection, PuTTY says ‘Out of memory’ and dies.-Question A.7.7: When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.!‚-Question A.7.8: PSFTP transfers files much slower than PSCP.îƒ-Question A.7.9: When I run full-colour applications, I see areas of black space where colour ought to be.C…-Question A.7.10: When I change some terminal settings, nothing happens.>ˆ-Question A.7.11: I can't type characters that require the AltGr key.݈-Question A.7.12: My PuTTY sessions unexpectedly close after they are idle for a while.÷.Question A.7.13: PuTTY's network connections time out too quickly when network connectivity is temporarily lost.C.Question A.7.14: When I cat a binary file, I get `PuTTYPuTTYPuTTY' on my command line.w.Question A.7.15: When I cat a binary file, my window title changes to a nonsense string.€.Question A.7.16: My keyboard stops working once PuTTY displays the password prompt.ż.Question A.7.17: One or more function keys don't do what I expected in a server-side application.>ˆ.Question A.7.18: Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.”/Question A.7.19: Why do I see "Couldn't load private key from ..."? Why can PuTTYgen load my key but not PuTTY?•/Question A.7.20: When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.ł/Section A.8: Security questionsR /Question A.8.1: Is it safe for me to download PuTTY and use it on a public PC?\‚/Question A.8.2: What does PuTTY leave on a system? How can I clean up after it?8˙˙˃/Question A.8.3: How come PuTTY now supports DSA, when the website used to say how insecure it was?Ɔ/Question A.8.4: Couldn't Pageant use VirtualLock() to stop private keys being written to disk?Śˆ/Section A.9: Administrative questions0Question A.9.1: Would you like me to register you a nicer domain name?00Question A.9.2: Would you like free web hosting for the PuTTY web site?œ0Question A.9.3: Why don't you move PuTTY to SourceForge?˝0Question A.9.4: Why can't I subscribe to the putty-bugs mailing list?ę0Question A.9.5: If putty-bugs isn't a general-subscription mailing list, what is?€0Question A.9.6: How can I donate to PuTTY development?ԅ0Section A.10: Miscellaneous questions܆0Question A.10.1: Is PuTTY a port of OpenSSH, or based on OpenSSH?î‡0Question A.10.2: Where can I buy silly putty?Q‰0Question A.10.3: What does ‘PuTTY’ mean?1Question A.10.4: How do I pronounce ‘PuTTY’?y1Appendix B: Feedback and bug reportingá1Section B.1: General guidelinesü1Section B.1.1: Sending large attachments‰1Section B.2: Reporting bugsš 2Section B.3: Requesting extra featuresć‡2Section B.4: Requesting features that have already been requested§3Section B.5: Support requests3Section B.6: Web server administrationa 3Section B.7: Asking permission for thingsxƒ3Section B.8: Mirroring the PuTTY web siteđ…3Section B.9: Praise and compliments"ˆ3Section B.10: E-mail address„ˆ3Appendix C: PuTTY LicenceÄ žƀ   2†„$% ):‰,˃/ /&;)z4˙˙ ‹ ˙˙˙˙|CONTEXT|CTXOMAP?|FONTJ|KWBTREE|KWDATA7!|KWMAP„!|SYSTEM•!|TOPICň"|TTLBTREEŚ