1 \cfg{man-identity}{plink}{1}{2004-03-24}{PuTTY tool suite}{PuTTY tool suite}
3 \H{plink-manpage} Man page for Plink
5 \S{plink-manpage-name} NAME
7 \cw{plink} \- PuTTY link, command line network connection tool
9 \S{plink-manpage-synopsis} SYNOPSIS
11 \c plink [options] [user@]host [command]
12 \e bbbbb iiiiiii iiiib iiii iiiiiii
14 \S{plink-manpage-description} DESCRIPTION
16 \cw{plink} is a network connection tool supporting several protocols.
18 \S{plink-manpage-options} OPTIONS
20 The command-line options supported by \cw{plink} are:
24 \dd Show version information and exit.
28 \dd Display the fingerprints of the PuTTY PGP Master Keys and exit,
29 to aid in verifying new files released by the PuTTY team.
33 \dd Show verbose messages.
35 \dt \cw{-load} \e{session}
37 \dd Load settings from saved session.
41 \dd Force use of SSH protocol (default).
45 \dd Force use of Telnet protocol.
49 \dd Force use of rlogin protocol.
57 \dd Force serial mode.
61 \dd Connect to port \e{port}.
65 \dd Set remote username to \e{user}.
69 \dd Read remote command(s) from local file \e{path}.
73 \dd Disable interactive prompts.
75 \dt \cw{-pw} \e{password}
77 \dd Set remote password to \e{password}. \e{CAUTION:} this will likely
78 make the password visible to other users of the local machine (via
79 commands such as \q{\c{w}}).
81 \dt \cw{\-L} \cw{[}\e{srcaddr}\cw{:]}\e{srcport}\cw{:}\e{desthost}\cw{:}\e{destport}
83 \dd Set up a local port forwarding: listen on \e{srcport} (or
84 \e{srcaddr}:\e{srcport} if specified), and forward any connections
85 over the SSH connection to the destination address
86 \e{desthost}:\e{destport}. Only works in SSH.
88 \dt \cw{\-R} \cw{[}\e{srcaddr}\cw{:]}\e{srcport}\cw{:}\e{desthost}\cw{:}\e{destport}
90 \dd Set up a remote port forwarding: ask the SSH server to listen on
91 \e{srcport} (or \e{srcaddr}:\e{srcport} if specified), and to
92 forward any connections back over the SSH connection where the
93 client will pass them on to the destination address
94 \e{desthost}:\e{destport}. Only works in SSH.
96 \dt \cw{\-D} [\e{srcaddr}:]\e{srcport}
98 \dd Set up dynamic port forwarding. The client listens on
99 \e{srcport} (or \e{srcaddr}:\e{srcport} if specified), and
100 implements a SOCKS server. So you can point SOCKS-aware applications
101 at this port and they will automatically use the SSH connection to
102 tunnel all their connections. Only works in SSH.
106 \dd Enable X11 forwarding.
110 \dd Disable X11 forwarding (default).
114 \dd Enable agent forwarding.
118 \dd Disable agent forwarding (default).
122 \dd Enable pty allocation (default if a command is NOT specified).
126 \dd Disable pty allocation (default if a command is specified).
130 \dd Force use of SSH protocol version 1.
134 \dd Force use of SSH protocol version 2.
138 \dd Enable SSH compression.
140 \dt \cw{-i} \e{keyfile}
142 \dd Private key file for user authentication. For SSH-2 keys, this key
143 file must be in PuTTY's PPK format, not OpenSSH's format or anyone
146 \lcont{ If you are using an authentication agent, you can also specify
147 a \e{public} key here (in RFC 4716 or OpenSSH format), to identify
148 which of the agent's keys to use. }
150 \dt \cw{\-hostkey} \e{key}
152 \dd Specify an acceptable host public key. This option may be specified
153 multiple times; each key can be either a fingerprint (\cw{99:aa:bb:...}) or
154 a base64-encoded blob in OpenSSH's one-line format.
156 \lcont{ Specifying this option overrides automated host key
157 management; \e{only} the key(s) specified on the command-line will be
158 accepted (unless a saved session also overrides host keys, in which
159 case those will be added to), and the host key cache will not be
164 \dd Remote command is SSH subsystem (SSH-2 only).
168 \dd Don't start a remote command or shell at all (SSH-2 only).
170 \dt \cw{\-sercfg} \e{configuration-string}
172 \dd Specify the configuration parameters for the serial port, in
173 \cw{-serial} mode. \e{configuration-string} should be a
174 comma-separated list of configuration parameters as follows:
178 \b Any single digit from 5 to 9 sets the number of data bits.
180 \b \cq{1}, \cq{1.5} or \cq{2} sets the number of stop bits.
182 \b Any other numeric string is interpreted as a baud rate.
184 \b A single lower-case letter specifies the parity: \cq{n} for none,
185 \cq{o} for odd, \cq{e} for even, \cq{m} for mark and \cq{s} for space.
187 \b A single upper-case letter specifies the flow control: \cq{N} for
188 none, \cq{X} for XON/XOFF, \cq{R} for RTS/CTS and \cq{D} for
193 \dt \cw{\-sshlog} \e{logfile}
195 \dt \cw{\-sshrawlog} \e{logfile}
197 \dd For SSH connections, these options make \cw{plink} log protocol
198 details to a file. (Some of these may be sensitive, although by default
199 an effort is made to suppress obvious passwords.)
202 \cw{\-sshlog} logs decoded SSH packets and other events (those that
203 \cw{\-v} would print). \cw{\-sshrawlog} additionally logs the raw
204 encrypted packet data.
207 \S{plink-manpage-more-information} MORE INFORMATION
209 For more information on plink, it's probably best to go and look at
210 the manual on the PuTTY web page:
212 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/}
214 \S{plink-manpage-bugs} BUGS
216 This man page isn't terribly complete. See the above web link for
217 better documentation.