summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrunge <runge>2007-03-13 23:06:38 +0000
committerrunge <runge>2007-03-13 23:06:38 +0000
commit15f792bc2185d9317b0a35855b15759520877ee9 (patch)
tree0435ffea43b1208ba1b53fba92f503e2d7a950f1
parent0d4870c0a0da2680d60cd2b91b0541af2558d640 (diff)
downloadlibtdevnc-15f792bc2185d9317b0a35855b15759520877ee9.tar.gz
libtdevnc-15f792bc2185d9317b0a35855b15759520877ee9.zip
x11vnc: fix crash for kde dcop. limit ncache beta tester to 96MB viewers.
Diffstat
-rw-r--r--x11vnc/ChangeLog4
-rw-r--r--x11vnc/README2148
-rw-r--r--x11vnc/help.c18
-rw-r--r--x11vnc/scan.c2
-rw-r--r--x11vnc/screen.c2
-rw-r--r--x11vnc/solid.c11
-rw-r--r--x11vnc/x11vnc.122
-rw-r--r--x11vnc/x11vnc.c21
-rw-r--r--x11vnc/x11vnc_defs.c2
9 files changed, 1271 insertions, 959 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index df0401e..1ba41de 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,3 +1,7 @@
+2007-03-13 Karl Runge <runge@karlrunge.com>
+ * x11vnc: fix crash for kde dcop. limit ncache beta
+ tester to 96MB viewers.
+
2007-02-18 Karl Runge <runge@karlrunge.com>
* x11vnc: Get ultravnc textchat working with ssvnc.
diff --git a/x11vnc/README b/x11vnc/README
index 3da443e..5cde165 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
-x11vnc README file Date: Mon Feb 19 01:15:25 EST 2007
+x11vnc README file Date: Tue Mar 13 06:20:11 EDT 2007
The following information is taken from these URLs:
@@ -859,15 +859,16 @@ make
such as x0rfbserver, krfb, x0vncserver, vino. x11vnc uses a 32 x 32
pixel tile model (the desktop is decomposed into roughly 1000 such
tiles), where changed tiles are found by pseudo-randomly polling 1
- pixel tall horizontal scanlines. This is a surprisingly effective
- algorithm for finding changed regions. For keyboard and mouse user
- input the XTEST extension is used to pass the input events to the X
- server. To detect XBell "beeps" the XKEYBOARD extension is used. If
- available, the XFIXES extension is used to retrieve the current mouse
- cursor shape. Also, if available the X DAMAGE extension is used to
- receive hints from the X server where modified regions on the screen
- are. This greatly reduces the system load when not much is changing on
- the screen and also improves how quickly the screen is updated.
+ pixel tall horizontal scanlines separated vertically by 32 pixels.
+ This is a surprisingly effective algorithm for finding changed
+ regions. For keyboard and mouse user input the XTEST extension is used
+ to pass the input events to the X server. To detect XBell "beeps" the
+ XKEYBOARD extension is used. If available, the XFIXES extension is
+ used to retrieve the current mouse cursor shape. Also, if available
+ the X DAMAGE extension is used to receive hints from the X server
+ where modified regions on the screen are. This greatly reduces the
+ system load when not much is changing on the screen and also improves
+ how quickly the screen is updated.
Barbershop mirrors effect: What if x11vnc is started up, and
vncviewer is then started up on the same machine and displayed on the
@@ -1389,20 +1390,24 @@ make
[281]Q-110: Which UltraVNC extensions are supported?
- [282]Q-111: Can I (temporarily) mount my local (viewer-side)
+ [282]Q-111: Can x11vnc emulate UltraVNC's Single Click helpdesk mode?
+ I.e. something very simple for a naive user to initiate a reverse vnc
+ connection from their desktop to a helpdesk operator's VNC Viewer.
+
+ [283]Q-112: Can I (temporarily) mount my local (viewer-side)
Windows/Samba File share on the machine where x11vnc is running?
- [283]Q-112: Can I redirect CUPS print jobs from the remote desktop
+ [284]Q-113: Can I redirect CUPS print jobs from the remote desktop
where x11vnc is running to a printer on my local (viewer-side)
machine?
- [284]Q-113: How can I hear the sound (audio) from the remote
+ [285]Q-114: How can I hear the sound (audio) from the remote
applications on the desktop I am viewing via x11vnc?
- [285]Q-114: Why don't I hear the "Beeps" in my X session (e.g. when
+ [286]Q-115: Why don't I hear the "Beeps" in my X session (e.g. when
typing tput bel in an xterm)?
- [286]Q-115: Thanks for your program and for your help! Can I make a
+ [287]Q-116: Thanks for your program and for your help! Can I make a
donation?
_________________________________________________________________
@@ -1415,7 +1420,7 @@ make
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 [287]-display
+ on). Set your DISPLAY environment variable or use the [288]-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).
@@ -1432,9 +1437,9 @@ make
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 [288]this Howto for much info on X11 permissions. For example, you
+ or [289]this Howto for much info on X11 permissions. For example, you
may need to set your XAUTHORITY environment variable or use the
- [289]-auth option to point to the correct MIT-MAGIC-COOKIE file (e.g.
+ [290]-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.), or simply be sure you run x11vnc as the
correct user (i.e. the user who is logged into the X session you wish
@@ -1456,11 +1461,11 @@ make
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 [290]this faq for other display manager
+ read the gdm cookie file, see [291]this faq for other display manager
cookie file names). While running x11vnc as root, remember it comes
with no warranty ;-).
- Note as of Feb/2007 you can also try the [291]-find option instead of
+ Note as of Feb/2007 you can also try the [292]-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
@@ -1469,7 +1474,7 @@ make
(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 be of use
- (please read the documentation on the [292]-users option).
+ (please read the documentation on the [293]-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
@@ -1573,7 +1578,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).
+ was doing). See [294]here too.
Q-3: I just built x11vnc successfully, but when I use it my keystrokes
@@ -1647,7 +1652,7 @@ h
earlier and perhaps non-Solaris):
First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
- above [293]Solaris build script to run the configure command. That
+ above [295]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
@@ -1673,7 +1678,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
- [294]SunOS 4.x
+ [296]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
@@ -1683,28 +1688,28 @@ typedef unsigned int in_addr_t;
Q-5: Where can I get a precompiled x11vnc binary for my Operating
System?
- Hopefully the [295]build steps above and [296]FAQ provide enough info
+ Hopefully the [297]build steps above and [298]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:
- Debian: (.deb) [297]http://packages.debian.org/x11vnc
-
- Slackware: (.tgz) [298]http://www.linuxpackages.net/ Redhat/Fedora:
- (.rpm) [299]http://dag.wieers.com/packages/x11vnc/
- [300]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm)
- [301]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
- [302]http://www.sunfreeware.com/ FreeBSD: (.tbz)
- [303]http://www.freebsd.org/ [304]http://www.freshports.org/net/x11vnc
- OpenBSD: (.tgz) [305]http://www.openbsd.org/ NetBSD: (src)
- [306]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb)
- [307]http://mike.saunby.googlepages.com/x11vncfornokia7702 Sharp
- Zaurus [308]http://www.pdaxrom.org/ and [309]http://www.focv.com/
+ Debian: (.deb) [299]http://packages.debian.org/x11vnc
+
+ Slackware: (.tgz) [300]http://www.linuxpackages.net/ Redhat/Fedora:
+ (.rpm) [301]http://dag.wieers.com/packages/x11vnc/
+ [302]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm)
+ [303]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg)
+ [304]http://www.sunfreeware.com/ FreeBSD: (.tbz)
+ [305]http://www.freebsd.org/ [306]http://www.freshports.org/net/x11vnc
+ OpenBSD: (.tgz) [307]http://www.openbsd.org/ NetBSD: (src)
+ [308]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb)
+ [309]http://mike.saunby.googlepages.com/x11vncfornokia7702 Sharp
+ Zaurus [310]http://www.pdaxrom.org/ and [311]http://www.focv.com/
If the above binaries don't work and building x11vnc on your OS fails
- (and all else fails!) you can try one of [310]my collection of
+ (and all else fails!) you can try one of [312]my collection of
binaries for various OS's and x11vnc releases.
As a general note, the x11vnc program is simple enough you don't
@@ -1722,7 +1727,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 [311]-httpdir option. E.g.:
+ tarball and point x11vnc to it via the [313]-httpdir option. E.g.:
x11vnc -httpdir /path/to/x11vnc-0.8.3/classes/ssl ...
@@ -1731,11 +1736,11 @@ typedef unsigned int in_addr_t;
To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
try here:
- * [312]http://www.tightvnc.com/download.html
- * [313]http://www.realvnc.com/download-free.html
- * [314]http://sourceforge.net/projects/cotvnc/
- * [315]http://www.ultravnc.com/
- * [316]Our Enhanced TightVNC Viewer (ssvnc)
+ * [314]http://www.tightvnc.com/download.html
+ * [315]http://www.realvnc.com/download-free.html
+ * [316]http://sourceforge.net/projects/cotvnc/
+ * [317]http://www.ultravnc.com/
+ * [318]Our Enhanced TightVNC Viewer (ssvnc)
Q-7: How can I see all of x11vnc's command line options and
@@ -1743,7 +1748,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
- [317]here as well. Yes, x11vnc does have a lot of options, doesn't
+ [319]here as well. Yes, x11vnc does have a lot of options, doesn't
it...
@@ -1775,10 +1780,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 [318]-gui option for more info. Examples: "x11vnc
+ for testing. See the [320]-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 "[319]-gui tray" system tray mode.
+ also a "[321]-gui tray" system tray mode.
Q-9: How can I get the GUI to run in the System Tray, or at least be a
@@ -1813,7 +1818,7 @@ display :0
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 "[320]-N" option will try to match the VNC display number to the X
+ The "[322]-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)).
@@ -1821,11 +1826,11 @@ display :0
Q-11: Can I make x11vnc more quiet and also go into the background
after starting up?
- Use the [321]-q and [322]-bg options, respectively. (also: -quiet is
+ Use the [323]-q and [324]-bg options, respectively. (also: -quiet is
an alias for -q)
Note that under -bg the stderr messages will be lost unless you use
- the "[323]-o logfile" option.
+ the "[325]-o logfile" option.
Q-12: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
@@ -1846,7 +1851,7 @@ display :0
There are some options. They are enabled by adding something like
-Dxxxx=1 to the CPPFLAGS environment variable before running configure
- (see the [324]build notes for general background).
+ (see the [326]build notes for general background).
/*
* Mar/2006
* Build-time customization via CPPFLAGS.
@@ -1917,21 +1922,21 @@ display :0
dual-screen mode to pass the keystrokes and mouse motions to the X11
display?
- Yes, for best response start up x11vnc with the "[325]-nofb" option
+ Yes, for best response start up x11vnc with the "[327]-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 [326]x2vnc, however you would
+ This will also work X11 to X11 using [328]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:
- * [327]Original Win2VNC
- * [328]Enhanced Win2VNC and [329]sourceforge link
- * [330]x2vnc
- * [331]x2x also [332]here
- * [333]zvnc (MorphOS)
+ * [329]Original Win2VNC
+ * [330]Enhanced Win2VNC and [331]sourceforge link
+ * [332]x2vnc
+ * [333]x2x also [334]here
+ * [335]zvnc (MorphOS)
All of them will work with x11vnc (except x2x where it is not needed).
@@ -1951,7 +1956,7 @@ display :0
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 [334]-visual option to allow you to force the framebuffer
+ has the [336]-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:
@@ -1965,7 +1970,7 @@ display :0
and keyboard input to it from Windows and X11 machines via Win2VNC and
x2vnc, respectively?
- Yes, as of Nov/2006 [335]you can. There may be a trick or two you'll
+ Yes, as of Nov/2006 [337]you can. There may be a trick or two you'll
need to do to get the Clipboard exchange between the machines to work.
@@ -1976,7 +1981,7 @@ display :0
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 [336]-flashcmap option to have x11vnc watch for changes in the
+ Use the [338]-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
@@ -1985,13 +1990,13 @@ display :0
example of this. Consider reconfiguring the system to 16 bpp or depth
24 TrueColor if at all possible.
- Also note the option [337]-8to24 (Jan/2006) can often remove the need
+ Also note the option [339]-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 the [338]-notruecolor option has corrected colors
+ In some rare cases the [340]-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.
@@ -2002,13 +2007,13 @@ display :0
different color depths: e.g. there are both depth 8 and 24 visuals
available at the same time.
- You may want to review the [339]previous question regarding 8 bpp
+ You may want to review the [341]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC and SGI), the [340]-overlay option
+ On some hardware (Sun/SPARC and SGI), the [342]-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
- [341]-8to24 option may help (also discussed below).
+ [343]-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
@@ -2044,7 +2049,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 [342]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+ use the [344]-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
@@ -2069,7 +2074,7 @@ TrueColor defdepth 24
Xsun, e.g. in your /etc/dt/config/Xservers file).
- The -8to24 mode: The [343]-8to24 x11vnc option (Jan/2006) is a kludge
+ The -8to24 mode: The [345]-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
@@ -2083,11 +2088,11 @@ TrueColor defdepth 24
32bpp view is exported via VNC.
Even on pure 8bpp displays it can be used as an alternative to
- [344]-flashcmap to avoid color flashing completely.
+ [346]-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: [345]-fixscreen V=3.0 to
+ row, or by using something like: [347]-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.
@@ -2100,23 +2105,23 @@ 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 [346]-8to24 help description for information on
+ speedup. See the [348]-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 [347]-id option to
+ possible workaround in this case is to use the [349]-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 [348]-8to24 method
+ for x11vnc to be able to do so in real time. The [350]-8to24 method
does this approximately and is somewhat usable. Fortunately the
- [349]-overlay option works for Solaris machines with overlay visuals
+ [351]-overlay option works for Solaris machines with overlay visuals
where most of this problem occurs.
@@ -2127,9 +2132,9 @@ TrueColor defdepth 24
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 [350]color problems.
+ debugging x11vnc [352]color problems.
- Also, as of Dec/2004 you can use "[351]-id pick" to have x11vnc run
+ Also, as of Dec/2004 you can use "[353]-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.
@@ -2147,7 +2152,7 @@ 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 [352]-sid windowid option ("shifted" windowid).
+ polling, try the [354]-sid windowid option ("shifted" windowid).
Q-21: My X display is depth 24 at 24bpp (instead of the normal depth
@@ -2182,7 +2187,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 [353]-24to32 option to have
+ Update: as of Apr/2006 you can use the [355]-24to32 option to have
x11vnc dynamically transform the 24bpp pixel data to 32bpp. This extra
transformation could slow things down further however.
@@ -2201,15 +2206,15 @@ 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 [354]-display option to point the display to that of
+ machine. Use the [356]-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 [355]-noshm option (this enables the polling
+ and finally supply the [357]-noshm option (this enables the polling
over the network).
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 [356]-flipbyteorder if the
+ on the polling rate. You may also need [358]-flipbyteorder if the
colors get messed up due to endian byte order differences.
Q-23: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct
@@ -2233,7 +2238,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
- [357]-auth option to point to the correct file). Other options include
+ [359]-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 -
@@ -2245,7 +2250,7 @@ TrueColor defdepth 24
details.
If the display name in the cookie file needs to be changed between the
- two hosts, see [358]this note on the "xauth add ..." command.
+ two hosts, see [360]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
@@ -2259,7 +2264,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 [359]poll
+ Not recommended, but as a last resort, you could have x11vnc [361]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...)
@@ -2288,13 +2293,13 @@ TrueColor defdepth 24
Q-24: I'm having trouble using x11vnc with my Sun Ray session.
- The [360]Sun Ray technology is a bit like "VNC done in hardware" (the
+ The [362]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 [361]this discussion of Sun Ray issues for
+ "Soft Ray". Please see [363]this discussion of Sun Ray issues for
solutions to problems.
[Remote Control]
@@ -2302,18 +2307,18 @@ TrueColor defdepth 24
Q-25: 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
- amount of things on the fly: see the [362]-remote and [363]-query
+ amount of things on the fly: see the [364]-remote and [365]-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 [364]-forever option has not been supplied, x11vnc will
+ If the [366]-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 [365]-bg option
+ If you have not put x11vnc in the background via the [367]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it.
@@ -2323,15 +2328,15 @@ 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 [366]-clear_mods
- option and [367]-clear_keys option can be used to release pressed keys
+ by tapping Ctrl, Shift, and Alt. Alternatively, the [368]-clear_mods
+ option and [369]-clear_keys option can be used to release pressed keys
at startup and exit.
Q-26: Can I change settings in x11vnc without having to restart it?
Can I remote control it?
- Look at the [368]-remote (same as -R) and [369]-query (same as -Q)
+ Look at the [370]-remote (same as -R) and [371]-query (same as -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 modtweak",
@@ -2342,7 +2347,7 @@ TrueColor defdepth 24
correctly for communication to be possible.
There is also a simple Tcl/Tk gui based on this remote control
- mechanism. See the [370]-gui option for more info. You will need to
+ mechanism. See the [372]-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 icon window:
"-gui icon".
@@ -2357,12 +2362,12 @@ TrueColor defdepth 24
vncpasswd(1) program from those packages.
As of Jun/2004 x11vnc supports the -storepasswd "pass" "file"
- [371]option, which is the same functionality of storepasswd. Be sure
+ [373]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: "[372]-rfbauth
+ You then use the password via the x11vnc option: "[374]-rfbauth
$HOME/myvncpasswd"
As of Jan/2006 if you do not supply any arguments:
@@ -2374,11 +2379,11 @@ TrueColor defdepth 24
~/.mypass", the password you are prompted for will be stored in that
file.
- x11vnc also has the [373]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [375]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
- You can use the [374]-usepw option to automatically use any password
+ You can use the [376]-usepw option to automatically use any password
file you have in ~/.vnc/passwd or ~/.vnc/passwdfile (the latter is
used with the -passwdfile option).
@@ -2410,14 +2415,14 @@ TrueColor defdepth 24
Q-29: 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 [375]-viewpasswd option to supply the
- view-only password. Note the full-access password option [376]-passwd
+ Yes, as of May/2004 there is the [377]-viewpasswd option to supply the
+ view-only password. Note the full-access password option [378]-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
- [377]-passwdfile option to specify a file containing plain text
+ [379]-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
@@ -2425,7 +2430,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 [378]-rfbauth
+ View-only passwords currently do not work for the [380]-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
@@ -2438,7 +2443,7 @@ TrueColor defdepth 24
Q-30: Can I have as many full-access and view-only passwords as I
like?
- Yes, as of Jan/2006 in the libvncserver CVS the [379]-passwdfile
+ Yes, as of Jan/2006 in the libvncserver CVS the [381]-passwdfile
option has been extended to handle as many passwords as you like. You
put the view-only passwords after a line __BEGIN_VIEWONLY__.
@@ -2448,7 +2453,7 @@ TrueColor defdepth 24
Q-31: 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 [380]-unixpw option that does
+ Update: as of Feb/2006 x11vnc has the [382]-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
@@ -2458,7 +2463,7 @@ TrueColor defdepth 24
A list of allowed Unix usernames may also be supplied along with
per-user settings.
- There is also the [381]-unixpw_nis option for non-shadow-password
+ There is also the [383]-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
@@ -2467,11 +2472,11 @@ TrueColor defdepth 24
shadow(5).
Two settings are enforced in the -unixpw and -unixpw_nis modes to
- provide extra security: the 1) [382]-localhost and 2) [383]-stunnel or
- [384]-ssl options. Without these one might send the Unix username and
+ provide extra security: the 1) [384]-localhost and 2) [385]-stunnel or
+ [386]-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 [385]-ssl (the constraint is automatically relaxed if
+ stunnel or [387]-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).
@@ -2490,13 +2495,13 @@ TrueColor defdepth 24
approximate at best.
One approximate method involves starting x11vnc with the
- [386]-localhost option. This basically requires the viewer user to log
+ [388]-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 [387]elsewhere on this page. [388]stunnel does this as well.
+ mentioned [389]elsewhere on this page. [390]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
@@ -2507,7 +2512,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 [389]-accept option that runs a program to examine the connection
+ the [391]-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
@@ -2543,7 +2548,7 @@ exit 1 # reject it
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 [390]-accept where an external program may be run to decide if a
+ the [392]-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,
@@ -2551,26 +2556,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:
- * [391]-unixpw_cmd command
- * [392]-passwdfile cmd:command
- * [393]-passwdfile custom:command
+ * [393]-unixpw_cmd command
+ * [394]-passwdfile cmd:command
+ * [395]-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 [394]-unixpw_cmd the normal [395]-unixpw Login: and Password:
+ For [396]-unixpw_cmd the normal [397]-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 "[396]-passwdfile cmd:command" the command is run and it returns a
- password list (like a password file, see the [397]-passwdfile
+ For "[398]-passwdfile cmd:command" the command is run and it returns a
+ password list (like a password file, see the [399]-passwdfile
read:filename mode). Perhaps a dynamic, one-time password is retrieved
from a server this way.
- For "[398]-passwdfile custom:command" one gets complete control over
+ For "[400]-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
@@ -2584,7 +2589,7 @@ exit 1 # reject it
it is rejected.
In all cases the "RFB_*" enviornment variables are set as under
- [399]-accept. These variables can provide useful information for the
+ [401]-accept. These variables can provide useful information for the
externally supplied program to use.
@@ -2594,15 +2599,15 @@ exit 1 # reject it
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 [400]-forever option (aka -many) to have
+ periods of time. Use the [402]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [401]-shared option to have x11vnc allow multiple clients to
+ Use the [403]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([402]see
- above), stunnel, [403]-ssl, or a VPN to authenticate and encrypt the
+ Recommended additional safety measures include using ssh ([404]see
+ above), stunnel, [405]-ssl, or a VPN to authenticate and encrypt the
viewer connections or to at least use the -rfbauth passwd-file
- [404]option to use VNC password protection (or [405]-passwdfile) It is
+ [406]option to use VNC password protection (or [407]-passwdfile) It is
up to YOU to apply these security measures, they will not be done for
you automatically.
@@ -2610,7 +2615,7 @@ exit 1 # reject it
Q-34: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [406]-allow and [407]-localhost options to limit
+ Yes, look at the [408]-allow and [409]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -2622,7 +2627,7 @@ 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
- [408](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [410](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
@@ -2642,7 +2647,7 @@ exit 1 # reject it
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [409]inetd you do not need to build
+ Note that if you run x11vnc out of [411]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.
@@ -2651,15 +2656,15 @@ exit 1 # reject it
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 "[410]-listen ipaddr" option that enables
+ As of Mar/2005 there is the "[412]-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
- "[411]-allow host1,..." option to allow only specific hosts in.
+ "[413]-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 [412]-localhost now implies "-listen localhost" since that
+ The option [414]-localhost now implies "-listen localhost" since that
is what most people expect it to do.
@@ -2667,7 +2672,7 @@ exit 1 # reject it
interface, how I can occasionally allow in a non-localhost via the -R
allowonce remote control command?
- To do this specify "[413]-allow localhost". Unlike [414]-localhost
+ To do this specify "[415]-allow localhost". Unlike [416]-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
@@ -2678,7 +2683,7 @@ exit 1 # reject it
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [415]-input option allows you to do this. "K",
+ As of Feb/2005, the [417]-input option allows you to do this. "K",
"M", "B", and "C" stand for Keystroke, Mouse-motion, Button-clicks,
and Clipboard, respectively. The setting: "-input M" makes attached
viewers only able to move the mouse. "-input KMBC,M" lets normal
@@ -2693,7 +2698,7 @@ exit 1 # reject it
some clients view-only? How about running an arbitrary program to make
the decisions?
- Yes, look at the "[416]-accept command" option, it allows you to
+ Yes, look at the "[418]-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 the client is accepted, otherwise the
@@ -2712,7 +2717,7 @@ exit 1 # reject it
own simple popup window. To accept the 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 [417]-viewonly option has been
+ mouse on the "View" button. If the [419]-viewonly option has been
supplied, the "View" action will not be present: the whole display is
view only in that case.
@@ -2728,7 +2733,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 [418]ftp://ftp.x.org/
+ is available at [420]ftp://ftp.x.org/
To include view-only decisions for the external commands, prefix the
command something like this: "yes:0,no:*,view:3 mycommand ..." This
@@ -2767,7 +2772,7 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [419]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [421]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.
@@ -2776,13 +2781,13 @@ 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 "[420]-gone
+ To run a command when a client disconnects, use the "[422]-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 "[421]-afteraccept command" option will run the
+ As of Jan/2006 the "[423]-afteraccept command" option will run the
command only after the VNC client has been accepted and authenticated.
Like -gone the return code is not interprted. RFB_MODE will be
"afteraccept").
@@ -2792,7 +2797,7 @@ exit 1
display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- As of Feb/2005 x11vnc has the [422]-users option that allows things
+ As of Feb/2005 x11vnc has the [424]-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.
@@ -2817,7 +2822,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 [423]blockdpy.c The idea behind it is simple (but
+ source for it is [425]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
@@ -2833,8 +2838,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 [424]-accept option and told
- to exit via the [425]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [426]-accept option and told
+ to exit via the [427]-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:
@@ -2843,17 +2848,17 @@ exit 1
but please read the top of the file.
Update: As of Feb/2007 there is some builtin support for this:
- [426]-forcedpms and [427]-clientdpms however, they are probably less
+ [428]-forcedpms and [429]-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 [428]-grabkbd, [429]-grabptr, and [430]-grabalways options.
+ also the [430]-grabkbd, [431]-grabptr, and [432]-grabalways options.
Q-42: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [431]-gone option under CDE to run a
+ Yes, a user mentions he uses the [433]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -2862,7 +2867,7 @@ exit 1
x11vnc -display :0 -forever -gone 'kdesktop_lock'
x11vnc -display :0 -forever -gone 'xlock &'
- Here is a scheme using the [432]-afteraccept option (in version 0.7.3)
+ Here is a scheme using the [434]-afteraccept option (in version 0.7.3)
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
@@ -2893,21 +2898,21 @@ fi
Q-43: 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 [433]how to tunnel VNC via
+ See the description earlier on this page on [435]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 [434]Enhanced TightVNC Viewer (ssvnc) page where much of
+ See also the [436]Enhanced TightVNC Viewer (ssvnc) page where much of
this is now automated.
Q-44: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [435]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [437]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
@@ -2928,11 +2933,11 @@ fi
:0 (plus other cmdline options) in the 'Remote command' Putty setting
under 'Connections/SSH'.
- See also the [436]Enhanced TightVNC Viewer (ssvnc) page where much of
+ See also the [438]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 [437]-localhost
- and [438]-rfbauth/[439]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [439]-localhost
+ and [440]-rfbauth/[441]-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
@@ -2940,11 +2945,11 @@ fi
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 [440]chaining ssh's.
+ automated by [442]chaining ssh's.
- As discussed [441]above another option is to first start the VNC
+ As discussed [443]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[442]-connect localhost" option to establish the reverse connection.
+ "[444]-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).
@@ -2954,7 +2959,7 @@ fi
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 [443]stunnel (also [444]stunnel.mirt.net)
+ IPSEC. SSL tunnels such as [445]stunnel (also [446]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
@@ -2962,12 +2967,12 @@ fi
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 [445]-ssl,
- [446]-stunnel, and [447]-sslverify to provide integrated SSL schemes.
- They are discussed [448]in the Next FAQ (you may want to skip to it
+ Update: As of Feb/2006 x11vnc has the options [447]-ssl,
+ [448]-stunnel, and [449]-sslverify to provide integrated SSL schemes.
+ They are discussed [450]in the Next FAQ (you may want to skip to it
now).
- Here are some basic examples using [449]stunnel but the general idea
+ Here are some basic examples using [451]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
@@ -2991,7 +2996,7 @@ fi
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 [450]signed by
+ stunnel is built. One can also create certificates [452]signed by
Certificate Authorities or self-signed if desired using the x11vnc
utilities described there.
@@ -3005,7 +3010,7 @@ fi
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 [451]ss_vncviewer script can automate
+ That's it. (note that the [453]ss_vncviewer script can automate
this.)
Be sure to use a VNC password because unlike ssh by default the
@@ -3013,13 +3018,13 @@ fi
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 [452]the key management section for details.
+ and also [454]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 [453]article The article also
+ found at the stunnel site and in this [455]article The article also
shows the detailed steps to set up all the authentication
- certificates. (for both server and clients, see also the [454]x11vnc
+ certificates. (for both server and clients, see also the [456]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
@@ -3040,7 +3045,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 [455]-inetd mode:
+ start up x11vnc in [457]-inetd mode:
stunnel -p /path/to/stunnel.pem -P none -d 5900 -l ./x11vnc_sh
Where the script x11vnc_sh starts up x11vnc:
@@ -3083,28 +3088,28 @@ connect = 5900
they probably wouldn't work since the SSL negotiation is likely
embedded in the VNC protocol unlike our case where it is external.
- Note: as of Mar/2006 libvncserver/x11vnc provides a [456]SSL-enabled
- Java applet that can be served up via the [457]-httpdir or [458]-http
- options when [459]-ssl is enabled. It will also be served via HTTPS
+ Note: as of Mar/2006 libvncserver/x11vnc provides a [458]SSL-enabled
+ Java applet that can be served up via the [459]-httpdir or [460]-http
+ options when [461]-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 [460]-https option.
+ the [462]-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 [461]-stunnel or [462]-ssl option on the server side it works well
- and is convenient. Here is a simple script [463]ss_vncviewer that
+ the [463]-stunnel or [464]-ssl option on the server side it works well
+ and is convenient. Here is a simple script [465]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 [464]Enhanced TightVNC Viewer
+ Update Jul/2006: we now provide an [466]Enhanced TightVNC Viewer
(ssvnc) package that starts up STUNNEL automatically along with some
other features. All binaries are provided in the package.
Q-46: Does x11vnc have built-in SSL tunneling?
- You can read about non-built-in methods [465]in the Previous FAQ
+ You can read about non-built-in methods [467]in the Previous FAQ
SSL tunnels provide an encrypted channel without the need for Unix
users, passwords, and key passphrases required for ssh (and at the
@@ -3115,14 +3120,14 @@ connect = 5900
Built-in SSL x11vnc options:
- As of Feb/2006 the x11vnc [466]-ssl and [467]-stunnel options automate
- the SSL tunnel creation on the x11vnc server side. An [468]SSL-enabled
+ As of Feb/2006 the x11vnc [468]-ssl and [469]-stunnel options automate
+ the SSL tunnel creation on the x11vnc server side. An [470]SSL-enabled
Java Viewer applet is also provided that can be served via HTTP or
HTTPS to automate SSL on the client side.
- The [469]-ssl mode uses the [470]www.openssl.org library if available
- at build time. The [471]-stunnel mode requires the
- [472]www.stunnel.org command stunnel(8) to be installed on the system.
+ The [471]-ssl mode uses the [472]www.openssl.org library if available
+ at build time. The [473]-stunnel mode requires the
+ [474]www.stunnel.org command stunnel(8) to be installed on the system.
Both modes require an SSL certificate and key (i.e. .pem file). These
are usually created via the openssl(1) (in fact in for options "-ssl"
@@ -3174,12 +3179,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 [473]x11vnc Key Management for some utilities
+ See the discussion on [475]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 [474]ss_vncviewer provides an example on unix
+ The wrapper script [476]ss_vncviewer provides an example on unix
(-verify option).
Here are some notes on the simpler default (non-CA) operation. To have
@@ -3195,7 +3200,7 @@ connect = 5900
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
- [475]here), then Man-In-The-Middle-Attacks are prevented. Otherwise,
+ [477]here), then Man-In-The-Middle-Attacks are prevented. Otherwise,
the SSL encryption only provides protection against passive network
traffic "sniffing". Nowadays, most people seem mostly concerned about
only the latter (and the default x11vnc SSL modes protect against it.)
@@ -3220,7 +3225,7 @@ connect = 5900
including using https to download it into the browser and connect to
x11vnc.
- See the [476]next FAQ for SSL enabled VNC Viewers.
+ See the [478]next FAQ for SSL enabled VNC Viewers.
Q-47: How do I use VNC Viewers with built-in SSL tunneling?
@@ -3231,9 +3236,9 @@ connect = 5900
The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package
supports only SSL based connections by default (set the applet
parameter disableSSL=yes in index.vnc to override). As mentioned above
- the [477]-httpdir can be used to specify the path to .../classes/ssl.
+ the [479]-httpdir can be used to specify the path to .../classes/ssl.
A typical location might be /usr/local/share/x11vnc/classes/ssl. Or
- [478]-http can be used to try to have it find the directory
+ [480]-http can be used to try to have it find the directory
automatically.
The Java viewer uses SSL to communicate securely with x11vnc. Note
@@ -3258,7 +3263,7 @@ connect = 5900
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 and you still want to serve the Java applet via https, use
- the [479]-https option to get an additional port dedicated to https
+ the [481]-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:
@@ -3271,7 +3276,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
- [480]proxy scheme to enter a firewall or otherwise have rules applied
+ [482]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".)
@@ -3295,11 +3300,11 @@ connect = 5900
connection is VNC instead of the HTTPS it actually is (but since you
have paused too long at the dialog the GET request comes too late).
Often hitting Reload and going through the dialogs more quickly will
- let you connect. Use the [481]-https option if you want a dedicated
+ let you connect. Use the [483]-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 [482]This Page.
+ connection with the Java Applet see [484]This Page.
Notes on the VNC Viewer ss_vncviewer wrapper script:
@@ -3307,10 +3312,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 the x11vnc
- package. The basic ideas of doing this were discussed [483]for
+ package. The basic ideas of doing this were discussed [485]for
external tunnel utilities here.
- The [484]ss_vncviewer script provided with x11vnc can set up the
+ The [486]ss_vncviewer script provided with x11vnc 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 Debian based system you will need to
@@ -3342,14 +3347,14 @@ 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 [485]this page for more information on
+ separate the two by commas. See [487]this page for more information on
how Web proxies come into play.
- If one uses a Certificate Authority (CA) scheme described [486]here,
+ If one uses a Certificate Authority (CA) scheme described [488]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 [487]Enhanced TightVNC Viewer
+ Update Jul/2006: we now provide an [489]Enhanced TightVNC Viewer
(ssvnc) package that starts up STUNNEL automatically along with some
other features. All binaries are provided in the package.
@@ -3385,7 +3390,7 @@ connect = 5900
(instead of the unsigned one in https://yourmachine.com:5900/ that
gives the default index.vnc)
- Note that the [488]ss_vncviewer stunnel wrapper script can use Web
+ Note that the [490]ss_vncviewer stunnel wrapper script can use Web
proxies as well.
Proxies that limit CONNECT to ports 443 and 563:
@@ -3414,7 +3419,7 @@ 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. To use the GET [489]trick discussed above, do:
+ parameters in the URL. To use the GET [491]trick discussed above, do:
https://yourmachine.com/proxy.vnc?PORT=443&GET=1
@@ -3422,7 +3427,7 @@ connect = 5900
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 [490]here. This provides a clean alternative to the
+ It is discussed [492]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.
@@ -3430,7 +3435,7 @@ connect = 5900
Q-50: Can I create and use my own SSL Certificate Authority (CA) with
x11vnc?
- Yes, see [491]this page for how to do this and the utility commands
+ Yes, see [493]this page for how to do this and the utility commands
x11vnc provides to create and manage many types of certificates and
private keys.
@@ -3449,14 +3454,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 [492]FAQ on x11vnc
+ * Use the description under "Continuously" in the [494]FAQ on x11vnc
and Display Managers
- * Use the description in the [493]FAQ on x11vnc and inetd(8)
- * Use the description in the [494]FAQ on Unix user logins and
+ * Use the description in the [495]FAQ on x11vnc and inetd(8)
+ * Use the description in the [496]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 [495]x11vnc_loop rc.local hack
+ * Although less reliable, see the [497]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -3478,7 +3483,7 @@ 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
- [496]this link.
+ [498]this link.
Q-52: How can I use x11vnc to connect to an X login screen like xdm,
@@ -3493,7 +3498,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 [497]-auth option sets the XAUTHORITY variable for you).
+ (the [499]-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
@@ -3518,7 +3523,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
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
- [498]the example at the end of this FAQ). Then restart dtlogin, e.g.:
+ [500]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.
Continuously. Have x11vnc reattach each time the X server is
@@ -3566,7 +3571,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 [499]-N) to avoid autoselecting one if 5900 is already
+ 5900" (or [501]-N) to avoid autoselecting one if 5900 is already
taken.
_________________________________________________________________
@@ -3582,7 +3587,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 [500]full details
+ killed immediately after the user logs in. Here are [502]full details
on how to configure gdm
_________________________________________________________________
@@ -3624,14 +3629,14 @@ 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: [501]x11vnc_loop It will need some local
+ file like rc.local: [503]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 [502]-loop
+ described above is greatly preferred. There is also the [504]-loop
option that does something similar.
If the machine is a traditional Xterminal you may want to read
- [503]this FAQ.
+ [505]this FAQ.
Q-53: Can I run x11vnc out of inetd(8)? How about xinetd(8)?
@@ -3641,7 +3646,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh
- where the shell script /usr/local/bin/x11vnc_sh uses the [504]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [506]-inetd
option and looks something like (you'll need to customize to your
settings).
#!/bin/sh
@@ -3654,7 +3659,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 [505]-quiet) option: "/usr/local/bin/x11vnc -q
+ specify the -q (aka [507]-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
@@ -3662,12 +3667,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 [506]-auth to point to the
+ Note also the need to set XAUTHORITY via [508]-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
- [507]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY
+ [509]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
@@ -3734,9 +3739,9 @@ service x11vncservice
it automatically?
Yes, as of Feb/2007 x11vnc supports mDNS / Zeroconf advertising of its
- service via the Avahi client library. Use the option [508]-avahi (same
- as [509]-mdns) to enable it. Depending on your setup you may need to
- install [510]Avahi (including the development packages), enable the
+ service via the Avahi client library. Use the option [510]-avahi (same
+ as [511]-mdns) to enable it. Depending on your setup you may need to
+ install [512]Avahi (including the development packages), enable the
server: avahi-daemon and avahi-dnsconfd, and possibly open up UDP port
5353 on your firewall.
@@ -3761,23 +3766,23 @@ service x11vncservice
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 [511]inetd(8) using the [512]-unixpw
- and [513]-display WAIT options. The reason inetd(8) makes this easier
+ The easiest way to do this is via [513]inetd(8) using the [514]-unixpw
+ and [515]-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 [514]this example and also the [515]-loopbg option).
+ x11vnc's (see [516]this example and also the [517]-loopbg option).
Also with inetd(8) users always connect to a fixed VNC display, say
machine:0, and do not need to memorize a special VNC display number
just for their personal use, etc.
- Update: Use the [516]-find, [517]-create, [518]-svc, and [519]-xdmsvc
+ Update: Use the [518]-find, [519]-create, [520]-svc, and [521]-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 [520]-display WAIT option makes x11vnc wait until a VNC viewer is
+ The [522]-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
@@ -3818,7 +3823,7 @@ nt $2}'`
exit 0
A default script somewhat like the above is used under "-display
- WAIT:cmd=FINDDISPLAY" (same as [521]-find) (use
+ WAIT:cmd=FINDDISPLAY" (same as [523]-find) (use
"WAIT:cmd=FINDDISPLAY-print" to print out the 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 xauth data
@@ -3830,10 +3835,10 @@ nt $2}'`
Or if you only know the X server process ID and suspect a chvt will be
needed append ",XPID=n".
- Tip: Note that the [522]-find option is an alias for "-display
+ Tip: Note that the [524]-find option is an alias for "-display
WAIT:cmd=FINDDISPLAY".
- The [523]-unixpw option allows [524]UNIX password logins. It
+ The [525]-unixpw option allows [526]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
@@ -3847,16 +3852,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 [525]-svc alias).
+ options. (see also the [527]-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 "[526]-users unixpw=" option.
+ logs in due to the "[528]-users unixpw=" option.
- Note that [527]SSL is required for this mode because otherwise the
+ Note that [529]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
@@ -3864,17 +3869,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 [528]-localhost
+ If you really want to disable the SSL or SSH [530]-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 [529]-unixpw documentation.
+ read the [531]-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 "[530]-users =fred" option will cause x11vnc to switch to user
+ The "[532]-users =fred" option will cause x11vnc to switch to user
fred and then find his X display.
@@ -3883,7 +3888,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 [531]Xdummy and if that is not
+ virtual (non-hardware) X servers: first [533]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.
@@ -3893,19 +3898,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. [532]ss_vncviewer) access and also Java Web browers access via:
+ (e.g. [534]ss_vncviewer) access and also Java Web browers access via:
https://hostname:5900/.
- Tip: Note that the [533]-create option is an alias for "-display
+ Tip: Note that the [535]-create option is an alias for "-display
WAIT:cmd=FINDCREATEDISPLAY-Xvfb".
- Tip: Note that [534]-svc is a short hand for the long "-ssl SAVE
+ Tip: Note that [536]-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 [535]-display WAIT for
+ after his username (following a ":" see [537]-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.
@@ -3936,7 +3941,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 [536]need to be run to switch to the correct Linux
+ chvt program may [538]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.
@@ -3963,7 +3968,7 @@ service x11vnc
will also typically block UDP (port 177 for XDMCP) by default
effectively limiting the UDP connections to localhost.
- Tip: Note that [537]-xdmsvc is a short hand for the long "-ssl SAVE
+ Tip: Note that [539]-xdmsvc is a short hand for the long "-ssl SAVE
-unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp"
part. E.g.:
service x11vnc
@@ -3997,15 +4002,15 @@ service x11vnc
Q-56: Can I have x11vnc restart itself after it terminates?
One could do this in a shell script, but now there is an option
- [538]-loop that makes it easier. Of course when x11vnc restarts it
+ [540]-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 [539]-loopbg to emulate inetd(8) to some degree,
+ One can also use the [541]-loopbg to emulate inetd(8) to some degree,
where each connected process runs in the background. It could be
- combined, say, with the [540]-svc option to provide simple terminal
+ combined, say, with the [542]-svc option to provide simple terminal
services without using inetd(8).
@@ -4013,7 +4018,7 @@ service x11vnc
web browser?
To have x11vnc serve up a Java VNC viewer applet to any web browsers
- that connect to it, run x11vnc with this [541]option:
+ that connect to it, run x11vnc with this [543]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -4032,7 +4037,7 @@ service x11vnc
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 [542]-http option will try to guess where the Java
+ As of May/2005 the [544]-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.
@@ -4048,7 +4053,7 @@ service x11vnc
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
- [543]-connect option. To connect immediately at x11vnc startup time
+ [545]-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 5500).
@@ -4056,7 +4061,7 @@ service x11vnc
file is checked periodically (about once a second) for new hosts to
connect to.
- The [544]-remote control option (aka -R) can also be used to do this
+ The [546]-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
@@ -4068,7 +4073,7 @@ x11vnc -display :0 -R connect:hostname.domain
starting x11vnc.
To use the vncconnect(1) program (from the core VNC package at
- www.realvnc.com) specify the [545]-vncconnect option to x11vnc (Note:
+ www.realvnc.com) specify the [547]-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 or do not want to get
@@ -4111,19 +4116,19 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
"screen scrape" it efficiently (more than, say, 100X faster than
normal video hardware).
- Update Nov/2006: See the [546]FINDCREATEDISPLAY discussion of the
- "[547]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or
+ Update Nov/2006: See the [548]FINDCREATEDISPLAY discussion of the
+ "[549]-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 [548]-find,
- [549]-create, [550]-svc, and [551]-xdmsvc aliases can also come in
+ (inetd(8) is a nice way to provide this service). The [550]-find,
+ [551]-create, [552]-svc, and [553]-xdmsvc aliases can also come in
handy here.
There are some annoyances WRT Xvfb though. The default keyboard
mapping seems to be very poor. One should run x11vnc with
- [552]-add_keysyms option to have keysyms added automatically. Also, to
+ [554]-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"
@@ -4135,7 +4140,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 [553]FINDCREATEDISPLAY
+ (note: these are applied automatically in the [555]FINDCREATEDISPLAY
mode). Perhaps the Xvfb options -xkbdb or -xkbmap could be used to get
a better default keyboard mapping.
@@ -4150,11 +4155,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) [554]switching even though it
+ Linux Virtual Console/Terminal (VC/VT) [556]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 [555]Xdummy that allows you to
+ Jul/2005 we have an LD_PRELOAD script [557]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
@@ -4186,7 +4191,7 @@ startx -- /path/to/Xdummy :1
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 [556]this FAQ) and access it from
+ display via x11vnc (e.g. see [558]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
@@ -4209,10 +4214,10 @@ startx -- /path/to/Xdummy :1
cards as it can hold to provide multiple simultaneous access or
testing on different kinds of video hardware.
- See also the [557]FINDCREATEDISPLAY discussion of the "[558]-display
+ See also the [559]FINDCREATEDISPLAY discussion of the "[560]-display
WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X
servers are started automatically for new users connecting. The
- [559]-find, [560]-create, [561]-svc, and [562]-xdmsvc aliases can also
+ [561]-find, [562]-create, [563]-svc, and [564]-xdmsvc aliases can also
come in handy here.
[Resource Usage and Performance]
@@ -4235,7 +4240,7 @@ startx -- /path/to/Xdummy :1
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 [563]shm_clear to list and prompt for removal
+ Here is a shell script [565]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,
@@ -4269,40 +4274,40 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [564]-onetile option (corresponds to only 3 shm segments used, and
+ [566]-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
- [565]-noshm option. Performance will be somewhat degraded but when
+ [567]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [566]earlier question discussing -noshm).
+ [568]earlier question discussing -noshm).
Q-62: How can I make x11vnc use less system resources?
- The [567]-nap (now on by default) and "[568]-wait n" (where n is the
+ The [569]-nap (now on by default) and "[570]-wait n" (where n is the
sleep between polls in milliseconds, the default is 30 or so) option
- are good places to start. Something like "[569]-sb 15" will cause
+ are good places to start. Something like "[571]-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
- will make x11vnc's screen polling less severe. Using the [570]-onetile
+ will make x11vnc's screen polling less severe. Using the [572]-onetile
option will use less memory and use fewer shared memory slots (add
- [571]-fs 1.0 for one less slot).
+ [573]-fs 1.0 for one less slot).
Q-63: How can I make x11vnc use MORE system resources?
- You can try [572]-threads and dial down the wait time (e.g. -wait 1)
- and possibly dial down [573]-defer as well. Note that if you try to
+ You can try [574]-threads and dial down the wait time (e.g. -wait 1)
+ and possibly dial down [575]-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 [574]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [576]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate.
@@ -4318,7 +4323,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
- [575]-solid [color] option to try to do this automatically.
+ [577]-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
@@ -4327,9 +4332,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 [576]-scrollcopyrect is active and
+ problem in x11vnc 0.7.2 if [578]-scrollcopyrect is active and
detecting scrolls for the application).
- * If the [577]-wireframe option is not available (earlier than
+ * If the [579]-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)
@@ -4352,7 +4357,7 @@ ied)
noticed.
VNC viewer parameters:
- * Use a [578]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer
+ * Use a [580]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
@@ -4374,37 +4379,37 @@ ied)
file.
x11vnc parameters:
- * Make sure the [579]-wireframe option is active (it should be on by
+ * Make sure the [581]-wireframe option is active (it should be on by
default) and you have Opaque Moves/Resizes Enabled in the window
manager.
- * Make sure the [580]-scrollcopyrect option is active (it should be
+ * Make sure the [582]-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
- [581]-solid
- * Specify [582]-speeds modem to force the wireframe and
+ [583]-solid
+ * Specify [584]-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 [583]-nodragging (no screen updates when dragging mouse,
+ drastic [585]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Set [584]-fs 1.0 (disables fullscreen updates)
- * Try increasing [585]-wait or [586]-defer (reduces the maximum
+ * Set [586]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [587]-wait or [588]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * Try the [587]-progressive pixelheight mode with the block
+ * Try the [589]-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 [588]-id (cuts
+ * If you just want to watch one (simple) window use [590]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [589]-nosel (disables all clipboard selection exchange)
- * Use [590]-nocursor and [591]-nocursorpos (repainting the remote
+ * Set [591]-nosel (disables all clipboard selection exchange)
+ * Use [592]-nocursor and [593]-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
- [592]-readtimeout n setting if it sometimes takes more than 20sec
+ [594]-readtimeout n setting if it sometimes takes more than 20sec
to paint the full screen, etc.
- * Do not use [593]-fixscreen to automatically refresh the whole
+ * Do not use [595]-fixscreen to automatically refresh the whole
screen, tap three Alt_L's then the screen has painting errors
(rare problem).
@@ -4473,7 +4478,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 [594]slow (e.g.
+ in main memory. So reading the fb is still painfully [596]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
@@ -4491,41 +4496,41 @@ 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 "[595]-xd_area A" option to adjust the size
+ skipped). You can use the "[597]-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 "[596]-xd_mem f" may also be of use in tuning the
- algorithm. To disable using DAMAGE entirely use "[597]-noxdamage".
+ The option "[598]-xd_mem f" may also be of use in tuning the
+ algorithm. To disable using DAMAGE entirely use "[599]-noxdamage".
Q-66: 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 "[598]-noxdamage" option.
+ he uses the "[600]-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.
- Update: see [599]this FAQ too.
+ Update: see [601]this FAQ too.
Q-67: 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 [600]slow hardware read rates from
+ This problem is primarily due to [602]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
- [601]-pointer_mode option for more info. The next bottleneck is
+ [603]-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
@@ -4535,26 +4540,26 @@ 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 "[602]-pointer_mode 1" option.
+ the "[604]-pointer_mode 1" option.
- Also added was the [603]-nodragging option that disables all screen
+ Also added was the [605]-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 [604]-pointer_mode n option was introduced. n=1 is
+ As of Dec/2004 the [606]-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 [605]-threads option can improve
+ Also, in some circumstances the [607]-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).
- As of Apr/2005 two new options (see the [606]wireframe FAQ and
- [607]scrollcopyrect FAQ below) provide schemes to sweep this problem
+ As of Apr/2005 two new options (see the [608]wireframe FAQ and
+ [609]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
@@ -4578,8 +4583,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 [608]slow video card
- read rates (see [609]here too). A displacement, even a small one, of a
+ intermediate steps. BTW the lurching is due to [610]slow video card
+ read rates (see [611]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.
@@ -4587,7 +4592,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 [610]-nowireframe option
+ with the problem. It can be disabled with the [612]-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
@@ -4632,13 +4637,13 @@ EndSection
* Maximum time to show a wireframe animation.
* Minimum time between sending wireframe outlines.
- See the [611]"-wireframe tweaks" option for more details. On a slow
+ See the [613]"-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
- [612]"-wirecopyrect mode" option. It is also on by default. This
+ [614]"-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
@@ -4686,7 +4691,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 [613]slow).
+ the hardware framebuffer is [615]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.
@@ -4713,10 +4718,10 @@ EndSection
the X server display: if one falls too far behind it could become a
mess...
- The initial implementation of [614]-scrollcopyrect option is useful in
+ The initial implementation of [616]-scrollcopyrect option is useful in
that it detects many scrolls and thus gives a much nicer working
- environment (especially when combined with the [615]-wireframe
- [616]-wirecopyrect [617]options, which are also on by default; and if
+ environment (especially when combined with the [617]-wireframe
+ [618]-wirecopyrect [619]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.
@@ -4749,10 +4754,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: [618]-fixscreen
+ also: [620]-fixscreen
* Some applications, notably OpenOffice, do XCopyArea scrolls in
weird ways that assume ancestor window clipping is taking place.
- See the [619]-scr_skip option for ways to tweak this on a
+ See the [621]-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
@@ -4769,7 +4774,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 [620]-scale option there will be a quick CopyRect
+ * When using the [622]-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
@@ -4782,7 +4787,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 [621]-noscrollcopyrect (or -noscr for short). If you find
+ with the [623]-noscrollcopyrect (or -noscr for short). If you find
some extremely bad and repeatable behavior for -scrollcopyrect please
report a bug.
@@ -4807,9 +4812,9 @@ EndSection
that pixel data is needed again it does not have to be retransmitted
over the network.
- As of Dec/2006 in the [622]0.8.5 development tarball there is an
+ As of Dec/2006 in the [624]0.8.5 development tarball there is an
experimental client-side caching implementation enabled by the
- "[623]-ncache n" option. In fact, during the test period at least it
+ "[625]-ncache n" option. In fact, during the test period at least it
is on by default with n set to 12. To disable it use "-noncache".
It is a simple scheme where a (very large) lower portion of the
@@ -4842,7 +4847,7 @@ EndSection
perhaps something else, maybe double buffering or other offscreen
rendering...).
- The Enhanced TightVNC Viewer Unix viewer has a nice [624]-ycrop option
+ The Enhanced TightVNC Viewer Unix viewer has a nice [626]-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
@@ -4872,7 +4877,7 @@ EndSection
an additional factor of 2 in memory use.
However, even in the smallest usage mode with n equal 2 and
- [625]-ncache_no_rootpixmap set (this requires only 2X additional
+ [627]-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.
@@ -4883,7 +4888,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 "[626]-ncache_cr". By specifying
+ Another option to experiment with is "[628]-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
@@ -4922,7 +4927,13 @@ Section "Device"
EndSection
No problems like this have been observed with Windows VNC Viewers:
- they all seem to keep their entire framebuffer in local memory.
+ they all seem to keep their entire framebuffer in local memory. Gotcha
+ for KDE krdc VNC Viewer: One user found that KDE's krdc viewer has
+ some sort of hardwired limit on the maximum size of the framebuffer
+ (64MB?). It fails quickly saying "The connection to the host has been
+ interrupted." The workaround for his 1280x1024 x11vnc-side display was
+ to run with "-ncache 10", i.e. a smaller value to be under the krdc
+ threshold.
@@ -4943,23 +4954,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 "[627]-cursor X" option that
+ A simple kludge is provided by the "[629]-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 "[628]-cursor some" option for
+ work for those cases. Also see the "[630]-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
- [629]-overlay option is supplied. See [630]this FAQ for more info.
+ [631]-overlay option is supplied. See [632]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
- [631]Solaris 10.
+ [633]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
@@ -4967,7 +4978,7 @@ 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. [632]Details can be found here.
+ hidden alpha channel data under 32bpp. [634]Details can be found here.
Q-72: When using XFIXES cursorshape mode, some of the cursors look
@@ -5000,17 +5011,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 "[633]-alphacut n" option lets
+ course!) some tunable parameters. The "[635]-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 "[634]-alphafrac f" option tries to correct individual
+ 240. The "[636]-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 [635]-alpharemove that is useful for
+ Finally, there is an option [637]-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
@@ -5036,10 +5047,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 [636]-nocursorshape x11vnc option. In this case the cursor is
+ with the [638]-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 [637]-noalphablend option to disable this
+ the x11vnc side. Use the [639]-noalphablend option to disable this
behavior (always approximate transparent cursors with opaque RGB
values).
@@ -5063,7 +5074,7 @@ 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 [638]Enhanced TightVNC Viewer (ssvnc)
+ This patch is applied to the [640]Enhanced TightVNC Viewer (ssvnc)
package we provide.
[Mouse Pointer]
@@ -5071,9 +5082,9 @@ EndSection
Q-74: 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 [639]tightvnc extension
+ This default takes advantage of a [641]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [640]-nocursor
+ the local VNC viewer. You may disable it with the [642]-nocursor
option to x11vnc if your viewer does not have this extension.
Note: as of Aug/2004 this should be fixed: the default for
@@ -5087,17 +5098,17 @@ EndSection
clients (i.e. passive viewers can see the mouse cursor being moved
around by another viewer)?
- Use the [641]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [643]-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 [642]-nocursorpos and [643]-nocursorshape.
+ is the default. See also [644]-nocursorpos and [645]-nocursorshape.
Q-76: 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: [644]-buttonmap
+ You can remap the mouse buttons via something like: [646]-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.
@@ -5105,7 +5116,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 [645]-debug_pointer option prints out much info for
+ Note that the [647]-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
@@ -5127,7 +5138,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 [646]-buttonmap but rather configuring the X server
+ consider not using [648]-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"').
@@ -5157,7 +5168,7 @@ EndSection
Q-77: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [647]-modtweak should help here. It is a mode that monitors
+ The option [649]-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.
@@ -5166,16 +5177,16 @@ 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 [648]this FAQ for more info). Without
+ not exist on the keyboard (see [650]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 [649]FAQ about the -xkb option for a more powerful method
+ Also see the [651]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
- [650]-debug_keyboard option prints out much info for every keystroke
+ [652]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
@@ -5187,9 +5198,9 @@ EndSection
(e.g. pc105 in the XF86Config file when it should be something else,
say pc104).
- Short Cut: Try the [651]-xkb or [652]-sloppy_keys options and see if
+ Short Cut: Try the [653]-xkb or [654]-sloppy_keys options and see if
that helps the situation. The discussion below is a bit outdated (e.g.
- [653]-modtweak is now the default) but it is useful reference for
+ [655]-modtweak is now the default) but it is useful reference for
various tricks and so is kept.
@@ -5232,17 +5243,17 @@ EndSection
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([654]-modtweak) is a mode that monitors the
+ settings. The former ([656]-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 ([655]-remap less-comma) is an immediate remapping of the
+ The latter ([657]-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 [656]FAQ about the -xkb option as a possible workaround
+ See also the [658]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [657]-debug_keyboard option prints out much info for
+ Note that the [659]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
@@ -5250,13 +5261,13 @@ EndSection
(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 [658]keymapping
+ the Shift key before releasing the "<". Because of a [660]keymapping
ambiguity the last event "< up" is interpreted as "," because that key
unshifted is the comma.
- This should not happen in [659]-xkb mode, because it works hard to
+ This should not happen in [661]-xkb mode, because it works hard to
resolve the ambiguities. If you do not want to use -xkb, try the
- option [660]-sloppy_keys to attempt a similar type of algorithm.
+ option [662]-sloppy_keys to attempt a similar type of algorithm.
Q-80: I'm using an "international" keyboard (e.g. German "de", or
@@ -5280,7 +5291,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 [661]-modtweak
+ This all worked fine with x11vnc running with the [663]-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
@@ -5297,7 +5308,7 @@ EndSection
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [662]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [664]-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
@@ -5305,7 +5316,7 @@ EndSection
debugging output (send it along with any problems you report).
Update: as of Jun/2005 x11vnc will try to automatically enable
- [663]-xkb if it appears that would be beneficial (e.g. if it sees any
+ [665]-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.
@@ -5320,7 +5331,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:
- [664]-skip_keycodes 93
+ [666]-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
@@ -5338,16 +5349,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 [665]-remap x11vnc option:
+ created using the [667]-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
- [666]-add_keysyms option in the next paragraph.
- Update: for convenience "[667]-remap DEAD" does many of these
+ [668]-add_keysyms option in the next paragraph.
+ Update: for convenience "[669]-remap DEAD" does many of these
mappings at once.
- * To complement the above workaround using the [668]-remap, an
- option [669]-add_keysyms was added. This option instructs x11vnc
+ * To complement the above workaround using the [670]-remap, an
+ option [671]-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
@@ -5366,7 +5377,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) [670]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [672]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side.
@@ -5390,7 +5401,7 @@ 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 [671]-norepeat (which has since Dec/2004 been
+ needed, or to use the [673]-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
@@ -5401,7 +5412,7 @@ EndSection
keystrokes!!
Are you using x11vnc to log in to an X session via display manager?
- (as described in [672]this FAQ) If so, x11vnc is starting before your
+ (as described in [674]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
@@ -5425,7 +5436,7 @@ EndSection
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 "[673]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[675]-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)).
@@ -5448,7 +5459,7 @@ 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 [674]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [676]-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.
@@ -5468,7 +5479,7 @@ EndSection
and similar triple mappings (with two in the AltGr/Mode_switch group)
of a keysum to a single keycode.
- Use the [675]-nomodtweak option as a workaround. You can also use
+ Use the [677]-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"
@@ -5482,7 +5493,7 @@ EndSection
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 [676]-remap
+ have x11vnc do the remapping. This can be done via the [678]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -5491,7 +5502,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:
- [677]-remap Super_R-Button2
+ [679]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -5510,10 +5521,10 @@ 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
- [678]-skip_lockkeys option should help to accomplish this. For finer
- grain control use something like: "[679]-remap Caps_Lock-None".
+ [680]-skip_lockkeys option should help to accomplish this. For finer
+ grain control use something like: "[681]-remap Caps_Lock-None".
- Also try the [680]-nomodtweak and [681]-capslock options.
+ Also try the [682]-nomodtweak and [683]-capslock options.
[Screen Related Issues and Features]
@@ -5536,7 +5547,7 @@ 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
- [682]this FAQ on x11vnc scaling.
+ [684]this FAQ on x11vnc scaling.
Q-89: Does x11vnc support server-side framebuffer scaling? (E.g. to
@@ -5544,7 +5555,7 @@ EndSection
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 "[683]-scale fraction" option. "fraction" can either be a
+ use the "[685]-scale fraction" option. "fraction" can either be a
floating point number (e.g. -scale 0.5) or the alternative m/n
fraction notation (e.g. -scale 3/4). Note that if fraction is greater
than one the display is magnified.
@@ -5565,7 +5576,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
- [684]applications. Since with integer scale factors the framebuffers
+ [686]applications. Since with integer scale factors the framebuffers
become huge and scaling operations time consuming, be sure to use
":nb" for the fastest response.
@@ -5591,7 +5602,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 ([685]-rfbport option,
+ different scalings listening on separate ports ([687]-rfbport option,
etc.).
Update: As of May/2006 x11vnc also supports the UltraVNC server-side
@@ -5601,8 +5612,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 [686]GUI, then to avoid all of the x11vnc's simultaneously
- answering the gui you will need to use something like [687]"-connect
+ use the [688]GUI, then to avoid all of the x11vnc's simultaneously
+ answering the gui you will need to use something like [689]"-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 proces and the
@@ -5611,7 +5622,7 @@ 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
- [688]"-scale_cursor frac" option to set the cursor scaling to a
+ [690]"-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).
@@ -5633,17 +5644,17 @@ 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 [689]-blackout x11vnc option
+ may be distracting to the viewer. The [691]-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
- [690]-xinerama x11vnc option can be used to have it automatically
+ [692]-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:
- [691]-xinerama is now on by default.
+ [693]-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 [692]-xwarppointer
+ of the large display. If this happens try using the [694]-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
@@ -5668,23 +5679,23 @@ 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 [693]FAQ to increase the limit. It
- is probably also a good idea to run with the [694]-onetile option in
+ /etc/system as mentioned in another [695]FAQ to increase the limit. It
+ is probably also a good idea to run with the [696]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [695]-noshm to use no shm segments.
+ [697]-noshm to use no shm segments.
Q-92: Can x11vnc show only a portion of the display? (E.g. for a
special purpose rfb application).
- As of Mar/2005 x11vnc has the "[696]-clip WxH+X+Y" option to select a
+ As of Mar/2005 x11vnc has the "[698]-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 [697]Xinerama screen into two
+ One user used -clip to split up a large [699]Xinerama screen into two
more managable smaller screens.
This also works to view a sub-region of a single application window if
- the [698]-id or [699]-sid options are used. The offset is measured
+ the [700]-id or [701]-sid options are used. The offset is measured
from the upper left corner of the selected window.
@@ -5693,7 +5704,7 @@ EndSection
crash.
As of Dec/2004 x11vnc supports XRANDR. You enable it with the
- [700]-xrandr option to make x11vnc monitor XRANDR events and also trap
+ [702]-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.
@@ -5703,9 +5714,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 [701]-padgeom option to make the region big
+ viewers you can try the [703]-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: [702]enhanced_tightvnc_viewer
+ for the TightVNC Viewer on Unix: [704]enhanced_tightvnc_viewer
If you specify "-xrandr newfbsize" then vnc viewers that do not
support NewFBSize will be disconnected before the resize. If you
@@ -5717,7 +5728,7 @@ EndSection
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 [703]-rotate option allow this. E.g's:
+ As of Jul/2006 there is the [705]-rotate option allow this. E.g's:
"-rotate +90", "-rotate -90", "-rotate x", etc.
@@ -5782,13 +5793,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 [704]here for how to
+ straight xscreensaver (see the instructions [706]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 [705]-nodpms option was added
+ suspend, or off). In Nov/2006 the x11vnc [707]-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
@@ -5804,15 +5815,20 @@ EndSection
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
- [706]beryl or XDAMAGE/Xorg or the (possibly 3rd party) video card
+ [708]beryl or XDAMAGE/Xorg or the (possibly 3rd party) video card
driver.
- As a workaround apply the [707]-noxdamage option. As of Feb/2007
+ As a workaround apply the [709]-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 [708]this
+ beryl you might as well always supply -noxdamage. Thanks to [710]this
user who reported the problem and discovered the workaround.
+ Please report a bug or complaint to Beryl and/or Xorg about this:
+ running x11vnc with -noxdamage disables a nice improvement in
+ responsiveness (especially for typing) and also leads to unnecessary
+ CPU and memory I/O load due to the extra polling.
+
Q-100: Can I use x11vnc to view my VMWare session remotely?
Yes, since VMWare usually runs as an X application you can view it via
@@ -5824,9 +5840,9 @@ EndSection
* Fullscreen mode
The way VMWare does Fullscreen mode on Linux is to display the Guest
- desktop in a separate Virtual Console (e.g. VC 8) (see [709]this FAQ
+ desktop in a separate Virtual Console (e.g. VC 8) (see [711]this FAQ
on VC's for background). Unfortunately, this Fullscreen VC is not an X
- server. So x11vnc cannot access it (however, [710]see this discussion
+ server. So x11vnc cannot access it (however, [712]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.
@@ -5847,13 +5863,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 [711]is in the active VC.
+ as long as the VMWare X session [713]is in the active VC.
Also note that with a little bit of playing with "xwininfo -all
-children" output one can extract the (non-toplevel) windowid 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 [712]-id windowid option. The
+ the VMWare menu buttons) by use of the [714]-id windowid option. The
caveats are the X session VMWare is in must be in the active VC and
the window must be fully visible, so this mode is not terribly
convenient, but could be useful in some circumstances (e.g. running
@@ -5869,10 +5885,10 @@ EndSection
controlled) via VNC with x11vnc?
As of Apr/2005 there is support for this. Two options were added:
- "[713]-rawfb string" (to indicate the raw framembuffer device, file,
- etc. and its parameters) and "[714]-pipeinput command" (to provide an
+ "[715]-rawfb string" (to indicate the raw framembuffer device, file,
+ etc. and its parameters) and "[716]-pipeinput command" (to provide an
external program that will inject or otherwise process mouse and
- keystroke input). Some useful [715]-pipeinput schemes, VID, CONSOLE,
+ keystroke input). Some useful [717]-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
@@ -5910,9 +5926,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 [716]-snapfb option with
+ this). The "snap:" setting applies the [718]-snapfb option with
"file:" type reading (this is useful for exporting webcams or TV tuner
- video; see [717]the next FAQ for more info).
+ video; see [719]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
@@ -5956,7 +5972,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 [718]X
+ for the case of Xvfb x11vnc can poll it much better via the [720]X
API, but you get the idea.
By default in -rawfb mode x11vnc will actually close any X display it
@@ -5985,13 +6001,13 @@ EndSection
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 [719]Qt-embedded apps (PDAs/Handhelds). By default the
+ fullscreen, or [721]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 [720]this FAQ for details. If specified via "-rawfb Video"
+ kernel. See [722]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).
@@ -5999,10 +6015,10 @@ EndSection
also useful in testing.
- All of the above [721]-rawfb options are just for viewing the raw
+ All of the above [723]-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 [722]video camera mapped its framebuffer
+ this feature (e.g. suppose a [724]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
@@ -6040,7 +6056,7 @@ EndSection
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 VC #2 (assuming it is the [723]active VC) one
+ view and interact with VC #2 (assuming it is the [725]active VC) one
can run something like:
x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2'
@@ -6095,7 +6111,7 @@ EndSection
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
- [724]Qt-embedded Also, for example the [725]VMWare Fullscreen mode is
+ [726]Qt-embedded Also, for example the [727]VMWare Fullscreen mode is
actually viewable under -rawfb and can be interacted with if uinput is
enabled.
@@ -6115,9 +6131,9 @@ EndSection
Q-102: Can I export via VNC a Webcam or TV tuner framebuffer using
x11vnc?
- Yes, this is possible to some degree with the [726]-rawfb option.
+ Yes, this is possible to some degree with the [728]-rawfb option.
There is no X11 involved: snapshots from the video capture device are
- used for the screen image data. See the [727]previous FAQ on -rawfb
+ used for the screen image data. See the [729]previous FAQ on -rawfb
for background. For best results, use x11vnc version 0.8.1 or later.
Roughly, one would do something like this:
@@ -6129,7 +6145,7 @@ EndSection
snapshot to a file that you point -rawfb to; ask me if it is not clear
what to do).
- The "snap:" enforces [728]-snapfb mode which appears to be necessary.
+ The "snap:" enforces [730]-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.
@@ -6151,7 +6167,7 @@ EndSection
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 [729]-24to32 option will be automatically imposed when in
+ etc, the [731]-24to32 option will be automatically imposed when in
24bpp.
Note that by its very nature, video capture involves rapid change in
@@ -6159,7 +6175,7 @@ EndSection
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 [730]-wait, [731]-slow_fb, or [732]-defer
+ the framerate via the [732]-wait, [733]-slow_fb, or [734]-defer
options. Decreasing the window size and bpp also helps.
@@ -6248,7 +6264,7 @@ EndSection
format to HI240, RGB565, RGB24, RGB32, RGB555, and
GREY respectively. See -rawfb video for details.
- See also the [733]-freqtab option to supply your own xawtv channel to
+ See also the [735]-freqtab option to supply your own xawtv channel to
frequency mappings for your country (only ntsc-cable-us is built into
x11vnc).
@@ -6257,7 +6273,7 @@ EndSection
running on my handheld or PC using the Linux console framebuffer (i.e.
not X11)?
- Yes, the basic method for this is the [734]-rawfb scheme where the
+ Yes, the basic method for this is the [736]-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:
@@ -6270,7 +6286,7 @@ EndSection
x11vnc -rawfb /dev/fb0@640x480x16
Also, to force usage of the uinput injection method use "-pipeinput
- UINPUT". See the [735]-pipeinput description for tunable parameters,
+ UINPUT". See the [737]-pipeinput description for tunable parameters,
etc.
One problem with the x11vnc uinput scheme is that it cannot guess the
@@ -6286,7 +6302,7 @@ EndSection
Even with the correct acceleration setting there is stil 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 [736]-pipeinput UINPUT option for tuning
+ times a second. See the [738]-pipeinput UINPUT option for tuning
parameters that can be set (there are some experimental thresh=N
tuning parameters as well)
@@ -6320,7 +6336,7 @@ EndSection
Q-104: 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 [737]-rawfb only
+ Yes, as of Jul/2006 x11vnc enables building for [739]-rawfb only
support. Just do something like when building:
./configure --without-x (plus any other flags)
make
@@ -6336,11 +6352,11 @@ EndSection
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
- [738]-rawfb mechanism described above. The mouse and keyboard input is
+ [740]-rawfb mechanism described above. The mouse and keyboard input is
acheived via Mac OS X API's.
- So you can use x11vnc as an alternative to [739]OSXvnc (aka Vine
- Server), or [740]Apple Remote Desktop (ARD). Perhaps there is some
+ So you can use x11vnc as an alternative to [741]OSXvnc (aka Vine
+ Server), or [742]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.
@@ -6350,7 +6366,7 @@ EndSection
(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 [741]-id windowid mode (and the
+ only work reasonably in single window [743]-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
@@ -6364,9 +6380,9 @@ EndSection
./configure --without-x
make
- Win2VNC/x2vnc: One handy use is to use the [742]-nofb mode to
+ Win2VNC/x2vnc: One handy use is to use the [744]-nofb mode to
redirect mouse and keyboard input to a nearby Mac (i.e. one to the
- side of your desk) via [743]x2vnc or Win2VNC. See [744]this FAQ for
+ side of your desk) via [745]x2vnc or Win2VNC. See [746]this FAQ for
more info.
Options: Here are the Mac OS X specific x11vnc options:
@@ -6440,13 +6456,13 @@ rm -f $tmp
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 "[745]-reflect host:N" option to
+ Yes, as of Feb/2007 there is the "[747]-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
- [746]-rawfb description under "VNC HOST" for more details.
+ [748]-rawfb description under "VNC HOST" for more details.
You can replace "host:N" with "listen" or "listen:port" for reverse
connections.
@@ -6507,20 +6523,20 @@ 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 [747]-nodragging if the
+ not doing wireframing somehow, consider [749]-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:
- [748]http://sourceforge.net/projects/vnc-reflector/,
- [749]http://www.tightvnc.com/projector/ (closed source?),
- [750]http://www.ultravnc.com/addons/repeater.html (seems to be a NAT g
+ [750]http://sourceforge.net/projects/vnc-reflector/,
+ [751]http://www.tightvnc.com/projector/ (closed source?),
+ [752]http://www.ultravnc.com/addons/repeater.html (seems to be a NAT g
ateway and not a broadcaster?)
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 "[751]"-connect host1,host2,..." option).
+ connections (the x11vnc "[753]"-connect host1,host2,..." option).
Suppose all the clients "C" are started up in Listen mode:
client1> vncviewer -listen
client2> vncviewer -listen
@@ -6555,11 +6571,11 @@ ateway and not a broadcaster?)
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 [752]-nosel option. If you don't
+ Clipboard/Selection exchanged use the [754]-nosel option. If you don't
want the PRIMARY selection to be polled for changes use the
- [753]-noprimary option. (with a similar thing for CLIPBOARD). You can
- also fine-tune it a bit with the [754]-seldir dir option and also
- [755]-input.
+ [755]-noprimary option. (with a similar thing for CLIPBOARD). You can
+ also fine-tune it a bit with the [756]-seldir dir option and also
+ [757]-input.
You may need to watch out for desktop utilities such as KDE's
"Klipper" that do odd things with the selection, clipboard, and
@@ -6571,7 +6587,7 @@ ateway and not a broadcaster?)
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
- [756]pyvnc2swf. There are a number of [757]tutorials on how to do
+ [758]pyvnc2swf. There are a number of [759]tutorials 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
@@ -6587,7 +6603,7 @@ ateway and not a broadcaster?)
do work to some degree under Wine on Linux).
TightVNC file transfer is off by default, if you want to enable it use
- the [758]-nofilexfer option.
+ the [760]-nofilexfer option.
UltraVNC file transfer is off by default, to enable it use something
like "-rfbversion 3.6 -permitfiletransfer"
@@ -6621,7 +6637,7 @@ ateway and not a broadcaster?)
these extensions you will need to supply this option to x11vnc:
-rfbversion 3.6
- Or use [759]-ultrafilexfer which is an alias for the above option and
+ Or use [761]-ultrafilexfer which is an alias for the above option and
"-permitfiletransfer". UltraVNC evidently treats any other RFB version
number as non-UltraVNC.
@@ -6633,18 +6649,278 @@ ateway and not a broadcaster?)
* 1/n Server Scaling
* rfbEncodingUltra compression encoding
- To disable SingleWindow and ServerInput use [760]-noultraext (the
+ To disable SingleWindow and ServerInput use [762]-noultraext (the
others are managed by LibVNCServer). See this option too:
- [761]-noserverdpms.
+ [763]-noserverdpms.
+
+
+ Q-111: Can x11vnc emulate UltraVNC's Single Click helpdesk mode? I.e.
+ something very simple for a naive user to initiate a reverse vnc
+ connection from their desktop to a helpdesk operator's VNC Viewer.
+
+ Yes, UltraVNC's [764]Single Click (SC) mode can be emulated reasonably
+ 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 [765]Mac OS X.
+
+ Assume you create a helpdesk directory "hd" on your website:
+ http://www.mysite.com/hd
+
+ In that "hd" subdirectory copy an x11vnc binary and also create a file
+ named "vnc" containing the following:
+#!/bin/sh
+
+webhost="http://www.mysite.com/hd" # Your helpdesk dir URL.
+vnchost="hd1.mysite.com" # Your host running 'vncviewer -listen'
+
+
+dir=/tmp/vnc_helpdesk.$$ # Make working dir.
+mkdir $dir || exit 1
+cd $dir || exit 1
+
+trap "cd /tmp; rm -rf $dir" 0 2 15 # Clean up on exit.
+
+wget $webhost/x11vnc # Fetch x11vnc binary. If multi-
+chmod 755 ./x11vnc # platform, use `uname` etc.
+
+./x11vnc -connect_or_exit $vnchost -rfbport 0 -nopw
+
+ with the hostnames customized to your case.
+
+ On the helpdesk VNC viewer machine (hd1.mysite.com in this example)
+ you have the helpdesk operator running VNC viewer in listen mode:
+ vncviewer -listen
+
+ or if on Windows, etc. somehow have the VNC viewer be in "listen"
+ mode.
+
+ Then, when the naive user needs assistance he opens up a terminal
+ window on his Unix desktop and pastes the following into the shell:
+ wget -qO - http://www.mysite.com/hd/vnc | sh -
+
+ You could have this instruction on a web page or in an email you send
+ him, etc.
+
+
+ So I guess this is about 3-4 clicks and pressing "Enter" instead of
+ "single click".
+
+ If it is beyond the user how to open a terminal window and paste in a
+ command (you have my condolences...) you would have to somehow setup
+ his Web browser to download the "vnc" file (or a script containing the
+ above wget line) and prompt the user if he wants to run it. This may
+ be tricky to set up (which is probably a good thing to not have the
+ web browser readily run arbitrary programs downloaded from the
+ internet...).
+
+ One command-line free way, tested with KDE, is to name the file vnc.sh
+ and then instruct the user to right-click on the link and do "Save
+ Link As" to his Desktop. It will appear as an icon, probably one that
+ looks like a terminal or a command line prompt. He next should
+ right-click on the icon and select "Properties" and go to the
+ "Permissions" tab. Then in that dialog select the checkbox "Is
+ executable". He should then be able to click on the icon to launch it.
+ Another option is to right-click on the icon and select "Open With ->
+ Other ..." and for the name of the application type in "/bin/sh".
+ Unfortunately in both cases the command output is lost and so errors
+ cannot be debugged as easily. A similar thing appears to work in GNOME
+ if under "Properties -> Permissions" they click on "Execute" checkbox
+ for "Owner". Then when they click on the icon, they will get a dialog
+ where they can select "Run in Terminal". In general for such cases, if
+ it is feasible, it might be easier to ssh to his machine and set
+ things up yourself...
+
+
+ If you need to support multiple Unix platforms via this scheme,
+ perhaps create subdirs hd/Linux.i686, hd/SunOS.sun4u, etc. placing the
+ correct binaries in each and then modify the vnc script to have:
+ wget $webhost/`uname -sm | sed -e 's/ /./g'`/x11vnc
+
+ to find the OS's binary. Of course you could create .tar.gz or .zip
+ archives of the x11vnc and vnc (the latter modified, i.e. no wget or
+ tmpdir needed) programs that the user downloads, unpacks and runs vnc.
+ Or perhaps you avoid the website completely and just email him the
+ archive with instructions to unpack and run the script.
+
+ Note if the user is on MacOSX then he more likely has curl than wget.
+ So you could change everything to use that, e.g.:
+curl $webhost/x11vnc > ./x11vnc
+
+ etc. Or one could also have vnc test for the the presence of wget or
+ curl, e.g.
+if type wget >/dev/null; then
+ wget -O - $webhost/x11vnc > ./x11vnc
+elif type curl >/dev/null; then
+ curl $webhost/x11vnc > ./x11vnc
+else
+ lynx -source $webhost/x11vnc > ./x11vnc
+fi
+
+ etc.
+
+ 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).
+
+
+ SSL Encrypted Helpdesk Connections: Currently x11vnc does not support
+ reverse connections in SSL [766]-ssl mode. This may change in a future
+ release, until then you would need to cook up something with
+ [767]STUNNEL.
+
+ To do this, include a copy of an stunnel binary in the "hd" directory
+
+ Next, create a file named "vncs" containing the following:
+#!/bin/sh
+
+webhost="http://www.mysite.com/hd" # Your helpdesk dir URL.
+vnchost="hd1.mysite.com:5501" # Your stunnel passing to 'vncviewer -listen
+'
+
+dir=/tmp/vnc_helpdesk.$$ # Make working dir.
+mkdir $dir || exit 1
+cd $dir || exit 1
+
+trap 'cd /tmp; kill $pid; rm -rf $dir' 0 2 15 # Clean up on exit.
+
+# One could put these files in a .tar.gz file instead, and "| tar xzvf -"
+#
+wget $webhost/x11vnc
+wget $webhost/stunnel
+chmod 755 ./x11vnc ./stunnel
+
+# Make stunnel conf file:
+#
+cat > ./stunnel.conf <<END
+foreground = yes
+pid =
+client = yes
+debug = 6
+# One could do SSL cert auth too... need to wget vnchost's public key.
+# CAfile = ./cert.pub
+# verify = 2
+
+[vnc]
+accept = localhost:5500
+connect = $vnchost
+END
+
+./stunnel ./stunnel.conf &
+pid=$!
+
+./x11vnc -connect_or_exit localhost:5500 -rfbport 0 -nopw
+
+ with the hostnames customized to your case.
+
+ The helpdesk operator would have "vncviewer -listen" running as above,
+ but he also needs an stunnel at his end. To do so make a file
+ "stunnel.cfg" containing:
+foreground = yes
+pid =
+
+[vnc]
+accept = 5501
+connect = localhost:5500
+
+ and run:
+ stunnel ./stunnel.cfg
+
+ That should be it. Note that this assumes the stunnel install created
+ a Server SSL cert+key, usually /etc/stunnel/stunnel.pem (not all
+ distros will do this). Also, that file is by default only readable by
+ root, so stunnel needs to be run as root. If your system does not have
+ a key installed or you do not want to run stunnel as root (or change
+ the permissions on the file), you can use x11vnc to create one for you
+ for example:
+ x11vnc -sslGenCert server self:mystunnel
+
+ 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.
+ This creates $HOME/.vnc/certs/server-self:mystunnel.pem, then you
+ would change the "stunnel.cfg" to look something like:
+foreground = yes
+pid =
+cert = /home/myusername/.vnc/certs/server-self:mystunnel.pem
+
+[vnc]
+accept = 5501
+connect = localhost:5500
+
+ In any event, with stunnel having been setup, the naive user is
+ instructed to paste in and run:
+ wget -qO - http://www.mysite.com/hd/vncs | sh -
+
+ to pick up the vncs script this time.
+
+ With an stunnel scheme like this you could add the helpdesk's public
+ key (see the CAfile line above) to add some more protection by
+ requiring the VNC viewer side to authenticate itself. (Of course if a
+ man-in-the-middle can alter what the user downloads then all bets are
+ off!).
+
+
+ OpenSSL libssl.so.0.9.7 problems: If you build your own stunnel for
+ deployment, you may want to statically link libssl.a and libcrypto.a
+ into it because Linux distros are currently a bit of a mess regarding
+ which version of libssl is installed. The quickest way to static link
+ is a bit of a kludge: you let the build proceed normally then look at
+ the output for the final link, e.g.:
+ ...
+ (build output)
+ ...
+ gcc -g -O2 -Wall -Wshadow -Wcast-align -Wpointer-arith -I/usr/include -o stun
+nel client.o log.o options.o protocol.o network.o resolver.o ssl.o sthreads.o s
+tunnel.o pty.o -lz -ldl -lutil -lnsl -L/usr/lib -lssl -lcrypto -lwrap
+
+ You see that command was run in the src/ subdirectory, and so you cd
+ to it and change the command line so that everywhere you see -lssl you
+ replace it with /usr/lib/libssl.a and -lcrypto you replace it with
+ /usr/lib/libcrypto.a:
+ cd src
+ gcc -g -O2 -Wall -Wshadow -Wcast-align -Wpointer-arith -I/usr/include -o stun
+nel client.o log.o options.o protocol.o network.o resolver.o ssl.o sthreads.o s
+tunnel.o pty.o -lz -ldl -lutil -lnsl -L/usr/lib /usr/lib/libssl.a /usr/lib/libc
+rypto.a -lwrap
+
+ Then the resulting stunnel binary does not have a dynamic dependency
+ on libssl.so.0.9.X or libcrypto.so.0.9.X and so should work on many
+ Linux systems. You should do this build on a relatively older, 1-3
+ years (or the oldest you plan to deploy on), Linux distro (since glibc
+ often adds new spurious dependencies on internal symbols, e.g.
+ __strncpy_chk, even though the application source code is unchanged
+ and does not refer to them).
+
+ Perhaps a cleaner way that avoids rerunning a modified link line:
+ mkdir /tmp/libs
+ cp /usr/lib/libssl.a /usr/lib/libcrypto.a /tmp/libs
+ env LDFLAGS=-L/tmp/libs ./configure
+ make
+ ...
+
+ This libssl problem affects x11vnc binary deployment as well, you
+ could do the same trick as above or you may want to build it using
+ -without-ssl which is OK for this helpdesk reverse connection
+ application (at some point x11vnc will do reverse connections via SSL
+ as well).
+
+ To try to link even more libaries statically into x11vnc (to try to
+ increase the chances for portability of the deployed binary) consider:
+ /usr/X11R6/lib/libXinerama.a, /usr/X11R6/lib/libXfixes.a,
+ /usr/X11R6/lib/libXdamage.a , and /usr/lib/libjpeg.a. Copy them to
+ using the /tmp/libs scheme above. If you want bundle
+ /usr/X11R6/lib/libXrandr.a you will also need include
+ /usr/X11R6/lib/libXrender.a and add -lXrender to the link line.
- Q-111: Can I (temporarily) mount my local (viewer-side) Windows/Samba
+ Q-112: 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 [762]Samba example here.
+ We show a simple [768]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:
@@ -6681,17 +6957,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 [763]Enhanced TightVNC Viewer (ssvnc) package we provide (as
+ into the [769]Enhanced TightVNC Viewer (ssvnc) package we provide (as
of Sep 2006 it is there for testing).
- Q-112: Can I redirect CUPS print jobs from the remote desktop where
+ Q-113: 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 [764]CUPS example here. Non-CUPS port
+ We show a simple Unix to Unix [770]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).
@@ -6763,11 +7039,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 [765]Enhanced TightVNC Viewer (ssvnc) package we provide (as
+ into the [771]Enhanced TightVNC Viewer (ssvnc) package we provide (as
of Sep 2006 it is there for testing).
- Q-113: How can I hear the sound (audio) from the remote applications
+ Q-114: 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.
@@ -6864,11 +7140,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 [766]Enhanced TightVNC Viewer (ssvnc) package
+ redir setup into the [772]Enhanced TightVNC Viewer (ssvnc) package
we provide (as of Sep/2006 it is there for testing).
- Q-114: Why don't I hear the "Beeps" in my X session (e.g. when typing
+ Q-115: 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
@@ -6876,16 +7152,16 @@ 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 [767]-nobell option. If
+ If you don't want to hear the beeps use the [773]-nobell option. If
you want to hear the audio from the remote applications, consider
- trying a [768]redirector such as esd.
+ trying a [774]redirector such as esd.
Contributions:
- Q-115: Thanks for your program and for your help! Can I make a
+ Q-116: Thanks for your program and for your help! Can I make a
donation?
Please do (any amount is appreciated) and thank you for your support!
@@ -7176,493 +7452,499 @@ References
279. http://www.karlrunge.com/x11vnc/index.html#faq-record-swf
280. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer
281. http://www.karlrunge.com/x11vnc/index.html#faq-ultravnc
- 282. http://www.karlrunge.com/x11vnc/index.html#faq-smb-shares
- 283. http://www.karlrunge.com/x11vnc/index.html#faq-cups
- 284. http://www.karlrunge.com/x11vnc/index.html#faq-sound
- 285. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
- 286. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 288. http://www.tldp.org/HOWTO/Remote-X-Apps.html
- 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 290. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 293. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 294. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 295. http://www.karlrunge.com/x11vnc/index.html#building
- 296. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 297. http://packages.debian.org/x11vnc
- 298. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 299. http://dag.wieers.com/packages/x11vnc/
- 300. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html
- 301. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
- 302. http://www.sunfreeware.com/
- 303. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
- 304. http://www.freshports.org/net/x11vnc
- 305. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html
- 306. http://pkgsrc.se/x11/x11vnc
- 307. http://mike.saunby.googlepages.com/
- 308. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc
- 309. http://www.focv.com/ipkg/
- 310. http://www.karlrunge.com/x11vnc/bins
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 312. http://www.tightvnc.com/download.html
- 313. http://www.realvnc.com/download-free.html
- 314. http://sourceforge.net/projects/cotvnc/
- 315. http://www.ultravnc.com/
- 316. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 319. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 324. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 326. http://fredrik.hubbe.net/x2vnc.html
- 327. http://www.hubbe.net/~hubbe/win2vnc.html
- 328. http://www.deboer.gmxhome.de/
- 329. http://sourceforge.net/projects/win2vnc/
- 330. http://fredrik.hubbe.net/x2vnc.html
- 331. http://freshmeat.net/projects/x2x/
- 332. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 333. http://zapek.com/software/zvnc/
- 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 335. http://www.karlrunge.com/x11vnc/index.html#faq-macosx
- 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 339. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 282. http://www.karlrunge.com/x11vnc/index.html#faq-singleclick
+ 283. http://www.karlrunge.com/x11vnc/index.html#faq-smb-shares
+ 284. http://www.karlrunge.com/x11vnc/index.html#faq-cups
+ 285. http://www.karlrunge.com/x11vnc/index.html#faq-sound
+ 286. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
+ 287. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 289. http://www.tldp.org/HOWTO/Remote-X-Apps.html
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 291. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 294. http://www.karlrunge.com/x11vnc/index.html#libssl-problems
+ 295. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 297. http://www.karlrunge.com/x11vnc/index.html#building
+ 298. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 299. http://packages.debian.org/x11vnc
+ 300. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 301. http://dag.wieers.com/packages/x11vnc/
+ 302. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html
+ 303. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/
+ 304. http://www.sunfreeware.com/
+ 305. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all
+ 306. http://www.freshports.org/net/x11vnc
+ 307. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html
+ 308. http://pkgsrc.se/x11/x11vnc
+ 309. http://mike.saunby.googlepages.com/
+ 310. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc
+ 311. http://www.focv.com/ipkg/
+ 312. http://www.karlrunge.com/x11vnc/bins
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 314. http://www.tightvnc.com/download.html
+ 315. http://www.realvnc.com/download-free.html
+ 316. http://sourceforge.net/projects/cotvnc/
+ 317. http://www.ultravnc.com/
+ 318. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 321. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray
+ 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 326. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 328. http://fredrik.hubbe.net/x2vnc.html
+ 329. http://www.hubbe.net/~hubbe/win2vnc.html
+ 330. http://www.deboer.gmxhome.de/
+ 331. http://sourceforge.net/projects/win2vnc/
+ 332. http://fredrik.hubbe.net/x2vnc.html
+ 333. http://freshmeat.net/projects/x2x/
+ 334. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 335. http://zapek.com/software/zvnc/
+ 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 337. http://www.karlrunge.com/x11vnc/index.html#faq-macosx
+ 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 341. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
- 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 350. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 358. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 359. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 360. http://wwws.sun.com/sunray/index.html
- 361. http://www.karlrunge.com/x11vnc/sunray.html
- 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 373. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
- 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24
+ 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 352. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 360. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 361. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 362. http://wwws.sun.com/sunray/index.html
+ 363. http://www.karlrunge.com/x11vnc/sunray.html
+ 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 369. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 370. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 371. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 375. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw
+ 377. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 378. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
379. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
- 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 383. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 387. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 388. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel
- 389. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 390. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
- 392. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
- 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 380. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 382. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 383. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis
+ 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 389. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 390. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel
+ 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 392. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd
+ 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 399. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 402. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 404. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 405. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 408. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 409. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
- 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 401. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 404. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 406. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 407. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 410. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 411. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 418. ftp://ftp.x.org/
- 419. http://www.karlrunge.com/x11vnc/dtVncPopup
- 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 423. http://www.karlrunge.com/x11vnc/blockdpy.c
- 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
- 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
- 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd
- 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
- 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
- 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
- 433. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 434. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 420. ftp://ftp.x.org/
+ 421. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
+ 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 425. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms
+ 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms
+ 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd
+ 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
+ 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr
+ 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept
435. http://www.karlrunge.com/x11vnc/index.html#tunnelling
436. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 440. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
- 441. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 443. http://www.stunnel.org/
- 444. http://stunnel.mirt.net/
- 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
- 448. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
- 449. http://www.stunnel.org/
- 450. http://www.karlrunge.com/x11vnc/ssl.html
- 451. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 437. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 438. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 442. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh
+ 443. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 445. http://www.stunnel.org/
+ 446. http://stunnel.mirt.net/
+ 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
+ 450. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+ 451. http://www.stunnel.org/
452. http://www.karlrunge.com/x11vnc/ssl.html
- 453. http://www.securityfocus.com/infocus/1677
+ 453. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
454. http://www.karlrunge.com/x11vnc/ssl.html
- 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 456. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 463. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
- 464. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 465. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
- 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 468. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
- 470. http://www.openssl.org/
- 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
- 472. http://www.stunnel.org/
- 473. http://www.karlrunge.com/x11vnc/ssl.html
- 474. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 455. http://www.securityfocus.com/infocus/1677
+ 456. http://www.karlrunge.com/x11vnc/ssl.html
+ 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 458. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 465. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 466. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 467. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 470. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 472. http://www.openssl.org/
+ 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel
+ 474. http://www.stunnel.org/
475. http://www.karlrunge.com/x11vnc/ssl.html
- 476. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 480. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
+ 476. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 477. http://www.karlrunge.com/x11vnc/ssl.html
+ 478. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
- 482. http://www.karlrunge.com/x11vnc/ssl-output.html
- 483. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
- 484. http://www.karlrunge.com/x11vnc/ss_vncviewer
- 485. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 486. http://www.karlrunge.com/x11vnc/ssl.html
- 487. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 488. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
- 489. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
- 490. http://www.karlrunge.com/x11vnc/ssl-portal.html
- 491. http://www.karlrunge.com/x11vnc/ssl.html
- 492. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 493. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 494. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 495. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 496. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset
- 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 498. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
- 500. http://www.jirka.org/gdm-documentation/x241.html
- 501. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 503. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 507. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
- 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
- 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns
- 510. http://www.avahi.org/
- 511. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 514. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd
- 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 524. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 527. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
- 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
- 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 531. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 532. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
- 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 536. http://www.karlrunge.com/x11vnc/faq-linuxvc
- 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
- 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
- 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 546. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
- 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 553. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
- 554. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 555. http://www.karlrunge.com/x11vnc/Xdummy
- 556. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
- 557. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
- 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
- 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
- 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
- 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
- 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
- 563. http://www.karlrunge.com/x11vnc/shm_clear
- 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 566. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
- 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 578. http://www.tightvnc.com/
+ 482. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal
+ 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https
+ 484. http://www.karlrunge.com/x11vnc/ssl-output.html
+ 485. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext
+ 486. http://www.karlrunge.com/x11vnc/ss_vncviewer
+ 487. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 488. http://www.karlrunge.com/x11vnc/ssl.html
+ 489. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 490. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 491. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers
+ 492. http://www.karlrunge.com/x11vnc/ssl-portal.html
+ 493. http://www.karlrunge.com/x11vnc/ssl.html
+ 494. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 495. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 496. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 497. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 498. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset
+ 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 500. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N
+ 502. http://www.jirka.org/gdm-documentation/x241.html
+ 503. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 505. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 509. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin
+ 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi
+ 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns
+ 512. http://www.avahi.org/
+ 513. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 516. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd
+ 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 526. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 529. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int
+ 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw
+ 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 533. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 534. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer
+ 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 538. http://www.karlrunge.com/x11vnc/faq-linuxvc
+ 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop
+ 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http
+ 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 548. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
+ 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 555. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
+ 556. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 557. http://www.karlrunge.com/x11vnc/Xdummy
+ 558. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously
+ 559. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay
+ 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT
+ 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find
+ 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create
+ 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc
+ 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc
+ 565. http://www.karlrunge.com/x11vnc/shm_clear
+ 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 568. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
+ 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb
+ 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
- 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
- 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 594. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
- 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
- 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 599. http://www.karlrunge.com/x11vnc/index.html#faq-beryl
- 600. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 580. http://www.tightvnc.com/
+ 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds
+ 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout
+ 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 596. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area
+ 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem
+ 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 601. http://www.karlrunge.com/x11vnc/index.html#faq-beryl
+ 602. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 606. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 607. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
- 608. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 609. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 608. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 609. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect
+ 610. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 611. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 613. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
- 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
- 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
- 617. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
- 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
- 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
- 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
- 622. http://www.karlrunge.com/x11vnc/index.html#beta-test
- 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
- 624. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#ycrop
- 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap
- 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
- 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 630. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 631. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 632. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 638. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 639. http://www.tightvnc.com/
- 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 615. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow
+ 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe
+ 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect
+ 619. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe
+ 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen
+ 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip
+ 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect
+ 624. http://www.karlrunge.com/x11vnc/index.html#beta-test
+ 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache
+ 626. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#ycrop
+ 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap
+ 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr
+ 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 632. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 633. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 634. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 640. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 641. http://www.tightvnc.com/
+ 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 648. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 649. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 655. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 656. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 658. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 660. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
- 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 663. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 650. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 651. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 655. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 658. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 660. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys
+ 663. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 672. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 674. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
- 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
- 682. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 684. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
- 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
- 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 693. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
- 697. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 702. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
- 704. http://www.jwz.org/xscreensaver/man1.html
- 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
- 706. http://www.beryl-project.org/
- 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
- 708. http://www.dslinux.org/blogs/pepsiman/?p=73
- 709. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 710. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys
+ 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak
+ 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock
+ 684. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 686. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html
+ 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor
+ 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 695. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip
+ 699. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 704. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate
+ 706. http://www.jwz.org/xscreensaver/man1.html
+ 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms
+ 708. http://www.beryl-project.org/
+ 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage
+ 710. http://www.dslinux.org/blogs/pepsiman/?p=73
711. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 713. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 714. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 717. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 718. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
- 719. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
- 720. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 721. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 712. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 713. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 714. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 717. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 718. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 719. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 720. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb
+ 721. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
722. http://www.karlrunge.com/x11vnc/index.html#faq-video
- 723. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 724. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
- 725. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
- 726. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 727. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 728. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
- 729. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
- 730. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 731. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
- 732. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 733. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
- 734. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
- 735. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 736. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
- 737. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 738. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 739. http://www.redstonesoftware.com/vnc.html
- 740. http://www.apple.com/remotedesktop/
- 741. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 742. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 743. http://fredrik.hubbe.net/x2vnc.html
- 744. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
- 745. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
- 746. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
- 747. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 748. http://sourceforge.net/projects/vnc-reflector/
- 749. http://www.tightvnc.com/projector/
- 750. http://www.ultravnc.com/addons/repeater.html
- 751. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 752. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 753. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 754. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
- 755. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 756. http://www.unixuser.org/~euske/vnc2swf/
- 757. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
- 758. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
- 759. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
- 760. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext
- 761. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
- 762. http://www.samba.org/
- 763. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 764. http://www.cups.org/
- 765. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 766. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
- 767. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 768. http://www.karlrunge.com/x11vnc/index.html#faq-sound
+ 723. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 724. http://www.karlrunge.com/x11vnc/index.html#faq-video
+ 725. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 726. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded
+ 727. http://www.karlrunge.com/x11vnc/index.html#faq-vmware
+ 728. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 729. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 730. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb
+ 731. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32
+ 732. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 733. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb
+ 734. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 735. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab
+ 736. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb
+ 737. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 738. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput
+ 739. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 740. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 741. http://www.redstonesoftware.com/vnc.html
+ 742. http://www.apple.com/remotedesktop/
+ 743. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 744. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 745. http://fredrik.hubbe.net/x2vnc.html
+ 746. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
+ 747. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect
+ 748. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb
+ 749. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 750. http://sourceforge.net/projects/vnc-reflector/
+ 751. http://www.tightvnc.com/projector/
+ 752. http://www.ultravnc.com/addons/repeater.html
+ 753. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 754. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 755. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 756. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir
+ 757. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 758. http://www.unixuser.org/~euske/vnc2swf/
+ 759. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/
+ 760. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer
+ 761. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer
+ 762. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext
+ 763. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms
+ 764. http://www.uvnc.com/addons/singleclick.html
+ 765. http://www.karlrunge.com/x11vnc/index.html#faq-macosx
+ 766. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
+ 767. http://stunnel.mirt.net/
+ 768. http://www.samba.org/
+ 769. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 770. http://www.cups.org/
+ 771. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 772. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html
+ 773. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 774. http://www.karlrunge.com/x11vnc/index.html#faq-sound
=======================================================================
http://www.karlrunge.com/x11vnc/chainingssh.html:
@@ -8408,7 +8690,8 @@ pem
More info:
See also this [21]article for some some general info and examples
- using stunnel and openssl on Windows with VNC.
+ using stunnel and openssl on Windows with VNC. Also
+ [22]http://www.stunnel.org/faq/certs.html
References
@@ -8433,6 +8716,7 @@ References
19. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify
20. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCertInfo
21. http://www.securityfocus.com/infocus/1677
+ 22. http://www.stunnel.org/faq/certs.html
=======================================================================
http://www.karlrunge.com/x11vnc/ssl-portal.html:
@@ -10040,7 +10324,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.8.5 lastmod: 2007-02-19
+x11vnc: allow VNC connections to real X11 displays. 0.8.5 lastmod: 2007-03-13
x11vnc options:
-display disp -auth file -N
@@ -10153,7 +10437,7 @@ libvncserver-tight-extension options:
% x11vnc -help
-x11vnc: allow VNC connections to real X11 displays. 0.8.5 lastmod: 2007-02-19
+x11vnc: allow VNC connections to real X11 displays. 0.8.5 lastmod: 2007-03-13
(type "x11vnc -opts" to just list the options.)
@@ -10250,11 +10534,14 @@ Options:
etc, although they will be clipped if they extend beyond
the window.
-clip WxH+X+Y Only show the sub-region of the full display that
- corresponds to the rectangle with size WxH and offset
- +X+Y. The VNC display has size WxH (i.e. smaller than
- the full display). This also works for -id/-sid mode
- where the offset is relative to the upper left corner
- of the selected window.
+ corresponds to the rectangle geometry with size WxH and
+ offset +X+Y. The VNC display has size WxH (i.e. smaller
+ than the full display). This also works for -id/-sid
+ mode where the offset is relative to the upper left
+ corner of the selected window. An example use of this
+ option would be to split a large (e.g. Xinerama) display
+ into two parts to be accessed via separate viewers by
+ running a separate x11vnc on each part.
-flashcmap In 8bpp indexed color, let the installed colormap flash
as the pointer moves from window to window (slow).
@@ -10489,9 +10776,8 @@ Options:
per-client viewonly state the filetransfer permissions
will NOT change.
--ultrafilexfer Note, to *enable* UltraVNC filetransfer (currently
- disabled by default, this may change...) and to get it
- to work you probably need to supply these libvncserver
+-ultrafilexfer Note: to enable UltraVNC filetransfer and to get it to
+ work you probably need to supply these libvncserver
options: "-rfbversion 3.6 -permitfiletransfer"
"-ultrafilexfer" is an alias for this combination.
diff --git a/x11vnc/help.c b/x11vnc/help.c
index 6fdc991..0cb7beb 100644
--- a/x11vnc/help.c
+++ b/x11vnc/help.c
@@ -115,11 +115,14 @@ void print_help(int mode) {
" etc, although they will be clipped if they extend beyond\n"
" the window.\n"
"-clip WxH+X+Y Only show the sub-region of the full display that\n"
-" corresponds to the rectangle with size WxH and offset\n"
-" +X+Y. The VNC display has size WxH (i.e. smaller than\n"
-" the full display). This also works for -id/-sid mode\n"
-" where the offset is relative to the upper left corner\n"
-" of the selected window.\n"
+" corresponds to the rectangle geometry with size WxH and\n"
+" offset +X+Y. The VNC display has size WxH (i.e. smaller\n"
+" than the full display). This also works for -id/-sid\n"
+" mode where the offset is relative to the upper left\n"
+" corner of the selected window. An example use of this\n"
+" option would be to split a large (e.g. Xinerama) display\n"
+" into two parts to be accessed via separate viewers by\n"
+" running a separate x11vnc on each part.\n"
"\n"
"-flashcmap In 8bpp indexed color, let the installed colormap flash\n"
" as the pointer moves from window to window (slow).\n"
@@ -354,9 +357,8 @@ void print_help(int mode) {
" per-client viewonly state the filetransfer permissions\n"
" will NOT change.\n"
"\n"
-"-ultrafilexfer Note, to *enable* UltraVNC filetransfer (currently\n"
-" disabled by default, this may change...) and to get it\n"
-" to work you probably need to supply these libvncserver\n"
+"-ultrafilexfer Note: to enable UltraVNC filetransfer and to get it to\n"
+" work you probably need to supply these libvncserver\n"
" options: \"-rfbversion 3.6 -permitfiletransfer\"\n"
" \"-ultrafilexfer\" is an alias for this combination.\n"
"\n"
diff --git a/x11vnc/scan.c b/x11vnc/scan.c
index f4810ac..1c5b54e 100644
--- a/x11vnc/scan.c
+++ b/x11vnc/scan.c
@@ -2846,7 +2846,7 @@ static int scan_display(int ystart, int rescan) {
int x, y, w, n;
int tile_count = 0;
int nodiffs = 0, diff_hint;
- int xd_check, xd_freq = 1;
+ int xd_check = 0, xd_freq = 1;
static int xd_tck = 0;
y = ystart;
diff --git a/x11vnc/screen.c b/x11vnc/screen.c
index 31cce52..3eea705 100644
--- a/x11vnc/screen.c
+++ b/x11vnc/screen.c
@@ -845,7 +845,7 @@ static void initialize_snap_fb(void) {
snap_fb = snap->data;
}
-rfbClient* client = NULL;
+static rfbClient* client = NULL;
void vnc_reflect_bell(rfbClient *cl) {
if (cl) {}
diff --git a/x11vnc/solid.c b/x11vnc/solid.c
index 9fb2562..e1b7049 100644
--- a/x11vnc/solid.c
+++ b/x11vnc/solid.c
@@ -611,26 +611,27 @@ static void solid_gnome(char *color) {
}
static char *dcop_session(void) {
+ char *empty = strdup("");
#if NO_X11
- RAWFB_RET("");
- return "";
+ RAWFB_RET(empty);
+ return empty;
#else
char list_sessions[] = "dcop --user '%s' --list-sessions";
int len;
char *cmd, *host, *user = NULL;
char *out, *p, *ds, *dsn = NULL, *sess = NULL, *sess2 = NULL;
- RAWFB_RET("");
+ RAWFB_RET(empty);
if (getenv("SESSION_MANAGER")) {
- return "";
+ return empty;
}
user = get_user_name();
if (strstr(user, "'") != NULL) {
rfbLog("invalid user: %s\n", user);
free(user);
- return "";
+ return empty;
}
len = strlen(list_sessions) + strlen(user) + 1;
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index 872ed68..870d56a 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" "February 2007" "x11vnc " "User Commands"
+.TH X11VNC "1" "March 2007" "x11vnc " "User Commands"
.SH NAME
x11vnc - allow VNC connections to real X11 displays
- version: 0.8.5, lastmod: 2007-02-19
+ version: 0.8.5, lastmod: 2007-03-13
.SH SYNOPSIS
.B x11vnc
[OPTION]...
@@ -125,11 +125,14 @@ the window.
\fB-clip\fR \fIWxH+X+Y\fR
.IP
Only show the sub-region of the full display that
-corresponds to the rectangle with size WxH and offset
-+X+Y. The VNC display has size WxH (i.e. smaller than
-the full display). This also works for \fB-id/-sid\fR mode
-where the offset is relative to the upper left corner
-of the selected window.
+corresponds to the rectangle geometry with size WxH and
+offset +X+Y. The VNC display has size WxH (i.e. smaller
+than the full display). This also works for \fB-id/-sid\fR
+mode where the offset is relative to the upper left
+corner of the selected window. An example use of this
+option would be to split a large (e.g. Xinerama) display
+into two parts to be accessed via separate viewers by
+running a separate x11vnc on each part.
.PP
\fB-flashcmap\fR
.IP
@@ -417,9 +420,8 @@ will NOT change.
.PP
\fB-ultrafilexfer\fR
.IP
-Note, to *enable* UltraVNC filetransfer (currently
-disabled by default, this may change...) and to get it
-to work you probably need to supply these libvncserver
+Note: to enable UltraVNC filetransfer and to get it to
+work you probably need to supply these libvncserver
options: "\fB-rfbversion\fR \fI3.6 \fB-permitfiletransfer\fR"\fR
"\fB-ultrafilexfer\fR" is an alias for this combination.
.IP
diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c
index 0b292ba..5c0dc02 100644
--- a/x11vnc/x11vnc.c
+++ b/x11vnc/x11vnc.c
@@ -75,7 +75,7 @@
* extensions exists that allow drawing the mouse into the framebuffer)
*
* The current *position* of the remote X mouse pointer is shown with
- * the -cursor option. Further, if -cursorX or -X is used, a trick
+ * the -cursor option. Further, if -cursor X is used, a trick
* is done to at least show the root window cursor vs non-root cursor.
* (perhaps some heuristic can be done to further distinguish cases...,
* currently "-cursor some" is a first hack at this)
@@ -3266,6 +3266,23 @@ int main(int argc, char* argv[]) {
scr = DefaultScreen(dpy);
rootwin = RootWindow(dpy, scr);
+ if (ncache_beta_tester) {
+ int h = DisplayHeight(dpy, scr);
+ int w = DisplayWidth(dpy, scr);
+ int mem = (w * h * 4) / (1000 * 1000), MEM = 96;
+ if (mem < 1) mem = 1;
+
+ /* limit poor, unsuspecting beta tester's viewer to 96 MB */
+ if ( (ncache+2) * mem > MEM ) {
+ int n = (MEM/mem) - 2;
+ if (n < 0) n = 0;
+ n = 2 * (n / 2);
+ if (n < ncache) {
+ ncache = n;
+ }
+ }
+ }
+
if (grab_always) {
Window save = window;
window = rootwin;
@@ -3533,7 +3550,7 @@ int main(int argc, char* argv[]) {
rfbLog(" iconifying/deiconifying windows, moving and raising\n");
rfbLog(" windows, and reposting menus. In the simple CopyRect\n");
rfbLog(" encoding scheme used (no compression) a huge amount\n");
- rfbLog(" of extra memory (20-80MB) is used on both the server and\n");
+ rfbLog(" of extra memory (20-100MB) is used on both the server and\n");
rfbLog(" client sides. This mode works with any VNC viewer.\n");
rfbLog(" However, in most you can actually see the cached pixel\n");
rfbLog(" data by scrolling down, so you need to re-adjust its size.\n");
diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c
index 22d98b6..5438a79 100644
--- a/x11vnc/x11vnc_defs.c
+++ b/x11vnc/x11vnc_defs.c
@@ -15,7 +15,7 @@ int xtrap_base_event_type = 0;
int xdamage_base_event_type = 0;
/* date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.8.5 lastmod: 2007-02-19";
+char lastmod[] = "0.8.5 lastmod: 2007-03-13";
/* X display info */
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-25 17:35:59 +0000