39a938f7 |
1 | \define{versionidpsftp} \versionid $Id$ |
9a313f60 |
2 | |
421406a4 |
3 | \C{psftp} Using \i{PSFTP} to transfer files securely |
9a313f60 |
4 | |
421406a4 |
5 | \i{PSFTP}, the PuTTY SFTP client, is a tool for \i{transferring files} |
9a313f60 |
6 | securely between computers using an SSH connection. |
7 | |
8 | PSFTP differs from PSCP in the following ways: |
9 | |
10 | \b PSCP should work on virtually every SSH server. PSFTP uses the |
421406a4 |
11 | new \i{SFTP} protocol, which is a feature of SSH-2 only. (PSCP will also |
2e85c969 |
12 | use this protocol if it can, but there is an SSH-1 equivalent it can |
9a313f60 |
13 | fall back to if it cannot.) |
14 | |
15 | \b PSFTP allows you to run an interactive file transfer session, |
421406a4 |
16 | much like the Windows \i\c{ftp} program. You can list the contents of |
9a313f60 |
17 | directories, browse around the file system, issue multiple \c{get} |
18 | and \c{put} commands, and eventually log out. By contrast, PSCP is |
19 | designed to do a single file transfer operation and immediately |
20 | terminate. |
21 | |
22 | \H{psftp-starting} Starting PSFTP |
23 | |
24 | The usual way to start PSFTP is from a command prompt, much like |
25 | PSCP. To do this, it will need either to be on your \i{\c{PATH}} or |
26 | in your current directory. To add the directory containing PSFTP to |
27 | your \c{PATH} environment variable, type into the console window: |
28 | |
29 | \c set PATH=C:\path\to\putty\directory;%PATH% |
30 | |
31 | Unlike PSCP, however, PSFTP has no complex command-line syntax; you |
32 | just specify a host name and perhaps a user name: |
33 | |
34 | \c psftp server.example.com |
35 | |
36 | or perhaps |
37 | |
38 | \c psftp fred@server.example.com |
39 | |
40 | Alternatively, if you just type \c{psftp} on its own (or |
41 | double-click the PSFTP icon in the Windows GUI), you will see the |
42 | PSFTP prompt, and a message telling you PSFTP has not connected to |
43 | any server: |
44 | |
45 | \c C:\>psftp |
46 | \c psftp: no hostname specified; use "open host.name" to connect |
47 | \c psftp> |
48 | |
49 | At this point you can type \c{open server.example.com} or \c{open |
50 | fred@server.example.com} to start a session. |
51 | |
e117a742 |
52 | PSFTP accepts all the general command line options supported by the |
53 | PuTTY tools, except the ones which make no sense in a file transfer |
54 | utility. See \k{using-general-opts} for a description of these |
55 | options. (The ones not supported by PSFTP are clearly marked.) |
9a313f60 |
56 | |
e117a742 |
57 | PSFTP also supports some of its own options. The following sections |
58 | describe PSFTP's specific command-line options. |
9a313f60 |
59 | |
421406a4 |
60 | \S{psftp-option-b} \I{-b-PSFTP}\c{-b}: specify a file containing batch commands |
9a313f60 |
61 | |
62 | In normal operation, PSFTP is an interactive program which displays |
63 | a command line and accepts commands from the keyboard. |
64 | |
65 | If you need to do automated tasks with PSFTP, you would probably |
421406a4 |
66 | prefer to \I{batch scripts in PSFTP}specify a set of commands in |
67 | advance and have them executed automatically. The \c{-b} option |
68 | allows you to do this. You use it with a file name containing batch |
69 | commands. For example, you might create a file called \c{myscript.scr} |
70 | containing lines like this: |
9a313f60 |
71 | |
72 | \c cd /home/ftp/users/jeff |
73 | \c del jam-old.tar.gz |
74 | \c ren jam.tar.gz jam-old.tar.gz |
75 | \c put jam.tar.gz |
76 | \c chmod a+r jam.tar.gz |
9a313f60 |
77 | |
78 | and then you could run the script by typing |
79 | |
80 | \c psftp user@hostname -b myscript.scr |
81 | |
82 | When you run a batch script in this way, PSFTP will abort the script |
83 | if any command fails to complete successfully. To change this |
f45c22d6 |
84 | behaviour, you can add the \c{-be} option (\k{psftp-option-be}). |
9a313f60 |
85 | |
1854be53 |
86 | PSFTP will terminate after it finishes executing the batch script. |
87 | |
421406a4 |
88 | \S{psftp-option-bc} \I{-bc-PSFTP}\c{-bc}: display batch commands as they are run |
9a313f60 |
89 | |
90 | The \c{-bc} option alters what PSFTP displays while processing a |
f45c22d6 |
91 | batch script specified with \c{-b}. With the \c{-bc} option, PSFTP |
92 | will display prompts and commands just as if the commands had been |
93 | typed at the keyboard. So instead of seeing this: |
9a313f60 |
94 | |
f45c22d6 |
95 | \c C:\>psftp fred@hostname -b batchfile |
9a313f60 |
96 | \c Sent username "fred" |
97 | \c Remote working directory is /home/fred |
98 | \c Listing directory /home/fred/lib |
99 | \c drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 . |
100 | \c drwxr-sr-x 25 fred fred 2048 Dec 14 09:36 .. |
101 | \c drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jed |
102 | \c lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timber |
103 | \c drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn |
104 | |
105 | you might see this: |
106 | |
f45c22d6 |
107 | \c C:\>psftp fred@hostname -bc -b batchfile |
9a313f60 |
108 | \c Sent username "fred" |
109 | \c Remote working directory is /home/fred |
110 | \c psftp> dir lib |
111 | \c Listing directory /home/fred/lib |
112 | \c drwxrwsr-x 4 fred fred 1024 Sep 6 10:42 . |
113 | \c drwxr-sr-x 25 fred fred 2048 Dec 14 09:36 .. |
114 | \c drwxrwsr-x 3 fred fred 1024 Apr 17 2000 jed |
115 | \c lrwxrwxrwx 1 fred fred 24 Apr 17 2000 timber |
116 | \c drwxrwsr-x 2 fred fred 1024 Mar 13 2000 trn |
117 | \c psftp> quit |
118 | |
421406a4 |
119 | \S{psftp-option-be} \I{-be-PSFTP}\c{-be}: continue batch processing on errors |
9a313f60 |
120 | |
f45c22d6 |
121 | When running a batch file, this additional option causes PSFTP to |
122 | continue processing even if a command fails to complete successfully. |
9a313f60 |
123 | |
124 | You might want this to happen if you wanted to delete a file and |
125 | didn't care if it was already not present, for example. |
126 | |
421406a4 |
127 | \S{psftp-usage-options-batch} \I{-batch-PSFTP}\c{-batch}: avoid |
128 | interactive prompts |
ff2ae367 |
129 | |
130 | If you use the \c{-batch} option, PSFTP will never give an |
131 | interactive prompt while establishing the connection. If the |
132 | server's host key is invalid, for example (see \k{gs-hostkey}), then |
133 | the connection will simply be abandoned instead of asking you what |
134 | to do next. |
135 | |
136 | This may help PSFTP's behaviour when it is used in automated |
137 | scripts: using \c{-batch}, if something goes wrong at connection |
138 | time, the batch job will fail rather than hang. |
139 | |
9a313f60 |
140 | \H{psftp-commands} Running PSFTP |
141 | |
142 | Once you have started your PSFTP session, you will see a \c{psftp>} |
143 | prompt. You can now type commands to perform file-transfer |
144 | functions. This section lists all the available commands. |
145 | |
421406a4 |
146 | \S{psftp-quoting} \I{quoting, in PSFTP}General quoting rules for PSFTP commands |
3af97463 |
147 | |
148 | Most PSFTP commands are considered by the PSFTP command interpreter |
149 | as a sequence of words, separated by spaces. For example, the |
150 | command \c{ren oldfilename newfilename} splits up into three words: |
151 | \c{ren} (the command name), \c{oldfilename} (the name of the file to |
152 | be renamed), and \c{newfilename} (the new name to give the file). |
153 | |
421406a4 |
154 | Sometimes you will need to specify \I{spaces in filenames}file names |
155 | that \e{contain} spaces. In order to do this, you can surround |
156 | the file name with double quotes. This works equally well for |
157 | local file names and remote file names: |
3af97463 |
158 | |
159 | \c psftp> get "spacey file name.txt" "save it under this name.txt" |
160 | |
161 | The double quotes themselves will not appear as part of the file |
162 | names; they are removed by PSFTP and their only effect is to stop |
163 | the spaces inside them from acting as word separators. |
164 | |
165 | If you need to \e{use} a double quote (on some types of remote |
166 | system, such as Unix, you are allowed to use double quotes in file |
167 | names), you can do this by doubling it. This works both inside and |
168 | outside double quotes. For example, this command |
169 | |
170 | \c psftp> ren ""this"" "a file with ""quotes"" in it" |
171 | |
172 | will take a file whose current name is \c{"this"} (with a double |
173 | quote character at the beginning and the end) and rename it to a |
174 | file whose name is \c{a file with "quotes" in it}. |
175 | |
176 | (The one exception to the PSFTP quoting rules is the \c{!} command, |
177 | which passes its command line straight to Windows without splitting |
178 | it up into words at all. See \k{psftp-cmd-pling}.) |
179 | |
9d210cac |
180 | \S{psftp-wildcards} Wildcards in PSFTP |
181 | |
421406a4 |
182 | Several commands in PSFTP support \q{\i{wildcards}} to select multiple |
9d210cac |
183 | files. |
184 | |
185 | For \e{local} file specifications (such as the first argument to |
186 | \c{put}), wildcard rules for the local operating system are used. For |
187 | instance, PSFTP running on Windows might require the use of \c{*.*} |
188 | where PSFTP on Unix would need \c{*}. |
189 | |
190 | For \e{remote} file specifications (such as the first argument to |
421406a4 |
191 | \c{get}), PSFTP uses a standard wildcard syntax (similar to \i{POSIX} |
9d210cac |
192 | wildcards): |
193 | |
194 | \b \c{*} matches any sequence of characters (including a zero-length |
195 | sequence). |
196 | |
197 | \b \c{?} matches exactly one character. |
198 | |
199 | \b \c{[abc]} matches exactly one character which can be \cw{a}, |
200 | \cw{b}, or \cw{c}. |
201 | |
202 | \lcont{ |
203 | |
204 | \c{[a-z]} matches any character in the range \cw{a} to \cw{z}. |
205 | |
206 | \c{[^abc]} matches a single character that is \e{not} \cw{a}, \cw{b}, |
207 | or \cw{c}. |
208 | |
209 | Special cases: \c{[-a]} matches a literal hyphen (\cw{-}) or \cw{a}; |
210 | \c{[^-a]} matches all other characters. \c{[a^]} matches a literal |
211 | caret (\cw{^}) or \cw{a}. |
212 | |
213 | } |
214 | |
215 | \b \c{\\} (backslash) before any of the above characters (or itself) |
216 | removes that character's special meaning. |
217 | |
218 | A leading period (\cw{.}) on a filename is not treated specially, |
219 | unlike in some Unix contexts; \c{get *} will fetch all files, whether |
220 | or not they start with a leading period. |
221 | |
9a313f60 |
222 | \S{psftp-cmd-open} The \c{open} command: start a session |
223 | |
224 | If you started PSFTP by double-clicking in the GUI, or just by |
225 | typing \c{psftp} at the command line, you will need to open a |
226 | connection to an SFTP server before you can issue any other |
227 | commands (except \c{help} and \c{quit}). |
228 | |
229 | To create a connection, type \c{open host.name}, or if you need to |
230 | specify a user name as well you can type \c{open user@host.name}. |
231 | |
232 | Once you have issued this command, you will not be able to issue it |
233 | again, \e{even} if the command fails (for example, if you mistype |
234 | the host name or the connection times out). So if the connection is |
235 | not opened successfully, PSFTP will terminate immediately. |
236 | |
237 | \S{psftp-cmd-quit} The \c{quit} command: end your session |
238 | |
239 | When you have finished your session, type the command \c{quit} to |
9d210cac |
240 | close the connection, terminate PSFTP and return to the command line |
241 | (or just close the PSFTP console window if you started it from the |
242 | GUI). |
9a313f60 |
243 | |
244 | You can also use the \c{bye} and \c{exit} commands, which have |
245 | exactly the same effect. |
246 | |
9d210cac |
247 | \S{psftp-cmd-close} The \c{close} command: close your connection |
248 | |
249 | If you just want to close the network connection but keep PSFTP |
250 | running, you can use the \c{close} command. You can then use the |
251 | \c{open} command to open a new connection. |
252 | |
9a313f60 |
253 | \S{psftp-cmd-help} The \c{help} command: get quick online help |
254 | |
255 | If you type \c{help}, PSFTP will give a short list of the available |
256 | commands. |
257 | |
258 | If you type \c{help} with a command name - for example, \c{help get} |
259 | - then PSFTP will give a short piece of help on that particular |
260 | command. |
261 | |
262 | \S{psftp-cmd-cd} The \c{cd} and \c{pwd} commands: changing the |
421406a4 |
263 | remote \i{working directory} |
9a313f60 |
264 | |
265 | PSFTP maintains a notion of your \q{working directory} on the |
266 | server. This is the default directory that other commands will |
267 | operate on. For example, if you type \c{get filename.dat} then PSFTP |
3af97463 |
268 | will look for \c{filename.dat} in your remote working directory on |
269 | the server. |
9a313f60 |
270 | |
25d1ef43 |
271 | To change your remote working directory, use the \c{cd} command. If |
272 | you don't provide an argument, \c{cd} will return you to your home |
273 | directory on the server (more precisely, the remote directory you were |
274 | in at the start of the connection). |
275 | |
276 | To display your current remote working directory, type \c{pwd}. |
3af97463 |
277 | |
278 | \S{psftp-cmd-lcd} The \c{lcd} and \c{lpwd} commands: changing the |
421406a4 |
279 | local \i{working directory} |
3af97463 |
280 | |
281 | As well as having a working directory on the remote server, PSFTP |
282 | also has a working directory on your local machine (just like any |
283 | other Windows process). This is the default local directory that |
284 | other commands will operate on. For example, if you type \c{get |
285 | filename.dat} then PSFTP will save the resulting file as |
286 | \c{filename.dat} in your local working directory. |
287 | |
288 | To change your local working directory, use the \c{lcd} command. To |
289 | display your current local working directory, type \c{lpwd}. |
9a313f60 |
290 | |
291 | \S{psftp-cmd-get} The \c{get} command: fetch a file from the server |
292 | |
421406a4 |
293 | To \i{download a file} from the server and store it on your local PC, |
9a313f60 |
294 | you use the \c{get} command. |
295 | |
296 | In its simplest form, you just use this with a file name: |
297 | |
298 | \c get myfile.dat |
299 | |
300 | If you want to store the file locally under a different name, |
301 | specify the local file name after the remote one: |
302 | |
303 | \c get myfile.dat newname.dat |
304 | |
305 | This will fetch the file on the server called \c{myfile.dat}, but |
306 | will save it to your local machine under the name \c{newname.dat}. |
307 | |
421406a4 |
308 | To fetch an entire directory \i{recursive}ly, you can use the \c{-r} |
93e86a8b |
309 | option: |
310 | |
311 | \c get -r mydir |
312 | \c get -r mydir newname |
313 | |
314 | (If you want to fetch a file whose name starts with a hyphen, you |
315 | may have to use the \c{--} special argument, which stops \c{get} |
316 | from interpreting anything as a switch after it. For example, |
317 | \cq{get -- -silly-name-}.) |
318 | |
9a313f60 |
319 | \S{psftp-cmd-put} The \c{put} command: send a file to the server |
320 | |
421406a4 |
321 | To \i{upload a file} to the server from your local PC, you use the |
9a313f60 |
322 | \c{put} command. |
323 | |
324 | In its simplest form, you just use this with a file name: |
325 | |
326 | \c put myfile.dat |
327 | |
328 | If you want to store the file remotely under a different name, |
329 | specify the remote file name after the local one: |
330 | |
331 | \c put myfile.dat newname.dat |
332 | |
333 | This will send the local file called \c{myfile.dat}, but will store |
334 | it on the server under the name \c{newname.dat}. |
335 | |
421406a4 |
336 | To send an entire directory \i{recursive}ly, you can use the \c{-r} |
93e86a8b |
337 | option: |
338 | |
339 | \c put -r mydir |
340 | \c put -r mydir newname |
341 | |
342 | (If you want to send a file whose name starts with a hyphen, you may |
343 | have to use the \c{--} special argument, which stops \c{put} from |
344 | interpreting anything as a switch after it. For example, \cq{put -- |
345 | -silly-name-}.) |
346 | |
9c77ddf6 |
347 | \S{psftp-cmd-mgetput} The \c{mget} and \c{mput} commands: fetch or |
348 | send multiple files |
349 | |
350 | \c{mget} works almost exactly like \c{get}, except that it allows |
351 | you to specify more than one file to fetch at once. You can do this |
352 | in two ways: |
353 | |
354 | \b by giving two or more explicit file names (\cq{mget file1.txt |
355 | file2.txt}) |
356 | |
357 | \b by using a wildcard (\cq{mget *.txt}). |
358 | |
359 | Every argument to \c{mget} is treated as the name of a file to fetch |
360 | (unlike \c{get}, which will interpret at most one argument like |
361 | that, and a second argument will be treated as an alternative name |
421406a4 |
362 | under which to store the retrieved file), or a \i{wildcard} expression |
9c77ddf6 |
363 | matching more than one file. |
364 | |
9d210cac |
365 | The \c{-r} and \c{--} options from \c{get} are also available with |
366 | \c{mget}. |
367 | |
9c77ddf6 |
368 | \c{mput} is similar to \c{put}, with the same differences. |
369 | |
9a313f60 |
370 | \S{psftp-cmd-regetput} The \c{reget} and \c{reput} commands: |
421406a4 |
371 | \i{resuming file transfers} |
9a313f60 |
372 | |
373 | If a file transfer fails half way through, and you end up with half |
374 | the file stored on your disk, you can resume the file transfer using |
375 | the \c{reget} and \c{reput} commands. These work exactly like the |
376 | \c{get} and \c{put} commands, but they check for the presence of the |
377 | half-written destination file and start transferring from where the |
378 | last attempt left off. |
379 | |
380 | The syntax of \c{reget} and \c{reput} is exactly the same as the |
381 | syntax of \c{get} and \c{put}: |
382 | |
383 | \c reget myfile.dat |
384 | \c reget myfile.dat newname.dat |
9d210cac |
385 | \c reget -r mydir |
386 | |
387 | These commands are intended mainly for resuming interrupted transfers. |
388 | They assume that the remote file or directory structure has not |
389 | changed in any way; if there have been changes, you may end up with |
390 | corrupted files. In particular, the \c{-r} option will not pick up |
391 | changes to files or directories already transferred in full. |
9a313f60 |
392 | |
421406a4 |
393 | \S{psftp-cmd-dir} The \c{dir} command: \I{listing files}list remote files |
9a313f60 |
394 | |
395 | To list the files in your remote working directory, just type |
396 | \c{dir}. |
397 | |
398 | You can also list the contents of a different directory by typing |
399 | \c{dir} followed by the directory name: |
400 | |
401 | \c dir /home/fred |
402 | \c dir sources |
403 | |
3394416c |
404 | And you can list a subset of the contents of a directory by |
405 | providing a wildcard: |
406 | |
407 | \c dir /home/fred/*.txt |
408 | \c dir sources/*.c |
409 | |
9a313f60 |
410 | The \c{ls} command works exactly the same way as \c{dir}. |
411 | |
412 | \S{psftp-cmd-chmod} The \c{chmod} command: change permissions on |
413 | remote files |
414 | |
421406a4 |
415 | \I{changing permissions on files}PSFTP |
416 | allows you to modify the file permissions on files and |
c1b8799b |
417 | directories on the server. You do this using the \c{chmod} command, |
418 | which works very much like the Unix \c{chmod} command. |
9a313f60 |
419 | |
420 | The basic syntax is \c{chmod modes file}, where \c{modes} represents |
421 | a modification to the file permissions, and \c{file} is the filename |
c1b8799b |
422 | to modify. You can specify multiple files or wildcards. For example: |
9a313f60 |
423 | |
424 | \c chmod go-rwx,u+w privatefile |
c1b8799b |
425 | \c chmod a+r public* |
426 | \c chmod 640 groupfile1 groupfile2 |
9a313f60 |
427 | |
428 | The \c{modes} parameter can be a set of octal digits in the Unix |
429 | style. (If you don't know what this means, you probably don't want |
430 | to be using it!) Alternatively, it can be a list of permission |
431 | modifications, separated by commas. Each modification consists of: |
432 | |
433 | \b The people affected by the modification. This can be \c{u} (the |
434 | owning user), \c{g} (members of the owning group), or \c{o} |
435 | (everybody else - \q{others}), or some combination of those. It can |
436 | also be \c{a} (\q{all}) to affect everybody at once. |
437 | |
438 | \b A \c{+} or \c{-} sign, indicating whether permissions are to be |
439 | added or removed. |
440 | |
421406a4 |
441 | \b The actual permissions being added or removed. These can be |
442 | \I{read permission}\c{r} (permission to read the file), |
443 | \I{write permission}\c{w} (permission to write to the file), and |
444 | \I{execute permission}\c{x} (permission to execute the file, or in |
445 | the case of a directory, permission to access files within the |
446 | directory). |
9a313f60 |
447 | |
448 | So the above examples would do: |
449 | |
450 | \b The first example: \c{go-rwx} removes read, write and execute |
451 | permissions for members of the owning group and everybody else (so |
452 | the only permissions left are the ones for the file owner). \c{u+w} |
453 | adds write permission for the file owner. |
454 | |
c1b8799b |
455 | \b The second example: \c{a+r} adds read permission for everybody to |
456 | all files and directories starting with \q{public}. |
9a313f60 |
457 | |
458 | In addition to all this, there are a few extra special cases for |
421406a4 |
459 | \i{Unix} systems. On non-Unix systems these are unlikely to be useful: |
9a313f60 |
460 | |
461 | \b You can specify \c{u+s} and \c{u-s} to add or remove the Unix |
421406a4 |
462 | \i{set-user-ID bit}. This is typically only useful for special purposes; |
9a313f60 |
463 | refer to your Unix documentation if you're not sure about it. |
464 | |
465 | \b You can specify \c{g+s} and \c{g-s} to add or remove the Unix |
421406a4 |
466 | \i{set-group-ID bit}. On a file, this works similarly to the set-user-ID |
9a313f60 |
467 | bit (see your Unix documentation again); on a directory it ensures |
468 | that files created in the directory are accessible by members of the |
469 | group that owns the directory. |
470 | |
471 | \b You can specify \c{+t} and \c{-t} to add or remove the Unix |
421406a4 |
472 | \q{\i{sticky bit}}. When applied to a directory, this means that the |
9a313f60 |
473 | owner of a file in that directory can delete the file (whereas |
474 | normally only the owner of the \e{directory} would be allowed to). |
475 | |
476 | \S{psftp-cmd-del} The \c{del} command: delete remote files |
477 | |
421406a4 |
478 | To \I{deleting files}delete a file on the server, type \c{del} and |
479 | then the filename or filenames: |
9a313f60 |
480 | |
481 | \c del oldfile.dat |
c1b8799b |
482 | \c del file1.txt file2.txt |
483 | \c del *.o |
484 | |
485 | Files will be deleted without further prompting, even if multiple files |
486 | are specified. |
487 | |
488 | \c{del} will only delete files. You cannot use it to delete |
489 | directories; use \c{rmdir} for that. |
9a313f60 |
490 | |
491 | The \c{rm} command works exactly the same way as \c{del}. |
492 | |
493 | \S{psftp-cmd-mkdir} The \c{mkdir} command: create remote directories |
494 | |
421406a4 |
495 | To \i{create a directory} on the server, type \c{mkdir} and then the |
9a313f60 |
496 | directory name: |
497 | |
498 | \c mkdir newstuff |
499 | |
c1b8799b |
500 | You can specify multiple directories to create at once: |
501 | |
502 | \c mkdir dir1 dir2 dir3 |
503 | |
9a313f60 |
504 | \S{psftp-cmd-rmdir} The \c{rmdir} command: remove remote directories |
505 | |
421406a4 |
506 | To \i{remove a directory} on the server, type \c{rmdir} and then the |
c1b8799b |
507 | directory name or names: |
9a313f60 |
508 | |
509 | \c rmdir oldstuff |
c1b8799b |
510 | \c rmdir *.old ancient |
511 | |
512 | Directories will be deleted without further prompting, even if |
513 | multiple directories are specified. |
9a313f60 |
514 | |
515 | Most SFTP servers will probably refuse to remove a directory if the |
516 | directory has anything in it, so you will need to delete the |
517 | contents first. |
518 | |
421406a4 |
519 | \S{psftp-cmd-mv} The \c{mv} command: move and \i{rename remote files} |
c1b8799b |
520 | |
521 | To rename a single file on the server, type \c{mv}, then the current |
522 | file name, and then the new file name: |
523 | |
524 | \c mv oldfile newname |
525 | |
526 | You can also move the file into a different directory and change the |
527 | name: |
528 | |
529 | \c mv oldfile dir/newname |
9a313f60 |
530 | |
c1b8799b |
531 | To move one or more files into an existing subdirectory, specify the |
532 | files (using wildcards if desired), and then the destination |
533 | directory: |
9a313f60 |
534 | |
c1b8799b |
535 | \c mv file dir |
536 | \c mv file1 dir1/file2 dir2 |
537 | \c mv *.c *.h .. |
9a313f60 |
538 | |
c1b8799b |
539 | The \c{rename} and \c{ren} commands work exactly the same way as |
540 | \c{mv}. |
eb4f8180 |
541 | |
421406a4 |
542 | \S{psftp-cmd-pling} The \c{!} command: run a \i{local Windows command} |
3af97463 |
543 | |
544 | You can run local Windows commands using the \c{!} command. This is |
545 | the only PSFTP command that is not subject to the command quoting |
546 | rules given in \k{psftp-quoting}. If any command line begins with |
547 | the \c{!} character, then the rest of the line will be passed |
548 | straight to Windows without further translation. |
549 | |
550 | For example, if you want to move an existing copy of a file out of |
551 | the way before downloading an updated version, you might type: |
552 | |
553 | \c psftp> !ren myfile.dat myfile.bak |
554 | \c psftp> get myfile.dat |
555 | |
556 | using the Windows \c{ren} command to rename files on your local PC. |
557 | |
421406a4 |
558 | \H{psftp-pubkey} Using \i{public key authentication} with PSFTP |
eb4f8180 |
559 | |
560 | Like PuTTY, PSFTP can authenticate using a public key instead of a |
870239d3 |
561 | password. There are three ways you can do this. |
eb4f8180 |
562 | |
563 | Firstly, PSFTP can use PuTTY saved sessions in place of hostnames. |
564 | So you might do this: |
565 | |
566 | \b Run PuTTY, and create a PuTTY saved session (see |
567 | \k{config-saving}) which specifies your private key file (see |
568 | \k{config-ssh-privkey}). You will probably also want to specify a |
569 | username to log in as (see \k{config-username}). |
570 | |
571 | \b In PSFTP, you can now use the name of the session instead of a |
572 | hostname: type \c{psftp sessionname}, where \c{sessionname} is |
573 | replaced by the name of your saved session. |
574 | |
870239d3 |
575 | Secondly, you can supply the name of a private key file on the command |
576 | line, with the \c{-i} option. See \k{using-cmdline-identity} for more |
577 | information. |
578 | |
579 | Thirdly, PSFTP will attempt to authenticate using Pageant if Pageant |
eb4f8180 |
580 | is running (see \k{pageant}). So you would do this: |
581 | |
582 | \b Ensure Pageant is running, and has your private key stored in it. |
583 | |
584 | \b Specify a user and host name to PSFTP as normal. PSFTP will |
585 | automatically detect Pageant and try to use the keys within it. |
586 | |
587 | For more general information on public-key authentication, see |
588 | \k{pubkey}. |