9448161f |
1 | \versionid $Id: faq.but,v 1.65 2004/03/30 11:36:51 jacob Exp $ |
8f1529bc |
2 | |
ee46ef84 |
3 | \A{faq} PuTTY FAQ |
4 | |
5 | This FAQ is published on the PuTTY web site, and also provided as an |
6 | appendix in the manual. |
7 | |
64fb6efd |
8 | \H{faq-intro} Introduction |
9 | |
9448161f |
10 | \S{faq-what}{Question} What is PuTTY? |
64fb6efd |
11 | |
12 | PuTTY is a client program for the SSH, Telnet and Rlogin network |
13 | protocols. |
14 | |
15 | These protocols are all used to run a remote session on a computer, |
16 | over a network. PuTTY implements the client end of that session: the |
17 | end at which the session is displayed, rather than the end at which |
18 | it runs. |
19 | |
20 | In really simple terms: you run PuTTY on a Windows machine, and tell |
21 | it to connect to (for example) a Unix machine. PuTTY opens a window. |
22 | Then, anything you type into that window is sent straight to the |
23 | Unix machine, and everything the Unix machine sends back is |
24 | displayed in the window. So you can work on the Unix machine as if |
25 | you were sitting at its console, while actually sitting somewhere |
26 | else. |
27 | |
ee46ef84 |
28 | \H{faq-support} Features supported in PuTTY |
29 | |
30 | In general, if you want to know if PuTTY supports a particular |
31 | feature, you should look for it on the |
32 | \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}{PuTTY web site}. |
33 | In particular: |
34 | |
35 | \b try the |
36 | \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{changes |
37 | page}, and see if you can find the feature on there. If a feature is |
38 | listed there, it's been implemented. If it's listed as a change made |
39 | \e{since} the latest version, it should be available in the |
40 | development snapshots, in which case testing will be very welcome. |
41 | |
42 | \b try the |
ebe9a956 |
43 | \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist |
ee46ef84 |
44 | page}, and see if you can find the feature there. If it's on there, |
b21091fb |
45 | and not in the \q{Recently fixed} section, it probably \e{hasn't} been |
46 | implemented. |
ee46ef84 |
47 | |
a1d2976b |
48 | \S{faq-ssh2}{Question} Does PuTTY support SSH v2? |
ee46ef84 |
49 | |
50 | Yes. SSH v2 support has been available in PuTTY since version 0.50. |
ee46ef84 |
51 | |
32c37ecd |
52 | Public key authentication (both RSA and DSA) in SSH v2 is new in |
53 | version 0.52. |
ee46ef84 |
54 | |
a1d2976b |
55 | \S{faq-ssh2-keyfmt}{Question} Does PuTTY support reading OpenSSH or |
ee46ef84 |
56 | \cw{ssh.com} SSHv2 private key files? |
57 | |
a58b605b |
58 | PuTTY doesn't support this natively, but as of 0.53 |
59 | PuTTYgen can convert both OpenSSH and \cw{ssh.com} private key |
60 | files into PuTTY's format. |
ee46ef84 |
61 | |
a1d2976b |
62 | \S{faq-ssh1}{Question} Does PuTTY support SSH v1? |
ee46ef84 |
63 | |
64 | Yes. SSH 1 support has always been available in PuTTY. |
65 | |
a1d2976b |
66 | \S{faq-localecho}{Question} Does PuTTY support local echo? |
ee46ef84 |
67 | |
32c37ecd |
68 | Yes. Version 0.52 has proper support for local echo. |
ee46ef84 |
69 | |
32c37ecd |
70 | In version 0.51 and before, local echo could not be separated from |
ee46ef84 |
71 | local line editing (where you type a line of text locally, and it is |
72 | not sent to the server until you press Return, so you have the |
73 | chance to edit it and correct mistakes \e{before} the server sees |
32c37ecd |
74 | it). New in version 0.52, local echo and local line editing are |
75 | separate options, and by default PuTTY will try to determine |
76 | automatically whether to enable them or not, based on which protocol |
77 | you have selected and also based on hints from the server. If you |
78 | have a problem with PuTTY's default choice, you can force each |
79 | option to be enabled or disabled as you choose. The controls are in |
80 | the Terminal panel, in the section marked \q{Line discipline |
81 | options}. |
ee46ef84 |
82 | |
a1d2976b |
83 | \S{faq-disksettings}{Question} Does PuTTY support storing its |
70706890 |
84 | settings in a disk file? |
ee46ef84 |
85 | |
86 | Not at present, although \k{config-file} in the documentation gives |
87 | a method of achieving the same effect. |
88 | |
a1d2976b |
89 | \S{faq-fullscreen}{Question} Does PuTTY support full-screen mode, |
70706890 |
90 | like a DOS box? |
ee46ef84 |
91 | |
32c37ecd |
92 | Yes; this is a new feature in version 0.52. |
ee46ef84 |
93 | |
babac7bd |
94 | \S{faq-password-remember}{Question} Does PuTTY have the ability to |
95 | remember my password so I don't have to type it every time? |
ee46ef84 |
96 | |
97 | No, it doesn't. |
98 | |
99 | Remembering your password is a bad plan for obvious security |
100 | reasons: anyone who gains access to your machine while you're away |
101 | from your desk can find out the remembered password, and use it, |
102 | abuse it or change it. |
103 | |
104 | In addition, it's not even \e{possible} for PuTTY to automatically |
105 | send your password in a Telnet session, because Telnet doesn't give |
106 | the client software any indication of which part of the login |
107 | process is the password prompt. PuTTY would have to guess, by |
108 | looking for words like \q{password} in the session data; and if your |
109 | login program is written in something other than English, this won't |
110 | work. |
111 | |
112 | In SSH, remembering your password would be possible in theory, but |
113 | there doesn't seem to be much point since SSH supports public key |
114 | authentication, which is more flexible and more secure. See |
115 | \k{pubkey} in the documentation for a full discussion of public key |
116 | authentication. |
117 | |
a1d2976b |
118 | \S{faq-hostkeys}{Question} Is there an option to turn off the |
70706890 |
119 | annoying host key prompts? |
cad566a9 |
120 | |
121 | No, there isn't. And there won't be. Even if you write it yourself |
122 | and send us the patch, we won't accept it. |
123 | |
124 | Those annoying host key prompts are the \e{whole point} of SSH. |
125 | Without them, all the cryptographic technology SSH uses to secure |
126 | your session is doing nothing more than making an attacker's job |
127 | slightly harder; instead of sitting between you and the server with |
128 | a packet sniffer, the attacker must actually subvert a router and |
129 | start modifying the packets going back and forth. But that's not all |
130 | that much harder than just sniffing; and without host key checking, |
131 | it will go completely undetected by client or server. |
132 | |
133 | Host key checking is your guarantee that the encryption you put on |
134 | your data at the client end is the \e{same} encryption taken off the |
135 | data at the server end; it's your guarantee that it hasn't been |
136 | removed and replaced somewhere on the way. Host key checking makes |
137 | the attacker's job \e{astronomically} hard, compared to packet |
138 | sniffing, and even compared to subverting a router. Instead of |
139 | applying a little intelligence and keeping an eye on Bugtraq, the |
140 | attacker must now perform a brute-force attack against at least one |
141 | military-strength cipher. That insignificant host key prompt really |
142 | does make \e{that} much difference. |
143 | |
144 | If you're having a specific problem with host key checking - perhaps |
145 | you want an automated batch job to make use of PSCP or Plink, and |
146 | the interactive host key prompt is hanging the batch process - then |
147 | the right way to fix it is to add the correct host key to the |
148 | Registry in advance. That way, you retain the \e{important} feature |
149 | of host key checking: the right key will be accepted and the wrong |
150 | ones will not. Adding an option to turn host key checking off |
151 | completely is the wrong solution and we will not do it. |
152 | |
2981454b |
153 | If you have host keys available in the common \c{known_hosts} format, |
154 | we have a script called |
155 | \W{http://cvs.tartarus.org/putty/contrib/kh2reg.py}\c{kh2reg.py} |
156 | to convert them to a Windows .REG file, which can be installed ahead of |
157 | time by double-clicking or using \c{REGEDIT}. |
158 | |
a1d2976b |
159 | \S{faq-server}{Question} Will you write an SSH server for the PuTTY |
70706890 |
160 | suite, to go with the client? |
ae915483 |
161 | |
162 | No. The only reason we might want to would be if we could easily |
163 | re-use existing code and significantly cut down the effort. We don't |
164 | believe this is the case; there just isn't enough common ground |
165 | between an SSH client and server to make it worthwhile. |
166 | |
167 | If someone else wants to use bits of PuTTY in the process of writing |
168 | a Windows SSH server, they'd be perfectly welcome to of course, but |
169 | I really can't see it being a lot less effort for us to do that than |
170 | it would be for us to write a server from the ground up. We don't |
171 | have time, and we don't have motivation. The code is available if |
172 | anyone else wants to try it. |
173 | |
67325335 |
174 | \S{faq-pscp-ascii}{Question} Can PSCP or PSFTP transfer files in |
175 | ASCII mode? |
176 | |
d2df61b3 |
177 | Unfortunately not. |
67325335 |
178 | |
d2df61b3 |
179 | Until recently, this was a limitation of the file transfer protocols: |
180 | the SCP and SFTP protocols had no notion of transferring a file in |
181 | anything other than binary mode. (This is still true of SCP.) |
182 | |
183 | The current draft protocol spec of SFTP proposes a means of |
184 | implementing ASCII transfer. At some point PSCP/PSFTP may implement |
185 | this proposal. |
67325335 |
186 | |
ee46ef84 |
187 | \H{faq-ports} Ports to other operating systems |
188 | |
189 | The eventual goal is for PuTTY to be a multi-platform program, able |
b18bcea3 |
190 | to run on at least Windows, Mac OS and Unix. |
ee46ef84 |
191 | |
192 | Porting will become easier once PuTTY has a generalised porting |
193 | layer, drawing a clear line between platform-dependent and |
59adac11 |
194 | platform-independent code. The general intention was for this |
195 | porting layer to evolve naturally as part of the process of doing |
5bcf5d50 |
196 | the first port; a Unix port has now been released and the plan |
197 | seems to be working so far. |
ee46ef84 |
198 | |
aff5267a |
199 | \S{faq-ports-general}{Question} What ports of PuTTY exist? |
200 | |
5bcf5d50 |
201 | Currently, release versions of PuTTY tools only run on full Win32 |
202 | systems and Unix. \q{Win32} includes Windows 95, 98, and ME, and it |
203 | includes Windows NT, Windows 2000 and Windows XP. |
204 | |
205 | In the development code, a partial port to the Mac OS (see |
206 | \k{faq-mac-port}) is under way. |
aff5267a |
207 | |
59adac11 |
208 | Currently PuTTY does \e{not} run on Windows CE (see \k{faq-wince}), |
209 | and it does not quite run on the Win32s environment under Windows |
210 | 3.1 (see \k{faq-win31}). |
aff5267a |
211 | |
59adac11 |
212 | We do not have release-quality ports for any other systems at the |
5bcf5d50 |
213 | present time. If anyone told you we had an EPOC port, or an iPaq port, |
59adac11 |
214 | or any other port of PuTTY, they were mistaken. We don't. |
215 | |
cb89ba78 |
216 | There are some third-party ports to various platforms, mentioned |
217 | on the Links page of our website. |
218 | |
5bcf5d50 |
219 | \S{faq-unix}{Question} Is there a port to Unix? |
220 | |
e6c7a73a |
221 | As of 0.54, there are Unix ports of most of the traditional PuTTY |
222 | tools, and also one entirely new application. |
59adac11 |
223 | |
5bcf5d50 |
224 | If you look at the source release, you should find a \c{unix} |
225 | subdirectory containing \c{Makefile.gtk}, which should build you Unix |
226 | ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also |
227 | \c{pterm} - an \cw{xterm}-type program which supports the same |
228 | terminal emulation as PuTTY. We do not yet have a Unix port of |
6bbb19af |
229 | Pageant. |
aff5267a |
230 | |
5bcf5d50 |
231 | If you don't have Gtk, you should still be able to build the |
232 | command-line tools. |
233 | |
234 | Note that Unix PuTTY has mostly only been tested on Linux so far; |
235 | portability problems such as BSD-style ptys or different header file |
236 | requirements are expected. |
237 | |
b86e68d8 |
238 | \S{faq-unix-why}{Question} What's the point of the Unix port? Unix |
239 | has OpenSSH. |
240 | |
241 | All sorts of little things. \c{pterm} is directly useful to anyone |
242 | who prefers PuTTY's terminal emulation to \c{xterm}'s, which at |
243 | least some people do. Unix Plink has apparently found a niche among |
244 | people who find the complexity of OpenSSL makes OpenSSH hard to |
245 | install (and who don't mind Plink not having as many features). Some |
246 | users want to generate a large number of SSH keys on Unix and then |
247 | copy them all into PuTTY, and the Unix PuTTYgen should allow them to |
248 | automate that conversion process. |
249 | |
250 | There were development advantages as well; porting PuTTY to Unix was |
251 | a valuable path-finding effort for other future ports, and also |
252 | allowed us to use the excellent Linux tool |
253 | \W{http://valgrind.kde.org/}{Valgrind} to help with debugging, which |
254 | has already improved PuTTY's stability on \e{all} platforms. |
255 | |
256 | However, if you're a Unix user and you can see no reason to switch |
257 | from OpenSSH to PuTTY/Plink, then you're probably right. We don't |
258 | expect our Unix port to be the right thing for everybody. |
259 | |
70cd2027 |
260 | \S{faq-wince}{Question} Will there be a port to Windows CE or PocketPC? |
ee46ef84 |
261 | |
4f2fd423 |
262 | It's currently being worked on, but it's only in its early stages yet, |
263 | and certainly isn't yet useful. PuTTY on portable devices would |
264 | clearly be a useful thing, so in the long term I hope it can be |
265 | brought up to release quality. |
ee46ef84 |
266 | |
22bf65b3 |
267 | There's a also third-party port at |
268 | \W{http://pocketputty.aleq.cz/}\c{http://pocketputty.aleq.cz/}. |
269 | |
f82f00d0 |
270 | \S{faq-win31}{Question} Is there a port to Windows 3.1? |
271 | |
272 | PuTTY is a 32-bit application from the ground up, so it won't run on |
273 | Windows 3.1 as a native 16-bit program; and it would be \e{very} |
274 | hard to port it to do so, because of Windows 3.1's vile memory |
275 | allocation mechanisms. |
276 | |
277 | However, it is possible in theory to compile the existing PuTTY |
278 | source in such a way that it will run under Win32s (an extension to |
279 | Windows 3.1 to let you run 32-bit programs). In order to do this |
280 | you'll need the right kind of C compiler - modern versions of Visual |
281 | C at least have stopped being backwards compatible to Win32s. Also, |
282 | the last time we tried this it didn't work very well. |
283 | |
284 | If you're interested in running PuTTY under Windows 3.1, help and |
285 | testing in this area would be very welcome! |
286 | |
babac7bd |
287 | \S{faq-mac-port}{Question} Will there be a port to the Mac? |
ee46ef84 |
288 | |
4f2fd423 |
289 | There is a port to the Mac OS in progress. It's just about usable, but |
290 | has an awful lot of gaps and rough edges that will need cleaning up |
9448161f |
291 | before release (such as useful random numbers). |
292 | |
293 | A separate port to Mac OS X is also underway. |
ee46ef84 |
294 | |
a1d2976b |
295 | \S{faq-epoc}{Question} Will there be a port to EPOC? |
ee46ef84 |
296 | |
297 | I hope so, but given that ports aren't really progressing very fast |
298 | even on systems the developers \e{do} already know how to program |
299 | for, it might be a long time before any of us get round to learning |
300 | a new system and doing the port for that. |
301 | |
4f2fd423 |
302 | However, some of the work has been done by other people, and a beta |
303 | port of PuTTY for the Nokia 9200 Communicator series is available |
304 | from \W{http://www.s2.org/putty/}\cw{http://www.s2.org/putty/} |
305 | |
ee46ef84 |
306 | \H{faq-embedding} Embedding PuTTY in other programs |
307 | |
a1d2976b |
308 | \S{faq-dll}{Question} Is the SSH or Telnet code available as a DLL? |
ee46ef84 |
309 | |
310 | No, it isn't. It would take a reasonable amount of rewriting for |
311 | this to be possible, and since the PuTTY project itself doesn't |
312 | believe in DLLs (they make installation more error-prone) none of us |
313 | has taken the time to do it. |
314 | |
315 | Most of the code cleanup work would be a good thing to happen in |
316 | general, so if anyone feels like helping, we wouldn't say no. |
317 | |
a1d2976b |
318 | \S{faq-vb}{Question} Is the SSH or Telnet code available as a Visual |
70706890 |
319 | Basic component? |
ee46ef84 |
320 | |
321 | No, it isn't. None of the PuTTY team uses Visual Basic, and none of |
322 | us has any particular need to make SSH connections from a Visual |
323 | Basic application. In addition, all the preliminary work to turn it |
324 | into a DLL would be necessary first; and furthermore, we don't even |
325 | know how to write VB components. |
326 | |
327 | If someone offers to do some of this work for us, we might consider |
328 | it, but unless that happens I can't see VB integration being |
329 | anywhere other than the very bottom of our priority list. |
330 | |
a1d2976b |
331 | \S{faq-ipc}{Question} How can I use PuTTY to make an SSH connection |
70706890 |
332 | from within another program? |
ee46ef84 |
333 | |
334 | Probably your best bet is to use Plink, the command-line connection |
335 | tool. If you can start Plink as a second Windows process, and |
336 | arrange for your primary process to be able to send data to the |
337 | Plink process, and receive data from it, through pipes, then you |
338 | should be able to make SSH connections from your program. |
339 | |
340 | This is what CVS for Windows does, for example. |
341 | |
342 | \H{faq-details} Details of PuTTY's operation |
343 | |
a1d2976b |
344 | \S{faq-term}{Question} What terminal type does PuTTY use? |
ee46ef84 |
345 | |
346 | For most purposes, PuTTY can be considered to be an \cw{xterm} |
32c37ecd |
347 | terminal. |
ee46ef84 |
348 | |
349 | PuTTY also supports some terminal control sequences not supported by |
350 | the real \cw{xterm}: notably the Linux console sequences that |
351 | reconfigure the colour palette, and the title bar control sequences |
352 | used by \cw{DECterm} (which are different from the \cw{xterm} ones; |
353 | PuTTY supports both). |
354 | |
355 | By default, PuTTY announces its terminal type to the server as |
356 | \c{xterm}. If you have a problem with this, you can reconfigure it |
357 | to say something else; \c{vt220} might help if you have trouble. |
358 | |
a1d2976b |
359 | \S{faq-settings}{Question} Where does PuTTY store its data? |
ee46ef84 |
360 | |
361 | PuTTY stores most of its data (saved sessions, SSH host keys) in the |
362 | Registry. The precise location is |
363 | |
364 | \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY |
365 | |
366 | and within that area, saved sessions are stored under \c{Sessions} |
367 | while host keys are stored under \c{SshHostKeys}. |
368 | |
369 | PuTTY also requires a random number seed file, to improve the |
370 | unpredictability of randomly chosen data needed as part of the SSH |
371 | cryptography. This is stored by default in your Windows home |
372 | directory (\c{%HOMEDRIVE%\\%HOMEPATH%}), or in the actual Windows |
373 | directory (such as \c{C:\\WINDOWS}) if the home directory doesn't |
374 | exist, for example if you're using Win95. If you want to change the |
375 | location of the random number seed file, you can put your chosen |
376 | pathname in the Registry, at |
377 | |
378 | \c HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\RandSeedFile |
379 | |
380 | \H{faq-howto} HOWTO questions |
381 | |
a1d2976b |
382 | \S{faq-startmax}{Question} How can I make PuTTY start up maximised? |
ee46ef84 |
383 | |
384 | Create a Windows shortcut to start PuTTY from, and set it as \q{Run |
385 | Maximized}. |
386 | |
a1d2976b |
387 | \S{faq-startsess}{Question} How can I create a Windows shortcut to |
70706890 |
388 | start a particular saved session directly? |
ee46ef84 |
389 | |
390 | To run a PuTTY session saved under the name \q{\cw{mysession}}, |
391 | create a Windows shortcut that invokes PuTTY with a command line |
392 | like |
393 | |
a58b605b |
394 | \c \path\name\to\putty.exe -load mysession |
395 | |
396 | (Note: prior to 0.53, the syntax was \c{@session}. This is now |
397 | deprecated and may be removed at some point.) |
ee46ef84 |
398 | |
a1d2976b |
399 | \S{faq-startssh}{Question} How can I start an SSH session straight |
70706890 |
400 | from the command line? |
ee46ef84 |
401 | |
402 | Use the command line \c{putty -ssh host.name}. Alternatively, create |
403 | a saved session that specifies the SSH protocol, and start the saved |
404 | session as shown in \k{faq-startsess}. |
405 | |
a1d2976b |
406 | \S{faq-cutpaste}{Question} How do I copy and paste between PuTTY and |
70706890 |
407 | other Windows applications? |
ee46ef84 |
408 | |
409 | Copy and paste works similarly to the X Window System. You use the |
410 | left mouse button to select text in the PuTTY window. The act of |
411 | selection \e{automatically} copies the text to the clipboard: there |
412 | is no need to press Ctrl-Ins or Ctrl-C or anything else. In fact, |
413 | pressing Ctrl-C will send a Ctrl-C character to the other end of |
414 | your connection (just like it does the rest of the time), which may |
415 | have unpleasant effects. The \e{only} thing you need to do, to copy |
416 | text to the clipboard, is to select it. |
417 | |
418 | To paste the clipboard contents into a PuTTY window, by default you |
419 | click the right mouse button. If you have a three-button mouse and |
420 | are used to X applications, you can configure pasting to be done by |
421 | the middle button instead, but this is not the default because most |
422 | Windows users don't have a middle button at all. |
423 | |
424 | You can also paste by pressing Shift-Ins. |
425 | |
a1d2976b |
426 | \S{faq-options}{Question} How do I use all PuTTY's features (public |
a58b605b |
427 | keys, proxying, cipher selection, etc.) in PSCP, PSFTP and Plink? |
428 | |
429 | Most major features (e.g., public keys, port forwarding) are available |
430 | through command line options. See the documentation. |
72be5b5e |
431 | |
a58b605b |
432 | Not all features are accessible from the command line yet, although |
433 | we'd like to fix this. In the meantime, you can use most of |
72be5b5e |
434 | PuTTY's features if you create a PuTTY saved session, and then use |
435 | the name of the saved session on the command line in place of a |
436 | hostname. This works for PSCP, PSFTP and Plink (but don't expect |
437 | port forwarding in the file transfer applications!). |
f2003e32 |
438 | |
a1d2976b |
439 | \S{faq-pscp}{Question} How do I use PSCP.EXE? When I double-click it |
70706890 |
440 | gives me a command prompt window which then closes instantly. |
ee46ef84 |
441 | |
442 | PSCP is a command-line application, not a GUI application. If you |
443 | run it without arguments, it will simply print a help message and |
444 | terminate. |
445 | |
446 | To use PSCP properly, run it from a Command Prompt window. See |
447 | \k{pscp} in the documentation for more details. |
448 | |
a1d2976b |
449 | \S{faq-pscp-spaces}{Question} How do I use PSCP to copy a file whose |
70706890 |
450 | name has spaces in? |
ee46ef84 |
451 | |
452 | If PSCP is using the traditional SCP protocol, this is confusing. If |
453 | you're specifying a file at the local end, you just use one set of |
454 | quotes as you would normally do: |
455 | |
456 | \c pscp "local filename with spaces" user@host: |
457 | \c pscp user@host:myfile "local filename with spaces" |
458 | |
459 | But if the filename you're specifying is on the \e{remote} side, you |
460 | have to use backslashes and two sets of quotes: |
461 | |
462 | \c pscp user@host:"\"remote filename with spaces\"" local_filename |
463 | \c pscp local_filename user@host:"\"remote filename with spaces\"" |
464 | |
465 | Worse still, in a remote-to-local copy you have to specify the local |
466 | file name explicitly, otherwise PSCP will complain that they don't |
467 | match (unless you specified the \c{-unsafe} option). The following |
468 | command will give an error message: |
469 | |
470 | \c c:\>pscp user@host:"\"oo er\"" . |
e9cee352 |
471 | \c warning: remote host tried to write to a file called 'oo er' |
472 | \c when we requested a file called '"oo er"'. |
ee46ef84 |
473 | |
e9cee352 |
474 | Instead, you need to specify the local file name in full: |
475 | |
476 | \c c:\>pscp user@host:"\"oo er\"" "oo er" |
477 | |
ee46ef84 |
478 | If PSCP is using the newer SFTP protocol, none of this is a problem, |
479 | and all filenames with spaces in are specified using a single pair |
480 | of quotes in the obvious way: |
481 | |
482 | \c pscp "local file" user@host: |
483 | \c pscp user@host:"remote file" . |
484 | |
485 | \H{faq-trouble} Troubleshooting |
486 | |
babac7bd |
487 | \S{faq-incorrect-mac}{Question} Why do I see \q{Incorrect MAC |
488 | received on packet}? |
ee46ef84 |
489 | |
f348999d |
490 | One possible cause of this that used to be common is a bug in old |
491 | SSH 2 servers distributed by \cw{ssh.com}. (This is not the only |
492 | possible cause; see \k{errors-crc} in the documentation.) |
493 | Version 2.3.0 and below of their SSH 2 server |
ee46ef84 |
494 | constructs Message Authentication Codes in the wrong way, and |
495 | expects the client to construct them in the same wrong way. PuTTY |
496 | constructs the MACs correctly by default, and hence these old |
497 | servers will fail to work with it. |
498 | |
32c37ecd |
499 | If you are using PuTTY version 0.52 or better, this should work |
500 | automatically: PuTTY should detect the buggy servers from their |
501 | version number announcement, and automatically start to construct |
502 | its MACs in the same incorrect manner as they do, so it will be able |
503 | to work with them. |
ee46ef84 |
504 | |
32c37ecd |
505 | If you are using PuTTY version 0.51 or below, you can enable the |
506 | workaround by going to the SSH panel and ticking the box labelled |
507 | \q{Imitate SSH 2 MAC bug}. It's possible that you might have to do |
508 | this with 0.52 as well, if a buggy server exists that PuTTY doesn't |
509 | know about. |
ee46ef84 |
510 | |
b7e2c163 |
511 | In this context MAC stands for Message Authentication Code. It's a |
512 | cryptographic term, and it has nothing at all to do with Ethernet |
513 | MAC (Media Access Control) addresses. |
514 | |
67325335 |
515 | \S{faq-pscp-protocol}{Question} Why do I see \q{Fatal: Protocol |
516 | error: Expected control record} in PSCP? |
517 | |
518 | This happens because PSCP was expecting to see data from the server |
519 | that was part of the PSCP protocol exchange, and instead it saw data |
520 | that it couldn't make any sense of at all. |
521 | |
522 | This almost always happens because the startup scripts in your |
523 | account on the server machine are generating output. This is |
524 | impossible for PSCP, or any other SCP client, to work around. You |
525 | should never use startup files (\c{.bashrc}, \c{.cshrc} and so on) |
526 | which generate output in non-interactive sessions. |
527 | |
528 | This is not actually a PuTTY problem. If PSCP fails in this way, |
529 | then all other SCP clients are likely to fail in exactly the same |
530 | way. The problem is at the server end. |
531 | |
a1d2976b |
532 | \S{faq-colours}{Question} I clicked on a colour in the Colours |
70706890 |
533 | panel, and the colour didn't change in my terminal. |
ee46ef84 |
534 | |
535 | That isn't how you're supposed to use the Colours panel. |
536 | |
537 | During the course of a session, PuTTY potentially uses \e{all} the |
538 | colours listed in the Colours panel. It's not a question of using |
539 | only one of them and you choosing which one; PuTTY will use them |
540 | \e{all}. The purpose of the Colours panel is to let you adjust the |
541 | appearance of all the colours. So to change the colour of the |
542 | cursor, for example, you would select \q{Cursor Colour}, press the |
543 | \q{Modify} button, and select a new colour from the dialog box that |
544 | appeared. Similarly, if you want your session to appear in green, |
545 | you should select \q{Default Foreground} and press \q{Modify}. |
546 | Clicking on \q{ANSI Green} won't turn your session green; it will |
547 | only allow you to adjust the \e{shade} of green used when PuTTY is |
548 | instructed by the server to display green text. |
549 | |
a1d2976b |
550 | \S{faq-winsock2}{Question} Plink on Windows 95 says it can't find |
70706890 |
551 | \cw{WS2_32.DLL}. |
ee46ef84 |
552 | |
553 | Plink requires the extended Windows network library, WinSock version |
554 | 2. This is installed as standard on Windows 98 and above, and on |
555 | Windows NT, and even on later versions of Windows 95; but early |
556 | Win95 installations don't have it. |
557 | |
558 | In order to use Plink on these systems, you will need to download |
559 | the |
560 | \W{http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/}{WinSock 2 upgrade}: |
561 | |
562 | \c http://www.microsoft.com/windows95/downloads/contents/wuadmintools/ |
563 | \c s_wunetworkingtools/w95sockets2/ |
564 | |
a1d2976b |
565 | \S{faq-outofmem}{Question} After trying to establish an SSH 2 |
70706890 |
566 | connection, PuTTY says \q{Out of memory} and dies. |
ee46ef84 |
567 | |
568 | If this happens just while the connection is starting up, this often |
569 | indicates that for some reason the client and server have failed to |
570 | establish a session encryption key. Somehow, they have performed |
571 | calculations that should have given each of them the same key, but |
572 | have ended up with different keys; so data encrypted by one and |
573 | decrypted by the other looks like random garbage. |
574 | |
575 | This causes an \q{out of memory} error because the first encrypted |
576 | data PuTTY expects to see is the length of an SSH message. Normally |
577 | this will be something well under 100 bytes. If the decryption has |
578 | failed, PuTTY will see a completely random length in the region of |
579 | two \e{gigabytes}, and will try to allocate enough memory to store |
580 | this non-existent message. This will immediately lead to it thinking |
581 | it doesn't have enough memory, and panicking. |
582 | |
583 | If this happens to you, it is quite likely to still be a PuTTY bug |
584 | and you should report it (although it might be a bug in your SSH |
585 | server instead); but it doesn't necessarily mean you've actually run |
586 | out of memory. |
587 | |
9accb45d |
588 | \S{faq-outofmem2}{Question} When attempting a file transfer, either |
589 | PSCP or PSFTP says \q{Out of memory} and dies. |
590 | |
591 | This is almost always caused by your login scripts on the server |
592 | generating output. PSCP or PSFTP will receive that output when they |
593 | were expecting to see the start of a file transfer protocol, and |
594 | they will attempt to interpret the output as file-transfer protocol. |
595 | This will usually lead to an \q{out of memory} error for much the |
596 | same reasons as given in \k{faq-outofmem}. |
597 | |
598 | This is a setup problem in your account on your server, \e{not} a |
599 | PSCP/PSFTP bug. Your login scripts should \e{never} generate output |
600 | during non-interactive sessions; secure file transfer is not the |
601 | only form of remote access that will break if they do. |
602 | |
603 | On Unix, a simple fix is to ensure that all the parts of your login |
604 | script that might generate output are in \c{.profile} (if you use a |
605 | Bourne shell derivative) or \c{.login} (if you use a C shell). |
606 | Putting them in more general files such as \c{.bashrc} or \c{.cshrc} |
607 | is liable to lead to problems. |
608 | |
7b24f677 |
609 | \S{faq-psftp-slow}{Question} PSFTP transfers files much slower than PSCP. |
9accb45d |
610 | |
b7280cfe |
611 | The throughput of PSFTP 0.54 should be much better than 0.53b and |
612 | prior; we've added code to the SFTP backend to queue several blocks |
613 | of data rather than waiting for an acknowledgement for each. (The |
614 | SCP backend did not suffer from this performance issue because SCP |
615 | is a much simpler protocol.) |
9accb45d |
616 | |
a1d2976b |
617 | \S{faq-bce}{Question} When I run full-colour applications, I see |
70706890 |
618 | areas of black space where colour ought to be. |
f1453e5c |
619 | |
620 | You almost certainly need to enable the \q{Use background colour to |
621 | erase screen} setting in the Terminal panel. Note that if you do |
5bcf5d50 |
622 | this in mid-session, it may not take effect until you reset the |
f1453e5c |
623 | terminal (see \k{faq-resetterm}). |
624 | |
a1d2976b |
625 | \S{faq-resetterm}{Question} When I change some terminal settings, |
70706890 |
626 | nothing happens. |
f1453e5c |
627 | |
628 | Some of the terminal options (notably Auto Wrap and |
629 | background-colour screen erase) actually represent the \e{default} |
630 | setting, rather than the currently active setting. The server can |
631 | send sequences that modify these options in mid-session, but when |
632 | the terminal is reset (by server action, or by you choosing \q{Reset |
633 | Terminal} from the System menu) the defaults are restored. |
634 | |
5bcf5d50 |
635 | In versions 0.53b and prior, if you change one of these options in |
636 | the middle of a session, you will find that the change does not |
637 | immediately take effect. It will only take effect once you reset |
638 | the terminal. |
639 | |
e6c7a73a |
640 | In version 0.54, the behaviour has changed - changes to these |
641 | settings take effect immediately. |
f1453e5c |
642 | |
a1d2976b |
643 | \S{faq-idleout}{Question} My PuTTY sessions unexpectedly close after |
70706890 |
644 | they are idle for a while. |
ee46ef84 |
645 | |
646 | Some types of firewall, and almost any router doing Network Address |
647 | Translation (NAT, also known as IP masquerading), will forget about |
648 | a connection through them if the connection does nothing for too |
649 | long. This will cause the connection to be rudely cut off when |
650 | contact is resumed. |
651 | |
652 | You can try to combat this by telling PuTTY to send \e{keepalives}: |
653 | packets of data which have no effect on the actual session, but |
654 | which reassure the router or firewall that the network connection is |
655 | still active and worth remembering about. |
656 | |
657 | Keepalives don't solve everything, unfortunately; although they |
658 | cause greater robustness against this sort of router, they can also |
659 | cause a \e{loss} of robustness against network dropouts. See |
660 | \k{config-keepalive} in the documentation for more discussion of |
661 | this. |
662 | |
a1d2976b |
663 | \S{faq-timeout}{Question} PuTTY's network connections time out too |
70706890 |
664 | quickly when network connectivity is temporarily lost. |
ee46ef84 |
665 | |
666 | This is a Windows problem, not a PuTTY problem. The timeout value |
667 | can't be set on per application or per session basis. To increase |
668 | the TCP timeout globally, you need to tinker with the Registry. |
669 | |
670 | On Windows 95, 98 or ME, the registry key you need to change is |
671 | |
672 | \c HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\ |
673 | \c MSTCP\MaxDataRetries |
674 | |
675 | (it must be of type DWORD in Win95, or String in Win98/ME). |
676 | |
677 | On Windows NT or 2000, the registry key is |
678 | |
679 | \c HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ |
680 | \c Parameters\TcpMaxDataRetransmissions |
681 | |
682 | and it must be of type DWORD. |
683 | |
684 | Set the key's value to something like 10. This will cause Windows to |
685 | try harder to keep connections alive instead of abandoning them. |
686 | |
a1d2976b |
687 | \S{faq-puttyputty}{Question} When I \cw{cat} a binary file, I get |
ee46ef84 |
688 | `PuTTYPuTTYPuTTY' on my command line. |
689 | |
a5a6cb30 |
690 | Don't do that, then. |
ee46ef84 |
691 | |
692 | This is designed behaviour; when PuTTY receives the character |
693 | Control-E from the remote server, it interprets it as a request to |
694 | identify itself, and so it sends back the string \q{\cw{PuTTY}} as |
695 | if that string had been entered at the keyboard. Control-E should |
696 | only be sent by programs that are prepared to deal with the |
697 | response. Writing a binary file to your terminal is likely to output |
698 | many Control-E characters, and cause this behaviour. Don't do it. |
699 | It's a bad plan. |
700 | |
a5a6cb30 |
701 | To mitigate the effects, you could configure the answerback string |
702 | to be empty (see \k{config-answerback}); but writing binary files to |
703 | your terminal is likely to cause various other unpleasant behaviour, |
704 | so this is only a small remedy. |
705 | |
babac7bd |
706 | \S{faq-wintitle}{Question} When I \cw{cat} a binary file, my window |
707 | title changes to a nonsense string. |
ee46ef84 |
708 | |
a5a6cb30 |
709 | Don't do that, then. |
ee46ef84 |
710 | |
711 | It is designed behaviour that PuTTY should have the ability to |
712 | adjust the window title on instructions from the server. Normally |
713 | the control sequence that does this should only be sent |
714 | deliberately, by programs that know what they are doing and intend |
715 | to put meaningful text in the window title. Writing a binary file to |
716 | your terminal runs the risk of sending the same control sequence by |
717 | accident, and cause unexpected changes in the window title. Don't do |
718 | it. |
719 | |
babac7bd |
720 | \S{faq-password-fails}{Question} My keyboard stops working once |
721 | PuTTY displays the password prompt. |
59c1f1f6 |
722 | |
723 | No, it doesn't. PuTTY just doesn't display the password you type, so |
724 | that someone looking at your screen can't see what it is. |
725 | |
726 | Unlike the Windows login prompts, PuTTY doesn't display the password |
727 | as a row of asterisks either. This is so that someone looking at |
728 | your screen can't even tell how \e{long} your password is, which |
729 | might be valuable information. |
730 | |
b5bee048 |
731 | \S{faq-keyboard}{Question} One or more function keys don't do what I |
732 | expected in a server-side application. |
733 | |
734 | If you've already tried all the relevant options in the PuTTY |
735 | Keyboard panel, you may need to mail the PuTTY maintainers and ask. |
736 | |
737 | It is \e{not} usually helpful just to tell us which application, |
738 | which server operating system, and which key isn't working; in order |
739 | to replicate the problem we would need to have a copy of every |
740 | operating system, and every application, that anyone has ever |
741 | complained about. |
742 | |
743 | PuTTY responds to function key presses by sending a sequence of |
744 | control characters to the server. If a function key isn't doing what |
745 | you expect, it's likely that the character sequence your application |
746 | is expecting to receive is not the same as the one PuTTY is sending. |
747 | Therefore what we really need to know is \e{what} sequence the |
748 | application is expecting. |
749 | |
750 | The simplest way to investigate this is to find some other terminal |
751 | environment, in which that function key \e{does} work; and then |
752 | investigate what sequence the function key is sending in that |
753 | situation. One reasonably easy way to do this on a Unix system is to |
754 | type the command \c{cat}, and then press the function key. This is |
755 | likely to produce output of the form \c{^[[11~}. You can also do |
756 | this in PuTTY, to find out what sequence the function key is |
757 | producing in that. Then you can mail the PuTTY maintainers and tell |
758 | us \q{I wanted the F1 key to send \c{^[[11~}, but instead it's |
759 | sending \c{^[OP}, can this be done?}, or something similar. |
760 | |
761 | You should still read the |
762 | \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html}{Feedback |
763 | page} on the PuTTY website (also provided as \k{feedback} in the |
764 | manual), and follow the guidelines contained in that. |
765 | |
941d39e2 |
766 | \S{faq-openssh-bad-openssl}{Question} Since my SSH server was upgraded |
767 | to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY. |
1d2a9c9c |
768 | |
769 | There is a known problem when OpenSSH has been built against an |
770 | incorrect version of OpenSSL; the quick workaround is to configure |
771 | PuTTY to use SSH protocol 2 and the Blowfish cipher. |
772 | |
941d39e2 |
773 | For more details and OpenSSH patches, see |
774 | \W{http://bugzilla.mindrot.org/show_bug.cgi?id=138}{bug 138} in the |
775 | OpenSSH BTS. |
776 | |
1d2a9c9c |
777 | This is not a PuTTY-specific problem; if you try to connect with |
941d39e2 |
778 | another client you'll likely have similar problems. (Although PuTTY's |
779 | default cipher differs from many other clients.) |
1d2a9c9c |
780 | |
941d39e2 |
781 | \e{OpenSSH 3.1p1:} configurations known to be broken (and symptoms): |
1d2a9c9c |
782 | |
783 | \b SSH 2 with AES cipher (PuTTY says "Assertion failed! Expression: |
784 | (len & 15) == 0" in sshaes.c, or "Out of memory", or crashes) |
785 | |
9712b085 |
786 | \b SSH 2 with 3DES (PuTTY says "Incorrect MAC received on packet") |
787 | |
1d2a9c9c |
788 | \b SSH 1 with Blowfish (PuTTY says "Incorrect CRC received on |
789 | packet") |
790 | |
791 | \b SSH 1 with 3DES |
792 | |
941d39e2 |
793 | \e{OpenSSH 3.4p1:} as of 3.4p1, only the problem with SSH 1 and |
794 | Blowfish remains. Rebuild your server, apply the patch linked to from |
795 | bug 138 above, or use another cipher (e.g., 3DES) instead. |
59f76022 |
796 | |
46ccbe20 |
797 | \e{Other versions:} we occasionally get reports of the same symptom |
798 | and workarounds with older versions of OpenSSH, although it's not |
799 | clear the underlying cause is the same. |
800 | |
1bb76745 |
801 | \S{faq-ssh2key-ssh1conn}{Question} Why do I see "Couldn't load private |
802 | key from ..."? Why can PuTTYgen load my key but not PuTTY? |
803 | |
804 | It's likely that you've generated an SSH protocol 2 key with PuTTYgen, |
805 | but you're trying to use it in an SSH 1 connection. SSH1 and SSH2 keys |
806 | have different formats, and (at least in 0.52) PuTTY's reporting of a |
807 | key in the wrong format isn't optimal. |
808 | |
809 | To connect using SSH 2 to a server that supports both versions, you |
810 | need to change the configuration from the default (see \k{faq-ssh2}). |
811 | |
2c4b913d |
812 | \S{faq-rh8-utf8}{Question} When I'm connected to a Red Hat Linux 8.0 |
813 | system, some characters don't display properly. |
814 | |
815 | A common complaint is that hyphens in man pages show up as a-acute. |
816 | |
817 | With release 8.0, Red Hat appear to have made UTF-8 the default |
818 | character set. There appears to be no way for terminal emulators such |
819 | as PuTTY to know this (as far as we know, the appropriate escape |
820 | sequence to switch into UTF-8 mode isn't sent). |
821 | |
822 | A fix is to configure sessions to RH8 systems to use UTF-8 |
823 | translation - see \k{config-charset} in the documentation. (Note that |
824 | if you use \q{Change Settings}, changes may not take place immediately |
825 | - see \k{faq-resetterm}.) |
826 | |
827 | If you really want to change the character set used by the server, the |
828 | right place is \c{/etc/sysconfig/i18n}, but this shouldn't be |
829 | necessary. |
830 | |
b86e68d8 |
831 | \S{faq-screen}{Question} Since I upgraded to PuTTY 0.54, the |
832 | scrollback has stopped working when I run \c{screen}. |
833 | |
834 | PuTTY's terminal emulator has always had the policy that when the |
835 | \q{alternate screen} is in use, nothing is added to the scrollback. |
836 | This is because the usual sorts of programs which use the alternate |
837 | screen are things like text editors, which tend to scroll back and |
838 | forth in the same document a lot; so (a) they would fill up the |
839 | scrollback with a large amount of unhelpfully disordered text, and |
840 | (b) they contain their \e{own} method for the user to scroll back to |
841 | the bit they were interested in. We have generally found this policy |
842 | to do the Right Thing in almost all situations. |
843 | |
844 | Unfortunately, \c{screen} is one exception: it uses the alternate |
845 | screen, but it's still usually helpful to have PuTTY's scrollback |
846 | continue working. The simplest solution is to go to the Features |
847 | control panel and tick \q{Disable switching to alternate terminal |
848 | screen}. (See \k{config-features-altscreen} for more details.) |
849 | |
850 | The reason why this only started to be a problem in 0.54 is because |
851 | \c{screen} typically uses an unusual control sequence to switch to |
852 | the alternate screen, and previous versions of PuTTY did not support |
853 | this sequence. |
854 | |
ee46ef84 |
855 | \H{faq-secure} Security questions |
856 | |
a1d2976b |
857 | \S{faq-publicpc}{Question} Is it safe for me to download PuTTY and |
70706890 |
858 | use it on a public PC? |
ee46ef84 |
859 | |
860 | It depends on whether you trust that PC. If you don't trust the |
861 | public PC, don't use PuTTY on it, and don't use any other software |
862 | you plan to type passwords into either. It might be watching your |
863 | keystrokes, or it might tamper with the PuTTY binary you download. |
864 | There is \e{no} program safe enough that you can run it on an |
865 | actively malicious PC and get away with typing passwords into it. |
866 | |
867 | If you do trust the PC, then it's probably OK to use PuTTY on it |
868 | (but if you don't trust the network, then the PuTTY download might |
869 | be tampered with, so it would be better to carry PuTTY with you on a |
870 | floppy). |
871 | |
a1d2976b |
872 | \S{faq-cleanup}{Question} What does PuTTY leave on a system? How can |
70706890 |
873 | I clean up after it? |
ee46ef84 |
874 | |
875 | PuTTY will leave some Registry entries, and a random seed file, on |
876 | the PC (see \k{faq-settings}). If you are using PuTTY on a public |
877 | PC, or somebody else's PC, you might want to clean these up when you |
878 | leave. You can do that automatically, by running the command |
879 | \c{putty -cleanup}. |
880 | |
a1d2976b |
881 | \S{faq-dsa}{Question} How come PuTTY now supports DSA, when the |
70706890 |
882 | website used to say how insecure it was? |
ee46ef84 |
883 | |
884 | DSA has a major weakness \e{if badly implemented}: it relies on a |
885 | random number generator to far too great an extent. If the random |
886 | number generator produces a number an attacker can predict, the DSA |
887 | private key is exposed - meaning that the attacker can log in as you |
888 | on all systems that accept that key. |
889 | |
890 | The PuTTY policy changed because the developers were informed of |
891 | ways to implement DSA which do not suffer nearly as badly from this |
892 | weakness, and indeed which don't need to rely on random numbers at |
893 | all. For this reason we now believe PuTTY's DSA implementation is |
894 | probably OK. However, if you have the choice, we still recommend you |
895 | use RSA instead. |
896 | |
ee4b471f |
897 | \S{faq-virtuallock}{Question} Couldn't Pageant use |
898 | \cw{VirtualLock()} to stop private keys being written to disk? |
f9908cf7 |
899 | |
ee4b471f |
900 | Unfortunately not. The \cw{VirtualLock()} function in the Windows |
901 | API doesn't do a proper job: it may prevent small pieces of a |
902 | process's memory from being paged to disk while the process is |
903 | running, but it doesn't stop the process's memory as a whole from |
904 | being swapped completely out to disk when the process is long-term |
905 | inactive. And Pageant spends most of its time inactive. |
f9908cf7 |
906 | |
ee46ef84 |
907 | \H{faq-admin} Administrative questions |
908 | |
a1d2976b |
909 | \S{faq-domain}{Question} Would you like me to register you a nicer |
70706890 |
910 | domain name? |
ee46ef84 |
911 | |
912 | No, thank you. Even if you can find one (most of them seem to have |
913 | been registered already, by people who didn't ask whether we |
914 | actually wanted it before they applied), we're happy with the PuTTY |
915 | web site being exactly where it is. It's not hard to find (just type |
916 | \q{putty} into \W{http://www.google.com/}{google.com} and we're the |
917 | first link returned), and we don't believe the administrative hassle |
918 | of moving the site would be worth the benefit. |
919 | |
920 | In addition, if we \e{did} want a custom domain name, we would want |
921 | to run it ourselves, so we knew for certain that it would continue |
922 | to point where we wanted it, and wouldn't suddenly change or do |
923 | strange things. Having it registered for us by a third party who we |
924 | don't even know is not the best way to achieve this. |
925 | |
a1d2976b |
926 | \S{faq-webhosting}{Question} Would you like free web hosting for the |
70706890 |
927 | PuTTY web site? |
ee46ef84 |
928 | |
929 | We already have some, thanks. |
930 | |
34185d04 |
931 | \S{faq-link}{Question} Would you link to my web site from the PuTTY |
932 | web site? |
933 | |
934 | Only if the content of your web page is of definite direct interest |
935 | to PuTTY users. If your content is unrelated, or only tangentially |
936 | related, to PuTTY, then the link would simply be advertising for |
937 | you. |
938 | |
939 | One very nice effect of the Google ranking mechanism is that by and |
940 | large, the most popular web sites get the highest rankings. This |
941 | means that when an ordinary person does a search, the top item in |
942 | the search is very likely to be a high-quality site or the site they |
943 | actually wanted, rather than the site which paid the most money for |
944 | its ranking. |
945 | |
946 | The PuTTY web site is held in high esteem by Google, for precisely |
947 | this reason: lots of people have linked to it simply because they |
948 | like PuTTY, without us ever having to ask anyone to link to us. We |
949 | feel that it would be an abuse of this esteem to use it to boost the |
950 | ranking of random advertisers' web sites. If you want your web site |
951 | to have a high Google ranking, we'd prefer that you achieve this the |
952 | way we did - by being good enough at what you do that people will |
953 | link to you simply because they like you. |
954 | |
b609f258 |
955 | In particular, we aren't interested in trading links for money (see |
956 | above), and we \e{certainly} aren't interested in trading links for |
957 | other links (since we have no advertising on our web site, our |
958 | Google ranking is not even directly worth anything to us). If we |
959 | don't want to link to you for free, then we probably won't want to |
960 | link to you at all. |
961 | |
34185d04 |
962 | If you have software based on PuTTY, or specifically designed to |
963 | interoperate with PuTTY, or in some other way of genuine interest to |
964 | PuTTY users, then we will probably be happy to add a link to you on |
965 | our Links page. And if you're running a mirror of the PuTTY web |
966 | site, we're \e{definitely} interested. |
967 | |
a1d2976b |
968 | \S{faq-sourceforge}{Question} Why don't you move PuTTY to |
70706890 |
969 | SourceForge? |
ee46ef84 |
970 | |
971 | Partly, because we don't want to move the web site location (see |
972 | \k{faq-domain}). |
973 | |
974 | Also, security reasons. PuTTY is a security product, and as such it |
975 | is particularly important to guard the code and the web site against |
976 | unauthorised modifications which might introduce subtle security |
977 | flaws. Therefore, we prefer that the CVS repository, web site and |
978 | FTP site remain where they are, under the direct control of system |
979 | administrators we know and trust personally, rather than being run |
980 | by a large organisation full of people we've never met and which is |
981 | known to have had breakins in the past. |
982 | |
983 | No offence to SourceForge; I think they do a wonderful job. But |
984 | they're not ideal for everyone, and in particular they're not ideal |
985 | for us. |
986 | |
a1d2976b |
987 | \S{faq-mailinglist1}{Question} Why can't I subscribe to the |
70706890 |
988 | putty-bugs mailing list? |
ee46ef84 |
989 | |
990 | Because you're not a member of the PuTTY core development team. The |
991 | putty-bugs mailing list is not a general newsgroup-like discussion |
992 | forum; it's a contact address for the core developers, and an |
993 | \e{internal} mailing list for us to discuss things among ourselves. |
994 | If we opened it up for everybody to subscribe to, it would turn into |
995 | something more like a newsgroup and we would be completely |
996 | overwhelmed by the volume of traffic. It's hard enough to keep up |
997 | with the list as it is. |
998 | |
a1d2976b |
999 | \S{faq-mailinglist2}{Question} If putty-bugs isn't a |
70706890 |
1000 | general-subscription mailing list, what is? |
ee46ef84 |
1001 | |
1002 | There isn't one, that we know of. |
1003 | |
be86e512 |
1004 | If someone else wants to set up a mailing list or other forum for |
1005 | PuTTY users to help each other with common problems, that would be |
1006 | fine with us, though the PuTTY team would almost certainly not have the |
1007 | time to read it. It's probably better to use the established |
1008 | newsgroup \cw{comp.security.ssh} for this purpose. |
ee46ef84 |
1009 | |
a1d2976b |
1010 | \S{faq-donations}{Question} How can I donate to PuTTY development? |
ee46ef84 |
1011 | |
1012 | Please, \e{please} don't feel you have to. PuTTY is completely free |
1013 | software, and not shareware. We think it's very important that |
1014 | \e{everybody} who wants to use PuTTY should be able to, whether they |
1015 | have any money or not; so the last thing we would want is for a |
1016 | PuTTY user to feel guilty because they haven't paid us any money. If |
1017 | you want to keep your money, please do keep it. We wouldn't dream of |
1018 | asking for any. |
1019 | |
1020 | Having said all that, if you still really \e{want} to give us money, |
1021 | we won't argue :-) The easiest way for us to accept donations is if |
2244ea7b |
1022 | you send money to \cw{<anakin@pobox.com>} using PayPal |
1023 | (\W{http://www.paypal.com/}\cw{www.paypal.com}). Alternatively, if |
1024 | you don't trust PayPal, you could donate through e-gold |
1025 | (\W{http://www.e-gold.com}\cw{www.e-gold.com}): deposit your |
1026 | donation in account number 174769, then send us e-mail to let us |
1027 | know you've done so (otherwise we might not notice for months!). |
ee46ef84 |
1028 | |
1029 | Small donations (tens of dollars or tens of euros) will probably be |
1030 | spent on beer or curry, which helps motivate our volunteer team to |
1031 | continue doing this for the world. Larger donations will be spent on |
1032 | something that actually helps development, if we can find anything |
9cd3f7b0 |
1033 | (perhaps new hardware, or a copy of Windows XP), but if we can't |
ee46ef84 |
1034 | find anything then we'll just distribute the money among the |
1035 | developers. If you want to be sure your donation is going towards |
1036 | something worthwhile, ask us first. If you don't like these terms, |
1037 | feel perfectly free not to donate. We don't mind. |
1038 | |
f9908cf7 |
1039 | \H{faq-misc} Miscellaneous questions |
1040 | |
1041 | \S{faq-openssh}{Question} Is PuTTY a port of OpenSSH, or based on |
1042 | OpenSSH? |
1043 | |
1044 | No, it isn't. PuTTY is almost completely composed of code written |
1045 | from scratch for PuTTY. The only code we share with OpenSSH is the |
1046 | detector for SSH1 CRC compensation attacks, written by CORE SDI S.A. |
1047 | |
606398fb |
1048 | \S{faq-sillyputty}{Question} Where can I buy silly putty? |
1049 | |
1050 | You're looking at the wrong web site; the only PuTTY we know about |
1051 | here is the name of a computer program. |
1052 | |
1053 | If you want the kind of putty you can buy as an executive toy, the |
1054 | PuTTY team can personally recommend Thinking Putty, which you can |
1055 | buy from Crazy Aaron's Putty World, at |
1056 | \W{http://www.puttyworld.com}\cw{www.puttyworld.com}. |
1057 | |
fa58cf81 |
1058 | \S{faq-meaning}{Question} What does \q{PuTTY} mean? |
ee46ef84 |
1059 | |
fa58cf81 |
1060 | It's the name of a popular SSH and Telnet client. Any other meaning |
1061 | is in the eye of the beholder. It's been rumoured that \q{PuTTY} |
1062 | is the antonym of \q{\cw{getty}}, or that it's the stuff that makes your |
1063 | Windows useful, or that it's a kind of plutonium Teletype. We |
1064 | couldn't possibly comment on such allegations. |
1065 | |
1066 | \S{faq-pronounce}{Question} How do I pronounce \q{PuTTY}? |
1067 | |
1068 | Exactly like the English word \q{putty}, which we pronounce |
1069 | /\u02C8{'}p\u028C{V}t\u026A{I}/. |