ee46ef84 |
1 | \A{faq} PuTTY FAQ |
2 | |
3 | This FAQ is published on the PuTTY web site, and also provided as an |
4 | appendix in the manual. |
5 | |
6 | \H{faq-support} Features supported in PuTTY |
7 | |
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}. |
11 | In particular: |
12 | |
13 | \b try the |
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. |
19 | |
20 | \b try the |
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. |
24 | |
25 | \S{faq-ssh2} Does PuTTY support SSH v2? |
26 | |
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. |
31 | |
32 | Public key authentication (both RSA and DSA) in SSH v2 has been |
33 | added since version 0.51. |
34 | |
35 | \S{faq-ssh2-keyfmt} Does PuTTY support reading OpenSSH or |
36 | \cw{ssh.com} SSHv2 private key files? |
37 | |
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 |
41 | some stage. |
42 | |
43 | \S{faq-ssh1} Does PuTTY support SSH v1? |
44 | |
45 | Yes. SSH 1 support has always been available in PuTTY. |
46 | |
47 | \S{faq-localecho} Does PuTTY support local echo? |
48 | |
49 | Yes. |
50 | |
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. |
60 | |
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}. |
68 | |
69 | \S{faq-disksettings} Does PuTTY support storing its settings in a |
70 | disk file? |
71 | |
72 | Not at present, although \k{config-file} in the documentation gives |
73 | a method of achieving the same effect. |
74 | |
75 | \S{faq-fullscreen} Does PuTTY support full-screen mode, like a DOS |
76 | box? |
77 | |
78 | Not in the 0.51 release, but it has been added since then. |
79 | |
80 | \S{faq-password} Does PuTTY have the ability to remember my password |
81 | so I don't have to type it every time? |
82 | |
83 | No, it doesn't. |
84 | |
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. |
89 | |
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 |
96 | work. |
97 | |
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 |
102 | authentication. |
103 | |
cad566a9 |
104 | \S{faq-hostkeys} Is there an option to turn off the annoying host |
105 | key prompts? |
106 | |
107 | No, there isn't. And there won't be. Even if you write it yourself |
108 | and send us the patch, we won't accept it. |
109 | |
110 | Those annoying host key prompts are the \e{whole point} of SSH. |
111 | Without them, all the cryptographic technology SSH uses to secure |
112 | your session is doing nothing more than making an attacker's job |
113 | slightly harder; instead of sitting between you and the server with |
114 | a packet sniffer, the attacker must actually subvert a router and |
115 | start modifying the packets going back and forth. But that's not all |
116 | that much harder than just sniffing; and without host key checking, |
117 | it will go completely undetected by client or server. |
118 | |
119 | Host key checking is your guarantee that the encryption you put on |
120 | your data at the client end is the \e{same} encryption taken off the |
121 | data at the server end; it's your guarantee that it hasn't been |
122 | removed and replaced somewhere on the way. Host key checking makes |
123 | the attacker's job \e{astronomically} hard, compared to packet |
124 | sniffing, and even compared to subverting a router. Instead of |
125 | applying a little intelligence and keeping an eye on Bugtraq, the |
126 | attacker must now perform a brute-force attack against at least one |
127 | military-strength cipher. That insignificant host key prompt really |
128 | does make \e{that} much difference. |
129 | |
130 | If you're having a specific problem with host key checking - perhaps |
131 | you want an automated batch job to make use of PSCP or Plink, and |
132 | the interactive host key prompt is hanging the batch process - then |
133 | the right way to fix it is to add the correct host key to the |
134 | Registry in advance. That way, you retain the \e{important} feature |
135 | of host key checking: the right key will be accepted and the wrong |
136 | ones will not. Adding an option to turn host key checking off |
137 | completely is the wrong solution and we will not do it. |
138 | |
ae915483 |
139 | \S{faq-server} Will you write an SSH server for the PuTTY suite, to |
140 | go with the client? |
141 | |
142 | No. The only reason we might want to would be if we could easily |
143 | re-use existing code and significantly cut down the effort. We don't |
144 | believe this is the case; there just isn't enough common ground |
145 | between an SSH client and server to make it worthwhile. |
146 | |
147 | If someone else wants to use bits of PuTTY in the process of writing |
148 | a Windows SSH server, they'd be perfectly welcome to of course, but |
149 | I really can't see it being a lot less effort for us to do that than |
150 | it would be for us to write a server from the ground up. We don't |
151 | have time, and we don't have motivation. The code is available if |
152 | anyone else wants to try it. |
153 | |
ee46ef84 |
154 | \H{faq-ports} Ports to other operating systems |
155 | |
156 | The eventual goal is for PuTTY to be a multi-platform program, able |
157 | to run on at least Windows, MacOS and Unix. Whether this will |
158 | actually ever happen I have no idea, but it is the plan. A Mac port |
159 | has been started, but is only half-finished and currently not moving |
160 | very fast. |
161 | |
162 | Porting will become easier once PuTTY has a generalised porting |
163 | layer, drawing a clear line between platform-dependent and |
164 | platform-independent code. The general intention is for this porting |
165 | layer to evolve naturally as part of the process of doing the first |
166 | port. One particularly nasty part of this will be separating the |
167 | many configuration options into platform-dependent and |
168 | platform-independent ones; for example, the options controlling when |
169 | the Windows System menu appears will be pretty much meaningless |
170 | under X11 or perhaps other windowing systems, whereas Telnet Passive |
171 | Mode is universal and shouldn't need to be specified once for each |
172 | platform. |
173 | |
174 | \S{faq-wince} Will there be a port to Windows CE? |
175 | |
176 | Probably not in the particularly near future. Despite sharing large |
177 | parts of the Windows API, in practice WinCE doesn't appear to be |
178 | significantly easier to port to than a totally different operating |
179 | system. |
180 | |
181 | However, PuTTY on portable devices would clearly be a useful thing, |
182 | so in the long term I hope there will be a WinCE port. |
183 | |
184 | \S{faq-mac} Will there be a port to the Mac? |
185 | |
186 | A Mac port was started once and is half-finished, but development |
187 | has been static for some time and the main PuTTY code has moved on, |
188 | so it's not clear how quickly development would resume even if |
189 | developer effort were available. |
190 | |
191 | \S{faq-unix} Will there be a port to Unix? |
192 | |
193 | I hope so, if only so that I can have an \cw{xterm}-like program |
194 | that supports exactly the same terminal emulation as PuTTY. If and |
195 | when we do do a Unix port, it will have a local-terminal back end so |
196 | it can be used like an \cw{xterm}, rather than only being usable as |
197 | a network utility. |
198 | |
199 | \S{faq-epoc} Will there be a port to EPOC? |
200 | |
201 | I hope so, but given that ports aren't really progressing very fast |
202 | even on systems the developers \e{do} already know how to program |
203 | for, it might be a long time before any of us get round to learning |
204 | a new system and doing the port for that. |
205 | |
206 | \H{faq-embedding} Embedding PuTTY in other programs |
207 | |
208 | \S{faq-dll} Is the SSH or Telnet code available as a DLL? |
209 | |
210 | No, it isn't. It would take a reasonable amount of rewriting for |
211 | this to be possible, and since the PuTTY project itself doesn't |
212 | believe in DLLs (they make installation more error-prone) none of us |
213 | has taken the time to do it. |
214 | |
215 | Most of the code cleanup work would be a good thing to happen in |
216 | general, so if anyone feels like helping, we wouldn't say no. |
217 | |
218 | \S{faq-vb} Is the SSH or Telnet code available as a Visual Basic |
219 | component? |
220 | |
221 | No, it isn't. None of the PuTTY team uses Visual Basic, and none of |
222 | us has any particular need to make SSH connections from a Visual |
223 | Basic application. In addition, all the preliminary work to turn it |
224 | into a DLL would be necessary first; and furthermore, we don't even |
225 | know how to write VB components. |
226 | |
227 | If someone offers to do some of this work for us, we might consider |
228 | it, but unless that happens I can't see VB integration being |
229 | anywhere other than the very bottom of our priority list. |
230 | |
231 | \S{faq-ipc} How can I use PuTTY to make an SSH connection from |
232 | within another program? |
233 | |
234 | Probably your best bet is to use Plink, the command-line connection |
235 | tool. If you can start Plink as a second Windows process, and |
236 | arrange for your primary process to be able to send data to the |
237 | Plink process, and receive data from it, through pipes, then you |
238 | should be able to make SSH connections from your program. |
239 | |
240 | This is what CVS for Windows does, for example. |
241 | |
242 | \H{faq-details} Details of PuTTY's operation |
243 | |
244 | \S{faq-term} What terminal type does PuTTY use? |
245 | |
246 | For most purposes, PuTTY can be considered to be an \cw{xterm} |
247 | terminal, although full support for some of \cw{xterm}'s features, |
248 | such as passing mouse actions to the server-side program, is not |
249 | present in the 0.51 release (but has been added since). |
250 | |
251 | PuTTY also supports some terminal control sequences not supported by |
252 | the real \cw{xterm}: notably the Linux console sequences that |
253 | reconfigure the colour palette, and the title bar control sequences |
254 | used by \cw{DECterm} (which are different from the \cw{xterm} ones; |
255 | PuTTY supports both). |
256 | |
257 | By default, PuTTY announces its terminal type to the server as |
258 | \c{xterm}. If you have a problem with this, you can reconfigure it |
259 | to say something else; \c{vt220} might help if you have trouble. |
260 | |
261 | \S{faq-settings} Where does PuTTY store its data? |
262 | |
263 | PuTTY stores most of its data (saved sessions, SSH host keys) in the |
264 | Registry. The precise location is |
265 | |
266 | \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY |
267 | |
268 | and within that area, saved sessions are stored under \c{Sessions} |
269 | while host keys are stored under \c{SshHostKeys}. |
270 | |
271 | PuTTY also requires a random number seed file, to improve the |
272 | unpredictability of randomly chosen data needed as part of the SSH |
273 | cryptography. This is stored by default in your Windows home |
274 | directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in the actual Windows |
275 | directory (such as \c{C:\\WINDOWS}) if the home directory doesn't |
276 | exist, for example if you're using Win95. If you want to change the |
277 | location of the random number seed file, you can put your chosen |
278 | pathname in the Registry, at |
279 | |
280 | \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile |
281 | |
282 | \H{faq-howto} HOWTO questions |
283 | |
284 | \S{faq-startmax} How can I make PuTTY start up maximised? |
285 | |
286 | Create a Windows shortcut to start PuTTY from, and set it as \q{Run |
287 | Maximized}. |
288 | |
289 | \S{faq-startsess} How can I create a Windows shortcut to start a |
290 | particular saved session directly? |
291 | |
292 | To run a PuTTY session saved under the name \q{\cw{mysession}}, |
293 | create a Windows shortcut that invokes PuTTY with a command line |
294 | like |
295 | |
296 | \c \path\name\to\putty.exe @mysession |
297 | |
298 | \S{faq-startssh} How can I start an SSH session straight from the |
299 | command line? |
300 | |
301 | Use the command line \c{putty -ssh host.name}. Alternatively, create |
302 | a saved session that specifies the SSH protocol, and start the saved |
303 | session as shown in \k{faq-startsess}. |
304 | |
305 | \S{faq-cutpaste} How do I copy and paste between PuTTY and other |
306 | Windows applications? |
307 | |
308 | Copy and paste works similarly to the X Window System. You use the |
309 | left mouse button to select text in the PuTTY window. The act of |
310 | selection \e{automatically} copies the text to the clipboard: there |
311 | is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact, |
312 | pressing Ctrl-C will send a Ctrl-C character to the other end of |
313 | your connection (just like it does the rest of the time), which may |
314 | have unpleasant effects. The \e{only} thing you need to do, to copy |
315 | text to the clipboard, is to select it. |
316 | |
317 | To paste the clipboard contents into a PuTTY window, by default you |
318 | click the right mouse button. If you have a three-button mouse and |
319 | are used to X applications, you can configure pasting to be done by |
320 | the middle button instead, but this is not the default because most |
321 | Windows users don't have a middle button at all. |
322 | |
323 | You can also paste by pressing Shift-Ins. |
324 | |
f2003e32 |
325 | \S{faq-tunnels} How do I use X forwarding and port forwarding? I |
326 | can't find the Tunnels panel. |
327 | |
328 | If you're looking in the 0.51 release or earlier, the Tunnels panel |
329 | isn't there. It was added in the development snapshots after 0.51, |
330 | and releases 0.52 and onwards will contain it. |
331 | |
72be5b5e |
332 | \S{faq-options} How do I use all PuTTY's features (public keys, port |
333 | forwarding, SSH v2, etc.) in PSCP, PSFTP and Plink? |
334 | |
335 | The command-line tools are currently rather short of command line |
336 | options to enable this sort of thing. However, you can use most of |
337 | PuTTY's features if you create a PuTTY saved session, and then use |
338 | the name of the saved session on the command line in place of a |
339 | hostname. This works for PSCP, PSFTP and Plink (but don't expect |
340 | port forwarding in the file transfer applications!). |
f2003e32 |
341 | |
ee46ef84 |
342 | \S{faq-pscp} How do I use PSCP.EXE? When I double-click it gives me |
343 | a command prompt window which then closes instantly. |
344 | |
345 | PSCP is a command-line application, not a GUI application. If you |
346 | run it without arguments, it will simply print a help message and |
347 | terminate. |
348 | |
349 | To use PSCP properly, run it from a Command Prompt window. See |
350 | \k{pscp} in the documentation for more details. |
351 | |
352 | \S{faq-pscp-spaces} How do I use PSCP to copy a file whose name has |
353 | spaces in? |
354 | |
355 | If PSCP is using the traditional SCP protocol, this is confusing. If |
356 | you're specifying a file at the local end, you just use one set of |
357 | quotes as you would normally do: |
358 | |
359 | \c pscp "local filename with spaces" user@host: |
360 | \c pscp user@host:myfile "local filename with spaces" |
361 | |
362 | But if the filename you're specifying is on the \e{remote} side, you |
363 | have to use backslashes and two sets of quotes: |
364 | |
365 | \c pscp user@host:"\"remote filename with spaces\"" local_filename |
366 | \c pscp local_filename user@host:"\"remote filename with spaces\"" |
367 | |
368 | Worse still, in a remote-to-local copy you have to specify the local |
369 | file name explicitly, otherwise PSCP will complain that they don't |
370 | match (unless you specified the \c{-unsafe} option). The following |
371 | command will give an error message: |
372 | |
373 | \c c:\>pscp user@host:"\"oo er\"" . |
e9cee352 |
374 | \c warning: remote host tried to write to a file called 'oo er' |
375 | \c when we requested a file called '"oo er"'. |
ee46ef84 |
376 | |
e9cee352 |
377 | Instead, you need to specify the local file name in full: |
378 | |
379 | \c c:\>pscp user@host:"\"oo er\"" "oo er" |
380 | |
ee46ef84 |
381 | If PSCP is using the newer SFTP protocol, none of this is a problem, |
382 | and all filenames with spaces in are specified using a single pair |
383 | of quotes in the obvious way: |
384 | |
385 | \c pscp "local file" user@host: |
386 | \c pscp user@host:"remote file" . |
387 | |
388 | \H{faq-trouble} Troubleshooting |
389 | |
390 | \S{faq-mac} Why do I see \q{Incorrect MAC received on packet}? |
391 | |
392 | This is due to a bug in old SSH 2 servers distributed by |
393 | \cw{ssh.com}. Version 2.3.0 and below of their SSH 2 server |
394 | constructs Message Authentication Codes in the wrong way, and |
395 | expects the client to construct them in the same wrong way. PuTTY |
396 | constructs the MACs correctly by default, and hence these old |
397 | servers will fail to work with it. |
398 | |
399 | If you are using PuTTY version 0.51 or below, go to the SSH panel |
400 | and check the box labelled \q{Imitate SSH 2 MAC bug}. This will |
401 | cause PuTTY to construct its MACs in the same incorrect manner as |
402 | the buggy servers, so it will be able to work with them. |
403 | |
404 | Since version 0.51, PuTTY has been enhanced to detect buggy servers |
405 | automatically (when they announce their version) and enable the |
406 | workaround without the user needing to ask. Therefore you \e{should} |
407 | never have to use this option again after 0.52, but it is still |
408 | provided just in case another buggy server shows up. |
409 | |
b7e2c163 |
410 | In this context MAC stands for Message Authentication Code. It's a |
411 | cryptographic term, and it has nothing at all to do with Ethernet |
412 | MAC (Media Access Control) addresses. |
413 | |
ee46ef84 |
414 | \S{faq-colours} I clicked on a colour in the Colours panel, and the |
415 | colour didn't change in my terminal. |
416 | |
417 | That isn't how you're supposed to use the Colours panel. |
418 | |
419 | During the course of a session, PuTTY potentially uses \e{all} the |
420 | colours listed in the Colours panel. It's not a question of using |
421 | only one of them and you choosing which one; PuTTY will use them |
422 | \e{all}. The purpose of the Colours panel is to let you adjust the |
423 | appearance of all the colours. So to change the colour of the |
424 | cursor, for example, you would select \q{Cursor Colour}, press the |
425 | \q{Modify} button, and select a new colour from the dialog box that |
426 | appeared. Similarly, if you want your session to appear in green, |
427 | you should select \q{Default Foreground} and press \q{Modify}. |
428 | Clicking on \q{ANSI Green} won't turn your session green; it will |
429 | only allow you to adjust the \e{shade} of green used when PuTTY is |
430 | instructed by the server to display green text. |
431 | |
432 | \S{faq-winsock2} Plink on Windows 95 says it can't find \cw{WS2_32.DLL}. |
433 | |
434 | Plink requires the extended Windows network library, WinSock version |
435 | 2. This is installed as standard on Windows 98 and above, and on |
436 | Windows NT, and even on later versions of Windows 95; but early |
437 | Win95 installations don't have it. |
438 | |
439 | In order to use Plink on these systems, you will need to download |
440 | the |
441 | \W{http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/}{WinSock 2 upgrade}: |
442 | |
443 | \c http://www.microsoft.com/windows95/downloads/contents/wuadmintools/ |
444 | \c s_wunetworkingtools/w95sockets2/ |
445 | |
446 | \S{faq-rekey} My PuTTY sessions close after an hour and tell me |
447 | \q{Server failed host key check}. |
448 | |
449 | This is a bug in all versions of PuTTY up to and including 0.51. SSH |
450 | v2 servers from \cw{ssh.com} will require the key exchange to be |
451 | repeated one hour after the start of the connection, and PuTTY will |
452 | get this wrong. |
453 | |
454 | The bug has been fixed since version 0.51, so upgrading to a later |
455 | version or snapshot should solve the problem. |
456 | |
e9cee352 |
457 | \S{faq-outofmem} After trying to establish an SSH 2 connection, |
458 | PuTTY says \q{Out of memory} and dies. |
ee46ef84 |
459 | |
460 | If this happens just while the connection is starting up, this often |
461 | indicates that for some reason the client and server have failed to |
462 | establish a session encryption key. Somehow, they have performed |
463 | calculations that should have given each of them the same key, but |
464 | have ended up with different keys; so data encrypted by one and |
465 | decrypted by the other looks like random garbage. |
466 | |
467 | This causes an \q{out of memory} error because the first encrypted |
468 | data PuTTY expects to see is the length of an SSH message. Normally |
469 | this will be something well under 100 bytes. If the decryption has |
470 | failed, PuTTY will see a completely random length in the region of |
471 | two \e{gigabytes}, and will try to allocate enough memory to store |
472 | this non-existent message. This will immediately lead to it thinking |
473 | it doesn't have enough memory, and panicking. |
474 | |
475 | If this happens to you, it is quite likely to still be a PuTTY bug |
476 | and you should report it (although it might be a bug in your SSH |
477 | server instead); but it doesn't necessarily mean you've actually run |
478 | out of memory. |
479 | |
480 | \S{faq-altgr} I can't type characters that require the AltGr key. |
481 | |
482 | In PuTTY version 0.51, the AltGr key was broken. The bug has been |
483 | fixed since then. |
484 | |
485 | \S{faq-idleout} My PuTTY sessions unexpectedly close after they |
486 | are idle for a while. |
487 | |
488 | Some types of firewall, and almost any router doing Network Address |
489 | Translation (NAT, also known as IP masquerading), will forget about |
490 | a connection through them if the connection does nothing for too |
491 | long. This will cause the connection to be rudely cut off when |
492 | contact is resumed. |
493 | |
494 | You can try to combat this by telling PuTTY to send \e{keepalives}: |
495 | packets of data which have no effect on the actual session, but |
496 | which reassure the router or firewall that the network connection is |
497 | still active and worth remembering about. |
498 | |
499 | Keepalives don't solve everything, unfortunately; although they |
500 | cause greater robustness against this sort of router, they can also |
501 | cause a \e{loss} of robustness against network dropouts. See |
502 | \k{config-keepalive} in the documentation for more discussion of |
503 | this. |
504 | |
505 | \S{faq-timeout} PuTTY's network connections time out too quickly |
506 | when network connectivity is temporarily lost. |
507 | |
508 | This is a Windows problem, not a PuTTY problem. The timeout value |
509 | can't be set on per application or per session basis. To increase |
510 | the TCP timeout globally, you need to tinker with the Registry. |
511 | |
512 | On Windows 95, 98 or ME, the registry key you need to change is |
513 | |
514 | \c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\ |
515 | \c MSTCP\MaxDataRetries |
516 | |
517 | (it must be of type DWORD in Win95, or String in Win98/ME). |
518 | |
519 | On Windows NT or 2000, the registry key is |
520 | |
521 | \c HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ |
522 | \c Parameters\TcpMaxDataRetransmissions |
523 | |
524 | and it must be of type DWORD. |
525 | |
526 | Set the key's value to something like 10. This will cause Windows to |
527 | try harder to keep connections alive instead of abandoning them. |
528 | |
529 | \S{faq-puttyputty} When I \cw{cat} a binary file, I get |
530 | `PuTTYPuTTYPuTTY' on my command line. |
531 | |
532 | Don't \cw{cat} binary files, then. |
533 | |
534 | This is designed behaviour; when PuTTY receives the character |
535 | Control-E from the remote server, it interprets it as a request to |
536 | identify itself, and so it sends back the string \q{\cw{PuTTY}} as |
537 | if that string had been entered at the keyboard. Control-E should |
538 | only be sent by programs that are prepared to deal with the |
539 | response. Writing a binary file to your terminal is likely to output |
540 | many Control-E characters, and cause this behaviour. Don't do it. |
541 | It's a bad plan. |
542 | |
543 | \S{faq-puttyputty} When I \cw{cat} a binary file, my window title |
544 | changes to a nonsense string. |
545 | |
546 | Don't \cw{cat} binary files, then. |
547 | |
548 | It is designed behaviour that PuTTY should have the ability to |
549 | adjust the window title on instructions from the server. Normally |
550 | the control sequence that does this should only be sent |
551 | deliberately, by programs that know what they are doing and intend |
552 | to put meaningful text in the window title. Writing a binary file to |
553 | your terminal runs the risk of sending the same control sequence by |
554 | accident, and cause unexpected changes in the window title. Don't do |
555 | it. |
556 | |
59c1f1f6 |
557 | \S{faq-password} My keyboard stops working once PuTTY displays the |
558 | password prompt. |
559 | |
560 | No, it doesn't. PuTTY just doesn't display the password you type, so |
561 | that someone looking at your screen can't see what it is. |
562 | |
563 | Unlike the Windows login prompts, PuTTY doesn't display the password |
564 | as a row of asterisks either. This is so that someone looking at |
565 | your screen can't even tell how \e{long} your password is, which |
566 | might be valuable information. |
567 | |
ee46ef84 |
568 | \H{faq-secure} Security questions |
569 | |
570 | \S{faq-publicpc} Is it safe for me to download PuTTY and use it on a |
571 | public PC? |
572 | |
573 | It depends on whether you trust that PC. If you don't trust the |
574 | public PC, don't use PuTTY on it, and don't use any other software |
575 | you plan to type passwords into either. It might be watching your |
576 | keystrokes, or it might tamper with the PuTTY binary you download. |
577 | There is \e{no} program safe enough that you can run it on an |
578 | actively malicious PC and get away with typing passwords into it. |
579 | |
580 | If you do trust the PC, then it's probably OK to use PuTTY on it |
581 | (but if you don't trust the network, then the PuTTY download might |
582 | be tampered with, so it would be better to carry PuTTY with you on a |
583 | floppy). |
584 | |
585 | \S{faq-cleanup} What does PuTTY leave on a system? How can I clean |
586 | up after it? |
587 | |
588 | PuTTY will leave some Registry entries, and a random seed file, on |
589 | the PC (see \k{faq-settings}). If you are using PuTTY on a public |
590 | PC, or somebody else's PC, you might want to clean these up when you |
591 | leave. You can do that automatically, by running the command |
592 | \c{putty -cleanup}. |
593 | |
594 | \S{faq-dsa} How come PuTTY now supports DSA, when the website used |
595 | to say how insecure it was? |
596 | |
597 | DSA has a major weakness \e{if badly implemented}: it relies on a |
598 | random number generator to far too great an extent. If the random |
599 | number generator produces a number an attacker can predict, the DSA |
600 | private key is exposed - meaning that the attacker can log in as you |
601 | on all systems that accept that key. |
602 | |
603 | The PuTTY policy changed because the developers were informed of |
604 | ways to implement DSA which do not suffer nearly as badly from this |
605 | weakness, and indeed which don't need to rely on random numbers at |
606 | all. For this reason we now believe PuTTY's DSA implementation is |
607 | probably OK. However, if you have the choice, we still recommend you |
608 | use RSA instead. |
609 | |
610 | \H{faq-admin} Administrative questions |
611 | |
612 | \S{faq-domain} Would you like me to register you a nicer domain name? |
613 | |
614 | No, thank you. Even if you can find one (most of them seem to have |
615 | been registered already, by people who didn't ask whether we |
616 | actually wanted it before they applied), we're happy with the PuTTY |
617 | web site being exactly where it is. It's not hard to find (just type |
618 | \q{putty} into \W{http://www.google.com/}{google.com} and we're the |
619 | first link returned), and we don't believe the administrative hassle |
620 | of moving the site would be worth the benefit. |
621 | |
622 | In addition, if we \e{did} want a custom domain name, we would want |
623 | to run it ourselves, so we knew for certain that it would continue |
624 | to point where we wanted it, and wouldn't suddenly change or do |
625 | strange things. Having it registered for us by a third party who we |
626 | don't even know is not the best way to achieve this. |
627 | |
628 | \S{faq-webhosting} Would you like free web hosting for the PuTTY web |
629 | site? |
630 | |
631 | We already have some, thanks. |
632 | |
633 | \S{faq-sourceforge} Why don't you move PuTTY to SourceForge? |
634 | |
635 | Partly, because we don't want to move the web site location (see |
636 | \k{faq-domain}). |
637 | |
638 | Also, security reasons. PuTTY is a security product, and as such it |
639 | is particularly important to guard the code and the web site against |
640 | unauthorised modifications which might introduce subtle security |
641 | flaws. Therefore, we prefer that the CVS repository, web site and |
642 | FTP site remain where they are, under the direct control of system |
643 | administrators we know and trust personally, rather than being run |
644 | by a large organisation full of people we've never met and which is |
645 | known to have had breakins in the past. |
646 | |
647 | No offence to SourceForge; I think they do a wonderful job. But |
648 | they're not ideal for everyone, and in particular they're not ideal |
649 | for us. |
650 | |
651 | \S{faq-mailinglist1} Why can't I subscribe to the putty-bugs mailing |
652 | list? |
653 | |
654 | Because you're not a member of the PuTTY core development team. The |
655 | putty-bugs mailing list is not a general newsgroup-like discussion |
656 | forum; it's a contact address for the core developers, and an |
657 | \e{internal} mailing list for us to discuss things among ourselves. |
658 | If we opened it up for everybody to subscribe to, it would turn into |
659 | something more like a newsgroup and we would be completely |
660 | overwhelmed by the volume of traffic. It's hard enough to keep up |
661 | with the list as it is. |
662 | |
663 | \S{faq-mailinglist2} If putty-bugs isn't a general-subscription |
664 | mailing list, what is? |
665 | |
666 | There isn't one, that we know of. |
667 | |
668 | If someone else wants to set up a mailing list for PuTTY users to |
669 | help each other with common problems, that would be fine with us; |
670 | but the PuTTY team would almost certainly not have the time to read |
671 | it, so any questions the list couldn't answer would have to be |
672 | forwarded on to us by the questioner. In any case, it's probably |
673 | better to use the established newsgroup \cw{comp.security.ssh} for |
674 | this purpose. |
675 | |
676 | \S{faq-donations} How can I donate to PuTTY development? |
677 | |
678 | Please, \e{please} don't feel you have to. PuTTY is completely free |
679 | software, and not shareware. We think it's very important that |
680 | \e{everybody} who wants to use PuTTY should be able to, whether they |
681 | have any money or not; so the last thing we would want is for a |
682 | PuTTY user to feel guilty because they haven't paid us any money. If |
683 | you want to keep your money, please do keep it. We wouldn't dream of |
684 | asking for any. |
685 | |
686 | Having said all that, if you still really \e{want} to give us money, |
687 | we won't argue :-) The easiest way for us to accept donations is if |
688 | you go to \W{http://www.e-gold.com}\cw{www.e-gold.com}, and deposit |
689 | your donation in account number 174769. Then send us e-mail to let |
690 | us know you've done so (otherwise we might not notice for months!). |
691 | |
692 | Small donations (tens of dollars or tens of euros) will probably be |
693 | spent on beer or curry, which helps motivate our volunteer team to |
694 | continue doing this for the world. Larger donations will be spent on |
695 | something that actually helps development, if we can find anything |
696 | (perhaps new hardware, or a copy of Windows 2000), but if we can't |
697 | find anything then we'll just distribute the money among the |
698 | developers. If you want to be sure your donation is going towards |
699 | something worthwhile, ask us first. If you don't like these terms, |
700 | feel perfectly free not to donate. We don't mind. |
701 | |
702 | \S{faq-pronounce} How do I pronounce PuTTY? |
703 | |
704 | Exactly like the normal word \q{putty}. Just like the stuff you put |
705 | on window frames. (One of the reasons it's called PuTTY is because |
706 | it makes Windows usable. :-) |