Lines Matching full:vnc
4 x11vnc - allow VNC connections to real X11 displays
23 as a VNC server it will print out a string: PORT=XXXX where XXXX is typically
24 5900 (the default VNC server port). One would next run something like
31 these protections. See the FAQ for details how to tunnel the VNC connection
40 Also, use of a VNC password (-rfbauth or \fB-passwdfile)\fR is strongly recommended.
93 If the X display is :N, try to set the VNC display to
102 Automatically probe for a free VNC port starting at n.
104 stay away from other VNC servers near 5900.
108 The VNC port to listen on (a LibVNCServer option), e.g.
181 connect to the remote VNC server host:N and be a
183 to manage the case of many simultaneous VNC viewers
189 \fB-rawfb\fR vnc:host:N for more details.
229 offset +X+Y. The VNC display has size WxH (i.e. smaller
343 of the display that is then exported via VNC.
414 VNC viewers cannot handle 24bpp (e.g. "main: setPF:
474 All VNC clients can only watch (default off).
478 VNC display is shared, i.e. more than one viewer can
491 To get the standard non-shared VNC behavior where when
492 a new VNC client connects the existing VNC client is
518 use if a VNC client (the only client for that process)
576 VNC Viewers that connect are able to do filetransfer
592 VNC Viewers that connect are able to do filetransfer
621 this VNC server to the local network. (Related terms:
657 Note that unlike most vnc servers, x11vnc will require a
673 "vnc repeater": http://www.uvnc.com/addons/repeater.html
677 before the VNC protocol is started. Here are the ways
695 vnc viewer. Somehow the pre-string tells the repeater
696 server how to find the vnc viewer and connect you to it.
721 that if the VNC Client does any sort of a 'Fetch Cert'
806 reach the VNC viewer. Up to 3 may be chained, separate
821 VNC program
932 When VNC viewers are connected, attempt to the grab
973 Apply both \fB-grabkbd\fR and \fB-grabptr\fR even when no VNC
999 (BTW: neither should the VNC \fB-rfbauth\fR file: it is NOT
1016 Note that due to the VNC protocol only the first 8
1029 VNC spec). Then follows len bytes which is the random
1038 are used. The latter will require customizing the VNC
1066 Print to the screen the obscured VNC password kept in
1090 as it is typed. This could be of use for VNC viewers
1289 with status 0 (success) the VNC user will be accepted.
1322 env | egrep \fB-i\fR 'rfb|vnc' 1>&2
1494 to the connecting VNC client in combined \fB-unixpw\fR
1497 Normally in a \fB-unixpw\fR mode the VNC client must
1539 or creation) to a VNC server listening on port. You
1543 If 0 <= port < 200 it is taken as a VNC display (5900 is
1549 This provides an easy way to add SSL encryption to a VNC
1550 server that does not support SSL (e.g. Xvnc or vnc.so)
1551 In fact, the protocol does not even need to be VNC,
1565 x11vnc waits until a VNC client connects before opening
1579 VNC client first attaches to since some VNC viewers
1628 be applied to the VNC screen. For example,
1682 (x11vnc \fB-R\fR opt:val) during his VNC session.
1686 authenticated VNC user with his desktop. This could
1690 for his desktop and VNC.
1855 "Xvnc" will start up a VNC X server (real-
1856 or tight-vnc, e.g. use if Xvfb is not available).
1909 redirection of the connected VNC viewer to the Xvnc.
1911 So in Xvnc.redirect x11vnc does no VNC but merely
1914 as connecting directly to the Xvnc with the VNC Viewer.
1919 Xvnc.redirect should also work for the vnc.so X server
1926 The VeNCrypt extension to the VNC protocol allows
1971 The ANONTLS extension to the VNC protocol allows
1979 It is referred to as 'TLS' for its registered VNC
2036 built-in encrypted SSL/TLS tunnel between VNC viewers
2043 The VNC Viewer-side needs to support SSL/TLS as well.
2052 If the VNC Viewer supports VeNCrypt or ANONTLS (vino's
2065 The connecting VNC viewer SSL tunnel can (at its option)
2071 if the VNC viewer simply accepts this server's key
2084 file ~/.vnc/certs/server.pem. On subsequent calls if
2097 to refer to the file ~/.vnc/certs/server-<string>.pem
2100 ~/.vnc/certs/server-charlie.pem
2121 authentication of the server to VNC viewers.)
2130 the VNC viewer authenticating them (via the public
2136 to authenticate either the VNC server or VNC client.
2143 default ~/.vnc/certs
2180 ~/.vnc/certs
2188 manage multiple VNC Certificate Authority (CA) keys.
2189 Another use is if ~/.vnc/cert is on an NFS share you
2200 to provide certificates to authenticate incoming VNC
2242 ~/.vnc/certs default.
2262 They provide VNC Certificate Authority (CA) key creation
2265 VNC-ing with x11vnc. (note that they require
2271 temporary key and the VNC viewers always accept it,
2288 if you had a large number of VNC client and server
2293 Next, he could create signed VNC server keys
2296 any VNC client that has the CA cert.
2299 VNC clients themselves are authenticated to x11vnc
2304 key files. On the VNC client side, they will need to
2325 certificate chain used to verify the VNC client.
2346 \fB-gencrl\fR ...' are useful. (Run them in ~/.vnc/certs)
2355 or otherwise ~/.vnc/certs is used.
2364 x11vnc command exits; the VNC server is not run.
2368 as long as clients accept the cert for VNC connections.
2374 workstations where VNC viewers will be run. One will
2389 Generate a VNC server or client certificate and private
2397 VNC server is not run.
2401 "client" (for a VNC viewer). Note that typically
2402 only "server" is used: the VNC clients authenticate
2403 themselves by a non-public-key method (e.g. VNC or
2441 directory other than the default ~/.vnc/certs You will
2467 file will be ~/.vnc/certs/server.pem. This one would
2473 to be copied and imported into the VNC viewer
2477 it is only needed on the VNC viewer side. The,
2478 e.g. ~/.vnc/certs/clients/<name>.pem contains both
2485 masquerade as the x11vnc server (or VNC viewer client).
2502 was safely copied to the VNC viewer machine where
2513 scp ~/.vnc/certs/clients/roger.pem somehost:.
2514 rm ~/.vnc/certs/clients/roger.pem
2517 ~/.vnc/certs/clients/roger.crt (or simply \fB-sslverify\fR
2539 a directory besides the default ~/.vnc/certs)
2545 the x11vnc command exits; the VNC server is not run.
2562 the VNC server is not run.
2568 managed (in the ~/.vnc/certs dir, use \fB-ssldir\fR to refer
2578 ([dir] is ~/.vnc/certs or one given by \fB-ssldir.)\fR
2638 "The SSL VNC desktop is ..." and "SSLPORT=..."
2657 Your VNC viewer will also need to be able to connect
2708 use SSH but want some encryption for your VNC session.
2725 side of the VNC connection (See SSVNC for examples).
2771 The SSVNC vnc viewer project supplies a symmetric
2780 or server (VNC or otherwise.) The cipher (1st arg)
2796 single VNC port (e.g. 5900) for both VNC and HTTPS
2810 or VNC Viewer applet. That's right 3 separate "Are
2829 ('index.vnc' or 'proxy.vnc') is sent do NOT set the
2830 applet PORT parameter to the actual VNC port but set it
2838 connect to the firewall/router port, not the VNC port
2854 not need to specify extra PARAMS in the index.vnc file.
2858 the network (i.e. you just want the single VNC/HTTPS
2869 \fB-stunnel,\fR or \fB-enc\fR options), allow the Java VNC Viewer
2870 applet to be downloaded thru the VNC port via HTTP.
2912 the ssh machine "host" can be reached by the VNC
2923 "disp" is the VNC display for the remote SSH side,
2947 line, first look for ~/.vnc/passwd and if found use it
2948 with \fB-rfbauth;\fR next, look for ~/.vnc/passwdfile and
2950 for a password to create ~/.vnc/passwd and use it with
2956 Store password \fIpass\fR as the VNC password in the
2962 in the file ~/.vnc/passwd. Called with one argument,
3236 To improve performance, when VNC clients are connected
3330 all viewers that do not support the NewFBSize VNC
3337 Rotate and/or flip the framebuffer view exported by VNC.
3362 not the final one sent to VNC viewers.
3389 it is expanded to the vnc display (the name may need
3525 in some circumstances: namely *both* the VNC viewer
3533 *only* enable CapsLock on the VNC viewer side (i.e. by
3542 you press Caps_Lock on the VNC Viewer side but that does
3575 Some VNC viewers send impossible repeated key events,
3579 just process the first event. Note: some VNC viewers
3587 If a Keysym is received from a VNC viewer and that
3651 "dead_acute", etc. However some VNC viewers send the
3683 VNC clients are connected and VNC keyboard input is
3693 Note: your VNC viewer side will likely do autorepeating,
3716 VNC viewers and the X server at all.
3727 from VNC clients.
3738 received from VNC clients.
3755 is done depends on the VNC viewer and the X server.
3758 Some VNC viewers support the TightVNC CursorPosUpdates
3767 will be some lag between the vnc viewer pointer and
3892 back to all vnc clients that support the TightVNC
3912 VNC mouse event force the pointer to the indicated x,y
3920 VNC input event.
4001 an awkward way in that in the VNC Viewer you can see the
4012 both on the x11vnc server side and on the VNC Viewer
4014 tripled for both x11vnc and the VNC Viewer. As a rule
4044 Some VNC Viewers provide better response than others
4059 the window will be pushed to top in the VNC viewer.
4080 GNOME) when VNC clients are connected.
4167 sent efficiently to the VNC clients). Use this option
4174 telling the VNC viewers to locally copy the translated
4175 window region. This is the VNC CopyRect encoding:
4216 it does there is a nice speedup from using the VNC
4242 your VNC viewer may have its own refresh hot-key
4484 Neither x11vnc's screen polling and vnc compression
4693 VNC clients are connected.
4701 VNC clients are connected, while "\fB-fbpm\fR" means to not
4712 going into a reduced power state when VNC clients
4726 VNC clients are connected, while "\fB-dpms\fR" means to not
4754 As \fB-forcedpms\fR but only when VNC clients are connected.
4759 This allows the VNC viewer to click a button that will
4774 that x11vnc is polling. That way the person on the VNC
4963 If the string begins with "vnc", see the VNC HOST
4965 of another remote VNC server.
4996 \fB-rawfb\fR vnc:somehost:0
5073 network VNC traffic.
5132 the settings through the VNC Viewer via keystrokes.
5234 VNC HOST: if the \fB-rawfb\fR string is of the form
5235 "vnc:host:N" then the VNC display "N" on the remote
5236 VNC server "host" is connected to (i.e. x11vnc acts as
5237 a VNC client itself) and that framebuffer is exported.
5241 10) simultaneous VNC viewers, and you try a divide
5249 For example, if there will be 64 simultaneous VNC
5250 viewers this can lead to a lot of redundant VNC traffic
5255 with option \fB-rawfb\fR vnc:host:N, then there are only
5257 8 vnc viewer connections thereby spreading the load
5267 second that must be propagated. Tip: if the remote VNC
5274 the password needed to log into the vnc host server, or
5278 To set the pixel format that x11vnc requests as a VNC
5285 The VNC HOST mode implies \fB-shared.\fR Use \fB-noshared\fR as
5631 VNC session password. If =<hexnumber> is appended
5652 with the VNC display number. You can also set the font
6550 command from standard VNC
6727 connected VNC clients. str is a non-empty string. If a
6728 VNC client sends rfbCutText having the prefix \fIstr\fR
6738 VNC viewers to run x11vnc \fB-remote\fR commands. Do not
6858 VNC desktop name (default "LibVNCServer")
