nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 19:42:48 -05:00
Code Issues Projects Releases Wiki Activity

Updated usage messages for command-line utilities to reflect new options.

Browse Source 
Updated manual to reflect reality (e.g. usage messages, '-p port' not actually
  implemented, sprinkle references to '-i keyfile').
(I've put "Release 0.53" in the messages; let's hope this doesn't cause a
  flood of "where is 0.53?" email.)
I don't guarantee that the result is entirely sane and sensible in all
  respects, but it is at least consistent.

[originally from svn r1951]
This commit is contained in:
Jacob Nevins
2002-09-11 17:30:36 +00:00
parent 3711af9a53
commit c7fa2f6183
8 changed files with 81 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
doc/pscp.but
View File

@ -1,4 +1,4 @@
\versionid $Id: pscp.but,v 1.21 2002/08/07 19:20:06 simon Exp $
\versionid $Id: pscp.but,v 1.22 2002/09/11 17:30:36 jacob Exp $
\#FIXME: Need examples
@ -41,17 +41,24 @@ use PSCP:
\c Z:\owendadmin>pscp
\c PuTTY Secure Copy client
\c Release 0.50
\c Release 0.53
\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 -load sessname Load settings from saved session
\c -P port connect to specified port
\c -l user connect with specified username
\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.)
@ -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
password. There are two ways you can do this.
password. There are three 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:
@ -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.
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.