3 vncs, vncv \- remote frame buffer server and viewer for Virtual Network Computing (VNC)
59 VNC is a lightweight protocol
60 for accessing graphical applications
61 remotely. The protocol allows one or more
62 clients to connect to a server.
63 While connected, clients display the frame buffer
64 presented by the server and can send mouse events,
65 keyboard events, and exchange snarf buffers.
66 The server persists across viewer sessions, so that
67 the virtual application can be accessed from various locations
68 as its owner moves around.
70 VNC displays have names of the form
74 is the machine's network name and
76 is a small integer identifier; display
82 starts a new virtual frame buffer in memory, simulating
83 a Plan 9 terminal running
86 by default an interactive shell.
87 As viewers connect, each is authenticated using a
88 (rather breakable) challenge-response protocol using
89 the user's Inferno/POP password.
96 start TLS on each viewer connection using the certificate
99 The corresponding private key must be loaded into
102 When serving TLS connections, the base port is
103 35729 rather than 5900.
108 without this option, the server searches
109 for an unused display.
111 .B -g \fIwidth\fBx\fIheight\fR
112 set the virtual frame buffer to be
119 set the virtual frame buffer's internal pixel format to
125 print verbose output to standard error.
128 announce on an alternate network interface.
129 Because of the weak authentication protocol and
130 default lack of encryption, this option must
139 kills the VNC server running on display
143 provides access to remote display
145 It resizes its window to be the smaller of the
146 remote frame buffer size and the local screen.
151 when connecting to 8-bit displays, request
156 This takes up more bandwidth but usually gives
157 significantly better matching to the Plan 9 color map.
160 set the ordered list of allowed frame buffer update encodings.
161 The default (and full) set is
167 The encodings should be given as a single space-separated argument
168 (quoted when using the shell).
173 to the pattern used to select a key from
177 share the display with extant viewers;
178 by default extant viewers are closed
179 when a new viewer connects.
182 start TLS on the connection.
185 print verbose output to standard error.
188 The VNC protocol represents keyboard input as
190 Plan 9 does not expose the state of the
191 Ctl and Shift keys except as it can be inferred
192 from receipt of control or shifted characters.
193 It does not expose the state of the Alt key at all,
194 since the Alt key is used to compose Unicode characters
198 correctly handles the sending of control and shifted
200 To support systems that use key sequences like Alt-X
201 (or worse, Alt-mouse-click), typing the Plan 9 compose
216 will send a ``key down'' message for
218 A corresponding ``key up'' message
219 will be sent after the next key is pressed,
220 or when the sequence is retyped,
221 whichever happens first.
227 .B http://www.uk.research.att.com/vnc
229 If the remote frame buffer is larger than the local screen,
230 only the upper left corner can be accessed.
233 does no verification of the TLS certificate presented
237 supports only version 3.3 of the RFB protocol.