You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Xvnc.man 14KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391
  1. .TH Xvnc 1 "" "TigerVNC" "Virtual Network Computing"
  2. .SH NAME
  3. Xvnc \- the X VNC server
  4. .SH SYNOPSIS
  5. .B Xvnc
  6. .RI [ options ]
  7. .RI : display#
  8. .SH DESCRIPTION
  9. .B Xvnc
  10. is the X VNC (Virtual Network Computing) server. It is based on a standard X
  11. server, but it has a "virtual" screen rather than a physical one. X
  12. applications display themselves on it as if it were a normal X display, but
  13. they can only be accessed via a VNC viewer - see \fBvncviewer\fP(1).
  14. So Xvnc is really two servers in one. To the applications it is an X server,
  15. and to the remote VNC users it is a VNC server. By convention we have arranged
  16. that the VNC server display number will be the same as the X server display
  17. number, which means you can use eg. snoopy:2 to refer to display 2 on machine
  18. "snoopy" in both the X world and the VNC world.
  19. The best way of starting \fBXvnc\fP is via \fBvncsession\fP. This sets up the
  20. environment appropriately and starts a desktop environment. See the manual
  21. page for \fBvncsession\fP(8) for more information.
  22. .SH OPTIONS
  23. .B Xvnc
  24. takes lots of options - running \fBXvnc -help\fP gives a list. Many of these
  25. are standard X server options, which are described in the \fBXserver\fP(1)
  26. manual page. In addition to options which can only be set via the
  27. command-line, there are also "parameters" which can be set both via the
  28. command-line and through the \fBvncconfig\fP(1) program.
  29. .TP
  30. .B \-geometry \fIwidth\fPx\fIheight\fP
  31. Specify the size of the desktop to be created. Default is 1024x768.
  32. .
  33. .TP
  34. .B \-depth \fIdepth\fP
  35. Specify the pixel depth in bits of the desktop to be created. Default is 24,
  36. other possible values are 16 and 32. Anything else is likely to cause strange
  37. behaviour by applications and may prevent the server from starting at all.
  38. .
  39. .TP
  40. .B \-pixelformat \fIformat\fP
  41. Specify pixel format for server to use (BGRnnn or RGBnnn). The default for
  42. depth 16 is RGB565 and for depth 24 and 32 is RGB888.
  43. .
  44. .TP
  45. .B \-interface \fIIP address\fP
  46. Listen on interface. By default Xvnc listens on all available interfaces.
  47. .
  48. .TP
  49. .B \-inetd
  50. This significantly changes Xvnc's behaviour so that it can be launched from
  51. inetd. See the section below on usage with inetd.
  52. .
  53. .TP
  54. .B \-help
  55. List all the options and parameters
  56. .SH PARAMETERS
  57. VNC parameters can be set both via the command-line and through the
  58. \fBvncconfig\fP(1) program, and with a VNC-enabled Xorg server via Options
  59. entries in the xorg.conf file.
  60. Parameters can be turned on with -\fIparam\fP or off with
  61. -\fIparam\fP=0. Parameters which take a value can be specified as
  62. -\fIparam\fP \fIvalue\fP. Other valid forms are \fIparam\fP\fB=\fP\fIvalue\fP
  63. -\fIparam\fP=\fIvalue\fP --\fIparam\fP=\fIvalue\fP. Parameter names are
  64. case-insensitive.
  65. .TP
  66. .B \-desktop \fIdesktop-name\fP
  67. Each desktop has a name which may be displayed by the viewer. It defaults to
  68. "x11".
  69. .
  70. .TP
  71. .B \-rfbport \fIport\fP
  72. Specifies the TCP port on which Xvnc listens for connections from viewers (the
  73. protocol used in VNC is called RFB - "remote framebuffer"). The default is
  74. 5900 plus the display number.
  75. .
  76. .TP
  77. .B \-UseIPv4
  78. Use IPv4 for incoming and outgoing connections. Default is on.
  79. .
  80. .TP
  81. .B \-UseIPv6
  82. Use IPv6 for incoming and outgoing connections. Default is on.
  83. .
  84. .TP
  85. .B \-rfbunixpath \fIpath\fP
  86. Specifies the path of a Unix domain socket on which Xvnc listens for
  87. connections from viewers, instead of listening on a TCP port.
  88. .
  89. .TP
  90. .B \-rfbunixmode \fImode\fP
  91. Specifies the mode of the Unix domain socket. The default is 0600.
  92. .
  93. .TP
  94. .B \-rfbauth \fIpasswd-file\fP, \-PasswordFile \fIpasswd-file\fP
  95. Password file for VNC authentication. There is no default, you should
  96. specify the password file explicitly. Password file should be created with
  97. the \fBvncpasswd\fP(1) utility. The file is accessed each time a connection
  98. comes in, so it can be changed on the fly.
  99. .
  100. .TP
  101. .B \-AcceptCutText
  102. Accept clipboard updates from clients. Default is on.
  103. .
  104. .TP
  105. .B \-MaxCutText \fIbytes\fP
  106. The maximum size of a clipboard update that will be accepted from a client.
  107. Default is \fB262144\fP.
  108. .
  109. .TP
  110. .B \-SendCutText
  111. Send clipboard changes to clients. Default is on.
  112. .
  113. .TP
  114. .B \-SendPrimary
  115. Send the primary selection and cut buffer to the server as well as the
  116. clipboard selection. Default is on.
  117. .
  118. .TP
  119. .B \-AcceptPointerEvents
  120. Accept pointer press and release events from clients. Default is on.
  121. .
  122. .TP
  123. .B \-AcceptKeyEvents
  124. Accept key press and release events from clients. Default is on.
  125. .
  126. .TP
  127. .B \-AcceptSetDesktopSize
  128. Accept requests to resize the size of the desktop. Default is on.
  129. .
  130. .TP
  131. .B \-DisconnectClients
  132. Disconnect existing clients if an incoming connection is non-shared. Default is
  133. on. If \fBDisconnectClients\fP is false, then a new non-shared connection will
  134. be refused while there is a client active. When combined with
  135. \fBNeverShared\fP this means only one client is allowed at a time.
  136. .
  137. .TP
  138. .B \-NeverShared
  139. Never treat incoming connections as shared, regardless of the client-specified
  140. setting. Default is off.
  141. .
  142. .TP
  143. .B \-AlwaysShared
  144. Always treat incoming connections as shared, regardless of the client-specified
  145. setting. Default is off.
  146. .
  147. .TP
  148. .B \-Protocol3.3
  149. Always use protocol version 3.3 for backwards compatibility with badly-behaved
  150. clients. Default is off.
  151. .
  152. .TP
  153. .B \-FrameRate \fIfps\fP
  154. The maximum number of updates per second sent to each client. If the screen
  155. updates any faster then those changes will be aggregated and sent in a single
  156. update to the client. Note that this only controls the maximum rate and a
  157. client may get a lower rate when resources are limited. Default is \fB60\fP.
  158. .
  159. .TP
  160. .B \-CompareFB \fImode\fP
  161. Perform pixel comparison on framebuffer to reduce unnecessary updates. Can
  162. be either \fB0\fP (off), \fB1\fP (always) or \fB2\fP (auto). Default is
  163. \fB2\fP.
  164. .
  165. .TP
  166. .B \-ZlibLevel \fIlevel\fP
  167. Zlib compression level for ZRLE encoding (it does not affect Tight encoding).
  168. Acceptable values are between 0 and 9. Default is to use the standard
  169. compression level provided by the \fBzlib\fP(3) compression library.
  170. .
  171. .TP
  172. .B \-ImprovedHextile
  173. Use improved compression algorithm for Hextile encoding which achieves better
  174. compression ratios by the cost of using slightly more CPU time. Default is
  175. on.
  176. .
  177. .TP
  178. .B \-SecurityTypes \fIsec-types\fP
  179. Specify which security scheme to use for incoming connections. Valid values
  180. are a comma separated list of \fBNone\fP, \fBVncAuth\fP, \fBPlain\fP,
  181. \fBTLSNone\fP, \fBTLSVnc\fP, \fBTLSPlain\fP, \fBX509None\fP, \fBX509Vnc\fP
  182. and \fBX509Plain\fP. Default is \fBVncAuth,TLSVnc\fP.
  183. .
  184. .TP
  185. .B \-Password \fIpassword\fP
  186. Obfuscated binary encoding of the password which clients must supply to
  187. access the server. Using this parameter is insecure, use \fBPasswordFile\fP
  188. parameter instead.
  189. .
  190. .TP
  191. .B \-PlainUsers \fIuser-list\fP
  192. A comma separated list of user names that are allowed to authenticate via
  193. any of the "Plain" security types (Plain, TLSPlain, etc.). Specify \fB*\fP
  194. to allow any user to authenticate using this security type. Default is to
  195. deny all users.
  196. .
  197. .TP
  198. .B \-pam_service \fIname\fP, \-PAMService \fIname\fP
  199. PAM service name to use when authentication users using any of the "Plain"
  200. security types. Default is \fBvnc\fP.
  201. .
  202. .TP
  203. .B \-X509Cert \fIpath\fP
  204. Path to a X509 certificate in PEM format to be used for all X509 based
  205. security types (X509None, X509Vnc, etc.).
  206. .
  207. .TP
  208. .B \-X509Key \fIpath\fP
  209. Private key counter part to the certificate given in \fBX509Cert\fP. Must
  210. also be in PEM format.
  211. .
  212. .TP
  213. .B \-GnuTLSPriority \fIpriority\fP
  214. GnuTLS priority string that controls the TLS session’s handshake algorithms.
  215. See the GnuTLS manual for possible values. Default is \fBNORMAL\fP.
  216. .
  217. .TP
  218. .B \-UseBlacklist
  219. Temporarily reject connections from a host if it repeatedly fails to
  220. authenticate. Default is on.
  221. .
  222. .TP
  223. .B \-BlacklistThreshold \fIcount\fP
  224. The number of unauthenticated connection attempts allowed from any individual
  225. host before that host is black-listed. Default is 5.
  226. .
  227. .TP
  228. .B \-BlacklistTimeout \fIseconds\fP
  229. The initial timeout applied when a host is first black-listed. The host
  230. cannot re-attempt a connection until the timeout expires. Default is 10.
  231. .
  232. .TP
  233. .B \-IdleTimeout \fIseconds\fP
  234. The number of seconds after which an idle VNC connection will be dropped.
  235. Default is 0, which means that idle connections will never be dropped.
  236. .
  237. .TP
  238. .B \-MaxDisconnectionTime \fIseconds\fP
  239. Terminate when no client has been connected for \fIN\fP seconds. Default is
  240. 0.
  241. .
  242. .TP
  243. .B \-MaxConnectionTime \fIseconds\fP
  244. Terminate when a client has been connected for \fIN\fP seconds. Default is
  245. 0.
  246. .
  247. .TP
  248. .B \-MaxIdleTime \fIseconds\fP
  249. Terminate after \fIN\fP seconds of user inactivity. Default is 0.
  250. .
  251. .TP
  252. .B \-QueryConnect
  253. Prompts the user of the desktop to explicitly accept or reject incoming
  254. connections. Default is off.
  255. The \fBvncconfig\fP(1) program must be running on the desktop in order for
  256. QueryConnect to be supported.
  257. .
  258. .TP
  259. .B \-QueryConnectTimeout \fIseconds\fP
  260. Number of seconds to show the Accept Connection dialog before rejecting the
  261. connection. Default is \fB10\fP.
  262. .
  263. .TP
  264. .B \-localhost
  265. Only allow connections from the same machine. Useful if you use SSH and want to
  266. stop non-SSH connections from any other hosts.
  267. .
  268. .TP
  269. .B \-Log \fIlogname\fP:\fIdest\fP:\fIlevel\fP
  270. Configures the debug log settings. \fIdest\fP can currently be \fBstderr\fP,
  271. \fBstdout\fP or \fBsyslog\fP, and \fIlevel\fP is between 0 and 100, 100 meaning
  272. most verbose output. \fIlogname\fP is usually \fB*\fP meaning all, but you can
  273. target a specific source file if you know the name of its "LogWriter". Default
  274. is \fB*:stderr:30\fP.
  275. .
  276. .TP
  277. .B \-RemapKeys \fImapping
  278. Sets up a keyboard mapping.
  279. .I mapping
  280. is a comma-separated string of character mappings, each of the form
  281. .IR char -> char ,
  282. or
  283. .IR char <> char ,
  284. where
  285. .I char
  286. is a hexadecimal keysym. For example, to exchange the " and @ symbols you would specify the following:
  287. .RS 10
  288. RemapKeys=0x22<>0x40
  289. .RE
  290. .
  291. .TP
  292. .B \-AvoidShiftNumLock
  293. Key affected by NumLock often require a fake Shift to be inserted in order
  294. for the correct symbol to be generated. Turning on this option avoids these
  295. extra fake Shift events but may result in a slightly different symbol
  296. (e.g. a Return instead of a keypad Enter).
  297. .
  298. .TP
  299. .B \-RawKeyboard
  300. Send keyboard events straight through and avoid mapping them to the current
  301. keyboard layout. This effectively makes the keyboard behave according to the
  302. layout configured on the server instead of the layout configured on the
  303. client. Default is off.
  304. .
  305. .TP
  306. .B \-AllowOverride
  307. Comma separated list of parameters that can be modified using VNC extension.
  308. Parameters can be modified for example using \fBvncconfig\fP(1) program from
  309. inside a running session.
  310. Allowing override of parameters such as \fBPAMService\fP or \fBPasswordFile\fP
  311. can negatively impact security if Xvnc runs under different user than the
  312. programs allowed to override the parameters.
  313. When \fBNoClipboard\fP parameter is set, allowing override of \fBSendCutText\fP
  314. and \fBAcceptCutText\fP has no effect.
  315. Default is \fBdesktop,AcceptPointerEvents,SendCutText,AcceptCutText,SendPrimary,SetPrimary\fP.
  316. .SH USAGE WITH INETD
  317. By configuring the \fBinetd\fP(1) service appropriately, Xvnc can be launched
  318. on demand when a connection comes in, rather than having to be started
  319. manually. When given the \fB-inetd\fP option, instead of listening for TCP
  320. connections on a given port it uses its standard input and standard output.
  321. There are two modes controlled by the wait/nowait entry in the inetd.conf file.
  322. In the nowait mode, Xvnc uses its standard input and output directly as the
  323. connection to a viewer. It never has a listening socket, so cannot accept
  324. further connections from viewers (it can however connect out to listening
  325. viewers by use of the vncconfig program). Further viewer connections to the
  326. same TCP port result in inetd spawning off a new Xvnc to deal with each
  327. connection. When the connection to the viewer dies, the Xvnc and any
  328. associated X clients die. This behaviour is most useful when combined with the
  329. XDMCP options -query and -once. An typical example in inetd.conf might be (all
  330. on one line):
  331. 5950 stream tcp nowait nobody /usr/local/bin/Xvnc Xvnc -inetd -query
  332. localhost -once securitytypes=none
  333. In this example a viewer connection to :50 will result in a new Xvnc for that
  334. connection which should display the standard XDM login screen on that machine.
  335. Because the user needs to login via XDM, it is usually OK to accept connections
  336. without a VNC password in this case.
  337. In the wait mode, when the first connection comes in, inetd gives the listening
  338. socket to Xvnc. This means that for a given TCP port, there is only ever one
  339. Xvnc at a time. Further viewer connections to the same port are accepted by
  340. the same Xvnc in the normal way. Even when the original connection is broken,
  341. the Xvnc will continue to run. If this is used with the XDMCP options -query
  342. and -once, the Xvnc and associated X clients will die when the user logs out of
  343. the X session in the normal way. It is important to use a VNC password in this
  344. case. A typical entry in inetd.conf might be:
  345. 5951 stream tcp wait james /usr/local/bin/Xvnc Xvnc -inetd -query localhost -once passwordFile=/home/james/.vnc/passwd
  346. In fact typically, you would have one entry for each user who uses VNC
  347. regularly, each of whom has their own dedicated TCP port which they use. In
  348. this example, when user "james" connects to :51, he enters his VNC password,
  349. then gets the XDM login screen where he logs in in the normal way. However,
  350. unlike the previous example, if he disconnects, the session remains persistent,
  351. and when he reconnects he will get the same session back again. When he logs
  352. out of the X session, the Xvnc will die, but of course a new one will be
  353. created automatically the next time he connects.
  354. .SH SEE ALSO
  355. .BR vncconfig (1),
  356. .BR vncpasswd (1),
  357. .BR vncviewer (1),
  358. .BR vncsession (8),
  359. .BR Xserver (1),
  360. .BR inetd (1)
  361. .br
  362. https://www.tigervnc.org
  363. .SH AUTHOR
  364. Tristan Richardson, RealVNC Ltd. and others.
  365. VNC was originally developed by the RealVNC team while at Olivetti
  366. Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were
  367. implemented by Constantin Kaplinsky. Many other people have since
  368. participated in development, testing and support. This manual is part
  369. of the TigerVNC software suite.