diff options
| author | runge <runge> | 2005-02-23 17:50:17 +0000 |
|---|---|---|
| committer | runge <runge> | 2005-02-23 17:50:17 +0000 |
| commit | b36ca2379084baac477dc89e5d6a045995141b68 (patch) | |
| tree | 65d4f6a71c33a6cc82734b723eca3f37c250d942 | |
| parent | b70fcb448e72269c6320d71fb54179d2cb3a52d7 (diff) | |
| download | libtdevnc-b36ca237.tar.gz libtdevnc-b36ca237.zip | |
x11vnc: final changes for 0.7.1 release.
| -rw-r--r-- | x11vnc/ChangeLog | 3 | ||||
| -rw-r--r-- | x11vnc/README | 2246 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 2 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 2 |
4 files changed, 1267 insertions, 986 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index 588b7f9..dbeb8b7 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,6 @@ +2005-02-23 Karl Runge <runge@karlrunge.com> + * final changes for 0.7.1 release. + 2005-02-21 Karl Runge <runge@karlrunge.com> * -nap is now the default, disable with -nonap * set version to 0.7.1, word tune -help, etc. diff --git a/x11vnc/README b/x11vnc/README index 8563027..2ee2b8c 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Mon Feb 21 22:41:53 EST 2005 +x11vnc README file Date: Wed Feb 23 12:59:36 EST 2005 The following information is taken from these URLs: @@ -33,9 +33,10 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) Background: VNC (Virtual Network Computing) is a very useful network graphics - protocol in the spirit of X, however, unlike X, the viewing-end is - very simple and maintains no state. It is a remote framebuffer (RFB) - protocol + protocol (applications running on one computer but displaying their + windows on another) in the spirit of X, however, unlike X, the + viewing-end is very simple and maintains no state. It is a remote + framebuffer (RFB) protocol Some VNC links: * [6]http://www.uk.research.att.com/vnc/ @@ -44,7 +45,7 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated - with a real display, but provides a "fake" one X11 clients (xterm, + with a physical display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. @@ -55,9 +56,10 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11. - So the standard Xvnc program is very useful, I use it for things like: - * desktop conferencing with other users (e.g. codereviews). - * long running apps/tasks I want to be able to view from many + So the standard Xvnc/vncserver program is very useful, I use it for + things like: + * Desktop conferencing with other users (e.g. codereviews). + * Long running apps/tasks I want to be able to view from many places. * Motif, GNOME, and similar applications that would yield very poor performance over a high latency link. @@ -73,9 +75,9 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) How to use x11vnc: - In this example let's assume the remote machine with the X display you - wish to view is "far-away.east:0" and the workstation you are - presently working at is "sitting-here.west". + In this basic example let's assume the remote machine with the X + display you wish to view is "far-away.east:0" and the workstation you + are presently working at is "sitting-here.west". Step 0. Download x11vnc ([9]see below) and have it available to run on far-away.east. Similarly, have a VNC viewer (e.g. vncviewer) ready to @@ -97,9 +99,9 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) display (no viewer clients yet). To get X11 permissions right, you may also need to set the XAUTHORITY - environment variable (or use the -auth option) to point to the correct - MIT-MAGIC-COOKIE file (e.g. /home/joe/.Xauthority). More on this - [11]below. + environment variable (or use the [11]-auth option) to point to the + correct MIT-MAGIC-COOKIE file (e.g. /home/joe/.Xauthority). More on + this [12]below. There will then be much chatter printed out from x11vnc, until it finally says something like: @@ -117,8 +119,8 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) viewers for Unix, Windows, MacOS, Java-enabled web browsers, and even for PDA's like the Palm Pilot! You can use any of them to connect to x11vnc (see the above VNC links under "Background:" on how to obtain a - viewer for your platform or [12]this FAQ. For Solaris, vncviewer is - available in the [13]Companion CD package SFWvnc ). + viewer for your platform or see [13]this FAQ. For Solaris, vncviewer + is available in the [14]Companion CD package SFWvnc ). In this example we'll use the Unix vncviewer program on sitting-here by typing the following command in a second terminal window: @@ -128,13 +130,14 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) That should pop up a viewer window on sitting-here.west showing and allowing interaction with the far-away.east:0 X11 desktop. Pretty nifty! When finished, exit the viewer: the remote x11vnc process will - shutdown automatically (or you can use the -forever [14]option to have + shutdown automatically (or you can use the [15]-forever option to have it wait for additional viewer connections). - Shortcut: Of course if you left x11vnc running in a terminal window or - as a [15]service on far-away.east:0, you'd only have to do Step 3 as - you moved around. Be sure to use a VNC [16]password or [17]other - measures if you do that. + Shortcut: Of course if you left x11vnc running on far-away.east:0 in a + terminal window with the [16]-forever option or as a [17]service, + you'd only have to do Step 3 as you moved around. Be sure to use a VNC + [18]password or [19]other measures if you do that. + Desktop Sharing: The above more or less assumed nobody was sitting at the workstation display "far-away.east:0". This is often the case: a @@ -149,7 +152,7 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) For these cases it should be obvious how it is done. The above steps will work, but more easily the user sitting at far-away.east:0 simply starts up x11vnc from a terminal window, after which the guests would - start their VNC viewers. For this usage mode the "-connect + start their VNC viewers. For this usage mode the "[20]-connect host1,host2" option may be of use automatically connect to vncviewers in "-listen" mode on the list of hosts. _________________________________________________________________ @@ -176,15 +179,16 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) Some VNC viewers will do the ssh tunnelling for you automatically, the TightVNC vncviewer does this when the "-via far-away.east" option is supplied to it (this requires x11vnc to be already running on - far-away.east or having it started by [18]inetd(1)). See the 3rd - script example [19]below for more info. + far-away.east or having it started by [21]inetd(1)). See the 3rd + script example [22]below for more info. If the machine you SSH into is not the same machine with the X display you wish to view (e.g. your company provides incoming SSH access to a gateway machine), then you need to change the above to, e.g.: "-L 5900:otherhost:5900". Once logged in, you'll need to do a second login (ssh, rsh, etc.) to the workstation machine 'otherhost' and then start - up x11vnc on it. + up x11vnc on it if it isn't already running. + _________________________________________________________________ Scripts to automate ssh tunneling: As discussed below, there may be @@ -192,11 +196,12 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]downloads) above port and display numbers may change a bit (e.g. -> 5901 and :1). However, if you "know" port 5900 will be free on the local and remote machines, you can easily automate the above two steps by using the - x11vnc option -bg (forks into background after connection to the - display is set up) or using the -f option of ssh. - + x11vnc option [23]-bg (forks into background after connection to the + display is set up) or using the -f option of ssh. Three example + scripts are shown below. + _________________________________________________________________ - A simple example script, assuming no problems with port 5900 being + #1. A simple example script, assuming no problems with port 5900 being taken on the local or remote sides, looks like: #!/bin/sh # usage: x11vnc_ssh <host>:<xdisplay> @@ -220,9 +225,9 @@ done See also rx11vnc.pl below. _________________________________________________________________ - Another method is to start the VNC viewer in listen mode "vncviewer - -listen" and have x11vnc initiate a reverse connection using the - -connect option: + #2. Another method is to start the VNC viewer in listen mode + "vncviewer -listen" and have x11vnc initiate a reverse connection + using the [24]-connect option: #!/bin/sh # usage: x11vnc_ssh <host>:<xdisplay> # e.g.: x11vnc_ssh snoopy.peanuts.com:0 @@ -231,7 +236,7 @@ host=`echo $1 | awk -F: '{print $1}'` disp=`echo $1 | awk -F: '{print $2}'` if [ "x$disp" = "x" ]; then disp=0; fi -cmd="x11vnc -display :$disp -localhost -connect localhost" # <-- note new opt +cmd="x11vnc -display :$disp -localhost -connect localhost" # <== note new opt ion enc="copyrect tight zrle hextile zlib corre rre raw" @@ -239,12 +244,16 @@ vncviewer -encodings "$enc" -listen & pid=$! ssh -R 5500:localhost:5500 $host "$cmd" kill $pid + + Note the use of the ssh option -R instead of -L to set up a remote + port redirection. _________________________________________________________________ - A third way is specific to the TightVNC vncviewer special option -via - for gateways. The only tricky part is we need to start up x11vnc and - give it some time to start listening for connections (so we cannot use - the TightVNC default setting for VNC_VIA_CMD): + #3. A third way is specific to the TightVNC vncviewer special option + -via for gateways. The only tricky part is we need to start up x11vnc + and give it some time (5 seconds in this example) to start listening + for connections (so we cannot use the TightVNC default setting for + VNC_VIA_CMD): #!/bin/sh # usage: x11vnc_ssh <host>:<xdisplay> # e.g.: x11vnc_ssh snoopy.peanuts.com:0 @@ -260,62 +269,65 @@ export VNC_VIA_CMD vncviewer -via $host localhost:0 # must be TightVNC vncviewer. Of course if you already have the x11vnc running waiting for - connections (or have it started out of [20]inetd(1)), you can simply + connections (or have it started out of [25]inetd(1)), you can simply use the TightVNC "vncviewer -via gateway host:port" in its default mode to provide secure ssh tunnelling. - VNC password file: Also note in the first example script that the - option "-rfbauth .vnc/passwd" provides additional protection by + VNC password file: Also note in the #1. example script that the + [26]option "-rfbauth .vnc/passwd" provides additional protection by requiring a VNC password for every VNC viewer that connects. The - vncpasswd or storepasswd programs, or the x11vnc [21]-storepasswd + vncpasswd or storepasswd programs, or the x11vnc [27]-storepasswd option can be used to create the password file. x11vnc also has the - slightly less secure [22]-passwdfile and "-passwd XXXXX" options. + slightly less secure [28]-passwdfile and "-passwd XXXXX" [29]options + to specify passwords. Important: It is up to you to tell x11vnc to use password protection, - it will not do it for you automatically. The same goes for encrypting - the channel between the viewer and x11vnc: it is up to you to use ssh, - stunnel, VPN, etc. Also look into the -allow and -localhost - [23]options and building x11vnc with [24]tcp_wrappers support to limit - host access. + it will not do it for you automatically or force you to. The same goes + for encrypting the channel between the viewer and x11vnc: it is up to + you to use ssh, stunnel, VPN, etc. Also look into the -allow and + -localhost [30]options and building x11vnc with [31]tcp_wrappers + support to limit host access. _________________________________________________________________ Downloading x11vnc: - x11vnc is a contributed program to the [25]LibVNCServer project at + x11vnc is a contributed program to the [32]LibVNCServer project at SourceForge.net. I use libvncserver for all of the VNC aspects; I couldn't have done without it. The full source code may be found and downloaded (either file-release tarball or CVS tree) from the above - link. As of Dec 2004, the [26]x11vnc-0.7.tar.gz source package is - released (recommended download) . The [27]x11vnc 0.7 release notes. + link. As of Dec 2004, the [33]x11vnc-0.7.tar.gz source package is + released (recommended download) . The [34]x11vnc 0.7 release notes. The x11vnc package is the subset of the libvncserver package needed to build the x11vnc program. Also, you can get a copy of my latest, - bleeding edge [28]x11vnc.c file to replace the one in the above + bleeding edge [35]x11vnc.c file to replace the one in the above packages or the one in the CVS tree and then rebuild. You can also - update the tcl/tk gui with the [29]tkx11vnc.h file. If you have an + update the tcl/tk gui with the [36]tkx11vnc.h file. If you have an older libvncserver source tree, you may need to switch on the OLD_TREE variable near the top of the x11vnc.c file. - See the [30]FAQ below for information about where you might obtain a + See the [37]FAQ below for information about where you might obtain a precompiled x11vnc binary from 3rd parties. To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix) - try here: - * [31]http://www.tightvnc.com/download.html - * [32]http://www.realvnc.com/download-free.html - * [33]http://sourceforge.net/projects/cotvnc/ + try these links: + * [38]http://www.tightvnc.com/download.html + * [39]http://www.realvnc.com/download-free.html + * [40]http://sourceforge.net/projects/cotvnc/ + More tools: Here is a rsh/ssh wrapper script rx11vnc that attempts to automatically do the above Steps 1-3 for you (provided you have rsh/ssh login permission on the machine x11vnc is to be run on). The - above example would be: rx11vnc far-away.east:0 typed into a shell on - sitting-here.west. Also included is an experimental script rx11vnc.pl - that attempts to tunnel the vnc traffic through an ssh port + above example would be: "rx11vnc far-away.east:0" typed into a shell + on sitting-here.west. Also included is an experimental script + rx11vnc.pl that attempts to tunnel the vnc traffic through an ssh port redirection (and does not assume port 5900 is free). Have a look at them to see what they do and customize as needed: - * [34]rx11vnc wrapper script - * [35]rx11vnc.pl wrapper script to tunnel traffic thru ssh + * [41]rx11vnc wrapper script + * [42]rx11vnc.pl wrapper script to tunnel traffic thru ssh + _________________________________________________________________ Building x11vnc: @@ -343,54 +355,64 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. Note: Currently gcc is required to build libvncserver. In some cases it will build with non-gcc compilers, but the resulting binary often - fails to run properly. + fails to run properly. For Solaris pre-built gcc binaries are at + [43]http://www.sunfreeware.com/ + + _________________________________________________________________ - Building on Solaris: Depending on your version of Solaris (or other - Unix OS), the jpeg and/or zlib libraries may be in non-standard places - (e.g. /usr/local, /usr/sfw, /opt/sfw, etc). + Building on Solaris, FreeBSD, etc: Depending on your version of + Solaris or other Unix OS the jpeg and/or zlib libraries may be in + non-standard places (e.g. /usr/local, /usr/sfw, /opt/sfw, etc). Note: If configure cannot find these two libraries then TightVNC and - ZRLE encoding support will be disabled, and you don't want that! (the + ZRLE encoding support will be disabled, and you don't want that! The TightVNC encoding gives very good compression and performance, it even - makes a noticeable difference over a fast LAN) + makes a noticeable difference over a fast LAN. + Shortcut: On Solaris 10 you can pick up everything just by insuring that your PATH has /usr/sfw/bin (for gcc) and /usr/ccs/bin (for other build tools), e.g.: - env PATH=/usr/sfw/bin:/usr/ccs/bin:$PATH sh -c './configure; make' libjpeg is included in Solaris 9 and later (/usr/sfw/include and /usr/sfw/lib), and zlib in Solaris 8 and later (/usr/include and - /usr/lib). - - So on Solaris 9 you can pick up everything with something like this: + /usr/lib). So on Solaris 9 you can pick up everything with something + like this: env PATH=/usr/local/bin:/usr/ccs/bin:$PATH CPPFLAGS='-I /usr/sfw/include' LDF LAGS='-L/usr/sfw/lib -R/usr/sfw/lib' sh -c './configure; make' - assuming your gcc is in /usr/local/bin. That is getting pretty long, - see those assignments split up in the build script below. + assuming your gcc is in /usr/local/bin. Or starting with the 0.7.1 + x11vnc release: + env PATH=/usr/local/bin:/usr/ccs/bin:$PATH sh -c './configure --with-jpeg=/us +r/sfw; make' + + These are getting pretty long, see those assignments split up in the + build script below. - If your system does not have these libraries you can get the source - for these libraries to build them: libjpeg is available at - [36]ftp://ftp.uu.net/graphics/jpeg/ and zlib at - [37]http://www.gzip.org/zlib/. See also - [38]http://www.sunfreeware.com/ for Solaris binary packages of these + + If your system does not have these libraries at all you can get the + source for the libraries to build them: libjpeg is available at + [44]ftp://ftp.uu.net/graphics/jpeg/ and zlib at + [45]http://www.gzip.org/zlib/. See also + [46]http://www.sunfreeware.com/ for Solaris binary packages of these libraries as well as for gcc. Normally they will install into /usr/local. + Here is a build script that indicates one way to pass the library locations information to the libvncserver configuration via the - CPPFLAGS and LDFLAGS environmental variables: + CPPFLAGS and LDFLAGS environmental variables. #!/bin/sh # Build script for Solaris, etc, with gcc, libjpeg and libz in # non-standard locations. -PATH=/path/to/gcc/bin:/usr/ccs/bin:$PATH # set to get your gcc +# set to get your gcc, etc: +PATH=/path/to/gcc/bin:/usr/ccs/bin:/usr/sfw/bin:$PATH -JPEG=/path/to/jpeg # maybe "/usr/local", "/usr/sfw", or "/opt/sfw" -ZLIB=/path/to/zlib # maybe "/usr/local", "/usr/sfw", or "/opt/sfw" +JPEG=/path/to/jpeg # set to maybe "/usr/local", "/usr/sfw", or "/opt/sfw" +ZLIB=/path/to/zlib # set to maybe "/usr/local", "/usr/sfw", or "/opt/sfw" # Below we assume headers in $JPEG/include and $ZLIB/include and the # shared libraries are in $JPEG/lib and $ZLIB/lib. If your situation @@ -403,11 +425,6 @@ LDFLAGS="-L $JPEG/lib -R $JPEG/lib -L $ZLIB/lib -R $ZLIB/lib" CPPFLAGS="$CPPFLAGS -I /usr/openwin/include" LDFLAGS="$LDFLAGS -L /usr/openwin/lib -R /usr/openwin/lib" -# This only applies to Solaris 10 or later (XFIXES, DAMAGE, and RANDR) -CPPFLAGS="$CPPFLAGS -I /usr/X11/include" -LDFLAGS="$LDFLAGS -L /usr/X11/lib -R /usr/X11/lib" -LDFLAGS="$LDFLAGS -L /usr/openwin/sfw/lib -R /usr/openwin/sfw/lib" - # Everything needs to built with _REENTRANT for thread safe errno: CPPFLAGS="$CPPFLAGS -D_REENTRANT" @@ -418,21 +435,37 @@ make ls -l ./x11vnc/x11vnc - Then do make install or copy the binary to your desired destination. + Then do make install or copy the x11vnc binary to your desired + destination. + + BTW, To run a shell script, just cut-and-paste the above into a file, + say "myscript", then modify the "/path/to/..." items to correspond to + your system/environment, and then type: "sh myscript" to run it. Note that on Solaris make is /usr/ccs/bin/make, so that is why the above puts /usr/ccs/bin in PATH. Other important build utilities are there too: ld, ar, etc. Also, it is probably a bad idea to have /usr/ucb in your PATH while building. + Starting with the 0.7.1 x11vnc release the "configure --with-jpeg=DIR + --with-zlib=DIR" options are handy if you want to avoid making a + script. + One user had a problem where the above build script was failing because his work environment had the ENV variable set to a script that was resetting his PATH so that gcc could no longer be found. Make sure you do not have any ENV or BASH_ENV in your environment doing things like that. - If you need to build on Solaris 2.5.1 or earlier, see [39]this - workaround FAQ. + If you need to build on Solaris 2.5.1 or earlier or other older Unix + OS's, see [47]this workaround FAQ. + + Building on FreeBSD, OpenBSD, ...: The jpeg libraries seem to be in + /usr/local or /usr/pkg on these OS's. You won't need the openwin stuff + in the above script (but you may need /usr/X11R6/...). Also starting + with the 0.7.1 x11vnc release, this usually works: + ./configure --with-jpeg=/usr/local + make Building on HP-UX: For jpeg and zlib you will need to do the same sort of thing as described above for Solaris. You set CPPFLAGS and @@ -440,7 +473,8 @@ ls -l ./x11vnc/x11vnc /usr/openwin stuff. Also, HP-UX does not seem to support -R, so get rid of the -R items in LDFLAGS. Because of this, at runtime you may need to set LD_LIBRARY_PATH to indicate the directory paths so the - libraries can be found. + libraries can be found. Starting with the 0.7.1 x11vnc release the + configure --with-jpeg=DIR --with-zlib=DIR options are handy. Finally, there seems to be a bug with gcc on HP-UX 11.xx: something fails (in the gcc private header files?) and it thinks it cannot find @@ -461,11 +495,11 @@ ls -l ./x11vnc/x11vnc protocol.) I suggest using xsetroot, dtstyle or similar utility to set a solid background while using x11vnc. You can turn the pretty background image back on when you are using the display directly. - Update: As of Feb/2005 in the libvncserver CVS, x11vnc has the -solid - [color] option that works on recent GNOME and KDE and also on classic - X (background image is on the root window). + Update: As of Feb/2005 in the libvncserver CVS, x11vnc has the + [48]-solid [color] option that works on recent GNOME, KDE, and CDE and + also on classic X (background image is on the root window). - I also find the [40]tightvnc encoding gives the best response for my + I also find the [49]TightVNC encoding gives the best response for my usage (Unix <-> Unix over cable modem). One needs a tightvnc-aware vncviewer to take advantage of this encoding. @@ -477,14 +511,16 @@ ls -l ./x11vnc/x11vnc is X11's default listening port). Had port 5900 been taken by some other application, x11vnc would have next tried 5901. That would mean the viewer command above should be changed to vncviewer - far-away.east:1. You can force the issue with the "-rfbport NNNN" - option where NNNN is the desired port number. + far-away.east:1. You can force the issue with the "[50]-rfbport NNNN" + option where NNNN is the desired port number. If that port is already + taken, x11vnc will exit immediately. (also see the "SunRay Gotcha" + note below) Options: x11vnc has (far too) many features that may be activated - via its [41]command line options. Useful options are -nap to use fewer + via its [51]command line options. Useful options are -nap to use fewer resources (it sleeps more between polls when activity is low) and -rfbauth passwd-file to use VNC password protection (the vncpasswd or - storepasswd programs, or the x11vnc [42]-storepasswd option can be + storepasswd programs, or the x11vnc [52]-storepasswd option can be used to create the password file). Algorithm: How does x11vnc do it? Rather brute-forcedly: it @@ -494,8 +530,8 @@ ls -l ./x11vnc/x11vnc libvncserver compresses the changes and sends them off to any connected VNC viewers. A number of applications do similar things, such as x0rfbserver, krfb, x0vncserver. x11vnc uses a 32 x 32 pixel - tile model (the desktop is decomposed into ~1000 such tiles), where - changed tiles are found by pseudo-randomly polling 1 pixel tall + 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 @@ -508,16 +544,16 @@ ls -l ./x11vnc/x11vnc first testing out the programs. You get an interesting "feedback" effect where vncviewer images keep popping up each one contained in the previous one and slightly shifted a bit by the window manager - decorations. There will be an [43]even more interesting effect if + decorations. There will be an [53]even more interesting effect if -scale is used. Also, if the XKEYBOARD is supported and the XBell "beeps" once, you get an infinite loop of beeps going off. Although all of this is mildly exciting it is not much use: you will normally run and display the viewer on a different machine! SunRay notes: You can run x11vnc on your (connected or disconnected) - [44]SunRay session (Please remember to use -nap and maybe -wait 200 to - avoid being a resource hog! It also helps a bit to have a solid - background color). You have to know the name of the machine your + [54]SunRay session (Please remember to use [55]-nap and maybe + [56]-wait 200 to avoid being a resource hog! It also helps to have a + solid background color). You have to know the name of the machine your SunRay session X server is running on. You also need to know the X11 DISPLAY number for the session: on a SunRay it could be a large number, e.g. :137, since there are many people with X sessions (Xsun @@ -527,6 +563,11 @@ ls -l ./x11vnc/x11vnc server machine has your session, you could login to all possible ones looking at the who output for your username...). + I put some code in my ~/.xsession script that stores $DISPLAY in my + ~/.sunray_current file at session startup and deletes it when the + session ends to make it easy to get at the hostname and X11 display + number info for my current X sessions. + SunRay Gotcha #1: Note that even though your SunRay X11 DISPLAY is something like :137, x11vnc still tries for port 5900 as its listening port if it can get it, in which case the VNC display (i.e. the @@ -534,7 +575,24 @@ ls -l ./x11vnc/x11vnc sunray-server:0 (note the :0 corresponding to port 5900, it is not :137). If it cannot get 5900, it tries for 5901, and so on. You can also try to force the port (and thereby the VNC display) using the - -rfbport NNNN option. + [57]-rfbport NNNN option. + + SunRay Gotcha #2: If you get an error like: + shmget(tile) failed. + shmget: No space left on device + + when starting up x11vnc that most likely means all the shared memory + (shm) slots are filled up on your machine. The Solaris default is only + 100, and that can get filled up in a week or so on a SunRay server + with lots of users. If the shm slot is orphaned (e.g. creator process + dies) the slot is not reclaimed. You can view the shm slots with the + "ipcs -mA" command. If there are about 100 then you've probably hit + this problem. They can be cleaned out (by the owner or by root) using + the ipcrm command. I wrote a script [58]shm_clear that finds the + orphans and lists or removes them. Longer term, have your SunRay + sysadmin add something like this to /etc/system: + set shmsys:shminfo_shmmax = 0x2000000 + set shmsys:shminfo_shmmni = 0x1000 Limitations: @@ -549,10 +607,11 @@ ls -l ./x11vnc/x11vnc * A rate limiting factor for x11vnc performance is that video hardware is optimized for writing, not reading (x11vnc reads the video framebuffer for the screen image data). The difference can - be a factor of 10-200, and it usually takes about 0.5-1 sec to - read in the whole video hardware framebuffer (5MB for 1280x1024 at - depth 24). So whenever activity changes most of the screen there - is a delay of 0.5-1 sec while x11vnc reads the changed regions in. + be a factor of 10 to 1000, and so it usually takes about 0.5-1 sec + to read in the whole video hardware framebuffer (e.g. 5MB for + 1280x1024 at depth 24). So whenever activity changes most of the + screen (e.g. moving a large window) there is a delay of 0.5-1 sec + while x11vnc reads the changed regions in. To get a sense of the read and write speeds of your video card, you can run the benchmarks like: x11perf -getimage500, x11perf -putimage500, x11perf -shmput500 and for XFree86 displays with @@ -574,15 +633,15 @@ ls -l ./x11vnc/x11vnc * Somewhat surprisingly, the X11 mouse (cursor) shape is write-only and cannot be queried from the X server. So in x11vnc the cursor shape stays fixed at an arrow. (see the "-cursor X" and "-cursor - some", however, for a partial hack for the root window, etc.). - Also, on Solaris using the SUN_OVL overlay extension, x11vnc can - show the correct mouse cursor when the -overlay option is also - supplied. A similar thing is done on IRIX as well when -overlay is - supplied. As of Dec/2004 x11vnc supports the XFIXES extension (in - Xorg and Solaris 10) to query the X server for the exact cursor - shape, this works pretty well except that cursors with - transparency (alpha channel) need to approximated to solid RGB - values. + some" [59]options, however, for a partial hack for the root + window, etc.). Also, on Solaris using the SUN_OVL overlay + extension, x11vnc can show the correct mouse cursor when the + [60]-overlay option is also supplied. A similar thing is done on + IRIX as well when -overlay is supplied. As of Dec/2004 x11vnc + supports the XFIXES extension (in Xorg and Solaris 10) to query + the X server for the exact cursor shape, this works pretty well + except that cursors with transparency (alpha channel) need to + approximated to solid RGB values. * Audio from applications is of course not redirected (separate redirectors do exist, e.g. esd). The XBell() "beeps" will work if the X server supports the XKEYBOARD extension. (Note that on @@ -592,7 +651,7 @@ ls -l ./x11vnc/x11vnc Evidently a timing related bug and difficult to reproduce... * Using -threads can expose some bugs in libvncserver. - Please feel free to [45]contact me if you have any questions, + Please feel free to [61]contact me if you have any questions, problems, or comments about x11vnc, etc. _________________________________________________________________ @@ -601,243 +660,251 @@ ls -l ./x11vnc/x11vnc [Building and Starting] - [46]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed + [62]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed (null)" or "Xlib: connection to ":0.0" refused by server" and then exits. What do I need to do? - [47]Q-2: I can't get x11vnc and/or libvncserver to compile. + [63]Q-2: I can't get x11vnc and/or libvncserver to compile. - [48]Q-3: Help, I need to run x11vnc on Solaris 2.5.1 and it doesn't + [64]Q-3: Help, I need to run x11vnc on Solaris 2.5.1 and it doesn't compile! - [49]Q-4: Where can I get a precompiled x11vnc binary for my Operating + [65]Q-4: Where can I get a precompiled x11vnc binary for my Operating System? - [50]Q-5: Where can I get a VNC Viewer binary (or source code) for the + [66]Q-5: Where can I get a VNC Viewer binary (or source code) for the Operating System I will be viewing from? - [51]Q-6: How can I see all of x11vnc's command line options and + [67]Q-6: How can I see all of x11vnc's command line options and documentation on how to use them? - [52]Q-7: I don't like typing arcane command line options every time I + [68]Q-7: I don't like typing arcane command line options every time I start x11vnc. What can I do? Is there a config file? Or a GUI? - [53]Q-8: Can I make x11vnc more quiet and also go into the background + [69]Q-8: Can I make x11vnc more quiet and also go into the background after starting up? - [54]Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies + [70]Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with the error message like: "Broken pipe". I'm using the -forever mode and I want x11vnc to keep running. [Win2VNC Related] - [55]Q-10: I have two separate machine displays in front of me, one + [71]Q-10: I have two separate machine displays in front of me, one Windows the other X11: can I use x11vnc in combination with Win2VNC in dual-screen mode to pass the keystrokes and mouse motions to the X11 display? - [56]Q-11: I am running Win2VNC on my windows machine and trying to - create a dual-screen mode with my second display by running "x11vnc - -nofb". Whenever I initiate the connection Win2VNC quickly disconnects - and x11vnc says something like: rfbProcessClientNormalMessage: read: - Connection reset by peer + [72]Q-11: I am running Win2VNC on my Windows machine and I'm trying to + create a dual-screen mode with my second display monitor by running + "x11vnc -nofb". Whenever I initiate the connection Win2VNC quickly + disconnects and x11vnc says something like: + rfbProcessClientNormalMessage: read: Connection reset by peer [Color Issues] - [57]Q-12: The X display I run x11vnc on is only 8 bits per pixel (bpp) + [73]Q-12: The X display I run x11vnc on is only 8 bits per pixel (bpp) PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while the colors are incorrect in certain windows. - [58]Q-13: Color problems: Why are the colors for some windows messed + [74]Q-13: Color problems: Why are the colors for some windows messed up in x11vnc? BTW, I have an X display that has nice overlay/multi-depth visuals of different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - [59]Q-14: How do I figure out the window id to supply to the -id + [75]Q-14: How do I figure out the window id to supply to the -id windowid option? - [60]Q-15: Why don't menus or other transient windows come up when I am + [76]Q-15: Why don't menus or other transient windows come up when I am using the -id windowid option to view a single application window? - [61]Q-16: My X display is depth 24 at 24bpp (instead of the normal + [77]Q-16: My X display is depth 24 at 24bpp (instead of the normal depth 24 at 32bpp). I'm having lots of color and visual problems with - x11vnc and vncviewer. + x11vnc and vncviewer. What's up? [Xterminals] - [62]Q-17: Can I use x11vnc to view and interact with an Xterminal + [78]Q-17: Can I use x11vnc to view and interact with an Xterminal (e.g. NCD) that is not running UNIX and so x11vnc cannot be run on it directly? - [63]Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for + [79]Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a Unix/Linux machine acting as an Xterminal? [Remote Control] - [64]Q-19: How do I stop x11vnc once it is running in the background? + [80]Q-19: How do I stop x11vnc once it is running in the background? - [65]Q-20: Can I change settings in x11vnc without having to restart - it? Is there a way to remote control it? + [81]Q-20: Can I change settings in x11vnc without having to restart + it? I.e., is there a way to remote control it? [Security and Permissions] - [66]Q-21: Why does x11vnc exit as soon as the VNC viewer disconnects? + [82]Q-21: How do I create a VNC password for use with x11vnc? + + [83]Q-22: Can I have two passwords for VNC viewers, one for full + access and the other for view-only access to the display? + + [84]Q-23: Can I fine tune what types of user input are allowed? E.g. + have some users just be able to move the mouse, but not click or type + anything? + + [85]Q-24: Why does x11vnc exit as soon as the VNC viewer disconnects? And why doesn't it allow more than one VNC viewer to connect at the same time? - [67]Q-22: Can I limit which machines incoming VNC clients can connect + [86]Q-25: Can I limit which machines incoming VNC clients can connect from? - [68]Q-23: How do I build x11vnc/libvncserver with libwrap + [87]Q-26: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) support? - [69]Q-24: Can I prompt the user at the local X display whether the - incoming VNC client should be accepted or not? Can I decide to make - some clients view-only? How about running an arbitrary program to make - the decisions? - - [70]Q-25: How do I create a VNC password for use with x11vnc? - - [71]Q-26: How can I tunnel my connection to x11vnc via an encrypted + [88]Q-27: How can I tunnel my connection to x11vnc via an encrypted SSH channel between two Unix machines? - [72]Q-27: How can I tunnel my connection to x11vnc via an encrypted + [89]Q-28: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [73]Q-28: Does x11vnc support Unix usernames and passwords? Can I + [90]Q-29: Can I prompt the user at the local X display whether the + incoming VNC client should be accepted or not? Can I decide to make + some clients view-only? How about running an arbitrary program to make + the decisions? + + [91]Q-30: Does x11vnc support Unix usernames and passwords? Can I further limit the set of Unix usernames who can connect to the VNC desktop? - [74]Q-29: Can I have two passwords for VNC viewers, one for full - access and the other for view-only access to the display? + [92]Q-31: I start x11vnc as root because it is launched via inetd(1) + or a display manager like gdm(1). Can I have x11vnc later switch to a + different user? - [75]Q-30: I use a screen-lock when I leave my workstation (e.g. + [93]Q-32: I use a screen-lock when I leave my workstation (e.g. xscreensaver or xlock). When I remotely access my workstation desktop via x11vnc I can unlock the desktop fine, but I am worried people will see my activities on the physical monitor. What can I do to prevent this, or at least make it more difficult? - [76]Q-31: Can I have x11vnc automatically lock the screen when I + [94]Q-33: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? [Display Managers and Services] - [77]Q-32: How can I run x11vnc as a "service" that is always + [95]Q-34: How can I run x11vnc as a "service" that is always available? - [78]Q-33: How can I use x11vnc to connect to an X login screen like + [96]Q-35: How can I use x11vnc to connect to an X login screen like xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X session yet). - [79]Q-34: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + [97]Q-36: Can I run x11vnc out of inetd(1)? How about xinetd(1)? - [80]Q-35: How do I make x11vnc work with the Java VNC viewer applet in + [98]Q-37: How do I make x11vnc work with the Java VNC viewer applet in a web browser? - [81]Q-36: Are reverse connections (i.e. the VNC server connecting to + [99]Q-38: Are reverse connections (i.e. the VNC server connecting to the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported? [Resource Usage and Performance] - [82]Q-37: I have lots of memory, but why does x11vnc fail with + [100]Q-39: I have lots of memory, but why does x11vnc fail with shmget: No space left on device or Minor opcode of failed request: 1 (X_ShmAttach)? - [83]Q-38: How can I make x11vnc use less system resources? + [101]Q-40: How can I make x11vnc use less system resources? - [84]Q-39: How can I make x11vnc use MORE system resources? + [102]Q-41: How can I make x11vnc use MORE system resources? - [85]Q-40: I use x11vnc over a slow link with high latency (e.g. dialup - modem), is there anything I can do to speed things up? + [103]Q-42: I use x11vnc over a slow link with high latency (e.g. + dialup modem), is there anything I can do to speed things up? - [86]Q-41: When I drag windows around with the mouse or scroll up and + [104]Q-43: 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? [Mouse Cursor Shapes] - [87]Q-42: Why isn't the mouse cursor shape (the little icon shape + [105]Q-44: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? - [88]Q-43: When using XFIXES cursorshape mode, some of the cursors look - really bad with extra black borders around the cursor and other cruft. - How can I improve their appearance? + [106]Q-45: When using XFIXES cursorshape mode, some of the cursors + look really bad with extra black borders around the cursor and other + cruft. How can I improve their appearance? - [89]Q-44: In XFIXES mode, are there any hacks to handle cursor + [107]Q-46: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? [Mouse Pointer] - [90]Q-45: Why does the mouse arrow just stay in one corner in my + [108]Q-47: Why does the mouse arrow just stay in one corner in my vncviewer, whereas my cursor (that does move) is just a dot? - [91]Q-46: Can I take advantage of the TightVNC extension to the VNC + [109]Q-48: Can I take advantage of the TightVNC extension to the VNC protocol where Cursor Positions Updates are sent back to all connected clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - [92]Q-47: Is it possible to swap the mouse buttons (e.g. left-handed + [110]Q-49: Is it possible to swap the mouse buttons (e.g. left-handed operation), or arbitrarily remap them? How about mapping button clicks to keystrokes, e.g. to partially emulate Mouse wheel scrolling? [Keyboard Issues] - [93]Q-48: How can I get my AltGr and Shift modifiers to work between + [111]Q-50: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - [94]Q-49: When I try to type a "<" (i.e. less than) instead I get ">" + [112]Q-51: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! - [95]Q-50: I'm using an "international" keyboard (e.g. German "de", or + [113]Q-52: I'm using an "international" keyboard (e.g. German "de", or Danish "dk") and the -modtweak mode works well if the VNC viewer is run on a Unix/Linux machine with a similar keyboard. But if I run the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or Windows with any keyboard, I can't type some keys like: "@", "$", "<", ">", etc. How can I fix this? - [96]Q-51: When typing I sometimes get double, triple, or more of my + [114]Q-53: When typing I sometimes get double, triple, or more of my keystrokes repeated. I'm sure I only typed them once, what can I do? - [97]Q-52: The x11vnc -norepeat mode is in effect, but I still get + [115]Q-54: The x11vnc -norepeat mode is in effect, but I still get repeated keystrokes!! - [98]Q-53: The machine where I run x11vnc has an AltGr key, but the + [116]Q-55: The machine where I run x11vnc has an AltGr key, but the local machine where I run the VNC viewer does not. Is there a way I can map a local unused key to send an AltGr? How about a Compose key as well? - [99]Q-54: I have a Sun machine I run x11vnc on. Its Sun keyboard has + [117]Q-56: I have a Sun machine I run x11vnc on. Its Sun keyboard has just one Alt key labelled "Alt" and two Meta keys labelled with little diamonds. The machine where I run the VNC viewer only has Alt keys. How can I send a Meta keypress? (e.g. emacs needs this) - [100]Q-55: Can I map a keystroke to a mouse button click on the remote + [118]Q-57: Can I map a keystroke to a mouse button click on the remote machine? [Screen Related Issues and Features] - [101]Q-56: The remote display is larger (in number of pixels) than the + [119]Q-58: The remote display is larger (in number of pixels) than the local display I am running the vncviewer on. I don't like the vncviewer scrollbars, what I can do? - [102]Q-57: Does x11vnc support server-side framebuffer scaling? (E.g. + [120]Q-59: Does x11vnc support server-side framebuffer scaling? (E.g. to make the desktop smaller). - [103]Q-58: Does x11vnc work with Xinerama? (i.e. multiple monitors + [121]Q-60: Does x11vnc work with Xinerama? (i.e. multiple monitors joined together to form one big, single screen). - [104]Q-59: Can I use x11vnc on a multi-headed display that is not + [122]Q-61: Can I use x11vnc on a multi-headed display that is not Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? - [105]Q-60: Does x11vnc support the XRANDR (X Resize, Rotate and + [123]Q-62: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) extension? Whenever I rotate or resize the screen x11vnc just seems to crash. - [106]Q-61: Why is the view in my VNC viewer completely black? Or why + [124]Q-63: Why is the view in my VNC viewer completely black? Or why is everything flashing around randomly? - [107]Q-62: I use Linux Virtual Consoles (VC's) to implement 'Fast User + [125]Q-64: I use Linux Virtual Consoles (VC's) to implement 'Fast User Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7, Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those keystrokes to switch between their sessions). How come the view in a @@ -845,19 +912,22 @@ ls -l ./x11vnc/x11vnc otherwise all messed up unless the X session x11vnc is attached to is in the active VC? - [108]Q-63: I am using x11vnc where my local machine has "popup/hidden + [126]Q-65: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars interfere and fight with each other in strange ways. What can I do? - [Misc: Clipboard, Beeps, etc.] + [Misc: Clipboard, Beeps, Thanks, etc.] - [109]Q-64: Does the Clipboard/Selection get transferred between the + [127]Q-66: Does the Clipboard/Selection get transferred between the vncviewer and the X display? - [110]Q-65: Why don't I hear the "Beeps" in my X session (e.g. when + [128]Q-67: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? + + [129]Q-68: Thanks for your program and for your help! Can I make a + donation? _________________________________________________________________ @@ -869,18 +939,18 @@ ls -l ./x11vnc/x11vnc For the former error, you need to specify the X display to connect to (it also needs to be on the same machine x11vnc is to run on). Set - your DISPLAY environment variable or use the -display option to + your DISPLAY environment variable or use the [130]-display option to specify it. Nearly always the correct value will be ":0" For the latter error, you need to set up the X11 permissions correctly. See the xauth(1), Xsecurity(7), and xhost(1) man pages for much info. For example, you may need to set your XAUTHORITY - environment variable or use the -auth option to point to the correct - cookie file (e.g. /home/joe/.Xauthority or /var/gdm/:0.Xauth), or - simply be sure you run x11vnc as the correct user (i.e. the user who - owns the X session you wish to view). Running x11vnc as root is not - enough: you need to know where the XAUTHORITY file for the desired X - display is. Example: + environment variable or use the [131]-auth option to point to the + correct cookie file (e.g. /home/joe/.Xauthority or /var/gdm/:0.Xauth), + or simply be sure you run x11vnc as the correct user (i.e. the user + who owns the X session you wish to view). Running x11vnc as root is + not enough: you need to know where the XAUTHORITY file for the desired + X display is. Example: x11vnc -display :0 -auth /var/gdm/:0.Xauth Less safe, but to avoid figuring out where the XAUTHORITY file is, if @@ -889,11 +959,11 @@ ls -l ./x11vnc/x11vnc 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 -users option). + documentation on the [132]-users option). Some Linux distributions or display managers may set XAUTHORITY to a random local filename. You need to dig out where they have hidden the - MIT-MAGIC-COOKIE file (and set XAUTHORITY to it or use the -auth + MIT-MAGIC-COOKIE file (and set XAUTHORITY to it or use the [133]-auth option). This command is often useful to find non-standard settings for XAUTHORITY: ps wwwweaux | tr ' ' '\n' | grep XAUTHORITY | sort -u @@ -963,8 +1033,8 @@ ls -l ./x11vnc/x11vnc earlier and perhaps non-Solaris): First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the - above [111]Solaris build script to run the configure command. That - should succeed without failure. Then, you have to hand edit the + above [134]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 lines: @@ -991,14 +1061,13 @@ typedef unsigned int in_addr_t; Then run make with the Solaris build script environment, everything should compile without problems, and the resulting x11vnc binary - should work OK (but note the workaround for XConvertCase in x11vnc.c - only covers Latin 1). If some non-x11vnc related programs fail (e.g. - test programs) and the x11vnc binary is not created try "make -k". - Similar sorts of kludges can be done on other older OS (Solaris, - Linux, ...) releases. + should work OK. If some non-x11vnc related programs fail (e.g. test + programs) and the x11vnc binary is not created try "make -k" to have + it keep going. Similar sorts of kludges in rfb/rfbconfig.h can be done + on other older OS (Solaris, Linux, ...) releases. Here are some notes for similar steps that need to be done to build on - [112]SunOS 4.x + [135]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 @@ -1007,19 +1076,19 @@ typedef unsigned int in_addr_t; Q-4: Where can I get a precompiled x11vnc binary for my Operating System? - Hopefully the [113]build steps above and [114]FAQ provide enough info + Hopefully the [136]build steps above and [137]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 made by other groups available - at the following locations: - Debian: (.deb) [115]http://packages.debian.org/x11vnc + There are precompiled x11vnc binaries built by other groups that are + available at the following locations: + Debian: (.deb) [138]http://packages.debian.org/x11vnc - Slackware: (.tgz) [116]http://www.linuxpackages.net/ Redhat/Fedora: - (.rpm) [117]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) - [118]http://www.sunfreeware.com/ wwexptools: (.tgz) - [119]http://www.bell-labs.com/project/wwexptools/packages.html The + Slackware: (.tgz) [139]http://www.linuxpackages.net/ Redhat/Fedora: + (.rpm) [140]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) + [141]http://www.sunfreeware.com/ wwexptools: (.tgz) + [142]http://www.bell-labs.com/project/wwexptools/packages.html The last one, wwexptools, provides a variety of Unix binaries (Linux, Solaris, HP-UX, IRIX, ...) with the intent of being compatible on a wide range of OS releases. Find x11vnc near the bottom of that page @@ -1031,16 +1100,14 @@ typedef unsigned int in_addr_t; this by looking at the x11vnc output and if it says the encoding for a client is "hextile" then likely the fast compression encodings are missing. If you want optimal performance on your OS, you should see - the [120]build notes above for where to download libz and libjpeg, and + the [143]build notes above for where to download libz and libjpeg, and then build everything with gcc. For Solaris, the http://www.sunfreeware.com/ packages are built with libz and libjpeg. If the above binaries don't work and building x11vnc on your OS fails (and all else fails!) you can try one of my motley collection of - [121]test binaries. Some may be old, some may have extra debugging - output, etc. They may work on your OS, but please understand they are - test/experimental binaries not intended for general usage like the - above precompiled ones from 3rd parties. + [144]test binaries. Some may be old, some may have extra debugging + output, etc. They may work on your OS. As a general note, the x11vnc program is simple enough you don't really need to install a package: the binary will in most cases work @@ -1059,16 +1126,16 @@ typedef unsigned int in_addr_t; To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix) try here: - * [122]http://www.tightvnc.com/download.html - * [123]http://www.realvnc.com/download-free.html - * [124]http://sourceforge.net/projects/cotvnc/ + * [145]http://www.tightvnc.com/download.html + * [146]http://www.realvnc.com/download-free.html + * [147]http://sourceforge.net/projects/cotvnc/ Q-6: How can I see all of x11vnc's command line options and documentation on how to use them? Run: x11vnc -opts to list just the option names or run: x11vnc -help for long descriptions about each option. The output is listed - [125]here as well. + [148]here as well. Q-7: I don't like typing arcane command line options every time I start x11vnc. What can I do? Is there a config file? Or a GUI? @@ -1081,8 +1148,8 @@ typedef unsigned int in_addr_t; # x11vnc -nap -wait 50 -localhost -rfbauth $HOME/.vnc/passwd -display :0 $* - a similar thing can be via aliases in your shell (bash, tcsh, csh, - etc..). + a similar thing can be done via aliases in your shell (bash, tcsh, + csh, etc..). Or as of Jun/2004 in the libvncserver CVS you can use the simple $HOME/.x11vncrc config file support. If that file exists, each line is @@ -1100,18 +1167,18 @@ display :0 GUI based on the remote-control functionality that was added. It's not particularly user-friendly, it just provides a point and click mode to set all the many x11vnc parameters and obtain help on them. See the - -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. + [149]-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. Q-8: Can I make x11vnc more quiet and also go into the background after starting up? - Use the -q and -bg options, respectively. (also: -quiet is an alias - for -q) + Use the [150]-q and [151]-bg options, respectively. (also: -quiet is + an alias for -q) Note that under -bg the stderr messages will be lost unless you use - the "-o logfile" option. + the "[152]-o logfile" option. Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with the error message like: "Broken pipe". I'm using the -forever mode and @@ -1121,10 +1188,10 @@ display :0 So if a viewer client terminates abruptly, libvncserver will notice on the next I/O operation and will close the connection and continue on. - As of Apr/2004 the above fix only works for BSD signal systems (Linux, - FreeBSD, ...) For SYSV systems there is a workaround in my - [126]x11vnc.c file. It also has an option -sigpipe exit to have x11vnc - clean up and exit upon receiving SIGPIPE. + Up until of Apr/2004 the above fix only works for BSD signal systems + (Linux, FreeBSD, ...) For SYSV systems there is a workaround in my + [153]x11vnc.c file. It also has an [154]option -sigpipe exit to have + x11vnc clean up and exit upon receiving SIGPIPE. [Win2VNC Related] @@ -1133,29 +1200,29 @@ 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 "-nofb" option + Yes, for best response start up x11vnc with the "[155]-nofb" option (disables framebuffer polling, and does other optimizations) on the - secondary display (X11). Then start up Win2VNC on the primary display - (Windows) referring it to the secondary display. + 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 [127]x2vnc, however you would + This will also work X11 to X11 using [156]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: - * [128]Original Win2VNC - * [129]Enhanced Win2VNC and [130]sourceforge link - * [131]x2vnc - * [132]x2x also [133]here - * [134]zvnc (MorphOS) + * [157]Original Win2VNC + * [158]Enhanced Win2VNC and [159]sourceforge link + * [160]x2vnc + * [161]x2x also [162]here + * [163]zvnc (MorphOS) - All of them (except x2x) will work with x11vnc. + All of them will work with x11vnc (except x2x where it is not needed). - Q-11: I am running Win2VNC on my windows machine and trying to create - a dual-screen mode with my second display by running "x11vnc -nofb". - Whenever I initiate the connection Win2VNC quickly disconnects and - x11vnc says something like: rfbProcessClientNormalMessage: read: - Connection reset by peer + Q-11: I am running Win2VNC on my Windows machine and I'm trying to + create a dual-screen mode with my second display monitor by running + "x11vnc -nofb". Whenever I initiate the connection Win2VNC quickly + disconnects and x11vnc says something like: + rfbProcessClientNormalMessage: read: Connection reset by peer Is the default visual of the X display you run x11vnc on low color (e.g. 8 bit per pixel PseudoColor)? (you can run xdpyinfo to check, @@ -1167,9 +1234,9 @@ 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, in the - libvncserver CVS, x11vnc has the -visual option to allow you to force - the framebuffer visual to whatever you want (this usually messes up - the colors unless you are very careful). In this case, the option + libvncserver CVS, x11vnc has the [164]-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: x11vnc -nofb -visual TrueColor -display :0 ... @@ -1183,7 +1250,7 @@ display :0 start out OK, but after a while the colors are incorrect in certain windows. - Use the -flashcmap option to have x11vnc watch for changes in the + Use the [165]-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 @@ -1192,7 +1259,7 @@ display :0 example of this. Consider reconfiguring the system to 16 bpp or depth 24 TrueColor if at all possible. - Also note that in some rare cases the -notruecolor option has + Also note that in some rare cases the [166]-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. @@ -1202,12 +1269,12 @@ display :0 visuals of different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - You may want to review the [135]previous question regarding 8 bpp + You may want to review the [167]previous question regarding 8 bpp PseudoColor. - On some hardware (Sun/SPARC, Sgi), the -overlay option discussed a - couple paragraphs down may solve this for you (you may want to skip to - it directly). + On some hardware (Sun/SPARC, Sgi), the [168]-overlay option discussed + a couple paragraphs down may solve this for you (you may want to skip + to it directly). 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? @@ -1227,8 +1294,8 @@ display :0 :0 Local local_uid@console root /usr/openwin/bin/Xsun -dev /dev/fb defclass TrueColor defdepth 24 - in /etc/dt/config/Xservers (see /usr/dt/config/Xservers). Also look at - the fbconfig(1) and related manpages (e.g. ffbconfig, m64config, + in /etc/dt/config/Xservers (copy /usr/dt/config/Xservers). Also look + at the fbconfig(1) and related manpages (e.g. ffbconfig, m64config, pgxconfig, SUNWjfb_config, etc ...) for hardware framebuffer settings that may achieve the same effect. In general for non-Sun machines, look at the "-cc class" and related options in your X server manpage @@ -1238,9 +1305,10 @@ TrueColor defdepth 24 "Overlay" "24,8" to support multi-depth overlays. For these, use the "-cc 4" X server command line option to get a depth 24 default visual. + 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 -overlay x11vnc option (Aug/2004) to have x11vnc use the + use the [169]-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 @@ -1254,39 +1322,40 @@ TrueColor defdepth 24 somewhat slower than normal mode due to the extra framebuffer manipulations that must be performed. Also, on Solaris there is a bug in that for some popup menus, the windows they overlap will have - painting problems while the popup is up (a workaround is to disable - SaveUnders by passing -su to Xsun, e.g. in your + painting errors (flashing colors) while the popup is up (a workaround + is to disable SaveUnders by passing -su to Xsun, e.g. in your /etc/dt/config/Xservers file). + Still not working? Run xwininfo on the application with the messed up 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 -id option to point x11vnc at the + in this case is to use the [170]-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. Fortunately the -overlay - option works for Solaris machines with overlay visuals where most of - this problem occurs. + for x11vnc to be able to do so in real time. Fortunately the + [171]-overlay option works for Solaris machines with overlay visuals + where most of this problem occurs. Q-14: How do I figure out the window id to supply to the -id windowid option? Run the xwininfo program in a terminal. It will ask you to click on the desired application window. After clicking, it will print out much - information, including the window id. Also, the visual and depth of - the window printed out is often useful in debugging x11vnc - [136]problems. + information, including the window id (e.g. 0x6000010). Also, the + visual and depth of the window printed out is often useful in + debugging x11vnc [172]problems. When using -id windowid, note that some VNC viewers will have problems rendering screens that have a width that is not a multiple of 4. Try to manually adjust the window width before starting x11vnc -id .... - Also, as of Dec/2004 libvncserver CVS you can use "-id pick" to have - x11vnc run xwininfo(1) for you and after you click the window it + Also, as of Dec/2004 libvncserver CVS you can use "[173]-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. @@ -1302,14 +1371,14 @@ TrueColor defdepth 24 be able to see these transient windows. If things are not working and you still want to do the single window - polling, try the -sid windowid option ("shifted" windowid). + polling, try the [174]-sid windowid option ("shifted" windowid). x11vnc is known to crash under both -id and -sid, so both modes are still experimental. Please report any reproducible bugs. Q-16: My X display is depth 24 at 24bpp (instead of the normal depth 24 at 32bpp). I'm having lots of color and visual problems with x11vnc - and vncviewer. + and vncviewer. What's up? First off, depth 24 at 24bpp (bpp=bits-per-pixel) is fairly uncommon and can cause problems in general. It also can be slower than depth 24 @@ -1353,16 +1422,17 @@ TrueColor defdepth 24 You can, but it will likely be very wasteful of network bandwidth 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 to the Xterminal machine. Use the - -display to point the display to that of the Xterminal (you'll of - course need basic X11 permission to do that) and also supply the - -noshm option (this enables the polling over the network). + close as possible network-wise (e.g. same switch) to the Xterminal + machine. Use the [175]-display option to point the display to that of + the Xterminal (you'll of course need basic X11 permission to do that) + and also supply the [176]-noshm option (this enables the polling over + the network). The response will likely be sluggish. 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 - -flipbyteorder if the colors get messed up due to endian byte order - differences. + [177]-flipbyteorder if the colors get messed up due to endian byte + order differences. Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a Unix/Linux machine acting as an Xterminal? @@ -1375,32 +1445,32 @@ TrueColor defdepth 24 the MIT-MAGIC-COOKIE auth file data must be copied to the Xterminal. If $HOME/.Xauthority is exported via NFS (this is insecure of course), then x11vnc can simply pick it up via NFS (you may need to use the - -auth option to point to the correct file). Other options include + [178]-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 - and then perhaps ssh from central-server to xterm123 to start x11vnc. - You can use "xauth -f /path/to/cookie.file list" to examine the - contents of the cookie in a file "/path/to/cookie.file". See the + You can use "xauth -f /path/to/cookie-file list" to examine the + contents of the cookie in a file "/path/to/cookie-file". See the xauth(1) manpage for more details. If the display name needs to be changed between the two hosts, see - [137]this note on the xauth add ... command. + [179]this note on the xauth add ... command. - A less secure option is to run something like "xhost +127.0.0.1" to - allow cookie-free local access for x11vnc. + A less secure option is to run something like "xhost +127.0.0.1" while + sitting at the Xterminal to allow cookie-free local access for x11vnc. If the Xterminal is really stripped down and doesn't have any user accounts, NFS, etc. you'll need to contact your system administrator - to set something up. + to set something up. It can be done! - Not recommended, but as a last resort, you could have x11vnc [138]poll + Not recommended, but as a last resort, you could have x11vnc [180]poll the Xterminal over the network. Note: use of Display Manager (gdm, kdm, ...) auth cookie files (i.e. from /var/..., /tmp/..., or elsewhere) may require modification via xauth(1) to correctly include the display x11vnc refers to (e.g. - "xauth -f cookie.file add :0 . 45be51ae2ce9dfbacd882ab3ef8e96b1", + "xauth -f cookie-file add :0 . 45be51ae2ce9dfbacd882ab3ef8e96b1", where 45be51... was found from an "xauth -f /var/... list") or other reasons. See xauth(1) manpage for full details on how to transfer an MIT-MAGIC-COOKIE between machines and displays. @@ -1411,69 +1481,136 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - As of Dec/2004 in the libvncserver CVS there is a remote control feature. It can change a huge amount of things on the fly: see the - -remote and -query options. To shut down the running x11vnc server - just type "x11vnc -R stop". To disconnect all clients do "x11vnc -R - disconnect:all", etc. + [181]-remote and [182]-query options. To shut down the running x11vnc + server just type "x11vnc -R stop". To disconnect all clients do + "x11vnc -R disconnect:all", etc. - For older versions: If the -forever option has not been supplied, + For older versions: If the [183]-forever option has not been supplied, x11vnc will automatically exit after the first client disconnects. In general 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 -bg option or - shell & operator, then simply press Ctrl-C in the shell where x11vnc - is running to stop it. Potential Gotcha: If somehow your Keypress of - Ctrl-C went through x11vnc to the Xserver that then delivered it to - x11vnc it is possible one or both of the Ctrl or C keys will be left - stuck in the pressed down state in the Xserver. Tapping the stuck key - (either via 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 - -clear_mods and -clear_keys options can be used to release pressed - keys at startup and exit. - - Q-20: Can I change settings in x11vnc without having to restart it? Is - there a way to remote control it? - - Look at the -remote (same as -R) and -query (same as -Q) options added - in the Dec/2004 libvncserver CVS. 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", "x11vnc -R stop", "x11vnc -R disconnect:all", etc.. These - commands do not start a x11vnc server, but rather communicate with one - that is already running. The X display (VNC_CONNECT property) is used - as the communication channel, so the X permissions and DISPLAY must be - set up correctly for communication to be possible. + If you have not put x11vnc in the background via the [184]-bg option + or shell & operator, then simply press Ctrl-C in the shell where + x11vnc is running to stop it. Potential Gotcha: If somehow your + Keypress of Ctrl-C went through x11vnc to the Xserver that then + delivered it to x11vnc it is possible one or both of the Ctrl or C + keys will be left stuck in the pressed 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 [185]-clear_mods option and [186]-clear_keys + option can be used to release pressed keys at startup and exit. + + Q-20: Can I change settings in x11vnc without having to restart it? + I.e., is there a way to remote control it? + + Look at the [187]-remote (same as -R) and [188]-query (same as -Q) + options added in the Dec/2004 libvncserver CVS. 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", "x11vnc -R stop", "x11vnc -R + disconnect:all", etc.. These commands do not start a x11vnc server, + but rather communicate with one that is already running. The X display + (VNC_CONNECT property) is used as the communication channel, so the X + permissions and DISPLAY must be set up correctly for communication to + be possible. There is also a simple tcl/tk gui based on this remote control - mechanism. See the -gui option for more info. + mechanism. See the [189]-gui option for more info. [Security and Permissions] - Q-21: Why does x11vnc exit as soon as the VNC viewer disconnects? And + Q-21: How do I create a VNC password for use with x11vnc? + + You may already have one in $HOME/.vnc/passwd if you have used, say, + the vncserver program from the regular RealVNC or TightVNC packages + (i.e. launching the Xvnc server). Otherwise, you could use the + vncpasswd(1) program from those packages. The libvncserver package + also comes with a simple program: storepasswd in the examples + directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports + the -storepasswd "pass" "file" [190]option, which is the 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: [191]-rfbauth + $HOME/myvncpasswd + + Compared to vncpasswd(1) the latter two methods are a somewhat unsafe + because the password is specified on the command line and so someone + may see it by using ps(1) or looking over your shoulder. Also watch + out for the command winding up in your shell's history file (history + -c is often a way to clear it). + + x11vnc also has the [192]-passwdfile and -passwd/-viewpasswd plain + text (i.e. not obscured like the -rfbauth VNC passwords) password + options. + + Q-22: 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 in the libvncserver CVS there is the + [193]-viewpasswd option to supply the view-only password. Note the + full-access password option [194]-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 + [195]-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 + password. If there is a second line in the file and it is non-blank, + it is taken as the view-only password. (use "__EMPTY__" to supply an + empty one). + + View-only passwords currently do not work for the [196]-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 + encrypted they are really just obscured to avoid "casual" password + stealing. It takes almost no skill to figure out how to extract the + plain text passwords from $HOME/.vnc/passwd since it is very + straight-forward to work out what to do from the VNC source code. + + Q-23: Can I fine tune what types of user input are allowed? E.g. have + some users just be able to move the mouse, but not click or type + anything? + + As of Feb/2005, the [197]-input option allows you to do this. "K", + "M", and "B" stand for Keystroke, Mouse-motion, and Button-clicks, + respectively. The setting: "-input M" makes attached viewers only able + to move the mouse. "-input KMB,M" lets normal clients do everything + and enables view-only clients to move the mouse. + + These settings can also be applied on a per-viewer basis via the + remote control mechanism or the GUI. E.g. x11vnc -R input:hostname:M + + Q-24: Why does x11vnc exit as soon as the VNC viewer disconnects? And why doesn't it allow more than one VNC viewer to connect at the same time? These defaults are simple safety measures to avoid someone unknowingly leaving his X11 desktop exposed (to the internet, say) for long - periods of time. Use the -forever option (aka -many) to have x11vnc - wait for more connections after the first client disconnects. Use the - -shared option to have x11vnc allow multiple clients to connect - simultaneously. + periods of time. Use the [198]-forever option (aka -many) to have + x11vnc wait for more connections after the first client disconnects. + Use the [199]-shared option to have x11vnc allow multiple clients to + connect simultaneously. - Recommended additional safety measures include using ssh ([139]see + Recommended additional safety measures include using ssh ([200]see above), stunnel, or a VPN to authenticate and encrypt the viewer - connections or to at least use the -rfbauth passwd-file [140]option to - use VNC password protection (or [141]-passwdfile) It is up to you to + connections or to at least use the -rfbauth passwd-file [201]option to + use VNC password protection (or [202]-passwdfile) It is up to you to apply these security measures, they will not be done for you automatically. - Q-22: Can I limit which machines incoming VNC clients can connect + Q-25: Can I limit which machines incoming VNC clients can connect from? - Yes, look at the -allow and -localhost options to limit connections by - IP address. E.g. + Yes, look at the [203]-allow and [204]-localhost options to limit + connections by hostname or IP address. E.g. x11vnc -allow 192.168.0.1,192.168.0.2 for those two hosts or @@ -1484,9 +1621,10 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - Note that -localhost is the same as "-allow 127.0.0.1" For more control, build libvncserver with libwrap support - (tcp_wrappers) and then use /etc/hosts.allow. + [205](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) + for complete details. - Q-23: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) + Q-26: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) support? Here is one way to pass this information to the configure script: @@ -1494,27 +1632,81 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - then run make as usual. This requires libwrap and its development package (tcpd.h) to be installed on the build machine. If additional - CPPFLAGS or LDFLAGS options are needed supply them as well. + CPPFLAGS or LDFLAGS options are needed supply them as well using + quotes. The resulting x11vnc then uses libwrap/tcp_wrappers for connections. The service name you will use in /etc/hosts.allow and /etc/hosts.deny is "vnc", e.g.: vnc: 192.168.100.3 .example.com - Note that if you run x11vnc out of [142]inetd you do not need to build + Note that if you run x11vnc out of [206]inetd you do not need to build x11vnc with libwrap support because the /usr/sbin/tcpd reference in /etc/inetd.conf handles the tcp_wrappers stuff. - Q-24: Can I prompt the user at the local X display whether the + Q-27: 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 [207]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. + + Q-28: How can I tunnel my connection to x11vnc via an encrypted SSH + channel from Windows using an SSH client like Putty? + + [208]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 + IP number of the Unix machine with display to be viewed. + * Make sure the SSH protocol is selected and the server port is + correct. + * Under 'Connections/SSH/Tunnels' Add a Local connection with + 'Source port: 5900' and 'Destination: localhost:5900' + * Log into the remote machine by pressing 'Open' and supplying + username, password, etc. + * In that SSH shell, start up x11vnc by typing the command: x11vnc + -display :0 plus any other desired options. + * Finally, start up your VNC Viewer in Windows and enter + 'localhost:0' as the VNC server. + + You can keep all of the settings in a Putty 'Saved Session'. Also, + once everything is working, you can consider putting x11vnc -display + :0 (plus other cmdline options) in the 'Remote command' Putty setting + under 'Connections/SSH'. It is likely possible to script the whole + process in a BAT file including launching the VNC viewer by using the + plink Putty utility. Send us the script if you get that working. + + For extra protection feel free to run x11vnc with the [209]-localhost + and [210]-rfbauth/[211]-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 + access to a gateway machine), then you need to change the above Putty + 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. + + As discussed [212]above another option is to first start the VNC + viewer in "listen" mode, and then launch x11vnc with the + "[213]-connect localhost" option to establish the reverse connection. + In this case a Remote port redirection (not Local) is needed for port + 5500 instead of 5900 (i.e. 'Source port: 5500' and + 'Destination: localhost:5500' for a Remote connection). + + Q-29: Can I prompt the user at the local X display whether the incoming VNC client should be accepted or not? Can I decide to make some clients view-only? How about running an arbitrary program to make the decisions? - Yes, look at the "-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 client is rejected. - See below how to also accept clients view-only. + Yes, look at the "[214]-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 + client is rejected. See below how to also accept clients view-only. The external command will have the RFB_CLIENT_IP environment variable set to the client's numerical IP address, RFB_CLIENT_PORT its port @@ -1529,9 +1721,9 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - 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 -viewonly option has been supplied, - the "View" action will not be present: the whole display is view only - in that case. + mouse on the "View" button. If the [215]-viewonly option has been + supplied, the "View" action will not be present: the whole display is + view only in that case. The popup window times out after 120 seconds, to change this behavior use "-accept popup:N" where N is the number of seconds (use 0 for no @@ -1545,7 +1737,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - 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 [143]ftp://ftp.x.org/ + is available at [216]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 @@ -1584,7 +1776,7 @@ elif [ $rc = 4 ]; then fi exit 1 - Stefan Radman has written a nice dtksh script [144]dtVncPopup for use + Stefan Radman has written a nice dtksh script [217]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. @@ -1594,123 +1786,44 @@ exit 1 updates, etc during this period. (use of -threads may or may not alter this behavior). - To run a command when a client disconnects, use the "-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 + To run a command when a client disconnects, use the "[218]-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"). - Q-25: How do I create a VNC password for use with x11vnc? - - You may already have one in $HOME/.vnc/passwd if you have used, say, - the vncserver program from the regular RealVNC or TightVNC packages - (i.e. launching the Xvnc server). Otherwise, you could use the - vncpasswd(1) program from those packages. The libvncserver package - also comes with a simple program: storepasswd in the examples - directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports - the -storepasswd "pass" "file" option, which is the 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: -rfbauth - $HOME/myvncpasswd - - Compared to vncpasswd(1) the latter two methods are a somewhat unsafe - because the password is specified on the command line and so someone - may see it by using ps(1) or looking over your shoulder. Also watch - out for the command winding up in your shell's history file (history - -c is often a way to clear it). - - x11vnc also has the [145]-passwdfile and -passwd/-viewpasswd plain - text (i.e. not obscured like the -rfbauth VNC passwords) password - options. - - Q-26: 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 [146]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. - - Q-27: How can I tunnel my connection to x11vnc via an encrypted SSH - channel from Windows using an SSH client like Putty? - - [147]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 - IP number of the Unix machine with display to be viewed. - * Make sure the SSH protocol is selected and the server port is - correct. - * Under 'Connections/SSH/Tunnels' Add a Local connection with - 'Source port: 5900' and 'Destination: localhost:5900' - * Log into the remote machine by pressing 'Open' and supplying - username, password, etc. - * In that SSH shell, start up x11vnc by typing the command: x11vnc - -display :0 plus any other desired options. - * Finally, start up your VNC Viewer in Windows and enter - 'localhost:0' as the VNC server. - - You can keep all of the settings in a Putty 'Saved Session'. Also, - once everything is working, you can consider putting x11vnc -display - :0 (plus other cmdline options) in the 'Remote command' Putty setting - under 'Connections/SSH'. It is likely possible to script the whole - process in a BAT file including launching the VNC viewer by using the - plink Putty utility. Send us the script if you get that working. - - For extra protection feel free to run x11vnc with the -localhost and - -rfbauth/-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 - access to a gateway machine), then you need to change the above Putty - 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. - - As discussed [148]above another option is to first start the VNC - viewer in "listen" mode, and then launch x11vnc with the "-connection - localhost" option to establish the reverse connection. In this case a - Remote port redirection (not Local) is needed for port 5500 instead of - 5900 (i.e. 'Source port: 5500' and 'Destination: localhost:5500' for - a Remote connection). - - Q-28: Does x11vnc support Unix usernames and passwords? Can I further + Q-30: Does x11vnc support Unix usernames and passwords? Can I further limit the set of Unix usernames who can connect to the VNC desktop? Until the VNC protocol and libvncserver support this things will be approximate at best. Hopefully, it will not be too long to wait for such support. - One approximate method involves starting x11vnc with the -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 username -L - 5900:localhost:5900 hostname ... See the ssh wrapper scripts mentioned - [149]elsewhere on this page. 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 watch out for is a malicious user on - the viewer side (where ssh is running) trying to sneak in through the - ssh port redirection. + One approximate method involves starting x11vnc with the + [219]-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 username + -L 5900:localhost:5900 hostname ... See the ssh wrapper scripts + mentioned [220]elsewhere on this page. 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 watch out for is a + malicious user on the viewer side (where ssh is running) trying to + sneak in through the ssh port redirection. Regarding limiting the set of Unix usernames who can connect, the traditional way would be to further require a VNC password to supplied (-rfbauth, -passwd, etc). A scheme that avoids a second password - involves using the -accept option that runs a program to examine the - connection information to determine which user is connecting from the - local machine. For example, the program could use the ident service on - the local machine (normally ident should not be trusted over the - network, but on the local machine it should be accurate: otherwise - root has been compromised and so there are more serious problems!). An - example script passed in via -accept scriptname that deduces the Unix - username and limits who can be accepted might look something like - this: + involves using the [221]-accept option that runs a program to examine + the connection information to determine which user is connecting from + the local machine. For example, the program could use the ident + service on the local machine (normally ident should not be trusted + over the network, but on the local machine it should be accurate: + otherwise root has been compromised and so there are more serious + problems!). An example script passed in via -accept scriptname that + deduces the Unix username and limits who can be accepted might look + something like this: #!/bin/sh if [ "$RFB_CLIENT_IP" != "127.0.0.1" -o "$RFB_SERVER_IP" != "127.0.0.1" ]; then exit 1 # something fishy... reject it. @@ -1730,33 +1843,18 @@ exit 1 # reject it For this to work with ssh port redirection, the ssh option UsePrivilegeSeparation must be enabled. - 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 in the libvncserver CVS there is the -viewpasswd - option to supply the view-only password. Note the full-access password - option -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 - -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 - password. If there is a second line in the file and it is non-blank, - it is taken as the view-only password. + Q-31: I start x11vnc as root because it is launched via inetd(1) or a + display manager like gdm(1). Can I have x11vnc later switch to a + different user? - View-only passwords currently do not work for the -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 - encrypted they are really just obscured to avoid "casual" password - stealing. It takes almost no skill to figure out how to extract the - plain text passwords from $HOME/.vnc/passwd since it is very - straight-forward to work out what to do from the VNC source code. + As of Feb/2005 x11vnc has the [222]-users option that allows things + like this. Please read the documentation on it (in the x11vnc -help + output) carefully for features and caveats. It's use can often + decrease security unless care is taken. A nice use of it is "-users + +nobody" that switches to the Unix user nobody right after connections + to the X display are established. - Q-30: I use a screen-lock when I leave my workstation (e.g. + Q-32: I use a screen-lock when I leave my workstation (e.g. xscreensaver or xlock). When I remotely access my workstation desktop via x11vnc I can unlock the desktop fine, but I am worried people will see my activities on the physical monitor. What can I do to prevent @@ -1769,7 +1867,7 @@ exit 1 # reject it 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 [150]blockdpy.c The idea behind it is simple (but + source for it is [223]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 @@ -1785,15 +1883,15 @@ exit 1 # reject it bulletproof. A really robust solution would likely require X server and perhaps even video hardware support. - The blockdpy utility is launched by the -accept option and told to - exit via the -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. + The blockdpy utility is launched by the [224]-accept option and told + to exit via the [225]-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. - Q-31: Can I have x11vnc automatically lock the screen when I + Q-33: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? - Yes, a user mentions he uses the -gone option under CDE to run a + Yes, a user mentions he uses the [226]-gone option under CDE to run a screen lock program: x11vnc -display :0 -forever -gone 'dtaction LockDisplay' @@ -1805,7 +1903,7 @@ exit 1 # reject it [Display Managers and Services] - Q-32: How can I run x11vnc as a "service" that is always available? + Q-34: How can I run x11vnc as a "service" that is always available? There are a number of ways to do this. The primary thing you need to decide is whether you want x11vnc to connect to the X session on the @@ -1813,21 +1911,21 @@ exit 1 # reject it only if a certain user has the X session. Because X sessions are protected by X permissions (XAUTHORITY and $HOME/.Xauthority) the automatically started x11vnc will of course need to have sufficient - permissions. + permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [151]FAQ on x11vnc + * Use the description under "Continuously" in the [227]FAQ on x11vnc and Display Managers - * Use the description in the [152]FAQ on x11vnc and inetd(1) - * Start x11vnc from $HOME/.xsession (or $HOME/.xinitrc) - * Although less reliable, see the [153]x11vnc_loop rc.local hack + * Use the description in the [228]FAQ on x11vnc and inetd(1) + * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc) + * Although less reliable, see the [229]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the X session unless a test is specifically put into the display startup - script (often Xsetup). The inetd(1) scheme may or may not be specific - to which user has the X session (and it may not be able to do all - users via the XAUTHORITY permission issues). + script (often named Xsetup). The inetd(1) scheme may or may not be + specific to which user has the X session (and it may not be able to do + all users via the XAUTHORITY permission issues). The $HOME/.xsession scheme is obviously is specific to a particular user. If you do not know what a $HOME/.xsession script is or how to @@ -1838,7 +1936,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg plus any other options you desire. - Q-33: How can I use x11vnc to connect to an X login screen like xdm, + Q-35: How can I use x11vnc to connect to an X login screen like xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X session yet). @@ -1850,9 +1948,9 @@ 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 -auth option sets XAUTHORITY). There will be a similar thing for - xdm using however a different auth directory path (perhaps something - like /var/lib/xdm/authdir/authfiles/A:0-XQvaJk for xdm or + (the [230]-auth option sets XAUTHORITY). There will be a similar thing + for xdm using however a different auth directory path (perhaps + something like /var/lib/xdm/authdir/authfiles/A:0-XQvaJk for xdm or /var/lib/kdm/A:0-crWk72 for kdm, where the random characters in basename will vary a bit). @@ -1870,8 +1968,9 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg For dtlogin in addition to the above sort of trick (BTW, the auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig - or /usr/dt/config/Xconfig on Solaris). Then restart dtlogin, e.g.: - /etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot. + or /usr/dt/config/Xconfig on Solaris, see [231]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 restarted (i.e. after each logout): @@ -1908,10 +2007,11 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg debugging. In that case replace the -bg above with something like: 1>> /var/tmp/x11vnc.log 2>&1 & - (or use the "-o logfile" option). + (or use the "[232]-o logfile" option). + _________________________________________________________________ - Here is an example what we did on a vanilla install of Fedora-C3 - (seems to use gdm by default). Add a line like this to + Fedora/gdm: Here is an example of what we did on a vanilla install of + Fedora-C3 (seems to use gdm by default). Add a line like this to /etc/X11/gdm/Init/:0 /usr/local/bin/x11vnc -rfbauth /etc/x11vnc.passwd -forever -bg -o /var/tmp/x1 1vnc.log @@ -1922,10 +2022,12 @@ 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 [154]full details + killed immediately after the user logs in. Here are [233]full details on how to configure gdm + _________________________________________________________________ - Here is an example what we did on a vanilla install of Solaris: + Solaris/dtlogin: Here is an example of what we did on a vanilla + install of Solaris: Make the directory /etc/dt/config: mkdir -p /etc/dt/config @@ -1949,26 +2051,29 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg /etc/init.d/dtlogin start (or reboot or maybe just restart the X session). + _________________________________________________________________ + 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: [155]x11vnc_loop It will need some local + file like rc.local: [234]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 above is preferred. If the machine is a traditional Xterminal you may want to read - [156]this FAQ. + [235]this FAQ. - Q-34: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + Q-36: Can I run x11vnc out of inetd(1)? How about xinetd(1)? Yes, perhaps a line something like this in /etc/inetd.conf will do it for you: 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh - where the shell script /usr/local/bin/x11vnc_sh looks something like - (you'll need to customize to your settings). + where the shell script /usr/local/bin/x11vnc_sh uses the [236]-inetd + option and looks something like (you'll need to customize to your + settings). #!/bin/sh /usr/local/bin/x11vnc -inetd -display :0 -auth /home/fred/.Xauthority \ -rfbauth /home/fred/.vnc/passwd 2>> /tmp/x11vnc_sh.log @@ -1978,13 +2083,13 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg also goes to the VNC vncviewer, and that confuses it greatly). If you do not use a wrapper script as above but rather call x11vnc directly in /etc/inetd.conf and do not redirect stderr, then you must specify - the -q (aka -quiet) option: /usr/local/bin/x11vnc -q -inetd ... or use - the -o logfile to collect the output in a file. The wrapper script + the -q (aka [237]-quiet) option: /usr/local/bin/x11vnc -q -inetd ... + or use -o logfile to collect the output in a file. The wrapper script with stderr redirection to a log file is the recommended method because the errors and warnings printed out are very useful in troubleshooting problems. - Note also the need to set XAUTHORITY via -auth to point to the + Note also the need to set XAUTHORITY via [238]-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 @@ -2027,11 +2132,11 @@ service x11vncservice With the contents of /usr/local/bin/x11vnc_sh similar to the example given above. - Q-35: How do I make x11vnc work with the Java VNC viewer applet in a + Q-37: How do I make x11vnc work with the Java VNC viewer applet in a web browser? To have x11vnc serve up a Java VNC viewer applet to any web browsers - that connect to it, run x11vnc with this option: + that connect to it, run x11vnc with this [239]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -2054,21 +2159,21 @@ service x11vncservice entirely from the viewer-side by having the jar file there and using either the java or appletviewer commands to run the program. - Q-36: Are reverse connections (i.e. the VNC server connecting to the + Q-38: Are reverse connections (i.e. the VNC server connecting to the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported? As of Mar/2004 in the libvncserver CVS x11vnc supports reverse connections. On Unix one starts the VNC viewer in listen mode: - vncviewer -listen, and then starts up x11vnc with the -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). If a file is specified instead: - -connect /path/to/some/file then that file is checked periodically - (about once a second) for new hosts to connect to. + vncviewer -listen, and then starts up x11vnc with the [240]-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). If a file is specified + instead: -connect /path/to/some/file then that file is checked + periodically (about once a second) for new hosts to connect to. To use the vncconnect(1) program (from the core VNC package at - www.realvnc.com) specify the -vncconnect option to x11vnc (Note: as of - Dec/2004 -vncconnect is now the default). vncconnect(1) must be + www.realvnc.com) specify the [241]-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 the vncconnect(1) program, the following script (named "Vncconnect") @@ -2083,7 +2188,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" [Resource Usage and Performance] - Q-37: I have lots of memory, but why does x11vnc fail with shmget: + Q-39: I have lots of memory, but why does x11vnc fail with shmget: No space left on device or Minor opcode of failed request: 1 (X_ShmAttach)? @@ -2101,7 +2206,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$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 [157]shm_clear to list and prompt for removal + Here is a shell script [242]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, @@ -2135,35 +2240,36 @@ ied) in /etc/system. See the next paragraph for more workarounds. To minimize the number of shm segments used by x11vnc try using the - -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 -noshm option. - Performance will be somewhat degraded but when done over local machine - sockets it should be acceptable (see an [158]earlier question - discussing -noshm). + [243]-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 + [244]-noshm option. Performance will be somewhat degraded but when + done over local machine sockets it should be acceptable (see an + [245]earlier question discussing -noshm). - Q-38: How can I make x11vnc use less system resources? + Q-40: How can I make x11vnc use less system resources? - The -nap and "-wait n" (where n is the sleep between polls in - milliseconds, the default is 30 or so) option are good places to + The [246]-nap and "[247]-wait n" (where n is the sleep between polls + in milliseconds, the default is 30 or so) option are good places to start. 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. Using the - -onetile option will use less memory and use fewer shared memory slots - (add -fs 1.0 for one less slot). + [248]-onetile option will use less memory and use fewer shared memory + slots (add [249]-fs 1.0 for one less slot). - Q-39: How can I make x11vnc use MORE system resources? + Q-41: How can I make x11vnc use MORE system resources? - You can try -threads and dial down the wait time (e.g. -wait 1) and - possibly dial down -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. + You can try [250]-threads and dial down the wait time (e.g. -wait 1) + and possibly dial down [251]-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 -id option) can be streamed over a LAN or wireless at a - reasonable frame rate. + the x11vnc [252]-id option) can be streamed over a LAN or wireless at + a reasonable frame rate. - Q-40: I use x11vnc over a slow link with high latency (e.g. dialup + Q-42: I use x11vnc over a slow link with high latency (e.g. dialup modem), is there anything I can do to speed things up? Some things you might want to experiment with (most of which will help @@ -2174,8 +2280,8 @@ ied) (reduces amount of data needed to be sent) * 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 -solid - [color] option. + is resent every time it is re-exposed). Consider using the + [253]-solid [color] option. * Configure your window manager or desktop "theme" to not use fancy images, shading, and gradients for the window decorations, etc. Disable Opaque moves, resizes, and animations. @@ -2188,7 +2294,7 @@ ied) worth it, but could be of use in some situations. VNC viewer parameters: - * Use a [159]TightVNC enabled viewer! + * Use a [254]TightVNC enabled viewer! * Make sure the tight encoding is being used (look at vncviewer and x11vnc outputs) * Request 8 bits per pixel using -bgr233 (up to 4X speedup over @@ -2206,21 +2312,22 @@ ied) vncviewer to be very slow) x11vnc parameters: - * Try using -nodragging (no screen updates when dragging mouse, but - sometimes you miss visual feedback) - * Try the -progressive pixelheight mode with the block pixelheight - 100 or so (delays sending vertical blocks since they may change - while viewer is receiving earlier ones) - * Set -fs 1.0 (disables fullscreen updates) - * Try increasing -wait or -defer (reduces the maximum "frame rate", - but won't help much for large screen changes) - * If you just want to watch one (simple) window use -id (cuts down - extraneous polling and updates, but can be buggy or insufficient) - * Set -nosel (disables all clipboard selection exchange) - * Use -nocursor and -nocursorpos (repainting the remote cursor - position and shape takes resources and round trips) - - Q-41: When I drag windows around with the mouse or scroll up and down + * Try using [255]-nodragging (no screen updates when dragging mouse, + but sometimes you miss visual feedback) + * Try the [256]-progressive pixelheight mode with the block + pixelheight 100 or so (delays sending vertical blocks since they + may change while viewer is receiving earlier ones) + * Set [257]-fs 1.0 (disables fullscreen updates) + * Try increasing [258]-wait or [259]-defer (reduces the maximum + "frame rate", but won't help much for large screen changes) + * If you just want to watch one (simple) window use [260]-id (cuts + down extraneous polling and updates, but can be buggy or + insufficient) + * Set [261]-nosel (disables all clipboard selection exchange) + * Use [262]-nocursor and [263]-nocursorpos (repainting the remote + cursor position and shape takes resources and round trips) + + Q-43: 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? @@ -2228,54 +2335,62 @@ ied) tree. The 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 -pointer_mode 1 option. + way via the "[264]-pointer_mode 1" option. - Also added was the -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 + Also added was the [265]-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 in the libvncserver CVS the -pointer_mode n option was - introduced. n=1 is the original mose, n=2 and improvement, etc.. See - the -pointer_mode n help for more info. + As of Dec/2004 in the libvncserver CVS the [266]-pointer_mode n option + was introduced. n=1 is the original mose, n=2 and improvement, etc.. + See the -pointer_mode n help for more info. [Mouse Cursor Shapes] - Q-42: Why isn't the mouse cursor shape (the little icon shape where + Q-44: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? - On X servers supporting XFIXES or Overlay extensions this is possible. - See the paragraphs below. + On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it + is possible for x11vnc to do this correctly. See the paragraphs below. - As mentioned above, the X11 mouse cursor shape (i.e. little picture: - an arrow, X, I-beam, resizer, etc) is one of the few write-only - objects in X11. That is, an application can tell the X server what the - cursor shape should be when the pointer is in a given window, but a - program (like x11vnc) unfortunately cannot read this information. I - believe this is because the cursor shape is often downloaded to the - graphics hardware (video card), but I could be mistaken. + Historically, the X11 mouse cursor shape (i.e. little picture: an + arrow, X, I-beam, resizer, etc) is one of the few write-only objects + in X11. That is, an application can tell the X server what the cursor + shape should be when the pointer is in a given window, but a program + (like x11vnc) unfortunately cannot read this information. I believe + 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 "-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 "-cursor some" option for additional kludges. + A simple kludge is provided by the "[267]-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 "[268]-cursor some" option for + additional kludges. Note that as of Aug/2004 in the libvncserver CVS, on Solaris using the SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse - cursor when the -overlay is also supplied. (-overlay has some other - problems however, and can be slower). + cursor when the [269]-overlay option is supplied. See [270]this FAQ + for more info. Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support has been added to allow exact extraction of the mouse cursor shape. - The only issue is the handling of alpha channel transparency in - cursors (they must be approximated). XFIXES is available on recent - Linux Xorg based distros and Solaris 10 (on Solaris you will need to - add "-L /usr/openwin/sfw/lib -R /usr/openwin/sfw/lib" to LDFLAGS for - configure to enable it). - - Q-43: When using XFIXES cursorshape mode, some of the cursors look + 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 [271]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 + approximated to opaque RGB values. There are some 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. [272]Details can be found here. + + Q-45: When using XFIXES cursorshape mode, some of the cursors look really bad with extra black borders around the cursor and other cruft. How can I improve their appearance? @@ -2295,107 +2410,108 @@ ied) =< a =< 1), with similar for Green and Blue. The VNC protocol does not currently support an alpha channel in cursors: it only supports regular X bitmap cursors and Rich Cursors that have RGB (Red, Green, - Blue) color data, but no "A" = alpha data. So x11vnc has to + Blue) color data, but no "A" = alpha data. So in general x11vnc has to approximate a cursor with transparency to create a Rich Cursor. This is easier said than done: some cursor themes have cursors with complicated drop shadows and other forms of translucency. Anyway, for the x11vnc 0.7.1 release the algorithm for approximating transparency is much improved and hopefully gives decent cursor shapes - for most cursor themes. + 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 "-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 - "-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 -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 -alpharemove - to brighten them by dividing out the alpha value. - - Q-44: In XFIXES mode, are there any hacks to handle cursor + course!) some tunable parameters. The "[273]-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 "[274]-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 [275]-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 + -alpharemove to brighten them by having x11vnc divide out the alpha + value. + + Q-46: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? - As of Jan/2005 in the libvncserver CVS, libvncserver has been modified - to allow an alpha channel (i.e. RGBA data) for Rich Cursors. This only - works if the screen pixel format has extra unused pixels where the - alpha data can be stored. This effectively limits things to depth 24 - at 32bpp (bpp = bits per pixel, depth = the number of bits used to - represent RGB color data and can be less than bpp); fortunately this - is a common screen setup. This hack won't work for 16bpp. (well, it - could work for depth 15 at 16bpp, but that only leaves one bit for the - alpha data, which is not worth it). - - The -alphablend option instructs x11vnc to use RGBA for Rich Cursors - (currently it is ignored except for depth 24 at 32bpp). So, in - -nocursorshape mode, or for VNC clients that do not support - CursorShapeUpdates (or have disabled them), x11vnc will draw the - blended cursor with transparency into the x11vnc framebuffer for these - clients, and the transparency should look correct for them. - - Now, if you want CursorShapeUpdates turned on for your viewer (e.g. - because you do not like the lag between your pointer and the drawn - cursor) it is possible to modify your VNC viewer to apply the alpha - channel blending locally. This hack is outside of the VNC protocol. - Not only does this require depth 24 at 32bpp (for the extra space to - hide the alpha data), but it also currently requires the client and - server to be of the same endianness (otherwise the hidden alpha data - gets reset to zero by the translation function). As an example, for - the TightVNC 1.3dev5 Unix vncviewer [160]this patch enables the - TightVNC viewer to do the blending locally. You have to set the - environment variable ALPHABLEND=1 before starting your modified - viewer. The patch code should give an example on how to change the - Windows TightVNC viewer to achieve the same thing (send me the patch - if you get that working). + As of Jan/2005 in the CVS, libvncserver has been modified to allow an + alpha channel (i.e. RGBA data) for Rich Cursors. So x11vnc can now + send the 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 [276]-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 + [277]-noalphablend option to disable this behavior (always approximate + transparent cursors with opaque RGB values). + + The CursorShapeUpdates VNC extension complicates matters because the + cursor shape is sent to the VNC viewers supporting it, and the viewers + draw the cursor locally. This improves response over slow links. Alpha + channel data for these locally drawn cursors is not supported by the + VNC protocol. + + However, in the libvncserver CVS there is a patch to the TightVNC + viewer to make this work for CursorShapeUpdates under some + circumstances. This hack is outside of the VNC protocol. It requires + the screens on both sides to be depth 24 at 32bpp (it uses the extra 8 + bits to secretly hide the cursor alpha channel data). Not only does it + require depth 24 at 32bpp, but it also currently requires the client + and server to be of the same endianness (otherwise the hidden alpha + data gets reset to zero by a libvncserver translation function; we can + fix this at some point if there is interest). The patch is for the + TightVNC 1.3dev5 Unix vncviewer and it enables the TightVNC viewer to + do the cursor alpha blending locally. The patch code should give an + example on how to change the Windows TightVNC viewer to achieve the + same thing (send me the patch if you get that working). [Mouse Pointer] - Q-45: Why does the mouse arrow just stay in one corner in my + Q-47: 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 [161]tightvnc extension + This default takes advantage of a [278]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the -nocursor option to - x11vnc if your viewer does not have this extension. + the local VNC viewer. You may disable it with the [279]-nocursor + option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 in the libvncserver CVS this should be fixed: the default for non-tightvnc viewers (or ones that do not support CursorShapeUpdates) will be to draw the moving cursor into the x11vnc framebuffer. This can also be disabled via -nocursor. - Q-46: Can I take advantage of the TightVNC extension to the VNC + Q-48: Can I take advantage of the TightVNC extension to the VNC protocol where Cursor Positions Updates are sent back to all connected clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the -cursorpos option when starting x11vnc. A VNC viewer must + Use the [280]-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 in the - libvncserver CVS -cursorpos is the default. See also -nocursorpos and - -nocursorshape. + libvncserver CVS -cursorpos is the default. See also [281]-nocursorpos + and [282]-nocursorshape. - Q-47: Is it possible to swap the mouse buttons (e.g. left-handed + Q-49: 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: -buttonmap 13-31 - (or perhaps 12-21). Also, note that xmodmap(1) lets you directly + You can remap the mouse buttons via something like: [283]-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. 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 -debug_pointer option prints out much info for every - mouse/pointer event. + Note that the [284]-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 format where the keystrokes are enclosed between colons like this @@ -2416,8 +2532,8 @@ ied) 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 -buttonmap but rather configuring the X server to - think it has a mouse with 5 buttons even though the physical mouse + consider not using [285]-buttonmap but rather configuring the X server + to think it has a mouse with 5 buttons even though the physical mouse does not. Note that when a keysym-mapped mouse button is clicked down this @@ -2434,11 +2550,11 @@ ied) (yes, this is getting a little silly). [Keyboard Issues] - Q-48: How can I get my AltGr and Shift modifiers to work between + Q-50: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option -modtweak should be of some use for this. It is a mode that - monitors the state of the Shift and AltGr Modifiers and tries to + The option [286]-modtweak should be of some use for this. 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. @@ -2446,20 +2562,20 @@ ied) default (use -nomodtweak 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 [162]this FAQ + and ">" it. This key does not exist on the keyboard (see [287]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 [163]FAQ about the -xkb option for a more powerful method + Also see the [288]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, that the - -debug_keyboard option prints out much info for every keystroke and so - can be useful debugging things. + When trying to resolve keyboard mapping problems, note that the + [289]-debug_keyboard option prints out much info for every keystroke + and so can be useful debugging things. - Q-49: When I try to type a "<" (i.e. less than) instead I get ">" + Q-51: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! Does your keyboard have a single key with both "<" and ">" on it? Even @@ -2506,20 +2622,20 @@ ied) -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former is a mode that monitors the state of the Shift - and AltGr modifiers and tries to deduce the correct keycode sequence - to send. The latter 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 "<"). + settings. The former ([290]-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 ([291]-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 [164]FAQ about the -xkb option as a possible workaround - using the XKEYBOARD extension. Note that of Jul/2004 in the - libvncserver CVS the -modtweak option is now that default. + See also the [292]FAQ about the -xkb option as a possible workaround + using the XKEYBOARD extension. - Note that the -debug_keyboard option prints out much info for every - keystroke to aid debugging keyboard problems. + Note that the [293]-debug_keyboard option prints out much info for + every keystroke to aid debugging keyboard problems. - Q-50: I'm using an "international" keyboard (e.g. German "de", or + Q-52: I'm using an "international" keyboard (e.g. German "de", or Danish "dk") and the -modtweak mode works well if the VNC viewer is run on a Unix/Linux machine with a similar keyboard. But if I run the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or @@ -2540,11 +2656,11 @@ ied) 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 -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 default and make - heavy use of it to handle international keyboards. + This all worked fine with x11vnc running with the [294]-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 + default and make heavy use of it to handle international keyboards. To make a long story short, on these newer XFree86 setups the traditional X keymap lookup x11vnc uses is no longer accurate. x11vnc @@ -2558,8 +2674,8 @@ ied) * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The -xkb option seems to fix all of the missing keys: "@", "<", ">", - etc.: it is recommended that you try it if you have this sort of + The [295]-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 (aka -dk) option twice you will get a huge amount of keystroke @@ -2576,7 +2692,7 @@ ied) 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: - -skip_keycodes 93 + [296]-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 @@ -2593,22 +2709,22 @@ ied) 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 -remap x11vnc option: + created using the [297]-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. See the -add_keysyms - option below. - * To complement the above workaround using the -remap, an option - -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 created. Note - that the -remap mappings are applied first, right when the Keysym - is received from a VNC viewer, and only after that would - -add_keysyms, or anything else, come into play. - - Q-51: When typing I sometimes get double, triple, or more of my + x11vnc adjust automatically at some point. Also see the + [298]-add_keysyms option in the next paragraph. + * To complement the above workaround using the [299]-remap, an + option [300]-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 + created. Note that the -remap mappings are applied first, right + when the Keysym is received from a VNC viewer, and only after that + would -add_keysyms, or anything else, come into play. + + Q-53: When typing I sometimes get double, triple, or more of my keystrokes repeated. I'm sure I only typed them once, what can I do? This may be due to an interplay between your X server's key autorepeat @@ -2616,10 +2732,10 @@ ied) 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) -norepeat x11vnc option. You will still have - autorepeating because that is taken care of on your VNC viewer side. - Update: as of Dec/2004 -norepeat is now the default. Use -repeat to - disable it. + use the new (Jul/2004) [301]-norepeat x11vnc option. You will still + have autorepeating because that is taken care of on your VNC viewer + side. Update: as of Dec/2004 -norepeat is now the default. Use -repeat + to disable it. Details: suppose you press a key DOWN and it generates changes in large regions of the screen. The CPU and I/O work x11vnc does for the @@ -2634,51 +2750,48 @@ ied) otherwise high latency link (e.g. > 250 ms latency). Look at the output of "xset q" for the "auto repeat delay" setting. Is - it low (e.g. < 500 ms)? If you increase it to a very large delay, e.g. - "xset r rate 1500" or turn off autorepeat completely: "xset r off", - does the problem go away? - - We are looking into a good way to fix this, but in the meantime as a - workaround try to use xset r rate N for large enough delay N or xset r - off to get rid of the problem. Also, as of Jul/2004 in the - libvncserver CVS there is the -norepeat option to automatically - disable autorepeating in the X server whenever VNC viewers are - attached. Note that the VNC viewer side of the connection will (nearly - always) do its own autorepeating so there is no big loss here, unless - someone is also working at the physical display and misses his - autorepeating. - - Q-52: The x11vnc -norepeat mode is in effect, but I still get repeated + it low (e.g. < 300 ms)? If you turn off autorepeat completely: "xset r + 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 [302]-norepeat (which has since Dec/2004 been + made the default). Note that with X server autorepeat turned off the + VNC viewer side of the connection will (nearly always) do its own + autorepeating so there is no big loss here, unless someone is also + working at the physical display and misses his autorepeating. + + Q-54: The x11vnc -norepeat mode is in effect, but I still get repeated keystrokes!! - Are you using x11vnc to log in to an X session? (as described - [165]this FAQ) If so, x11vnc is starting before your session, and then - your session startup could be resetting the autorepeat to be on. Or it - could be something inside your desktop that decides to turn it back - on. x11vnc in -norepeat mode will not battle with things turning - autorepeat back on. (It will, however, turn it off whenever it goes - from a state of zero clients to one client). + Are you using x11vnc to log in to an X session? (as described in + [303]this FAQ) If so, x11vnc is starting before your session and it + disables autorepeat when you connect, and then your session startup + could be resetting the autorepeat to be on. Or it could be something + inside your desktop that decides to turn it back on. x11vnc in + -norepeat mode will not battle with things turning autorepeat back on. + (It will, however, turn it off whenever it goes from a state of zero + clients to one client). Under these circumstances you will have to manually turn autorepeating off by typing "xset r off" or "x11vnc -R norepeat" or a desktop utility. If something in your desktop is automatically turning it back on you will have to disable that somehow. - Q-53: The machine where I run x11vnc has an AltGr key, but the local + Q-55: The machine where I run x11vnc has an AltGr key, but the local machine where I run the VNC viewer does not. Is there a way I can map a local unused key to send an AltGr? How about a Compose key as well? - Something like "-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)). + Something like "[304]-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)). For Compose how about "-remap Menu-Multi_key" (note that Multi_key is - the official name for Compose) To do both at the same time: "-remap + the official name for Compose). To do both at the same time: "-remap Super_R-Mode_switch,Menu-Multi_key" or use "-remap filename" to specify remappings from a file. - Q-54: I have a Sun machine I run x11vnc on. Its Sun keyboard has just + Q-56: I have a Sun machine I run x11vnc on. Its Sun keyboard has just one Alt key labelled "Alt" and two Meta keys labelled with little diamonds. The machine where I run the VNC viewer only has Alt keys. How can I send a Meta keypress? (e.g. emacs needs this) @@ -2690,25 +2803,25 @@ ied) 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 -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. + the [305]-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. - Q-55: Can I map a keystroke to a mouse button click on the remote + Q-57: Can I map a keystroke to a mouse button click on the remote machine? This can be done directly in some X servers using AccessX and Pointer_EnableKeys, but is a bit awkward. It may be more convenient to - have x11vnc do the remapping. This can be done via the -remap option - using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. - the ones after the "-") + have x11vnc do the remapping. This can be done via the [306]-remap + option using the fake "keysyms" Button1, Button2, etc. as the "to" + keys (i.e. the ones after the "-") - As an example, consider a laptop that has a touchpad with only two - buttons. It is difficult to do a middle button "paste" because (using - XFree86 Emulate3Buttons) you have to click both buttons on the touch - pad at the same time. This remapping: - -remap Super_R-Button2 + As an example, consider a laptop where the VNC viewer is run that has + a touchpad with only two buttons. It is difficult to do a middle + button "paste" because (using XFree86 Emulate3Buttons) you have to + click both buttons on the touch pad at the same time. This remapping: + [307]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -2719,7 +2832,7 @@ ied) [Screen Related Issues and Features] - Q-56: The remote display is larger (in number of pixels) than the + Q-58: The remote display is larger (in number of pixels) than the local display I am running the vncviewer on. I don't like the vncviewer scrollbars, what I can do? @@ -2737,19 +2850,19 @@ ied) There may also be scaling viewers out there (e.g. TightVNC on Windows) that automatically shrink or expand the remote framebuffer to fit the - local display. Especially for hand-held devices. See also [166]this + local display. Especially for hand-held devices. See also [308]this FAQ on x11vnc scaling. - Q-57: Does x11vnc support server-side framebuffer scaling? (E.g. to + Q-59: Does x11vnc support server-side framebuffer scaling? (E.g. to make the desktop smaller). As of Jun/2004 in the libvncserver CVS x11vnc provides basic server-side scaling. It is a global scaling of the desktop, not a - per-client setting. To enable it use the "-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 2/3). Note that if - fraction is greater than one the display is expanded (not clear how - useful this is). + per-client setting. To enable it use the "[309]-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 2/3). Note + that if fraction is greater than one the display is expanded (not + clear how useful that is...) The current implementation is experimental in that it still needs to be optimized. Extra resources (CPU, memory I/O, and memory) are @@ -2769,14 +2882,14 @@ ied) may want to turn off jpeg encoding (e.g. vncviewer -nojpeg host:0). There appears to be a noise enhancement effect, especially for regions containing font/text: the scaling can introduce some pixel artifacts - that evidently causes the TightVNC to incorrectly detect the regions - as image data and thereby introduce additional pixel artifacts due to - the lossiness of the jpeg compression algorithm. Experiment to see if - -nojpeg vncviewer option improves the readability of text when using - -scale to shrink the display size. Also note that scaling may actually - slow down the transfer of text regions because after being scaled they - do not compress as well. (this can often be a significant slowdown, - e.g. 10X). + that evidently causes the tight encoding algorithm to incorrectly + detect the regions as image data and thereby introduce additional + pixel artifacts due to the lossiness of the jpeg compression + algorithm. Experiment to see if -nojpeg vncviewer option improves the + readability of text when using -scale to shrink the display size. Also + note that scaling may actually slow down the transfer of text regions + because after being scaled they do not compress as well. (this can + often be a significant slowdown, e.g. 10X). Another issue is that it appears VNC viewers require the screen width to be a multiple of 4. When scaling x11vnc will round the width to the @@ -2787,10 +2900,10 @@ ied) 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 (-rfbport option, + different scalings listening on separate ports ([310]-rfbport option, etc.). - Q-58: Does x11vnc work with Xinerama? (i.e. multiple monitors joined + Q-60: Does x11vnc work with Xinerama? (i.e. multiple monitors joined together to form one big, single screen). Yes, it should generally work because it simply polls the big @@ -2802,22 +2915,22 @@ ied) 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 -blackout x11vnc option allows you to - blacken-out rectangles by specifying their WxH+X+Y geometries. If your - system has the libXinerama library, the -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). + distracting to the viewer. The [311]-blackout x11vnc option allows you + to blacken-out rectangles by specifying their WxH+X+Y geometries. If + your system has the libXinerama library, the [312]-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). 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 -xwarppointer + of the large display. If this happens try using the [313]-xwarppointer option. This instructs x11vnc to fake mouse pointer motions using the XWarpPointer function instead of the XTestFakeMotionEvent XTEST function. (This may be due to a bug in the X server for XTEST when Xinerama is enabled). - Q-59: Can I use x11vnc on a multi-headed display that is not Xinerama + Q-61: Can I use x11vnc on a multi-headed display that is not Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? You can, but it is a little bit awkward: you must start separate @@ -2835,37 +2948,39 @@ ied) 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 [167]FAQ to increase the limit. It - is probably also a good idea to run with the -onetile option in this - case (to limit each x11vnc to 3 shm segments), or even -noshm to use - no shm segments. + /etc/system as mentioned in another [314]FAQ to increase the limit. It + is probably also a good idea to run with the [315]-onetile option in + this case (to limit each x11vnc to 3 shm segments), or even + [316]-noshm to use no shm segments. - Q-60: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) + Q-62: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) extension? Whenever I rotate or resize the screen x11vnc just seems to crash. As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You - enable it with the -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. If the connected - vnc viewers support the NewFBSize VNC extension (Windows TightVNC - viewer and RealVNC 4.0 windows and Unix viewers do) 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). + enable it with the [317]-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. If the + connected vnc viewers support the NewFBSize VNC extension (Windows + TightVNC viewer and RealVNC 4.0 windows and Unix viewers do) 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 + [318]-padgeom option to make the region big enough to hold all resizes + and rotations. If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you specify "-xrandr exit" then all will be disconnected and x11vnc will terminate. - Q-61: Why is the view in my VNC viewer completely black? Or why is + Q-63: Why is the view in my VNC viewer completely black? Or why is everything flashing around randomly? See the next FAQ for a possible explanation. - Q-62: I use Linux Virtual Consoles (VC's) to implement 'Fast User + Q-64: I use Linux Virtual Consoles (VC's) to implement 'Fast User Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7, Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those keystrokes to switch between their sessions). How come the view in a @@ -2889,10 +3004,10 @@ ied) If no one is sitting at the workstation and you just want to remotely switch the VC over to the one associated with your X session (so - x11vnc can poll it), one can use the switchto(1) command, e.g. - "switchto 7" for VC #7. + x11vnc can poll it correctly), one can use the switchto(1) command, + e.g. "switchto 7" for VC #7. - Q-63: I am using x11vnc where my local machine has "popup/hidden + Q-65: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars @@ -2904,34 +3019,42 @@ ied) uncheck "enable auto-hide" from the panel properties dialog box. This will make the panel always visible. - [Misc: Clipboard, Beeps, etc.] + [Misc: Clipboard, Beeps, Thanks, etc.] - Q-64: Does the Clipboard/Selection get transferred between the + Q-66: Does the Clipboard/Selection get transferred between the vncviewer and the X display? As of Jan/2004 in the libvncserver CVS x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY selection (Xvnc does not seem to do this). If you don't want - the Clipboard/Selection exchanged use the -nosel option. If you don't - want the PRIMARY selection to be polled for changes use the -noprimary - option. + the Clipboard/Selection exchanged use the [319]-nosel option. If you + don't want the PRIMARY selection to be polled for changes use the + [320]-noprimary option. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and cutbuffers. - Q-65: Why don't I hear the "Beeps" in my X session (e.g. when typing + Q-67: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? As of Dec/2003 in the libvncserver CVS "Beep" XBell events are tracked by default. The X server must support the XKEYBOARD extension (this is - not on by default in Solaris, see Xserver(1) for how to turn it on), - and so you won't hear them if the extension is not present. + not on by default 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 -nobell option. If you - want to hear the audio from the remote applications, consider trying a - redirector such as esd. - _________________________________________________________________ + If you don't want to hear the beeps use the [321]-nobell option. If + you want to hear the audio from the remote applications, consider + trying a redirector such as esd. + + Q-68: 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! + Click on the PayPal button below. + Also, in general I always enjoy hearing from x11vnc users, how they + use it, what new features they would like, etc. Please send me an + [322]email. [PayPal] @@ -2947,163 +3070,318 @@ References 8. http://www.tightvnc.com/ 9. http://www.karlrunge.com/x11vnc/index.html#downloading 10. http://www.tightvnc.com/download.html - 11. http://www.karlrunge.com/x11vnc/index.html#xperms - 12. http://www.karlrunge.com/x11vnc/index.html#viewer-download - 13. http://www.sun.com/software/solaris/freeware/ - 14. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 15. http://www.karlrunge.com/x11vnc/index.html#service - 16. http://www.karlrunge.com/x11vnc/index.html#passwd - 17. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file - 18. http://www.karlrunge.com/x11vnc/index.html#inetd - 19. http://www.karlrunge.com/x11vnc/index.html#tightvnc_via - 20. http://www.karlrunge.com/x11vnc/index.html#inetd - 21. http://www.karlrunge.com/x11vnc/index.html#passwd - 22. http://www.karlrunge.com/x11vnc/index.html#passwdfile - 23. http://www.karlrunge.com/x11vnc/index.html#allow_opt - 24. http://www.karlrunge.com/x11vnc/index.html#tcp_wrappers - 25. http://sourceforge.net/projects/libvncserver/ - 26. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=292078 - 27. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=292078 - 28. http://www.karlrunge.com/x11vnc/x11vnc.c - 29. http://www.karlrunge.com/x11vnc/tkx11vnc.h - 30. http://www.karlrunge.com/x11vnc/index.html#binaries - 31. http://www.tightvnc.com/download.html - 32. http://www.realvnc.com/download-free.html - 33. http://sourceforge.net/projects/cotvnc/ - 34. http://www.karlrunge.com/x11vnc/rx11vnc - 35. http://www.karlrunge.com/x11vnc/rx11vnc.pl - 36. ftp://ftp.uu.net/graphics/jpeg/ - 37. http://www.gzip.org/zlib/ - 38. http://www.sunfreeware.com/ - 39. http://www.karlrunge.com/x11vnc/index.html#solaris251build - 40. http://www.tightvnc.com/ - 41. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 42. http://www.karlrunge.com/x11vnc/index.html#passwd - 43. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg - 44. http://wwws.sun.com/sunray/index.html - 45. mailto:xvml@karlrunge.com - 46. http://www.karlrunge.com/x11vnc/index.html#FAQ-1 - 47. http://www.karlrunge.com/x11vnc/index.html#FAQ-2 - 48. http://www.karlrunge.com/x11vnc/index.html#FAQ-3 - 49. http://www.karlrunge.com/x11vnc/index.html#FAQ-4 - 50. http://www.karlrunge.com/x11vnc/index.html#FAQ-5 - 51. http://www.karlrunge.com/x11vnc/index.html#FAQ-6 - 52. http://www.karlrunge.com/x11vnc/index.html#FAQ-7 - 53. http://www.karlrunge.com/x11vnc/index.html#FAQ-8 - 54. http://www.karlrunge.com/x11vnc/index.html#FAQ-9 - 55. http://www.karlrunge.com/x11vnc/index.html#FAQ-10 - 56. http://www.karlrunge.com/x11vnc/index.html#FAQ-11 - 57. http://www.karlrunge.com/x11vnc/index.html#FAQ-12 - 58. http://www.karlrunge.com/x11vnc/index.html#FAQ-13 - 59. http://www.karlrunge.com/x11vnc/index.html#FAQ-14 - 60. http://www.karlrunge.com/x11vnc/index.html#FAQ-15 - 61. http://www.karlrunge.com/x11vnc/index.html#FAQ-16 - 62. http://www.karlrunge.com/x11vnc/index.html#FAQ-17 - 63. http://www.karlrunge.com/x11vnc/index.html#FAQ-18 - 64. http://www.karlrunge.com/x11vnc/index.html#FAQ-19 - 65. http://www.karlrunge.com/x11vnc/index.html#FAQ-20 - 66. http://www.karlrunge.com/x11vnc/index.html#FAQ-21 - 67. http://www.karlrunge.com/x11vnc/index.html#FAQ-22 - 68. http://www.karlrunge.com/x11vnc/index.html#FAQ-23 - 69. http://www.karlrunge.com/x11vnc/index.html#FAQ-24 - 70. http://www.karlrunge.com/x11vnc/index.html#FAQ-25 - 71. http://www.karlrunge.com/x11vnc/index.html#FAQ-26 - 72. http://www.karlrunge.com/x11vnc/index.html#FAQ-27 - 73. http://www.karlrunge.com/x11vnc/index.html#FAQ-28 - 74. http://www.karlrunge.com/x11vnc/index.html#FAQ-29 - 75. http://www.karlrunge.com/x11vnc/index.html#FAQ-30 - 76. http://www.karlrunge.com/x11vnc/index.html#FAQ-31 - 77. http://www.karlrunge.com/x11vnc/index.html#FAQ-32 - 78. http://www.karlrunge.com/x11vnc/index.html#FAQ-33 - 79. http://www.karlrunge.com/x11vnc/index.html#FAQ-34 - 80. http://www.karlrunge.com/x11vnc/index.html#FAQ-35 - 81. http://www.karlrunge.com/x11vnc/index.html#FAQ-36 - 82. http://www.karlrunge.com/x11vnc/index.html#FAQ-37 - 83. http://www.karlrunge.com/x11vnc/index.html#FAQ-38 - 84. http://www.karlrunge.com/x11vnc/index.html#FAQ-39 - 85. http://www.karlrunge.com/x11vnc/index.html#FAQ-40 - 86. http://www.karlrunge.com/x11vnc/index.html#FAQ-41 - 87. http://www.karlrunge.com/x11vnc/index.html#FAQ-42 - 88. http://www.karlrunge.com/x11vnc/index.html#FAQ-43 - 89. http://www.karlrunge.com/x11vnc/index.html#FAQ-44 - 90. http://www.karlrunge.com/x11vnc/index.html#FAQ-45 - 91. http://www.karlrunge.com/x11vnc/index.html#FAQ-46 - 92. http://www.karlrunge.com/x11vnc/index.html#FAQ-47 - 93. http://www.karlrunge.com/x11vnc/index.html#FAQ-48 - 94. http://www.karlrunge.com/x11vnc/index.html#FAQ-49 - 95. http://www.karlrunge.com/x11vnc/index.html#FAQ-50 - 96. http://www.karlrunge.com/x11vnc/index.html#FAQ-51 - 97. http://www.karlrunge.com/x11vnc/index.html#FAQ-52 - 98. http://www.karlrunge.com/x11vnc/index.html#FAQ-53 - 99. http://www.karlrunge.com/x11vnc/index.html#FAQ-54 - 100. http://www.karlrunge.com/x11vnc/index.html#FAQ-55 - 101. http://www.karlrunge.com/x11vnc/index.html#FAQ-56 - 102. http://www.karlrunge.com/x11vnc/index.html#FAQ-57 - 103. http://www.karlrunge.com/x11vnc/index.html#FAQ-58 - 104. http://www.karlrunge.com/x11vnc/index.html#FAQ-59 - 105. http://www.karlrunge.com/x11vnc/index.html#FAQ-60 - 106. http://www.karlrunge.com/x11vnc/index.html#FAQ-61 - 107. http://www.karlrunge.com/x11vnc/index.html#FAQ-62 - 108. http://www.karlrunge.com/x11vnc/index.html#FAQ-63 - 109. http://www.karlrunge.com/x11vnc/index.html#FAQ-64 - 110. http://www.karlrunge.com/x11vnc/index.html#FAQ-65 - 111. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 112. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html - 113. http://www.karlrunge.com/x11vnc/index.html#building - 114. http://www.karlrunge.com/x11vnc/index.html#buildfaq - 115. http://packages.debian.org/x11vnc - 116. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc - 117. http://dag.wieers.com/packages/x11vnc/ - 118. http://www.sunfreeware.com/ - 119. http://www.bell-labs.com/project/wwexptools/packages.html - 120. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 121. http://www.karlrunge.com/x11vnc/bins - 122. http://www.tightvnc.com/download.html - 123. http://www.realvnc.com/download-free.html - 124. http://sourceforge.net/projects/cotvnc/ - 125. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 126. http://www.karlrunge.com/x11vnc/x11vnc.c - 127. http://fredrik.hubbe.net/x2vnc.html - 128. http://www.hubbe.net/~hubbe/win2vnc.html - 129. http://www.deboer.gmxhome.de/ - 130. http://sourceforge.net/projects/win2vnc/ - 131. http://fredrik.hubbe.net/x2vnc.html - 132. http://freshmeat.net/projects/x2x/ - 133. http://ftp.digital.com/pub/Digital/SRC/x2x/ - 134. http://zapek.com/software/zvnc/ - 135. http://www.karlrunge.com/x11vnc/index.html#8bpp - 136. http://www.karlrunge.com/x11vnc/index.html#overlays - 137. http://www.karlrunge.com/x11vnc/index.html#xauth_pain - 138. http://www.karlrunge.com/x11vnc/index.html#noshm - 139. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 140. http://www.karlrunge.com/x11vnc/index.html#passwd - 141. http://www.karlrunge.com/x11vnc/index.html#passwdfile - 142. http://www.karlrunge.com/x11vnc/index.html#inetd - 143. ftp://ftp.x.org/ - 144. http://www.karlrunge.com/x11vnc/dtVncPopup - 145. http://www.karlrunge.com/x11vnc/index.html#passwdfile - 146. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 147. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 148. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 149. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 150. http://www.karlrunge.com/x11vnc/blockdpy.c - 151. http://www.karlrunge.com/x11vnc/index.html#display_manager - 152. http://www.karlrunge.com/x11vnc/index.html#inetd - 153. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop - 154. http://www.jirka.org/gdm-documentation/x241.html - 155. http://www.karlrunge.com/x11vnc/x11vnc_loop - 156. http://www.karlrunge.com/x11vnc/index.html#xterminal_xauth - 157. http://www.karlrunge.com/x11vnc/shm_clear - 158. http://www.karlrunge.com/x11vnc/index.html#noshm - 159. http://www.tightvnc.com/ - 160. http://www.karlrunge.com/x11vnc/tight-vncviewer-alphahack.patch - 161. http://www.tightvnc.com/ - 162. http://www.karlrunge.com/x11vnc/index.html#greaterless - 163. http://www.karlrunge.com/x11vnc/index.html#xkbmodtweak - 164. http://www.karlrunge.com/x11vnc/index.html#xkbmodtweak - 165. http://www.karlrunge.com/x11vnc/index.html#display_manager - 166. http://www.karlrunge.com/x11vnc/index.html#scaling - 167. http://www.karlrunge.com/x11vnc/index.html#solshm + 11. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 12. http://www.karlrunge.com/x11vnc/index.html#faq-xperms + 13. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download + 14. http://www.sun.com/software/solaris/freeware/ + 15. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 16. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 17. http://www.karlrunge.com/x11vnc/index.html#faq-service + 18. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 19. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file + 20. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 21. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 22. http://www.karlrunge.com/x11vnc/index.html#tightvnc_via + 23. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 24. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 25. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 26. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 27. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 28. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 29. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 30. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt + 31. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 32. http://sourceforge.net/projects/libvncserver/ + 33. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=292078 + 34. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=292078 + 35. http://www.karlrunge.com/x11vnc/x11vnc.c + 36. http://www.karlrunge.com/x11vnc/tkx11vnc.h + 37. http://www.karlrunge.com/x11vnc/index.html#faq-binaries + 38. http://www.tightvnc.com/download.html + 39. http://www.realvnc.com/download-free.html + 40. http://sourceforge.net/projects/cotvnc/ + 41. http://www.karlrunge.com/x11vnc/rx11vnc + 42. http://www.karlrunge.com/x11vnc/rx11vnc.pl + 43. http://www.sunfreeware.com/ + 44. ftp://ftp.uu.net/graphics/jpeg/ + 45. http://www.gzip.org/zlib/ + 46. http://www.sunfreeware.com/ + 47. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build + 48. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 49. http://www.tightvnc.com/ + 50. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 51. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 52. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 53. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg + 54. http://wwws.sun.com/sunray/index.html + 55. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 56. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 57. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 58. http://www.karlrunge.com/x11vnc/shm_clear + 59. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 60. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 61. mailto:xvml@karlrunge.com + 62. http://www.karlrunge.com/x11vnc/index.html#faq-xperms + 63. http://www.karlrunge.com/x11vnc/index.html#faq-build + 64. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build + 65. http://www.karlrunge.com/x11vnc/index.html#faq-binaries + 66. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download + 67. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts + 68. http://www.karlrunge.com/x11vnc/index.html#faq-config-file + 69. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg + 70. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe + 71. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc + 72. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp + 73. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 74. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 75. http://www.karlrunge.com/x11vnc/index.html#faq-windowid + 76. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id + 77. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp + 78. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 79. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 80. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg + 81. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control + 82. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 83. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 84. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt + 85. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared + 86. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt + 87. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 88. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix + 89. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty + 90. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt + 91. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords + 92. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt + 93. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy + 94. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock + 95. http://www.karlrunge.com/x11vnc/index.html#faq-service + 96. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 97. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 98. http://www.karlrunge.com/x11vnc/index.html#faq-java-http + 99. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect + 100. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 101. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource + 102. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource + 103. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link + 104. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 105. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape + 106. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha + 107. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 108. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow + 109. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions + 110. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt + 111. http://www.karlrunge.com/x11vnc/index.html#faq-altgr + 112. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 113. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 114. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys + 115. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still + 116. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt + 117. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta + 118. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click + 119. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars + 120. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 121. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama + 122. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen + 123. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr + 124. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen + 125. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 126. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars + 127. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard + 128. http://www.karlrunge.com/x11vnc/index.html#faq-beeps + 129. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 130. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 134. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 135. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html + 136. http://www.karlrunge.com/x11vnc/index.html#building + 137. http://www.karlrunge.com/x11vnc/index.html#faq-build + 138. http://packages.debian.org/x11vnc + 139. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc + 140. http://dag.wieers.com/packages/x11vnc/ + 141. http://www.sunfreeware.com/ + 142. http://www.bell-labs.com/project/wwexptools/packages.html + 143. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 144. http://www.karlrunge.com/x11vnc/bins + 145. http://www.tightvnc.com/download.html + 146. http://www.realvnc.com/download-free.html + 147. http://sourceforge.net/projects/cotvnc/ + 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 149. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 153. http://www.karlrunge.com/x11vnc/x11vnc.c + 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe + 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 156. http://fredrik.hubbe.net/x2vnc.html + 157. http://www.hubbe.net/~hubbe/win2vnc.html + 158. http://www.deboer.gmxhome.de/ + 159. http://sourceforge.net/projects/win2vnc/ + 160. http://fredrik.hubbe.net/x2vnc.html + 161. http://freshmeat.net/projects/x2x/ + 162. http://ftp.digital.com/pub/Digital/SRC/x2x/ + 163. http://zapek.com/software/zvnc/ + 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 165. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor + 167. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 172. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid + 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder + 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 179. http://www.karlrunge.com/x11vnc/index.html#xauth_pain + 180. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys + 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd + 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 192. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd + 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd + 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared + 200. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 201. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 202. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 205. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 206. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 207. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 208. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 212. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly + 216. ftp://ftp.x.org/ + 217. http://www.karlrunge.com/x11vnc/dtVncPopup + 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 220. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 223. http://www.karlrunge.com/x11vnc/blockdpy.c + 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 227. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 228. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 229. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 231. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris + 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 233. http://www.jirka.org/gdm-documentation/x241.html + 234. http://www.karlrunge.com/x11vnc/x11vnc_loop + 235. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 242. http://www.karlrunge.com/x11vnc/shm_clear + 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 245. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 254. http://www.tightvnc.com/ + 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 270. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode + 271. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 272. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 278. http://www.tightvnc.com/ + 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 287. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 288. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 292. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes + 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 303. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 308. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 314. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 322. mailto:xvml@karlrunge.com ======================================================================= @@ -3116,7 +3394,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.7.1 lastmod: 2005-02-22 +x11vnc: allow VNC connections to real X11 displays. 0.7.1 lastmod: 2005-02-23 x11vnc options: -display disp -auth file @@ -3191,7 +3469,7 @@ libvncserver options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.7.1 lastmod: 2005-02-22 +x11vnc: allow VNC connections to real X11 displays. 0.7.1 lastmod: 2005-02-23 Typical usage is: @@ -3458,7 +3736,7 @@ Options: established try to switch to one of the users in the comma separated "list". If x11vnc is not running as root this option is ignored. - + Why use this option? In general it is not needed since x11vnc is already connected to the X display and can perform its primary functions. The option was added @@ -3472,10 +3750,10 @@ Options: It also affects the ability to read files for options such as -connect, -allow, and -remap. Note that the -connect file is also sometimes written to. - + So be careful with this option since in many situations its use can decrease security. - + The switch to a user will only take place if the display can still be successfully opened as that user (this is primarily to try to guess the actual owner @@ -3483,7 +3761,7 @@ Options: Note that a malicious user "barney" by quickly using "xhost +" when logging in may get x11vnc to switch to user "fred". What happens next? - + Under display managers it may be a long time before the switch succeeds (i.e. a user logs in). To make it switch immediately regardless if the display @@ -3492,18 +3770,18 @@ Options: The latter (i.e. switching immediately to user "nobody") is probably the only use of this option that increases security. - + To immediately switch to a user *before* connections to the X display are made or any files opened use the "=" character: "-users =bob". That user needs to be able to open the X display of course. - + The special user "guess=" means to examine the utmpx database (see who(1)) looking for a user attached to the display number (from DISPLAY or -display option) and try him/her. To limit the list of guesses, use: "-users guess=bob,betty". - + Even more sinister is the special user "lurk=" that means to try to guess the DISPLAY from the utmpx login database as well. So it "lurks" waiting for anyone @@ -3516,11 +3794,11 @@ Options: they are in the utmpx database) for all users that are logged in. Examples: "-users lurk=" and also "-users lurk=:0-1,bob,mary" - + Be especially careful using the "guess=" and "lurk=" modes. They are not recommended for use on machines with untrustworthy local users. - + -noshm Do not use the MIT-SHM extension for the polling. Remote displays can be polled this way: be careful this can use large amounts of network bandwidth. This is @@ -3705,7 +3983,7 @@ Options: default (see -noxfixes below). This can be disabled with -nocursor, and also some values of the "mode" option below. - + Note that under XFIXES cursors with transparency (alpha channel) will not be exactly represented and one may find Overlay preferable. See also the -alphacut and @@ -3752,7 +4030,7 @@ Options: with values ranging from 0 to 255) Any cursor pixel with alpha value less than n becomes completely transparent. Otherwise the pixel is completely opaque. Default 240 - + Note: the options -alphacut, -alphafrac, and -alphafrac may be removed if a more accurate internal method for handling cursor transparency is implemented. @@ -4327,7 +4605,7 @@ These options are passed to libvncserver: -rfbwait time max time in ms to wait for RFB client -rfbauth passwd-file use authentication on RFB protocol (use 'storepasswd' to create a password file) --passwd plain-password use authentication +-passwd plain-password use authentication (use plain-password as password, USE AT YOUR RISK) -deferupdate time time in ms to defer updates (default 40) -desktop name VNC desktop name (default "LibVNCServer") diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index 84263e4..8df6029 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "February 2005" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.7.1, lastmod: 2005-02-22 + version: 0.7.1, lastmod: 2005-02-23 .SH SYNOPSIS .B x11vnc [OPTION]... diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index 1ee7bd8..27148fc 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -290,7 +290,7 @@ static int xdamage_base_event_type; #endif /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.7.1 lastmod: 2005-02-22"; +char lastmod[] = "0.7.1 lastmod: 2005-02-23"; /* X display info */ |