+\S2{pscp-usage-options-P}\c{-P port} connect to specified \i{port}
+
+If the \c{host} you specify is a saved session, PSCP uses any port
+number specified in that saved session. If not, PSCP uses the default
+SSH port, 22. The \c{-P} option allows you specify the port number to
+connect to for PSCP's SSH connection.
+
+\S2{pscp-usage-options-pw}\c{-pw passw} login with specified \i{password}
+
+If a password is required to connect to the \c{host}, PSCP will
+interactively prompt you for it. However, this may not always be
+appropriate. If you are running PSCP as part of some automated job,
+it will not be possible to enter a password by hand. The \c{-pw}
+option to PSCP lets you specify the password to use on the command
+line.
+
+Since specifying passwords in scripts is a bad idea for security
+reasons, you might want instead to consider using public-key
+authentication; see \k{pscp-pubkey}.
+
+\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.
+
+Firstly, PSCP can use PuTTY saved sessions in place of hostnames
+(see \k{pscp-usage-basics-host}). So you would do this:
+
+\b Run PuTTY, and create a PuTTY saved session (see
+\k{config-saving}) which specifies your private key file (see
+\k{config-auth}). You will probably also want to specify a username
+to log in as (see \k{config-username}).
+
+\b In PSCP, you can now use the name of the session instead of a
+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
+is running (see \k{pageant}). So you would do this: