man-putty.but 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350
  1. \cfg{man-identity}{putty}{1}{2004-03-24}{PuTTY tool suite}{PuTTY tool suite}
  2. \H{putty-manpage} Man page for PuTTY
  3. \S{putty-manpage-name} NAME
  4. \cw{putty} - GUI SSH, Telnet, Rlogin, and SUPDUP client for X
  5. \S{putty-manpage-synopsis} SYNOPSIS
  6. \c putty [ options ] [ host ]
  7. \e bbbbb iiiiiii iiii
  8. \S{putty-manpage-description} DESCRIPTION
  9. \cw{putty} is a graphical SSH, Telnet, Rlogin, and SUPDUP client for
  10. X. It is a direct port of the Windows SSH client of the same name.
  11. \S{putty-manpage-options} OPTIONS
  12. The command-line options supported by \cw{putty} are:
  13. \dt \cw{\-\-display} \e{display\-name}
  14. \dd Specify the X display on which to open \cw{putty}. (Note this
  15. option has a double minus sign, even though none of the others do.
  16. This is because this option is supplied automatically by GTK.
  17. Sorry.)
  18. \dt \cw{\-fn} \e{font-name}
  19. \dd Specify the font to use for normal text displayed in the terminal.
  20. For example, \cw{\-fn\_fixed}, \cw{\-fn\_"Monospace\_12"}.
  21. \dt \cw{\-fb} \e{font-name}
  22. \dd Specify the font to use for bold text displayed in the terminal.
  23. If the \cw{BoldAsColour} resource is set to 1 (the default), bold
  24. text will be displayed in different colours instead of a different
  25. font, so this option will be ignored. If \cw{BoldAsColour} is set to
  26. 0 or 2 and you do not specify a bold font, \cw{putty} will overprint the
  27. normal font to make it look bolder.
  28. \dt \cw{\-fw} \e{font-name}
  29. \dd Specify the font to use for double-width characters (typically
  30. Chinese, Japanese and Korean text) displayed in the terminal.
  31. \dt \cw{\-fwb} \e{font-name}
  32. \dd Specify the font to use for bold double-width characters
  33. (typically Chinese, Japanese and Korean text). Like \cw{-fb}, this
  34. will be ignored unless the \cw{BoldAsColour} resource is set to 0 or 2.
  35. \dt \cw{\-geometry} \e{geometry}
  36. \dd Specify the size of the terminal, in rows and columns of text.
  37. See \cw{X}(\e{7}) for more information on the syntax of geometry
  38. specifications.
  39. \dt \cw{\-sl} \e{lines}
  40. \dd Specify the number of lines of scrollback to save off the top of the
  41. terminal.
  42. \dt \cw{\-fg} \e{colour}
  43. \dd Specify the foreground colour to use for normal text.
  44. \dt \cw{\-bg} \e{colour}
  45. \dd Specify the background colour to use for normal text.
  46. \dt \cw{\-bfg} \e{colour}
  47. \dd Specify the foreground colour to use for bold text, if the
  48. \cw{BoldAsColour} resource is set to 1 (the default) or 2.
  49. \dt \cw{\-bbg} \e{colour}
  50. \dd Specify the foreground colour to use for bold reverse-video
  51. text, if the \cw{BoldAsColour} resource is set to 1 (the default) or 2.
  52. (This colour is best thought of as the bold version of the
  53. background colour; so it only appears when text is displayed \e{in}
  54. the background colour.)
  55. \dt \cw{\-cfg} \e{colour}
  56. \dd Specify the foreground colour to use for text covered by the cursor.
  57. \dt \cw{\-cbg} \e{colour}
  58. \dd Specify the background colour to use for text covered by the cursor.
  59. In other words, this is the main colour of the cursor.
  60. \dt \cw{\-title} \e{title}
  61. \dd Specify the initial title of the terminal window. (This can be
  62. changed under control of the server.)
  63. \dt \cw{\-sb\-} or \cw{+sb}
  64. \dd Tells \cw{putty} not to display a scroll bar.
  65. \dt \cw{\-sb}
  66. \dd Tells \cw{putty} to display a scroll bar: this is the opposite of
  67. \cw{\-sb\-}. This is the default option: you will probably only need
  68. to specify it explicitly if you have changed the default using the
  69. \cw{ScrollBar} resource.
  70. \dt \cw{\-log} \e{logfile}, \cw{\-sessionlog} \e{logfile}
  71. \dd This option makes \cw{putty} log all the terminal output to a file
  72. as well as displaying it in the terminal.
  73. \dt \cw{\-sshlog} \e{logfile}
  74. \dt \cw{\-sshrawlog} \e{logfile}
  75. \dd For SSH connections, these options make \cw{putty} log protocol
  76. details to a file. (Some of these may be sensitive, although by default
  77. an effort is made to suppress obvious passwords.)
  78. \lcont{
  79. \cw{\-sshlog} logs decoded SSH packets and other events (those that
  80. \cw{\-v} would print). \cw{\-sshrawlog} additionally logs the raw
  81. encrypted packet data.
  82. }
  83. \dt \cw{\-logoverwrite}
  84. \dd If \cw{putty} is configured to write to a log file that already exists,
  85. discard the existing file.
  86. \dt \cw{\-logappend}
  87. \dd If \cw{putty} is configured to write to a log file that already exists,
  88. append new log data to the existing file.
  89. \dt \cw{\-cs} \e{charset}
  90. \dd This option specifies the character set in which \cw{putty}
  91. should assume the session is operating. This character set will be
  92. used to interpret all the data received from the session, and all
  93. input you type or paste into \cw{putty} will be converted into
  94. this character set before being sent to the session.
  95. \lcont{ Any character set name which is valid in a MIME header (and
  96. supported by \cw{putty}) should be valid here (examples are
  97. \q{\cw{ISO-8859-1}}, \q{\cw{windows-1252}} or \q{\cw{UTF-8}}). Also,
  98. any character encoding which is valid in an X logical font
  99. description should be valid (\q{\cw{ibm-cp437}}, for example).
  100. \cw{putty}'s default behaviour is to use the same character
  101. encoding as its primary font. If you supply a Unicode
  102. (\cw{iso10646-1}) font, it will default to the UTF-8 character set.
  103. Character set names are case-insensitive.
  104. }
  105. \dt \cw{\-nethack}
  106. \dd Tells \cw{putty} to enable NetHack keypad mode, in which the
  107. numeric keypad generates the NetHack \c{hjklyubn} direction keys.
  108. This enables you to play NetHack with the numeric keypad without
  109. having to use the NetHack \c{number_pad} option (which requires you
  110. to press \q{\cw{n}} before any repeat count). So you can move with
  111. the numeric keypad, and enter repeat counts with the normal number
  112. keys.
  113. \dt \cw{\-help}, \cw{\-\-help}
  114. \dd Display a message summarizing the available options.
  115. \dt \cw{\-pgpfp}
  116. \dd Display the fingerprints of the PuTTY PGP Master Keys, to aid
  117. in verifying new files released by the PuTTY team.
  118. \dt \cw{\-load} \e{session}
  119. \dd Load a saved session by name. This allows you to run a saved session
  120. straight from the command line without having to go through the
  121. configuration box first.
  122. \dt \cw{\-ssh}, \cw{\-telnet}, \cw{\-rlogin}, \cw{\-supdup}, \cw{\-raw},
  123. \cw{-ssh-connection}, \cw{\-serial}
  124. \dd Select the protocol \cw{putty} will use to make the connection.
  125. \dt \cw{\-proxycmd} \e{command}
  126. \dd Instead of making a TCP connection, use \e{command} as a proxy;
  127. network traffic will be redirected to the standard input and output
  128. of \e{command}. \e{command} must be a single word, so is likely to
  129. need quoting by the shell.
  130. \lcont{
  131. The special strings \cw{%host} and \cw{%port} in \e{command} will be
  132. replaced by the hostname and port number you want to connect to; to get
  133. a literal \c{%} sign, enter \c{%%}.
  134. Backslash escapes are also supported, such as sequences like \c{\\n}
  135. being replaced by a literal newline; to get a literal backslash,
  136. enter \c{\\\\}. (Further escaping may be required by the shell.)
  137. (See the main PuTTY manual for full details of the supported \cw{%}-
  138. and backslash-delimited tokens, although most of them are probably not
  139. very useful in this context.)
  140. }
  141. \dt \cw{\-l} \e{username}
  142. \dd Specify the username to use when logging in to the server.
  143. \dt \cw{\-L} \cw{[}\e{srcaddr}\cw{:]}\e{srcport}\cw{:}\e{desthost}\cw{:}\e{destport}
  144. \dd Set up a local port forwarding: listen on \e{srcport} (or
  145. \e{srcaddr}:\e{srcport} if specified), and forward any connections
  146. over the SSH connection to the destination address
  147. \e{desthost}:\e{destport}. Only works in SSH.
  148. \dt \cw{\-R} \cw{[}\e{srcaddr}\cw{:]}\e{srcport}\cw{:}\e{desthost}\cw{:}\e{destport}
  149. \dd Set up a remote port forwarding: ask the SSH server to listen on
  150. \e{srcport} (or \e{srcaddr}:\e{srcport} if specified), and to
  151. forward any connections back over the SSH connection where the
  152. client will pass them on to the destination address
  153. \e{desthost}:\e{destport}. Only works in SSH.
  154. \dt \cw{\-D} [\e{srcaddr}:]\e{srcport}
  155. \dd Set up dynamic port forwarding. The client listens on
  156. \e{srcport} (or \e{srcaddr}:\e{srcport} if specified), and
  157. implements a SOCKS server. So you can point SOCKS-aware applications
  158. at this port and they will automatically use the SSH connection to
  159. tunnel all their connections. Only works in SSH.
  160. \dt \cw{\-P} \e{port}
  161. \dd Specify the port to connect to the server on.
  162. \dt \cw{\-A}, \cw{\-a}
  163. \dd Enable (\cw{\-A}) or disable (\cw{\-a}) SSH agent forwarding.
  164. Currently this only works with OpenSSH and SSH-1.
  165. \dt \cw{\-X}, \cw{\-x}
  166. \dd Enable (\cw{\-X}) or disable (\cw{\-x}) X11 forwarding.
  167. \dt \cw{\-T}, \cw{\-t}
  168. \dd Enable (\cw{\-t}) or disable (\cw{\-T}) the allocation of a
  169. pseudo-terminal at the server end.
  170. \dt \cw{\-C}
  171. \dd Enable zlib-style compression on the connection.
  172. \dt \cw{\-1}, \cw{\-2}
  173. \dd Select SSH protocol version 1 or 2.
  174. \dt \cw{-4}, \cw{-6}
  175. \dd Force use of IPv4 or IPv6 for network connections.
  176. \dt \cw{\-i} \e{keyfile}
  177. \dd Private key file for user authentication. For SSH-2 keys, this key
  178. file must be in PuTTY's PPK format, not OpenSSH's format or anyone
  179. else's.
  180. \lcont{ If you are using an authentication agent, you can also specify
  181. a \e{public} key here (in RFC 4716 or OpenSSH format), to identify
  182. which of the agent's keys to use. }
  183. \dt \cw{\-noagent}
  184. \dd Don't try to use an authentication agent for local authentication.
  185. (This doesn't affect agent forwarding.)
  186. \dt \cw{\-agent}
  187. \dd Allow use of an authentication agent. (This option is only necessary
  188. to override a setting in a saved session.)
  189. \dt \cw{\-no\-trivial\-auth}
  190. \dd Disconnect from any SSH server which accepts authentication without
  191. ever having asked for any kind of password or signature or token. (You
  192. might want to enable this for a server you always expect to challenge
  193. you, for instance to ensure you don't accidentally type your key file's
  194. passphrase into a compromised server spoofing PuTTY's passphrase
  195. prompt.)
  196. \dt \cw{\-hostkey} \e{key}
  197. \dd Specify an acceptable host public key. This option may be specified
  198. multiple times; each key can be either a fingerprint (\cw{SHA256:AbCdE...},
  199. \cw{99:aa:bb:...}, etc) or a base64-encoded blob in OpenSSH's one-line
  200. format.
  201. \lcont{ Specifying this option overrides automated host key
  202. management; \e{only} the key(s) specified on the command-line will be
  203. accepted (unless a saved session also overrides host keys, in which
  204. case those will be added to), and the host key cache will not be
  205. written. }
  206. \dt \cw{\-sercfg} \e{configuration-string}
  207. \dd Specify the configuration parameters for the serial port, in
  208. \cw{-serial} mode. \e{configuration-string} should be a
  209. comma-separated list of configuration parameters as follows:
  210. \lcont{
  211. \b Any single digit from 5 to 9 sets the number of data bits.
  212. \b \cq{1}, \cq{1.5} or \cq{2} sets the number of stop bits.
  213. \b Any other numeric string is interpreted as a baud rate.
  214. \b A single lower-case letter specifies the parity: \cq{n} for none,
  215. \cq{o} for odd, \cq{e} for even, \cq{m} for mark and \cq{s} for space.
  216. \b A single upper-case letter specifies the flow control: \cq{N} for
  217. none, \cq{X} for XON/XOFF, \cq{R} for RTS/CTS and \cq{D} for
  218. DSR/DTR.
  219. }
  220. \S{putty-manpage-saved-sessions} SAVED SESSIONS
  221. Saved sessions are stored in a \cw{.putty/sessions} subdirectory in
  222. your home directory.
  223. \S{putty-manpage-more-information} MORE INFORMATION
  224. For more information on PuTTY, it's probably best to go and look at
  225. the manual on the web page:
  226. \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
  227. \S{putty-manpage-bugs} BUGS
  228. This man page isn't terribly complete.