summaryrefslogtreecommitdiffstats
path: root/x11vnc
diff options
context:
space:
mode:
authorrunge <[email protected]>2009-08-10 17:56:10 -0400
committerrunge <[email protected]>2009-08-10 17:56:10 -0400
commitfd084b5d28189727f1dff6022d2b421d772bcc1a (patch)
treeb06223e1b18a4988e9c97ae6f759f7151570c1af /x11vnc
parent2c6bf9234edc30fd564a693a3bb954fd1ea50455 (diff)
downloadlibtdevnc-fd084b5d28189727f1dff6022d2b421d772bcc1a.tar.gz
libtdevnc-fd084b5d28189727f1dff6022d2b421d772bcc1a.zip
Improvements to -unixpw_cmd and -unixpw_nis.
Experimental X11VNC_WATCH_DX_DY=1 for buggy theme menus, see: http://ubuntuforums.org/showthread.php?t=1223490
Diffstat (limited to 'x11vnc')
-rw-r--r--x11vnc/README3659
-rw-r--r--x11vnc/connections.c47
-rw-r--r--x11vnc/enc.h4
-rw-r--r--x11vnc/help.c150
-rw-r--r--x11vnc/pointer.c13
-rw-r--r--x11vnc/unixpw.c80
-rw-r--r--x11vnc/unixpw.h1
-rw-r--r--x11vnc/user.c138
-rw-r--r--x11vnc/x11vnc.1158
-rw-r--r--x11vnc/x11vnc.c3
-rw-r--r--x11vnc/x11vnc_defs.c2
11 files changed, 2336 insertions, 1919 deletions
diff --git a/x11vnc/README b/x11vnc/README
index 5d21f4a..80269e3 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -2,7 +2,7 @@
Copyright (C) 2002-2009 Karl J. Runge <[email protected]>
All rights reserved.
-x11vnc README file Date: Sat Jul 11 12:53:06 EDT 2009
+x11vnc README file Date: Mon Aug 10 13:38:13 EDT 2009
The following information is taken from these URLs:
@@ -877,7 +877,7 @@ make
I'd appreciate any additional testing very much.
Thanks to those who suggested features and helped beta test x11vnc
- 0.9.8 released in Mar 2009!
+ 0.9.8 released in Jul 2009!
Please help test and debug the 0.9.9 version for release sometime in
2009.
@@ -901,17 +901,28 @@ make
Here are some features that will appear in the 0.9.9 release:
+ * The FINDDISPLAY and FINDCREATEDISPLAY modes (i.e. "[122]-display
+ WAIT:cmd=...", [123]-find, [124]-create) now work correctly for
+ the user-supplied login program scheme "[125]-unixpw_cmd ...", as
+ long as the login program supports running commands specified in
+ the environment variable "RFB_UNIXPW_CMD_RUN" as the logged-in
+ user. The mode "[126]-unixpw_nis ..." has also been made more
+ consistent.
+ * There is an experimental workaround: "-env X11VNC_WATCH_DX_DY=1"
+ that tries to avoid problems with poorly constructed menu themes
+ that place the initial position of the mouse cursor inside a menu
+ item's active zone. More information [127]can be found here.
Here are some features that appeared in the 0.9.8 release:
- * Stability improvements to [122]-threads mode. Running x11vnc this
+ * Stability improvements to [128]-threads mode. Running x11vnc this
way is more reliable now. Threaded operation sometimes gives
better interactive response and faster updates: try it out. The
threaded mode now supports multiple VNC viewers using the same VNC
encoding. The threaded mode can also yield a performance
enhancement in the many client case (e.g. class-room broadcast.)
We have tested with 30 to 50 simultaneous clients. See also
- [123]-reflect.
+ [129]-reflect.
For simultaneous clients: the ZRLE encoding is thread safe on all
platforms, and the Tight and Zlib encodings are currently only
thread safe on Linux where thread local storage, __thread, is
@@ -920,12 +931,12 @@ make
connected client, all encodings are safe on all platforms. Note
that some features (e.g. scroll detection and -ncache) may be
disabled or run with reduced functionality in -threads mode.
- * Automatically tries to work around an [124]Xorg server bug
+ * Automatically tries to work around an [130]Xorg server bug
involving infinitely repeating keys when turning off key
- repeating. Use [125]-repeat if the automatic workaround fails.
+ repeating. Use [131]-repeat if the automatic workaround fails.
* Improved reliability of the Single Port SSL VNC and HTTPS java
viewer applet delivery mechanism.
- * The [126]-clip mode works under [127]-rawfb.
+ * The [132]-clip mode works under [133]-rawfb.
Here are some features that appeared in the 0.9.7 release:
@@ -935,38 +946,38 @@ make
case the special file /dev/vcsa2 is used to retrieve vt2's current
text. Text and colors are shown, but no graphics.
* Support for less than 8 bits per pixel framebuffers (e.g. 4 or 1
- bpp) in the [128]-rawfb mode.
+ bpp) in the [134]-rawfb mode.
* The SSL enabled UltraVNC Java viewer applet now has a [Home] entry
in the "drives" drop down menu. This menu can be configured with
the ftpDropDown applet parameter. All of the applet parameters are
documented in classes/ssl/README.
- * Experimental support for [129]VirtualGL's [130]TurboVNC (an
+ * Experimental support for [135]VirtualGL's [136]TurboVNC (an
enhanced TightVNC for fast LAN high framerate usage.)
* The CUPS Terminal Services helper mode has been improved.
- * Improvements to the [131]-ncache_cr that allows smooth opaque
+ * Improvements to the [137]-ncache_cr that allows smooth opaque
window motions using the 'copyrect' encoding when using
- [132]-ncache mode.
- * The [133]-rmflag option enables a way to indicate to other
+ [138]-ncache mode.
+ * The [139]-rmflag option enables a way to indicate to other
processes x11vnc has exited.
* Reverse connections using anonymous Diffie Hellman SSL encryption
now work.
Here are some features that appeared in the 0.9.6 release:
- * Support for [134]VeNCrypt SSL/TLS encrypted connections. It is
- enabled by default in the [135]-ssl mode. VNC Viewers like
+ * Support for [140]VeNCrypt SSL/TLS encrypted connections. It is
+ enabled by default in the [141]-ssl mode. VNC Viewers like
vinagre, gvncviewer/gtk-vnc, the vencrypt package, and others
support this encryption mode. It can also be used with the
- [136]-unixpw option to enable Unix username and password
+ [142]-unixpw option to enable Unix username and password
authentication (VeNCrypt's "*Plain" modes.) A similar but older
VNC security type "ANONTLS" (used by vino) is supported as well.
- See the [137]-vencrypt and [138]-anontls options for additional
+ See the [143]-vencrypt and [144]-anontls options for additional
control. The difference between x11vnc's normal -ssl mode and
VeNCrypt is that the former wraps the entire VNC connection in SSL
(like HTTPS does for HTTP, i.e. "vncs://") while VeNCrypt switches
on the SSL/TLS at a certain point during the VNC handshake. Use
- [139]-sslonly to disable both VeNCrypt and ANONTLS (vino.)
- * The "[140]-ssl ANON" option enables Anonymous Diffie-Hellman (ADH)
+ [145]-sslonly to disable both VeNCrypt and ANONTLS (vino.)
+ * The "[146]-ssl ANON" option enables Anonymous Diffie-Hellman (ADH)
key exchange for x11vnc's normal SSL/TLS operation. Note that
Anonymous Diffie-Hellman uses encryption for privacy, but provides
no authentication and so is susceptible to Man-In-The-Middle
@@ -974,17 +985,17 @@ make
SAVE", etc. and have the VNC viewer verify the cert.) The ANONTLS
mode (vino) only supports ADH. VeNCrypt mode supports both ADH and
regular X509 SSL certificates modes. For these ADH is enabled by
- default. See [141]-vencrypt and [142]-anontls for how to disable
+ default. See [147]-vencrypt and [148]-anontls for how to disable
ADH.
* For x11vnc's SSL/TLS modes, one can now specify a Certificate
- Revocation List (CRL) with the [143]-sslCRL option. This will only
+ Revocation List (CRL) with the [149]-sslCRL option. This will only
be useful for wide deployments: say a company-wide x11vnc SSL
access deployment using a central Certificate Authority (CA) via
- [144]-sslGenCA and [145]-sslGenCert. This way if a user has his
+ [150]-sslGenCA and [151]-sslGenCert. This way if a user has his
laptop lost or stolen, you only have to revoke his key instead of
creating a new Certificate Authority and redeploying new keys to
all users.
- * The default SSL/TLS mode, "[146]-ssl" (no pem file parameter
+ * The default SSL/TLS mode, "[152]-ssl" (no pem file parameter
supplied), is now the same as "-ssl SAVE" and will save the
generated self-signed cert in "~/.vnc/certs/server.pem".
Previously "-ssl" would create a temporary self-signed cert that
@@ -994,45 +1005,45 @@ make
same x11vnc server. Use "-ssl TMP" to regain the previous
behavior. Use "-ssl SAVE_NOPROMPT" to avoid being prompted about
using passphrase when the certificate is created.
- * The option [147]-http_oneport enables single-port HTTP connections
+ * The option [153]-http_oneport enables single-port HTTP connections
via the Java VNC Viewer. So, for example, the web browser URL
"http://myhost.org:5900" works the same as
"http://myhost.org:5800", but with the convenience of only
involving one port instead of two. This works for both unencrypted
- connections and for SSH tunnels (see [148]-httpsredir if the
+ connections and for SSH tunnels (see [154]-httpsredir if the
tunnel port differs.) Note that HTTPS single-port operation in
- [149]-ssl SSL encrypted mode has been available since x11vnc
+ [155]-ssl SSL encrypted mode has been available since x11vnc
version 0.8.3.
- * For the [150]-avahi/[151]-zeroconf Service Advertizing mode, if
+ * For the [156]-avahi/[157]-zeroconf Service Advertizing mode, if
x11vnc was not compiled with the avahi-client library, then an
external helper program, either avahi-publish(1) (on Unix) or
dns-sd(1) (on Mac OS X), is used instead.
- * The "[152]-rfbport PROMPT" option will prompt the user via the GUI
+ * The "[158]-rfbport PROMPT" option will prompt the user via the GUI
to select the VNC port (e.g. 5901) to listen on, and a few other
basic settings. This enables a handy GUI mode for naive users:
x11vnc -gui tray=setpass -rfbport PROMPT -logfile $HOME/.x11vnc.log.%VNCDISP
LAY
suitable for putting in a launcher or menu, e.g.
- [153]x11vnc.desktop. The [154]-logfile expansion is new too. In
+ [159]x11vnc.desktop. The [160]-logfile expansion is new too. In
the GUI, the tray=setpass Properties panel has been improved.
- * The [155]-solid solid background color option now works for the
+ * The [161]-solid solid background color option now works for the
Mac OS X console.
- * The [156]-reopen option instructs x11vnc to try to reopen the X
+ * The [162]-reopen option instructs x11vnc to try to reopen the X
display if it is prematurely closed by, say, the display manager
- (e.g. [157]GDM.)
+ (e.g. [163]GDM.)
Here are some features that appeared in the 0.9.5 release:
- * Symmetric key [158]encryption ciphers. ARC4, AES-128, AES-256,
+ * Symmetric key [164]encryption ciphers. ARC4, AES-128, AES-256,
blowfish, and 3des are supported. Salt and initialization vector
seeding is provided. These compliment the more widely used SSL and
- SSH encryption access methods. [159]SSVNC also supports these
+ SSH encryption access methods. [165]SSVNC also supports these
encryption modes.
* Scaling differently along the X- and Y-directions. E.g.
- "[160]-scale 1280x1024" or "-scale 0.8x0.75" Also,
- "[161]-geometry WxH" is an alias for "-scale WxH"
+ "[166]-scale 1280x1024" or "-scale 0.8x0.75" Also,
+ "[167]-geometry WxH" is an alias for "-scale WxH"
* By having SSVNC version 1.0.21 or later available in your $PATH,
- the [162]-chatwindow option allows a UltraVNC Text Chat window to
+ the [168]-chatwindow option allows a UltraVNC Text Chat window to
appear on the local X11 console/display (this way the remote
viewer can chat with the person at the physical display; e.g.
helpdesk mode.) This also works on the Mac OS X console if the
@@ -1044,46 +1055,46 @@ LAY
Here are some features that appeared in the 0.9.4 release:
- * Improvements to the [163]-find and [164]-create X session finding
+ * Improvements to the [169]-find and [170]-create X session finding
or creating modes: new desktop types and service redirection
options. Personal cupsd daemon and SSH port redirection helper for
- use with [165]SSVNC's Terminal Services feature.
- * Reverse VNC connections via [166]-connect work in the [167]-find,
- [168]-create and related [169]-display WAIT:... modes.
+ use with [171]SSVNC's Terminal Services feature.
+ * Reverse VNC connections via [172]-connect work in the [173]-find,
+ [174]-create and related [175]-display WAIT:... modes.
* Reverse VNC connections (either normal or SSL) can use a Web Proxy
or a SOCKS proxy, or a SSH connection, or even a CGI URL to make
- the outgoing connection. See: [170]-proxy. Forward connections can
- also use: [171]-ssh.
- * Reverse VNC connections via the [172]UltraVNC repeater proxy
+ the outgoing connection. See: [176]-proxy. Forward connections can
+ also use: [177]-ssh.
+ * Reverse VNC connections via the [178]UltraVNC repeater proxy
(either normal or SSL) are supported. Use either the
- "[173]-connect repeater=ID:NNNN+host:port" or "[174]-connect
- repeater://host:port+ID:NNNN" notation. The [175]SSVNC VNC viewer
+ "[179]-connect repeater=ID:NNNN+host:port" or "[180]-connect
+ repeater://host:port+ID:NNNN" notation. The [181]SSVNC VNC viewer
also supports the UltraVNC repeater.
* Support for indexed colormaps (PseudoColor) with depths other than
8 (from 1 to 16 now work) for non-standard hardware. Option
- "[176]-advertise_truecolor" to handle some workaround in this
+ "[182]-advertise_truecolor" to handle some workaround in this
mode.
* Support for the ZYWRLE encoding, this is the RealVNC ZRLE encoding
extended to do motion video and photo regions more efficiently by
way of a Wavelet based transformation.
- * The [177]-finddpy and [178]-listdpy utilities help to debug and
- configure the [179]-find, [180]-create, and [181]-display WAIT:...
+ * The [183]-finddpy and [184]-listdpy utilities help to debug and
+ configure the [185]-find, [186]-create, and [187]-display WAIT:...
modes.
* Some automatic detection of screen resizes are handled even if the
- [182]-xrandr option is not supplied.
- * The [183]-autoport options gives more control over the VNC port
+ [188]-xrandr option is not supplied.
+ * The [189]-autoport options gives more control over the VNC port
x11vnc chooses.
- * The [184]-ping secs can be used to help keep idle connections
+ * The [190]-ping secs can be used to help keep idle connections
alive.
* Pasting of the selection/clipboard into remote applications (e.g.
Java) has been improved.
* Fixed a bug if a client disconnects during the 'speed-estimation'
phase.
* To unset Caps_Lock, Num_Lock and raise all keys in the X server
- use [185]-clear_all.
+ use [191]-clear_all.
* Usage with dvorak keyboards has been improved. See also:
- [186]-xkb.
- * The [187]Java Viewer applet source code is now included in the
+ [192]-xkb.
+ * The [193]Java Viewer applet source code is now included in the
x11vnc-0.9.*.tar.gz tarball. This means you can now build the Java
viewer applet jar files from source. If you stopped shipping the
Java viewer applet jar files due to lack of source code, you can
@@ -1091,7 +1102,7 @@ LAY
Here are some features that appeared in the 0.9.3 release:
- * [188]Viewer-side pixmap caching. A large area of pixels (at least
+ * [194]Viewer-side pixmap caching. A large area of pixels (at least
2-3 times as big as the framebuffer itself; the bigger the
better... default is 10X) is placed below the framebuffer to act
as a buffer/cache area for pixel data. The VNC CopyRect encoding
@@ -1099,7 +1110,7 @@ LAY
Until we start modifying viewers you will be able to see the cache
area if you scroll down (this makes it easier to debug!) For
testing the default is "-ncache 10". The unix Enhanced TightVNC
- Viewer [189]ssvnc has a nice [190]-ycrop option to help hide the
+ Viewer [195]ssvnc has a nice [196]-ycrop option to help hide the
pixel cache area from view.
@@ -1112,14 +1123,14 @@ LAY
* If UltraVNC file transfer or chat is detected, then VNC clients
are "pinged" more often to prevent these side channels from
becoming serviced too infrequently.
- * In [191]-unixpw mode in the username and password dialog no text
+ * In [197]-unixpw mode in the username and password dialog no text
will be echoed if the first character sent is "Escape". This
enables a convenience feature in SSVNC to send the username and
password automatically.
Here are some features that appeared in the 0.9.1 release:
- * The [192]UltraVNC Java viewer has been enhanced to support SSL (as
+ * The [198]UltraVNC Java viewer has been enhanced to support SSL (as
the TightVNC viewer had been previously.) The UltraVNC Java
supports ultravnc filetransfer, and so can be used as a VNC viewer
on Unix that supports ultravnc filetransfer. It is in the
@@ -1130,12 +1141,12 @@ LAY
Some other bugs in the UltraVNC Java viewer were fixed and a few
improvements to the UI made.
* A new Unix username login mode for VNC Viewers authenticated via a
- Client SSL Certificate: "[193]-users sslpeer=". The emailAddress
+ Client SSL Certificate: "[199]-users sslpeer=". The emailAddress
subject field is inspected for username@hostname and then acts as
though "-users +username" has been supplied. This way the Unix
username is identified by (i.e. simply extracted from) the Client
- SSL Certificate. This could be useful with [194]-find,
- [195]-create and [196]-svc modes if you are also have set up and
+ SSL Certificate. This could be useful with [200]-find,
+ [201]-create and [202]-svc modes if you are also have set up and
use VNC Client SSL Certificate authentication.
* For external display finding/creating programs (e.g. WAIT:cmd=...)
if the VNC Viewer is authenticated via a Client SSL Certificate,
@@ -1144,41 +1155,41 @@ LAY
Here are some features that appeared in the 0.9 release:
- * [197]VNC Service advertising via mDNS / ZeroConf / BonJour with
- the [198]Avahi client library. Enable via "[199]-avahi" or
- "[200]-zeroconf".
+ * [203]VNC Service advertising via mDNS / ZeroConf / BonJour with
+ the [204]Avahi client library. Enable via "[205]-avahi" or
+ "[206]-zeroconf".
* Implementations of UltraVNC's TextChat, SingleWindow, and
- ServerInput extensions (requires ultravnc viewer or [201]ssvnc
+ ServerInput extensions (requires ultravnc viewer or [207]ssvnc
Unix viewer.) They toggle the selection of a single window
- ([202]-id), and disable (friendly) user input and viewing (monitor
+ ([208]-id), and disable (friendly) user input and viewing (monitor
blank) at the VNC server.
- * Short aliases "[203]-find", "[204]-create", "[205]-svc", and
- "[206]-xdmsvc" for commonly used FINDCREATEDISPLAY usage modes.
+ * Short aliases "[209]-find", "[210]-create", "[211]-svc", and
+ "[212]-xdmsvc" for commonly used FINDCREATEDISPLAY usage modes.
* Reverse VNC connections (viewer listening) now work in SSL
- ([207]-ssl) mode.
+ ([213]-ssl) mode.
* New options to control the Monitor power state and keyboard/mouse
- grabbing: [208]-forcedpms, [209]-clientdpms, [210]-noserverdpms,
- and [211]-grabalways.
+ grabbing: [214]-forcedpms, [215]-clientdpms, [216]-noserverdpms,
+ and [217]-grabalways.
* A simple way to emulate inetd(8) to some degree via the
- "[212]-loopbg" option.
- * Monitor the accuracy of XDAMAGE and apply "[213]-noxdamage" if it
- is not working well. OpenGL applications like like [214]beryl and
+ "[218]-loopbg" option.
+ * Monitor the accuracy of XDAMAGE and apply "[219]-noxdamage" if it
+ is not working well. OpenGL applications like like [220]beryl and
MythTv have been shown to make XDAMAGE not work properly.
* For Java SSL connections involving a router/firewall port
- redirection, an option [215]-httpsredir to spare the user from
+ redirection, an option [221]-httpsredir to spare the user from
needing to include &PORT=NNN in the browser URL.
Here are some features that appeared in the 0.8.4 release:
- * Native [216]Mac OS X Aqua/Quartz support. (i.e. OSXvnc
+ * Native [222]Mac OS X Aqua/Quartz support. (i.e. OSXvnc
alternative; some activities are faster)
- * A [217]new login mode: "-display WAIT:cmd=FINDCREATEDISPLAY
+ * A [223]new login mode: "-display WAIT:cmd=FINDCREATEDISPLAY
-unixpw ..." that will Create a new X session (either virtual or
real and with or without a display manager, e.g. kdm) for the user
if it cannot find the user's X session display via the FINDDISPLAY
- method. See the [218]-svc and the [219]-xdmsvc aliases.
- * x11vnc can act as a VNC [220]reflector/repeater using the
- "[221]-reflect host:N" option. Instead of polling an X display,
+ method. See the [224]-svc and the [225]-xdmsvc aliases.
+ * x11vnc can act as a VNC [226]reflector/repeater using the
+ "[227]-reflect host:N" option. Instead of polling an X display,
the remote VNC Server host:N is connected to and re-exported via
VNC. This is intended for use in broadcasting a display to many
(e.g. > 16; classroom or large demo) VNC viewers where bandwidth
@@ -1186,16 +1197,16 @@ LAY
number of repeaters.
* Wireframe copyrect detection for local user activity (e.g. someone
sitting at the physical display moving windows) Use
- [222]-nowireframelocal to disable.
- * The "[223]-N" option couples the VNC Display number to the X
+ [228]-nowireframelocal to disable.
+ * The "[229]-N" option couples the VNC Display number to the X
Display number. E.g. if your X DISPLAY is :2 then the VNC display
will be :2 (i.e. using port 5902.) If that port is taken x11vnc
will exit.
- * Option [224]-nodpms to avoid problems with programs like KDE's
+ * Option [230]-nodpms to avoid problems with programs like KDE's
kdesktop_lock that keep restarting the screen saver every few
seconds.
* To automatically fix the common mouse motion problem on XINERAMA
- (multi-headed) displays, the [225]-xwarppointer option is enabled
+ (multi-headed) displays, the [231]-xwarppointer option is enabled
by default when XINERAMA is active.
If you have a Mac please try out the native Mac OS X support, build
@@ -1205,62 +1216,62 @@ LAY
Here are some features that appeared in the 0.8.3 release:
- * The [226]-ssl option provides SSL encryption and authentication
- natively via the [227]www.openssl.org library. One can use from a
+ * The [232]-ssl option provides SSL encryption and authentication
+ natively via the [233]www.openssl.org library. One can use from a
simple self-signed certificate server certificate up to full CA
and client certificate authentication schemes.
- * Similar to -ssl, the [228]-stunnel option starts up a SSL tunnel
+ * Similar to -ssl, the [234]-stunnel option starts up a SSL tunnel
server stunnel (that must be installed separately on the system:
- [229]www.stunnel.org [230]stunnel.mirt.net ) to allow only
+ [235]www.stunnel.org [236]stunnel.mirt.net ) to allow only
encrypted SSL connections from the network.
- * The [231]-sslverify option allows for authenticating VNC clients
+ * The [237]-sslverify option allows for authenticating VNC clients
via their certificates in either -ssl or -stunnel modes.
* Certificate creation and management tools are provide in the
- [232]-sslGenCert, [233]-sslGenCA, and [234]related options.
+ [238]-sslGenCert, [239]-sslGenCA, and [240]related options.
* An SSL enabled Java applet VNC Viewer applet is provided by x11vnc
in classes/ssl/VncViewer.jar. In addition to normal HTTP, the
applet may be loaded into the web browser via HTTPS (HTTP over
SSL.) (one can use the VNC port, e.g. https://host:5900/, or also
- the separate [235]-https port option.) A wrapper shell script
- [236]ss_vncviewer is also provided that sets up a stunnel
- client-side tunnel on Unix systems. See [237]Enhanced TightVNC
+ the separate [241]-https port option.) A wrapper shell script
+ [242]ss_vncviewer is also provided that sets up a stunnel
+ client-side tunnel on Unix systems. See [243]Enhanced TightVNC
Viewer (SSVNC) for other SSL/SSH viewer possibilities.
- * The [238]-unixpw option supports Unix username and password
- authentication (a simpler variant is the [239]-unixpw_nis option
+ * The [244]-unixpw option supports Unix username and password
+ authentication (a simpler variant is the [245]-unixpw_nis option
that works in environments where the encrypted passwords are
- readable, e.g. NIS.) The [240]-ssl or [241]-localhost +
- [242]-stunnel options are enforced in this mode to prevent
+ readable, e.g. NIS.) The [246]-ssl or [247]-localhost +
+ [248]-stunnel options are enforced in this mode to prevent
password sniffing. As a convenience, these requirements are lifted
if a SSH tunnel can be deduced (but -localhost still applies.)
- * Coupling [243]-unixpw with "[244]-display WAIT:cmd=FINDDISPLAY" or
+ * Coupling [249]-unixpw with "[250]-display WAIT:cmd=FINDDISPLAY" or
"-display WAIT:cmd=FINDCREATEDISPLAY" provides a way to allow a
user to login with their UNIX password and have their display
- connected to [245]automatically. See the [246]-svc and the
- [247]-xdmsvc aliases.
- * Hooks are provided in the [248]-unixpw_cmd and "[249]-passwdfile
+ connected to [251]automatically. See the [252]-svc and the
+ [253]-xdmsvc aliases.
+ * Hooks are provided in the [254]-unixpw_cmd and "[255]-passwdfile
cmd:,custom:..." options to allow you to supply your own
authentication and password lookup programs.
* x11vnc can be configured and built to not depend on X11 libraries
- "./configure --without-x" for [250]-rawfb only operation (e.g.
+ "./configure --without-x" for [256]-rawfb only operation (e.g.
embedded linux console devices.)
- * The [251]-rotate option enables you to rotate or reflect the
+ * The [257]-rotate option enables you to rotate or reflect the
screen before exporting via VNC. This is intended for use on
handhelds and other devices where the rotation orientation is not
"natural".
- * The "[252]-ultrafilexfer" alias is provided and improved UltraVNC
+ * The "[258]-ultrafilexfer" alias is provided and improved UltraVNC
filetransfer rates have been achieved.
- * Under the "[253]-connect_or_exit host" option x11vnc will exit
+ * Under the "[259]-connect_or_exit host" option x11vnc will exit
immediately unless the reverse connection to host succeeds. The
"-rfbport 0" option disables TCP listening for connections (useful
for this mode.)
- * The "[254]-rawfb rand" and "-rawfb none" options are useful for
+ * The "[260]-rawfb rand" and "-rawfb none" options are useful for
testing automation scripts, etc., without requiring a full
desktop.
- * Reduced spewing of information at startup, use "[255]-verbose"
+ * Reduced spewing of information at startup, use "[261]-verbose"
(also "-v") to turn it back on for debugging or if you are going
to send me a problem report.
- Here are some [256]Previous Release Notes
+ Here are some [262]Previous Release Notes
_________________________________________________________________
Some Notes:
@@ -1287,13 +1298,13 @@ LAY
protocol.) I suggest using xsetroot, dtstyle or similar utility to set
a solid background while using x11vnc. You can turn the pretty
background image back on when you are using the display directly.
- Update: As of Feb/2005 x11vnc has the [257]-solid [color] option that
+ Update: As of Feb/2005 x11vnc has the [263]-solid [color] option that
works on recent GNOME, KDE, and CDE and also on classic X (background
image is on the root window.) Update: As of Oct/2007 x11vnc has the
- [258]-ncache option that does a reasonable job caching the background
+ [264]-ncache option that does a reasonable job caching the background
(and other) pixmap data on the viewer side.
- I also find the [259]TightVNC encoding gives the best response for my
+ I also find the [265]TightVNC encoding gives the best response for my
usage (Unix <-> Unix over cable modem.) One needs a tightvnc-aware
vncviewer to take advantage of this encoding.
@@ -1305,17 +1316,17 @@ LAY
is X11's default listening port.) Had port 5900 been taken by some
other application, x11vnc would have next tried 5901. That would mean
the viewer command above should be changed to vncviewer
- far-away.east:1. You can force the port with the "[260]-rfbport NNNN"
+ far-away.east:1. You can force the port with the "[266]-rfbport NNNN"
option where NNNN is the desired port number. If that port is already
- taken, x11vnc will exit immediately. The "[261]-N" option will try to
+ taken, x11vnc will exit immediately. The "[267]-N" option will try to
match the VNC display number to the X display. (also see the "SunRay
Gotcha" note below)
Options: x11vnc has (far too) many features that may be activated
- via its [262]command line options. Useful options are, e.g., -scale to
+ via its [268]command line options. Useful options are, e.g., -scale to
do server-side scaling, and -rfbauth passwd-file to use VNC password
protection (the vncpasswd or storepasswd programs, or the x11vnc
- [263]-storepasswd option can be used to create the password file.)
+ [269]-storepasswd option can be used to create the password file.)
Algorithm: How does x11vnc do it? Rather brute-forcedly: it
continuously polls the X11 framebuffer for changes using
@@ -1343,7 +1354,7 @@ LAY
first testing out the programs. You get an interesting
recursive/feedback effect where vncviewer images keep popping up each
one contained in the previous one and slightly shifted a bit by the
- window manager decorations. There will be an [264]even more
+ window manager decorations. There will be an [270]even more
interesting effect if -scale is used. Also, if the XKEYBOARD is
supported and the XBell "beeps" once, you get an infinite loop of
beeps going off. Although all of this is mildly exciting it is not
@@ -1353,8 +1364,8 @@ LAY
Sun Ray Notes:
- You can run x11vnc on your (connected or disconnected) [265]SunRay
- session. Here are some [266]notes on SunRay usage with x11vnc.
+ You can run x11vnc on your (connected or disconnected) [271]SunRay
+ session. Here are some [272]notes on SunRay usage with x11vnc.
_________________________________________________________________
@@ -1366,7 +1377,7 @@ LAY
than you normally do to minimize the effects (e.g. do fullpage
paging rather than line-by-line scrolling, and move windows in a
single, quick motion.) Recent work has provided the
- [267]-scrollcopyrect and [268]-wireframe speedups using the
+ [273]-scrollcopyrect and [274]-wireframe speedups using the
CopyRect VNC encoding and other things, but they only speed up
some activities, not all.
* A rate limiting factor for x11vnc performance is that graphics
@@ -1425,18 +1436,18 @@ LAY
but we mention it because it may be of use for special purpose
applications. You may need to use the "-cc 4" option to force Xvfb
to use a TrueColor visual instead of DirectColor. See also the
- description of the [269]-create option that does all of this
+ description of the [275]-create option that does all of this
automatically for you.
Also, a faster and more accurate way is to use the "dummy"
XFree86/Xorg device driver (or our Xdummy wrapper script.) See
- [270]this FAQ for details.
+ [276]this FAQ for details.
* Somewhat surprisingly, the X11 mouse (cursor) shape is write-only
and cannot be queried from the X server. So traditionally in
x11vnc the cursor shape stays fixed at an arrow. (see the "-cursor
- X" and "-cursor some" [271]options, however, for a partial hack
+ X" and "-cursor some" [277]options, however, for a partial hack
for the root window, etc.) However, on Solaris using the SUN_OVL
overlay extension, x11vnc can show the correct mouse cursor when
- the [272]-overlay option is also supplied. A similar thing is done
+ the [278]-overlay option is also supplied. A similar thing is done
on IRIX as well when -overlay is supplied.
More generally, as of Dec/2004 x11vnc supports the new XFIXES
extension (in Xorg and Solaris 10) to query the X server for the
@@ -1444,18 +1455,18 @@ LAY
with transparency (alpha channel) need to approximated to solid
RGB values (some cursors look worse than others.)
* Audio from applications is of course not redirected (separate
- redirectors do exist, e.g. esd, see [273]the FAQ on this below.)
+ redirectors do exist, e.g. esd, see [279]the FAQ on this below.)
The XBell() "beeps" will work if the X server supports the
XKEYBOARD extension. (Note that on Solaris XKEYBOARD is disabled
by default. Passing +kb to Xsun enables it.)
- * The scroll detection algorithm for the [274]-scrollcopyrect option
+ * The scroll detection algorithm for the [280]-scrollcopyrect option
can give choppy or bunched up transient output and occasionally
painting errors.
* Using -threads can expose some bugs/crashes in libvncserver.
- Please feel free to [275]contact me if you have any questions,
+ Please feel free to [281]contact me if you have any questions,
problems, or comments about x11vnc, etc.
- Also, some people ask if they can make a donation, see [276]this link
+ Also, some people ask if they can make a donation, see [282]this link
for that.
References
@@ -1552,7 +1563,7 @@ References
90. http://sourceforge.net/projects/libvncserver/
91. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=695585
92. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=695585
- 93. http://x11vnc.sourceforge.net/dev/x11vnc-0.9.8.tar.gz
+ 93. http://x11vnc.sourceforge.net/dev/x11vnc-0.9.9.tar.gz
94. http://www.karlrunge.com/x11vnc/faq.html#faq-binaries
95. http://www.tightvnc.com/download.html
96. http://www.realvnc.com/products/free/4.1/download.html
@@ -1573,7 +1584,7 @@ References
111. http://www.karlrunge.com/x11vnc/faq.html#faq-solaris251build
112. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
113. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
- 114. http://x11vnc.sourceforge.net/dev/x11vnc-0.9.8.tar.gz
+ 114. http://x11vnc.sourceforge.net/dev/x11vnc-0.9.9.tar.gz
115. http://www.karlrunge.com/x11vnc/bins
116. mailto:[email protected]
117. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
@@ -1581,161 +1592,167 @@ References
119. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
120. http://www.karlrunge.com/x11vnc/ssvnc.html
121. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc
- 122. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 123. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
- 124. http://bugs.freedesktop.org/show_bug.cgi?id=21454
- 125. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-repeat
- 126. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 127. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 128. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 129. http://www.virtualgl.org/
- 130. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
- 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
- 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
- 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rmflag
- 134. http://sourceforge.net/projects/vencrypt/
- 135. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
- 138. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
- 139. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslonly
- 140. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
- 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
- 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCRL
- 144. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA
- 145. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert
+ 122. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 123. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 124. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 125. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 126. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 127. http://ubuntuforums.org/showthread.php?t=1223490
+ 128. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 129. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
+ 130. http://bugs.freedesktop.org/show_bug.cgi?id=21454
+ 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-repeat
+ 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 134. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 135. http://www.virtualgl.org/
+ 136. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
+ 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
+ 138. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
+ 139. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rmflag
+ 140. http://sourceforge.net/projects/vencrypt/
+ 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
+ 144. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
+ 145. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslonly
146. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 147. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_oneport
- 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
- 149. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
- 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
- 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 153. http://www.karlrunge.com/x11vnc/x11vnc.desktop
- 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 156. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen
- 157. http://www.karlrunge.com/x11vnc/faq.html#infaq_gdm
- 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc
- 159. http://www.karlrunge.com/x11vnc/ssvnc.html
- 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-geometry
- 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-chatwindow
- 163. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 147. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
+ 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
+ 149. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCRL
+ 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA
+ 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert
+ 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 153. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_oneport
+ 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
+ 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 156. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
+ 157. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
+ 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 159. http://www.karlrunge.com/x11vnc/x11vnc.desktop
+ 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen
+ 163. http://www.karlrunge.com/x11vnc/faq.html#infaq_gdm
+ 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc
165. http://www.karlrunge.com/x11vnc/ssvnc.html
- 166. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
- 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 169. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
- 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh
- 172. http://www.uvnc.com/addons/repeater.html
- 173. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
- 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 175. http://www.karlrunge.com/x11vnc/ssvnc.html
- 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-advertise_truecolor
- 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-finddpy
- 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listdpy
- 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 181. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 182. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr
- 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport
- 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ping
- 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
- 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 187. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
- 188. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
- 189. http://www.karlrunge.com/x11vnc/ssvnc.html
- 190. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop
- 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 192. http://www.ultravnc.com/
- 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 197. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi
- 198. http://www.avahi.org/
- 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
- 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
- 201. http://www.karlrunge.com/x11vnc/ssvnc.html
- 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
- 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
- 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
- 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabalways
- 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 214. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
- 216. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
- 217. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 220. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect
- 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nowireframelocal
- 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
- 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 227. http://www.openssl.org/
- 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 229. http://www.stunnel.org/
- 230. http://stunnel.mirt.net/
- 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert
- 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA
- 234. http://www.karlrunge.com/x11vnc/ssl.html
- 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 236. http://www.karlrunge.com/x11vnc/faq.html#infaq_ss_vncviewer
- 237. http://www.karlrunge.com/x11vnc/ssvnc.html
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 245. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit
- 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-v,
- 256. http://www.karlrunge.com/x11vnc/prevrels.html
- 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
- 259. http://www.tightvnc.com/
- 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 263. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
- 264. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
- 265. http://www.sun.com/sunray/index.html
- 266. http://www.karlrunge.com/x11vnc/sunray.html
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 269. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 270. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
- 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 273. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
- 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 275. mailto:[email protected]
- 276. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks
+ 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-geometry
+ 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-chatwindow
+ 169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 171. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 172. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
+ 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 175. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
+ 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh
+ 178. http://www.uvnc.com/addons/repeater.html
+ 179. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
+ 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 181. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-advertise_truecolor
+ 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-finddpy
+ 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listdpy
+ 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 187. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 188. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr
+ 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport
+ 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ping
+ 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
+ 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 193. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 194. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
+ 195. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 196. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop
+ 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 198. http://www.ultravnc.com/
+ 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 203. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi
+ 204. http://www.avahi.org/
+ 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
+ 207. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabalways
+ 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 220. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
+ 222. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
+ 223. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 226. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect
+ 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
+ 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nowireframelocal
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
+ 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 233. http://www.openssl.org/
+ 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 235. http://www.stunnel.org/
+ 236. http://stunnel.mirt.net/
+ 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
+ 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert
+ 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA
+ 240. http://www.karlrunge.com/x11vnc/ssl.html
+ 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 242. http://www.karlrunge.com/x11vnc/faq.html#infaq_ss_vncviewer
+ 243. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 251. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
+ 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
+ 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
+ 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-v,
+ 262. http://www.karlrunge.com/x11vnc/prevrels.html
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
+ 265. http://www.tightvnc.com/
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 269. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
+ 270. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg
+ 271. http://www.sun.com/sunray/index.html
+ 272. http://www.karlrunge.com/x11vnc/sunray.html
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 275. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 276. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 279. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 281. mailto:[email protected]
+ 282. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks
=======================================================================
http://www.karlrunge.com/x11vnc/faq.html:
@@ -1801,330 +1818,333 @@ http://www.karlrunge.com/x11vnc/faq.html:
[19]Q-17: When I start x11vnc on an Alpha Tru64 workstation the X
server crashes!
- [20]Q-18: Are there any build-time customizations possible, e.g.
+ [20]Q-18: When running x11vnc on an IBM AIX workstation after a few
+ minutes the VNC connection freezes.
+
+ [21]Q-19: Are there any build-time customizations possible, e.g.
change defaults, create a smaller binary, etc?
[Win2VNC Related]
- [21]Q-19: I have two separate machine displays in front of me, one
+ [22]Q-20: I have two separate machine displays in front of me, one
Windows the other X11: can I use x11vnc in combination with Win2VNC in
dual-screen mode to pass the keystrokes and mouse motions to the X11
display?
- [22]Q-20: I am running Win2VNC on my Windows machine and "x11vnc
+ [23]Q-21: I am running Win2VNC on my Windows machine and "x11vnc
-nofb" on Unix to pass keyboard and mouse to the Unix monitor.
Whenever I start Win2VNC it quickly disconnects and x11vnc says:
rfbProcessClientNormalMessage: read: Connection reset by peer
- [23]Q-21: Can I run "x11vnc -nofb" on a Mac OS X machine to redirect
+ [24]Q-22: Can I run "x11vnc -nofb" on a Mac OS X machine to redirect
mouse and keyboard input to it from Windows and X11 machines via
Win2VNC and x2vnc, respectively?
[Color Issues]
- [24]Q-22: The X display I run x11vnc on is only 8 bits per pixel (bpp)
+ [25]Q-23: The X display I run x11vnc on is only 8 bits per pixel (bpp)
PseudoColor (i.e. only 256 distinct colors.) The x11vnc colors may
start out OK, but after a while they are incorrect in certain windows.
- [25]Q-23: Color problems: Why are the colors for some windows
+ [26]Q-24: Color problems: Why are the colors for some windows
incorrect in x11vnc? BTW, my X display has nice overlay/multi-depth
visuals of different color depths: e.g. there are both depth 8 and 24
visuals available at the same time.
- [26]Q-24: I am on a high color system (depth >= 24) but I seem to have
+ [27]Q-25: I am on a high color system (depth >= 24) but I seem to have
colormap problems. They either flash or everything is very dark.
- [27]Q-25: How do I figure out the window id to supply to the -id
+ [28]Q-26: How do I figure out the window id to supply to the -id
windowid option?
- [28]Q-26: Why don't menus or other transient windows come up when I am
+ [29]Q-27: Why don't menus or other transient windows come up when I am
using the -id windowid option to view a single application window?
- [29]Q-27: My X display is depth 24 at 24bpp (instead of the normal
+ [30]Q-28: My X display is depth 24 at 24bpp (instead of the normal
depth 24 at 32bpp.) I'm having lots of color and visual problems with
x11vnc and/or vncviewer. What's up?
[Xterminals]
- [30]Q-28: Can I use x11vnc to view and interact with an Xterminal
+ [31]Q-29: Can I use x11vnc to view and interact with an Xterminal
(e.g. NCD) that is not running UNIX and so x11vnc cannot be run on it
directly?
- [31]Q-29: How do I get my X permissions (MIT-MAGIC-COOKIE file)
+ [32]Q-30: How do I get my X permissions (MIT-MAGIC-COOKIE file)
correct for a Unix/Linux machine acting as an Xterminal?
[Sun Rays]
- [32]Q-30: I'm having trouble using x11vnc with my Sun Ray session.
+ [33]Q-31: I'm having trouble using x11vnc with my Sun Ray session.
[Remote Control]
- [33]Q-31: How do I stop x11vnc once it is running in the background?
+ [34]Q-32: How do I stop x11vnc once it is running in the background?
- [34]Q-32: Can I change settings in x11vnc without having to restart
+ [35]Q-33: Can I change settings in x11vnc without having to restart
it? Can I remote control it?
[Security and Permissions]
- [35]Q-33: How do I create a VNC password for use with x11vnc?
+ [36]Q-34: How do I create a VNC password for use with x11vnc?
- [36]Q-34: Can I make it so -storepasswd doesn't show my password on
+ [37]Q-35: Can I make it so -storepasswd doesn't show my password on
the screen?
- [37]Q-35: Can I have two passwords for VNC viewers, one for full
+ [38]Q-36: Can I have two passwords for VNC viewers, one for full
access and the other for view-only access to the display?
- [38]Q-36: Can I have as many full-access and view-only passwords as I
+ [39]Q-37: Can I have as many full-access and view-only passwords as I
like?
- [39]Q-37: Does x11vnc support Unix usernames and passwords? Can I
+ [40]Q-38: Does x11vnc support Unix usernames and passwords? Can I
further limit the set of Unix usernames who can connect to the VNC
desktop?
- [40]Q-38: Can I supply an external program to provide my own custom
+ [41]Q-39: Can I supply an external program to provide my own custom
login method (e.g. Dynamic/One-time passwords or non-Unix (LDAP)
usernames and passwords)?
- [41]Q-39: Why does x11vnc exit as soon as the VNC viewer disconnects?
+ [42]Q-40: Why does x11vnc exit as soon as the VNC viewer disconnects?
And why doesn't it allow more than one VNC viewer to connect at the
same time?
- [42]Q-40: Can I limit which machines incoming VNC clients can connect
+ [43]Q-41: Can I limit which machines incoming VNC clients can connect
from?
- [43]Q-41: How do I build x11vnc/libvncserver with libwrap
+ [44]Q-42: How do I build x11vnc/libvncserver with libwrap
(tcp_wrappers) support?
- [44]Q-42: Can I have x11vnc only listen on one network interface (e.g.
+ [45]Q-43: Can I have x11vnc only listen on one network interface (e.g.
internal LAN) rather than having it listen on all network interfaces
and relying on -allow to filter unwanted connections out?
- [45]Q-43: Now that -localhost implies listening only on the loopback
+ [46]Q-44: Now that -localhost implies listening only on the loopback
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- [46]Q-44: Can I fine tune what types of user input are allowed? E.g.
+ [47]Q-45: Can I fine tune what types of user input are allowed? E.g.
have some users just be able to move the mouse, but not click or type
anything?
- [47]Q-45: Can I prompt the user at the local X display whether the
+ [48]Q-46: Can I prompt the user at the local X display whether the
incoming VNC client should be accepted or not? Can I decide to make
some clients view-only? How about running an arbitrary program to make
the decisions?
- [48]Q-46: I start x11vnc as root because it is launched via inetd(8)
+ [49]Q-47: I start x11vnc as root because it is launched via inetd(8)
or a display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- [49]Q-47: I use a screen-lock when I leave my workstation (e.g.
+ [50]Q-48: I use a screen-lock when I leave my workstation (e.g.
xscreensaver or xlock.) When I remotely access my workstation desktop
via x11vnc I can unlock the desktop fine, but I am worried people will
see my activities on the physical monitor. What can I do to prevent
this, or at least make it more difficult?
- [50]Q-48: Can I have x11vnc automatically lock the screen when I
+ [51]Q-49: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
[Encrypted Connections]
- [51]Q-49: How can I tunnel my connection to x11vnc via an encrypted
+ [52]Q-50: How can I tunnel my connection to x11vnc via an encrypted
SSH channel between two Unix machines?
- [52]Q-50: How can I tunnel my connection to x11vnc via an encrypted
+ [53]Q-51: How can I tunnel my connection to x11vnc via an encrypted
SSH channel from Windows using an SSH client like Putty?
- [53]Q-51: How can I tunnel my connection to x11vnc via an encrypted
+ [54]Q-52: How can I tunnel my connection to x11vnc via an encrypted
SSL channel using an external tool like stunnel?
- [54]Q-52: Does x11vnc have built-in SSL tunneling?
+ [55]Q-53: Does x11vnc have built-in SSL tunneling?
- [55]Q-53: How do I use VNC Viewers with built-in SSL tunneling?
+ [56]Q-54: How do I use VNC Viewers with built-in SSL tunneling?
- [56]Q-54: How do I use the Java applet VNC Viewer with built-in SSL
+ [57]Q-55: How do I use the Java applet VNC Viewer with built-in SSL
tunneling when going through a Web Proxy?
- [57]Q-55: Can Apache web server act as a gateway for users to connect
+ [58]Q-56: Can Apache web server act as a gateway for users to connect
via SSL from the Internet with a Web browser to x11vnc running on
their workstations behind a firewall?
- [58]Q-56: Can I create and use my own SSL Certificate Authority (CA)
+ [59]Q-57: Can I create and use my own SSL Certificate Authority (CA)
with x11vnc?
[Display Managers and Services]
- [59]Q-57: How can I run x11vnc as a "service" that is always
+ [60]Q-58: How can I run x11vnc as a "service" that is always
available?
- [60]Q-58: How can I use x11vnc to connect to an X login screen like
+ [61]Q-59: How can I use x11vnc to connect to an X login screen like
xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into
an X session yet.)
- [61]Q-59: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
+ [62]Q-60: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
- [62]Q-60: Can I have x11vnc advertise its VNC service and port via
+ [63]Q-61: Can I have x11vnc advertise its VNC service and port via
mDNS / Zeroconf (e.g. Avahi) so VNC viewers on the local network can
detect it automatically?
- [63]Q-61: Can I have x11vnc allow a user to log in with her UNIX
+ [64]Q-62: Can I have x11vnc allow a user to log in with her UNIX
username and password and then have it find her X session display on
that machine and then connect to it? How about starting an X session
if one cannot be found?
- [64]Q-62: Can I have x11vnc restart itself after it terminates?
+ [65]Q-63: Can I have x11vnc restart itself after it terminates?
- [65]Q-63: How do I make x11vnc work with the Java VNC viewer applet in
+ [66]Q-64: How do I make x11vnc work with the Java VNC viewer applet in
a web browser?
- [66]Q-64: Are reverse connections (i.e. the VNC server connecting to
+ [67]Q-65: Are reverse connections (i.e. the VNC server connecting to
the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
- [67]Q-65: Can reverse connections be made to go through a Web or SOCKS
+ [68]Q-66: Can reverse connections be made to go through a Web or SOCKS
proxy or SSH?
- [68]Q-66: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
+ [69]Q-67: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a
real display, but for a virtual one I keep around.)
- [69]Q-67: How can I use x11vnc on "headless" machines? Why might I
+ [70]Q-68: How can I use x11vnc on "headless" machines? Why might I
want to?
[Resource Usage and Performance]
- [70]Q-68: I have lots of memory, but why does x11vnc fail with
+ [71]Q-69: I have lots of memory, but why does x11vnc fail with
shmget: No space left on device or Minor opcode of failed
request: 1 (X_ShmAttach)?
- [71]Q-69: How can I make x11vnc use less system resources?
+ [72]Q-70: How can I make x11vnc use less system resources?
- [72]Q-70: How can I make x11vnc use MORE system resources?
+ [73]Q-71: How can I make x11vnc use MORE system resources?
- [73]Q-71: I use x11vnc over a slow link with high latency (e.g. dialup
+ [74]Q-72: I use x11vnc over a slow link with high latency (e.g. dialup
modem or broadband), is there anything I can do to speed things up?
- [74]Q-72: Does x11vnc support the X DAMAGE Xserver extension to find
+ [75]Q-73: Does x11vnc support the X DAMAGE Xserver extension to find
modified regions of the screen quickly and efficiently?
- [75]Q-73: My OpenGL application shows no screen updates unless I
+ [76]Q-74: My OpenGL application shows no screen updates unless I
supply the -noxdamage option to x11vnc.
- [76]Q-74: When I drag windows around with the mouse or scroll up and
+ [77]Q-75: When I drag windows around with the mouse or scroll up and
down things really bog down (unless I do the drag in a single, quick
motion.) Is there anything to do to improve things?
- [77]Q-75: Why not do something like wireframe animations to avoid the
+ [78]Q-76: Why not do something like wireframe animations to avoid the
windows "lurching" when being moved or resized?
- [78]Q-76: Can x11vnc try to apply heuristics to detect when a window
+ [79]Q-77: Can x11vnc try to apply heuristics to detect when a window
is scrolling its contents and use the CopyRect encoding for a speedup?
- [79]Q-77: Can x11vnc do client-side caching of pixel data? I.e. so
+ [80]Q-78: Can x11vnc do client-side caching of pixel data? I.e. so
when that pixel data is needed again it does not have to be
retransmitted over the network.
- [80]Q-78: Does x11vnc support TurboVNC?
+ [81]Q-79: Does x11vnc support TurboVNC?
[Mouse Cursor Shapes]
- [81]Q-79: Why isn't the mouse cursor shape (the little icon shape
+ [82]Q-80: Why isn't the mouse cursor shape (the little icon shape
where the mouse pointer is) correct as I move from window to window?
- [82]Q-80: When using XFIXES cursorshape mode, some of the cursors look
+ [83]Q-81: When using XFIXES cursorshape mode, some of the cursors look
really bad with extra black borders around the cursor and other cruft.
How can I improve their appearance?
- [83]Q-81: In XFIXES mode, are there any hacks to handle cursor
+ [84]Q-82: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
[Mouse Pointer]
- [84]Q-82: Why does the mouse arrow just stay in one corner in my
+ [85]Q-83: Why does the mouse arrow just stay in one corner in my
vncviewer, whereas my cursor (that does move) is just a dot?
- [85]Q-83: Can I take advantage of the TightVNC extension to the VNC
+ [86]Q-84: Can I take advantage of the TightVNC extension to the VNC
protocol where Cursor Positions Updates are sent back to all connected
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- [86]Q-84: Is it possible to swap the mouse buttons (e.g. left-handed
+ [87]Q-85: Is it possible to swap the mouse buttons (e.g. left-handed
operation), or arbitrarily remap them? How about mapping button clicks
to keystrokes, e.g. to partially emulate Mouse wheel scrolling?
[Keyboard Issues]
- [87]Q-85: How can I get my AltGr and Shift modifiers to work between
+ [88]Q-86: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- [88]Q-86: When I try to type a "<" (i.e. less than) instead I get ">"
+ [89]Q-87: When I try to type a "<" (i.e. less than) instead I get ">"
(i.e. greater than)! Strangely, typing ">" works OK!!
- [89]Q-87: Extra Character Inserted, E.g.: When I try to type a "<"
+ [90]Q-88: Extra Character Inserted, E.g.: When I try to type a "<"
(i.e. less than) instead I get "<," (i.e. an extra comma.)
- [90]Q-88: I'm using an "international" keyboard (e.g. German "de", or
+ [91]Q-89: I'm using an "international" keyboard (e.g. German "de", or
Danish "dk") and the -modtweak mode works well if the VNC viewer is
run on a Unix/Linux machine with a similar keyboard. But if I run
the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or
Windows with any keyboard, I can't type some keys like: "@", "$",
"<", ">", etc. How can I fix this?
- [91]Q-89: When typing I sometimes get double, triple, or more of my
+ [92]Q-90: When typing I sometimes get double, triple, or more of my
keystrokes repeated. I'm sure I only typed them once, what can I do?
- [92]Q-90: The x11vnc -norepeat mode is in effect, but I still get
+ [93]Q-91: The x11vnc -norepeat mode is in effect, but I still get
repeated keystrokes!!
- [93]Q-91: After using x11vnc for a while, I find that I cannot type
+ [94]Q-92: After using x11vnc for a while, I find that I cannot type
some (or any) characters or my mouse clicks and drags no longer have
any effect, or they lead to strange effects. What happened?
- [94]Q-92: The machine where I run x11vnc has an AltGr key, but the
+ [95]Q-93: The machine where I run x11vnc has an AltGr key, but the
local machine where I run the VNC viewer does not. Is there a way I
can map a local unused key to send an AltGr? How about a Compose key
as well?
- [95]Q-93: I have a Sun machine I run x11vnc on. Its Sun keyboard has
+ [96]Q-94: I have a Sun machine I run x11vnc on. Its Sun keyboard has
just one Alt key labelled "Alt" and two Meta keys labelled with little
diamonds. The machine where I run the VNC viewer only has Alt keys.
How can I send a Meta keypress? (e.g. emacs needs this)
- [96]Q-94: Running x11vnc on HP-UX I cannot type "#" I just get a "3"
+ [97]Q-95: Running x11vnc on HP-UX I cannot type "#" I just get a "3"
instead.
- [97]Q-95: Can I map a keystroke to a mouse button click on the remote
+ [98]Q-96: Can I map a keystroke to a mouse button click on the remote
machine?
- [98]Q-96: How can I get Caps_Lock to work between my VNC viewer and
+ [99]Q-97: How can I get Caps_Lock to work between my VNC viewer and
x11vnc?
[Screen Related Issues and Features]
- [99]Q-97: The remote display is larger (in number of pixels) than the
+ [100]Q-98: The remote display is larger (in number of pixels) than the
local display I am running the vncviewer on. I don't like the
vncviewer scrollbars, what I can do?
- [100]Q-98: Does x11vnc support server-side framebuffer scaling? (E.g.
+ [101]Q-99: Does x11vnc support server-side framebuffer scaling? (E.g.
to make the desktop smaller.)
- [101]Q-99: Does x11vnc work with Xinerama? (i.e. multiple monitors
+ [102]Q-100: Does x11vnc work with Xinerama? (i.e. multiple monitors
joined together to form one big, single screen.)
- [102]Q-100: Can I use x11vnc on a multi-headed display that is not
+ [103]Q-101: Can I use x11vnc on a multi-headed display that is not
Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)?
- [103]Q-101: Can x11vnc show only a portion of the display? (E.g. for a
+ [104]Q-102: Can x11vnc show only a portion of the display? (E.g. for a
special purpose application or a very large screen.)
- [104]Q-102: Does x11vnc support the XRANDR (X Resize, Rotate and
+ [105]Q-103: Does x11vnc support the XRANDR (X Resize, Rotate and
Reflection) extension? Whenever I rotate or resize the screen x11vnc
just seems to crash.
- [105]Q-103: Independent of any XRANDR, can I have x11vnc rotate and/or
+ [106]Q-104: Independent of any XRANDR, can I have x11vnc rotate and/or
reflect the screen that the VNC viewers see? (e.g. for a handheld
whose screen is rotated 90 degrees.)
- [106]Q-104: Why is the view in my VNC viewer completely black? Or why
+ [107]Q-105: Why is the view in my VNC viewer completely black? Or why
is everything flashing around randomly?
- [107]Q-105: I use Linux Virtual Terminals (VT's) to implement 'Fast
+ [108]Q-106: I use Linux Virtual Terminals (VT's) to implement 'Fast
User Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7,
Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those
keystrokes to switch between their sessions.) How come the view in a
@@ -2132,83 +2152,83 @@ http://www.karlrunge.com/x11vnc/faq.html:
otherwise all messed up unless the X session x11vnc is attached to is
in the active VT?
- [108]Q-106: I am using x11vnc where my local machine has "popup/hidden
+ [109]Q-107: I am using x11vnc where my local machine has "popup/hidden
taskbars" and the remote display where x11vnc runs also has
"popup/hidden taskbars" and they interfere and fight with each other.
What can I do?
- [109]Q-107: Help! x11vnc and my KDE screensaver keep switching each
+ [110]Q-108: Help! x11vnc and my KDE screensaver keep switching each
other on and off every few seconds.
- [110]Q-108: I am running the beryl 3D window manager (or compiz,
+ [111]Q-109: I am running the beryl 3D window manager (or compiz,
MythTv, Google Earth, or some other OpenGL app) and I do not get
screen updates in x11vnc.
- [111]Q-109: Can I use x11vnc to view my VMWare session remotely?
+ [112]Q-110: Can I use x11vnc to view my VMWare session remotely?
[Exporting non-X11 devices via VNC]
- [112]Q-110: Can non-X devices (e.g. a raw framebuffer) be viewed (and
+ [113]Q-111: Can non-X devices (e.g. a raw framebuffer) be viewed (and
even controlled) via VNC with x11vnc?
- [113]Q-111: Can I export the Linux Console (Virtual Terminals) via VNC
+ [114]Q-112: Can I export the Linux Console (Virtual Terminals) via VNC
using x11vnc?
- [114]Q-112: Can I export via VNC a Webcam or TV tuner framebuffer
+ [115]Q-113: Can I export via VNC a Webcam or TV tuner framebuffer
using x11vnc?
- [115]Q-113: Can I connect via VNC to a Qt-embedded/Qtopia application
+ [116]Q-114: Can I connect via VNC to a Qt-embedded/Qtopia application
running on my handheld or PC using the Linux console framebuffer (i.e.
not X11)?
- [116]Q-114: Now that non-X11 devices can be exported via VNC using
+ [117]Q-115: Now that non-X11 devices can be exported via VNC using
x11vnc, can I build it with no dependencies on X11 header files and
libraries?
- [117]Q-115: Does x11vnc support Mac OS X Aqua/Quartz displays natively
+ [118]Q-116: Does x11vnc support Mac OS X Aqua/Quartz displays natively
(i.e. no X11 involved)?
- [118]Q-116: Can x11vnc be used as a VNC reflector/repeater to improve
+ [119]Q-117: Can x11vnc be used as a VNC reflector/repeater to improve
performance for the case of a large number of simultaneous VNC viewers
(e.g. classroom broadcasting or a large demo)?
- [119]Q-117: Can x11vnc be used during a Linux, Solaris, etc. system
+ [120]Q-118: Can x11vnc be used during a Linux, Solaris, etc. system
Installation so the Installation can be done remotely?
[Misc: Clipboard, File Transfer/Sharing, Printing, Sound, Beeps,
Thanks, etc.]
- [120]Q-118: Does the Clipboard/Selection get transferred between the
+ [121]Q-119: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
- [121]Q-119: Can I use x11vnc to record a Shock Wave Flash (or other
+ [122]Q-120: Can I use x11vnc to record a Shock Wave Flash (or other
format) video of my desktop, e.g. to record a tutorial or demo?
- [122]Q-120: Can I transfer files back and forth with x11vnc?
+ [123]Q-121: Can I transfer files back and forth with x11vnc?
- [123]Q-121: Which UltraVNC extensions are supported?
+ [124]Q-122: Which UltraVNC extensions are supported?
- [124]Q-122: Can x11vnc emulate UltraVNC's Single Click helpdesk mode
+ [125]Q-123: Can x11vnc emulate UltraVNC's Single Click helpdesk mode
for Unix? I.e. something very simple for a naive user to initiate a
reverse vnc connection from their Unix desktop to a helpdesk
operator's VNC Viewer.
- [125]Q-123: Can I (temporarily) mount my local (viewer-side)
+ [126]Q-124: Can I (temporarily) mount my local (viewer-side)
Windows/Samba File share on the machine where x11vnc is running?
- [126]Q-124: Can I redirect CUPS print jobs from the remote desktop
+ [127]Q-125: Can I redirect CUPS print jobs from the remote desktop
where x11vnc is running to a printer on my local (viewer-side)
machine?
- [127]Q-125: How can I hear the sound (audio) from the remote
+ [128]Q-126: How can I hear the sound (audio) from the remote
applications on the desktop I am viewing via x11vnc?
- [128]Q-126: Why don't I hear the "Beeps" in my X session (e.g. when
+ [129]Q-127: Why don't I hear the "Beeps" in my X session (e.g. when
typing tput bel in an xterm)?
- [129]Q-127: Does x11vnc work with IPv6?
+ [130]Q-128: Does x11vnc work with IPv6?
- [130]Q-128: Thanks for your program and for your help! Can I make a
+ [131]Q-129: Thanks for your program and for your help! Can I make a
donation?
_________________________________________________________________
@@ -2221,7 +2241,7 @@ http://www.karlrunge.com/x11vnc/faq.html:
For the former error, you need to specify the X display to connect to
(it also needs to be on the same machine the x11vnc process is to run
- on.) Set your DISPLAY environment variable (or use the [131]-display
+ on.) Set your DISPLAY environment variable (or use the [132]-display
option) to specify it. Nearly always the correct value will be ":0"
(in fact, x11vnc will now assume :0 if given no other information.)
@@ -2238,9 +2258,9 @@ http://www.karlrunge.com/x11vnc/faq.html:
working when you try to start x11vnc via, say, a remote shell.
How to Solve: See the xauth(1), Xsecurity(7), and xhost(1) man pages
- or [132]this Howto for much info on X11 permissions. For example, you
+ or [133]this Howto for much info on X11 permissions. For example, you
may need to set your XAUTHORITY environment variable (or use the
- [133]-auth option) to point to the correct MIT-MAGIC-COOKIE file (e.g.
+ [134]-auth option) to point to the correct MIT-MAGIC-COOKIE file (e.g.
/home/joe/.Xauthority or /var/gdm/:0.Xauth or /var/lib/kdm/A:0-crWk72K
or /tmp/.gdmzndVlR, etc, etc.), or simply be sure you run x11vnc as
the correct user (i.e. the user who is logged into the X session you
@@ -2262,10 +2282,10 @@ http://www.karlrunge.com/x11vnc/faq.html:
x11vnc -display :0 -auth /var/gdm/:0.Xauth
(this is for the display manager gdm and requires root permission to
- read the gdm cookie file, see [134]this faq for other display manager
+ read the gdm cookie file, see [135]this faq for other display manager
cookie file names.)
- Note as of Feb/2007 you can also try the [135]-find option instead of
+ Note as of Feb/2007 you can also try the [136]-find option instead of
"-display ..." and see if that finds your display and Xauthority.
Less safe, but to avoid figuring out where the correct XAUTHORITY file
@@ -2274,7 +2294,7 @@ http://www.karlrunge.com/x11vnc/faq.html:
(from the same machine.) The person could then type "xhost -localhost"
after x11vnc has connected to go back to the default permissions.
Also, for some situations the "-users lurk=" option may soon be of use
- (please read the documentation on the [136]-users option.)
+ (please read the documentation on the [137]-users option.)
To test out your X11 permissions from a remote shell, set DISPLAY and
possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on
@@ -2293,7 +2313,7 @@ http://www.karlrunge.com/x11vnc/faq.html:
properly.)
Firewalls: Speaking of permissions, it should go without saying that
- the host-level [137]firewall will need to be configured to allow
+ the host-level [138]firewall will need to be configured to allow
connections in on a port. E.g. 5900 (default VNC port) or 22 (default
SSH port for tunnelling VNC.) Most systems these days have firewalls
turned on by default, so you will actively have to do something to
@@ -2372,7 +2392,7 @@ libssl.so libcrypto.so libcrypt.so
the above list may be out of date. So only use the above lists as
hints for the package names that are needed.
- Have a look at [138]Misc. Build Problems for additional fixes.
+ Have a look at [139]Misc. Build Problems for additional fixes.
Note: there is growing trend in Linux and other distros to slice up
core X11 software into more and smaller packages. So be prepared for
@@ -2390,7 +2410,7 @@ libssl.so libcrypto.so libcrypt.so
ii libssl0.9.8 0.9.8a-7ubuntu SSL shared libraries
(in fact it should have installed both by default if it knew what it
- was doing.) See [139]here too.
+ was doing.) See [140]here too.
Q-3: I just built x11vnc successfully, but when I use it my keystrokes
@@ -2464,7 +2484,7 @@ h
earlier and perhaps non-Solaris):
First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
- above [140]Solaris build script to run the configure command. That
+ above [141]Solaris build script to run the configure command. That
should succeed without failure. Then you have to hand edit the
autogenerated rfb/rfbconfig.h file in the source tree, and just before
the last #endif at the bottom of that file insert these workaround
@@ -2490,7 +2510,7 @@ typedef unsigned int in_addr_t;
on other older OS (Solaris, Linux, ...) releases.
Here are some notes for similar steps that need to be done to build on
- [141]SunOS 4.x
+ [142]SunOS 4.x
Please let us know if you had to use the above workaround (and whether
it worked or not.) If there is enough demand we will try to push clean
@@ -2500,33 +2520,32 @@ typedef unsigned int in_addr_t;
Q-5: Where can I get a precompiled x11vnc binary for my Operating
System?
- Hopefully the [142]build steps above and [143]FAQ provide enough info
+ Hopefully the [143]build steps above and [144]FAQ provide enough info
for a painless compile for most environments. Please report problems
with the x11vnc configure, make, etc. on your system (if your system
is known to compile other GNU packages successfully.)
There are precompiled x11vnc binaries built by other groups that are
available at the following locations:
- Slackware: (.tgz) [144]http://www.linuxpackages.net/
-
- SuSE: (.rpm) [145]http:/software.opensuse.org/ Gentoo: (info)
- [146]http://gentoo-wiki.com/ and [147]http://gentoo-portage.com/
- FreeBSD: (.tbz) [148]http://www.freebsd.org/
- [149]http://www.freshports.org/net/x11vnc NetBSD: (src)
- [150]http://pkgsrc.se/x11/x11vnc OpenBSD: (.tgz)
- [151]http://openports.se/ Arch Linux: (.tgz)
- [152]http://www.archlinux.org/ Nokia 770 (.deb)
- [153]http://mike.saunby.googlepages.com/x11vncfornokia7702 Sharp
- Zaurus [154]http://www.focv.com/ Redhat/Fedora: (.rpm)
- [155]http://packages.sw.be/x11vnc RPMforge
- [156]http://dag.wieers.com/rpm/packages/x11vnc/ (N.B.: unmaintained
- after 0.9.3) Debian: (.deb) [157]http://packages.debian.org/x11vnc
- (N.B: often unmaintained; better to compile from source) Solaris:
- (pkg) [158]http://www.sunfreeware.com/ (N.B: very old; better to
- compile from source)
+ Slackware: (.tgz) [145]http://www.linuxpackages.net/
+
+ SuSE: (.rpm) [146]http:/software.opensuse.org/ Gentoo: (info)
+ [147]http://gentoo-wiki.com/ and [148]http://gentoo-portage.com/
+ FreeBSD: (.tbz) [149]http://www.freebsd.org/
+ [150]http://www.freshports.org/net/x11vnc NetBSD: (src)
+ [151]http://pkgsrc.se/x11/x11vnc OpenBSD: (.tgz)
+ [152]http://openports.se/ Arch Linux: (.tgz)
+ [153]http://www.archlinux.org/ Nokia 770 (.deb)
+ [154]http://mike.saunby.googlepages.com/x11vncfornokia7702 Sharp
+ Zaurus [155]http://www.focv.com/ Debian: (.deb)
+ [156]http://packages.debian.org/x11vnc Redhat/Fedora: (.rpm)
+ [157]http://packages.sw.be/x11vnc RPMforge
+ [158]http://dag.wieers.com/rpm/packages/x11vnc/ (N.B.: unmaintained
+ after 0.9.3) Solaris: (pkg) [159]http://www.sunfreeware.com/ (N.B:
+ very old; better to compile from source)
If the above binaries don't work and building x11vnc on your OS fails
- (and all else fails!) you can try one of [159]My Collection of x11vnc
+ (and all else fails!) you can try one of [160]My Collection of x11vnc
Binaries for various OS's and x11vnc releases.
As a general note, the x11vnc program is simple enough you don't
@@ -2544,7 +2563,7 @@ typedef unsigned int in_addr_t;
If you use a standalone binary like this and also want x11vnc to serve
up the Java VNC Viewer jar file (either SSL enabled or regular one),
then you will need to extract the classes subdirectory from the source
- tarball and point x11vnc to it via the [160]-httpdir option. E.g.:
+ tarball and point x11vnc to it via the [161]-httpdir option. E.g.:
x11vnc -httpdir /path/to/x11vnc-0.8.3/classes/ssl ...
@@ -2553,11 +2572,11 @@ typedef unsigned int in_addr_t;
To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
try here:
- * [161]http://www.tightvnc.com/download.html
- * [162]http://www.realvnc.com/download-free.html
- * [163]http://sourceforge.net/projects/cotvnc/
- * [164]http://www.ultravnc.com/
- * [165]Our Enhanced TightVNC Viewer (SSVNC)
+ * [162]http://www.tightvnc.com/download.html
+ * [163]http://www.realvnc.com/download-free.html
+ * [164]http://sourceforge.net/projects/cotvnc/
+ * [165]http://www.ultravnc.com/
+ * [166]Our Enhanced TightVNC Viewer (SSVNC)
[ssvnc.gif]
@@ -2567,7 +2586,7 @@ typedef unsigned int in_addr_t;
Run: x11vnc -opts to list just the option names or run: x11vnc
-help for long descriptions about each option. The output is listed
- [166]here as well. Yes, x11vnc does have a lot of options, doesn't
+ [167]here as well. Yes, x11vnc does have a lot of options, doesn't
it...
@@ -2599,10 +2618,10 @@ display :0
program is needed for operation. The gui is not particularly
user-friendly, it just provides a point and click mode to set all the
many x11vnc parameters and obtain help on them. It is also very useful
- for testing. See the [167]-gui option for more info. Examples: "x11vnc
+ for testing. See the [168]-gui option for more info. Examples: "x11vnc
... -gui" and "x11vnc ... -gui other:0" in the latter case the gui is
displayed on other:0, not the X display x11vnc is polling. There is
- also a "[168]-gui tray" system tray mode.
+ also a "[169]-gui tray" system tray mode.
[tkx11vnc.gif]
@@ -2616,7 +2635,7 @@ display :0
smaller, simpler icon?
As of Jul/2005 the gui can run in a more friendly small icon mode
- "[169]-gui icon" or in the system tray: "[170]-gui tray". It has
+ "[170]-gui icon" or in the system tray: "[171]-gui tray". It has
balloon status, a simple menu, and a Properities dialog. The full,
complicated, gui is only available under "Advanced". Other
improvements were added as well. Try "Misc -> simple_gui" for a gui
@@ -2652,18 +2671,18 @@ LAY
PORT=59xx line to see which port it found, then subtract 5900 from it
for the VNC display number to enter into the VNC Viewer(s).
- The "[171]-N" option will try to match the VNC display number to the X
+ The "[172]-N" option will try to match the VNC display number to the X
display (e.g. X11 DISPLAY of :5 (port 6005) will have VNC display :5
(port 5905).)
- Also see the "[172]-autoport n" option to indicated at which value the
+ Also see the "[173]-autoport n" option to indicated at which value the
auto probing should start at.
Q-11: My Firewall/Router doesn't allow VNC Viewers to connect to
x11vnc.
- See the [173]Firewalls/Routers discussion.
+ See the [174]Firewalls/Routers discussion.
Q-12: Is it possible for a VNC Viewer and a VNC Server to connect to
@@ -2677,7 +2696,7 @@ LAY
In the following discussion, we will suppose port 5950 is being used
on the relay machine as the VNC port for the rendezvous.
- A way to rendezvous is to have the VNC Server start a [174]reverse
+ A way to rendezvous is to have the VNC Server start a [175]reverse
connection to the relay machine:
x11vnc -connect third-machine.net:5950 ...
@@ -2696,11 +2715,11 @@ LAY
the owner to allow you to install this software (and he would likely
need to open his server's firewall to allow the port through.)
- It is recommended that [175]SSL is used for encryption (e.g.
- "[176]-ssl SAVE") when going over the internet.
+ It is recommended that [176]SSL is used for encryption (e.g.
+ "[177]-ssl SAVE") when going over the internet.
We have a prototype for performing a rendezvous via a Web Server
- acting as the relay machine. Download the [177]vncxfer CGI script and
+ acting as the relay machine. Download the [178]vncxfer CGI script and
see the instructions at the top.
Once that CGI script is set up on the website, both users go to, say,
@@ -2730,7 +2749,7 @@ LAY
port requirement (e.g. use HTTP/CGI itself for the transfer... it is
difficult to emulate a full-duplex TCP connection with them.)
- See also the [178]Firewalls/Routers discussion and [179]Reverse
+ See also the [179]Firewalls/Routers discussion and [180]Reverse
Connection Proxy discussion.
@@ -2758,7 +2777,7 @@ LAY
vncviewer -encodings "copyrect tight zrle hextile" localhost:0
(we assume the old-style -encodings option needs to be used. See
- [180]here for details.)
+ [181]here for details.)
If the SSH machine has been configured (see sshd_config(5)) with the
option GatewayPorts=yes, then the tunnel set up by the VNC Server will
@@ -2768,16 +2787,16 @@ LAY
only runs:
vncviewer third-machine.net:33
- In this case we recommend [181]SSL be used for encryption.
+ In this case we recommend [182]SSL be used for encryption.
The creation of both tunnels can be automated. As of Oct/2007 the
- [182]-ssh x11vnc option is available and so only this command needs to
+ [183]-ssh x11vnc option is available and so only this command needs to
be run on the VNC Server side:
x11vnc -ssh [email protected]:33 ...
(the SSH passphrase may need to be supplied.)
- To automate on the VNC Viewer side, the user can use the [183]Enhanced
+ To automate on the VNC Viewer side, the user can use the [184]Enhanced
TightVNC Viewer (SSVNC) by:
* Clicking on 'Use SSH'
* Entering [email protected]:33 into 'VNC Host:Display' entry
@@ -2794,11 +2813,11 @@ LAY
Q-13: Can I make x11vnc more quiet and also go into the background
after starting up?
- Use the [184]-q and [185]-bg options, respectively. (also: -quiet is
+ Use the [185]-q and [186]-bg options, respectively. (also: -quiet is
an alias for -q)
Note that under -bg the stderr messages will be lost unless you use
- the "[186]-o logfile" option.
+ the "[187]-o logfile" option.
Q-14: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
@@ -2824,8 +2843,8 @@ LAY
Q-16: KDE's krdc VNC viewer cannot connect to x11vnc.
- This has been fixed in x11vnc version 0.8.4. More info [187]here,
- [188]here, and [189]here.
+ This has been fixed in x11vnc version 0.8.4. More info [188]here,
+ [189]here, and [190]here.
Q-17: When I start x11vnc on an Alpha Tru64 workstation the X server
@@ -2835,15 +2854,28 @@ LAY
able to crash it.
The problem seems to be with the RECORD X extension and so a
- workaround is to use the "[190]-noxrecord" x11vnc command line option.
+ workaround is to use the "[191]-noxrecord" x11vnc command line option.
- Q-18: Are there any build-time customizations possible, e.g. change
+ Q-18: When running x11vnc on an IBM AIX workstation after a few
+ minutes the VNC connection freezes.
+
+ One user reports when running x11vnc on AIX 5.3 in his CDE session
+ after a few minutes or seconds x11vnc will "freeze" (no more updates
+ being sent, etc.) The freezing appeared to be worse for versions later
+ than 0.9.2.
+
+ The problem seems to be with the RECORD X extension on AIX and so a
+ workaround is to use the "[192]-noxrecord" x11vnc command line option.
+ The user found no freezes occurred when using that option.
+
+
+ Q-19: Are there any build-time customizations possible, e.g. change
defaults, create a smaller binary, etc?
There are some options. They are enabled by adding something like
-Dxxxx=1 to the CPPFLAGS environment variable before running configure
- (see the [191]build notes for general background.)
+ (see the [193]build notes for general background.)
/*
* Mar/2006
* Build-time customization via CPPFLAGS.
@@ -2909,31 +2941,31 @@ LAY
[Win2VNC Related]
- Q-19: I have two separate machine displays in front of me, one Windows
+ Q-20: I have two separate machine displays in front of me, one Windows
the other X11: can I use x11vnc in combination with Win2VNC in
dual-screen mode to pass the keystrokes and mouse motions to the X11
display?
- Yes, for best response start up x11vnc with the "[192]-nofb" option
+ Yes, for best response start up x11vnc with the "[194]-nofb" option
(disables framebuffer polling, and does other optimizations) on the
secondary display (X11) machine. Then start up Win2VNC on the primary
display (Windows) referring it to the secondary display.
- This will also work X11 to X11 using [193]x2vnc, however you would
+ This will also work X11 to X11 using [195]x2vnc, however you would
probably just want to avoid VNC and use x2x for that.
For reference, here are some links to Win2VNC-like programs for
multiple monitor setups:
- * [194]Original Win2VNC
- * [195]Enhanced Win2VNC (broken?) and [196]sourceforge link
- * [197]x2vnc
- * [198]x2x
- * [199]zvnc (MorphOS)
+ * [196]Original Win2VNC
+ * [197]Enhanced Win2VNC (broken?) and [198]sourceforge link
+ * [199]x2vnc
+ * [200]x2x
+ * [201]zvnc (MorphOS)
All of them will work with x11vnc (except x2x where it is not needed.)
- Q-20: I am running Win2VNC on my Windows machine and "x11vnc -nofb" on
+ Q-21: I am running Win2VNC on my Windows machine and "x11vnc -nofb" on
Unix to pass keyboard and mouse to the Unix monitor. Whenever I start
Win2VNC it quickly disconnects and x11vnc says:
rfbProcessClientNormalMessage: read: Connection reset by peer
@@ -2948,7 +2980,7 @@ LAY
on your display to be depth 24 TrueColor? Sun machines often have 8+24
overlay/multi-depth visuals, and you can make the default visual depth
24 TrueColor (see fbconfig(1) and Xsun(1).) 2) As of Feb/2004 x11vnc
- has the [200]-visual option to allow you to force the framebuffer
+ has the [202]-visual option to allow you to force the framebuffer
visual to whatever you want (this usually messes up the colors unless
you are very clever.) In this case, the option provides a convenient
workaround for the Win2VNC bug:
@@ -2958,22 +2990,22 @@ LAY
this. Since Win2VNC does not use the framebuffer data there should be
no problems in doing this.
- Q-21: Can I run "x11vnc -nofb" on a Mac OS X machine to redirect mouse
+ Q-22: Can I run "x11vnc -nofb" on a Mac OS X machine to redirect mouse
and keyboard input to it from Windows and X11 machines via Win2VNC and
x2vnc, respectively?
- Yes, as of Nov/2006 [201]you can. There may be a trick or two you'll
+ Yes, as of Nov/2006 [203]you can. There may be a trick or two you'll
need to do to get the Clipboard exchange between the machines to work.
[Color Issues]
- Q-22: The X display I run x11vnc on is only 8 bits per pixel (bpp)
+ Q-23: The X display I run x11vnc on is only 8 bits per pixel (bpp)
PseudoColor (i.e. only 256 distinct colors.) The x11vnc colors may
start out OK, but after a while they are incorrect in certain windows.
- Use the [202]-flashcmap option to have x11vnc watch for changes in the
+ Use the [204]-flashcmap option to have x11vnc watch for changes in the
colormap, and propagate those changes back to connected clients. This
can be slow (since the whole screen must be updated over the network
whenever the colormap changes.) This flashing colormap behavior often
@@ -2982,30 +3014,30 @@ LAY
example of this. Consider reconfiguring the system to 16 bpp or depth
24 TrueColor if at all possible.
- Also note the option [203]-8to24 (Jan/2006) can often remove the need
+ Also note the option [205]-8to24 (Jan/2006) can often remove the need
for flashing the colormap. Everything is dynamically transformed to
depth 24 at 32 bpp using the colormaps. There may be painting errors
however (see the following FAQ for tips on reducing and correcting
them.)
- In some rare cases (SCO unixware) the [204]-notruecolor option has
+ In some rare cases (SCO unixware) the [206]-notruecolor option has
corrected colors on 8bpp displays. The red, green, and blue masks were
non-zero in 8bpp PseudoColor on an obscure setup, and this option
corrected the problems.
- Q-23: Color problems: Why are the colors for some windows incorrect in
+ Q-24: Color problems: Why are the colors for some windows incorrect in
x11vnc? BTW, my X display has nice overlay/multi-depth visuals of
different color depths: e.g. there are both depth 8 and 24 visuals
available at the same time.
- You may want to review the [205]previous question regarding 8 bpp
+ You may want to review the [207]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC and SGI), the [206]-overlay option
+ On some hardware (Sun/SPARC and SGI), the [208]-overlay option
discussed a couple paragraphs down may solve this for you (you may
want to skip to it directly.) On other hardware the less robust
- [207]-8to24 option may help (also discussed below.)
+ [209]-8to24 option may help (also discussed below.)
Run xdpyinfo(1) to see what the default visual is and what the depths
of the other visuals are. Does the default visual have a depth of 8
@@ -3041,7 +3073,7 @@ TrueColor defdepth 24
The -overlay mode: Another option is if the system with overlay
visuals is a Sun system running Solaris or SGI running IRIX you can
- use the [208]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+ use the [210]-overlay x11vnc option (Aug/2004) to have x11vnc use the
Solaris XReadScreen(3X11) function to poll the "true view" of the
whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on
IRIX. This is useful for Legacy applications (older versions of
@@ -3066,7 +3098,7 @@ TrueColor defdepth 24
Xsun, e.g. in your /etc/dt/config/Xservers file.)
- The -8to24 mode: The [209]-8to24 x11vnc option (Jan/2006) is a kludge
+ The -8to24 mode: The [211]-8to24 x11vnc option (Jan/2006) is a kludge
to try to dynamically rewrite the pixel values so that the 8bpp part
of the screen is mapped onto depth 24 TrueColor. This is less robust
than the -overlay mode because it is done by x11vnc outside of the X
@@ -3080,11 +3112,11 @@ TrueColor defdepth 24
32bpp view is exported via VNC.
Even on pure 8bpp displays it can be used as an alternative to
- [210]-flashcmap to avoid color flashing completely.
+ [212]-flashcmap to avoid color flashing completely.
This scheme is approximate and can often lead to painting errors. You
can manually correct most painting errors by pressing 3 Alt_L's in a
- row, or by using something like: [211]-fixscreen V=3.0 to
+ row, or by using something like: [213]-fixscreen V=3.0 to
automatically refresh the screen every 3 seconds. Also -fixscreen
8=3.0 has been added to just refresh the non-default visual parts of
the screen.
@@ -3097,27 +3129,27 @@ TrueColor defdepth 24
nogetimage can give a nice speedup if the default depth 24 X server
supports hiding the 8bpp bits in bits 25-32 of the framebuffer data.
On very slow machines -8to24 poll=0.2,cachewin=5.0 gives an useful
- speedup. See the [212]-8to24 help description for information on
+ speedup. See the [214]-8to24 help description for information on
tunable parameters, etc.
Colors still not working correctly? Run xwininfo on the application
with the incorrect colors to verify that the depth of its visual is
different from the default visual depth (gotten from xdpyinfo.) One
- possible workaround in this case is to use the [213]-id option to
+ possible workaround in this case is to use the [215]-id option to
point x11vnc at the application window itself. If the application is
complicated (lots of toplevel windows and popup menus) this may not be
acceptable, and may even crash x11vnc (but not the application.)
It is theoretically possible to solve this problem in general (see
xwd(1) for example), but it does not seem trivial or sufficiently fast
- for x11vnc to be able to do so in real time. The [214]-8to24 method
+ for x11vnc to be able to do so in real time. The [216]-8to24 method
does this approximately and is somewhat usable. Fortunately the
- [215]-overlay option works for Solaris machines with overlay visuals
+ [217]-overlay option works for Solaris machines with overlay visuals
where most of this problem occurs.
- Q-24: I am on a high color system (depth >= 24) but I seem to have
+ Q-25: I am on a high color system (depth >= 24) but I seem to have
colormap problems. They either flash or everything is very dark.
This can happen if the default Visual (use xdpyinfo to list them) is
@@ -3142,22 +3174,22 @@ TrueColor defdepth 24
can make xwud do this for example.
- Q-25: How do I figure out the window id to supply to the -id windowid
+ Q-26: How do I figure out the window id to supply to the -id windowid
option?
Run the xwininfo program in a terminal. It will ask you to click on
the desired application window. After clicking, it will print out much
information, including the window id (e.g. 0x6000010.) Also, the
visual and depth of the window printed out is often useful in
- debugging x11vnc [216]color problems.
+ debugging x11vnc [218]color problems.
- Also, as of Dec/2004 you can use "[217]-id pick" to have x11vnc run
+ Also, as of Dec/2004 you can use "[219]-id pick" to have x11vnc run
xwininfo(1) for you and after you click the window it extracts the
windowid. Besides "pick" there is also "id:root" to allow you to go
back to root window when doing remote-control.
- Q-26: Why don't menus or other transient windows come up when I am
+ Q-27: Why don't menus or other transient windows come up when I am
using the -id windowid option to view a single application window?
This is related to the behavior of the XGetImage(3X11) and
@@ -3169,10 +3201,10 @@ TrueColor defdepth 24
you should be able to see these transient windows.
If things are not working and you still want to do the single window
- polling, try the [218]-sid windowid option ("shifted" windowid.)
+ polling, try the [220]-sid windowid option ("shifted" windowid.)
- Q-27: My X display is depth 24 at 24bpp (instead of the normal depth
+ Q-28: My X display is depth 24 at 24bpp (instead of the normal depth
24 at 32bpp.) I'm having lots of color and visual problems with x11vnc
and/or vncviewer. What's up?
@@ -3205,7 +3237,7 @@ TrueColor defdepth 24
handle 24bpp from the server, so you may want to use those. They
evidently request 32 bpp and libvncserver obliges.
- Update: as of Apr/2006 you can use the [219]-24to32 option to have
+ Update: as of Apr/2006 you can use the [221]-24to32 option to have
x11vnc dynamically transform the 24bpp pixel data to 32bpp. This extra
transformation could slow things down further however.
@@ -3215,14 +3247,14 @@ TrueColor defdepth 24
couldn't find suitable pixmap format" so evidently you cannot use
24bpp for the vncviewers to work on that X display.
- Note, however, that the Unix viewer in the [220]Enhanced TightVNC
+ Note, however, that the Unix viewer in the [222]Enhanced TightVNC
Viewer (SSVNC) project can handle 24bpp X displays. It does this by
requesting a 16bpp pixel format (or 8bpp if the -bgr233 option has
been supplied) from the VNC server, and translates that to 24bpp
locally.
[Xterminals]
- Q-28: Can I use x11vnc to view and interact with an Xterminal (e.g.
+ Q-29: Can I use x11vnc to view and interact with an Xterminal (e.g.
NCD) that is not running UNIX and so x11vnc cannot be run on it
directly?
@@ -3230,9 +3262,9 @@ TrueColor defdepth 24
since you will be polling the X display over the network as opposed to
over the local hardware. To do this, run x11vnc on a UNIX machine as
close as possible network-wise (e.g. same switch) to the Xterminal
- machine. Use the [221]-display option to point the display to that of
+ machine. Use the [223]-display option to point the display to that of
the Xterminal (you'll of course need basic X11 permission to do that)
- and finally supply the [222]-noshm option (this enables the polling
+ and finally supply the [224]-noshm option (this enables the polling
over the network.)
If the Xterminal's X display is open to the network for connections,
@@ -3245,10 +3277,10 @@ TrueColor defdepth 24
The response will likely be sluggish (maybe only one "frame" per
second.) This mode is not recommended except for "quick checks" of
hard to get to X servers. Use something like "-wait 150" to cut down
- on the polling rate. You may also need [223]-flipbyteorder if the
+ on the polling rate. You may also need [225]-flipbyteorder if the
colors get messed up due to endian byte order differences.
- Q-29: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct
+ Q-30: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct
for a Unix/Linux machine acting as an Xterminal?
If the X display machine is a traditional Xterminal (where the X
@@ -3269,7 +3301,7 @@ TrueColor defdepth 24
copied to the Xterminal. If $HOME/.Xauthority is exported via NFS
(this is insecure of course, but has been going on for decades), then
x11vnc can simply pick it up via NFS (you may need to use the
- [224]-auth option to point to the correct file.) Other options include
+ [226]-auth option to point to the correct file.) Other options include
copying the auth file using scp, or something like:
central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
@@ -3281,7 +3313,7 @@ TrueColor defdepth 24
details.
If the display name in the cookie file needs to be changed between the
- two hosts, see [225]this note on the "xauth add ..." command.
+ two hosts, see [227]this note on the "xauth add ..." command.
A less secure option is to run something like "xhost +127.0.0.1" while
sitting at the Xterminal box to allow cookie-free local access for
@@ -3295,7 +3327,7 @@ TrueColor defdepth 24
occasional app more efficiently locally on the Xterminal box (e.g.
realplayer.)
- Not recommended, but as a last resort, you could have x11vnc [226]poll
+ Not recommended, but as a last resort, you could have x11vnc [228]poll
the Xterminal Display over the network. For this you would run a
"x11vnc -noshm ..." process on the central-server (and hope the
network admin doesn't get angry...)
@@ -3322,36 +3354,36 @@ TrueColor defdepth 24
[Sun Rays]
- Q-30: I'm having trouble using x11vnc with my Sun Ray session.
+ Q-31: I'm having trouble using x11vnc with my Sun Ray session.
- The [227]Sun Ray technology is a bit like "VNC done in hardware" (the
+ The [229]Sun Ray technology is a bit like "VNC done in hardware" (the
Sun Ray terminal device, DTU, playing the role of the vncviewer.)
Completely independent of that, the SunRay user's session is still an
X server that speaks the X11 protocol and so x11vnc simply talks to
the X server part to export the SunRay desktop to any place in the
world (i.e. not only to a Sun Ray terminal device), creating a sort of
- "Soft Ray". Please see [228]this discussion of Sun Ray issues for
+ "Soft Ray". Please see [230]this discussion of Sun Ray issues for
solutions to problems.
- Also see the [229]Sun Ray Remote Control Toolkit that uses x11vnc.
+ Also see the [231]Sun Ray Remote Control Toolkit that uses x11vnc.
[Remote Control]
- Q-31: How do I stop x11vnc once it is running in the background?
+ Q-32: How do I stop x11vnc once it is running in the background?
As of Dec/2004 there is a remote control feature. It can change a huge
- number of parameters on the fly: see the [230]-remote and [231]-query
+ number of parameters on the fly: see the [232]-remote and [233]-query
options. To shut down the running x11vnc server just type "x11vnc -R
stop". To disconnect all clients do "x11vnc -R disconnect:all", etc.
- If the [232]-forever option has not been supplied, x11vnc will
+ If the [234]-forever option has not been supplied, x11vnc will
automatically exit after the first client disconnects. In general if
you cannot use the remote control, then you will have to kill the
x11vnc process This can be done via: "kill NNNNN" (where NNNNN is the
x11vnc process id number found from ps(1)), or "pkill x11vnc", or
"killall x11vnc" (Linux only.)
- If you have not put x11vnc in the background via the [233]-bg option
+ If you have not put x11vnc in the background via the [235]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it.
@@ -3361,16 +3393,16 @@ TrueColor defdepth 24
down state in the Xserver. Tapping the stuck key (either via a new
x11vnc or at the physical console) will release it from the stuck
state. If the keyboard seems to be acting strangely it is often fixed
- by tapping Ctrl, Shift, and Alt. Alternatively, the [234]-clear_mods
- option and [235]-clear_keys option can be used to release pressed keys
- at startup and exit. The option [236]-clear_all will also try to unset
+ by tapping Ctrl, Shift, and Alt. Alternatively, the [236]-clear_mods
+ option and [237]-clear_keys option can be used to release pressed keys
+ at startup and exit. The option [238]-clear_all will also try to unset
Caps_Lock, Num_Lock, etc.
- Q-32: Can I change settings in x11vnc without having to restart it?
+ Q-33: Can I change settings in x11vnc without having to restart it?
Can I remote control it?
- Look at the [237]-remote (an alias is -R) and [238]-query (an alias is
+ Look at the [239]-remote (an alias is -R) and [240]-query (an alias is
-Q) options added in Dec/2004. They allow nearly everything to be
changed dynamically and settings to be queried. Examples: "x11vnc -R
shared", "x11vnc -R forever", "x11vnc -R scale:3/4", "x11vnc -Q
@@ -3381,8 +3413,8 @@ TrueColor defdepth 24
property) is used as the communication channel, so the X permissions
and DISPLAY must be set up correctly for communication to be possible.
- There is also a simple Tcl/Tk [239]gui based on this remote control
- mechanism. See the [240]-gui option for more info. You will need to
+ There is also a simple Tcl/Tk [241]gui based on this remote control
+ mechanism. See the [242]-gui option for more info. You will need to
have Tcl/Tk (i.e. /usr/bin/wish) installed for it to work. It can also
run in the system tray: "-gui tray" or as a standalone small icon
window: "-gui icon". Use "-gui tray=setpass" for a naive user "Share
@@ -3390,7 +3422,7 @@ TrueColor defdepth 24
[Security and Permissions]
- Q-33: How do I create a VNC password for use with x11vnc?
+ Q-34: How do I create a VNC password for use with x11vnc?
You may already have one in $HOME/.vnc/passwd if you have used, say,
the vncserver program from the regular RealVNC or TightVNC packages
@@ -3398,12 +3430,12 @@ TrueColor defdepth 24
vncpasswd(1) program from those packages.
As of Jun/2004 x11vnc supports the -storepasswd "pass" "file"
- [241]option, which is the same functionality of storepasswd. Be sure
+ [243]option, which is the same functionality of storepasswd. Be sure
to quote the "pass" if it contains shell meta characters, spaces, etc.
Example:
x11vnc -storepasswd 'sword*fish' $HOME/myvncpasswd
- You then use the password via the x11vnc option: "[242]-rfbauth
+ You then use the password via the x11vnc option: "[244]-rfbauth
$HOME/myvncpasswd"
As of Jan/2006 if you do not supply any arguments:
@@ -3415,11 +3447,11 @@ TrueColor defdepth 24
~/.mypass", the password you are prompted for will be stored in that
file.
- x11vnc also has the [243]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [245]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
- You can use the [244]-usepw option to automatically use any password
+ You can use the [246]-usepw option to automatically use any password
file you have in ~/.vnc/passwd or ~/.vnc/passwdfile (the latter is
used with the -passwdfile option.)
@@ -3431,7 +3463,7 @@ TrueColor defdepth 24
who do not know better.
- Q-34: Can I make it so -storepasswd doesn't show my password on the
+ Q-35: Can I make it so -storepasswd doesn't show my password on the
screen?
You can use the vncpasswd program from RealVNC or TightVNC mentioned
@@ -3448,17 +3480,17 @@ TrueColor defdepth 24
~/.mypass"
- Q-35: Can I have two passwords for VNC viewers, one for full access
+ Q-36: Can I have two passwords for VNC viewers, one for full access
and the other for view-only access to the display?
- Yes, as of May/2004 there is the [245]-viewpasswd option to supply the
- view-only password. Note the full-access password option [246]-passwd
+ Yes, as of May/2004 there is the [247]-viewpasswd option to supply the
+ view-only password. Note the full-access password option [248]-passwd
must be supplied at the same time. E.g.: -passwd sword -viewpasswd
fish.
To avoid specifying the passwords on the command line (where they
could be observed via the ps(1) command by any user) you can use the
- [247]-passwdfile option to specify a file containing plain text
+ [249]-passwdfile option to specify a file containing plain text
passwords. Presumably this file is readable only by you, and ideally
it is located on the machine x11vnc is run on (to avoid being snooped
on over the network.) The first line of this file is the full-access
@@ -3466,7 +3498,7 @@ TrueColor defdepth 24
it is taken as the view-only password. (use "__EMPTY__" to supply an
empty one.)
- View-only passwords currently do not work for the [248]-rfbauth
+ View-only passwords currently do not work for the [250]-rfbauth
password option (standard VNC password storing mechanism.) FWIW, note
that although the output (usually placed in $HOME/.vnc/passwd) by the
vncpasswd or storepasswd programs (or from x11vnc -storepasswd) looks
@@ -3476,10 +3508,10 @@ TrueColor defdepth 24
straight-forward to work out what to do from the VNC source code.
- Q-36: Can I have as many full-access and view-only passwords as I
+ Q-37: Can I have as many full-access and view-only passwords as I
like?
- Yes, as of Jan/2006 in the libvncserver CVS the [249]-passwdfile
+ Yes, as of Jan/2006 in the libvncserver CVS the [251]-passwdfile
option has been extended to handle as many passwords as you like. You
put the view-only passwords after a line __BEGIN_VIEWONLY__.
@@ -3487,9 +3519,9 @@ TrueColor defdepth 24
You can have x11vnc re-read the file dynamically when it is modified.
- Q-37: Does x11vnc support Unix usernames and passwords? Can I further
+ Q-38: Does x11vnc support Unix usernames and passwords? Can I further
limit the set of Unix usernames who can connect to the VNC desktop?
- Update: as of Feb/2006 x11vnc has the [250]-unixpw option that does
+ Update: as of Feb/2006 x11vnc has the [252]-unixpw option that does
this outside of the VNC protocol and libvncserver. The standard su(1)
program is used to validate the user's password. A familiar "login:"
and "Password:" dialog is presented to the user on a black screen
@@ -3499,7 +3531,7 @@ TrueColor defdepth 24
A list of allowed Unix usernames may also be supplied along with
per-user settings.
- There is also the [251]-unixpw_nis option for non-shadow-password
+ There is also the [253]-unixpw_nis option for non-shadow-password
(typically NIS environments, hence the name) systems where the
traditional getpwnam() and crypt() functions are used instead of
su(1). The encrypted user passwords must be accessible to the user
@@ -3508,11 +3540,11 @@ TrueColor defdepth 24
shadow(5).
Two settings are enforced in the -unixpw and -unixpw_nis modes to
- provide extra security: the 1) [252]-localhost and 2) [253]-stunnel or
- [254]-ssl options. Without these one might send the Unix username and
+ provide extra security: the 1) [254]-localhost and 2) [255]-stunnel or
+ [256]-ssl options. Without these one might send the Unix username and
password data in clear text over the network which is a very bad idea.
They can be relaxed if you want to provide encryption other than
- stunnel or [255]-ssl (the constraint is automatically relaxed if
+ stunnel or [257]-ssl (the constraint is automatically relaxed if
SSH_CONNECTION is set and indicates you have ssh-ed in, however the
-localhost requirement is still enforced.)
@@ -3531,13 +3563,13 @@ TrueColor defdepth 24
approximate at best.
One approximate method involves starting x11vnc with the
- [256]-localhost option. This basically requires the viewer user to log
+ [258]-localhost option. This basically requires the viewer user to log
into the workstation where x11vnc is running via their Unix username
and password, and then somehow set up a port redirection of his
vncviewer connection to make it appear to emanate from the local
machine. As discussed above, ssh is useful for this: "ssh -L
5900:localhost:5900 user@hostname ..." See the ssh wrapper scripts
- mentioned [257]elsewhere on this page. [258]stunnel does this as well.
+ mentioned [259]elsewhere on this page. [260]stunnel does this as well.
Of course a malicious user could allow other users to get in through
his channel, but that is a problem with every method. Another thing to
@@ -3548,7 +3580,7 @@ TrueColor defdepth 24
traditional way would be to further require a VNC password to supplied
(-rfbauth, -passwd, etc) and only tell the people allowed in what the
VNC password is. A scheme that avoids a second password involves using
- the [259]-accept option that runs a program to examine the connection
+ the [261]-accept option that runs a program to examine the connection
information to determine which user is connecting from the local
machine. That may be difficult to do, but, for example, the program
could use the ident service on the local machine (normally ident
@@ -3580,11 +3612,11 @@ exit 1 # reject it
always be "root".
- Q-38: Can I supply an external program to provide my own custom login
+ Q-39: Can I supply an external program to provide my own custom login
method (e.g. Dynamic/One-time passwords or non-Unix (LDAP) usernames
and passwords)?
Yes, there are several possibilities. For background see the FAQ on
- the [260]-accept where an external program may be run to decide if a
+ the [262]-accept where an external program may be run to decide if a
VNC client should be allowed to try to connect and log in. If the
program (or local user prompted by a popup) answers "yes", then
-accept proceeds to the normal VNC and x11vnc authentication methods,
@@ -3592,26 +3624,26 @@ exit 1 # reject it
To provide more direct coupling to the VNC client's username and/or
supplied password the following options were added in Sep/2006:
- * [261]-unixpw_cmd command
- * [262]-passwdfile cmd:command
- * [263]-passwdfile custom:command
+ * [263]-unixpw_cmd command
+ * [264]-passwdfile cmd:command
+ * [265]-passwdfile custom:command
In each case "command" is an external command run by x11vnc. You
supply it. For example, it may couple to your LDAP system or other
servers you set up.
- For [264]-unixpw_cmd the normal [265]-unixpw Login: and Password:
+ For [266]-unixpw_cmd the normal [267]-unixpw Login: and Password:
prompts are supplied to the VNC viewer and the strings the client
returns are then piped into "command" as the first two lines of its
standard input. If the command returns success, i.e. exit(0), the VNC
client is accepted, otherwise it is rejected.
- For "[266]-passwdfile cmd:command" the command is run and it returns a
- password list (like a password file, see the [267]-passwdfile
+ For "[268]-passwdfile cmd:command" the command is run and it returns a
+ password list (like a password file, see the [269]-passwdfile
read:filename mode.) Perhaps a dynamic, one-time password is retrieved
from a server this way.
- For "[268]-passwdfile custom:command" one gets complete control over
+ For "[270]-passwdfile custom:command" one gets complete control over
the VNC challenge-response dialog with the VNC client. x11vnc sends
out a string of random bytes (16 by the VNC spec) and the client
returns the same number of bytes in a way the server can verify only
@@ -3625,33 +3657,33 @@ exit 1 # reject it
accepted, otherwise it is rejected.
In all cases the "RFB_*" environment variables are set as under
- [269]-accept. These variables can provide useful information for the
+ [271]-accept. These variables can provide useful information for the
externally supplied program to use.
- Q-39: Why does x11vnc exit as soon as the VNC viewer disconnects? And
+ Q-40: Why does x11vnc exit as soon as the VNC viewer disconnects? And
why doesn't it allow more than one VNC viewer to connect at the same
time?
These defaults are simple safety measures to avoid someone unknowingly
leaving his X11 desktop exposed (to the internet, say) for long
- periods of time. Use the [270]-forever option (aka -many) to have
+ periods of time. Use the [272]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [271]-shared option to have x11vnc allow multiple clients to
+ Use the [273]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([272]see
- above), stunnel, [273]-ssl, or a VPN to authenticate and encrypt the
+ Recommended additional safety measures include using ssh ([274]see
+ above), stunnel, [275]-ssl, or a VPN to authenticate and encrypt the
viewer connections or to at least use the -rfbauth passwd-file
- [274]option to use VNC password protection (or [275]-passwdfile) It is
+ [276]option to use VNC password protection (or [277]-passwdfile) It is
up to YOU to apply these security measures, they will not be done for
you automatically.
- Q-40: Can I limit which machines incoming VNC clients can connect
+ Q-41: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [276]-allow and [277]-localhost options to limit
+ Yes, look at the [278]-allow and [279]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -3663,11 +3695,11 @@ exit 1 # reject it
Note that -localhost achieves the same thing as "-allow 127.0.0.1"
For more control, build libvncserver with libwrap support
- [278](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [280](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
- Q-41: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
+ Q-42: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
support?
Here is one way to pass this information to the configure script:
@@ -3683,43 +3715,43 @@ exit 1 # reject it
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [279]inetd you do not need to build
+ Note that if you run x11vnc out of [281]inetd you do not need to build
x11vnc with libwrap support because the /usr/sbin/tcpd reference in
/etc/inetd.conf handles the tcp_wrappers stuff.
- Q-42: Can I have x11vnc only listen on one network interface (e.g.
+ Q-43: Can I have x11vnc only listen on one network interface (e.g.
internal LAN) rather than having it listen on all network interfaces
and relying on -allow to filter unwanted connections out?
- As of Mar/2005 there is the "[280]-listen ipaddr" option that enables
+ As of Mar/2005 there is the "[282]-listen ipaddr" option that enables
this. For ipaddr either supply the desired network interface's IP
address (or use a hostname that resolves to it) or use the string
"localhost". For additional filtering simultaneously use the
- "[281]-allow host1,..." option to allow only specific hosts in.
+ "[283]-allow host1,..." option to allow only specific hosts in.
This option is useful if you want to insure that no one can even begin
a dialog with x11vnc from untrusted network interfaces (e.g. ppp0.)
- The option [282]-localhost now implies "-listen localhost" since that
+ The option [284]-localhost now implies "-listen localhost" since that
is what most people expect it to do.
- Q-43: Now that -localhost implies listening only on the loopback
+ Q-44: Now that -localhost implies listening only on the loopback
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- To do this specify "[283]-allow localhost". Unlike [284]-localhost
+ To do this specify "[285]-allow localhost". Unlike [286]-localhost
this will leave x11vnc listening on all interfaces (but of course only
allowing in local connections, e.g. ssh redirs.) Then you can later
run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot
connection from a remote host.
- Q-44: Can I fine tune what types of user input are allowed? E.g. have
+ Q-45: Can I fine tune what types of user input are allowed? E.g. have
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [285]-input option allows you to do this. "K",
+ As of Feb/2005, the [287]-input option allows you to do this. "K",
"M", "B", "C", and "F" stand for Keystroke, Mouse-motion,
Button-clicks, Clipboard, and File-Transfer, respectively. The
setting: "-input M" makes attached viewers only able to move the
@@ -3730,12 +3762,12 @@ exit 1 # reject it
remote control mechanism or the GUI. E.g. x11vnc -R input:hostname:M
- Q-45: Can I prompt the user at the local X display whether the
+ Q-46: Can I prompt the user at the local X display whether the
incoming VNC client should be accepted or not? Can I decide to make
some clients view-only? How about running an arbitrary program to make
the decisions?
- Yes, look at the "[286]-accept command" option, it allows you to
+ Yes, look at the "[288]-accept command" option, it allows you to
specify an external command that is run for each new client. (use
quotes around the command if it contains spaces, etc.) If the external
command returns 0 (success) the client is accepted, otherwise with any
@@ -3756,7 +3788,7 @@ exit 1 # reject it
client press "y" or click mouse on the "Yes" button. To reject the
client press "n" or click mouse on the "No" button. To accept the
client View-only, press "v" or click mouse on the "View" button. If
- the [287]-viewonly option has been supplied, the "View" action will
+ the [289]-viewonly option has been supplied, the "View" action will
not be present: the whole display is view only in that case.
The popup window times out after 120 seconds, to change this behavior
@@ -3771,7 +3803,7 @@ exit 1 # reject it
program to prompt the user whether the client should be accepted or
not. This requires that you have xmessage installed and available via
PATH. In case it is not already on your system, the xmessage program
- is available at [288]ftp://ftp.x.org/
+ is available at [290]ftp://ftp.x.org/
(End of Built-in Popup Window:)
To include view-only decisions for the external commands, prefix the
@@ -3811,7 +3843,7 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [289]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [291]dtVncPopup for use
in CDE environments to do the same sort of thing. Information on how
to use it is found at the top of the file. He encourages you to
provide feedback to him to help improve the script.
@@ -3820,23 +3852,23 @@ exit 1
popup is being run, so attached clients will not receive screen
updates, etc during this period.
- To run a command when a client disconnects, use the "[290]-gone
+ To run a command when a client disconnects, use the "[292]-gone
command" option. This is for the user's convenience only: the return
code of the command is not interpreted by x11vnc. The same environment
variables are set as in "-accept command" (except that RFB_MODE will
be "gone".)
- As of Jan/2006 the "[291]-afteraccept command" option will run the
+ As of Jan/2006 the "[293]-afteraccept command" option will run the
command only after the VNC client has been accepted and authenticated.
Like -gone the return code is not interpreted. RFB_MODE will be
"afteraccept".)
- Q-46: I start x11vnc as root because it is launched via inetd(8) or a
+ Q-47: I start x11vnc as root because it is launched via inetd(8) or a
display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- As of Feb/2005 x11vnc has the [292]-users option that allows things
+ As of Feb/2005 x11vnc has the [294]-users option that allows things
like this. Please read the documentation on it (also in the x11vnc
-help output) carefully for features and caveats. It's use can often
decrease security unless care is taken.
@@ -3848,7 +3880,7 @@ exit 1
warranty ;-).
- Q-47: I use a screen-lock when I leave my workstation (e.g.
+ Q-48: I use a screen-lock when I leave my workstation (e.g.
xscreensaver or xlock.) When I remotely access my workstation desktop
via x11vnc I can unlock the desktop fine, but I am worried people will
see my activities on the physical monitor. What can I do to prevent
@@ -3861,7 +3893,7 @@ exit 1
In any event, as of Jun/2004 there is an experimental utility to make
it more difficult for nosey people to see your x11vnc activities. The
- source for it is [293]blockdpy.c The idea behind it is simple (but
+ source for it is [295]blockdpy.c The idea behind it is simple (but
obviously not bulletproof): when a VNC client attaches to x11vnc put
the display monitor in the DPMS "off" state, if the DPMS state ever
changes immediately start up the screen-lock program. The x11vnc user
@@ -3877,8 +3909,8 @@ exit 1
bulletproof. A really robust solution would likely require X server
and perhaps even video hardware support.
- The blockdpy utility is launched by the [294]-accept option and told
- to exit via the [295]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [296]-accept option and told
+ to exit via the [297]-gone option (the vnc client user should
obviously re-lock the screen before disconnecting!) Instructions can
be found in the source code for the utility at the above link. Roughly
it is something like this:
@@ -3887,17 +3919,17 @@ exit 1
but please read the top of the file.
Update: As of Feb/2007 there is some builtin support for this:
- [296]-forcedpms and [297]-clientdpms however, they are probably less
+ [298]-forcedpms and [299]-clientdpms however, they are probably less
robust than the above blockdpy.c scheme, since if the person floods
the physical machine with mouse or pointer input he can usually see
flashes of the screen before the monitor is powered off again. See
- also the [298]-grabkbd, [299]-grabptr, and [300]-grabalways options.
+ also the [300]-grabkbd, [301]-grabptr, and [302]-grabalways options.
- Q-48: Can I have x11vnc automatically lock the screen when I
+ Q-49: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [301]-gone option under CDE to run a
+ Yes, a user mentions he uses the [303]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -3907,7 +3939,7 @@ exit 1
x11vnc -display :0 -forever -gone 'xlock &'
x11vnc -display :0 -forever -gone 'xlock -mode blank &'
- Here is a scheme using the [302]-afteraccept option (in version 0.8)
+ Here is a scheme using the [304]-afteraccept option (in version 0.8)
to unlock the screen after the first valid VNC login and to lock the
screen after the last valid VNC login disconnects:
x11vnc -display :0 -forever -shared -afteraccept ./myxlocker -gone ./myxlocke
@@ -3945,24 +3977,24 @@ exec @ARGV;
then use -gone "setpgrp xlock &", etc.
[Encrypted Connections]
- Q-49: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-50: How can I tunnel my connection to x11vnc via an encrypted SSH
channel between two Unix machines?
- See the description earlier on this page on [303]how to tunnel VNC via
+ See the description earlier on this page on [305]how to tunnel VNC via
SSH from Unix to Unix. A number of ways are described along with some
issues you may encounter.
Other secure encrypted methods exists, e.g. stunnel, IPSEC, various
VPNs, etc.
- See also the [304]Enhanced TightVNC Viewer (SSVNC) page where much of
+ See also the [306]Enhanced TightVNC Viewer (SSVNC) page where much of
this is now automated.
- Q-50: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-51: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [305]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [307]Above we described how to tunnel VNC via SSH from Unix to Unix,
you may want to review it. To do this from Windows using Putty it
would go something like this:
* In the Putty dialog window under 'Session' enter the hostname or
@@ -3983,11 +4015,11 @@ exec @ARGV;
:0 (plus other cmdline options) in the 'Remote command' Putty setting
under 'Connections/SSH'.
- See also the [306]Enhanced TightVNC Viewer (SSVNC) page where much of
+ See also the [308]Enhanced TightVNC Viewer (SSVNC) page where much of
this is now automated via the Putty plink utility.
- For extra protection feel free to run x11vnc with the [307]-localhost
- and [308]-rfbauth/[309]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [309]-localhost
+ and [310]-rfbauth/[311]-passwdfile options.
If the machine you SSH into via Putty is not the same machine with the
X display you wish to view (e.g. your company provides incoming SSH
@@ -3995,21 +4027,21 @@ exec @ARGV;
dialog setting to: 'Destination: otherhost:5900', Once logged in,
you'll need to do a second login (ssh or rsh) to the workstation
machine 'otherhost' and then start up x11vnc on it. This can also be
- automated by [310]Chaining SSH's.
+ automated by [312]Chaining SSH's.
- As discussed [311]above another option is to first start the VNC
+ As discussed [313]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[312]-connect localhost" option to establish the reverse connection.
+ "[314]-connect localhost" option to establish the reverse connection.
In this case a Remote port redirection (not Local) is needed for port
5500 instead of 5900 (i.e. 'Source port: 5500' and
'Destination: localhost:5500' for a Remote connection.)
- Q-51: How can I tunnel my connection to x11vnc via an encrypted SSL
+ Q-52: How can I tunnel my connection to x11vnc via an encrypted SSL
channel using an external tool like stunnel?
It is possible to use a "lighter weight" encryption setup than SSH or
- IPSEC. SSL tunnels such as [313]stunnel (also [314]stunnel.mirt.net)
+ IPSEC. SSL tunnels such as [315]stunnel (also [316]stunnel.mirt.net)
provide an encrypted channel without the need for Unix users,
passwords, and key passphrases required for ssh (and at the other
extreme SSL can also provide a complete signed certificate chain of
@@ -4017,9 +4049,9 @@ exec @ARGV;
and firewalls often let its port through, ssh is frequently the path
of least resistance (it also nicely manages public keys for you.)
- Update: As of Feb/2006 x11vnc has the options [315]-ssl,
- [316]-stunnel, and [317]-sslverify to provide integrated SSL schemes.
- They are discussed [318]in the Next FAQ (you probably want to skip to
+ Update: As of Feb/2006 x11vnc has the options [317]-ssl,
+ [318]-stunnel, and [319]-sslverify to provide integrated SSL schemes.
+ They are discussed [320]in the Next FAQ (you probably want to skip to
it now.)
We include these non-built-in method descriptions below for historical
@@ -4027,7 +4059,7 @@ exec @ARGV;
any VNC (or other type of) server.
- Here are some basic examples using [319]stunnel but the general idea
+ Here are some basic examples using [321]stunnel but the general idea
for any SSL tunnel utility is the same:
* Start up x11vnc and constrain it to listen on localhost.
* Then start up the SSL tunnel running on the same machine to
@@ -4051,7 +4083,7 @@ exec @ARGV;
The above two commands are run on host "far-away.east". The
stunnel.pem is the self-signed PEM file certificate created when
- stunnel is built. One can also create certificates [320]signed by
+ stunnel is built. One can also create certificates [322]signed by
Certificate Authorities or self-signed if desired using the x11vnc
utilities described there.
@@ -4065,21 +4097,21 @@ exec @ARGV;
Then point the viewer to the local tunnel on port 5902:
vncviewer -encodings "copyrect tight zrle hextile" localhost:2
- That's it. Note that the [321]ss_vncviewer script can automate this
- easily, and so can the [322]Enhanced TightVNC Viewer (SSVNC) package.
+ That's it. Note that the [323]ss_vncviewer script can automate this
+ easily, and so can the [324]Enhanced TightVNC Viewer (SSVNC) package.
Be sure to use a VNC password because unlike ssh by default the
encrypted SSL channel provides no authentication (only privacy.) With
some extra configuration one could also set up certificates to provide
authentication of either or both sides as well (and hence avoid
man-in-the-middle attacks.) See the stunnel and openssl documentation
- and also [323]the key management section for details.
+ and also [325]the key management section for details.
stunnel has also been ported to Windows, and there are likely others
to choose from for that OS. Much info for using it on Windows can be
- found at the stunnel site and in this [324]article The article also
+ found at the stunnel site and in this [326]article The article also
shows the detailed steps to set up all the authentication
- certificates. (for both server and clients, see also the [325]x11vnc
+ certificates. (for both server and clients, see also the [327]x11vnc
utilities that do this.) The default Windows client setup (no certs)
is simpler and only 4 files are needed in a folder: stunnel.exe,
stunnel.conf, libssl32.dll, libeay32.dll. We used an stunnel.conf
@@ -4100,7 +4132,7 @@ connect = far-away.east:5901
As an aside, if you don't like the little "gap" of unencrypted TCP
traffic (and a localhost listening socket) on the local machine
between stunnel and x11vnc it can actually be closed by having stunnel
- start up x11vnc in [326]-inetd mode:
+ start up x11vnc in [328]-inetd mode:
stunnel -p /path/to/stunnel.pem -P none -d 5900 -l ./x11vnc_sh
Where the script x11vnc_sh starts up x11vnc:
@@ -4137,36 +4169,36 @@ connect = 5900
SSL VNC Viewers:
Regarding VNC viewers that "natively" do SSL unfortunately there do
- not seem to be many. The [327]SingleClick UltraVNC Java Viewer is SSL
- and is compatible with x11vnc's [328]-ssl option and stunnel.)
+ not seem to be many. The [329]SingleClick UltraVNC Java Viewer is SSL
+ and is compatible with x11vnc's [330]-ssl option and stunnel.)
Commercial versions of VNC seem to have some SSL-like encryption built
in, but we haven't tried those either and they probably wouldn't work
since their (proprietary) SSL-like negotiation is likely embedded in
the VNC protocol unlike our case where it is external.
- Note: as of Mar/2006 libvncserver/x11vnc provides a [329]SSL-enabled
- Java applet that can be served up via the [330]-httpdir or [331]-http
- options when [332]-ssl is enabled. It will also be served via HTTPS
+ Note: as of Mar/2006 libvncserver/x11vnc provides a [331]SSL-enabled
+ Java applet that can be served up via the [332]-httpdir or [333]-http
+ options when [334]-ssl is enabled. It will also be served via HTTPS
via either the VNC port (e.g. https://host:5900/) or a 2nd port via
- the [333]-https option.
+ the [335]-https option.
In general current SSL VNC solutions are not particularly "seemless".
But it can be done, and with a wrapper script on the viewer side and
- the [334]-stunnel or [335]-ssl option on the server side it works well
- and is convenient. Here is a simple script [336]ss_vncviewer that
+ the [336]-stunnel or [337]-ssl option on the server side it works well
+ and is convenient. Here is a simple script [338]ss_vncviewer that
automates running stunnel on the VNC viewer side on Unix a little more
carefully than the commands printed above. (One could probably do a
similar thing with a .BAT file on Windows in the stunnel folder.)
- Update Jul/2006: we now provide an [337]Enhanced TightVNC Viewer
+ Update Jul/2006: we now provide an [339]Enhanced TightVNC Viewer
(SSVNC) package that starts up STUNNEL automatically along with some
other features. All binaries (stunnel, vncviewer, and some utilities)
are provided in the package. It works on Unix, Mac OS X, and Windows.
- Q-52: Does x11vnc have built-in SSL tunneling?
+ Q-53: Does x11vnc have built-in SSL tunneling?
- You can read about non-built-in methods [338]in the Previous FAQ for
+ You can read about non-built-in methods [340]in the Previous FAQ for
background.
SSL tunnels provide an encrypted channel without the need for Unix
@@ -4178,12 +4210,12 @@ connect = 5900
Built-in SSL x11vnc options:
- As of Feb/2006 the x11vnc [339]-ssl option automates the SSL tunnel
- creation on the x11vnc server side. An [340]SSL-enabled Java Viewer
+ As of Feb/2006 the x11vnc [341]-ssl option automates the SSL tunnel
+ creation on the x11vnc server side. An [342]SSL-enabled Java Viewer
applet is also provided that can be served via HTTP or HTTPS to
automate SSL on the client side.
- The [341]-ssl mode uses the [342]www.openssl.org library if available
+ The [343]-ssl mode uses the [344]www.openssl.org library if available
at build time.
The mode requires an SSL certificate and key (i.e. .pem file.) These
@@ -4209,11 +4241,11 @@ connect = 5900
"-ssl SAVE_NOPROMPT" to not be prompted. Use "-ssl TMP" to create a
temporary self-signed cert that will be discarded when x11vnc exits.
- Update: As of Nov/2008 x11vnc also supports the [343]VeNCrypt SSL/TLS
+ Update: As of Nov/2008 x11vnc also supports the [345]VeNCrypt SSL/TLS
tunnel extension to the VNC protocol. The older ANONTLS method (vino)
is also supported. This support is on by default when the -ssl option
- is in use and can be fine-tuned using these options: [344]-vencrypt
- and [345]-anontls.
+ is in use and can be fine-tuned using these options: [346]-vencrypt
+ and [347]-anontls.
The normal x11vnc -ssl operation is somewhat like a URL method
vncs://hostname if vnc://hostname indicates a standard unencrypted VNC
@@ -4225,7 +4257,7 @@ connect = 5900
SSL VNC Viewers:. Viewer-side will need to use SSL as well. See the
- [346]next FAQ and [347]here for SSL enabled VNC Viewers, including
+ [348]next FAQ and [349]here for SSL enabled VNC Viewers, including
SSVNC, to connect to the above x11vnc via SSL.
@@ -4240,12 +4272,12 @@ connect = 5900
is to encrypt the key with a passphrase (note however this requires
supplying the passphrase each time x11vnc is started up.)
- See the discussion on [348]x11vnc Key Management for some utilities
+ See the discussion on [350]x11vnc Key Management for some utilities
provided for creating and managing certificates and keys and even for
creating your own Certificate Authority (CA) for signing VNC server
and client certificates. This may be done by importing the certificate
into Web Browser or Java plugin keystores, or pointing stunnel to it.
- The wrapper script [349]ss_vncviewer provides an example on unix (see
+ The wrapper script [351]ss_vncviewer provides an example on unix (see
the -verify option.)
Here are some notes on the simpler default (non-CA) operation. To have
@@ -4259,7 +4291,7 @@ connect = 5900
the possibility of copying the server.crt to machines where the VNC
Viewer will be run to enable authenticating the x11vnc SSL VNC server
to the clients. When authentication takes place this way (or via the
- more sophisticated CA signing described [350]here), then
+ more sophisticated CA signing described [352]here), then
Man-In-The-Middle-Attacks are prevented. Otherwise, the SSL encryption
only provides protection against passive network traffic "sniffing"
(i.e. you are not protected against M-I-T-M attacks.) Nowadays, most
@@ -4291,11 +4323,11 @@ connect = 5900
The older -stunnel option: Before the -ssl option there was a
- convenience option [351]-stunnel that would start an external SSL
+ convenience option [353]-stunnel that would start an external SSL
tunnel for you using stunnel. The -ssl method is the preferred way,
but for historical reference we keep the -stunnel info here.
- The [352]-stunnel mode requires the [353]www.stunnel.org command
+ The [354]-stunnel mode requires the [355]www.stunnel.org command
stunnel(8) to be installed on the system.
Some -stunnel examples:
@@ -4319,15 +4351,15 @@ connect = 5900
TMP".)
- Q-53: How do I use VNC Viewers with built-in SSL tunneling?
+ Q-54: How do I use VNC Viewers with built-in SSL tunneling?
Notes on using "native" VNC Viewers with SSL:
There aren't any native VNC Viewers that do SSL (ask your VNC viewer
developer to add the feature.) So a tunnel must be setup that you
point the VNC Viewer to. This is often STUNNEL. You can do this
- [354]manually, or use the [355]ss_vncviewer script on Unix, or our
- [356]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or
+ [356]manually, or use the [357]ss_vncviewer script on Unix, or our
+ [358]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or
MacOSX. See the next section for Java Web browser SSL VNC Viewers (you
only need a Java-enabled Web browser for it to work.)
@@ -4339,13 +4371,13 @@ connect = 5900
The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package
supports only SSL based connections by default. As mentioned above the
- [357]-httpdir can be used to specify the path to .../classes/ssl. A
+ [359]-httpdir can be used to specify the path to .../classes/ssl. A
typical location might be /usr/local/share/x11vnc/classes/ssl. Or
- [358]-http can be used to try to have it find the directory
+ [360]-http can be used to try to have it find the directory
automatically.
- Also note that the [359]SingleClick UltraVNC Java Viewer is compatible
- with x11vnc's [360]-ssl SSL mode. (We tested it this way: "java -cp
+ Also note that the [361]SingleClick UltraVNC Java Viewer is compatible
+ with x11vnc's [362]-ssl SSL mode. (We tested it this way: "java -cp
./VncViewer.jar VncViewer HOST far-away.east PORT 5900 USESSL 1
TRUSTALL 1")
@@ -4380,13 +4412,13 @@ connect = 5900
If you are using a router/firewall with port-redirection, and you are
redirecting ports other than the default ones (5800, 5900) listed
- above [361]see here.
+ above [363]see here.
The https service provided thru the actual VNC port (5900 in the above
example) can occasionally be slow or unreliable (it has to read some
input and try to guess if the connection is VNC or HTTP.) If it is
unreliable for you and you still want to serve the Java applet via
- https, use the [362]-https option to get an additional port dedicated
+ https, use the [364]-https option to get an additional port dedicated
to https (its URL will also be printed in the output.)
Another possibility is to add the GET applet parameter:
@@ -4399,7 +4431,7 @@ connect = 5900
You may also use "urlPrefix=somestring" to have /somestring prepended
to /request.https.vnc.connection". Perhaps you are using a web server
- [363]proxy scheme to enter a firewall or otherwise have rules applied
+ [365]proxy scheme to enter a firewall or otherwise have rules applied
to the URL. If you need to have any slashes "/" in "somestring" use
"_2F_" (a deficiency in libvncserver prevents using the more natural
"%2F".)
@@ -4492,12 +4524,12 @@ connect = 5900
Then, if you plan to use them, enable "fancy stuff" like "-svc" or
"-unixpw", etc, etc. Be sure to add a password either "-rfbauth" or
"-unixpw" or both. If you need to have the web browser use a corporate
- [364]Web Proxy (i.e. it cannot connect directly) work on that last.
- Ditto for the [365]Apache portal.
+ [366]Web Proxy (i.e. it cannot connect directly) work on that last.
+ Ditto for the [367]Apache portal.
Router/Firewall port redirs: If you are doing port redirection at
- your [366]router to an internal machine running x11vnc AND the
+ your [368]router to an internal machine running x11vnc AND the
internet facing port is different from the internal machine's VNC
port, you will need to apply the PORT applet parameter to indicate to
the applet the Internet facing port number (otherwise by default the
@@ -4507,7 +4539,7 @@ connect = 5900
So in this example the user configures his router to redirect
connections to port 443 on his Internet side to, say, port 5900 on the
- internal machine running x11vnc. See also the [367]-httpsredir option
+ internal machine running x11vnc. See also the [369]-httpsredir option
that will try to automate this for you.
To configure your router to do port redirection, see its instructions.
@@ -4518,7 +4550,7 @@ connect = 5900
or Unix system acting as your firewall/router, see its firewall
configuration.
- You can also use x11vnc options [368]-rfbport NNNNN and [369]-httpport
+ You can also use x11vnc options [370]-rfbport NNNNN and [371]-httpport
NNNNN to match the ports that your firewall will be redirecting to the
machine where x11vnc is run.
@@ -4547,12 +4579,12 @@ connect = 5900
NOT linger at. If you see in the x11vnc output a request for
VncViewer.class instead of VncViewer.jar it is too late... you will
need to completely restart the Web browser to get it to try for the
- jar again. You can use the [370]-https option if you want a dedicated
+ jar again. You can use the [372]-https option if you want a dedicated
port for HTTPS connections instead of sharing the VNC port.
To see example x11vnc output for a successful https://host:5900/
- connection with the Java Applet see [371]This Page. And here is a
- newer example [372]including the Java Console output.
+ connection with the Java Applet see [373]This Page. And here is a
+ newer example [374]including the Java Console output.
All of the x11vnc Java Viewer applet parameters are described in the
file classes/ssl/README
@@ -4563,10 +4595,10 @@ connect = 5900
If you want to use a native VNC Viewer with the SSL enabled x11vnc you
will need to run an external SSL tunnel on the Viewer side. There do
not seem to be any native SSL VNC Viewers outside of our x11vnc and
- [373]SSVNC packages. The basic ideas of doing this were discussed
- [374]for external tunnel utilities here.
+ [375]SSVNC packages. The basic ideas of doing this were discussed
+ [376]for external tunnel utilities here.
- The [375]ss_vncviewer script provided with x11vnc and SSVNC can set up
+ The [377]ss_vncviewer script provided with x11vnc and SSVNC can set up
the stunnel tunnel automatically on unix as long as the stunnel
command is installed on the Viewer machine and available in PATH (and
vncviewer too of course.) Note that on a Debian based system you will
@@ -4600,20 +4632,20 @@ connect = 5900
The fifth one shows that Web proxies can be used if that is the only
way to get out of the firewall. If the "double proxy" situation arises
- separate the two by commas. See [376]this page for more information on
+ separate the two by commas. See [378]this page for more information on
how Web proxies come into play.
- If one uses a Certificate Authority (CA) scheme described [377]here,
+ If one uses a Certificate Authority (CA) scheme described [379]here,
the wrapper script would use the CA cert instead of the server cert:
3') ss_vncviewer -verify ./cacert.crt far-away.east:0
- Update Jul/2006: we now provide an [378]Enhanced TightVNC Viewer
+ Update Jul/2006: we now provide an [380]Enhanced TightVNC Viewer
(SSVNC) package that starts up STUNNEL automatically along with some
other features. All binaries (stunnel, vncviewer, and some utilities)
are provided in the package. It works on Unix, Mac OS X, and Windows.
- Q-54: How do I use the Java applet VNC Viewer with built-in SSL
+ Q-55: How do I use the Java applet VNC Viewer with built-in SSL
tunneling when going through a Web Proxy?
The SSL enabled Java VNC Viewer and firewall Proxies:
@@ -4670,36 +4702,36 @@ connect = 5900
https://yourmachine.com/proxy.vnc?PORT=443
this is cleaner because it avoids editing the file, but requires more
- parameters in the URL. See also the [379]-httpsredir x11vnc option
- that will try to automate this for you. To use the GET [380]trick
+ parameters in the URL. See also the [381]-httpsredir x11vnc option
+ that will try to automate this for you. To use the GET [382]trick
discussed above, do:
https://yourmachine.com/proxy.vnc?GET=1&PORT=443
All of the x11vnc Java Viewer applet parameters are described in the
file classes/ssl/README
- Here is an example of Java Console and x11vnc output for the [381]Web
+ Here is an example of Java Console and x11vnc output for the [383]Web
proxy case.
- Note that both the [382]ss_vncviewer stunnel Unix wrapper script and
- [383]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even
+ Note that both the [384]ss_vncviewer stunnel Unix wrapper script and
+ [385]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even
though they do not involve a Web browser.
- Q-55: Can Apache web server act as a gateway for users to connect via
+ Q-56: Can Apache web server act as a gateway for users to connect via
SSL from the Internet with a Web browser to x11vnc running on their
workstations behind a firewall?
Yes. You will need to configure apache to forward these connections.
- It is discussed [384]here. This provides a clean alternative to the
+ It is discussed [386]here. This provides a clean alternative to the
traditional method where the user uses SSH to log in through the
gateway to create the encrypted port redirection to x11vnc running on
her desktop.
- Q-56: Can I create and use my own SSL Certificate Authority (CA) with
+ Q-57: Can I create and use my own SSL Certificate Authority (CA) with
x11vnc?
- Yes, see [385]this page for how to do this and the utility commands
+ Yes, see [387]this page for how to do this and the utility commands
x11vnc provides to create and manage many types of certificates and
private keys.
@@ -4707,7 +4739,7 @@ connect = 5900
[Display Managers and Services]
- Q-57: How can I run x11vnc as a "service" that is always available?
+ Q-58: How can I run x11vnc as a "service" that is always available?
There are a number of ways to do this. The primary thing you need to
decide is whether you want x11vnc to connect to the X session on the
@@ -4718,14 +4750,14 @@ connect = 5900
need to have sufficient permissions to connect to the X display.
Here are some ideas:
- * Use the description under "Continuously" in the [386]FAQ on x11vnc
+ * Use the description under "Continuously" in the [388]FAQ on x11vnc
and Display Managers
- * Use the description in the [387]FAQ on x11vnc and inetd(8)
- * Use the description in the [388]FAQ on Unix user logins and
+ * Use the description in the [389]FAQ on x11vnc and inetd(8)
+ * Use the description in the [390]FAQ on Unix user logins and
inetd(8)
* Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc or
autostart script or ...)
- * Although less reliable, see the [389]x11vnc_loop rc.local hack
+ * Although less reliable, see the [391]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -4747,9 +4779,9 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
X startup scripts (traditionally .xsession/.xinitrc) may have to be in
a different directory or have a different basename. One user
recommends the description under 'Running Scripts Automatically' at
- [390]this link.
+ [392]this link.
- Firewalls: note all methods will require the host-level [391]firewall
+ Firewalls: note all methods will require the host-level [393]firewall
to be configured to allow connections in on a port. E.g. 5900 (default
VNC port) or 22 (default SSH port for tunnelling VNC.) Most systems
these days have firewalls turned on by default, so you will actively
@@ -4758,7 +4790,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
(Yast, Firestarter, etc.)
- Q-58: How can I use x11vnc to connect to an X login screen like xdm,
+ Q-59: How can I use x11vnc to connect to an X login screen like xdm,
GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X
session yet.)
_________________________________________________________________
@@ -4771,7 +4803,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
while running x11vnc as root, e.g. for the gnome display manager, gdm:
x11vnc -auth /var/gdm/:0.Xauth -display :0
- (the [392]-auth option sets the XAUTHORITY variable for you.)
+ (the [394]-auth option sets the XAUTHORITY variable for you.)
There will be a similar thing for xdm using however a different auth
directory path (perhaps something like
@@ -4793,14 +4825,14 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
(or /etc/gdm/gdm.conf, etc.) avoids this. Otherwise, just restart
x11vnc and then reconnect your viewer. Other display managers (kdm,
etc) may also have a similar problem. One user reports having to alter
- "gdm.conf-custom" as well. Update Nov/2008: See also the [393]-reopen
+ "gdm.conf-custom" as well. Update Nov/2008: See also the [395]-reopen
option for another possible workaround.
Note: Solaris: For dtlogin in addition to the above sort of trick
(BTW, the auth file should be in /var/dt), you'll also need to add
something like Dtlogin*grabServer:False to the Xconfig file
(/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see
- [394]the example at the end of this FAQ.) Then restart dtlogin, e.g.:
+ [396]the example at the end of this FAQ.) Then restart dtlogin, e.g.:
/etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot.
_________________________________________________________________
@@ -4813,7 +4845,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
Please consider the security implications of this! The VNC display for
the X session always accessible (but hopefully password protected.)
- Add [395]-localhost if you only plan to access via a [396]SSH tunnel.
+ Add [397]-localhost if you only plan to access via a [398]SSH tunnel.
The name of the display manager startup script file depends on desktop
used and seem to be:
@@ -4844,7 +4876,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
-forever -bg
where you should customize the exact command to your needs (e.g.
- [397]-localhost for SSH tunnel-only access; [398]-ssl SAVE for SSL
+ [399]-localhost for SSH tunnel-only access; [400]-ssl SAVE for SSL
access; etc.)
Happy, happy, joy, joy: Note that we do not need to specify -display
@@ -4852,7 +4884,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
and XAUTHORITY environment variables for the Xsetup script!!!
You may also want to force the VNC port with something like "-rfbport
- 5900" (or [399]-N) to avoid autoselecting one if 5900 is already
+ 5900" (or [401]-N) to avoid autoselecting one if 5900 is already
taken.
_________________________________________________________________
@@ -4868,7 +4900,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
Then restart: /usr/sbin/gdm-restart (or reboot.) The
KillInitClients=false setting is important: without it x11vnc will be
- killed immediately after the user logs in. Here are [400]full details
+ killed immediately after the user logs in. Here are [402]full details
on how to configure gdm
_________________________________________________________________
@@ -4910,16 +4942,16 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
If you do not want to deal with any display manager startup scripts,
here is a kludgey script that can be run manually or out of a boot
- file like rc.local: [401]x11vnc_loop It will need some local
+ file like rc.local: [403]x11vnc_loop It will need some local
customization before running. Because the XAUTHORITY auth file must be
guessed by this script, use of the display manager script method
- described above is greatly preferred. There is also the [402]-loop
+ described above is greatly preferred. There is also the [404]-loop
option that does something similar.
If the machine is a traditional Xterminal you may want to read
- [403]this FAQ.
+ [405]this FAQ.
- Firewalls: note all methods will require the host-level [404]firewall
+ Firewalls: note all methods will require the host-level [406]firewall
to be configured to allow connections in on a port. E.g. 5900 (default
VNC port) or 22 (default SSH port for tunnelling VNC.) Most systems
these days have firewalls turned on by default, so you will actively
@@ -4928,14 +4960,14 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
(Yast, Firestarter, etc.)
- Q-59: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
+ Q-60: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
Yes, perhaps a line something like this in /etc/inetd.conf will do it
for you:
5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
- where the shell script /usr/local/bin/x11vnc_sh uses the [405]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [407]-inetd
option and looks something like (you'll need to customize to your
settings.)
#!/bin/sh
@@ -4948,7 +4980,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
and that confuses it greatly, causing it to abort.) If you do not use
a wrapper script as above but rather call x11vnc directly in
/etc/inetd.conf and do not redirect stderr to a file, then you must
- specify the -q (aka [406]-quiet) option: "/usr/local/bin/x11vnc -q
+ specify the -q (aka [408]-quiet) option: "/usr/local/bin/x11vnc -q
-inetd ...". When you supply both -q and -inet and no "-o logfile"
then stderr will automatically be closed (to prevent, e.g. library
stderr messages leaking out to the viewer.) The recommended practice
@@ -4956,12 +4988,12 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
script with "2>logfile" redirection because the errors and warnings
printed out are very useful in troubleshooting problems.
- Note also the need to set XAUTHORITY via [407]-auth to point to the
+ Note also the need to set XAUTHORITY via [409]-auth to point to the
MIT-COOKIE auth file to get permission to connect to the X display
(setting and exporting the XAUTHORITY variable accomplishes the same
thing.) See the x11vnc_loop file in the previous question for more
ideas on what that auth file may be, etc. The scheme described in the
- [408]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY
+ [410]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY
issue nicely.
Note: On Solaris you cannot have the bare number 5900 in
@@ -5041,14 +5073,14 @@ exit 1
exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1
- Q-60: Can I have x11vnc advertise its VNC service and port via mDNS /
+ Q-61: Can I have x11vnc advertise its VNC service and port via mDNS /
Zeroconf (e.g. Avahi) so VNC viewers on the local network can detect
it automatically?
Yes, as of Feb/2007 x11vnc supports mDNS / Zeroconf advertising of its
- service via the Avahi client library. Use the option [409]-avahi (same
- as [410]-mdns or [411]-zeroconf) to enable it. Depending on your setup
- you may need to install [412]Avahi (including the development/build
+ service via the Avahi client library. Use the option [411]-avahi (same
+ as [412]-mdns or [413]-zeroconf) to enable it. Depending on your setup
+ you may need to install [414]Avahi (including the development/build
packages), enable the server: avahi-daemon and avahi-dnsconfd, and
possibly open up UDP port 5353 on your firewall.
@@ -5072,37 +5104,37 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1
other distros/OS's...
- Q-61: Can I have x11vnc allow a user to log in with her UNIX username
+ Q-62: Can I have x11vnc allow a user to log in with her UNIX username
and password and then have it find her X session display on that
machine and then connect to it? How about starting an X session if one
cannot be found?
- The easiest way to do this is via [413]inetd(8) using the [414]-unixpw
- and [415]-display WAIT options. The reason inetd(8) makes this easier
+ The easiest way to do this is via [415]inetd(8) using the [416]-unixpw
+ and [417]-display WAIT options. The reason inetd(8) makes this easier
is that it starts a new x11vnc process for each new user connection.
Otherwise a wrapper would have to listen for connections and spawn new
- x11vnc's (see [416]this example and also the [417]-loopbg option.)
+ x11vnc's (see [418]this example and also the [419]-loopbg option.)
Also with inetd(8) users always connect to a fixed VNC display, say
hostname:0, and do not need to memorize a special VNC display number
just for their personal use, etc.
- Update: Use the [418]-find, [419]-create, [420]-svc, and [421]-xdmsvc
+ Update: Use the [420]-find, [421]-create, [422]-svc, and [423]-xdmsvc
options that are shorthand for common FINDCREATEDISPLAY usage modes
(e.g. terminal services) described below. (i.e. just use "-svc"
instead of "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb -unixpw -users
unixpw= -ssl SAVE")
- The [422]-display WAIT option makes x11vnc wait until a VNC viewer is
+ The [424]-display WAIT option makes x11vnc wait until a VNC viewer is
connected before attaching to the X display. Additionally it can be
used to run an external command that returns the DISPLAY and
XAUTHORITY data. We provide some useful builtin ones (FINDDISPLAY and
FINDCREATEDISPLAY below), but in principle one could supply "-display
WAIT:cmd=/path/to/find_display" where the script find_display might
- look something like [423]this.
+ look something like [425]this.
A default script somewhat like the above is used under "-display
- WAIT:cmd=FINDDISPLAY" (same as [424]-find) (use
+ WAIT:cmd=FINDDISPLAY" (same as [426]-find) (use
"WAIT:cmd=FINDDISPLAY-print" to print out the gnarly script.) The
format for any such command is that it returns DISPLAY=:disp as the
first line and any remaining lines are either XAUTHORITY=file or raw
@@ -5114,10 +5146,10 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1
Or if you only know the X server process ID and suspect a chvt will be
needed append ",XPID=n".
- Tip: Note that the [425]-find option is an alias for "-display
+ Tip: Note that the [427]-find option is an alias for "-display
WAIT:cmd=FINDDISPLAY". Use it!
- The [426]-unixpw option allows [427]UNIX password logins. It
+ The [428]-unixpw option allows [429]UNIX password logins. It
conveniently knows the Unix username whose X display should be found.
Here are a couple /etc/inetd.conf examples for this:
5900 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd
@@ -5131,16 +5163,16 @@ xpw=
Note the very long lines have been split. An alternative is to use a
wrapper script, e.g. /usr/local/bin/x11vnc.sh that has all of the
- options. (see also the [428]-svc alias.)
+ options. (see also the [430]-svc alias.)
In the first one x11vnc is run as user "nobody" and stays user nobody
during the whole session. The permissions of the log files and certs
directory will need to be set up to allow "nobody" to use them.
In the second one x11vnc is run as root and switches to the user that
- logs in due to the "[429]-users unixpw=" option.
+ logs in due to the "[431]-users unixpw=" option.
- Note that [430]SSL is required for this mode because otherwise the
+ Note that [432]SSL is required for this mode because otherwise the
Unix password would be passed in clear text over the network. In
general -unixpw is not required for this sort of scheme, but it is
convenient because it determines exactly who the Unix user is whose
@@ -5148,17 +5180,17 @@ xpw=
to use some method to work out DISPLAY, XAUTHORITY, etc (perhaps you
use multiple inetd ports and hardwire usernames for different ports.)
- If you really want to disable the SSL or SSH [431]-localhost
+ If you really want to disable the SSL or SSH [433]-localhost
constraints (this is not recommended unless you really know what you
are doing: Unix passwords sent in clear text is a very bad idea...)
- read the [432]-unixpw documentation.
+ read the [434]-unixpw documentation.
A inetd(8) scheme for a fixed user that doesn't use SSL or unix
passwds could be:
/usr/local/bin/x11vnc -inetd -users =fred -find -rfbauth /home/fred/.vnc/passwd
-o /var/log/x11vnc.log
- The "[433]-users =fred" option will cause x11vnc to switch to user
+ The "[435]-users =fred" option will cause x11vnc to switch to user
fred and then find his X display.
@@ -5167,7 +5199,7 @@ xpw=
FINDDISPLAY method it will create an X server session for the user
(i.e. desktop/terminal server.) This is the only time x11vnc actually
tries to start up an X server. By default it will only try to start up
- virtual (non-hardware) X servers: first [434]Xdummy and if that is not
+ virtual (non-hardware) X servers: first [436]Xdummy and if that is not
available then Xvfb. Note that Xdummy requires root permission and
only works on Linux whereas Xvfb works just about everywhere.
@@ -5177,19 +5209,19 @@ xpw=
-display WAIT:cmd=FINDCREATEDISPLAY -prog /usr/local/bin/x11vnc
Where the very long lines have been split. This will allow direct SSL
- (e.g. [435]ss_vncviewer) access and also Java Web browers access via:
+ (e.g. [437]ss_vncviewer) access and also Java Web browers access via:
https://hostname:5900/.
- Tip: Note that the [436]-create option is an alias for "-display
+ Tip: Note that the [438]-create option is an alias for "-display
WAIT:cmd=FINDCREATEDISPLAY-Xvfb".
- Tip: Note that [437]-svc is a short hand for the long "-ssl SAVE
+ Tip: Note that [439]-svc is a short hand for the long "-ssl SAVE
-unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY" part.
Unlike -create, this alias also sets up SSL encryption and Unix
password login.
Tip: In addition to the usual unixpw parameters, the user can specify
- after his username (following a ":" see [438]-display WAIT for
+ after his username (following a ":" see [440]-display WAIT for
details) for FINDCREATEDISPLAY they can add "geom=WxH" or "geom=WxHxD"
to specify the width, height, and optionally the color depth. E.g.
"fred:geom=800x600" at the login: prompt. Also if the env. var
@@ -5226,7 +5258,7 @@ service x11vnc
WAIT:cmd=FINDCREATEDISPLAY-X,Xvfb,Xdummy". The "X" one means to try to
start up a real, hardware X server, e.g. startx(1) (if there is
already a real X server running this may only work on Linux and the
- chvt program may [439]need to be run to switch to the correct Linux
+ chvt program may [441]need to be run to switch to the correct Linux
virtual terminal.) x11vnc will try to run chvt automatically if it can
determine which VT should be switched to.
@@ -5253,7 +5285,7 @@ service x11vnc
will also typically block UDP (port 177 for XDMCP) by default
effectively limiting the UDP connections to localhost.
- Tip: Note that [440]-xdmsvc is a short hand for the long "-ssl SAVE
+ Tip: Note that [442]-xdmsvc is a short hand for the long "-ssl SAVE
-unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp"
part. E.g.:
service x11vnc
@@ -5317,26 +5349,26 @@ t:5
(e.g. :0) and it switches based on username.
- Q-62: Can I have x11vnc restart itself after it terminates?
+ Q-63: Can I have x11vnc restart itself after it terminates?
One could do this in a shell script, but now there is an option
- [441]-loop that makes it easier. Of course when x11vnc restarts it
+ [443]-loop that makes it easier. Of course when x11vnc restarts it
needs to have permissions to connect to the (potentially new) X
display. This mode could be useful if the X server restarts often. Use
e.g. "-loop5000" to sleep 5000 ms between restarts. Also "-loop2000,5"
to sleep 2000 ms and only restart 5 times.
- One can also use the [442]-loopbg to emulate inetd(8) to some degree,
+ One can also use the [444]-loopbg to emulate inetd(8) to some degree,
where each connected process runs in the background. It could be
- combined, say, with the [443]-svc option to provide simple terminal
+ combined, say, with the [445]-svc option to provide simple terminal
services without using inetd(8).
- Q-63: How do I make x11vnc work with the Java VNC viewer applet in a
+ Q-64: How do I make x11vnc work with the Java VNC viewer applet in a
web browser?
To have x11vnc serve up a Java VNC viewer applet to any web browsers
- that connect to it, run x11vnc with this [444]option:
+ that connect to it, run x11vnc with this [446]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -5355,7 +5387,7 @@ t:5
then you can connect to that URL with any Java enabled browser. Feel
free to customize the default index.vnc file in the classes directory.
- As of May/2005 the [445]-http option will try to guess where the Java
+ As of May/2005 the [447]-http option will try to guess where the Java
classes jar file is by looking in expected locations and ones relative
to the x11vnc binary.
@@ -5364,7 +5396,7 @@ t:5
either the java or appletviewer commands to run the program.
java -cp ./VncViewer.jar VncViewer HOST far-away.east PORT 5900
- Proxies: See the [446]discussion here if the web browser must use a
+ Proxies: See the [448]discussion here if the web browser must use a
web proxy to connect to the internet. It is tricky to get Java applets
to work in this case: a signed applet must be used so it can connect
to the proxy and ask for the redirection to the VNC server. One way to
@@ -5374,13 +5406,13 @@ t:5
in the URL or the file.
- Q-64: Are reverse connections (i.e. the VNC server connecting to the
+ Q-65: Are reverse connections (i.e. the VNC server connecting to the
VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
As of Mar/2004 x11vnc supports reverse connections. On Unix one starts
the VNC viewer in listen mode: "vncviewer -listen" (see your
documentation for Windows, etc), and then starts up x11vnc with the
- [447]-connect option. To connect immediately at x11vnc startup time
+ [449]-connect option. To connect immediately at x11vnc startup time
use the "-connect host:port" option (use commas for a list of hosts to
connect to.) The ":port" is optional (default is VNC listening port is
5500.)
@@ -5389,11 +5421,11 @@ t:5
file is checked periodically (about once a second) for new hosts to
connect to.
- The [448]-remote control option (aka -R) can also be used to do this
+ The [450]-remote control option (aka -R) can also be used to do this
during an active x11vnc session, e.g.:
x11vnc -display :0 -R connect:hostname.domain
- Use the "[449]-connect_or_exit" option to have x11vnc exit if the
+ Use the "[451]-connect_or_exit" option to have x11vnc exit if the
reverse connection fails. Also, note the "-rfbport 0" option disables
TCP listening for connections (potentially useful for reverse
connection mode, assuming you do not want any "forward" connections.)
@@ -5406,7 +5438,7 @@ x11vnc -display :0 -R connect:hostname.domain
X11VNC_REVERSE_CONNECTION_NO_AUTH=1" to x11vnc.
Vncconnect command: To use the vncconnect(1) program (from the core
- VNC package at www.realvnc.com) specify the [450]-vncconnect option to
+ VNC package at www.realvnc.com) specify the [452]-vncconnect option to
x11vnc (Note: as of Dec/2004 -vncconnect is now the default.)
vncconnect(1) must be pointed to the same X11 DISPLAY as x11vnc (since
it uses X properties to communicate with x11vnc.) If you do not have
@@ -5421,11 +5453,11 @@ x11vnc -display :0 -R connect:hostname.domain
xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
- Q-65: Can reverse connections be made to go through a Web or SOCKS
+ Q-66: Can reverse connections be made to go through a Web or SOCKS
proxy or SSH?
Yes, as of Oct/2007 x11vnc supports reverse connections through
- proxies: use the "[451]-proxy host:port" option. The default is to
+ proxies: use the "[453]-proxy host:port" option. The default is to
assume the proxy is a Web proxy. Note that most Web proxies only allow
proxy destination connections to ports 443 (HTTPS) and 563 (SNEWS) and
so this might not be too useful unless the proxy has been modified
@@ -5445,11 +5477,11 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
connections.
An experimental mode is "-proxy http://host:port/..." where the URL
- (e.g. a CGI script) is retrieved via the GET method. See [452]-proxy
+ (e.g. a CGI script) is retrieved via the GET method. See [454]-proxy
for more info.
Another experimental mode is "-proxy ssh://user@host" in which case a
- SSH tunnel is used for the proxying. See [453]-proxy for more info.
+ SSH tunnel is used for the proxying. See [455]-proxy for more info.
Up to 3 proxies may be chained together by listing them by commas
e.g.: "-proxy http://host1:port1,socks5://host2:port2" in case one
@@ -5457,7 +5489,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
listening viewer.
- Q-66: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
+ Q-67: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real
display, but for a virtual one I keep around.)
You can, but you would not be doing this for performance reasons (for
@@ -5472,10 +5504,10 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
Driver in XFree86/Xorg (see below.)
In either case, one can view this desktop both remotely and also
- [454]locally using vncviewer. Make sure vncviewer's "-encodings raw"
+ [456]locally using vncviewer. Make sure vncviewer's "-encodings raw"
is in effect for local viewing (compression seems to slow things down
locally.) For local viewing you set up a "bare" window manager that
- just starts up vncviewer and nothing else ([455]See how below.)
+ just starts up vncviewer and nothing else ([457]See how below.)
Here is one way to start up Xvfb:
xinit -- /usr/X11R6/bin/Xvfb :1 -cc 4 -screen 0 1024x768x16
@@ -5495,19 +5527,19 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
"screen scrape" it very efficiently (more than, say, 100X faster than
normal video hardware.)
- Update Nov/2006: See the [456]FINDCREATEDISPLAY discussion of the
- "[457]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or
+ Update Nov/2006: See the [458]FINDCREATEDISPLAY discussion of the
+ "[459]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or
Xdummy, or even real ones by changing an option) X servers are started
automatically for new users connecting. This provides a "desktop
service" for the machine. You either get your real X session or your
virtual (Xvfb/Xdummy) one whenever you connect to the machine
- (inetd(8) is a nice way to provide this service.) The [458]-find,
- [459]-create, [460]-svc, and [461]-xdmsvc aliases can also come in
+ (inetd(8) is a nice way to provide this service.) The [460]-find,
+ [461]-create, [462]-svc, and [463]-xdmsvc aliases can also come in
handy here.
There are some annoyances WRT Xvfb however. The default keyboard
mapping seems to be very poor. One should run x11vnc with
- [462]-add_keysyms option to have keysyms added automatically. Also, to
+ [464]-add_keysyms option to have keysyms added automatically. Also, to
add the Shift_R and Control_R modifiers something like this is needed:
#!/bin/sh
xmodmap -e "keycode any = Shift_R"
@@ -5519,7 +5551,7 @@ xmodmap -e "keycode any = Alt_R"
xmodmap -e "keycode any = Meta_L"
xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L"
- (note: these are applied automatically in the [463]FINDCREATEDISPLAY
+ (note: these are applied automatically in the [465]FINDCREATEDISPLAY
mode of x11vnc.) Perhaps the Xvfb options -xkbdb or -xkbmap could be
used to get a better default keyboard mapping...
@@ -5534,11 +5566,11 @@ xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L"
The main drawback to this method (besides requiring extra
configuration and possibly root permission) is that it also does the
- Linux Virtual Console/Terminal (VC/VT) [464]switching even though it
+ Linux Virtual Console/Terminal (VC/VT) [466]switching even though it
does not need to (since it doesn't use a real framebuffer.) There are
some "dual headed" (actually multi-headed/multi-user) patches to the X
server that turn off the VT usage in the X server. Update: As of
- Jul/2005 we have an LD_PRELOAD script [465]Xdummy that allows you to
+ Jul/2005 we have an LD_PRELOAD script [467]Xdummy that allows you to
use a stock (i.e. unpatched) Xorg or XFree86 server with the "dummy"
driver and not have any VT switching problems! Currently Xdummy needs
to be run as root, but with some luck that may be relaxed in the
@@ -5566,7 +5598,7 @@ x11vnc -display :5 -rfbport 5905 -bg
vncviewer -geometry +0+0 -encodings raw -passwd $HOME/.vnc/passwd localhost:5
The display numbers (VNC and X) will likely be different (you could
- also try [466]-find), and you may not need the -passwd. Recent RealVNC
+ also try [468]-find), and you may not need the -passwd. Recent RealVNC
viewers might be this:
#!/bin/sh
x11vnc -display :5 -rfbport 5905 -bg
@@ -5582,10 +5614,10 @@ t:5
For the general replacement of Xvnc by Xvfb+x11vnc, one user describes
- a similar setup he created [467]here.
+ a similar setup he created [469]here.
- Q-67: How can I use x11vnc on "headless" machines? Why might I want
+ Q-68: How can I use x11vnc on "headless" machines? Why might I want
to?
An interesting application of x11vnc is to let it export displays of
@@ -5597,7 +5629,7 @@ t:5
An X server can be started on the headless machine (sometimes this
requires configuring the X server to not fail if it cannot detect a
keyboard or mouse, see the next paragraph.) Then you can export that X
- display via x11vnc (e.g. see [468]this FAQ) and access it from
+ display via x11vnc (e.g. see [470]this FAQ) and access it from
anywhere on the network via a VNC viewer.
Some tips on getting X servers to start on machines without keyboard
@@ -5621,15 +5653,15 @@ t:5
cards as it can hold to provide multiple simultaneous access or
testing on different kinds of video hardware.
- See also the [469]FINDCREATEDISPLAY discussion of the "[470]-display
+ See also the [471]FINDCREATEDISPLAY discussion of the "[472]-display
WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X
servers are started automatically for new users connecting. The
- [471]-find, [472]-create, [473]-svc, and [474]-xdmsvc aliases can also
+ [473]-find, [474]-create, [475]-svc, and [476]-xdmsvc aliases can also
come in handy here.
[Resource Usage and Performance]
- Q-68: I have lots of memory, but why does x11vnc fail with shmget:
+ Q-69: I have lots of memory, but why does x11vnc fail with shmget:
No space left on device or Minor opcode of failed request: 1
(X_ShmAttach)?
@@ -5647,7 +5679,7 @@ t:5
19/03/2004 10:10:58 error creating tile-row shm for len=4
19/03/2004 10:10:58 reverting to single_copytile mode
- Here is a shell script [475]shm_clear to list and prompt for removal
+ Here is a shell script [477]shm_clear to list and prompt for removal
of your unattached shm segments (attached ones are skipped.) I use it
while debugging x11vnc (I use "shm_clear -y" to assume "yes" for each
prompt.) If x11vnc is regularly not cleaning up its shm segments,
@@ -5681,49 +5713,49 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [476]-onetile option (corresponds to only 3 shm segments used, and
+ [478]-onetile option (corresponds to only 3 shm segments used, and
adding -fs 1.0 knocks it down to 2.) If you are having much trouble
with shm segments, consider disabling shm completely via the
- [477]-noshm option. Performance will be somewhat degraded but when
+ [479]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [478]earlier question discussing -noshm.)
+ [480]earlier question discussing -noshm.)
- Q-69: How can I make x11vnc use less system resources?
+ Q-70: How can I make x11vnc use less system resources?
- The [479]-nap (now on by default; use -nonap to disable) and
- "[480]-wait n" (where n is the sleep between polls in milliseconds,
+ The [481]-nap (now on by default; use -nonap to disable) and
+ "[482]-wait n" (where n is the sleep between polls in milliseconds,
the default is 30 or so) option are good places to start. In addition,
- something like "[481]-sb 15" will cause x11vnc to go into a deep-sleep
+ something like "[483]-sb 15" will cause x11vnc to go into a deep-sleep
mode after 15 seconds of no activity (instead of the default 60.)
Reducing the X server bits per pixel depth (e.g. to 16bpp or even
8bpp) will further decrease memory I/O and network I/O. The ShadowFB X
server setting will make x11vnc's screen polling less severe. Using
- the [482]-onetile option will use less memory and use fewer shared
- memory slots (add [483]-fs 1.0 for one less slot.)
+ the [484]-onetile option will use less memory and use fewer shared
+ memory slots (add [485]-fs 1.0 for one less slot.)
- Q-70: How can I make x11vnc use MORE system resources?
+ Q-71: How can I make x11vnc use MORE system resources?
- You can try [484]-threads (note this mode can be unstable and/or
+ You can try [486]-threads (note this mode can be unstable and/or
crash; and as of May/2008 is strongly discouraged, see the option
description) or dial down the wait time (e.g. -wait 1) and possibly
- dial down [485]-defer as well. Note that if you try to increase the
+ dial down [487]-defer as well. Note that if you try to increase the
"frame rate" too much you can bog down the server end with the extra
work it needs to do compressing the framebuffer data, etc.
That said, it is possible to "stream" video via x11vnc if the video
window is small enough. E.g. a 256x192 xawtv TV capture window (using
- the x11vnc [486]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [488]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate. If the graphics card's framebuffer read rate
- is [487]faster than normal then the video window size and frame rate
- can be much higher. The use of [488]TurboVNC and/or TurboJPEG can make
+ is [489]faster than normal then the video window size and frame rate
+ can be much higher. The use of [490]TurboVNC and/or TurboJPEG can make
the frame rate somewhat higher still (but most of this hinges on the
graphics card's read rate.)
- Q-71: I use x11vnc over a slow link with high latency (e.g. dialup
+ Q-72: I use x11vnc over a slow link with high latency (e.g. dialup
modem or broadband), is there anything I can do to speed things up?
Some things you might want to experiment with (many of which will help
@@ -5735,7 +5767,7 @@ ied)
* Use a smaller desktop size (e.g. 1024x768 instead of 1280x1024)
* Make sure the desktop background is a solid color (the background
is resent every time it is re-exposed.) Consider using the
- [489]-solid [color] option to try to do this automatically.
+ [491]-solid [color] option to try to do this automatically.
* Configure your window manager or desktop "theme" to not use fancy
images, shading, and gradients for the window decorations, etc.
Disable window animations, etc. Maybe your desktop has a "low
@@ -5744,9 +5776,9 @@ ied)
-> Use Smooth Scrolling (deselect it.)
* Avoid small scrolls of large windows using the Arrow keys or
scrollbar. Try to use PageUp/PageDown instead. (not so much of a
- problem in x11vnc 0.7.2 if [490]-scrollcopyrect is active and
+ problem in x11vnc 0.7.2 if [492]-scrollcopyrect is active and
detecting scrolls for the application.)
- * If the [491]-wireframe option is not available (earlier than
+ * If the [493]-wireframe option is not available (earlier than
x11vnc 0.7.2 or you have disabled it via -nowireframe) then
Disable Opaque Moves and Resizes in the window manager/desktop.
* However if -wireframe is active (on by default in x11vnc 0.7.2)
@@ -5769,7 +5801,7 @@ ied)
noticed.
VNC viewer parameters:
- * Use a [492]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+ * Use a [494]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
with ZRLE encoding is not too bad either; some claim it is
faster.)
* Make sure the tight (or zrle) encoding is being used (look at
@@ -5777,7 +5809,7 @@ ied)
* Request 8 bits per pixel using -bgr233 (up to 4X speedup over
depth 24 TrueColor (32bpp), but colors will be off)
* RealVNC 4.x viewer has some extremely low color modes (only 64 and
- even 8 colors.) [493]SSVNC does too. The colors are poor, but it
+ even 8 colors.) [495]SSVNC does too. The colors are poor, but it
is usually noticeably faster than bgr233 (256 colors.)
* Try increasing the TightVNC -compresslevel (compresses more on
server side before sending, but uses more CPU)
@@ -5791,37 +5823,37 @@ ied)
file.
x11vnc parameters:
- * Make sure the [494]-wireframe option is active (it should be on by
+ * Make sure the [496]-wireframe option is active (it should be on by
default) and you have Opaque Moves/Resizes Enabled in the window
manager.
- * Make sure the [495]-scrollcopyrect option is active (it should be
+ * Make sure the [497]-scrollcopyrect option is active (it should be
on by default.) This detects scrolls in many (but not all)
applications an applies the CopyRect encoding for a big speedup.
* Enforce a solid background when VNC viewers are connected via
- [496]-solid
- * Specify [497]-speeds modem to force the wireframe and
+ [498]-solid
+ * Specify [499]-speeds modem to force the wireframe and
scrollcopyrect heuristic parameters (and any future ones) to those
of a dialup modem connection (or supply the rd,bw,lat numerical
values that characterize your link.)
* If wireframe and scrollcopyrect aren't working, try using the more
- drastic [498]-nodragging (no screen updates when dragging mouse,
+ drastic [500]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Set [499]-fs 1.0 (disables fullscreen updates)
- * Try increasing [500]-wait or [501]-defer (reduces the maximum
+ * Set [501]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [502]-wait or [503]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * Try the [502]-progressive pixelheight mode with the block
+ * Try the [504]-progressive pixelheight mode with the block
pixelheight 100 or so (delays sending vertical blocks since they
may change while viewer is receiving earlier ones)
- * If you just want to watch one (simple) window use [503]-id (cuts
+ * If you just want to watch one (simple) window use [505]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [504]-nosel (disables all clipboard selection exchange)
- * Use [505]-nocursor and [506]-nocursorpos (repainting the remote
+ * Set [506]-nosel (disables all clipboard selection exchange)
+ * Use [507]-nocursor and [508]-nocursorpos (repainting the remote
cursor position and shape takes resources and round trips)
* On very slow links (e.g. <= 28.8) you may need to increase the
- [507]-readtimeout n setting if it sometimes takes more than 20sec
+ [509]-readtimeout n setting if it sometimes takes more than 20sec
to paint the full screen, etc.
- * Do not use [508]-fixscreen to automatically refresh the whole
+ * Do not use [510]-fixscreen to automatically refresh the whole
screen, tap three Alt_L's then the screen has painting errors
(rare problem.)
@@ -5872,7 +5904,7 @@ ied)
* TBD.
- Q-72: Does x11vnc support the X DAMAGE Xserver extension to find
+ Q-73: Does x11vnc support the X DAMAGE Xserver extension to find
modified regions of the screen quickly and efficiently?
Yes, as of Mar/2005 x11vnc will use the X DAMAGE extension by default
@@ -5890,7 +5922,7 @@ ied)
Note that the DAMAGE extension does not speed up the actual reading of
pixels from the video card framebuffer memory, by, say, mirroring them
- in main memory. So reading the fb is still painfully [509]slow (e.g.
+ in main memory. So reading the fb is still painfully [511]slow (e.g.
5MB/sec), and so even using X DAMAGE when large changes occur on the
screen the bulk of the time is still spent retrieving them. Not ideal,
but use of the ShadowFB XFree86/Xorg option speeds up the reading
@@ -5908,45 +5940,45 @@ ied)
DAMAGE rectangles to contain real damage. The larger rectangles are
only used as hints to focus the traditional scanline polling (i.e. if
a scanline doesn't intersect a recent DAMAGE rectangle, the scan is
- skipped.) You can use the "[510]-xd_area A" option to adjust the size
+ skipped.) You can use the "[512]-xd_area A" option to adjust the size
of the trusted DAMAGE rectangles. The default is 20000 pixels (e.g. a
140x140 square, etc.) Use "-xd_area 0" to disable the cutoff and trust
all DAMAGE rectangles.
- The option "[511]-xd_mem f" may also be of use in tuning the
- algorithm. To disable using DAMAGE entirely use "[512]-noxdamage".
+ The option "[513]-xd_mem f" may also be of use in tuning the
+ algorithm. To disable using DAMAGE entirely use "[514]-noxdamage".
- Q-73: My OpenGL application shows no screen updates unless I supply
+ Q-74: My OpenGL application shows no screen updates unless I supply
the -noxdamage option to x11vnc.
One user reports in his environment (MythTV using the NVIDIA OpenGL
drivers) he gets no updates after the initial screen is drawn unless
- he uses the "[513]-noxdamage" option.
+ he uses the "[515]-noxdamage" option.
This seems to be a bug in the X DAMAGE implementation of that driver.
You may have to use -noxdamage as well. A way to autodetect this will
be tried, probably the best it will do is automatically stop using X
DAMAGE.
- A developer for [514]MiniMyth reports that the 'alphapulse' tag of the
+ A developer for [516]MiniMyth reports that the 'alphapulse' tag of the
theme G.A.N.T. can also cause problems, and should be avoided when
using VNC.
- Update: see [515]this FAQ too.
+ Update: see [517]this FAQ too.
- Q-74: When I drag windows around with the mouse or scroll up and down
+ Q-75: When I drag windows around with the mouse or scroll up and down
things really bog down (unless I do the drag in a single, quick
motion.) Is there anything to do to improve things?
- This problem is primarily due to [516]slow hardware read rates from
+ This problem is primarily due to [518]slow hardware read rates from
video cards: as you scroll or move a large window around the screen
changes are much too rapid for x11vnc to keep up them (it can usually
only read the video card at about 5-10 MB/sec, so it can take a good
fraction of a second to read the changes induce from moving a large
window, if this to be done a number of times in succession the window
or scroll appears to "lurch" forward.) See the description in the
- [517]-pointer_mode option for more info. The next bottleneck is
+ [519]-pointer_mode option for more info. The next bottleneck is
compressing all of these changes and sending them out to connected
viewers, however the VNC protocol is pretty much self-adapting with
respect to that (updates are only packaged and sent when viewers ask
@@ -5956,27 +5988,27 @@ ied)
default should now be much better than before and dragging small
windows around should no longer be a huge pain. If for some reason
these changes make matters worse, you can go back to the old way via
- the "[518]-pointer_mode 1" option.
+ the "[520]-pointer_mode 1" option.
- Also added was the [519]-nodragging option that disables all screen
+ Also added was the [521]-nodragging option that disables all screen
updates while dragging with the mouse (i.e. mouse motion with a button
held down.) This gives the snappiest response, but might be undesired
in some circumstances when you want to see the visual feedback while
dragging (e.g. menu traversal or text selection.)
- As of Dec/2004 the [520]-pointer_mode n option was introduced. n=1 is
+ As of Dec/2004 the [522]-pointer_mode n option was introduced. n=1 is
the original mode, n=2 an improvement, etc.. See the -pointer_mode n
help for more info.
- Also, in some circumstances the [521]-threads option can improve
+ Also, in some circumstances the [523]-threads option can improve
response considerably. Be forewarned that if more than one vncviewer
is connected at the same time then libvncserver may not be thread safe
(try to get the viewers to use different VNC encodings, e.g. tight and
ZRLE.) This option can be unstable and so as of Feb/2008 it is
disabled by default. Set env. X11VNC_THREADED=1 to re-enable.
- As of Apr/2005 two new options (see the [522]wireframe FAQ and
- [523]scrollcopyrect FAQ below) provide schemes to sweep this problem
+ As of Apr/2005 two new options (see the [524]wireframe FAQ and
+ [525]scrollcopyrect FAQ below) provide schemes to sweep this problem
under the rug for window moves or resizes and for some (but not all)
window scrolls. These are the preferred way of avoiding the "lurching"
problem, contact me if they are not working. Note on SuSE and some
@@ -5989,7 +6021,7 @@ Section "Module"
EndSection
- Q-75: Why not do something like wireframe animations to avoid the
+ Q-76: Why not do something like wireframe animations to avoid the
windows "lurching" when being moved or resized?
Nice idea for a hack! As of Apr/2005 x11vnc by default will apply
@@ -6000,8 +6032,8 @@ EndSection
the window move/resize stops, it returns to normal processing: you
should only see the window appear in the new position. This spares you
from interacting with a "lurching" window between all of the
- intermediate steps. BTW the lurching is due to [524]slow video card
- read rates (see [525]here too.) A displacement, even a small one, of a
+ intermediate steps. BTW the lurching is due to [526]slow video card
+ read rates (see [527]here too.) A displacement, even a small one, of a
large window requires a non-negligible amount of time, a good fraction
of a second, to read in from the hardware framebuffer.
@@ -6009,7 +6041,7 @@ EndSection
for -wireframe to do any good.
The mode is currently on by default because most people are afflicted
- with the problem. It can be disabled with the [526]-nowireframe option
+ with the problem. It can be disabled with the [528]-nowireframe option
(aka -nowf.) Why might one want to turn off the wireframing? Since
x11vnc is merely guessing when windows are being moved/resized, it may
guess poorly for your window-manager or desktop, or even for the way
@@ -6055,13 +6087,13 @@ EndSection
* Maximum time to show a wireframe animation.
* Minimum time between sending wireframe outlines.
- See the [527]"-wireframe tweaks" option for more details. On a slow
+ See the [529]"-wireframe tweaks" option for more details. On a slow
link, e.g. dialup modem, the parameters may be automatically adjusted
for better response.
CopyRect encoding: In addition to the above there is the
- [528]"-wirecopyrect mode" option. It is also on by default. This
+ [530]"-wirecopyrect mode" option. It is also on by default. This
instructs x11vnc to not only show the wireframe animation, but to also
instruct all connected VNC viewers to locally translate the window
image data from the original position to the new position on the
@@ -6092,7 +6124,7 @@ EndSection
-nowirecopyrect if this or other painting errors are unacceptable.
- Q-76: Can x11vnc try to apply heuristics to detect when a window is
+ Q-77: Can x11vnc try to apply heuristics to detect when a window is
scrolling its contents and use the CopyRect encoding for a speedup?
Another nice idea for a hack! As of May/2005 x11vnc will by default
@@ -6109,7 +6141,7 @@ EndSection
requiring the image data to be transmitted over the network. For fast
links the speedup is primarily due to x11vnc not having to read the
scrolled framebuffer data from the X server (recall that reading from
- the hardware framebuffer is [529]slow.)
+ the hardware framebuffer is [531]slow.)
To do this x11vnc uses the RECORD X extension to snoop the X11
protocol between the X client with the focus window and the X server.
@@ -6136,10 +6168,10 @@ EndSection
the X server display: if one falls too far behind it could become a
mess...
- The initial implementation of [530]-scrollcopyrect option is useful in
+ The initial implementation of [532]-scrollcopyrect option is useful in
that it detects many scrolls and thus gives a much nicer working
- environment (especially when combined with the [531]-wireframe
- [532]-wirecopyrect [533]options, which are also on by default; and if
+ environment (especially when combined with the [533]-wireframe
+ [534]-wirecopyrect [535]options, which are also on by default; and if
you are willing to enable the ShadowFB things are very fast.) The fact
that there aren't long delays or lurches during scrolling is the
primary improvement.
@@ -6172,10 +6204,10 @@ EndSection
One can tap the Alt_L key (Left "Alt" key) 3 times in a row to
signal x11vnc to refresh the screen to all viewers. Your
VNC-viewer may have its own screen refresh hot-key or button. See
- also: [534]-fixscreen
+ also: [536]-fixscreen
* Some applications, notably OpenOffice, do XCopyArea scrolls in
weird ways that assume ancestor window clipping is taking place.
- See the [535]-scr_skip option for ways to tweak this on a
+ See the [537]-scr_skip option for ways to tweak this on a
per-application basis.
* Selecting text while dragging the mouse may be slower, especially
if the Button-down event happens near the window's edge. This is
@@ -6192,7 +6224,7 @@ EndSection
because it fails to detect scrolls in it. Sometimes clicking
inside the application window or selecting some text in it to
force the focus helps.
- * When using the [536]-scale option there will be a quick CopyRect
+ * When using the [538]-scale option there will be a quick CopyRect
scroll, but it needs to be followed by a slower "cleanup" update.
This is because for a fixed finite screen resolution (e.g. 75 dpi)
scaling and copyrect-ing are not exactly independent. Scaling
@@ -6205,7 +6237,7 @@ EndSection
If you find the -scrollcopyrect behavior too approximate or
distracting you can go back to the standard polling-only update method
- with the [537]-noscrollcopyrect (or -noscr for short.) If you find
+ with the [539]-noscrollcopyrect (or -noscr for short.) If you find
some extremely bad and repeatable behavior for -scrollcopyrect please
report a bug.
@@ -6226,13 +6258,13 @@ EndSection
errors.
- Q-77: Can x11vnc do client-side caching of pixel data? I.e. so when
+ Q-78: Can x11vnc do client-side caching of pixel data? I.e. so when
that pixel data is needed again it does not have to be retransmitted
over the network.
- As of Dec/2006 in the [538]0.9 development tarball there is an
+ As of Dec/2006 in the [540]0.9 development tarball there is an
experimental client-side caching implementation enabled by the
- "[539]-ncache n" option. In fact, during the test period it was on by
+ "[541]-ncache n" option. In fact, during the test period it was on by
default with n set to 10. To disable it use "-noncache".
It is a simple scheme where a (very large) lower portion of the
@@ -6259,7 +6291,7 @@ EndSection
there is a bug: you can scroll down in your viewer and see a strange
"history" of windows on your desktop. This is working as intended. One
will need to try to adjust the size of his VNC Viewer window so the
- cache area cannot be seen. [540]SSVNC (see below) can do this
+ cache area cannot be seen. [542]SSVNC (see below) can do this
automatically.
At some point LibVNCServer may implement a "rfbFBCrop" pseudoencoding
@@ -6269,7 +6301,7 @@ EndSection
rendering...)
The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice
- [541]-ycrop option to help hide the pixel cache area from view. It
+ [543]-ycrop option to help hide the pixel cache area from view. It
will turn on automatically if the framebuffer appears to be very tall
(height more than twice the width), or you can supply the actual value
for the height. If the screen is resized by scaling, etc, the ycrop
@@ -6300,7 +6332,7 @@ EndSection
an additional factor of 2 in memory use.
However, even in the smallest usage mode with n equal 2 and
- [542]-ncache_no_rootpixmap set (this requires only 2X additional
+ [544]-ncache_no_rootpixmap set (this requires only 2X additional
framebuffer memory) there is still a noticable improvement for many
activities, although it is not as dramatic as with, say n equal 12 and
rootpixmap (desktop background) caching enabled.
@@ -6311,7 +6343,7 @@ EndSection
be tuned to use less, or the VNC community will extend the protocol to
allow caching and replaying of compressed blobs of data.
- Another option to experiment with is "[543]-ncache_cr". By specifying
+ Another option to experiment with is "[545]-ncache_cr". By specifying
it, x11vnc will try to do smooth opaque window moves instead of its
wireframe. This can give a very nice effect (note: on Unix the realvnc
viewer seems to be smoother than the tightvnc viewer), but can lead to
@@ -6364,28 +6396,28 @@ EndSection
improving VNC performance by client side caching.
- Q-78: Does x11vnc support TurboVNC?
+ Q-79: Does x11vnc support TurboVNC?
As of Feb/2009 (development tarball) there is an experimental kludge
to let you build x11vnc using TurboVNC's modified TightVNC encoding.
- [544]TurboVNC is part of the [545]VirtualGL project. It does two main
+ [546]TurboVNC is part of the [547]VirtualGL project. It does two main
things to speed up the TightVNC encoding:
* It eliminates bottlenecks, overheads, wait-times in the TightVNC
encoding implementation and instead only worries about sending
very well (and quickly) compressed JPEG data.
* A fast proprietary JPEG implemention is used (Intel IPP on x86)
- instead of the usual libjpeg implementation. [546]TurboJPEG is an
+ instead of the usual libjpeg implementation. [548]TurboJPEG is an
interface library, libturbojpeg, provided by the project that
achieves this.
TurboVNC works very well over LAN and evidently fast Broadband too.
When using it with x11vnc in such a situation you may want to dial
- down the delays, e.g. "[547]-wait 5" and "[548]-defer 5" (or even a
+ down the delays, e.g. "[549]-wait 5" and "[550]-defer 5" (or even a
smaller setting) to poll and pump things out more quickly.
See the instructions in "x11vnc/misc/turbovnc/README" for how to build
x11vnc with TurboVNC support. You will also need to download the
- [549]TurboJPEG software.
+ [551]TurboJPEG software.
In brief, the steps look like this:
cd x11vnc-x.y.z/x11vnc/misc/turbovnc
@@ -6397,22 +6429,22 @@ EndSection
where you replace "/DIR" with the directory containing libturbojpeg.so
you downloaded separately. If it works out well enough TurboVNC
support will be integrated into x11vnc and more of its tuning features
- will be implemented. Support for TurboVNC in [550]SSVNC viewer has
+ will be implemented. Support for TurboVNC in [552]SSVNC viewer has
been added as an experiment as well. If you try either one, let us
know how it went.
There also may be some Linux.i686 and Darwin.i386 x11vnc binaries with
- TurboVNC support in the [551]misc. bins directory. For other platforms
+ TurboVNC support in the [553]misc. bins directory. For other platforms
you will need to compile yourself.
On relatively cheap and old hardware (Althon64 X2 5000+ / GeForce
- 6200) x11vnc and [552]SSVNC, both TurboVNC enabled, were able to
+ 6200) x11vnc and [554]SSVNC, both TurboVNC enabled, were able to
sustain 13.5 frames/sec (fps) and 15 Megapixels/sec using the
VirtualGL supplied OpenGL benchmark program glxspheres. VirtualGL on
- higher-end hardware can sustain [553]20-30 fps with the glxspheres
+ higher-end hardware can sustain [555]20-30 fps with the glxspheres
benchmark.
- Potential Slowdown: As we describe [554]elsewhere, unless you use
+ Potential Slowdown: As we describe [556]elsewhere, unless you use
x11vnc with an X server using, say, NVidia proprietary drivers (or a
virtual X server like Xvfb or Xdummy, or in ShadowFB mode), then the
read rate from the graphics card can be rather slow (e.g. 10 MB/sec)
@@ -6437,7 +6469,7 @@ EndSection
[Mouse Cursor Shapes]
- Q-79: Why isn't the mouse cursor shape (the little icon shape where
+ Q-80: Why isn't the mouse cursor shape (the little icon shape where
the mouse pointer is) correct as I move from window to window?
On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it
@@ -6452,23 +6484,23 @@ EndSection
this is because the cursor shape is often downloaded to the graphics
hardware (video card), but I could be mistaken.
- A simple kludge is provided by the "[555]-cursor X" option that
+ A simple kludge is provided by the "[557]-cursor X" option that
changes the cursor when the mouse is on the root background (or any
window has the same cursor as the root background.) Note that desktops
like GNOME or KDE often cover up the root background, so this won't
- work for those cases. Also see the "[556]-cursor some" option for
+ work for those cases. Also see the "[558]-cursor some" option for
additional kludges.
Note that as of Aug/2004 on Solaris using the SUN_OVL overlay
extension and IRIX, x11vnc can show the correct mouse cursor when the
- [557]-overlay option is supplied. See [558]this FAQ for more info.
+ [559]-overlay option is supplied. See [560]this FAQ for more info.
Also as of Dec/2004 XFIXES X extension support has been added to allow
exact extraction of the mouse cursor shape. XFIXES fixes the problem
of the cursor-shape being write-only: x11vnc can now query the X
server for the current shape and send it back to the connected
viewers. XFIXES is available on recent Linux Xorg based distros and
- [559]Solaris 10.
+ [561]Solaris 10.
The only XFIXES issue is the handling of alpha channel transparency in
cursors. If a cursor has any translucency then in general it must be
@@ -6476,10 +6508,10 @@ EndSection
situations where the cursor transparency can also handled exactly:
when the VNC Viewer requires the cursor shape be drawn into the VNC
framebuffer or if you apply a patch to your VNC Viewer to extract
- hidden alpha channel data under 32bpp. [560]Details can be found here.
+ hidden alpha channel data under 32bpp. [562]Details can be found here.
- Q-80: When using XFIXES cursorshape mode, some of the cursors look
+ Q-81: When using XFIXES cursorshape mode, some of the cursors look
really bad with extra black borders around the cursor and other cruft.
How can I improve their appearance?
@@ -6509,17 +6541,17 @@ EndSection
for most cursor themes and you don't have to worry about it.
In case it still looks bad for your cursor theme, there are (of
- course!) some tunable parameters. The "[561]-alphacut n" option lets
+ course!) some tunable parameters. The "[563]-alphacut n" option lets
you set the threshold "n" (between 0 and 255): cursor pixels with
alpha values below n will be considered completely transparent while
values equal to or above n will be completely opaque. The default is
- 240. The "[562]-alphafrac f" option tries to correct individual
+ 240. The "[564]-alphafrac f" option tries to correct individual
cursors that did not fare well with the default -alphacut value: if a
cursor has less than fraction f (between 0.0 and 1.0) of its pixels
selected by the default -alphacut, the threshold is lowered until f of
its pixels are selected. The default fraction is 0.33.
- Finally, there is an option [563]-alpharemove that is useful for
+ Finally, there is an option [565]-alpharemove that is useful for
themes where many cursors are light colored (e.g. "whiteglass".)
XFIXES returns the cursor data with the RGB values pre-multiplied by
the alpha value. If the white cursors look too grey, specify
@@ -6537,7 +6569,7 @@ EndSection
heavily on redglass) look fine with the apparent default of alphacut:255.
- Q-81: In XFIXES mode, are there any hacks to handle cursor
+ Q-82: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
As of Jan/2005 libvncserver has been modified to allow an alpha
@@ -6545,10 +6577,10 @@ EndSection
alpha channel data to libvncserver. However, this data will only be
used for VNC clients that do not support the CursorShapeUpdates VNC
extension (or have disabled it.) It can be disabled for all clients
- with the [564]-nocursorshape x11vnc option. In this case the cursor is
+ with the [566]-nocursorshape x11vnc option. In this case the cursor is
drawn, correctly blended with the background, into the VNC framebuffer
before being sent out to the client. So the alpha blending is done on
- the x11vnc side. Use the [565]-noalphablend option to disable this
+ the x11vnc side. Use the [567]-noalphablend option to disable this
behavior (always approximate transparent cursors with opaque RGB
values.)
@@ -6572,17 +6604,17 @@ EndSection
example on how to change the Windows TightVNC viewer to achieve the
same thing (send me the patch if you get that working.)
- This patch is applied to the [566]Enhanced TightVNC Viewer (SSVNC)
+ This patch is applied to the [568]Enhanced TightVNC Viewer (SSVNC)
package we provide.
[Mouse Pointer]
- Q-82: Why does the mouse arrow just stay in one corner in my
+ Q-83: Why does the mouse arrow just stay in one corner in my
vncviewer, whereas my cursor (that does move) is just a dot?
- This default takes advantage of a [567]tightvnc extension
+ This default takes advantage of a [569]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [568]-nocursor
+ the local VNC viewer. You may disable it with the [570]-nocursor
option to x11vnc if your viewer does not have this extension.
Note: as of Aug/2004 this should be fixed: the default for
@@ -6591,22 +6623,22 @@ EndSection
can also be disabled via -nocursor.
- Q-83: Can I take advantage of the TightVNC extension to the VNC
+ Q-84: Can I take advantage of the TightVNC extension to the VNC
protocol where Cursor Positions Updates are sent back to all connected
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- Use the [569]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [571]-cursorpos option when starting x11vnc. A VNC viewer must
support the Cursor Positions Updates for the user to see the mouse
motions (the TightVNC viewers support this.) As of Aug/2004 -cursorpos
- is the default. See also [570]-nocursorpos and [571]-nocursorshape.
+ is the default. See also [572]-nocursorpos and [573]-nocursorshape.
- Q-84: Is it possible to swap the mouse buttons (e.g. left-handed
+ Q-85: Is it possible to swap the mouse buttons (e.g. left-handed
operation), or arbitrarily remap them? How about mapping button clicks
to keystrokes, e.g. to partially emulate Mouse wheel scrolling?
- You can remap the mouse buttons via something like: [572]-buttonmap
+ You can remap the mouse buttons via something like: [574]-buttonmap
13-31 (or perhaps 12-21.) Also, note that xmodmap(1) lets you directly
adjust the X server's button mappings, but in some circumstances it
might be more desirable to have x11vnc do it.
@@ -6614,7 +6646,7 @@ EndSection
One user had an X server with only one mouse button(!) and was able to
map all of the VNC client mouse buttons to it via: -buttonmap 123-111.
- Note that the [573]-debug_pointer option prints out much info for
+ Note that the [575]-debug_pointer option prints out much info for
every mouse/pointer event and is handy in solving problems.
To map mouse button clicks to keystrokes you can use the alternate
@@ -6636,7 +6668,7 @@ EndSection
Exactly what keystroke "scrolling" events they should be bound to
depends on one's taste. If this method is too approximate, one could
- consider not using [574]-buttonmap but rather configuring the X server
+ consider not using [576]-buttonmap but rather configuring the X server
to think it has a mouse with 5 buttons even though the physical mouse
does not. (e.g. 'Option "ZAxisMapping" "4 5"'.)
@@ -6663,10 +6695,10 @@ EndSection
"click" usually gives a multi-line scroll.)
[Keyboard Issues]
- Q-85: How can I get my AltGr and Shift modifiers to work between
+ Q-86: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [575]-modtweak should help here. It is a mode that monitors
+ The option [577]-modtweak should help here. It is a mode that monitors
the state of the Shift and AltGr Modifiers and tries to deduce the
correct keycode to send, possibly by sending fake modifier key presses
and releases in addition to the actual keystroke.
@@ -6675,25 +6707,25 @@ EndSection
to get the old behavior.) This was done because it was noticed on
newer XFree86 setups even on bland "us" keyboards like "pc104 us"
XFree86 included a "ghost" key with both "<" and ">" it. This key does
- not exist on the keyboard (see [576]this FAQ for more info.) Without
+ not exist on the keyboard (see [578]this FAQ for more info.) Without
-modtweak there was then an ambiguity in the reverse map keysym =>
keycode, making it so the "<" symbol could not be typed.
- Also see the [577]FAQ about the -xkb option for a more powerful method
+ Also see the [579]FAQ about the -xkb option for a more powerful method
of modifier tweaking for use on X servers with the XKEYBOARD
extension.
When trying to resolve keyboard mapping problems, note that the
- [578]-debug_keyboard option prints out much info for every keystroke
+ [580]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
Note that one user had a strange setup and none of the above helped.
- His solution was to disable all of the above and use [579]-nomodtweak.
+ His solution was to disable all of the above and use [581]-nomodtweak.
This is the simplest form of keystroke insertion and it actually
solved the problem. Try it if the other options don't help.
- Q-86: When I try to type a "<" (i.e. less than) instead I get ">"
+ Q-87: When I try to type a "<" (i.e. less than) instead I get ">"
(i.e. greater than)! Strangely, typing ">" works OK!!
Does your keyboard have a single key with both "<" and ">" on it? Even
@@ -6701,9 +6733,9 @@ EndSection
(e.g. pc105 in the XF86Config file when it should be something else,
say pc104.)
- Short Cut: Try the [580]-xkb or [581]-sloppy_keys options and see if
+ Short Cut: Try the [582]-xkb or [583]-sloppy_keys options and see if
that helps the situation. The discussion below is a bit outdated (e.g.
- [582]-modtweak is now the default) but it is useful reference for
+ [584]-modtweak is now the default) but it is useful reference for
various tricks and so is kept.
@@ -6746,25 +6778,25 @@ EndSection
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([583]-modtweak) is a mode that monitors the
+ settings. The former ([585]-modtweak) is a mode that monitors the
state of the Shift and AltGr modifiers and tries to deduce the correct
keycode sequence to send. Since Jul/2004 -modtweak is now the default.
- The latter ([584]-remap less-comma) is an immediate remapping of the
+ The latter ([586]-remap less-comma) is an immediate remapping of the
keysym less to the keysym comma when it comes in from a client (so
when Shift is down the comma press will yield "<".)
- See also the [585]FAQ about the -xkb option as a possible workaround
+ See also the [587]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [586]-debug_keyboard option prints out much info for
+ Note that the [588]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
- Q-87: Extra Character Inserted, E.g.: When I try to type a "<" (i.e.
+ Q-88: Extra Character Inserted, E.g.: When I try to type a "<" (i.e.
less than) instead I get "<," (i.e. an extra comma.)
This is likely because you press "Shift" then "<" but then released
- the Shift key before releasing the "<". Because of a [587]keymapping
+ the Shift key before releasing the "<". Because of a [589]keymapping
ambiguity the last event "< up" is interpreted as "," because that key
unshifted is the comma.
@@ -6772,16 +6804,16 @@ EndSection
characters: in general it can happen whenever the Shift key is
released early.
- This should not happen in [588]-xkb mode, because it works hard to
+ This should not happen in [590]-xkb mode, because it works hard to
resolve the ambiguities. If you do not want to use -xkb, try the
- option [589]-sloppy_keys to attempt a similar type of algorithm.
+ option [591]-sloppy_keys to attempt a similar type of algorithm.
One user had this problem for Italian and German keyboards with the
key containing ":" and "." When he typed ":" he would get an extra "."
inserted after the ":". The solution was -sloppy_keys.
- Q-88: I'm using an "international" keyboard (e.g. German "de", or
+ Q-89: I'm using an "international" keyboard (e.g. German "de", or
Danish "dk") and the -modtweak mode works well if the VNC viewer is
run on a Unix/Linux machine with a similar keyboard. But if I run
the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or
@@ -6802,7 +6834,7 @@ EndSection
In both cases no AltGr is sent to the VNC server, but we know AltGr is
needed on the physical international keyboard to type a "@".
- This all worked fine with x11vnc running with the [590]-modtweak
+ This all worked fine with x11vnc running with the [592]-modtweak
option (it figures out how to adjust the Modifier keys (Shift or
AltGr) to get the "@".) However it fails under recent versions of
XFree86 (and the X.org fork.) These run the XKEYBOARD extension by
@@ -6819,7 +6851,7 @@ EndSection
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [591]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [593]-xkb option seems to fix all of the missing keys: "@", "<",
">", etc.: it is recommended that you try it if you have this sort of
problem. Let us know if there are any remaining problems (see the next
paragraph for some known problems.) If you specify the -debug_keyboard
@@ -6827,7 +6859,7 @@ EndSection
debugging output (send it along with any problems you report.)
Update: as of Jun/2005 x11vnc will try to automatically enable
- [592]-xkb if it appears that would be beneficial (e.g. if it sees any
+ [594]-xkb if it appears that would be beneficial (e.g. if it sees any
of "@", "<", ">", "[" and similar keys are mapped in a way that needs
the -xkb to access them.) To disable this automatic check use -noxkb.
@@ -6842,7 +6874,7 @@ EndSection
was attached to keycode 93 (no physical key generates this
keycode) while ISO_Level3_Shift was attached to keycode 113. The
keycode skipping option was used to disable the ghost key:
- [593]-skip_keycodes 93
+ [595]-skip_keycodes 93
* In implementing -xkb we noticed that some characters were still
not getting through, e.g. "~" and "^". This is not really an
XKEYBOARD problem. What was happening was the VNC viewer was
@@ -6860,16 +6892,16 @@ EndSection
What to do? In general the VNC protocol has not really solved this
problem: what should be done if the VNC viewer sends a keysym not
recognized by the VNC server side? Workarounds can possibly be
- created using the [594]-remap x11vnc option:
+ created using the [596]-remap x11vnc option:
-remap asciitilde-dead_tilde,asciicircum-dead_circumflex
etc. Use -remap filename if the list is long. Please send us your
workarounds for this problem on your keyboard. Perhaps we can have
x11vnc adjust automatically at some point. Also see the
- [595]-add_keysyms option in the next paragraph.
- Update: for convenience "[596]-remap DEAD" does many of these
+ [597]-add_keysyms option in the next paragraph.
+ Update: for convenience "[598]-remap DEAD" does many of these
mappings at once.
- * To complement the above workaround using the [597]-remap, an
- option [598]-add_keysyms was added. This option instructs x11vnc
+ * To complement the above workaround using the [599]-remap, an
+ option [600]-add_keysyms was added. This option instructs x11vnc
to bind any unknown Keysyms coming in from VNC viewers to unused
Keycodes in the X server. This modifies the global state of the X
server. When x11vnc exits it removes the extra keymappings it
@@ -6880,7 +6912,7 @@ EndSection
disable.
- Q-89: When typing I sometimes get double, triple, or more of my
+ Q-90: When typing I sometimes get double, triple, or more of my
keystrokes repeated. I'm sure I only typed them once, what can I do?
This may be due to an interplay between your X server's key autorepeat
@@ -6888,7 +6920,7 @@ EndSection
Short answer: disable key autorepeating by running the command "xset r
off" on the Xserver where x11vnc is run (restore via "xset r on") or
- use the new (Jul/2004) [599]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [601]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side.
@@ -6912,18 +6944,18 @@ EndSection
off", does the problem go away?
The workaround is to manually apply "xset r off" and "xset r on" as
- needed, or to use the [600]-norepeat (which has since Dec/2004 been
+ needed, or to use the [602]-norepeat (which has since Dec/2004 been
made the default.) Note that with X server autorepeat turned off the
VNC viewer side of the connection will (nearly always) do its own
autorepeating so there is no big loss here, unless someone is also
working at the physical display and misses his autorepeating.
- Q-90: The x11vnc -norepeat mode is in effect, but I still get repeated
+ Q-91: The x11vnc -norepeat mode is in effect, but I still get repeated
keystrokes!!
Are you using x11vnc to log in to an X session via display manager?
- (as described in [601]this FAQ) If so, x11vnc is starting before your
+ (as described in [603]this FAQ) If so, x11vnc is starting before your
session and it disables autorepeat when you connect, but then after
you log in your session startup (GNOME, KDE, ...) could be resetting
the autorepeat to be on. Or it could be something inside your desktop
@@ -6943,7 +6975,7 @@ EndSection
should figure out how to disable that somehow.
- Q-91: After using x11vnc for a while, I find that I cannot type some
+ Q-92: After using x11vnc for a while, I find that I cannot type some
(or any) characters or my mouse clicks and drags no longer have any
effect, or they lead to strange effects. What happened?
@@ -6984,11 +7016,11 @@ EndSection
desktop manages these "warps". If the viewer is not notified it cannot
know it needs to release the modifiers.
- You can also use the [602]-clear_mods option to try to clear all of
+ You can also use the [604]-clear_mods option to try to clear all of
the modifier keys at x11vnc startup. You will still have to be careful
that you do not leave the modifier key pressed down during your
session. It is difficult to prevent this problem from occurring (short
- of using [603]-remap to prevent sending all of the problem modifier
+ of using [605]-remap to prevent sending all of the problem modifier
keys, which would make the destkop pretty unusable.)
During a session these x11vnc remote control commands can also help:
@@ -7001,16 +7033,16 @@ EndSection
Num_Lock down. When these are locked on the remote side it can
sometimes lead to strange desktop behavior (e.g. cannot drag or click
on windows.) As above you may not notice this because the lock isn't
- down on the local (Viewer) side. See [604]this FAQ on lock keys
- problem. These options may help avoid the problem: [605]-skip_lockkeys
- and [606]-capslock. See also [607]-clear_all.
+ down on the local (Viewer) side. See [606]this FAQ on lock keys
+ problem. These options may help avoid the problem: [607]-skip_lockkeys
+ and [608]-capslock. See also [609]-clear_all.
- Q-92: The machine where I run x11vnc has an AltGr key, but the local
+ Q-93: The machine where I run x11vnc has an AltGr key, but the local
machine where I run the VNC viewer does not. Is there a way I can map
a local unused key to send an AltGr? How about a Compose key as well?
- Something like "[608]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[610]-remap Super_R-Mode_switch" x11vnc option may
work. Note that Super_R is the "Right Windoze(tm) Flaggie" key; you
may want to choose another. The -debug_keyboard option comes in handy
in finding keysym names (so does xev(1).)
@@ -7021,7 +7053,7 @@ EndSection
specify remappings from a file.
- Q-93: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
+ Q-94: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
one Alt key labelled "Alt" and two Meta keys labelled with little
diamonds. The machine where I run the VNC viewer only has Alt keys.
How can I send a Meta keypress? (e.g. emacs needs this)
@@ -7033,13 +7065,13 @@ EndSection
Since xmodmap(1) modifies the X server mappings you may not want to do
this (because it affects local work on that machine.) Something like
- the [609]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [611]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
needs, and does not modify the X server environment. Note that you
cannot send Alt_L in this case, maybe -remap Super_L-Meta_L would be a
better choice if the Super_L key is typically unused in Unix.
- Q-94: Running x11vnc on HP-UX I cannot type "#" I just get a "3"
+ Q-95: Running x11vnc on HP-UX I cannot type "#" I just get a "3"
instead.
One user reports this problem on HP-UX Rel_B.11.23. The problem was
@@ -7053,7 +7085,7 @@ EndSection
and similar triple mappings (with two in the AltGr/Mode_switch group)
of a keysum to a single keycode.
- Use the [610]-nomodtweak option as a workaround. You can also use
+ Use the [612]-nomodtweak option as a workaround. You can also use
xmodmap to correct these mappings in the server, e.g.:
xmodmap -e "keycode 47 = 3 numbersign"
@@ -7062,12 +7094,12 @@ EndSection
handle these mappings better.
- Q-95: Can I map a keystroke to a mouse button click on the remote
+ Q-96: Can I map a keystroke to a mouse button click on the remote
machine?
This can be done directly in some X servers using AccessX and
Pointer_EnableKeys, but is a bit awkward. It may be more convenient to
- have x11vnc do the remapping. This can be done via the [611]-remap
+ have x11vnc do the remapping. This can be done via the [613]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -7076,7 +7108,7 @@ EndSection
button "paste" because (using XFree86/Xorg Emulate3Buttons) you have
to click both buttons on the touch pad at the same time. This
remapping:
- [612]-remap Super_R-Button2
+ [614]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -7085,7 +7117,7 @@ EndSection
are generated immediately on the x11vnc side. When the key is released
(i.e. goes up) no events are generated.
- Q-96: How can I get Caps_Lock to work between my VNC viewer and
+ Q-97: How can I get Caps_Lock to work between my VNC viewer and
x11vnc?
This is a little tricky because it is possible to get the Caps_Lock
@@ -7095,13 +7127,13 @@ EndSection
Caps_Lock in the viewer your local machine goes into the Caps_Lock on
state and sends keysym "A" say when you press "a". x11vnc will then
fake things up so that Shift is held down to generate "A". The
- [613]-skip_lockkeys option should help to accomplish this. For finer
- grain control use something like: "[614]-remap Caps_Lock-None".
+ [615]-skip_lockkeys option should help to accomplish this. For finer
+ grain control use something like: "[616]-remap Caps_Lock-None".
- Also try the [615]-nomodtweak and [616]-capslock options.
+ Also try the [617]-nomodtweak and [618]-capslock options.
Another useful option that turns off any Lock keys on the remote side
- at startup and end is the [617]-clear_all option. During a session you
+ at startup and end is the [619]-clear_all option. During a session you
can run these remote control commands to modify the Lock keys:
x11vnc -R clear_locks
x11vnc -R clear_all
@@ -7111,7 +7143,7 @@ EndSection
etc.)
[Screen Related Issues and Features]
- Q-97: The remote display is larger (in number of pixels) than the
+ Q-98: The remote display is larger (in number of pixels) than the
local display I am running the vncviewer on. I don't like the
vncviewer scrollbars, what I can do?
@@ -7130,15 +7162,15 @@ EndSection
There may also be scaling viewers out there (e.g. TightVNC or UltraVNC
on Windows) that automatically shrink or expand the remote framebuffer
to fit the local display. Especially for hand-held devices. See also
- [618]the next FAQ on x11vnc scaling.
+ [620]the next FAQ on x11vnc scaling.
- Q-98: Does x11vnc support server-side framebuffer scaling? (E.g. to
+ Q-99: Does x11vnc support server-side framebuffer scaling? (E.g. to
make the desktop smaller.)
As of Jun/2004 x11vnc provides basic server-side scaling. It is a
global scaling of the desktop, not a per-client setting. To enable it
- use the "[619]-scale fraction" option. "fraction" can either be a
+ use the "[621]-scale fraction" option. "fraction" can either be a
floating point number (e.g. -scale 0.75) or the alternative m/n
fraction notation (e.g. -scale 3/4.) Note that if fraction is greater
than one the display is magnified.
@@ -7163,7 +7195,7 @@ EndSection
One can also use the ":nb" with an integer scale factor (say "-scale
2:nb") to use x11vnc as a screen magnifier for vision impaired
- [620]applications. Since with integer scale factors the framebuffers
+ [622]applications. Since with integer scale factors the framebuffers
become huge and scaling operations time consuming, be sure to use
":nb" for the fastest response.
@@ -7189,7 +7221,7 @@ EndSection
If one desires per-client scaling for something like 1:1 from a
workstation and 1:2 from a smaller device (e.g. handheld), currently
the only option is to run two (or more) x11vnc processes with
- different scalings listening on separate ports ([621]-rfbport option,
+ different scalings listening on separate ports ([623]-rfbport option,
etc.)
Update: As of May/2006 x11vnc also supports the UltraVNC server-side
@@ -7199,8 +7231,8 @@ EndSection
"-rfbversion 3.6" for this to be recognized by UltraVNC viewers.
BTW, whenever you run two or more x11vnc's on the same X display and
- use the [622]GUI, then to avoid all of the x11vnc's simultaneously
- answering the gui you will need to use something like [623]"-connect
+ use the [624]GUI, then to avoid all of the x11vnc's simultaneously
+ answering the gui you will need to use something like [625]"-connect
file1 -gui ..." with different connect files for each x11vnc you want
to control via the gui (or remote-control.) The "-connect file1" usage
gives separate communication channels between a x11vnc process and the
@@ -7209,12 +7241,12 @@ EndSection
Update: As of Mar/2005 x11vnc now scales the mouse cursor with the
same scale factor as the screen. If you don't want that, use the
- [624]"-scale_cursor frac" option to set the cursor scaling to a
+ [626]"-scale_cursor frac" option to set the cursor scaling to a
different factor (e.g. use "-scale_cursor 1" to keep the cursor at its
natural unscaled size.)
- Q-99: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
+ Q-100: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
together to form one big, single screen.)
Yes, it should generally work because it simply polls the big
@@ -7237,26 +7269,26 @@ EndSection
screen is not rectangular (e.g. 1280x1024 and 1024x768 monitors joined
together), then there will be "non-existent" areas on the screen. The
X server will return "garbage" image data for these areas and so they
- may be distracting to the viewer. The [625]-blackout x11vnc option
+ may be distracting to the viewer. The [627]-blackout x11vnc option
allows you to blacken-out rectangles by manually specifying their
WxH+X+Y geometries. If your system has the libXinerama library, the
- [626]-xinerama x11vnc option can be used to have it automatically
+ [628]-xinerama x11vnc option can be used to have it automatically
determine the rectangles to be blackened out. (Note on 8bpp
PseudoColor displays the fill color may not be black.) Update:
- [627]-xinerama is now on by default.
+ [629]-xinerama is now on by default.
Some users have reported that the mouse does not behave properly for
their Xinerama display: i.e. the mouse cannot be moved to all regions
- of the large display. If this happens try using the [628]-xwarppointer
+ of the large display. If this happens try using the [630]-xwarppointer
option. This instructs x11vnc to fake mouse pointer motions using the
XWarpPointer function instead of the XTestFakeMotionEvent XTEST
function. (This may be due to a bug in the X server for XTEST when
- Xinerama is enabled.) Update: As of Dec/2006 [629]-xwarppointer will
+ Xinerama is enabled.) Update: As of Dec/2006 [631]-xwarppointer will
be applied automatically if Xinerama is detected. To disable use:
-noxwarppointer
- Q-100: Can I use x11vnc on a multi-headed display that is not Xinerama
+ Q-101: Can I use x11vnc on a multi-headed display that is not Xinerama
(i.e. separate screens :0.0, :0.1, ... for each monitor)?
You can, but it is a little bit awkward: you must start separate
@@ -7274,32 +7306,32 @@ EndSection
Note: if you are running on Solaris 8 or earlier you can easily hit up
against the maximum of 6 shm segments per process (for Xsun in this
case) from running multiple x11vnc processes. You should modify
- /etc/system as mentioned in another [630]FAQ to increase the limit. It
- is probably also a good idea to run with the [631]-onetile option in
+ /etc/system as mentioned in another [632]FAQ to increase the limit. It
+ is probably also a good idea to run with the [633]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [632]-noshm to use no shm segments.
+ [634]-noshm to use no shm segments.
- Q-101: Can x11vnc show only a portion of the display? (E.g. for a
+ Q-102: Can x11vnc show only a portion of the display? (E.g. for a
special purpose application or a very large screen.)
- As of Mar/2005 x11vnc has the "[633]-clip WxH+X+Y" option to select a
+ As of Mar/2005 x11vnc has the "[635]-clip WxH+X+Y" option to select a
rectangle of width W, height H and offset (X, Y). Thus the VNC screen
will be the clipped sub-region of the display and be only WxH in size.
- One user used -clip to split up a large [634]Xinerama screen into two
+ One user used -clip to split up a large [636]Xinerama screen into two
more managable smaller screens.
This also works to view a sub-region of a single application window if
- the [635]-id or [636]-sid options are used. The offset is measured
+ the [637]-id or [638]-sid options are used. The offset is measured
from the upper left corner of the selected window.
- Q-102: Does x11vnc support the XRANDR (X Resize, Rotate and
+ Q-103: Does x11vnc support the XRANDR (X Resize, Rotate and
Reflection) extension? Whenever I rotate or resize the screen x11vnc
just seems to crash.
As of Dec/2004 x11vnc supports XRANDR. You enable it with the
- [637]-xrandr option to make x11vnc monitor XRANDR events and also trap
+ [639]-xrandr option to make x11vnc monitor XRANDR events and also trap
X server errors if the screen change occurred in the middle of an X
call like XGetImage. Once it traps the screen change it will create a
new framebuffer using the new screen.
@@ -7309,9 +7341,9 @@ EndSection
then the viewer will automatically resize. Otherwise, the new
framebuffer is fit as best as possible into the original viewer size
(portions of the screen may be clipped, unused, etc.) For these
- viewers you can try the [638]-padgeom option to make the region big
+ viewers you can try the [640]-padgeom option to make the region big
enough to hold all resizes and rotations. We have fixed this problem
- for the TightVNC Viewer on Unix: [639]SSVNC
+ for the TightVNC Viewer on Unix: [641]SSVNC
If you specify "-xrandr newfbsize" then vnc viewers that do not
support NewFBSize will be disconnected before the resize. If you
@@ -7319,21 +7351,21 @@ EndSection
terminate.
- Q-103: Independent of any XRANDR, can I have x11vnc rotate and/or
+ Q-104: Independent of any XRANDR, can I have x11vnc rotate and/or
reflect the screen that the VNC viewers see? (e.g. for a handheld
whose screen is rotated 90 degrees.)
- As of Jul/2006 there is the [640]-rotate option allow this. E.g's:
+ As of Jul/2006 there is the [642]-rotate option allow this. E.g's:
"-rotate +90", "-rotate -90", "-rotate x", etc.
- Q-104: Why is the view in my VNC viewer completely black? Or why is
+ Q-105: Why is the view in my VNC viewer completely black? Or why is
everything flashing around randomly?
See the next FAQ for a possible explanation.
- Q-105: I use Linux Virtual Terminals (VT's) to implement 'Fast User
+ Q-106: I use Linux Virtual Terminals (VT's) to implement 'Fast User
Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7,
Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those
keystrokes to switch between their sessions.) How come the view in a
@@ -7362,7 +7394,7 @@ EndSection
"chvt 7" for VT #7.
- Q-106: I am using x11vnc where my local machine has "popup/hidden
+ Q-107: I am using x11vnc where my local machine has "popup/hidden
taskbars" and the remote display where x11vnc runs also has
"popup/hidden taskbars" and they interfere and fight with each other.
What can I do?
@@ -7377,7 +7409,7 @@ EndSection
click on the task bar panel, and uncheck "enable auto-hide" from the
panel properties dialog box. This will make the panel always visible.
- Q-107: Help! x11vnc and my KDE screensaver keep switching each other
+ Q-108: Help! x11vnc and my KDE screensaver keep switching each other
on and off every few seconds.
This is a new (Jul/2006) problem seen, say, on the version of KDE that
@@ -7388,13 +7420,13 @@ EndSection
This may be a bug in kdesktop_lock. For now the only workaround is to
disable the screensaver. You can try using another one such as
- straight xscreensaver (see the instructions [641]here for how to
+ straight xscreensaver (see the instructions [643]here for how to
disable kdesktop_lock.) If you have more info on this or see it
outside of KDE please let us know.
Update: It appears this is due to kdesktop_lock enabling the screen
saver when the Monitor is in DPMS low-power state (e.g. standby,
- suspend, or off.) In Nov/2006 the x11vnc [642]-nodpms option was added
+ suspend, or off.) In Nov/2006 the x11vnc [644]-nodpms option was added
as a workaround. Normally it is a good thing that the monitor powers
down (since x11vnc can still poll the framebuffer in this state), but
if you experience the kdesktop_lock problem you can specify the
@@ -7404,22 +7436,22 @@ EndSection
disable the screensaver.) Feel free to file a bug against
kdesktop_lock with KDE.
- Q-108: I am running the beryl 3D window manager (or compiz, MythTv,
+ Q-109: I am running the beryl 3D window manager (or compiz, MythTv,
Google Earth, or some other OpenGL app) and I do not get screen
updates in x11vnc.
This appears to be because the 3D OpenGL/GLX hardware screen updates
do not get reported via the XDAMAGE mechanism. So this is a bug in
- [643]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video
+ [645]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video
card driver.
- As a workaround apply the [644]-noxdamage option. As of Feb/2007
+ As a workaround apply the [646]-noxdamage option. As of Feb/2007
x11vnc will try to autodetect the problem and disable XDAMAGE if is
appears to be missing a lot of updates. But if you know you are using
- beryl you might as well always supply -noxdamage. Thanks to [645]this
+ beryl you might as well always supply -noxdamage. Thanks to [647]this
user who reported the problem and discovered the workaround.
- A developer for [646]MiniMyth reports that the 'alphapulse' tag of the
+ A developer for [648]MiniMyth reports that the 'alphapulse' tag of the
theme G.A.N.T. can also cause problems, and should be avoided when
using VNC.
@@ -7428,7 +7460,7 @@ EndSection
responsiveness (especially for typing) and also leads to unnecessary
CPU and memory I/O load due to the extra polling.
- Q-109: Can I use x11vnc to view my VMWare session remotely?
+ Q-110: Can I use x11vnc to view my VMWare session remotely?
Yes, since VMWare usually runs as an X application you can view it via
x11vnc in the normal way.
@@ -7439,9 +7471,9 @@ EndSection
* Fullscreen mode
The way VMWare does Fullscreen mode on Linux is to display the Guest
- desktop in a separate Virtual Terminal (e.g. VT 8) (see [647]this FAQ
+ desktop in a separate Virtual Terminal (e.g. VT 8) (see [649]this FAQ
on VT's for background.) Unfortunately, this Fullscreen VT is not an X
- server. So x11vnc cannot access it (however, [648]see this discussion
+ server. So x11vnc cannot access it (however, [650]see this discussion
of -rawfb for a possible workaround.) x11vnc works fine with "Normal X
application window" and "Quick-Switch mode" because these use X.
@@ -7462,13 +7494,13 @@ EndSection
improve response. One can also cut the display depth (e.g. to 16bpp)
in this 2nd X session to improve video performance. This 2nd X session
emulates Fullscreen mode to some degree and can be viewed via x11vnc
- as long as the VMWare X session [649]is in the active VT.
+ as long as the VMWare X session [651]is in the active VT.
Also note that with a little bit of playing with "xwininfo -all
-children" output one can extract the (non-toplevel) window-id of the
of the Guest desktop only when VMWare is running as a normal X
application. Then one can export just the guest desktop (i.e. without
- the VMWare menu buttons) by use of the [650]-id windowid option. The
+ the VMWare menu buttons) by use of the [652]-id windowid option. The
caveats are the X session VMWare is in must be in the active VT and
the window must be fully visible, so this mode is not terribly
convenient, but could be useful in some circumstances (e.g. running
@@ -7480,14 +7512,14 @@ EndSection
[Exporting non-X11 devices via VNC]
- Q-110: Can non-X devices (e.g. a raw framebuffer) be viewed (and even
+ Q-111: Can non-X devices (e.g. a raw framebuffer) be viewed (and even
controlled) via VNC with x11vnc?
As of Apr/2005 there is support for this. Two options were added:
- "[651]-rawfb string" (to indicate the raw frame buffer device, file,
- etc. and its parameters) and "[652]-pipeinput command" (to provide an
+ "[653]-rawfb string" (to indicate the raw frame buffer device, file,
+ etc. and its parameters) and "[654]-pipeinput command" (to provide an
external program that will inject or otherwise process mouse and
- keystroke input.) Some useful [653]-pipeinput schemes, VID, CONSOLE,
+ keystroke input.) Some useful [655]-pipeinput schemes, VID, CONSOLE,
and UINPUT, have since been built into x11vnc for convenience.
This non-X mode for x11vnc is somewhat experimental because it is so
@@ -7527,9 +7559,9 @@ EndSection
access method.) Only use file if map isn't working. BTW, "mmap" is an
alias for "map" and if you do not supply a type and the file exists,
map is assumed (see the -help output and below for some exceptions to
- this.) The "snap:" setting applies the [654]-snapfb option with
+ this.) The "snap:" setting applies the [656]-snapfb option with
"file:" type reading (this is useful for exporting webcams or TV tuner
- video; see [655]the next FAQ for more info.)
+ video; see [657]the next FAQ for more info.)
Also, if the string is of the form "setup:cmd" then cmd is run and the
first line of its output retrieved and used as the rawfb string. This
@@ -7574,7 +7606,7 @@ EndSection
screen to either shm or a mapped file. The format of these is XWD and
so the initial header should be skipped. BTW, since XWD is not
strictly RGB the view will only be approximate, but usable. Of course
- for the case of Xvfb x11vnc can poll it much better via the [656]X
+ for the case of Xvfb x11vnc can poll it much better via the [658]X
API, but you get the idea.
By default in -rawfb mode x11vnc will actually close any X display it
@@ -7605,13 +7637,13 @@ minal #2)
tty1-tty6), or X graphical display (usually starting at tty7.) In
addition to the text console other graphical ones may be viewed and
interacted with as well, e.g. DirectFB or SVGAlib apps, VMWare non-X
- fullscreen, or [657]Qt-embedded apps (PDAs/Handhelds.) By default the
+ fullscreen, or [659]Qt-embedded apps (PDAs/Handhelds.) By default the
pipeinput mechanisms UINPUT and CONSOLE (keystrokes only) are
automatically attempted in this mode under "-rawfb console".
The Video4Linux Capture device, /dev/video0, etc is either a Webcam or
a TV capture device and needs to have its driver enabled in the
- kernel. See [658]this FAQ for details. If specified via "-rawfb Video"
+ kernel. See [660]this FAQ for details. If specified via "-rawfb Video"
then the pipeinput method "VID" is applied (it lets you change video
parameters dynamically via keystrokes.)
@@ -7619,10 +7651,10 @@ minal #2)
also useful in testing.
- All of the above [659]-rawfb options are just for viewing the raw
+ All of the above [661]-rawfb options are just for viewing the raw
framebuffer (although some of the aliases do imply keystroke and mouse
pipeinput methods.) That may be enough for certain applications of
- this feature (e.g. suppose a [660]video camera mapped its framebuffer
+ this feature (e.g. suppose a [662]video camera mapped its framebuffer
into memory and you just wanted to look at it via VNC.)
To handle the pointer and keyboard input from the viewer users the
"-pipeinput cmd" option was added to indicate a helper program to
@@ -7660,7 +7692,7 @@ minal #2)
keystrokes into the Linux console (e.g. the virtual consoles:
/dev/tty1, /dev/tty2, etc) in x11vnc/misc/vcinject.pl. It is based on
the vncterm/LinuxVNC.c program also in the libvncserver CVS. So to
- view and interact with VT #2 (assuming it is the [661]active VT) one
+ view and interact with VT #2 (assuming it is the [663]active VT) one
can run something like:
x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
@@ -7715,7 +7747,7 @@ minal #2)
better to use the more accurate and faster LinuxVNC program. The
advantage x11vnc -rawfb might have is that it can allow interaction
with a non-text application, e.g. one based on SVGAlib or
- [662]Qt-embedded Also, for example the [663]VMWare Fullscreen mode is
+ [664]Qt-embedded Also, for example the [665]VMWare Fullscreen mode is
actually viewable under -rawfb and can be interacted with if uinput is
enabled.
@@ -7732,7 +7764,7 @@ minal #2)
program that passes the framebuffer to libvncserver.
- Q-111: Can I export the Linux Console (Virtual Terminals) via VNC
+ Q-112: Can I export the Linux Console (Virtual Terminals) via VNC
using x11vnc?
Yes, you may need to be root to access the devices that make up the
@@ -7777,12 +7809,12 @@ minal #2)
startx (or similar, e.g. gdm) in the virtual terminal. A 2nd x11vnc
could be used to see if the X server is now working correctly.
- Q-112: Can I export via VNC a Webcam or TV tuner framebuffer using
+ Q-113: Can I export via VNC a Webcam or TV tuner framebuffer using
x11vnc?
- Yes, this is possible to some degree with the [664]-rawfb option.
+ Yes, this is possible to some degree with the [666]-rawfb option.
There is no X11 involved: snapshots from the video capture device are
- used for the screen image data. See the [665]previous FAQ on -rawfb
+ used for the screen image data. See the [667]previous FAQ on -rawfb
for background. For best results, use x11vnc version 0.8.1 or later.
Roughly, one would do something like this:
@@ -7794,7 +7826,7 @@ minal #2)
snapshot to a file that you point -rawfb to; ask me if it is not clear
what to do.)
- The "snap:" enforces [666]-snapfb mode which appears to be necessary.
+ The "snap:" enforces [668]-snapfb mode which appears to be necessary.
The read pointer for video capture devices cannot be repositioned
(which would be needed for scanline polling), but you can read a full
frame of data from the device.
@@ -7816,7 +7848,7 @@ minal #2)
Many video4linux drivers tend to set the framebuffer to be 24bpp (as
opposed to 32bpp.) Since this can cause problems with VNC viewers,
- etc, the [667]-24to32 option will be automatically imposed when in
+ etc, the [669]-24to32 option will be automatically imposed when in
24bpp.
Note that by its very nature, video capture involves rapid change in
@@ -7824,7 +7856,7 @@ minal #2)
wavering in brightness is always happening. This can lead to much
network bandwidth consumption for the VNC traffic and also local CPU
and I/O resource usage. You may want to experiment with "dialing down"
- the framerate via the [668]-wait, [669]-slow_fb, or [670]-defer
+ the framerate via the [670]-wait, [671]-slow_fb, or [672]-defer
options. Decreasing the window size and bpp also helps.
@@ -7913,16 +7945,16 @@ minal #2)
format to HI240, RGB565, RGB24, RGB32, RGB555, and
GREY respectively. See -rawfb video for details.
- See also the [671]-freqtab option to supply your own xawtv channel to
+ See also the [673]-freqtab option to supply your own xawtv channel to
frequency mappings for your country (only ntsc-cable-us is built into
x11vnc.)
- Q-113: Can I connect via VNC to a Qt-embedded/Qtopia application
+ Q-114: Can I connect via VNC to a Qt-embedded/Qtopia application
running on my handheld or PC using the Linux console framebuffer (i.e.
not X11)?
- Yes, the basic method for this is the [672]-rawfb scheme where the
+ Yes, the basic method for this is the [674]-rawfb scheme where the
Linux console framebuffer (usually /dev/fb0) is polled and the uinput
driver is used to inject keystrokes and mouse input. Often you will
just have to type:
@@ -7935,7 +7967,7 @@ minal #2)
x11vnc -rawfb /dev/fb0@640x480x16
Also, to force usage of the uinput injection method use "-pipeinput
- UINPUT". See the [673]-pipeinput description for tunable parameters,
+ UINPUT". See the [675]-pipeinput description for tunable parameters,
etc.
One problem with the x11vnc uinput scheme is that it cannot guess the
@@ -7951,7 +7983,7 @@ minal #2)
Even with the correct acceleration setting there is still some drift
(probably because of the mouse threshold where the acceleration kicks
in) and so x11vnc needs to reposition the cursor from 0,0 about 5
- times a second. See the [674]-pipeinput UINPUT option for tuning
+ times a second. See the [676]-pipeinput UINPUT option for tuning
parameters that can be set (there are some experimental thresh=N
tuning parameters as well)
@@ -7983,10 +8015,10 @@ minal #2)
not work.
- Q-114: Now that non-X11 devices can be exported via VNC using x11vnc,
+ Q-115: Now that non-X11 devices can be exported via VNC using x11vnc,
can I build it with no dependencies on X11 header files and libraries?
- Yes, as of Jul/2006 x11vnc enables building for [675]-rawfb only
+ Yes, as of Jul/2006 x11vnc enables building for [677]-rawfb only
support. Just do something like when building:
./configure --without-x (plus any other flags)
make
@@ -7997,16 +8029,16 @@ minal #2)
know what you did.
- Q-115: Does x11vnc support Mac OS X Aqua/Quartz displays natively
+ Q-116: Does x11vnc support Mac OS X Aqua/Quartz displays natively
(i.e. no X11 involved)?
Yes, since Nov/2006 in the development tree (x11vnc-0.8.4 tarball)
there is support for native Mac OS X Aqua/Quartz displays using the
- [676]-rawfb mechanism described above. The mouse and keyboard input is
+ [678]-rawfb mechanism described above. The mouse and keyboard input is
achieved via Mac OS X API's.
- So you can use x11vnc as an alternative to [677]OSXvnc (aka Vine
- Server), or [678]Apple Remote Desktop (ARD). Perhaps there is some
+ So you can use x11vnc as an alternative to [679]OSXvnc (aka Vine
+ Server), or [680]Apple Remote Desktop (ARD). Perhaps there is some
x11vnc feature you'd like to use on Mac OS X, etc. For a number of
activities (e.g. window drags) it seems to be faster than OSXvnc.
@@ -8016,7 +8048,7 @@ minal #2)
(XDarwin) running on Mac OS X (people often install this software to
display remote X11 apps on their Mac OS X system, or use some old
favorites locally such as xterm.) However in this case x11vnc will
- only work reasonably in single window [679]-id windowid mode (and the
+ only work reasonably in single window [681]-id windowid mode (and the
window may need to have mouse focus.)
If you do not have the DISPLAY env. variable set, x11vnc will assume
@@ -8034,9 +8066,9 @@ minal #2)
./configure --without-x
make
- Win2VNC/x2vnc: One handy use is to use the [680]-nofb mode to
+ Win2VNC/x2vnc: One handy use is to use the [682]-nofb mode to
redirect mouse and keyboard input to a nearby Mac (i.e. one to the
- side of your desk) via [681]x2vnc or Win2VNC. See [682]this FAQ for
+ side of your desk) via [683]x2vnc or Win2VNC. See [684]this FAQ for
more info.
Options: Here are the Mac OS X specific x11vnc options:
@@ -8106,17 +8138,17 @@ rm -f $tmp
command for you.) Then once you are connected via VNC, iconify the
Terminal windows (you can't delete them since that will kill x11vnc.)
- Q-116: Can x11vnc be used as a VNC reflector/repeater to improve
+ Q-117: Can x11vnc be used as a VNC reflector/repeater to improve
performance for the case of a large number of simultaneous VNC viewers
(e.g. classroom broadcasting or a large demo)?
- Yes, as of Feb/2007 there is the "[683]-reflect host:N" option to
+ Yes, as of Feb/2007 there is the "[685]-reflect host:N" option to
connect to the VNC server "host:N" (either another x11vnc or any other
VNC server) and re-export it. VNC viewers then connect to the
x11vnc(s) running -reflect.
The -reflect option is the same as: "-rawfb vnc:host:N". See the
- [684]-rawfb description under "VNC HOST" for more details.
+ [686]-rawfb description under "VNC HOST" for more details.
You can replace "host:N" with "listen" or "listen:port" for reverse
connections.
@@ -8177,18 +8209,18 @@ rm -f $tmp
re-exports via VNC to its clients C.) However, CopyRect and
CursorShape encodings are preserved in the reflection and that helps.
Dragging windows with the mouse can be a problem (especially if S is
- not doing wireframing somehow, consider [685]-nodragging if the
+ not doing wireframing somehow, consider [687]-nodragging if the
problem is severe) For a really fast reflector/repeater it would have
to be implemented from scratch with performance in mind. See these
other projects:
- [686]http://sourceforge.net/projects/vnc-reflector/,
- [687]http://www.tightvnc.com/projector/ (closed source?),
+ [688]http://sourceforge.net/projects/vnc-reflector/,
+ [689]http://www.tightvnc.com/projector/ (closed source?),
Automation via Reverse Connections: Instead of having the R's
connect directly to S and then the C's connect directly to the R they
should use, some convenience can be achieved by using reverse
- connections (the x11vnc "[688]"-connect host1,host2,..." option.)
+ connections (the x11vnc "[690]"-connect host1,host2,..." option.)
Suppose all the clients "C" are started up in Listen mode:
client1> vncviewer -listen
client2> vncviewer -listen
@@ -8215,7 +8247,7 @@ rm -f $tmp
us know what you did. A really nice thing would be some sort of
auto-discovery of your repeater, etc...
- Q-117: Can x11vnc be used during a Linux, Solaris, etc. system
+ Q-118: Can x11vnc be used during a Linux, Solaris, etc. system
Installation so the Installation can be done remotely?
This can be done, but it doesn't always work because it depends on how
@@ -8247,7 +8279,7 @@ rm -f $tmp
If the Solaris install is an older X-based one, there will be a menu
for you to get a terminal window. From that window you might be able
to retrieve x11vnc.static via wget, scp, or ftp. Remember to do "chmod
- 755 ./x11vnc.static" and then find the -auth file as in [689]this FAQ.
+ 755 ./x11vnc.static" and then find the -auth file as in [691]this FAQ.
If it is a Linux install that uses an X server (e.g. SuSE and probably
Fedora), then you can often get a shell by pressing Ctrl-Alt-F2 or
@@ -8256,7 +8288,7 @@ rm -f $tmp
wget http://192.168.0.22/x11vnc.static
chmod 755 ./x11vnc.static
- Find the name of the auth file as in [690]this FAQ. (maybe run "ps
+ Find the name of the auth file as in [692]this FAQ. (maybe run "ps
wwwwaux | grep auth".) Then run it like this:
./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile
@@ -8265,7 +8297,7 @@ rm -f $tmp
the display being :1, etc.
If there is a firewall blocking incoming connections during the
- install, use the [691]"-connect hostname" option option for a reverse
+ install, use the [693]"-connect hostname" option option for a reverse
connection to the hostname running the VNC viewer in listen mode.
Debian based installs are either console-text or console-framebuffer
@@ -8308,36 +8340,36 @@ rm -f $tmp
[Misc: Clipboard, File Transfer/Sharing, Printing, Sound, Beeps,
Thanks, etc.]
- Q-118: Does the Clipboard/Selection get transferred between the
+ Q-119: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol.
Furthermore, x11vnc is able to hold the PRIMARY and CLIPBOARD
selection (Xvnc does not seem to do this.) If you don't want the
- Clipboard/Selection exchanged use the [692]-nosel option. If you don't
+ Clipboard/Selection exchanged use the [694]-nosel option. If you don't
want the PRIMARY selection to be polled for changes use the
- [693]-noprimary option. (with a similar thing for CLIPBOARD.) You can
- also fine-tune it a bit with the [694]-seldir dir option and also
- [695]-input.
+ [695]-noprimary option. (with a similar thing for CLIPBOARD.) You can
+ also fine-tune it a bit with the [696]-seldir dir option and also
+ [697]-input.
You may need to watch out for desktop utilities such as KDE's
"Klipper" that do odd things with the selection, clipboard, and
cutbuffers.
- Q-119: Can I use x11vnc to record a Shock Wave Flash (or other format)
+ Q-120: Can I use x11vnc to record a Shock Wave Flash (or other format)
video of my desktop, e.g. to record a tutorial or demo?
Yes, it is possible with a number of tools that record VNC and
transform it to swf format or others. One such popular tool is
- [696]pyvnc2swf. There are a number of [697]tutorials (broken link?) on
+ [698]pyvnc2swf. There are a number of [699]tutorials (broken link?) on
how to do this. Another option is to use the vnc2mpg that comes in the
LibVNCServer package.
An important thing to remember when doing this is that tuning
parameters should be applied to x11vnc to speed up its polling for
this sort of application, e.g. "-wait 10 -defer 10".
- Q-120: Can I transfer files back and forth with x11vnc?
+ Q-121: Can I transfer files back and forth with x11vnc?
As of Oct/2005 and May/2006 x11vnc enables, respectively, the TightVNC
and UltraVNC file transfer implementations that were added to
@@ -8345,11 +8377,11 @@ rm -f $tmp
(and Windows viewers only support filetransfer it appears... but they
do work to some degree under Wine on Linux.)
- The [698]SSVNC Unix VNC viewer supports UltraVNC file transfer by use
+ The [700]SSVNC Unix VNC viewer supports UltraVNC file transfer by use
of a Java helper program.
TightVNC file transfer is off by default, if you want to enable it use
- the [699]-tightfilexfer option.
+ the [701]-tightfilexfer option.
UltraVNC file transfer is off by default, to enable it use something
like "-rfbversion 3.6 -permitfiletransfer"
@@ -8372,7 +8404,7 @@ rm -f $tmp
IMPORTANT: please understand if -ultrafilexfer or -tightfilexfer is
specified and you run x11vnc as root for, say, inetd or display
manager (gdm, kdm, ...) access and you do not have it switch users via
- the [700]-users option, then VNC Viewers that connect are able to do
+ the [702]-users option, then VNC Viewers that connect are able to do
filetransfer reads and writes as *root*.
The UltraVNC and TightVNC settings can be toggled on and off inside
@@ -8385,13 +8417,13 @@ rm -f $tmp
control you will probably be foiled by the "-rfbversion 3.6" issue.
- Q-121: Which UltraVNC extensions are supported?
+ Q-122: Which UltraVNC extensions are supported?
Some of them are supported. To get UltraVNC Viewers to attempt to use
these extensions you will need to supply this option to x11vnc:
-rfbversion 3.6
- Or use [701]-ultrafilexfer which is an alias for the above option and
+ Or use [703]-ultrafilexfer which is an alias for the above option and
"-permitfiletransfer". UltraVNC evidently treats any other RFB version
number as non-UltraVNC.
@@ -8403,30 +8435,30 @@ rm -f $tmp
* 1/n Server Scaling
* rfbEncodingUltra compression encoding
- The [702]SSVNC Unix VNC viewer supports these UltraVNC extensions.
+ The [704]SSVNC Unix VNC viewer supports these UltraVNC extensions.
- To disable SingleWindow and ServerInput use [703]-noultraext (the
+ To disable SingleWindow and ServerInput use [705]-noultraext (the
others are managed by LibVNCServer.) See this option too:
- [704]-noserverdpms.
+ [706]-noserverdpms.
- Also, the [705]UltraVNC repeater proxy is supported for use with
- reverse connections: "[706]-connect repeater://host:port+ID:NNNN". Use
+ Also, the [707]UltraVNC repeater proxy is supported for use with
+ reverse connections: "[708]-connect repeater://host:port+ID:NNNN". Use
it for both plaintext and SSL connections. This mode can send any
string before switching to the VNC protocol, and so could be used with
other proxy/gateway tools.
- Q-122: Can x11vnc emulate UltraVNC's Single Click helpdesk mode for
+ Q-123: Can x11vnc emulate UltraVNC's Single Click helpdesk mode for
Unix? I.e. something very simple for a naive user to initiate a
reverse vnc connection from their Unix desktop to a helpdesk
operator's VNC Viewer.
- Yes, UltraVNC's [707]Single Click (SC) mode can be emulated fairly
+ Yes, UltraVNC's [709]Single Click (SC) mode can be emulated fairly
well on Unix.
We use the term "helpdesk" below, but it could be any sort of remote
assistance you want to set up, e.g. something for Unix-using friends
- or family to use. This includes [708]Mac OS X.
+ or family to use. This includes [710]Mac OS X.
Assume you create a helpdesk directory "hd" on your website:
http://www.mysite.com/hd (any website that you can upload files to
@@ -8482,7 +8514,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
So I guess this is about 3-4 clicks (start a terminal and paste) and
pressing "Enter" instead of "single click"...
- See [709]this page for some variations on this method, e.g. how to add
+ See [711]this page for some variations on this method, e.g. how to add
a password, SSL Certificates, etc.
@@ -8494,11 +8526,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
A bit of obscurity security could be put in with a -passwd, -rfbauth
options, etc. (note that x11vnc will require a password even for
- reverse connections.) More info [710]here.
+ reverse connections.) More info [712]here.
Firewalls: If the helpdesk (you) with the vncviewer is behind a
- NAT/Firewall/Router the [711]router will have to be configured to
+ NAT/Firewall/Router the [713]router will have to be configured to
redirect a port (i.e. 5500 or maybe different one if you like) to the
vncviewer machine. If the vncviewer machine also has its own
host-level firewall, you will have to open up the port there as well.
@@ -8508,7 +8540,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
configuring a router to do a port redirection (i.e. on your side, the
HelpDesk.) To avoid modifying either firewall/router, one would need
some public (IP address reachable on the internet) redirection/proxy
- service. Perhaps such a thing exists. [712]http://sc.uvnc.com provides
+ service. Perhaps such a thing exists. [714]http://sc.uvnc.com provides
this service for their UltraVNC Single Click users.
@@ -8544,7 +8576,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
As of Apr/2007 x11vnc supports reverse connections in SSL and so we
can do this. On the Helpdesk side (Viewer) you will need STUNNEL or
- better use the [713]Enhanced TightVNC Viewer (SSVNC) package we
+ better use the [715]Enhanced TightVNC Viewer (SSVNC) package we
provide that automates all of the SSL for you.
To do this create a file named "vncs" in the website "hd" directory
@@ -8574,11 +8606,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
with the hostnames or IP addresses customized to your case.
- The only change from the "vnc" above is the addition of the [714]-ssl
+ The only change from the "vnc" above is the addition of the [716]-ssl
option to x11vnc. This will create a temporary SSL cert: openssl(1)
will need to be installed on the user's end. A fixed SSL cert file
could be used to avoid this (and provide some authentication; more
- info [715]here.)
+ info [717]here.)
The naive user will be doing this:
wget -qO - http://www.mysite.com/hd/vncs | sh -
@@ -8587,7 +8619,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc
But before that, the helpdesk operator needs to have "vncviewer
-listen" running as before, however he needs an SSL tunnel at his end.
- The easiest way to do this is use [716]Enhanced TightVNC Viewer
+ The easiest way to do this is use [718]Enhanced TightVNC Viewer
(SSVNC). Start it, and select Options -> 'Reverse VNC Connection
(-listen)'. Then UN-select 'Verify All Certs' (this can be enabled
later if you want; you'll need the x11vnc SSL certificate), and click
@@ -8617,7 +8649,7 @@ connect = localhost:5501
answer the prompts with whatever you want; you can take the default
for all of them if you like. The openssl(1) package must be installed.
- See [717]this link and [718]this one too for more info on SSL certs.
+ See [719]this link and [720]this one too for more info on SSL certs.
This creates $HOME/.vnc/certs/server-self:mystunnel.pem, then you
would change the "stunnel.cfg" to look something like:
foreground = yes
@@ -8638,7 +8670,7 @@ connect = localhost:5501
then all bets are off!.
More SSL variations and info about certificates can be found
- [719]here.
+ [721]here.
OpenSSL libssl.so.0.9.7 problems:
@@ -8648,16 +8680,16 @@ connect = localhost:5501
distros are currently a bit of a mess regarding which version of
libssl is installed.
- You will find the [720]details here.
+ You will find the [722]details here.
- Q-123: Can I (temporarily) mount my local (viewer-side) Windows/Samba
+ Q-124: Can I (temporarily) mount my local (viewer-side) Windows/Samba
File share on the machine where x11vnc is running?
You will have to use an external network redirection for this.
Filesystem mounting is not part of the VNC protocol.
- We show a simple [721]Samba example here.
+ We show a simple [723]Samba example here.
First you will need a tunnel to redirect the SMB requests from the
remote machine to the one you sitting at. We use an ssh tunnel:
@@ -8697,17 +8729,17 @@ d,ip=127.0.0.1,port=1139
far-away> smbumount /home/fred/smb-haystack-pub
At some point we hope to fold some automation for SMB ssh redir setup
- into the [722]Enhanced TightVNC Viewer (SSVNC) package we provide (as
+ into the [724]Enhanced TightVNC Viewer (SSVNC) package we provide (as
of Sep 2006 it is there for testing.)
- Q-124: Can I redirect CUPS print jobs from the remote desktop where
+ Q-125: Can I redirect CUPS print jobs from the remote desktop where
x11vnc is running to a printer on my local (viewer-side) machine?
You will have to use an external network redirection for this.
Printing is not part of the VNC protocol.
- We show a simple Unix to Unix [723]CUPS example here. Non-CUPS port
+ We show a simple Unix to Unix [725]CUPS example here. Non-CUPS port
redirections (e.g. LPD) should also be possible, but may be a bit more
tricky. If you are viewing on Windows SMB and don't have a local cups
server it may be trickier still (see below.)
@@ -8789,11 +8821,11 @@ d,ip=127.0.0.1,port=1139
"localhost".
At some point we hope to fold some automation for CUPS ssh redir setup
- into the [724]Enhanced TightVNC Viewer (SSVNC) package we provide (as
+ into the [726]Enhanced TightVNC Viewer (SSVNC) package we provide (as
of Sep 2006 it is there for testing.)
- Q-125: How can I hear the sound (audio) from the remote applications
+ Q-126: How can I hear the sound (audio) from the remote applications
on the desktop I am viewing via x11vnc?
You will have to use an external network audio mechanism for this.
@@ -8890,11 +8922,11 @@ or:
the applications will fail to run because LD_PRELOAD will point to
libraries of the wrong wordsize.
* At some point we hope to fold some automation for esd or artsd ssh
- redir setup into the [725]Enhanced TightVNC Viewer (SSVNC) package
+ redir setup into the [727]Enhanced TightVNC Viewer (SSVNC) package
we provide (as of Sep/2006 it is there for testing.)
- Q-126: Why don't I hear the "Beeps" in my X session (e.g. when typing
+ Q-127: Why don't I hear the "Beeps" in my X session (e.g. when typing
tput bel in an xterm)?
As of Dec/2003 "Beep" XBell events are tracked by default. The X
@@ -8902,14 +8934,14 @@ or:
in Solaris, see Xserver(1) for how to turn it on via +kb), and so you
won't hear them if the extension is not present.
- If you don't want to hear the beeps use the [726]-nobell option. If
+ If you don't want to hear the beeps use the [728]-nobell option. If
you want to hear the audio from the remote applications, consider
- trying a [727]redirector such as esd.
+ trying a [729]redirector such as esd.
- Q-127: Does x11vnc work with IPv6?
+ Q-128: Does x11vnc work with IPv6?
- Currently the only way to do this is via [728]inetd. You configure
+ Currently the only way to do this is via [730]inetd. You configure
x11vnc to be run from inetd or xinetd and instruct it to listen on an
IPv6 address. For xinetd the setting "flags = IPv6" will be needed.
@@ -8918,7 +8950,7 @@ or:
connection.) Some sort of ipv4-to-ipv6 redirector tool (perhaps even a
perl script) could be useful to avoid this.
- Also note that not all VNC Viewers are [729]IPv6 enabled, so a
+ Also note that not all VNC Viewers are [731]IPv6 enabled, so a
redirector could even be needed on the client side.
@@ -8926,7 +8958,7 @@ or:
Contributions:
- Q-128: Thanks for your program and for your help! Can I make a
+ Q-129: Thanks for your program and for your help! Can I make a
donation?
Please do (any amount is appreciated; very few have donated) and thank
@@ -8955,716 +8987,718 @@ References
17. http://www.karlrunge.com/x11vnc/faq.html#faq-tight139
18. http://www.karlrunge.com/x11vnc/faq.html#faq-krdcprob
19. http://www.karlrunge.com/x11vnc/faq.html#faq-tru64-crash
- 20. http://www.karlrunge.com/x11vnc/faq.html#faq-build-customizations
- 21. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc
- 22. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc-8bpp
- 23. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx-nofb
- 24. http://www.karlrunge.com/x11vnc/faq.html#faq-8bpp
- 25. http://www.karlrunge.com/x11vnc/faq.html#faq-overlays
- 26. http://www.karlrunge.com/x11vnc/faq.html#faq-directcolor
- 27. http://www.karlrunge.com/x11vnc/faq.html#faq-windowid
- 28. http://www.karlrunge.com/x11vnc/faq.html#faq-transients-id
- 29. http://www.karlrunge.com/x11vnc/faq.html#faq-24bpp
- 30. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
- 31. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth
- 32. http://www.karlrunge.com/x11vnc/faq.html#faq-sunrays
- 33. http://www.karlrunge.com/x11vnc/faq.html#faq-stop-bg
- 34. http://www.karlrunge.com/x11vnc/faq.html#faq-remote_control
- 35. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
- 36. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd-noecho
- 37. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
- 38. http://www.karlrunge.com/x11vnc/faq.html#faq-multipasswd
- 39. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords
- 40. http://www.karlrunge.com/x11vnc/faq.html#faq-custom-passwords
- 41. http://www.karlrunge.com/x11vnc/faq.html#faq-forever-shared
- 42. http://www.karlrunge.com/x11vnc/faq.html#faq-allow-opt
- 43. http://www.karlrunge.com/x11vnc/faq.html#faq-tcp_wrappers
- 44. http://www.karlrunge.com/x11vnc/faq.html#faq-listen-interface
- 45. http://www.karlrunge.com/x11vnc/faq.html#faq-listen-localhost
- 46. http://www.karlrunge.com/x11vnc/faq.html#faq-input-opt
- 47. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
- 48. http://www.karlrunge.com/x11vnc/faq.html#faq-users-opt
- 49. http://www.karlrunge.com/x11vnc/faq.html#faq-blockdpy
- 50. http://www.karlrunge.com/x11vnc/faq.html#faq-gone-lock
- 51. http://www.karlrunge.com/x11vnc/faq.html#faq-ssh-unix
- 52. http://www.karlrunge.com/x11vnc/faq.html#faq-ssh-putty
- 53. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
- 54. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
- 55. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
- 56. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
- 57. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal
- 58. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-ca
- 59. http://www.karlrunge.com/x11vnc/faq.html#faq-service
- 60. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
- 61. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
- 62. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi
- 63. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
- 64. http://www.karlrunge.com/x11vnc/faq.html#faq-loop
- 65. http://www.karlrunge.com/x11vnc/faq.html#faq-java-http
- 66. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
- 67. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect-proxy
- 68. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
- 69. http://www.karlrunge.com/x11vnc/faq.html#faq-headless
- 70. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm
- 71. http://www.karlrunge.com/x11vnc/faq.html#faq-less-resource
- 72. http://www.karlrunge.com/x11vnc/faq.html#faq-more-resource
- 73. http://www.karlrunge.com/x11vnc/faq.html#faq-slow-link
- 74. http://www.karlrunge.com/x11vnc/faq.html#faq-xdamage
- 75. http://www.karlrunge.com/x11vnc/faq.html#faq-xdamage-opengl
- 76. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode
- 77. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
- 78. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect
- 79. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
- 80. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
- 81. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-shape
- 82. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha
- 83. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks
- 84. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-arrow
- 85. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-positions
- 86. http://www.karlrunge.com/x11vnc/faq.html#faq-buttonmap-opt
- 87. http://www.karlrunge.com/x11vnc/faq.html#faq-altgr
- 88. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
- 89. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless-sloppy
- 90. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
- 91. http://www.karlrunge.com/x11vnc/faq.html#faq-repeated-keys
- 92. http://www.karlrunge.com/x11vnc/faq.html#faq-repeated-keys-still
- 93. http://www.karlrunge.com/x11vnc/faq.html#faq-mod-stuck-down
- 94. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-opt
- 95. http://www.karlrunge.com/x11vnc/faq.html#faq-sun-alt-meta
- 96. http://www.karlrunge.com/x11vnc/faq.html#faq-hpux-multi-key
- 97. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-button-click
- 98. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock
- 99. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollbars
- 100. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling
- 101. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama
- 102. http://www.karlrunge.com/x11vnc/faq.html#faq-multi-screen
- 103. http://www.karlrunge.com/x11vnc/faq.html#faq-clip-screen
- 104. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr
- 105. http://www.karlrunge.com/x11vnc/faq.html#faq-rotate
- 106. http://www.karlrunge.com/x11vnc/faq.html#faq-black-screen
- 107. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 108. http://www.karlrunge.com/x11vnc/faq.html#faq-hidden-taskbars
- 109. http://www.karlrunge.com/x11vnc/faq.html#faq-kde-screensaver
- 110. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
- 111. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware
- 112. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
- 113. http://www.karlrunge.com/x11vnc/faq.html#faq-linux-vt
- 114. http://www.karlrunge.com/x11vnc/faq.html#faq-video
- 115. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
- 116. http://www.karlrunge.com/x11vnc/faq.html#faq-no-x11
- 117. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
- 118. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect
- 119. http://www.karlrunge.com/x11vnc/faq.html#faq-os-install
- 120. http://www.karlrunge.com/x11vnc/faq.html#faq-clipboard
- 121. http://www.karlrunge.com/x11vnc/faq.html#faq-record-swf
- 122. http://www.karlrunge.com/x11vnc/faq.html#faq-filexfer
- 123. http://www.karlrunge.com/x11vnc/faq.html#faq-ultravnc
- 124. http://www.karlrunge.com/x11vnc/faq.html#faq-singleclick
- 125. http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares
- 126. http://www.karlrunge.com/x11vnc/faq.html#faq-cups
- 127. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
- 128. http://www.karlrunge.com/x11vnc/faq.html#faq-beeps
- 129. http://www.karlrunge.com/x11vnc/faq.html#faq-ipv6
- 130. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks
- 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 132. http://www.tldp.org/HOWTO/Remote-X-Apps.html
- 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 134. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
- 135. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 137. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 138. http://www.karlrunge.com/x11vnc/miscbuild.html
- 139. http://www.karlrunge.com/x11vnc/faq.html#infaq_libssl-problems
- 140. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 141. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 142. http://www.karlrunge.com/x11vnc/index.html#building
- 143. http://www.karlrunge.com/x11vnc/faq.html#faq-build
- 144. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 145. http://software.opensuse.org/search?baseproject=openSUSE%3A11.1&p=1&q=x11vnc
- 146. http://gentoo-wiki.com/HOWTO_Use_VNC_to_connect_to_existing_X_Sessions
- 147. http://gentoo-portage.com/x11-misc/x11vnc
- 148. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
- 149. http://www.freshports.org/net/x11vnc
- 150. http://pkgsrc.se/x11/x11vnc
- 151. http://openports.se/x11/x11vnc
- 152. http://www.archlinux.org/packages/search/?q=x11vnc
- 153. http://mike.saunby.googlepages.com/
- 154. http://www.focv.com/ipkg/
- 155. http://packages.sw.be/x11vnc/
- 156. http://dag.wieers.com/rpm/packages/x11vnc/
- 157. http://packages.debian.org/x11vnc
- 158. http://www.sunfreeware.com/
- 159. http://www.karlrunge.com/x11vnc/bins
- 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 161. http://www.tightvnc.com/download.html
- 162. http://www.realvnc.com/products/free/4.1/download.html
- 163. http://sourceforge.net/projects/cotvnc/
- 164. http://www.ultravnc.com/
- 165. http://www.karlrunge.com/x11vnc/ssvnc.html
- 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 168. http://www.karlrunge.com/x11vnc/faq.html#faq-gui-tray
- 169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 20. http://www.karlrunge.com/x11vnc/faq.html#faq-aix-freeze
+ 21. http://www.karlrunge.com/x11vnc/faq.html#faq-build-customizations
+ 22. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc
+ 23. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc-8bpp
+ 24. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx-nofb
+ 25. http://www.karlrunge.com/x11vnc/faq.html#faq-8bpp
+ 26. http://www.karlrunge.com/x11vnc/faq.html#faq-overlays
+ 27. http://www.karlrunge.com/x11vnc/faq.html#faq-directcolor
+ 28. http://www.karlrunge.com/x11vnc/faq.html#faq-windowid
+ 29. http://www.karlrunge.com/x11vnc/faq.html#faq-transients-id
+ 30. http://www.karlrunge.com/x11vnc/faq.html#faq-24bpp
+ 31. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
+ 32. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth
+ 33. http://www.karlrunge.com/x11vnc/faq.html#faq-sunrays
+ 34. http://www.karlrunge.com/x11vnc/faq.html#faq-stop-bg
+ 35. http://www.karlrunge.com/x11vnc/faq.html#faq-remote_control
+ 36. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
+ 37. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd-noecho
+ 38. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
+ 39. http://www.karlrunge.com/x11vnc/faq.html#faq-multipasswd
+ 40. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords
+ 41. http://www.karlrunge.com/x11vnc/faq.html#faq-custom-passwords
+ 42. http://www.karlrunge.com/x11vnc/faq.html#faq-forever-shared
+ 43. http://www.karlrunge.com/x11vnc/faq.html#faq-allow-opt
+ 44. http://www.karlrunge.com/x11vnc/faq.html#faq-tcp_wrappers
+ 45. http://www.karlrunge.com/x11vnc/faq.html#faq-listen-interface
+ 46. http://www.karlrunge.com/x11vnc/faq.html#faq-listen-localhost
+ 47. http://www.karlrunge.com/x11vnc/faq.html#faq-input-opt
+ 48. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
+ 49. http://www.karlrunge.com/x11vnc/faq.html#faq-users-opt
+ 50. http://www.karlrunge.com/x11vnc/faq.html#faq-blockdpy
+ 51. http://www.karlrunge.com/x11vnc/faq.html#faq-gone-lock
+ 52. http://www.karlrunge.com/x11vnc/faq.html#faq-ssh-unix
+ 53. http://www.karlrunge.com/x11vnc/faq.html#faq-ssh-putty
+ 54. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
+ 55. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
+ 56. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 57. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
+ 58. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal
+ 59. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-ca
+ 60. http://www.karlrunge.com/x11vnc/faq.html#faq-service
+ 61. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
+ 62. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
+ 63. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi
+ 64. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
+ 65. http://www.karlrunge.com/x11vnc/faq.html#faq-loop
+ 66. http://www.karlrunge.com/x11vnc/faq.html#faq-java-http
+ 67. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
+ 68. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect-proxy
+ 69. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
+ 70. http://www.karlrunge.com/x11vnc/faq.html#faq-headless
+ 71. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm
+ 72. http://www.karlrunge.com/x11vnc/faq.html#faq-less-resource
+ 73. http://www.karlrunge.com/x11vnc/faq.html#faq-more-resource
+ 74. http://www.karlrunge.com/x11vnc/faq.html#faq-slow-link
+ 75. http://www.karlrunge.com/x11vnc/faq.html#faq-xdamage
+ 76. http://www.karlrunge.com/x11vnc/faq.html#faq-xdamage-opengl
+ 77. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode
+ 78. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
+ 79. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect
+ 80. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
+ 81. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
+ 82. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-shape
+ 83. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha
+ 84. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks
+ 85. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-arrow
+ 86. http://www.karlrunge.com/x11vnc/faq.html#faq-cursor-positions
+ 87. http://www.karlrunge.com/x11vnc/faq.html#faq-buttonmap-opt
+ 88. http://www.karlrunge.com/x11vnc/faq.html#faq-altgr
+ 89. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
+ 90. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless-sloppy
+ 91. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
+ 92. http://www.karlrunge.com/x11vnc/faq.html#faq-repeated-keys
+ 93. http://www.karlrunge.com/x11vnc/faq.html#faq-repeated-keys-still
+ 94. http://www.karlrunge.com/x11vnc/faq.html#faq-mod-stuck-down
+ 95. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-opt
+ 96. http://www.karlrunge.com/x11vnc/faq.html#faq-sun-alt-meta
+ 97. http://www.karlrunge.com/x11vnc/faq.html#faq-hpux-multi-key
+ 98. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-button-click
+ 99. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock
+ 100. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollbars
+ 101. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling
+ 102. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama
+ 103. http://www.karlrunge.com/x11vnc/faq.html#faq-multi-screen
+ 104. http://www.karlrunge.com/x11vnc/faq.html#faq-clip-screen
+ 105. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr
+ 106. http://www.karlrunge.com/x11vnc/faq.html#faq-rotate
+ 107. http://www.karlrunge.com/x11vnc/faq.html#faq-black-screen
+ 108. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
+ 109. http://www.karlrunge.com/x11vnc/faq.html#faq-hidden-taskbars
+ 110. http://www.karlrunge.com/x11vnc/faq.html#faq-kde-screensaver
+ 111. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
+ 112. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware
+ 113. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
+ 114. http://www.karlrunge.com/x11vnc/faq.html#faq-linux-vt
+ 115. http://www.karlrunge.com/x11vnc/faq.html#faq-video
+ 116. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
+ 117. http://www.karlrunge.com/x11vnc/faq.html#faq-no-x11
+ 118. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
+ 119. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect
+ 120. http://www.karlrunge.com/x11vnc/faq.html#faq-os-install
+ 121. http://www.karlrunge.com/x11vnc/faq.html#faq-clipboard
+ 122. http://www.karlrunge.com/x11vnc/faq.html#faq-record-swf
+ 123. http://www.karlrunge.com/x11vnc/faq.html#faq-filexfer
+ 124. http://www.karlrunge.com/x11vnc/faq.html#faq-ultravnc
+ 125. http://www.karlrunge.com/x11vnc/faq.html#faq-singleclick
+ 126. http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares
+ 127. http://www.karlrunge.com/x11vnc/faq.html#faq-cups
+ 128. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
+ 129. http://www.karlrunge.com/x11vnc/faq.html#faq-beeps
+ 130. http://www.karlrunge.com/x11vnc/faq.html#faq-ipv6
+ 131. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks
+ 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 133. http://www.tldp.org/HOWTO/Remote-X-Apps.html
+ 134. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 135. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
+ 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 138. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 139. http://www.karlrunge.com/x11vnc/miscbuild.html
+ 140. http://www.karlrunge.com/x11vnc/faq.html#infaq_libssl-problems
+ 141. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 142. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 143. http://www.karlrunge.com/x11vnc/index.html#building
+ 144. http://www.karlrunge.com/x11vnc/faq.html#faq-build
+ 145. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 146. http://software.opensuse.org/search?baseproject=openSUSE%3A11.1&p=1&q=x11vnc
+ 147. http://gentoo-wiki.com/HOWTO_Use_VNC_to_connect_to_existing_X_Sessions
+ 148. http://gentoo-portage.com/x11-misc/x11vnc
+ 149. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
+ 150. http://www.freshports.org/net/x11vnc
+ 151. http://pkgsrc.se/x11/x11vnc
+ 152. http://openports.se/x11/x11vnc
+ 153. http://www.archlinux.org/packages/search/?q=x11vnc
+ 154. http://mike.saunby.googlepages.com/
+ 155. http://www.focv.com/ipkg/
+ 156. http://packages.debian.org/x11vnc
+ 157. http://packages.sw.be/x11vnc/
+ 158. http://dag.wieers.com/rpm/packages/x11vnc/
+ 159. http://www.sunfreeware.com/
+ 160. http://www.karlrunge.com/x11vnc/bins
+ 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 162. http://www.tightvnc.com/download.html
+ 163. http://www.realvnc.com/products/free/4.1/download.html
+ 164. http://sourceforge.net/projects/cotvnc/
+ 165. http://www.ultravnc.com/
+ 166. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 169. http://www.karlrunge.com/x11vnc/faq.html#faq-gui-tray
170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport
- 173. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 174. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
- 175. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel
- 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 177. http://www.karlrunge.com/x11vnc/vncxfer
- 178. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 179. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect-proxy
- 180. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 181. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel
- 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh
- 183. http://www.karlrunge.com/x11vnc/ssvnc.html
- 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q,
- 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 187. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389750
- 188. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399408
- 189. http://bugs.kde.org/show_bug.cgi?id=136924
- 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxrecord
- 191. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 193. http://fredrik.hubbe.net/x2vnc.html
- 194. http://www.hubbe.net/~hubbe/win2vnc.html
- 195. http://www.deboer.gmxhome.de/
- 196. http://sourceforge.net/projects/win2vnc/
- 197. http://fredrik.hubbe.net/x2vnc.html
- 198. http://freshmeat.net/projects/x2x/
- 199. http://zapek.com/?page_id=26
- 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 201. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
- 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 205. http://www.karlrunge.com/x11vnc/faq.html#faq-8bpp
- 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport
+ 174. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 175. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect
+ 176. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel
+ 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 178. http://www.karlrunge.com/x11vnc/vncxfer
+ 179. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 180. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect-proxy
+ 181. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 182. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel
+ 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh
+ 184. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q,
+ 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 188. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389750
+ 189. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399408
+ 190. http://bugs.kde.org/show_bug.cgi?id=136924
+ 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxrecord
+ 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxrecord
+ 193. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 195. http://fredrik.hubbe.net/x2vnc.html
+ 196. http://www.hubbe.net/~hubbe/win2vnc.html
+ 197. http://www.deboer.gmxhome.de/
+ 198. http://sourceforge.net/projects/win2vnc/
+ 199. http://fredrik.hubbe.net/x2vnc.html
+ 200. http://freshmeat.net/projects/x2x/
+ 201. http://zapek.com/?page_id=26
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 203. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
+ 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 207. http://www.karlrunge.com/x11vnc/faq.html#faq-8bpp
208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 216. http://www.karlrunge.com/x11vnc/faq.html#faq-overlays
- 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 220. http://www.karlrunge.com/x11vnc/ssvnc.html
- 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 225. http://www.karlrunge.com/x11vnc/faq.html#infaq_xauth_pain
- 226. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
- 227. http://www.sun.com/sunray/index.html
- 228. http://www.karlrunge.com/x11vnc/sunray.html
- 229. http://wiki.sun-rays.org/index.php/Remote_Control_Toolkit
- 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
- 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 239. http://www.karlrunge.com/x11vnc/faq.html#faq-config-file
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 243. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
- 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 218. http://www.karlrunge.com/x11vnc/faq.html#faq-overlays
+ 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 222. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 227. http://www.karlrunge.com/x11vnc/faq.html#infaq_xauth_pain
+ 228. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
+ 229. http://www.sun.com/sunray/index.html
+ 230. http://www.karlrunge.com/x11vnc/sunray.html
+ 231. http://wiki.sun-rays.org/index.php/Remote_Control_Toolkit
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
+ 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 241. http://www.karlrunge.com/x11vnc/faq.html#faq-config-file
+ 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 245. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
+ 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 257. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 258. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
- 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 260. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
- 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 259. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 260. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 262. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 269. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
- 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 272. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 274. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
- 275. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
- 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 278. http://www.karlrunge.com/x11vnc/faq.html#faq-tcp_wrappers
- 279. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
- 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 271. http://www.karlrunge.com/x11vnc/faq.html#faq-accept-opt
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 274. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 276. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd
+ 277. http://www.karlrunge.com/x11vnc/faq.html#faq-passwdfile
+ 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 280. http://www.karlrunge.com/x11vnc/faq.html#faq-tcp_wrappers
+ 281. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
+ 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 288. ftp://ftp.x.org/
- 289. http://www.karlrunge.com/x11vnc/dtVncPopup
- 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 293. http://www.karlrunge.com/x11vnc/blockdpy.c
- 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
- 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 303. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 304. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 290. ftp://ftp.x.org/
+ 291. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 295. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
+ 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
+ 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
305. http://www.karlrunge.com/x11vnc/index.html#tunnelling
306. http://www.karlrunge.com/x11vnc/ssvnc.html
- 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 310. http://www.karlrunge.com/x11vnc/chainingssh.html#gateway_double_ssh
- 311. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 313. http://www.stunnel.org/
- 314. http://stunnel.mirt.net/
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
- 318. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
- 319. http://www.stunnel.org/
- 320. http://www.karlrunge.com/x11vnc/ssl.html
- 321. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
- 322. http://www.karlrunge.com/x11vnc/ssvnc.html
- 323. http://www.karlrunge.com/x11vnc/ssl.html
- 324. http://www.securityfocus.com/infocus/1677
+ 307. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 308. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 312. http://www.karlrunge.com/x11vnc/chainingssh.html#gateway_double_ssh
+ 313. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 315. http://www.stunnel.org/
+ 316. http://stunnel.mirt.net/
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
+ 320. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
+ 321. http://www.stunnel.org/
+ 322. http://www.karlrunge.com/x11vnc/ssl.html
+ 323. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 324. http://www.karlrunge.com/x11vnc/ssvnc.html
325. http://www.karlrunge.com/x11vnc/ssl.html
- 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 327. http://sc.uvnc.com/javaviewer/index.html
- 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 329. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
- 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 336. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
- 337. http://www.karlrunge.com/x11vnc/ssvnc.html
- 338. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
- 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 340. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 326. http://www.securityfocus.com/infocus/1677
+ 327. http://www.karlrunge.com/x11vnc/ssl.html
+ 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 329. http://sc.uvnc.com/javaviewer/index.html
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 331. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 338. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 339. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 340. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 342. http://www.openssl.org/
- 343. http://sourceforge.net/projects/vencrypt/
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
- 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
- 346. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
- 347. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-vnc-viewers
- 348. http://www.karlrunge.com/x11vnc/ssl.html
- 349. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 342. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 344. http://www.openssl.org/
+ 345. http://sourceforge.net/projects/vencrypt/
+ 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls
+ 348. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 349. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-vnc-viewers
350. http://www.karlrunge.com/x11vnc/ssl.html
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 353. http://www.stunnel.org/
- 354. http://www.karlrunge.com/x11vnc/faq.html#infaq_viewer-side-stunnel
- 355. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
- 356. http://www.karlrunge.com/x11vnc/ssvnc.html
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 359. http://sc.uvnc.com/javaviewer/index.html
- 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 361. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-router-redir
- 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 363. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal
- 364. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
+ 351. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 352. http://www.karlrunge.com/x11vnc/ssl.html
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 355. http://www.stunnel.org/
+ 356. http://www.karlrunge.com/x11vnc/faq.html#infaq_viewer-side-stunnel
+ 357. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 358. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 360. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 361. http://sc.uvnc.com/javaviewer/index.html
+ 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 363. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-router-redir
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
365. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal
- 366. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
- 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpport
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 371. http://www.karlrunge.com/x11vnc/ssl-output.html
- 372. http://www.karlrunge.com/x11vnc/java_console_direct.html
- 373. http://www.karlrunge.com/x11vnc/ssvnc.html
- 374. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
- 375. http://www.karlrunge.com/x11vnc/ss_vncviewer
- 376. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 377. http://www.karlrunge.com/x11vnc/ssl.html
- 378. http://www.karlrunge.com/x11vnc/ssvnc.html
- 379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
- 380. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
- 381. http://www.karlrunge.com/x11vnc/java_console_proxy.html
- 382. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
- 383. http://www.karlrunge.com/x11vnc/ssvnc.html
- 384. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 385. http://www.karlrunge.com/x11vnc/ssl.html
- 386. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously
- 387. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
- 388. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
- 389. http://www.karlrunge.com/x11vnc/faq.html#infaq_x11vnc_loop
- 390. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset
- 391. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen
- 394. http://www.karlrunge.com/x11vnc/faq.html#infaq_dtlogin_solaris
- 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 396. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 366. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
+ 367. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal
+ 368. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
+ 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpport
+ 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 373. http://www.karlrunge.com/x11vnc/ssl-output.html
+ 374. http://www.karlrunge.com/x11vnc/java_console_direct.html
+ 375. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 376. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext
+ 377. http://www.karlrunge.com/x11vnc/ss_vncviewer
+ 378. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 379. http://www.karlrunge.com/x11vnc/ssl.html
+ 380. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir
+ 382. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers
+ 383. http://www.karlrunge.com/x11vnc/java_console_proxy.html
+ 384. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 385. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 386. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 387. http://www.karlrunge.com/x11vnc/ssl.html
+ 388. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously
+ 389. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
+ 390. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
+ 391. http://www.karlrunge.com/x11vnc/faq.html#infaq_x11vnc_loop
+ 392. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset
+ 393. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen
+ 396. http://www.karlrunge.com/x11vnc/faq.html#infaq_dtlogin_solaris
397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 400. http://www.jirka.org/gdm-documentation/x241.html
- 401. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 403. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth
- 404. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q,
- 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 408. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
- 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
- 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns
- 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
- 412. http://www.avahi.org/
- 413. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
- 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 416. http://www.karlrunge.com/x11vnc/faq.html#infaq_stunnel-inetd
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 423. http://www.karlrunge.com/x11vnc/find_display.html
- 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 427. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords
- 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 430. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
- 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 434. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
- 435. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
- 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 439. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 446. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
- 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit
- 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
- 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
+ 398. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 402. http://www.jirka.org/gdm-documentation/x241.html
+ 403. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 405. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth
+ 406. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q,
+ 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 410. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin
+ 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
+ 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns
+ 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf
+ 414. http://www.avahi.org/
+ 415. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
+ 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 418. http://www.karlrunge.com/x11vnc/faq.html#infaq_stunnel-inetd
+ 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 425. http://www.karlrunge.com/x11vnc/find_display.html
+ 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 429. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords
+ 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 432. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int
+ 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 436. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
+ 437. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer
+ 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 441. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
+ 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 448. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy
+ 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit
+ 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
- 454. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess
- 455. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess
- 456. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 463. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 464. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 465. http://www.karlrunge.com/x11vnc/Xdummy
- 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 467. http://www.karlrunge.com/x11vnc/xdm_one_shot.html
- 468. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously
- 469. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
- 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 475. http://www.karlrunge.com/x11vnc/shm_clear
- 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 478. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
- 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
- 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 487. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 488. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
- 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 492. http://www.tightvnc.com/
- 493. http://www.karlrunge.com/x11vnc/ssvnc.html
- 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
- 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 509. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 514. http://minimyth.org/
- 515. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
- 516. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
+ 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy
+ 456. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess
+ 457. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess
+ 458. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 465. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 466. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
+ 467. http://www.karlrunge.com/x11vnc/Xdummy
+ 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 469. http://www.karlrunge.com/x11vnc/xdm_one_shot.html
+ 470. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously
+ 471. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay
+ 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 477. http://www.karlrunge.com/x11vnc/shm_clear
+ 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 480. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm
+ 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
+ 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 489. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 490. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc
+ 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 494. http://www.tightvnc.com/
+ 495. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
+ 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 511. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 516. http://minimyth.org/
+ 517. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl
+ 518. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 522. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
- 523. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect
- 524. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode
- 525. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 524. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
+ 525. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect
+ 526. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode
+ 527. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 529. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 533. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
- 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 538. http://www.karlrunge.com/x11vnc/index.html#beta-test
- 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
- 540. http://www.karlrunge.com/x11vnc/ssvnc.html
- 541. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop
- 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap
- 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
- 544. http://www.virtualgl.org/About/TurboVNC
- 545. http://www.virtualgl.org/
- 546. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100
- 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 549. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100
- 550. http://www.karlrunge.com/x11vnc/ssvnc.html
- 551. http://www.karlrunge.com/x11vnc/bins
+ 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 531. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 535. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe
+ 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 540. http://www.karlrunge.com/x11vnc/index.html#beta-test
+ 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
+ 542. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 543. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop
+ 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap
+ 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
+ 546. http://www.virtualgl.org/About/TurboVNC
+ 547. http://www.virtualgl.org/
+ 548. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100
+ 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 551. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100
552. http://www.karlrunge.com/x11vnc/ssvnc.html
- 553. http://www.virtualgl.org/About/Reports
- 554. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 558. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode
- 559. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 560. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks
- 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 566. http://www.karlrunge.com/x11vnc/ssvnc.html
- 567. http://www.tightvnc.com/
- 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 553. http://www.karlrunge.com/x11vnc/bins
+ 554. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 555. http://www.virtualgl.org/About/Reports
+ 556. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 560. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode
+ 561. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 562. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks
+ 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 568. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 569. http://www.tightvnc.com/
+ 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 576. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
- 577. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
- 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 585. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
- 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 587. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
- 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 578. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
+ 579. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
+ 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 587. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak
+ 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 589. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless
+ 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 601. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
- 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 604. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock
- 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
- 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
- 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
- 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 603. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
+ 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 606. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock
+ 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
+ 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
+ 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
- 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
- 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
- 618. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling
- 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 620. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html
- 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 630. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm
- 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 634. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama
- 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 639. http://www.karlrunge.com/x11vnc/ssvnc.html
- 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
- 641. http://www.jwz.org/xscreensaver/man1.html
- 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
- 643. http://www.beryl-project.org/
- 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 645. http://www.dslinux.org/blogs/pepsiman/?p=73
- 646. http://minimyth.org/
- 647. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 648. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
+ 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
+ 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all
+ 620. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling
+ 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 622. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html
+ 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 632. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm
+ 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 636. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama
+ 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 641. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
+ 643. http://www.jwz.org/xscreensaver/man1.html
+ 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
+ 645. http://www.beryl-project.org/
+ 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 647. http://www.dslinux.org/blogs/pepsiman/?p=73
+ 648. http://minimyth.org/
649. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 655. http://www.karlrunge.com/x11vnc/faq.html#faq-video
- 656. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
- 657. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
- 658. http://www.karlrunge.com/x11vnc/faq.html#faq-video
- 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 650. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
+ 651. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
+ 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 655. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 657. http://www.karlrunge.com/x11vnc/faq.html#faq-video
+ 658. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb
+ 659. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
660. http://www.karlrunge.com/x11vnc/faq.html#faq-video
- 661. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
- 662. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
- 663. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware
- 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 665. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
- 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
- 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
- 672. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
- 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 677. http://www.testplant.com/products/vine_server/OS_X
- 678. http://www.apple.com/remotedesktop/
- 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 681. http://fredrik.hubbe.net/x2vnc.html
- 682. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc
- 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
- 684. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 686. http://sourceforge.net/projects/vnc-reflector/
- 687. http://www.tightvnc.com/projector/
- 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 689. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
- 690. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
- 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 696. http://www.unixuser.org/~euske/vnc2swf/
- 697. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
- 698. http://www.karlrunge.com/x11vnc/ssvnc.html
- 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer
- 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
- 702. http://www.karlrunge.com/x11vnc/ssvnc.html
- 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext
- 704. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
- 705. http://www.uvnc.com/addons/repeater.html
- 706. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 707. http://www.uvnc.com/addons/singleclick.html
- 708. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
- 709. http://www.karlrunge.com/x11vnc/single-click.html
- 710. http://www.karlrunge.com/x11vnc/single-click.html
- 711. http://www.karlrunge.com/x11vnc/index.html#firewalls
- 712. http://sc.uvnc.com/
- 713. http://www.karlrunge.com/x11vnc/ssvnc.html
- 714. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 715. http://www.karlrunge.com/x11vnc/single-click.html
- 716. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 662. http://www.karlrunge.com/x11vnc/faq.html#faq-video
+ 663. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc
+ 664. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded
+ 665. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware
+ 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 667. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
+ 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
+ 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
+ 674. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb
+ 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 679. http://www.testplant.com/products/vine_server/OS_X
+ 680. http://www.apple.com/remotedesktop/
+ 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 683. http://fredrik.hubbe.net/x2vnc.html
+ 684. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc
+ 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
+ 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 688. http://sourceforge.net/projects/vnc-reflector/
+ 689. http://www.tightvnc.com/projector/
+ 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 691. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
+ 692. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager
+ 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 698. http://www.unixuser.org/~euske/vnc2swf/
+ 699. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
+ 700. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer
+ 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
+ 704. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext
+ 706. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
+ 707. http://www.uvnc.com/addons/repeater.html
+ 708. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 709. http://www.uvnc.com/addons/singleclick.html
+ 710. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx
+ 711. http://www.karlrunge.com/x11vnc/single-click.html
+ 712. http://www.karlrunge.com/x11vnc/single-click.html
+ 713. http://www.karlrunge.com/x11vnc/index.html#firewalls
+ 714. http://sc.uvnc.com/
+ 715. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
717. http://www.karlrunge.com/x11vnc/single-click.html
- 718. http://www.karlrunge.com/x11vnc/ssl.html
+ 718. http://www.karlrunge.com/x11vnc/ssvnc.html
719. http://www.karlrunge.com/x11vnc/single-click.html
- 720. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems
- 721. http://www.samba.org/
- 722. http://www.karlrunge.com/x11vnc/ssvnc.html
- 723. http://www.cups.org/
+ 720. http://www.karlrunge.com/x11vnc/ssl.html
+ 721. http://www.karlrunge.com/x11vnc/single-click.html
+ 722. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems
+ 723. http://www.samba.org/
724. http://www.karlrunge.com/x11vnc/ssvnc.html
- 725. http://www.karlrunge.com/x11vnc/ssvnc.html
- 726. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 727. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
- 728. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
- 729. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html
+ 725. http://www.cups.org/
+ 726. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 727. http://www.karlrunge.com/x11vnc/ssvnc.html
+ 728. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 729. http://www.karlrunge.com/x11vnc/faq.html#faq-sound
+ 730. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd
+ 731. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html
=======================================================================
http://www.karlrunge.com/x11vnc/chainingssh.html:
@@ -11670,6 +11704,10 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer)
* Local Port Protections for STUNNEL and SSH: avoid having for long
periods of time a listening port on the the local (VNC viewer)
side that redirects to the remote side.
+ * Reverse (viewer listening) VNC connections can show a Popup dialog
+ asking whether to accept the connection or not (-acceptpopup.) The
+ extra info provided by UltraVNC Single Click reverse connections
+ is also supported (-acceptpopupsc)
* Extremely low color modes: 64 and 8 colors in 8bpp
(-use64/-bgr222, -use8/-bgr111)
* Medium color mode: 16bpp mode on a 32bpp Viewer display
@@ -12080,6 +12118,16 @@ Enhanced TightVNC viewer (SSVNC) options:
the network to put (many) desktops on your screen over
a long window of time. Use -multilisten for no limit.
+ -acceptpopup In -listen (reverse connection listening) mode when
+ a reverse VNC connection comes in show a popup asking
+ whether to Accept or Reject the connection. The IP
+ address of the connecting host is shown. Same as
+ setting the env. var. SSVNC_ACCEPT_POPUP=1.
+
+ -acceptpopupsc As in -acceptpopup except assume UltraVNC Single
+ Click (SC) server. Retrieve User and ComputerName
+ info from UltraVNC Server and display in the Popup.
+
-use64 In -bgr233 mode, use 64 colors instead of 256.
-bgr222 Same as -use64.
@@ -12638,7 +12686,7 @@ x11vnc: a VNC server for real X displays
Here are all of x11vnc command line options:
% x11vnc -opts (see below for -help long descriptions)
-x11vnc: allow VNC connections to real X11 displays. 0.9.9 lastmod: 2009-07-11
+x11vnc: allow VNC connections to real X11 displays. 0.9.9 lastmod: 2009-08-10
x11vnc options:
-display disp -auth file -N
@@ -12763,7 +12811,7 @@ libvncserver-tight-extension options:
% x11vnc -help
-x11vnc: allow VNC connections to real X11 displays. 0.9.9 lastmod: 2009-07-11
+x11vnc: allow VNC connections to real X11 displays. 0.9.9 lastmod: 2009-08-10
(type "x11vnc -opts" to just list the options.)
@@ -13048,8 +13096,8 @@ Options:
is needed for the latter, feel free to ask).
-scale fraction Scale the framebuffer by factor "fraction". Values
- less than 1 shrink the fb, larger ones expand it. Note:
- image may not be sharp and response may be slower.
+ less than 1 shrink the fb, larger ones expand it. Note:
+ the image may not be sharp and response may be slower.
If "fraction" contains a decimal point "." it
is taken as a floating point number, alternatively
the notation "m/n" may be used to denote fractions
@@ -13220,8 +13268,7 @@ Options:
Repeater mode: Some services provide an intermediate
"vnc repeater": http://www.uvnc.com/addons/repeater.html
(and also http://koti.mbnet.fi/jtko/ for linux port)
- that acts as a proxy / gateway. Modes like these requir
-e
+ that acts as a proxy/gateway. Modes like these require
an initial string to be sent for the reverse connection
before the VNC protocol is started. Here are the ways
to do this:
@@ -13486,12 +13533,12 @@ e
full-access passwords)
-unixpw [list] Use Unix username and password authentication. x11vnc
- uses the su(1) program to verify the user's password.
- [list] is an optional comma separated list of allowed
- Unix usernames. If the [list] string begins with the
- character "!" then the entire list is taken as an
- exclude list. See below for per-user options that can
- be applied.
+ will use the su(1) program to verify the user's
+ password. [list] is an optional comma separated list
+ of allowed Unix usernames. If the [list] string begins
+ with the character "!" then the entire list is taken
+ as an exclude list. See below for per-user options
+ that can be applied.
A familiar "login:" and "Password:" dialog is
presented to the user on a black screen inside the
@@ -13507,8 +13554,9 @@ e
Since the detailed behavior of su(1) can vary from
OS to OS and for local configurations, test the mode
- carefully. x11vnc will attempt to be conservative and
- reject a login if anything abnormal occurs.
+ before deployment to make sure it is working properly.
+ x11vnc will attempt to be conservative and reject a
+ login if anything abnormal occurs.
One case to note: FreeBSD and the other BSD's by
default it is impossible for the user running x11vnc to
@@ -13541,7 +13589,7 @@ e
to come from the same machine x11vnc is running on
(e.g. from a ssh -L port redirection). And that the
-stunnel SSL mode be used for encryption over the
- network.(see the description of -stunnel below).
+ network. (see the description of -stunnel below).
Note: as a convenience, if you ssh(1) in and start
x11vnc it will check if the environment variable
@@ -13569,7 +13617,7 @@ e
Set UNIXPW_DISABLE_LOCALHOST=1 to disable the -localhost
requirement in Method 2). One should never do this
(i.e. allow the Unix passwords to be sniffed on the
- network).
+ network.)
Regarding reverse connections (e.g. -R connect:host
and -connect host), when the -localhost constraint is
@@ -13587,7 +13635,7 @@ e
in -inetd mode (thereby bypassing inetd). See the FAQ
for details.
- The user names in the comma separated [list] can have
+ The user names in the comma separated [list] may have
per-user options after a ":", e.g. "fred:opts"
where "opts" is a "+" separated list of
"viewonly", "fullaccess", "input=XXXX", or
@@ -13595,13 +13643,13 @@ e
For "input=" it is the K,M,B,C described under -input.
If an item in the list is "*" that means those
- options apply to all users. It also means all users
+ options apply to all users. It ALSO implies all users
are allowed to log in after supplying a valid password.
Use "deny" to explicitly deny some users if you use
- "*" to set a global option. If [list] begins with
- the "!" character then "*" is ignored for checking
- if the user is allowed, but the any value of options
- associated with it does apply as normal.
+ "*" to set a global option. If [list] begins with the
+ "!" character then "*" is ignored for checking if
+ the user is allowed, but the option values associated
+ with it do apply as normal.
There are also some utilities for testing password
if [list] starts with the "%" character. See the
@@ -13626,32 +13674,89 @@ e
NIS is not required for this mode to work (only that
getpwnam(3) return the encrypted password is required),
- but it is unlikely it will work for any most modern
- environments unless x11vnc is run as root to be able
- to access /etc/shadow (note running as root is often
- done when running x11vnc from inetd and xdm/gdm/kdm).
+ but it is unlikely it will work (as an ordinary user)
+ for most modern environments unless NIS is available.
+ On the other hand, when x11vnc is run as root it will
+ be able to to access /etc/shadow even if NIS is not
+ available (note running as root is often done when
+ running x11vnc from inetd and xdm/gdm/kdm).
Looked at another way, if you do not want to use the
- su(1) method provided by -unixpw, you can run x11vnc
- as root and use -unixpw_nis. Any users with passwords
- in /etc/shadow can then be authenticated. You may want
- to use -users unixpw= to switch the process user after
- the user logs in.
+ su(1) method provided by -unixpw (i.e. su_verify()), you
+ can run x11vnc as root and use -unixpw_nis. Any users
+ with passwords in /etc/shadow can then be authenticated.
+
+ In -unixpw_nis mode, under no circumstances is x11vnc's
+ user password verifying function based on su called
+ (i.e. the function su_verify() that runs /bin/su
+ in a pseudoterminal to verify passwords.) However,
+ if -unixpw_nis is used in conjunction with the -find
+ and -create -display WAIT:... modes then, if x11vnc is
+ running as root, /bin/su may be called externally to
+ run the find or create commands.
-unixpw_cmd cmd As -unixpw above, however do not use su(1) but rather
run the externally supplied command "cmd". The first
- line of its stdin will the username and the second line
- the received password. If the command exits with status
- 0 (success) the VNC client will be accepted. It will be
- rejected for any other return status.
-
- Dynamic passwords and non-unix passwords can be
- implemented this way by providing your own custom helper
- program. Note that under unixpw mode the remote viewer
- is given 3 tries to enter the correct password.
-
- If a list of allowed users is needed use -unixpw [list]
- in addition to this option.
+ line of its stdin will be the username and the second
+ line the received password. If the command exits
+ with status 0 (success) the VNC user will be accepted.
+ It will be rejected for any other return status.
+
+ Dynamic passwords and non-unix passwords, e.g. LDAP,
+ can be implemented this way by providing your own custom
+ helper program. Note that the remote viewer is given 3
+ tries to enter the correct password, and so the program
+ may be called in a row that many (or more) times.
+
+ If a list of allowed users is needed to limit who can
+ log in, use -unixpw [list] in addition to this option.
+
+ In FINDDISPLAY and FINDCREATEDISPLAY modes the "cmd"
+ will also be run with the RFB_UNIXPW_CMD_RUN env. var.
+ non-empty and set to the corresponding display
+ find/create command. The first two lines of input are
+ the username and passwd as in the normal case described
+ above. To support FINDDISPLAY and FINDCREATEDISPLAY,
+ "cmd" should run the requested command as the user
+ (and most likely refusing to run it if the password is
+ not correct.) Here is an example script (note it has
+ a hardwired bogus password "abc"!)
+
+ #!/bin/sh
+ # Example x11vnc -unixpw_cmd script.
+ # Read the first two lines of stdin (user and passwd)
+ read user
+ read pass
+
+ debug=0
+ if [ $debug = 1 ]; then
+ echo "user: $user" 1>&2
+ echo "pass: $pass" 1>&2
+ env | egrep -i 'rfb|vnc' 1>&2
+ fi
+
+ # Check if the password is valid.
+ # (A real example would use ldap lookup, etc!)
+ if [ "X$pass" != "Xabc" ]; then
+ exit 1 # incorrect password
+ fi
+
+ if [ "X$RFB_UNIXPW_CMD_RUN" = "X" ]; then
+ exit 0 # correct password
+ else
+ # Run the requested command (finddisplay)
+ if [ $debug = 1 ]; then
+ echo "run: $RFB_UNIXPW_CMD_RUN" 1>&2
+ fi
+ exec /bin/su - "$user" -c "$RFB_UNIXPW_CMD_RUN"
+ fi
+
+ In -unixpw_cmd mode, under no circumstances is x11vnc's
+ user password verifying function based on su called
+ (i.e. the function su_verify() that runs /bin/su in a
+ pseudoterminal to verify passwords.) It is up to the
+ supplied unixpw_cmd to do user switching if desired
+ and if it has the permissions to do so.
-find Find the user's display using FINDDISPLAY. This is an
alias for "-display WAIT:cmd=FINDDISPLAY".
@@ -13768,9 +13873,15 @@ e
xauth extract - $DISPLAY"
- In the case of -unixpw (but not -unixpw_nis), then the
- cmd= command is run as the user who just authenticated
- via the login and password prompt.
+ In the case of -unixpw (and -unixpw_nis only if x11vnc
+ is running as root), then the cmd= command is run
+ as the user who just authenticated via the login and
+ password prompt.
+
+ In the case of -unixpw_cmd, the commands will also be
+ run as the logged-in user, as long as the user-supplied
+ helper program supports RFB_UNIXPW_CMD_RUN (see the
+ -unixpw_cmd option.)
Also in the case of -unixpw, the user logging in can
place a colon at the end of her username and supply
diff --git a/x11vnc/connections.c b/x11vnc/connections.c
index 8c3e474..20defff 100644
--- a/x11vnc/connections.c
+++ b/x11vnc/connections.c
@@ -574,18 +574,57 @@ int run_user_command(char *cmd, rfbClientPtr client, char *mode, char *input,
close_exec_fds();
if (output != NULL) {
- FILE *ph = popen(cmd, "r");
+ FILE *ph;
char line[1024];
+ char *cmd2 = NULL;
+ char tmp[] = "/tmp/x11vnc-tmp.XXXXXX";
+ int deltmp = 0;
+
+ if (input != NULL) {
+ int tmp_fd = mkstemp(tmp);
+ if (tmp_fd < 0) {
+ rfbLog("mkstemp failed on: %s\n", tmp);
+ clean_up_exit(1);
+ }
+ write(tmp_fd, input, len);
+ close(tmp_fd);
+ deltmp = 1;
+ cmd2 = (char *) malloc(100 + strlen(tmp) + strlen(cmd));
+ sprintf(cmd2, "/bin/cat %s | %s", tmp, cmd);
+
+ ph = popen(cmd2, "r");
+ } else {
+ ph = popen(cmd, "r");
+ }
if (ph == NULL) {
rfbLog("popen(%s) failed", cmd);
rfbLogPerror("popen");
clean_up_exit(1);
}
- while (fgets(line, 1024, ph) != NULL) {
+ memset(line, 0, sizeof(line));
+ while (fgets(line, sizeof(line), ph) != NULL) {
+ int j, k = -1;
if (0) fprintf(stderr, "line: %s", line);
- fprintf(output, "%s", line);
+ /* take care to handle embedded nulls */
+ for (j=0; j < sizeof(line); j++) {
+ if (line[j] != '\0') {
+ k = j;
+ }
+ }
+ if (k >= 0) {
+ write(fileno(output), line, k+1);
+ }
+ memset(line, 0, sizeof(line));
}
+
rc = pclose(ph);
+
+ if (cmd2 != NULL) {
+ free(cmd2);
+ }
+ if (deltmp) {
+ unlink(tmp);
+ }
goto got_rc;
} else if (input != NULL) {
FILE *ph = popen(cmd, "w");
@@ -789,7 +828,7 @@ void client_gone(rfbClientPtr client) {
free(userhost);
} else {
rfbLog("client_gone: using cmd: %s\n", client->host);
- run_user_command(gone_cmd, client, "gone", NULL,0,NULL);
+ run_user_command(gone_cmd, client, "gone", NULL, 0, NULL);
}
}
diff --git a/x11vnc/enc.h b/x11vnc/enc.h
index 64fdf51..aa8b57b 100644
--- a/x11vnc/enc.h
+++ b/x11vnc/enc.h
@@ -83,8 +83,8 @@ so, delete this exception statement from your version.
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
* USA or see <http://www.gnu.org/licenses/>.
*
- * In addition, as a special exception, Karl J. Runge
- * gives permission to link the code of its release of x11vnc with the
+ * In addition, as a special exception, Karl J. Runge gives permission
+ * to link the code of its release of ultravnc_dsm_helper with the
* OpenSSL project's "OpenSSL" library (or with modified versions of it
* that use the same license as the "OpenSSL" library), and distribute
* the linked executables. You must obey the GNU General Public License
diff --git a/x11vnc/help.c b/x11vnc/help.c
index 248887e..ff697af 100644
--- a/x11vnc/help.c
+++ b/x11vnc/help.c
@@ -335,8 +335,8 @@ void print_help(int mode) {
" is needed for the latter, feel free to ask).\n"
"\n"
"-scale fraction Scale the framebuffer by factor \"fraction\". Values\n"
-" less than 1 shrink the fb, larger ones expand it. Note:\n"
-" image may not be sharp and response may be slower.\n"
+" less than 1 shrink the fb, larger ones expand it. Note:\n"
+" the image may not be sharp and response may be slower.\n"
" If \"fraction\" contains a decimal point \".\" it\n"
" is taken as a floating point number, alternatively\n"
" the notation \"m/n\" may be used to denote fractions\n"
@@ -507,7 +507,7 @@ void print_help(int mode) {
" Repeater mode: Some services provide an intermediate\n"
" \"vnc repeater\": http://www.uvnc.com/addons/repeater.html\n"
" (and also http://koti.mbnet.fi/jtko/ for linux port)\n"
-" that acts as a proxy / gateway. Modes like these require\n"
+" that acts as a proxy/gateway. Modes like these require\n"
" an initial string to be sent for the reverse connection\n"
" before the VNC protocol is started. Here are the ways\n"
" to do this:\n"
@@ -782,12 +782,12 @@ void print_help(int mode) {
" full-access passwords)\n"
"\n"
"-unixpw [list] Use Unix username and password authentication. x11vnc\n"
-" uses the su(1) program to verify the user's password.\n"
-" [list] is an optional comma separated list of allowed\n"
-" Unix usernames. If the [list] string begins with the\n"
-" character \"!\" then the entire list is taken as an\n"
-" exclude list. See below for per-user options that can\n"
-" be applied.\n"
+" will use the su(1) program to verify the user's\n"
+" password. [list] is an optional comma separated list\n"
+" of allowed Unix usernames. If the [list] string begins\n"
+" with the character \"!\" then the entire list is taken\n"
+" as an exclude list. See below for per-user options\n"
+" that can be applied.\n"
"\n"
" A familiar \"login:\" and \"Password:\" dialog is\n"
" presented to the user on a black screen inside the\n"
@@ -803,8 +803,9 @@ void print_help(int mode) {
"\n"
" Since the detailed behavior of su(1) can vary from\n"
" OS to OS and for local configurations, test the mode\n"
-" carefully. x11vnc will attempt to be conservative and\n"
-" reject a login if anything abnormal occurs.\n"
+" before deployment to make sure it is working properly.\n"
+" x11vnc will attempt to be conservative and reject a\n"
+" login if anything abnormal occurs.\n"
"\n"
" One case to note: FreeBSD and the other BSD's by\n"
" default it is impossible for the user running x11vnc to\n"
@@ -837,7 +838,7 @@ void print_help(int mode) {
" to come from the same machine x11vnc is running on\n"
" (e.g. from a ssh -L port redirection). And that the\n"
" -stunnel SSL mode be used for encryption over the\n"
-" network.(see the description of -stunnel below).\n"
+" network. (see the description of -stunnel below).\n"
"\n"
" Note: as a convenience, if you ssh(1) in and start\n"
" x11vnc it will check if the environment variable\n"
@@ -865,7 +866,7 @@ void print_help(int mode) {
" Set UNIXPW_DISABLE_LOCALHOST=1 to disable the -localhost\n"
" requirement in Method 2). One should never do this\n"
" (i.e. allow the Unix passwords to be sniffed on the\n"
-" network).\n"
+" network.)\n"
"\n"
" Regarding reverse connections (e.g. -R connect:host\n"
" and -connect host), when the -localhost constraint is\n"
@@ -883,7 +884,7 @@ void print_help(int mode) {
" in -inetd mode (thereby bypassing inetd). See the FAQ\n"
" for details.\n"
"\n"
-" The user names in the comma separated [list] can have\n"
+" The user names in the comma separated [list] may have\n"
" per-user options after a \":\", e.g. \"fred:opts\"\n"
" where \"opts\" is a \"+\" separated list of\n"
" \"viewonly\", \"fullaccess\", \"input=XXXX\", or\n"
@@ -891,13 +892,13 @@ void print_help(int mode) {
" For \"input=\" it is the K,M,B,C described under -input.\n"
"\n"
" If an item in the list is \"*\" that means those\n"
-" options apply to all users. It also means all users\n"
+" options apply to all users. It ALSO implies all users\n"
" are allowed to log in after supplying a valid password.\n"
" Use \"deny\" to explicitly deny some users if you use\n"
-" \"*\" to set a global option. If [list] begins with\n"
-" the \"!\" character then \"*\" is ignored for checking\n"
-" if the user is allowed, but the any value of options\n"
-" associated with it does apply as normal.\n"
+" \"*\" to set a global option. If [list] begins with the\n"
+" \"!\" character then \"*\" is ignored for checking if\n"
+" the user is allowed, but the option values associated\n"
+" with it do apply as normal.\n"
"\n"
" There are also some utilities for testing password\n"
" if [list] starts with the \"%%\" character. See the\n"
@@ -922,32 +923,89 @@ void print_help(int mode) {
"\n"
" NIS is not required for this mode to work (only that\n"
" getpwnam(3) return the encrypted password is required),\n"
-" but it is unlikely it will work for any most modern\n"
-" environments unless x11vnc is run as root to be able\n"
-" to access /etc/shadow (note running as root is often\n"
-" done when running x11vnc from inetd and xdm/gdm/kdm).\n"
+" but it is unlikely it will work (as an ordinary user)\n"
+" for most modern environments unless NIS is available.\n"
+" On the other hand, when x11vnc is run as root it will\n"
+" be able to to access /etc/shadow even if NIS is not\n"
+" available (note running as root is often done when\n"
+" running x11vnc from inetd and xdm/gdm/kdm).\n"
"\n"
" Looked at another way, if you do not want to use the\n"
-" su(1) method provided by -unixpw, you can run x11vnc\n"
-" as root and use -unixpw_nis. Any users with passwords\n"
-" in /etc/shadow can then be authenticated. You may want\n"
-" to use -users unixpw= to switch the process user after\n"
-" the user logs in.\n"
+" su(1) method provided by -unixpw (i.e. su_verify()), you\n"
+" can run x11vnc as root and use -unixpw_nis. Any users\n"
+" with passwords in /etc/shadow can then be authenticated.\n"
+"\n"
+" In -unixpw_nis mode, under no circumstances is x11vnc's\n"
+" user password verifying function based on su called\n"
+" (i.e. the function su_verify() that runs /bin/su\n"
+" in a pseudoterminal to verify passwords.) However,\n"
+" if -unixpw_nis is used in conjunction with the -find\n"
+" and -create -display WAIT:... modes then, if x11vnc is\n"
+" running as root, /bin/su may be called externally to\n"
+" run the find or create commands.\n"
"\n"
"-unixpw_cmd cmd As -unixpw above, however do not use su(1) but rather\n"
" run the externally supplied command \"cmd\". The first\n"
-" line of its stdin will the username and the second line\n"
-" the received password. If the command exits with status\n"
-" 0 (success) the VNC client will be accepted. It will be\n"
-" rejected for any other return status.\n"
-"\n"
-" Dynamic passwords and non-unix passwords can be\n"
-" implemented this way by providing your own custom helper\n"
-" program. Note that under unixpw mode the remote viewer\n"
-" is given 3 tries to enter the correct password.\n"
-"\n"
-" If a list of allowed users is needed use -unixpw [list]\n"
-" in addition to this option.\n"
+" line of its stdin will be the username and the second\n"
+" line the received password. If the command exits\n"
+" with status 0 (success) the VNC user will be accepted.\n"
+" It will be rejected for any other return status.\n"
+"\n"
+" Dynamic passwords and non-unix passwords, e.g. LDAP,\n"
+" can be implemented this way by providing your own custom\n"
+" helper program. Note that the remote viewer is given 3\n"
+" tries to enter the correct password, and so the program\n"
+" may be called in a row that many (or more) times.\n"
+"\n"
+" If a list of allowed users is needed to limit who can\n"
+" log in, use -unixpw [list] in addition to this option.\n"
+"\n"
+" In FINDDISPLAY and FINDCREATEDISPLAY modes the \"cmd\"\n"
+" will also be run with the RFB_UNIXPW_CMD_RUN env. var.\n"
+" non-empty and set to the corresponding display\n"
+" find/create command. The first two lines of input are\n"
+" the username and passwd as in the normal case described\n"
+" above. To support FINDDISPLAY and FINDCREATEDISPLAY,\n"
+" \"cmd\" should run the requested command as the user\n"
+" (and most likely refusing to run it if the password is\n"
+" not correct.) Here is an example script (note it has\n"
+" a hardwired bogus password \"abc\"!)\n"
+"\n"
+" #!/bin/sh\n"
+" # Example x11vnc -unixpw_cmd script.\n"
+" # Read the first two lines of stdin (user and passwd)\n"
+" read user\n"
+" read pass\n"
+" \n"
+" debug=0\n"
+" if [ $debug = 1 ]; then\n"
+" echo \"user: $user\" 1>&2\n"
+" echo \"pass: $pass\" 1>&2\n"
+" env | egrep -i 'rfb|vnc' 1>&2\n"
+" fi\n"
+" \n"
+" # Check if the password is valid.\n"
+" # (A real example would use ldap lookup, etc!)\n"
+" if [ \"X$pass\" != \"Xabc\" ]; then\n"
+" exit 1 # incorrect password\n"
+" fi\n"
+" \n"
+" if [ \"X$RFB_UNIXPW_CMD_RUN\" = \"X\" ]; then\n"
+" exit 0 # correct password\n"
+" else\n"
+" # Run the requested command (finddisplay)\n"
+" if [ $debug = 1 ]; then\n"
+" echo \"run: $RFB_UNIXPW_CMD_RUN\" 1>&2\n"
+" fi\n"
+" exec /bin/su - \"$user\" -c \"$RFB_UNIXPW_CMD_RUN\"\n"
+" fi\n"
+"\n"
+" In -unixpw_cmd mode, under no circumstances is x11vnc's\n"
+" user password verifying function based on su called\n"
+" (i.e. the function su_verify() that runs /bin/su in a\n"
+" pseudoterminal to verify passwords.) It is up to the\n"
+" supplied unixpw_cmd to do user switching if desired\n"
+" and if it has the permissions to do so.\n"
"\n"
"-find Find the user's display using FINDDISPLAY. This is an\n"
" alias for \"-display WAIT:cmd=FINDDISPLAY\".\n"
@@ -1064,9 +1122,15 @@ void print_help(int mode) {
"\n"
" xauth extract - $DISPLAY\"\n"
"\n"
-" In the case of -unixpw (but not -unixpw_nis), then the\n"
-" cmd= command is run as the user who just authenticated\n"
-" via the login and password prompt.\n"
+" In the case of -unixpw (and -unixpw_nis only if x11vnc\n"
+" is running as root), then the cmd= command is run\n"
+" as the user who just authenticated via the login and\n"
+" password prompt.\n"
+"\n"
+" In the case of -unixpw_cmd, the commands will also be\n"
+" run as the logged-in user, as long as the user-supplied\n"
+" helper program supports RFB_UNIXPW_CMD_RUN (see the\n"
+" -unixpw_cmd option.)\n"
"\n"
" Also in the case of -unixpw, the user logging in can\n"
" place a colon at the end of her username and supply\n"
diff --git a/x11vnc/pointer.c b/x11vnc/pointer.c
index 0a3d806..70d2b8e 100644
--- a/x11vnc/pointer.c
+++ b/x11vnc/pointer.c
@@ -343,11 +343,22 @@ void update_x11_pointer_position(int x, int y) {
return;
#else
int rc;
+ static int watch_dx_dy = -1;
RAWFB_RET_VOID
+ if (watch_dx_dy == -1) {
+ if (getenv("X11VNC_WATCH_DX_DY")) {
+ watch_dx_dy = 1;
+ } else {
+ watch_dx_dy = 0;
+ }
+ }
+
X_LOCK;
- if (use_xwarppointer) {
+ if (watch_dx_dy && cursor_x == x && cursor_y == y) {
+ ;
+ } else if (use_xwarppointer) {
/*
* off_x and off_y not needed with XWarpPointer since
* window is used:
diff --git a/x11vnc/unixpw.c b/x11vnc/unixpw.c
index 693012b..5ba3879 100644
--- a/x11vnc/unixpw.c
+++ b/x11vnc/unixpw.c
@@ -96,6 +96,7 @@ void unixpw_accept(char *user);
void unixpw_deny(void);
void unixpw_msg(char *msg, int delay);
int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size, int nodisp);
+int unixpw_cmd_run(char *user, char *pass, char *cmd, char *line, int *n, int nodisp);
int crypt_verify(char *user, char *pass);
int cmd_verify(char *user, char *pass);
void unixpw_verify_screen(char *user, char *pass);
@@ -530,6 +531,82 @@ int crypt_verify(char *user, char *pass) {
#endif /* UNIXPW_CRYPT */
}
+int unixpw_cmd_run(char *user, char *pass, char *cmd, char *line, int *n, int nodisp) {
+ int i, len, rc;
+ char *str;
+ FILE *out;
+
+ if (! user || ! pass) {
+ return 0;
+ }
+ if (! unixpw_cmd || *unixpw_cmd == '\0') {
+ return 0;
+ }
+
+ if (! scheck(user, 100, "username")) {
+ return 0;
+ }
+ if (! scheck(pass, 100, "password")) {
+ return 0;
+ }
+ if (! unixpw_list_match(user)) {
+ return 0;
+ }
+ if (cmd == NULL) {
+ cmd = "";
+ }
+
+ len = strlen(user) + 1 + strlen(pass) + 1 + 1;
+ str = (char *) malloc(len);
+ if (! str) {
+ return 0;
+ }
+ str[0] = '\0';
+ strcat(str, user);
+ strcat(str, "\n");
+ strcat(str, pass);
+ if (!strchr(pass, '\n')) {
+ strcat(str, "\n");
+ }
+
+ out = tmpfile();
+ if (out == NULL) {
+ rfbLog("unixpw_cmd_run tmpfile() failed.\n");
+ clean_up_exit(1);
+ }
+
+ set_env("RFB_UNIXPW_CMD_RUN", cmd);
+
+ rc = run_user_command(unixpw_cmd, unixpw_client, "cmd_verify",
+ str, strlen(str), out);
+
+ set_env("RFB_UNIXPW_CMD_RUN", "");
+
+ for (i=0; i < len; i++) {
+ str[i] = '\0';
+ }
+ free(str);
+
+ fflush(out);
+ rewind(out);
+ for (i=0; i < (*n) - 1; i++) {
+ int c = fgetc(out);
+ if (c == EOF) {
+ break;
+ }
+ line[i] = (char) c;
+ }
+ fclose(out);
+ *n = i;
+
+ if (rc == 0) {
+ return 1;
+ } else {
+ return 0;
+ }
+}
+
+
int cmd_verify(char *user, char *pass) {
int i, len, rc;
char *str;
@@ -602,6 +679,7 @@ int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size, int
set_db();
first = 0;
}
+ rfbLog("su_verify: '%s' for %s.\n", user, cmd ? "command" : "login");
if (! scheck(user, 100, "username")) {
return 0;
@@ -1043,7 +1121,7 @@ int unixpw_verify(char *user, char *pass) {
" succeeded.\n", user);
ok = 1;
} else {
- rfbLog("unixpw_verify: crypt_verify login for '%s'"
+ rfbLog("unixpw_verify: cmd_verify login for '%s'"
" failed.\n", user);
usleep(3000*1000);
ok = 0;
diff --git a/x11vnc/unixpw.h b/x11vnc/unixpw.h
index 374a59b..6da79e0 100644
--- a/x11vnc/unixpw.h
+++ b/x11vnc/unixpw.h
@@ -42,6 +42,7 @@ extern void unixpw_accept(char *user);
extern void unixpw_deny(void);
extern void unixpw_msg(char *msg, int delay);
extern int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size, int nodisp);
+extern int unixpw_cmd_run(char *user, char *pass, char *cmd, char *line, int *n, int nodisp);
extern int crypt_verify(char *user, char *pass);
extern int cmd_verify(char *user, char *pass);
extern int unixpw_verify(char *user, char *pass);
diff --git a/x11vnc/user.c b/x11vnc/user.c
index 35adec7..d1772d2 100644
--- a/x11vnc/user.c
+++ b/x11vnc/user.c
@@ -308,6 +308,9 @@ static void user2uid(char *user, uid_t *uid, gid_t *gid, char **name, char **hom
if (strstr(user2group[i], user) == user2group[i]) {
char *w = user2group[i] + strlen(user);
if (*w == '.') {
+#if (SMALL_FOOTPRINT > 2)
+ gotgroup = 0;
+#else
struct group* gr = getgrnam(++w);
if (! gr) {
rfbLog("Invalid group: %s\n", w);
@@ -320,6 +323,7 @@ static void user2uid(char *user, uid_t *uid, gid_t *gid, char **name, char **hom
did[i] = 1;
}
gotgroup = 1;
+#endif
}
}
i++;
@@ -761,7 +765,7 @@ static int switch_user_env(uid_t uid, gid_t gid, char *name, char *home, int fb_
return 0;
#else
/*
- * OK tricky here, we need to free the shm... otherwise
+ * OK, tricky here, we need to free the shm... otherwise
* we won't be able to delete it as the other user...
*/
if (fb_mode == 1 && (using_shm && ! xform24to32)) {
@@ -773,11 +777,13 @@ static int switch_user_env(uid_t uid, gid_t gid, char *name, char *home, int fb_
#if LIBVNCSERVER_HAVE_PWD_H
if (getpwuid(uid) != NULL && getenv("X11VNC_SINGLE_GROUP") == NULL) {
struct passwd *p = getpwuid(uid);
- if (initgroups(p->pw_name, gid) == 0) {
+ /* another possibility is p->pw_gid instead of gid */
+ if (setgid(gid) == 0 && initgroups(p->pw_name, gid) == 0) {
grp_ok = 1;
} else {
rfbLogPerror("initgroups");
}
+ endgrent();
}
#endif
#endif
@@ -2235,12 +2241,58 @@ static char *get_usslpeer() {
return upeer;
}
+static void do_try_switch(char *usslpeer, char *users_list_save) {
+ if (usslpeer) {
+ char *u = (char *) malloc(strlen(usslpeer+2));
+ sprintf(u, "+%s", usslpeer);
+ if (switch_user(u, 0)) {
+ rfbLog("sslpeer switched to user: %s\n", usslpeer);
+ } else {
+ rfbLog("sslpeer failed to switch to user: %s\n", usslpeer);
+ }
+ free(u);
+
+ } else if (users_list_save && keep_unixpw_user) {
+ char *user = keep_unixpw_user;
+ char *u = (char *)malloc(strlen(user)+1);
+
+ users_list = users_list_save;
+
+ u[0] = '\0';
+ if (!strcmp(users_list, "unixpw=")) {
+ sprintf(u, "+%s", user);
+ } else {
+ char *p, *str = strdup(users_list);
+ p = strtok(str + strlen("unixpw="), ",");
+ while (p) {
+ if (!strcmp(p, user)) {
+ sprintf(u, "+%s", user);
+ break;
+ }
+ p = strtok(NULL, ",");
+ }
+ free(str);
+ }
+
+ if (u[0] == '\0') {
+ rfbLog("unixpw_accept skipping switch to user: %s (drc)\n", user);
+ } else if (switch_user(u, 0)) {
+ rfbLog("unixpw_accept switched to user: %s (drc)\n", user);
+ } else {
+ rfbLog("unixpw_accept failed to switch to user: %s (drc)\n", user);
+ }
+ free(u);
+ }
+}
+
static int do_run_cmd(char *cmd, char *create_cmd, char *users_list_save, int created_disp, int db) {
char tmp[] = "/tmp/x11vnc-find_display.XXXXXX";
char line1[1024], line2[16384];
char *q, *usslpeer = NULL;
int n, nodisp = 0, saw_xdmcp = 0;
int tmp_fd = -1;
+ int internal_cmd = 0;
+ int tried_switch = 0;
memset(line1, 0, 1024);
memset(line2, 0, 16384);
@@ -2251,6 +2303,7 @@ static int do_run_cmd(char *cmd, char *create_cmd, char *users_list_save, int cr
return 0;
}
}
+ if (getenv("DEBUG_RUN_CMD")) db = 1;
/* only sets environment variables: */
run_user_command("", latest_client, "env", NULL, 0, NULL);
@@ -2265,7 +2318,11 @@ static int do_run_cmd(char *cmd, char *create_cmd, char *users_list_save, int cr
strstr(cmd, "FINDCREATEDISPLAY") == cmd) {
char *nd = "";
char fdout[128];
+
+ internal_cmd = 1;
+
tmp_fd = mkstemp(tmp);
+
if (tmp_fd < 0) {
rfbLog("wait_for_client: open failed: %s\n", tmp);
rfbLogPerror("mkstemp");
@@ -2302,7 +2359,7 @@ static int do_run_cmd(char *cmd, char *create_cmd, char *users_list_save, int cr
rfbLog("wait_for_client: running: %s\n", cmd);
- if (unixpw) {
+ if (unixpw && !unixpw_nis) {
int res = 0, k, j, i;
char line[18000];
@@ -2310,8 +2367,13 @@ static int do_run_cmd(char *cmd, char *create_cmd, char *users_list_save, int cr
if (keep_unixpw_user && keep_unixpw_pass) {
n = 18000;
- res = su_verify(keep_unixpw_user,
- keep_unixpw_pass, cmd, line, &n, nodisp);
+ if (unixpw_cmd != NULL) {
+ res = unixpw_cmd_run(keep_unixpw_user,
+ keep_unixpw_pass, cmd, line, &n, nodisp);
+ } else {
+ res = su_verify(keep_unixpw_user,
+ keep_unixpw_pass, cmd, line, &n, nodisp);
+ }
}
if (db) {fprintf(stderr, "line: "); write(2, line, n); write(2, "\n", 1); fprintf(stderr, "res=%d n=%d\n", res, n);}
@@ -2331,7 +2393,13 @@ if (db) {fprintf(stderr, "line: "); write(2, line, n); write(2, "\n", 1); fprint
findcreatedisplay = 1;
- if (getuid() != 0) {
+ if (unixpw_cmd != NULL) {
+ /* let the external unixpw command do it: */
+ n = 18000;
+ close_exec_fds();
+ res = unixpw_cmd_run(keep_unixpw_user,
+ keep_unixpw_pass, create_cmd, line, &n, nodisp);
+ } else if (getuid() != 0) {
/* if not root, run as the other user... */
n = 18000;
close_exec_fds();
@@ -2411,6 +2479,7 @@ if (db) fprintf(stderr, "line1: '%s'\n", line1);
}
if (db) write(2, line, 100);
if (db) fprintf(stderr, "\n");
+
} else {
FILE *p;
int rc;
@@ -2428,9 +2497,22 @@ if (db) fprintf(stderr, "\n");
p = popen(c, "r");
free(c);
+ } else if (unixpw_nis && keep_unixpw_user) {
+ char *c;
+ if (getuid() == 0) {
+ c = (char *) malloc(strlen("su - '' -c \"")
+ + strlen(keep_unixpw_user) + strlen(cmd) + 1 + 1);
+ sprintf(c, "su - '%s' -c \"%s\"", keep_unixpw_user, cmd);
+ } else {
+ c = strdup(cmd);
+ }
+ p = popen(c, "r");
+ free(c);
+
} else {
p = popen(cmd, "r");
}
+
if (! p) {
rfbLog("wait_for_client: cmd failed: %s\n", cmd);
rfbLogPerror("popen");
@@ -2575,49 +2657,13 @@ fprintf(stderr, "\n");}
}
}
- if (usslpeer) {
- char *u = (char *) malloc(strlen(usslpeer+2));
- sprintf(u, "+%s", usslpeer);
- if (switch_user(u, 0)) {
- rfbLog("sslpeer switched to user: %s\n", usslpeer);
- } else {
- rfbLog("sslpeer failed to switch to user: %s\n", usslpeer);
- }
- free(u);
-
- } else if (users_list_save && keep_unixpw_user) {
- char *user = keep_unixpw_user;
- char *u = (char *)malloc(strlen(user)+1);
-
- users_list = users_list_save;
-
- u[0] = '\0';
- if (!strcmp(users_list, "unixpw=")) {
- sprintf(u, "+%s", user);
- } else {
- char *p, *str = strdup(users_list);
- p = strtok(str + strlen("unixpw="), ",");
- while (p) {
- if (!strcmp(p, user)) {
- sprintf(u, "+%s", user);
- break;
- }
- p = strtok(NULL, ",");
- }
- free(str);
- }
-
- if (u[0] == '\0') {
- rfbLog("unixpw_accept skipping switch to user: %s\n", user);
- } else if (switch_user(u, 0)) {
- rfbLog("unixpw_accept switched to user: %s\n", user);
- } else {
- rfbLog("unixpw_accept failed to switch to user: %s\n", user);
- }
- free(u);
+ if (!tried_switch) {
+ do_try_switch(usslpeer, users_list_save);
+ tried_switch = 1;
}
if (unixpw) {
+ /* Some cleanup and messaging for -unixpw case: */
char str[32];
if (keep_unixpw_user && keep_unixpw_pass) {
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index c2da5ee..6c93474 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -1,8 +1,8 @@
.\" This file was automatically generated from x11vnc -help output.
-.TH X11VNC "1" "July 2009" "x11vnc " "User Commands"
+.TH X11VNC "1" "August 2009" "x11vnc " "User Commands"
.SH NAME
x11vnc - allow VNC connections to real X11 displays
- version: 0.9.9, lastmod: 2009-07-11
+ version: 0.9.9, lastmod: 2009-08-10
.SH SYNOPSIS
.B x11vnc
[OPTION]...
@@ -347,8 +347,8 @@ is needed for the latter, feel free to ask).
\fB-scale\fR \fIfraction\fR
.IP
Scale the framebuffer by factor \fIfraction\fR. Values
-less than 1 shrink the fb, larger ones expand it. Note:
-image may not be sharp and response may be slower.
+less than 1 shrink the fb, larger ones expand it. Note:
+the image may not be sharp and response may be slower.
If \fIfraction\fR contains a decimal point "." it
is taken as a floating point number, alternatively
the notation "m/n" may be used to denote fractions
@@ -568,7 +568,7 @@ is running as root (e.g. via
Repeater mode: Some services provide an intermediate
"vnc repeater": http://www.uvnc.com/addons/repeater.html
(and also http://koti.mbnet.fi/jtko/ for linux port)
-that acts as a proxy / gateway. Modes like these require
+that acts as a proxy/gateway. Modes like these require
an initial string to be sent for the reverse connection
before the VNC protocol is started. Here are the ways
to do this:
@@ -871,14 +871,14 @@ full-access passwords)
\fB-unixpw\fR \fI[list]\fR
.IP
Use Unix username and password authentication. x11vnc
-uses the
+will use the
.IR su (1)
-program to verify the user's password.
-[list] is an optional comma separated list of allowed
-Unix usernames. If the [list] string begins with the
-character "!" then the entire list is taken as an
-exclude list. See below for per-user options that can
-be applied.
+program to verify the user's
+password. [list] is an optional comma separated list
+of allowed Unix usernames. If the [list] string begins
+with the character "!" then the entire list is taken
+as an exclude list. See below for per-user options
+that can be applied.
.IP
A familiar "login:" and "Password:" dialog is
presented to the user on a black screen inside the
@@ -896,8 +896,9 @@ Since the detailed behavior of
.IR su (1)
can vary from
OS to OS and for local configurations, test the mode
-carefully. x11vnc will attempt to be conservative and
-reject a login if anything abnormal occurs.
+before deployment to make sure it is working properly.
+x11vnc will attempt to be conservative and reject a
+login if anything abnormal occurs.
.IP
One case to note: FreeBSD and the other BSD's by
default it is impossible for the user running x11vnc to
@@ -932,7 +933,7 @@ Method 2) requires the viewer connection to appear
to come from the same machine x11vnc is running on
(e.g. from a ssh \fB-L\fR port redirection). And that the
\fB-stunnel\fR SSL mode be used for encryption over the
-network.(see the description of \fB-stunnel\fR below).
+network. (see the description of \fB-stunnel\fR below).
.IP
Note: as a convenience, if you
.IR ssh (1)
@@ -966,7 +967,7 @@ local connections from that machine are accepted).
Set UNIXPW_DISABLE_LOCALHOST=1 to disable the \fB-localhost\fR
requirement in Method 2). One should never do this
(i.e. allow the Unix passwords to be sniffed on the
-network).
+network.)
.IP
Regarding reverse connections (e.g. \fB-R\fR connect:host
and \fB-connect\fR host), when the \fB-localhost\fR constraint is
@@ -984,7 +985,7 @@ Tip: you can also have your own stunnel spawn x11vnc
in \fB-inetd\fR mode (thereby bypassing inetd). See the FAQ
for details.
.IP
-The user names in the comma separated [list] can have
+The user names in the comma separated [list] may have
per-user options after a ":", e.g. "fred:opts"
where "opts" is a "+" separated list of
"viewonly", "fullaccess", "input=XXXX", or
@@ -992,13 +993,13 @@ where "opts" is a "+" separated list of
For "input=" it is the K,M,B,C described under \fB-input.\fR
.IP
If an item in the list is "*" that means those
-options apply to all users. It also means all users
+options apply to all users. It ALSO implies all users
are allowed to log in after supplying a valid password.
Use "deny" to explicitly deny some users if you use
-"*" to set a global option. If [list] begins with
-the "!" character then "*" is ignored for checking
-if the user is allowed, but the any value of options
-associated with it does apply as normal.
+"*" to set a global option. If [list] begins with the
+"!" character then "*" is ignored for checking if
+the user is allowed, but the option values associated
+with it do apply as normal.
.IP
There are also some utilities for testing password
if [list] starts with the "%" character. See the
@@ -1032,18 +1033,27 @@ user can authenticate ANY user.
NIS is not required for this mode to work (only that
.IR getpwnam (3)
return the encrypted password is required),
-but it is unlikely it will work for any most modern
-environments unless x11vnc is run as root to be able
-to access /etc/shadow (note running as root is often
-done when running x11vnc from inetd and xdm/gdm/kdm).
+but it is unlikely it will work (as an ordinary user)
+for most modern environments unless NIS is available.
+On the other hand, when x11vnc is run as root it will
+be able to to access /etc/shadow even if NIS is not
+available (note running as root is often done when
+running x11vnc from inetd and xdm/gdm/kdm).
.IP
Looked at another way, if you do not want to use the
.IR su (1)
-method provided by \fB-unixpw,\fR you can run x11vnc
-as root and use \fB-unixpw_nis.\fR Any users with passwords
-in /etc/shadow can then be authenticated. You may want
-to use \fB-users\fR unixpw= to switch the process user after
-the user logs in.
+method provided by \fB-unixpw\fR (i.e. su_verify()), you
+can run x11vnc as root and use \fB-unixpw_nis.\fR Any users
+with passwords in /etc/shadow can then be authenticated.
+.IP
+In \fB-unixpw_nis\fR mode, under no circumstances is x11vnc's
+user password verifying function based on su called
+(i.e. the function su_verify() that runs /bin/su
+in a pseudoterminal to verify passwords.) However,
+if \fB-unixpw_nis\fR is used in conjunction with the \fB-find\fR
+and \fB-create\fR \fB-display\fR WAIT:... modes then, if x11vnc is
+running as root, /bin/su may be called externally to
+run the find or create commands.
.PP
\fB-unixpw_cmd\fR \fIcmd\fR
.IP
@@ -1051,18 +1061,66 @@ As \fB-unixpw\fR above, however do not use
.IR su (1)
but rather
run the externally supplied command \fIcmd\fR. The first
-line of its stdin will the username and the second line
-the received password. If the command exits with status
-0 (success) the VNC client will be accepted. It will be
-rejected for any other return status.
-.IP
-Dynamic passwords and non-unix passwords can be
-implemented this way by providing your own custom helper
-program. Note that under unixpw mode the remote viewer
-is given 3 tries to enter the correct password.
-.IP
-If a list of allowed users is needed use \fB-unixpw\fR [list]
-in addition to this option.
+line of its stdin will be the username and the second
+line the received password. If the command exits
+with status 0 (success) the VNC user will be accepted.
+It will be rejected for any other return status.
+.IP
+Dynamic passwords and non-unix passwords, e.g. LDAP,
+can be implemented this way by providing your own custom
+helper program. Note that the remote viewer is given 3
+tries to enter the correct password, and so the program
+may be called in a row that many (or more) times.
+.IP
+If a list of allowed users is needed to limit who can
+log in, use \fB-unixpw\fR [list] in addition to this option.
+.IP
+In FINDDISPLAY and FINDCREATEDISPLAY modes the \fIcmd\fR
+will also be run with the RFB_UNIXPW_CMD_RUN env. var.
+non-empty and set to the corresponding display
+find/create command. The first two lines of input are
+the username and passwd as in the normal case described
+above. To support FINDDISPLAY and FINDCREATEDISPLAY,
+\fIcmd\fR should run the requested command as the user
+(and most likely refusing to run it if the password is
+not correct.) Here is an example script (note it has
+a hardwired bogus password "abc"!)
+.IP
+#!/bin/sh
+# Example x11vnc \fB-unixpw_cmd\fR script.
+# Read the first two lines of stdin (user and passwd)
+read user
+read pass
+.IP
+debug=0
+if [ $debug = 1 ]; then
+echo "user: $user" 1>&2
+echo "pass: $pass" 1>&2
+env | egrep \fB-i\fR 'rfb|vnc' 1>&2
+fi
+.IP
+# Check if the password is valid.
+# (A real example would use ldap lookup, etc!)
+if [ "X$pass" != "Xabc" ]; then
+exit 1 # incorrect password
+fi
+.IP
+if [ "X$RFB_UNIXPW_CMD_RUN" = "X" ]; then
+exit 0 # correct password
+else
+# Run the requested command (finddisplay)
+if [ $debug = 1 ]; then
+echo "run: $RFB_UNIXPW_CMD_RUN" 1>&2
+fi
+exec /bin/su - "$user" \fB-c\fR "$RFB_UNIXPW_CMD_RUN"
+fi
+.IP
+In \fB-unixpw_cmd\fR mode, under no circumstances is x11vnc's
+user password verifying function based on su called
+(i.e. the function su_verify() that runs /bin/su in a
+pseudoterminal to verify passwords.) It is up to the
+supplied unixpw_cmd to do user switching if desired
+and if it has the permissions to do so.
.PP
\fB-find\fR
.IP
@@ -1214,9 +1272,15 @@ xauthority data for the display. For example;
.IP
xauth extract - $DISPLAY"
.IP
-In the case of \fB-unixpw\fR (but not \fB-unixpw_nis),\fR then the
-cmd= command is run as the user who just authenticated
-via the login and password prompt.
+In the case of \fB-unixpw\fR (and \fB-unixpw_nis\fR only if x11vnc
+is running as root), then the cmd= command is run
+as the user who just authenticated via the login and
+password prompt.
+.IP
+In the case of \fB-unixpw_cmd,\fR the commands will also be
+run as the logged-in user, as long as the user-supplied
+helper program supports RFB_UNIXPW_CMD_RUN (see the
+\fB-unixpw_cmd\fR option.)
.IP
Also in the case of \fB-unixpw,\fR the user logging in can
place a colon at the end of her username and supply
@@ -5827,7 +5891,7 @@ max time in ms to wait for RFB client
\fB-rfbauth\fR \fIpasswd-file\fR
.IP
use authentication on RFB protocol
-(use 'storepasswd' to create a password file)
+(use 'x11vnc \fB-storepasswd\fR pass file' to create a password file)
.PP
\fB-rfbversion\fR \fI3.x\fR
.IP
diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c
index 95e042c..2ef6217 100644
--- a/x11vnc/x11vnc.c
+++ b/x11vnc/x11vnc.c
@@ -2482,6 +2482,9 @@ int main(int argc, char* argv[]) {
if (unixpw_list) {
unixpw_list = NULL;
}
+ if (unixpw_cmd) {
+ unixpw_cmd = NULL;
+ }
continue;
}
if (!strcmp(arg, "-vencrypt")) {
diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c
index 4c9d5b1..cc973f0 100644
--- a/x11vnc/x11vnc_defs.c
+++ b/x11vnc/x11vnc_defs.c
@@ -47,7 +47,7 @@ int xtrap_base_event_type = 0;
int xdamage_base_event_type = 0;
/* date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.9.9 lastmod: 2009-07-11";
+char lastmod[] = "0.9.9 lastmod: 2009-08-10";
/* X display info */
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-14 02:45:39 +0000