3 This FAQ is published on the PuTTY web site, and also provided as an
4 appendix in the manual.
6 \H{faq-support} Features supported in PuTTY
8 In general, if you want to know if PuTTY supports a particular
9 feature, you should look for it on the
10 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}{PuTTY web site}.
14 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{changes
15 page}, and see if you can find the feature on there. If a feature is
16 listed there, it's been implemented. If it's listed as a change made
17 \e{since} the latest version, it should be available in the
18 development snapshots, in which case testing will be very welcome.
21 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist.html}{Wishlist
22 page}, and see if you can find the feature there. If it's on there,
23 it probably \e{hasn't} been implemented.
25 \S{faq-ssh2} Does PuTTY support SSH v2?
27 Yes. SSH v2 support has been available in PuTTY since version 0.50.
28 However, currently the \e{default} SSH protocol is v1; to select SSH
29 v2 if your server supports both, go to the SSH panel and change the
30 \e{Preferred SSH protocol version} option.
32 Public key authentication (both RSA and DSA) in SSH v2 has been
33 added since version 0.51.
35 \S{faq-ssh2-keyfmt} Does PuTTY support reading OpenSSH or
36 \cw{ssh.com} SSHv2 private key files?
38 Not at present. OpenSSH and \cw{ssh.com} have totally different
39 formats for private key files, and neither one is particularly
40 pleasant, so PuTTY has its own. We do plan to write a converter at
43 \S{faq-ssh1} Does PuTTY support SSH v1?
45 Yes. SSH 1 support has always been available in PuTTY.
47 \S{faq-localecho} Does PuTTY support local echo?
51 In version 0.51 and before, local echo cannot be separated from
52 local line editing (where you type a line of text locally, and it is
53 not sent to the server until you press Return, so you have the
54 chance to edit it and correct mistakes \e{before} the server sees
55 it). The two features can be enabled and disabled from the Terminal
56 panel, using the checkbox marked \q{Use local terminal line
57 discipline}. Note that due to a bug in those versions of PuTTY,
58 changing this feature in mid-session will have no effect; you have
59 to enable it \e{before} you open the connection.
61 In later versions, local echo and local line editing are separate
62 options, and by default PuTTY will try to determine automatically
63 whether to enable them or not, based on which protocol you have
64 selected and also based on hints from the server. If you have a
65 problem with PuTTY's default choice, you can force each option to be
66 enabled or disabled as you choose. The controls are in the Terminal
67 panel, in the section marked \q{Line discipline options}.
69 \S{faq-disksettings} Does PuTTY support storing its settings in a
72 Not at present, although \k{config-file} in the documentation gives
73 a method of achieving the same effect.
75 \S{faq-fullscreen} Does PuTTY support full-screen mode, like a DOS
78 Not in the 0.51 release, but it has been added since then.
80 \S{faq-password} Does PuTTY have the ability to remember my password
81 so I don't have to type it every time?
85 Remembering your password is a bad plan for obvious security
86 reasons: anyone who gains access to your machine while you're away
87 from your desk can find out the remembered password, and use it,
88 abuse it or change it.
90 In addition, it's not even \e{possible} for PuTTY to automatically
91 send your password in a Telnet session, because Telnet doesn't give
92 the client software any indication of which part of the login
93 process is the password prompt. PuTTY would have to guess, by
94 looking for words like \q{password} in the session data; and if your
95 login program is written in something other than English, this won't
98 In SSH, remembering your password would be possible in theory, but
99 there doesn't seem to be much point since SSH supports public key
100 authentication, which is more flexible and more secure. See
101 \k{pubkey} in the documentation for a full discussion of public key
104 \S{faq-server} Will you write an SSH server for the PuTTY suite, to
107 No. The only reason we might want to would be if we could easily
108 re-use existing code and significantly cut down the effort. We don't
109 believe this is the case; there just isn't enough common ground
110 between an SSH client and server to make it worthwhile.
112 If someone else wants to use bits of PuTTY in the process of writing
113 a Windows SSH server, they'd be perfectly welcome to of course, but
114 I really can't see it being a lot less effort for us to do that than
115 it would be for us to write a server from the ground up. We don't
116 have time, and we don't have motivation. The code is available if
117 anyone else wants to try it.
119 \H{faq-ports} Ports to other operating systems
121 The eventual goal is for PuTTY to be a multi-platform program, able
122 to run on at least Windows, MacOS and Unix. Whether this will
123 actually ever happen I have no idea, but it is the plan. A Mac port
124 has been started, but is only half-finished and currently not moving
127 Porting will become easier once PuTTY has a generalised porting
128 layer, drawing a clear line between platform-dependent and
129 platform-independent code. The general intention is for this porting
130 layer to evolve naturally as part of the process of doing the first
131 port. One particularly nasty part of this will be separating the
132 many configuration options into platform-dependent and
133 platform-independent ones; for example, the options controlling when
134 the Windows System menu appears will be pretty much meaningless
135 under X11 or perhaps other windowing systems, whereas Telnet Passive
136 Mode is universal and shouldn't need to be specified once for each
139 \S{faq-wince} Will there be a port to Windows CE?
141 Probably not in the particularly near future. Despite sharing large
142 parts of the Windows API, in practice WinCE doesn't appear to be
143 significantly easier to port to than a totally different operating
146 However, PuTTY on portable devices would clearly be a useful thing,
147 so in the long term I hope there will be a WinCE port.
149 \S{faq-mac} Will there be a port to the Mac?
151 A Mac port was started once and is half-finished, but development
152 has been static for some time and the main PuTTY code has moved on,
153 so it's not clear how quickly development would resume even if
154 developer effort were available.
156 \S{faq-unix} Will there be a port to Unix?
158 I hope so, if only so that I can have an \cw{xterm}-like program
159 that supports exactly the same terminal emulation as PuTTY. If and
160 when we do do a Unix port, it will have a local-terminal back end so
161 it can be used like an \cw{xterm}, rather than only being usable as
164 \S{faq-epoc} Will there be a port to EPOC?
166 I hope so, but given that ports aren't really progressing very fast
167 even on systems the developers \e{do} already know how to program
168 for, it might be a long time before any of us get round to learning
169 a new system and doing the port for that.
171 \H{faq-embedding} Embedding PuTTY in other programs
173 \S{faq-dll} Is the SSH or Telnet code available as a DLL?
175 No, it isn't. It would take a reasonable amount of rewriting for
176 this to be possible, and since the PuTTY project itself doesn't
177 believe in DLLs (they make installation more error-prone) none of us
178 has taken the time to do it.
180 Most of the code cleanup work would be a good thing to happen in
181 general, so if anyone feels like helping, we wouldn't say no.
183 \S{faq-vb} Is the SSH or Telnet code available as a Visual Basic
186 No, it isn't. None of the PuTTY team uses Visual Basic, and none of
187 us has any particular need to make SSH connections from a Visual
188 Basic application. In addition, all the preliminary work to turn it
189 into a DLL would be necessary first; and furthermore, we don't even
190 know how to write VB components.
192 If someone offers to do some of this work for us, we might consider
193 it, but unless that happens I can't see VB integration being
194 anywhere other than the very bottom of our priority list.
196 \S{faq-ipc} How can I use PuTTY to make an SSH connection from
197 within another program?
199 Probably your best bet is to use Plink, the command-line connection
200 tool. If you can start Plink as a second Windows process, and
201 arrange for your primary process to be able to send data to the
202 Plink process, and receive data from it, through pipes, then you
203 should be able to make SSH connections from your program.
205 This is what CVS for Windows does, for example.
207 \H{faq-details} Details of PuTTY's operation
209 \S{faq-term} What terminal type does PuTTY use?
211 For most purposes, PuTTY can be considered to be an \cw{xterm}
212 terminal, although full support for some of \cw{xterm}'s features,
213 such as passing mouse actions to the server-side program, is not
214 present in the 0.51 release (but has been added since).
216 PuTTY also supports some terminal control sequences not supported by
217 the real \cw{xterm}: notably the Linux console sequences that
218 reconfigure the colour palette, and the title bar control sequences
219 used by \cw{DECterm} (which are different from the \cw{xterm} ones;
220 PuTTY supports both).
222 By default, PuTTY announces its terminal type to the server as
223 \c{xterm}. If you have a problem with this, you can reconfigure it
224 to say something else; \c{vt220} might help if you have trouble.
226 \S{faq-settings} Where does PuTTY store its data?
228 PuTTY stores most of its data (saved sessions, SSH host keys) in the
229 Registry. The precise location is
231 \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY
233 and within that area, saved sessions are stored under \c{Sessions}
234 while host keys are stored under \c{SshHostKeys}.
236 PuTTY also requires a random number seed file, to improve the
237 unpredictability of randomly chosen data needed as part of the SSH
238 cryptography. This is stored by default in your Windows home
239 directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in the actual Windows
240 directory (such as \c{C:\\WINDOWS}) if the home directory doesn't
241 exist, for example if you're using Win95. If you want to change the
242 location of the random number seed file, you can put your chosen
243 pathname in the Registry, at
245 \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile
247 \H{faq-howto} HOWTO questions
249 \S{faq-startmax} How can I make PuTTY start up maximised?
251 Create a Windows shortcut to start PuTTY from, and set it as \q{Run
254 \S{faq-startsess} How can I create a Windows shortcut to start a
255 particular saved session directly?
257 To run a PuTTY session saved under the name \q{\cw{mysession}},
258 create a Windows shortcut that invokes PuTTY with a command line
261 \c \path\name\to\putty.exe @mysession
263 \S{faq-startssh} How can I start an SSH session straight from the
266 Use the command line \c{putty -ssh host.name}. Alternatively, create
267 a saved session that specifies the SSH protocol, and start the saved
268 session as shown in \k{faq-startsess}.
270 \S{faq-cutpaste} How do I copy and paste between PuTTY and other
271 Windows applications?
273 Copy and paste works similarly to the X Window System. You use the
274 left mouse button to select text in the PuTTY window. The act of
275 selection \e{automatically} copies the text to the clipboard: there
276 is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact,
277 pressing Ctrl-C will send a Ctrl-C character to the other end of
278 your connection (just like it does the rest of the time), which may
279 have unpleasant effects. The \e{only} thing you need to do, to copy
280 text to the clipboard, is to select it.
282 To paste the clipboard contents into a PuTTY window, by default you
283 click the right mouse button. If you have a three-button mouse and
284 are used to X applications, you can configure pasting to be done by
285 the middle button instead, but this is not the default because most
286 Windows users don't have a middle button at all.
288 You can also paste by pressing Shift-Ins.
290 \S{faq-tunnels} How do I use X forwarding and port forwarding? I
291 can't find the Tunnels panel.
293 If you're looking in the 0.51 release or earlier, the Tunnels panel
294 isn't there. It was added in the development snapshots after 0.51,
295 and releases 0.52 and onwards will contain it.
297 \S{faq-options} How do I use all PuTTY's features (port forwarding,
298 SSH v2 etc) in Plink?
300 Plink is currently rather short of command line options to enable
301 this sort of thing. You can use these features if you create a PuTTY
302 saved session, and then use the name of the saved session on Plink's
303 command line in place of a hostname.
305 \S{faq-pscp} How do I use PSCP.EXE? When I double-click it gives me
306 a command prompt window which then closes instantly.
308 PSCP is a command-line application, not a GUI application. If you
309 run it without arguments, it will simply print a help message and
312 To use PSCP properly, run it from a Command Prompt window. See
313 \k{pscp} in the documentation for more details.
315 \S{faq-pscp-spaces} How do I use PSCP to copy a file whose name has
318 If PSCP is using the traditional SCP protocol, this is confusing. If
319 you're specifying a file at the local end, you just use one set of
320 quotes as you would normally do:
322 \c pscp "local filename with spaces" user@host:
323 \c pscp user@host:myfile "local filename with spaces"
325 But if the filename you're specifying is on the \e{remote} side, you
326 have to use backslashes and two sets of quotes:
328 \c pscp user@host:"\"remote filename with spaces\"" local_filename
329 \c pscp local_filename user@host:"\"remote filename with spaces\""
331 Worse still, in a remote-to-local copy you have to specify the local
332 file name explicitly, otherwise PSCP will complain that they don't
333 match (unless you specified the \c{-unsafe} option). The following
334 command will give an error message:
336 \c c:\>pscp user@host:"\"oo er\"" .
337 \c warning: remote host tried to write to a file called 'oo er'
338 \c when we requested a file called '"oo er"'.
340 Instead, you need to specify the local file name in full:
342 \c c:\>pscp user@host:"\"oo er\"" "oo er"
344 If PSCP is using the newer SFTP protocol, none of this is a problem,
345 and all filenames with spaces in are specified using a single pair
346 of quotes in the obvious way:
348 \c pscp "local file" user@host:
349 \c pscp user@host:"remote file" .
351 \H{faq-trouble} Troubleshooting
353 \S{faq-mac} Why do I see \q{Incorrect MAC received on packet}?
355 This is due to a bug in old SSH 2 servers distributed by
356 \cw{ssh.com}. Version 2.3.0 and below of their SSH 2 server
357 constructs Message Authentication Codes in the wrong way, and
358 expects the client to construct them in the same wrong way. PuTTY
359 constructs the MACs correctly by default, and hence these old
360 servers will fail to work with it.
362 If you are using PuTTY version 0.51 or below, go to the SSH panel
363 and check the box labelled \q{Imitate SSH 2 MAC bug}. This will
364 cause PuTTY to construct its MACs in the same incorrect manner as
365 the buggy servers, so it will be able to work with them.
367 Since version 0.51, PuTTY has been enhanced to detect buggy servers
368 automatically (when they announce their version) and enable the
369 workaround without the user needing to ask. Therefore you \e{should}
370 never have to use this option again after 0.52, but it is still
371 provided just in case another buggy server shows up.
373 In this context MAC stands for Message Authentication Code. It's a
374 cryptographic term, and it has nothing at all to do with Ethernet
375 MAC (Media Access Control) addresses.
377 \S{faq-colours} I clicked on a colour in the Colours panel, and the
378 colour didn't change in my terminal.
380 That isn't how you're supposed to use the Colours panel.
382 During the course of a session, PuTTY potentially uses \e{all} the
383 colours listed in the Colours panel. It's not a question of using
384 only one of them and you choosing which one; PuTTY will use them
385 \e{all}. The purpose of the Colours panel is to let you adjust the
386 appearance of all the colours. So to change the colour of the
387 cursor, for example, you would select \q{Cursor Colour}, press the
388 \q{Modify} button, and select a new colour from the dialog box that
389 appeared. Similarly, if you want your session to appear in green,
390 you should select \q{Default Foreground} and press \q{Modify}.
391 Clicking on \q{ANSI Green} won't turn your session green; it will
392 only allow you to adjust the \e{shade} of green used when PuTTY is
393 instructed by the server to display green text.
395 \S{faq-winsock2} Plink on Windows 95 says it can't find \cw{WS2_32.DLL}.
397 Plink requires the extended Windows network library, WinSock version
398 2. This is installed as standard on Windows 98 and above, and on
399 Windows NT, and even on later versions of Windows 95; but early
400 Win95 installations don't have it.
402 In order to use Plink on these systems, you will need to download
404 \W{http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/}{WinSock 2 upgrade}:
406 \c http://www.microsoft.com/windows95/downloads/contents/wuadmintools/
407 \c s_wunetworkingtools/w95sockets2/
409 \S{faq-rekey} My PuTTY sessions close after an hour and tell me
410 \q{Server failed host key check}.
412 This is a bug in all versions of PuTTY up to and including 0.51. SSH
413 v2 servers from \cw{ssh.com} will require the key exchange to be
414 repeated one hour after the start of the connection, and PuTTY will
417 The bug has been fixed since version 0.51, so upgrading to a later
418 version or snapshot should solve the problem.
420 \S{faq-outofmem} After trying to establish an SSH 2 connection,
421 PuTTY says \q{Out of memory} and dies.
423 If this happens just while the connection is starting up, this often
424 indicates that for some reason the client and server have failed to
425 establish a session encryption key. Somehow, they have performed
426 calculations that should have given each of them the same key, but
427 have ended up with different keys; so data encrypted by one and
428 decrypted by the other looks like random garbage.
430 This causes an \q{out of memory} error because the first encrypted
431 data PuTTY expects to see is the length of an SSH message. Normally
432 this will be something well under 100 bytes. If the decryption has
433 failed, PuTTY will see a completely random length in the region of
434 two \e{gigabytes}, and will try to allocate enough memory to store
435 this non-existent message. This will immediately lead to it thinking
436 it doesn't have enough memory, and panicking.
438 If this happens to you, it is quite likely to still be a PuTTY bug
439 and you should report it (although it might be a bug in your SSH
440 server instead); but it doesn't necessarily mean you've actually run
443 \S{faq-altgr} I can't type characters that require the AltGr key.
445 In PuTTY version 0.51, the AltGr key was broken. The bug has been
448 \S{faq-idleout} My PuTTY sessions unexpectedly close after they
449 are idle for a while.
451 Some types of firewall, and almost any router doing Network Address
452 Translation (NAT, also known as IP masquerading), will forget about
453 a connection through them if the connection does nothing for too
454 long. This will cause the connection to be rudely cut off when
457 You can try to combat this by telling PuTTY to send \e{keepalives}:
458 packets of data which have no effect on the actual session, but
459 which reassure the router or firewall that the network connection is
460 still active and worth remembering about.
462 Keepalives don't solve everything, unfortunately; although they
463 cause greater robustness against this sort of router, they can also
464 cause a \e{loss} of robustness against network dropouts. See
465 \k{config-keepalive} in the documentation for more discussion of
468 \S{faq-timeout} PuTTY's network connections time out too quickly
469 when network connectivity is temporarily lost.
471 This is a Windows problem, not a PuTTY problem. The timeout value
472 can't be set on per application or per session basis. To increase
473 the TCP timeout globally, you need to tinker with the Registry.
475 On Windows 95, 98 or ME, the registry key you need to change is
477 \c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
478 \c MSTCP\MaxDataRetries
480 (it must be of type DWORD in Win95, or String in Win98/ME).
482 On Windows NT or 2000, the registry key is
484 \c HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
485 \c Parameters\TcpMaxDataRetransmissions
487 and it must be of type DWORD.
489 Set the key's value to something like 10. This will cause Windows to
490 try harder to keep connections alive instead of abandoning them.
492 \S{faq-puttyputty} When I \cw{cat} a binary file, I get
493 `PuTTYPuTTYPuTTY' on my command line.
495 Don't \cw{cat} binary files, then.
497 This is designed behaviour; when PuTTY receives the character
498 Control-E from the remote server, it interprets it as a request to
499 identify itself, and so it sends back the string \q{\cw{PuTTY}} as
500 if that string had been entered at the keyboard. Control-E should
501 only be sent by programs that are prepared to deal with the
502 response. Writing a binary file to your terminal is likely to output
503 many Control-E characters, and cause this behaviour. Don't do it.
506 \S{faq-puttyputty} When I \cw{cat} a binary file, my window title
507 changes to a nonsense string.
509 Don't \cw{cat} binary files, then.
511 It is designed behaviour that PuTTY should have the ability to
512 adjust the window title on instructions from the server. Normally
513 the control sequence that does this should only be sent
514 deliberately, by programs that know what they are doing and intend
515 to put meaningful text in the window title. Writing a binary file to
516 your terminal runs the risk of sending the same control sequence by
517 accident, and cause unexpected changes in the window title. Don't do
520 \S{faq-password} My keyboard stops working once PuTTY displays the
523 No, it doesn't. PuTTY just doesn't display the password you type, so
524 that someone looking at your screen can't see what it is.
526 Unlike the Windows login prompts, PuTTY doesn't display the password
527 as a row of asterisks either. This is so that someone looking at
528 your screen can't even tell how \e{long} your password is, which
529 might be valuable information.
531 \H{faq-secure} Security questions
533 \S{faq-publicpc} Is it safe for me to download PuTTY and use it on a
536 It depends on whether you trust that PC. If you don't trust the
537 public PC, don't use PuTTY on it, and don't use any other software
538 you plan to type passwords into either. It might be watching your
539 keystrokes, or it might tamper with the PuTTY binary you download.
540 There is \e{no} program safe enough that you can run it on an
541 actively malicious PC and get away with typing passwords into it.
543 If you do trust the PC, then it's probably OK to use PuTTY on it
544 (but if you don't trust the network, then the PuTTY download might
545 be tampered with, so it would be better to carry PuTTY with you on a
548 \S{faq-cleanup} What does PuTTY leave on a system? How can I clean
551 PuTTY will leave some Registry entries, and a random seed file, on
552 the PC (see \k{faq-settings}). If you are using PuTTY on a public
553 PC, or somebody else's PC, you might want to clean these up when you
554 leave. You can do that automatically, by running the command
557 \S{faq-dsa} How come PuTTY now supports DSA, when the website used
558 to say how insecure it was?
560 DSA has a major weakness \e{if badly implemented}: it relies on a
561 random number generator to far too great an extent. If the random
562 number generator produces a number an attacker can predict, the DSA
563 private key is exposed - meaning that the attacker can log in as you
564 on all systems that accept that key.
566 The PuTTY policy changed because the developers were informed of
567 ways to implement DSA which do not suffer nearly as badly from this
568 weakness, and indeed which don't need to rely on random numbers at
569 all. For this reason we now believe PuTTY's DSA implementation is
570 probably OK. However, if you have the choice, we still recommend you
573 \H{faq-admin} Administrative questions
575 \S{faq-domain} Would you like me to register you a nicer domain name?
577 No, thank you. Even if you can find one (most of them seem to have
578 been registered already, by people who didn't ask whether we
579 actually wanted it before they applied), we're happy with the PuTTY
580 web site being exactly where it is. It's not hard to find (just type
581 \q{putty} into \W{http://www.google.com/}{google.com} and we're the
582 first link returned), and we don't believe the administrative hassle
583 of moving the site would be worth the benefit.
585 In addition, if we \e{did} want a custom domain name, we would want
586 to run it ourselves, so we knew for certain that it would continue
587 to point where we wanted it, and wouldn't suddenly change or do
588 strange things. Having it registered for us by a third party who we
589 don't even know is not the best way to achieve this.
591 \S{faq-webhosting} Would you like free web hosting for the PuTTY web
594 We already have some, thanks.
596 \S{faq-sourceforge} Why don't you move PuTTY to SourceForge?
598 Partly, because we don't want to move the web site location (see
601 Also, security reasons. PuTTY is a security product, and as such it
602 is particularly important to guard the code and the web site against
603 unauthorised modifications which might introduce subtle security
604 flaws. Therefore, we prefer that the CVS repository, web site and
605 FTP site remain where they are, under the direct control of system
606 administrators we know and trust personally, rather than being run
607 by a large organisation full of people we've never met and which is
608 known to have had breakins in the past.
610 No offence to SourceForge; I think they do a wonderful job. But
611 they're not ideal for everyone, and in particular they're not ideal
614 \S{faq-mailinglist1} Why can't I subscribe to the putty-bugs mailing
617 Because you're not a member of the PuTTY core development team. The
618 putty-bugs mailing list is not a general newsgroup-like discussion
619 forum; it's a contact address for the core developers, and an
620 \e{internal} mailing list for us to discuss things among ourselves.
621 If we opened it up for everybody to subscribe to, it would turn into
622 something more like a newsgroup and we would be completely
623 overwhelmed by the volume of traffic. It's hard enough to keep up
624 with the list as it is.
626 \S{faq-mailinglist2} If putty-bugs isn't a general-subscription
627 mailing list, what is?
629 There isn't one, that we know of.
631 If someone else wants to set up a mailing list for PuTTY users to
632 help each other with common problems, that would be fine with us;
633 but the PuTTY team would almost certainly not have the time to read
634 it, so any questions the list couldn't answer would have to be
635 forwarded on to us by the questioner. In any case, it's probably
636 better to use the established newsgroup \cw{comp.security.ssh} for
639 \S{faq-donations} How can I donate to PuTTY development?
641 Please, \e{please} don't feel you have to. PuTTY is completely free
642 software, and not shareware. We think it's very important that
643 \e{everybody} who wants to use PuTTY should be able to, whether they
644 have any money or not; so the last thing we would want is for a
645 PuTTY user to feel guilty because they haven't paid us any money. If
646 you want to keep your money, please do keep it. We wouldn't dream of
649 Having said all that, if you still really \e{want} to give us money,
650 we won't argue :-) The easiest way for us to accept donations is if
651 you go to \W{http://www.e-gold.com}\cw{www.e-gold.com}, and deposit
652 your donation in account number 174769. Then send us e-mail to let
653 us know you've done so (otherwise we might not notice for months!).
655 Small donations (tens of dollars or tens of euros) will probably be
656 spent on beer or curry, which helps motivate our volunteer team to
657 continue doing this for the world. Larger donations will be spent on
658 something that actually helps development, if we can find anything
659 (perhaps new hardware, or a copy of Windows 2000), but if we can't
660 find anything then we'll just distribute the money among the
661 developers. If you want to be sure your donation is going towards
662 something worthwhile, ask us first. If you don't like these terms,
663 feel perfectly free not to donate. We don't mind.
665 \S{faq-pronounce} How do I pronounce PuTTY?
667 Exactly like the normal word \q{putty}. Just like the stuff you put
668 on window frames. (One of the reasons it's called PuTTY is because
669 it makes Windows usable. :-)