~mdw
/
sgt
/
putty
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Support underline and vertical-line cursors as well as block.
[sgt/putty]
/
doc
/
pscp.but
diff --git
a/doc/pscp.but
b/doc/pscp.but
index
ad0144c
..
1a322f6
100644
(file)
--- a/
doc/pscp.but
+++ b/
doc/pscp.but
@@
-1,4
+1,4
@@
-\versionid $Id: pscp.but,v 1.2
1 2002/08/07 19:20:06 simon
Exp $
+\versionid $Id: pscp.but,v 1.2
2 2002/09/11 17:30:36 jacob
Exp $
\#FIXME: Need examples
\#FIXME: Need examples
@@
-41,17
+41,24
@@
use PSCP:
\c Z:\owendadmin>pscp
\c PuTTY Secure Copy client
\c Z:\owendadmin>pscp
\c PuTTY Secure Copy client
-\c Release 0.5
0
+\c Release 0.5
3
\c Usage: pscp [options] [user@]host:source target
\c Usage: pscp [options] [user@]host:source target
-\c pscp [options] source [source...] [user@]host:target
-\c pscp [options] -ls user@host:filespec
+\c
pscp [options] source [source...] [user@]host:target
+\c
pscp [options] -ls user@host:filespec
\c Options:
\c -p preserve file attributes
\c -q quiet, don't show statistics
\c -r copy directories recursively
\c -v show verbose messages
\c Options:
\c -p preserve file attributes
\c -q quiet, don't show statistics
\c -r copy directories recursively
\c -v show verbose messages
+\c -load sessname Load settings from saved session
\c -P port connect to specified port
\c -P port connect to specified port
+\c -l user connect with specified username
\c -pw passw login with specified password
\c -pw passw login with specified password
+\c -1 -2 force use of particular SSH protocol version
+\c -C enable compression
+\c -i key private key file for authentication
+\c -batch disable all interactive prompts
+\c -unsafe allow server-side wildcards (DANGEROUS)
(PSCP's interface is much like the Unix \c{scp} command, if you're
familiar with that.)
(PSCP's interface is much like the Unix \c{scp} command, if you're
familiar with that.)
@@
-226,7
+233,7
@@
using code such as this:
\S{pscp-pubkey} Using public key authentication with PSCP
Like PuTTY, PSCP can authenticate using a public key instead of a
\S{pscp-pubkey} Using public key authentication with PSCP
Like PuTTY, PSCP can authenticate using a public key instead of a
-password. There are t
wo
ways you can do this.
+password. There are t
hree
ways you can do this.
Firstly, PSCP can use PuTTY saved sessions in place of hostnames
(see \k{pscp-usage-basics-host}). So you would do this:
Firstly, PSCP can use PuTTY saved sessions in place of hostnames
(see \k{pscp-usage-basics-host}). So you would do this:
@@
-240,7
+247,11
@@
username to log in as (see \k{config-username}).
hostname: type \c{pscp sessionname:file localfile}, where
\c{sessionname} is replaced by the name of your saved session.
hostname: type \c{pscp sessionname:file localfile}, where
\c{sessionname} is replaced by the name of your saved session.
-Secondly, PSCP will attempt to authenticate using Pageant if Pageant
+Secondly, you can supply the name of a private key file on the command
+line, with the \c{-i} option. See \k{using-cmdline-identity} for more
+information.
+
+Thirdly, PSCP will attempt to authenticate using Pageant if Pageant
is running (see \k{pageant}). So you would do this:
\b Ensure Pageant is running, and has your private key stored in it.
is running (see \k{pageant}). So you would do this:
\b Ensure Pageant is running, and has your private key stored in it.