diff options
| author | runge <runge> | 2005-03-29 13:39:27 +0000 |
|---|---|---|
| committer | runge <runge> | 2005-03-29 13:39:27 +0000 |
| commit | dfe5981ce9c6f3e44d9949017a0fa9a84d9856e7 (patch) | |
| tree | 003294e34a8eb7047db4d9776a4783b71ebcdf38 | |
| parent | 1ce941862201ca320f46a3c23870555e41813f2f (diff) | |
| download | libvncserver-dfe5981ce9c6f3e44d9949017a0fa9a84d9856e7.zip libvncserver-dfe5981ce9c6f3e44d9949017a0fa9a84d9856e7.tar.gz | |
x11vnc: fix event leaks, build-time customizations, -nolookup
| -rw-r--r-- | ChangeLog | 3 | ||||
| -rw-r--r-- | x11vnc/ChangeLog | 8 | ||||
| -rw-r--r-- | x11vnc/README | 1739 | ||||
| -rwxr-xr-x | x11vnc/tkx11vnc | 1 | ||||
| -rw-r--r-- | x11vnc/tkx11vnc.h | 1 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 78 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 726 |
7 files changed, 1556 insertions, 1000 deletions
@@ -1,3 +1,6 @@ +2005-03-29 Karl Runge <runge@karlrunge.com> + * x11vnc: fix event leaks, build-time customizations, -nolookup + 2005-03-19 Karl Runge <runge@karlrunge.com> * x11vnc: scale cursors by default, -scale_cursor to tune, -arrow n, -norepeat n, speed up integer magnification. diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index 8307798..a996b14 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,11 @@ +2005-03-29 Karl Runge <runge@karlrunge.com> + * build-time customizations X11VNC_SHARED, X11VNC_FOREVER, + REMOTE_CONTROL, SMALL_FOOTPRINT for CPPFLAGS + * fix event leaks for xkb BellNotify and ClientMessage and others, + esp. under -nofb. make nofb work with remote control. + * -nolookup for bad DNS setups. + * more playing with pointer_mode: check_user_input3() + 2005-03-19 Karl Runge <runge@karlrunge.com> * scale cursors along with display. Use -scale_cursor to change or disable cursor scaling. diff --git a/x11vnc/README b/x11vnc/README index 202904e..dae101d 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Sun Mar 20 00:02:00 EST 2005 +x11vnc README file Date: Tue Mar 29 09:30:54 EST 2005 The following information is taken from these URLs: @@ -13,8 +13,9 @@ http://www.karlrunge.com/x11vnc/index.html: _________________________________________________________________ -x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]Downloads) -(to [3]Building) +x11vnc: a VNC server for real X displays + (to [1]FAQ) (to [2]Downloads) (to [3]Building) (to +[4]Contrib) x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and @@ -26,8 +27,8 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]Downloads) problems centered around esoteric C++ toolkits. x11vnc is written in plain C and uses only standard libraries. I also added a few enhancements to improve the interactive response, add esoteric - features, etc. The [4]FAQ contains a lot of information and solutions - to problems, but please feel free to [5]contact me if you have + features, etc. The [5]FAQ contains a lot of information and solutions + to problems, but please feel free to [6]contact me if you have problems or questions. Background: @@ -39,9 +40,9 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]Downloads) framebuffer (RFB) protocol Some VNC links: - * [6]http://www.uk.research.att.com/vnc/ - * [7]http://www.realvnc.com - * [8]http://www.tightvnc.com + * [7]http://www.uk.research.att.com/vnc/ + * [8]http://www.realvnc.com + * [9]http://www.tightvnc.com For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated @@ -79,9 +80,9 @@ x11vnc: a VNC server for real X displays (to [1]FAQ) (to [2]Downloads) 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 - run on sitting-here.west. We recommend [10]TightVNC Viewers. + Step 0. Download x11vnc ([10]see below) and have it available to run + on far-away.east. Similarly, have a VNC viewer (e.g. vncviewer) ready + to run on sitting-here.west. We recommend [11]TightVNC Viewers. Step 1. By some means log in to far-away.east and get a command shell running there. You can use ssh, rlogin, telnet, or any other method to @@ -99,9 +100,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 [11]-auth option) to point to the + environment variable (or use the [12]-auth option) to point to the correct MIT-MAGIC-COOKIE file (e.g. /home/joe/.Xauthority). More on - this [12]below. + this [13]below. There will then be much chatter printed out from x11vnc, until it finally says something like: @@ -119,8 +120,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 see [13]this FAQ. For Solaris, vncviewer - is available in the [14]Companion CD package SFWvnc ). + viewer for your platform or see [14]this FAQ. For Solaris, vncviewer + is available in the [15]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: @@ -130,13 +131,13 @@ 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 [15]-forever option to have + shutdown automatically (or you can use the [16]-forever option to have it wait for additional viewer connections). 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, + terminal window with the [17]-forever option or as a [18]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. + [19]password or [20]other measures if you do that. Desktop Sharing: The above more or less assumed nobody was sitting at @@ -152,7 +153,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 "[20]-connect + start their VNC viewers. For this usage mode the "[21]-connect host1,host2" option may be of use automatically connect to vncviewers in "-listen" mode on the list of hosts. _________________________________________________________________ @@ -179,8 +180,8 @@ 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 [21]inetd(1)). See the 3rd - script example [22]below for more info. + far-away.east or having it started by [22]inetd(1)). See the 3rd + script example [23]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 @@ -196,7 +197,7 @@ 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 [23]-bg (forks into background after connection to the + x11vnc option [24]-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. _________________________________________________________________ @@ -227,7 +228,7 @@ done #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: + using the [25]-connect option: #!/bin/sh # usage: x11vnc_ssh <host>:<xdisplay> # e.g.: x11vnc_ssh snoopy.peanuts.com:0 @@ -269,52 +270,52 @@ 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 [25]inetd(1)), you can simply + connections (or have it started out of [26]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 #1. example script that the - [26]option "-rfbauth .vnc/passwd" provides additional protection by + [27]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 [27]-storepasswd + vncpasswd or storepasswd programs, or the x11vnc [28]-storepasswd option can be used to create the password file. x11vnc also has the - slightly less secure [28]-passwdfile and "-passwd XXXXX" [29]options + slightly less secure [29]-passwdfile and "-passwd XXXXX" [30]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 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 + -localhost [31]options and building x11vnc with [32]tcp_wrappers support to limit host access. _________________________________________________________________ Downloading x11vnc: - x11vnc is a contributed program to the [32]LibVNCServer project at + x11vnc is a contributed program to the [33]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 Feb 2005, the [33]x11vnc-0.7.1.tar.gz source package is - released (recommended download) . The [34]x11vnc 0.7.1 release notes. + link. As of Feb 2005, the [34]x11vnc-0.7.1.tar.gz source package is + released (recommended download) . The [35]x11vnc 0.7.1 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 [35]x11vnc.c file to replace the one in the above + bleeding edge [36]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 [36]tkx11vnc.h file. If you have an + update the tcl/tk gui with the [37]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 [37]FAQ below for information about where you might obtain a + See the [38]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 these links: - * [38]http://www.tightvnc.com/download.html - * [39]http://www.realvnc.com/download-free.html - * [40]http://sourceforge.net/projects/cotvnc/ + * [39]http://www.tightvnc.com/download.html + * [40]http://www.realvnc.com/download-free.html + * [41]http://sourceforge.net/projects/cotvnc/ More tools: Here is a rsh/ssh wrapper script rx11vnc that attempts to @@ -325,8 +326,8 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. 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: - * [41]rx11vnc wrapper script - * [42]rx11vnc.pl wrapper script to tunnel traffic thru ssh + * [42]rx11vnc wrapper script + * [43]rx11vnc.pl wrapper script to tunnel traffic thru ssh _________________________________________________________________ @@ -356,7 +357,7 @@ 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. For Solaris pre-built gcc binaries are at - [43]http://www.sunfreeware.com/ However, one user reports it does + [44]http://www.sunfreeware.com/ However, one user reports it does work fine when built with Sun Studio 10, so YMMV. _________________________________________________________________ @@ -398,9 +399,9 @@ r/sfw; make' 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 + [45]ftp://ftp.uu.net/graphics/jpeg/ and zlib at + [46]http://www.gzip.org/zlib/. See also + [47]http://www.sunfreeware.com/ for Solaris binary packages of these libraries as well as for gcc. Normally they will install into /usr/local but you can install them anywhere with the --prefix=/path/to/anywhere, etc. @@ -408,7 +409,7 @@ r/sfw; make' 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 environment variables. #!/bin/sh # Build script for Solaris, etc, with gcc, libjpeg and libz in @@ -472,7 +473,7 @@ ls -l ./x11vnc/x11vnc like that. If you need to build on Solaris 2.5.1 or earlier or other older Unix - OS's, see [47]this workaround FAQ. + OS's, see [48]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 @@ -491,12 +492,12 @@ ls -l ./x11vnc/x11vnc to have static archives, e.g. libz.a and libjpeg.a for the nonstandard libraries so that they get bolted into the x11vnc binary. - 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 - gettimeofday(). As a workaround add this to CPPFLAGS: - -DLIBVNCSERVER_HAVE_GETTIMEOFDAY=1. You may get some warnings but we - have verified that this generates working x11vnc binaries on HP-UX - hppa and ia64. + Finally, there seems to be a bug with configure on HP-UX 11.xx: it + thinks it cannot find gettimeofday(). As a workaround add this to + CPPFLAGS: -DLIBVNCSERVER_HAVE_GETTIMEOFDAY=1. You may get some + warnings but we have verified that this generates working x11vnc + binaries on HP-UX hppa and ia64. (This problem will be fixed in + version 0.7.2 by using a newer autoconf). Here is what we recently did to build x11vnc 0.7.1 on HP-UX 11.11 env CPPFLAGS="-DLIBVNCSERVER_HAVE_GETTIMEOFDAY=1 -I $HOME/hpux/jpeg/include -I @@ -510,6 +511,14 @@ make Some Notes: + Both a client and a server: It is sometimes confusing to people that + x11vnc is both a client and a server at the same time. It is an X + client because it connects to the running X server to do the screen + polls. Think of it as a rather efficient "screenshot" program running + continuously. It is a server in the sense that it is a VNC server that + VNC viewers on the network can connect to and view the screen + framebuffer it manages. + Network performance: Whether you are using Xvnc or x11vnc it is always a good idea to have a solid background color instead of a pretty background image. Each and every re-exposure of the background @@ -520,10 +529,10 @@ make 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 - [48]-solid [color] option that works on recent GNOME, KDE, and CDE and + [49]-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 [49]TightVNC encoding gives the best response for my + I also find the [50]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. @@ -535,16 +544,16 @@ make 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 "[50]-rfbport NNNN" + far-away.east:1. You can force the issue with the "[51]-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 [51]command line options. Useful options are -nap to use fewer + via its [52]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 [52]-storepasswd option can be + storepasswd programs, or the x11vnc [53]-storepasswd option can be used to create the password file). Algorithm: How does x11vnc do it? Rather brute-forcedly: it @@ -572,15 +581,15 @@ make 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 [53]even more interesting effect if + decorations. There will be an [54]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) - [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 + [55]SunRay session (Please remember to use [56]-nap and maybe + [57]-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 @@ -603,7 +612,7 @@ make 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 - [57]-rfbport NNNN option. + [58]-rfbport NNNN option. SunRay Gotcha #2: If you get an error like: shmget(tile) failed. @@ -616,7 +625,7 @@ make 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 + the ipcrm command. I wrote a script [59]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 @@ -668,10 +677,10 @@ make * 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" [59]options, however, for a partial hack for the root + some" [60]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 + [61]-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 @@ -686,9 +695,9 @@ make Evidently a timing related bug and difficult to reproduce... * Using -threads can expose some bugs in libvncserver. - Please feel free to [61]contact me if you have any questions, + Please feel free to [62]contact me if you have any questions, problems, or comments about x11vnc, etc. - Also, some people ask if they can make a donation, see [62]this link + Also, some people ask if they can make a donation, see [63]this link for that. _________________________________________________________________ @@ -697,266 +706,276 @@ make [Building and Starting] - [63]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? + [64]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed + (null)" or "Xlib: connection to ":0.0" refused by server Xlib: No + protocol specified" and then exits. What do I need to do? - [64]Q-2: I can't get x11vnc and/or libvncserver to compile. + [65]Q-2: I can't get x11vnc and/or libvncserver to compile. - [65]Q-3: Help, I need to run x11vnc on Solaris 2.5.1 (or other old + [66]Q-3: I just built x11vnc successfully, but when I use it my + keystrokes and mouse button clicks are ignored (I am able to move the + mouse though). + + [67]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old Unix/Linux) and it doesn't compile! - [66]Q-4: Where can I get a precompiled x11vnc binary for my Operating + [68]Q-5: Where can I get a precompiled x11vnc binary for my Operating System? - [67]Q-5: Where can I get a VNC Viewer binary (or source code) for the + [69]Q-6: Where can I get a VNC Viewer binary (or source code) for the Operating System I will be viewing from? - [68]Q-6: How can I see all of x11vnc's command line options and + [70]Q-7: How can I see all of x11vnc's command line options and documentation on how to use them? - [69]Q-7: I don't like typing arcane command line options every time I + [71]Q-8: 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? - [70]Q-8: Can I make x11vnc more quiet and also go into the background + [72]Q-9: Can I make x11vnc more quiet and also go into the background after starting up? - [71]Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies + [73]Q-10: 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. + [74]Q-11: Are there any build-time customizations possible, e.g. + change defaults, create a smaller binary, etc? + [Win2VNC Related] - [72]Q-10: I have two separate machine displays in front of me, one + [75]Q-12: 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? - [73]Q-11: I am running Win2VNC on my Windows machine and "x11vnc + [76]Q-13: I am running Win2VNC on my Windows machine and "x11vnc -nofb" on Unix to pass keyboard and mouse to the Unix monitor. Whenever I start Win2VNC it quickly disconnects and x11vnc says: rfbProcessClientNormalMessage: read: Connection reset by peer [Color Issues] - [74]Q-12: The X display I run x11vnc on is only 8 bits per pixel (bpp) + [77]Q-14: The X display I run x11vnc on is only 8 bits per pixel (bpp) PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while they are incorrect in certain windows. - [75]Q-13: Color problems: Why are the colors for some windows messed + [78]Q-15: Color problems: Why are the colors for some windows messed up in x11vnc? BTW, my X display has nice overlay/multi-depth visuals of different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - [76]Q-14: How do I figure out the window id to supply to the -id + [79]Q-16: How do I figure out the window id to supply to the -id windowid option? - [77]Q-15: Why don't menus or other transient windows come up when I am + [80]Q-17: Why don't menus or other transient windows come up when I am using the -id windowid option to view a single application window? - [78]Q-16: My X display is depth 24 at 24bpp (instead of the normal + [81]Q-18: My X display is depth 24 at 24bpp (instead of the normal depth 24 at 32bpp). I'm having lots of color and visual problems with x11vnc and/or vncviewer. What's up? [Xterminals] - [79]Q-17: Can I use x11vnc to view and interact with an Xterminal + [82]Q-19: 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? - [80]Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for + [83]Q-20: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a Unix/Linux machine acting as an Xterminal? [Remote Control] - [81]Q-19: How do I stop x11vnc once it is running in the background? + [84]Q-21: How do I stop x11vnc once it is running in the background? - [82]Q-20: Can I change settings in x11vnc without having to restart + [85]Q-22: Can I change settings in x11vnc without having to restart it? Can I remote control it? [Security and Permissions] - [83]Q-21: How do I create a VNC password for use with x11vnc? + [86]Q-23: How do I create a VNC password for use with x11vnc? - [84]Q-22: Can I have two passwords for VNC viewers, one for full + [87]Q-24: Can I have two passwords for VNC viewers, one for full access and the other for view-only access to the display? - [85]Q-23: Can I fine tune what types of user input are allowed? E.g. + [88]Q-25: 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? - [86]Q-24: Why does x11vnc exit as soon as the VNC viewer disconnects? + [89]Q-26: 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? - [87]Q-25: Can I limit which machines incoming VNC clients can connect + [90]Q-27: Can I limit which machines incoming VNC clients can connect from? - [88]Q-26: How do I build x11vnc/libvncserver with libwrap + [91]Q-28: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) support? - [89]Q-27: Can I have x11vnc only listen on one network interface (e.g. + [92]Q-29: Can I have x11vnc only listen on one network interface (e.g. internal LAN) rather than having it listen on all network interfaces and relying on -allow to filter unwanted connections out? - [90]Q-28: Now that -localhost implies listening only on the loopback + [93]Q-30: Now that -localhost implies listening only on the loopback interface, how I can occasionally allow in a non-localhost via the allowonce remote control command? - [91]Q-29: How can I tunnel my connection to x11vnc via an encrypted + [94]Q-31: How can I tunnel my connection to x11vnc via an encrypted SSH channel between two Unix machines? - [92]Q-30: How can I tunnel my connection to x11vnc via an encrypted + [95]Q-32: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [93]Q-31: Can I prompt the user at the local X display whether the + [96]Q-33: 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? - [94]Q-32: Does x11vnc support Unix usernames and passwords? Can I + [97]Q-34: Does x11vnc support Unix usernames and passwords? Can I further limit the set of Unix usernames who can connect to the VNC desktop? - [95]Q-33: I start x11vnc as root because it is launched via inetd(1) + [98]Q-35: 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? - [96]Q-34: I use a screen-lock when I leave my workstation (e.g. + [99]Q-36: 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? - [97]Q-35: Can I have x11vnc automatically lock the screen when I + [100]Q-37: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? [Display Managers and Services] - [98]Q-36: How can I run x11vnc as a "service" that is always + [101]Q-38: How can I run x11vnc as a "service" that is always available? - [99]Q-37: How can I use x11vnc to connect to an X login screen like + [102]Q-39: 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). - [100]Q-38: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + [103]Q-40: Can I run x11vnc out of inetd(1)? How about xinetd(1)? - [101]Q-39: How do I make x11vnc work with the Java VNC viewer applet + [104]Q-41: How do I make x11vnc work with the Java VNC viewer applet in a web browser? - [102]Q-40: Are reverse connections (i.e. the VNC server connecting to + [105]Q-42: Are reverse connections (i.e. the VNC server connecting to the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported? - [103]Q-41: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a + [106]Q-43: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real display, but for a virtual one I keep around). + [107]Q-44: How can I use x11vnc on "headless" machines? Why might I + want to? + [Resource Usage and Performance] - [104]Q-42: I have lots of memory, but why does x11vnc fail with + [108]Q-45: 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)? - [105]Q-43: How can I make x11vnc use less system resources? + [109]Q-46: How can I make x11vnc use less system resources? - [106]Q-44: How can I make x11vnc use MORE system resources? + [110]Q-47: How can I make x11vnc use MORE system resources? - [107]Q-45: I use x11vnc over a slow link with high latency (e.g. + [111]Q-48: I use x11vnc over a slow link with high latency (e.g. dialup modem), is there anything I can do to speed things up? - [108]Q-46: When I drag windows around with the mouse or scroll up and + [112]Q-49: 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? - [109]Q-47: Does x11vnc support the X DAMAGE Xserver extension to find + [113]Q-50: Does x11vnc support the X DAMAGE Xserver extension to find modified regions of the screen quickly and efficiently? [Mouse Cursor Shapes] - [110]Q-48: Why isn't the mouse cursor shape (the little icon shape + [114]Q-51: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? - [111]Q-49: When using XFIXES cursorshape mode, some of the cursors + [115]Q-52: 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? - [112]Q-50: In XFIXES mode, are there any hacks to handle cursor + [116]Q-53: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? [Mouse Pointer] - [113]Q-51: Why does the mouse arrow just stay in one corner in my + [117]Q-54: Why does the mouse arrow just stay in one corner in my vncviewer, whereas my cursor (that does move) is just a dot? - [114]Q-52: Can I take advantage of the TightVNC extension to the VNC + [118]Q-55: 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)? - [115]Q-53: Is it possible to swap the mouse buttons (e.g. left-handed + [119]Q-56: 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] - [116]Q-54: How can I get my AltGr and Shift modifiers to work between + [120]Q-57: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - [117]Q-55: When I try to type a "<" (i.e. less than) instead I get ">" + [121]Q-58: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! - [118]Q-56: I'm using an "international" keyboard (e.g. German "de", or + [122]Q-59: 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? - [119]Q-57: When typing I sometimes get double, triple, or more of my + [123]Q-60: 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? - [120]Q-58: The x11vnc -norepeat mode is in effect, but I still get + [124]Q-61: The x11vnc -norepeat mode is in effect, but I still get repeated keystrokes!! - [121]Q-59: The machine where I run x11vnc has an AltGr key, but the + [125]Q-62: 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? - [122]Q-60: I have a Sun machine I run x11vnc on. Its Sun keyboard has + [126]Q-63: 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) - [123]Q-61: Can I map a keystroke to a mouse button click on the remote + [127]Q-64: Can I map a keystroke to a mouse button click on the remote machine? [Screen Related Issues and Features] - [124]Q-62: The remote display is larger (in number of pixels) than the + [128]Q-65: 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? - [125]Q-63: Does x11vnc support server-side framebuffer scaling? (E.g. + [129]Q-66: Does x11vnc support server-side framebuffer scaling? (E.g. to make the desktop smaller). - [126]Q-64: Does x11vnc work with Xinerama? (i.e. multiple monitors + [130]Q-67: Does x11vnc work with Xinerama? (i.e. multiple monitors joined together to form one big, single screen). - [127]Q-65: Can I use x11vnc on a multi-headed display that is not + [131]Q-68: Can I use x11vnc on a multi-headed display that is not Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? - [128]Q-66: Can x11vnc show only a portion of the display? (E.g. for a + [132]Q-69: Can x11vnc show only a portion of the display? (E.g. for a special purpose rfb application). - [129]Q-67: Does x11vnc support the XRANDR (X Resize, Rotate and + [133]Q-70: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) extension? Whenever I rotate or resize the screen x11vnc just seems to crash. - [130]Q-68: Why is the view in my VNC viewer completely black? Or why + [134]Q-71: Why is the view in my VNC viewer completely black? Or why is everything flashing around randomly? - [131]Q-69: I use Linux Virtual Consoles (VC's) to implement 'Fast User + [135]Q-72: 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 @@ -964,9 +983,9 @@ make otherwise all messed up unless the X session x11vnc is attached to is in the active VC? - [132]Q-70: Can I use x11vnc to view my VMWare session remotely? + [136]Q-73: Can I use x11vnc to view my VMWare session remotely? - [133]Q-71: I am using x11vnc where my local machine has "popup/hidden + [137]Q-74: 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 @@ -974,13 +993,13 @@ make [Misc: Clipboard, Beeps, Thanks, etc.] - [134]Q-72: Does the Clipboard/Selection get transferred between the + [138]Q-75: Does the Clipboard/Selection get transferred between the vncviewer and the X display? - [135]Q-73: Why don't I hear the "Beeps" in my X session (e.g. when + [139]Q-76: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? - [136]Q-74: Thanks for your program and for your help! Can I make a + [140]Q-77: Thanks for your program and for your help! Can I make a donation? _________________________________________________________________ @@ -988,18 +1007,18 @@ make [Building and Starting] 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? + (null)" or "Xlib: connection to ":0.0" refused by server Xlib: No + protocol specified" and then exits. What do I need to do? 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 [137]-display option to + your DISPLAY environment variable or use the [141]-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 [138]-auth option to point to the + environment variable or use the [142]-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 @@ -1013,14 +1032,7 @@ make 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 [139]-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 [140]-auth - option). This command is often useful to find non-standard settings - for XAUTHORITY: - ps wwwweaux | tr ' ' '\n' | grep XAUTHORITY | sort -u + documentation on the [143]-users option). To test out your X11 permissions, set DISPLAY and possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on how to set @@ -1034,7 +1046,8 @@ make Important: if you cannot get your X11 permissions so that the xdpyinfo or xclock tests work, x11vnc also will not work (all of these X - clients must be able to connect to the X server to function properly). + clients must be allowed to connect to the X server to function + properly). Q-2: I can't get x11vnc and/or libvncserver to compile. @@ -1074,7 +1087,46 @@ make XFree86-devel zlib-devel - Q-3: Help, I need to run x11vnc on Solaris 2.5.1 (or other old + Q-3: I just built x11vnc successfully, but when I use it my keystrokes + and mouse button clicks are ignored (I am able to move the mouse + though). + + This is most likely due to you not having a working build environment + for the XTEST client library libXtst.so. The library is probably + present on your system, but the package installing the development + header file is missing. + + If you were watching carefully while configure was running you would + have seen: + checking for XTestFakeKeyEvent in -lXtst... no + + The solution is to add the necessary build environment package (and + the library package if that is missing too). On Debian the build + package is libxtst-dev. Other distros/OS's may have it in another + package. + + x11vnc will build without support for this library (e.g. perhaps one + wants a view-only x11vnc on a stripped down or embedded system...). At + runtime it will also continue to run even if the X server it connects + to does not support XTEST. In both cases it cannot inject keystrokes + or button clicks since XTEST is needed for that (it can still move the + mouse pointer using the X API XWarpPointer()). + + You will see a warning message something like this at run time: + 20/03/2005 22:33:09 WARNING: XTEST extension not available (either missing fr +om + 20/03/2005 22:33:09 display or client library libXtst missing at build time +). + 20/03/2005 22:33:09 MOST user input (pointer and keyboard) will be DISCARDE +D. + 20/03/2005 22:33:09 If display does have XTEST, be sure to build x11vnc wit +h + 20/03/2005 22:33:09 a working libXtst build environment (e.g. libxtst-dev, + 20/03/2005 22:33:09 or other packages). + 20/03/2005 22:33:09 No XTEST extension, switching to -xwarppointer mode for + 20/03/2005 22:33:09 pointer motion input. + + Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old Unix/Linux) and it doesn't compile! We apologize that x11vnc does not build cleanly on older versions of @@ -1088,7 +1140,7 @@ make earlier and perhaps non-Solaris): First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the - above [141]Solaris build script to run the configure command. That + above [144]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 @@ -1102,12 +1154,8 @@ int gethostname(char *name, int namelen); long random(); int srandom(unsigned int seed); #undef LIBVNCSERVER_HAVE_LIBPTHREAD -#ifndef SHUT_RDWR #define SHUT_RDWR 2 -#endif -#ifndef in_addr_t typedef unsigned int in_addr_t; -#endif #define snprintf(a, n, args...) sprintf((a), ## args) Then run make with the Solaris build script environment, everything @@ -1118,28 +1166,28 @@ typedef unsigned int in_addr_t; on other older OS (Solaris, Linux, ...) releases. Here are some notes for similar steps that need to be done to build on - [142]SunOS 4.x + [145]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 compilations back to earlier Solaris, Linux, etc, releases. - Q-4: Where can I get a precompiled x11vnc binary for my Operating + Q-5: Where can I get a precompiled x11vnc binary for my Operating System? - Hopefully the [143]build steps above and [144]FAQ provide enough info + Hopefully the [146]build steps above and [147]FAQ provide enough info for a painless compile for most environments. Please report problems with the x11vnc configure, make, etc. on your system (if your system is known to compile other GNU packages successfully). There are precompiled x11vnc binaries built by other groups that are available at the following locations: - Debian: (.deb) [145]http://packages.debian.org/x11vnc + Debian: (.deb) [148]http://packages.debian.org/x11vnc - Slackware: (.tgz) [146]http://www.linuxpackages.net/ Redhat/Fedora: - (.rpm) [147]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) - [148]http://www.sunfreeware.com/ wwexptools: (.tgz) - [149]http://www.bell-labs.com/project/wwexptools/packages.html The + Slackware: (.tgz) [149]http://www.linuxpackages.net/ Redhat/Fedora: + (.rpm) [150]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) + [151]http://www.sunfreeware.com/ wwexptools: (.tgz) + [152]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 @@ -1151,13 +1199,13 @@ 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 [150]build notes above for where to download libz and libjpeg, and + the [153]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 - [151]test binaries. Some may be old, some may have extra debugging + [154]test binaries. Some may be old, some may have extra debugging output, etc. One of them may work on your OS... As a general note, the x11vnc program is simple enough you don't @@ -1172,23 +1220,23 @@ typedef unsigned int in_addr_t; resulting data.tar.gz tar file. Also, rpm2cpio(1) is useful in extracting files from rpm packages. - Q-5: Where can I get a VNC Viewer binary (or source code) for the + Q-6: Where can I get a VNC Viewer binary (or source code) for the Operating System I will be viewing from? To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix) try here: - * [152]http://www.tightvnc.com/download.html - * [153]http://www.realvnc.com/download-free.html - * [154]http://sourceforge.net/projects/cotvnc/ + * [155]http://www.tightvnc.com/download.html + * [156]http://www.realvnc.com/download-free.html + * [157]http://sourceforge.net/projects/cotvnc/ - Q-6: How can I see all of x11vnc's command line options and + Q-7: 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 - [155]here as well. + [158]here as well. - Q-7: I don't like typing arcane command line options every time I + Q-8: 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? You could create a shell script that calls x11vnc with your options: @@ -1218,20 +1266,20 @@ 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 - [156]-gui option for more info. Examples: "x11vnc ... -gui" and + [159]-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 + Q-9: Can I make x11vnc more quiet and also go into the background after starting up? - Use the [157]-q and [158]-bg options, respectively. (also: -quiet is + Use the [160]-q and [161]-bg options, respectively. (also: -quiet is an alias for -q) Note that under -bg the stderr messages will be lost unless you use - the "[159]-o logfile" option. + the "[162]-o logfile" option. - Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with + Q-10: 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. @@ -1241,35 +1289,55 @@ display :0 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 - [160]x11vnc.c file. It also has an [161]option -sigpipe exit to have + [163]x11vnc.c file. It also has an [164]option -sigpipe exit to have x11vnc clean up and exit upon receiving SIGPIPE. + Q-11: Are there any build-time customizations possible, e.g. change + defaults, create a smaller binary, etc? + + As of Mar/2004 in the libvncserver cvs there are a few such options. + They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS + environment variable before running configure (see the [165]build + notes for general background). + * -DX11VNC_SHARED=1 make -shared the default. + * -DX11VNC_FOREVER=1 make -forever the default. + * -DREMOTE_CONTROL=0 disable the remote control mechanism. + * -DSMALL_FOOTPRINT=1 strip out help text, gui, etc to make a + smaller binary (e.g. for PDA or embedded system with low disk + space). Also be sure to strip(1) the binary. Set to 2 or 3 to cut + out even more. + + For example: + env CPPFLAGS="-DX11VNC_FOREVER=1" ./configure; make + + If other things (e.g. "-I ...") are needed in CPPFLAGS add them as + well. Let us know if more customizations would be useful. [Win2VNC Related] - Q-10: I have two separate machine displays in front of me, one Windows + Q-12: I have two separate machine displays in front of me, one Windows the other X11: can I use x11vnc in combination with Win2VNC in dual-screen mode to pass the keystrokes and mouse motions to the X11 display? - Yes, for best response start up x11vnc with the "[162]-nofb" option + Yes, for best response start up x11vnc with the "[166]-nofb" option (disables framebuffer polling, and does other optimizations) on the secondary display (X11) machine. Then start up Win2VNC on the primary display (Windows) referring it to the secondary display. - This will also work X11 to X11 using [163]x2vnc, however you would + This will also work X11 to X11 using [167]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: - * [164]Original Win2VNC - * [165]Enhanced Win2VNC and [166]sourceforge link - * [167]x2vnc - * [168]x2x also [169]here - * [170]zvnc (MorphOS) + * [168]Original Win2VNC + * [169]Enhanced Win2VNC and [170]sourceforge link + * [171]x2vnc + * [172]x2x also [173]here + * [174]zvnc (MorphOS) 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 "x11vnc -nofb" on + Q-13: I am running Win2VNC on my Windows machine and "x11vnc -nofb" on Unix to pass keyboard and mouse to the Unix monitor. Whenever I start Win2VNC it quickly disconnects and x11vnc says: rfbProcessClientNormalMessage: read: Connection reset by peer @@ -1284,7 +1352,7 @@ display :0 on your display to be depth 24 TrueColor? Sun machines often have 8+24 overlay/multi-depth visuals, and you can make the default visual depth 24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004, in the - libvncserver CVS, x11vnc has the [171]-visual option to allow you to + libvncserver CVS, x11vnc has the [175]-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: @@ -1295,11 +1363,11 @@ display :0 no problems in doing this. [Color Issues] - Q-12: The X display I run x11vnc on is only 8 bits per pixel (bpp) + Q-14: The X display I run x11vnc on is only 8 bits per pixel (bpp) PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while they are incorrect in certain windows. - Use the [172]-flashcmap option to have x11vnc watch for changes in the + Use the [176]-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 @@ -1308,20 +1376,20 @@ 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 [173]-notruecolor option has + Also note that in some rare cases the [177]-notruecolor option has corrected colors on 8bpp displays. The red, green, and blue masks were non-zero in 8bpp PseudoColor on an obscure setup, and this option corrected the problems. - Q-13: Color problems: Why are the colors for some windows messed up in + Q-15: Color problems: Why are the colors for some windows messed up in x11vnc? BTW, my X display has nice overlay/multi-depth visuals of different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - You may want to review the [174]previous question regarding 8 bpp + You may want to review the [178]previous question regarding 8 bpp PseudoColor. - On some hardware (Sun/SPARC, Sgi), the [175]-overlay option discussed + On some hardware (Sun/SPARC, Sgi), the [179]-overlay option discussed a couple paragraphs down may solve this for you (you may want to skip to it directly). @@ -1359,7 +1427,7 @@ TrueColor defdepth 24 The -overlay mode: Another option is if the system with overlay visuals is a Sun system running Solaris or Sgi running IRIX you can - use the [176]-overlay x11vnc option (Aug/2004) to have x11vnc use the + use the [180]-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 @@ -1381,7 +1449,7 @@ TrueColor defdepth 24 Colors still not working correctly? 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 [177]-id option to + possible workaround in this case is to use the [181]-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). @@ -1389,28 +1457,28 @@ TrueColor defdepth 24 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 - [178]-overlay option works for Solaris machines with overlay visuals + [182]-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 + Q-16: How do I figure out the window id to supply to the -id windowid option? Run the xwininfo program in a terminal. It will ask you to click on the desired application window. After clicking, it will print out much information, including the window id (e.g. 0x6000010). Also, the visual and depth of the window printed out is often useful in - debugging x11vnc [179]problems. + debugging x11vnc [183]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 "[180]-id pick" to + Also, as of Dec/2004 libvncserver CVS you can use "[184]-id pick" to have x11vnc run xwininfo(1) for you and after you click the window it extracts the windowid. Besides "pick" there is also "id:root" to allow you to go back to root window when doing remote-control. - Q-15: Why don't menus or other transient windows come up when I am + Q-17: Why don't menus or other transient windows come up when I am using the -id windowid option to view a single application window? This is related to the behavior of the XGetImage(3X11) and @@ -1422,12 +1490,12 @@ 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 [181]-sid windowid option ("shifted" windowid). + polling, try the [185]-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 + Q-18: My X display is depth 24 at 24bpp (instead of the normal depth 24 at 32bpp). I'm having lots of color and visual problems with x11vnc and/or vncviewer. What's up? @@ -1466,7 +1534,7 @@ TrueColor defdepth 24 24bpp for the vncviewers to work on that X display. [Xterminals] - Q-17: Can I use x11vnc to view and interact with an Xterminal (e.g. + Q-19: 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? @@ -1474,76 +1542,105 @@ TrueColor defdepth 24 since you will be polling the X display over the network as opposed to over the local hardware. To do this, run x11vnc on a UNIX machine as close as possible network-wise (e.g. same switch) to the Xterminal - machine. Use the [182]-display option to point the display to that of + machine. Use the [186]-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 [183]-noshm option (this enables the polling over + and also supply the [187]-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 - [184]-flipbyteorder if the colors get messed up due to endian byte - order differences. + The response will likely be sluggish (maybe only one "frame" per + second). This mode is not recommended except for "quick checks" of + hard to get to X servers. Use something like -wait 150 to cut down on + the polling rate. You may also need [188]-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 + Q-20: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a Unix/Linux machine acting as an Xterminal? - If the display machine is a traditional Xterminal (where the X server - runs on the Xterminal box, but all of the X client applications run on - a central server), the login display manager, and hence the - MIT-MAGIC-COOKIE auth files, are on the central server and not on the - Xterminal where the X server and x11vnc processes are running. Somehow - 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 - [185]-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 - xauth(1) manpage for more details. - - If the display name needs to be changed between the two hosts, see - [186]this note on the "xauth add ..." command. + If the X display machine is a traditional Xterminal (where the X + server process runs on the Xterminal box, but all of the X client + applications (mozilla, etc) run on a central server (aka "terminal + server")), you will need somehow to be able to log into the Xterminal + machine (i.e. get a shell there) and start the x11vnc program. If the + Xterminal Linux/Unix machine is stripped down (e.g. no users besides + root) that may be difficult. + + The next problem is the login Display Manager (e.g. gdm, kdm), and + hence the MIT-MAGIC-COOKIE auth files, are on the central server and + not on the Xterminal box where the X server and x11vnc processes are. + + To run the x11vnc process on the Xterminal box, somehow the + MIT-MAGIC-COOKIE auth file data (XAUTHORITY or $HOME/.Xauthority) must + be accessible by or copied to the Xterminal. If $HOME/.Xauthority is + exported via NFS (this is insecure of course, but has been going on + for decades), then x11vnc can simply pick it up via NFS (you may need + to use the [189]-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, say, ssh from central-server to xterm123 to start x11vnc. + Here "xterm123" refers to the computer acting as the Xterminal and + "central-server" is the terminal server. You can use "xauth -f + /path/to/cookie-file list" to examine the contents of the cookie(s) in + a file "/path/to/cookie-file". See the xauth(1) manpage for more + details. + + If the display name in the cookie file needs to be changed between the + two hosts, see [190]this note on the "xauth add ..." command. A less secure option is to run something like "xhost +127.0.0.1" while - sitting at the Xterminal to allow cookie-free local access for x11vnc. - You can run "xhost -127.0.0.1" after x11vnc connects if you want. + sitting at the Xterminal box to allow cookie-free local access for + x11vnc. You can run "xhost -127.0.0.1" after x11vnc connects if you + want to go back to the original permissions. 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. It can be done! + to set something up. It can be done!!! Some Xterminal projects have + actually enabled "run locally" facilities for the running of an + occasional app more efficiently locally on the Xterminal box (e.g. + realplayer). - Not recommended, but as a last resort, you could have x11vnc [187]poll - the Xterminal over the network. + Not recommended, but as a last resort, you could have x11vnc [191]poll + the Xterminal Display over the network. For this you would run a + "x11vnc -noshm ..." process on the central-server (and hope the + network admin doesn't get angry...) 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", - 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. + where the "45be51..." cookie value was found from an "xauth -f + /path/to/original/cookie-file list") or other reasons. See xauth(1) + manpage for full details on how to transfer an MIT-MAGIC-COOKIE + between machines and displays. + + VNCviewer performance on Xterminals: This isn't related to x11vnc on + Xterminals, but we mention it here anyway because of the similar + issues. If you are on an Xterminal and want to use vncviewer to + connect to a VNC server somewhere, then performance would be best if + you ran the viewer on the Xterminal box. Otherwise, (i.e. running the + viewer process on the central-server) all of the vncviewer screen + drawing is done more inefficiently over the network. Something to + consider, especially on a busy network. (BTW, this has all of the + above permission, etc, problems: both vncviewer and x11vnc are X + client apps desired to be run on the Xterminal box). [Remote Control] - Q-19: How do I stop x11vnc once it is running in the background? + Q-21: How do I stop x11vnc once it is running in the background? 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 - [188]-remote and [189]-query options. To shut down the running x11vnc + [192]-remote and [193]-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 [190]-forever option has not been supplied, + For older versions: If the [194]-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 [191]-bg option + If you have not put x11vnc in the background via the [195]-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 @@ -1552,13 +1649,13 @@ TrueColor defdepth 24 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 [192]-clear_mods option and [193]-clear_keys + Alt. Alternatively, the [196]-clear_mods option and [197]-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? + Q-22: Can I change settings in x11vnc without having to restart it? Can I remote control it? - Look at the [194]-remote (same as -R) and [195]-query (same as -Q) + Look at the [198]-remote (same as -R) and [199]-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 @@ -1570,11 +1667,11 @@ TrueColor defdepth 24 be possible. There is also a simple tcl/tk gui based on this remote control - mechanism. See the [196]-gui option for more info. + mechanism. See the [200]-gui option for more info. [Security and Permissions] - Q-21: How do I create a VNC password for use with x11vnc? + Q-23: 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 @@ -1582,12 +1679,12 @@ TrueColor defdepth 24 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" [197]option, which is the the same + the -storepasswd "pass" "file" [201]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: [198]-rfbauth + You then use the password via the x11vnc option: [202]-rfbauth $HOME/myvncpasswd Compared to vncpasswd(1) the latter two methods are a somewhat unsafe @@ -1596,21 +1693,21 @@ TrueColor defdepth 24 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 [199]-passwdfile and -passwd/-viewpasswd plain + x11vnc also has the [203]-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 + Q-24: 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 - [200]-viewpasswd option to supply the view-only password. Note the - full-access password option [201]-passwd must be supplied at the same + [204]-viewpasswd option to supply the view-only password. Note the + full-access password option [205]-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 - [202]-passwdfile option to specify a file containing plain text + [206]-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 @@ -1618,7 +1715,7 @@ TrueColor defdepth 24 it is taken as the view-only password. (use "__EMPTY__" to supply an empty one). - View-only passwords currently do not work for the [203]-rfbauth + View-only passwords currently do not work for the [207]-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 @@ -1627,11 +1724,11 @@ TrueColor defdepth 24 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 + Q-25: 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 [204]-input option allows you to do this. "K", + As of Feb/2005, the [208]-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 @@ -1640,28 +1737,28 @@ TrueColor defdepth 24 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 + Q-26: 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 [205]-forever option (aka -many) to have + periods of time. Use the [209]-forever option (aka -many) to have x11vnc wait for more connections after the first client disconnects. - Use the [206]-shared option to have x11vnc allow multiple clients to + Use the [210]-shared option to have x11vnc allow multiple clients to connect simultaneously. - Recommended additional safety measures include using ssh ([207]see + Recommended additional safety measures include using ssh ([211]see above), stunnel, or a VPN to authenticate and encrypt the viewer - connections or to at least use the -rfbauth passwd-file [208]option to - use VNC password protection (or [209]-passwdfile) It is up to you to + connections or to at least use the -rfbauth passwd-file [212]option to + use VNC password protection (or [213]-passwdfile) It is up to you to apply these security measures, they will not be done for you automatically. - Q-25: Can I limit which machines incoming VNC clients can connect + Q-27: Can I limit which machines incoming VNC clients can connect from? - Yes, look at the [210]-allow and [211]-localhost options to limit + Yes, look at the [214]-allow and [215]-localhost options to limit connections by hostname or IP address. E.g. x11vnc -allow 192.168.0.1,192.168.0.2 @@ -1673,10 +1770,10 @@ TrueColor defdepth 24 Note that -localhost is the same as "-allow 127.0.0.1" For more control, build libvncserver with libwrap support - [212](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) + [216](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) for complete details. - Q-26: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) + Q-28: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) support? Here is one way to pass this information to the configure script: @@ -1692,57 +1789,57 @@ TrueColor defdepth 24 is "vnc", e.g.: vnc: 192.168.100.3 .example.com - Note that if you run x11vnc out of [213]inetd you do not need to build + Note that if you run x11vnc out of [217]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-27: Can I have x11vnc only listen on one network interface (e.g. + Q-29: Can I have x11vnc only listen on one network interface (e.g. internal LAN) rather than having it listen on all network interfaces and relying on -allow to filter unwanted connections out? - As of Mar/2005 in the libvncserver CVS, there is the "[214]-listen + As of Mar/2005 in the libvncserver CVS, there is the "[218]-listen ipaddr" option that enables this. For ipaddr either supply the desired network interface's IP address (or use a hostname that resolves to it) or use the string "localhost". For additional filtering simultaneously - use the "[215]-allow host1,..." option to allow only specific hosts + use the "[219]-allow host1,..." option to allow only specific hosts in. This option is useful if you want insure that no one can even begin a dialog with x11vnc from untrusted network interfaces (e.g. ppp0). The - option [216]-localhost now implies "-listen localhost" since that is + option [220]-localhost now implies "-listen localhost" since that is what most people expect it to do. - Q-28: Now that -localhost implies listening only on the loopback + Q-30: Now that -localhost implies listening only on the loopback interface, how I can occasionally allow in a non-localhost via the allowonce remote control command? - To do this specify "[217]-allow localhost". Unlike [218]-localhost + To do this specify "[221]-allow localhost". Unlike [222]-localhost this will leave x11vnc listening on all interfaces (but of course only allowing in local connections, e.g. ssh redirs). Then you can later run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot connection from a remote host. Note that if you do a lot of changing of the listening interface - ([219]-listen option) via remote control or gui, you may need to also - manually adjust the [220]-allow list if you unexpectedly get into a + ([223]-listen option) via remote control or gui, you may need to also + manually adjust the [224]-allow list if you unexpectedly get into a state where the allow list cannot match any hosts that would be coming - in on the listening interface. If you just toggle [221]-localhost on + in on the listening interface. If you just toggle [225]-localhost on and off x11vnc should see to it that you never get into such a state. - Q-29: How can I tunnel my connection to x11vnc via an encrypted SSH + Q-31: 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 [222]how to tunnel VNC via + See the description earlier on this page on [226]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-30: How can I tunnel my connection to x11vnc via an encrypted SSH + Q-32: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [223]Above we described how to tunnel VNC via SSH from Unix to Unix, + [227]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 @@ -1765,8 +1862,8 @@ TrueColor defdepth 24 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 [224]-localhost - and [225]-rfbauth/[226]-passwdfile options. + For extra protection feel free to run x11vnc with the [228]-localhost + and [229]-rfbauth/[230]-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 @@ -1775,19 +1872,19 @@ TrueColor defdepth 24 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 [227]above another option is to first start the VNC + As discussed [231]above another option is to first start the VNC viewer in "listen" mode, and then launch x11vnc with the - "[228]-connect localhost" option to establish the reverse connection. + "[232]-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-31: Can I prompt the user at the local X display whether the + Q-33: 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 "[229]-accept command" option, it allows you to + Yes, look at the "[233]-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 @@ -1806,7 +1903,7 @@ TrueColor defdepth 24 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 [230]-viewonly option has been + mouse on the "View" button. If the [234]-viewonly option has been supplied, the "View" action will not be present: the whole display is view only in that case. @@ -1822,7 +1919,7 @@ TrueColor defdepth 24 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 [231]ftp://ftp.x.org/ + is available at [235]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 @@ -1861,7 +1958,7 @@ elif [ $rc = 4 ]; then fi exit 1 - Stefan Radman has written a nice dtksh script [232]dtVncPopup for use + Stefan Radman has written a nice dtksh script [236]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. @@ -1870,13 +1967,13 @@ exit 1 popup is being run, so attached clients will not receive screen updates, etc during this period. - To run a command when a client disconnects, use the "[233]-gone + To run a command when a client disconnects, use the "[237]-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-32: Does x11vnc support Unix usernames and passwords? Can I further + Q-34: 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 @@ -1884,13 +1981,13 @@ exit 1 such support. One approximate method involves starting x11vnc with the - [234]-localhost option. This basically requires the viewer user to log + [238]-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 [235]elsewhere on this page. Of course a malicious user + mentioned [239]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 @@ -1899,7 +1996,7 @@ exit 1 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 [236]-accept option that runs a program to examine + involves using the [240]-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 @@ -1927,18 +2024,18 @@ exit 1 # reject it For this to work with ssh port redirection, the ssh option UsePrivilegeSeparation must be enabled. - Q-33: I start x11vnc as root because it is launched via inetd(1) or a + Q-35: 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? - As of Feb/2005 x11vnc has the [237]-users option that allows things + As of Feb/2005 x11vnc has the [241]-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-34: I use a screen-lock when I leave my workstation (e.g. + Q-36: 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 @@ -1951,7 +2048,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 [238]blockdpy.c The idea behind it is simple (but + source for it is [242]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 @@ -1967,15 +2064,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 [239]-accept option and told - to exit via the [240]-gone option (the vnc client user should + The blockdpy utility is launched by the [243]-accept option and told + to exit via the [244]-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-35: Can I have x11vnc automatically lock the screen when I + Q-37: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? - Yes, a user mentions he uses the [241]-gone option under CDE to run a + Yes, a user mentions he uses the [245]-gone option under CDE to run a screen lock program: x11vnc -display :0 -forever -gone 'dtaction LockDisplay' @@ -1987,7 +2084,7 @@ exit 1 # reject it [Display Managers and Services] - Q-36: How can I run x11vnc as a "service" that is always available? + Q-38: 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 @@ -1998,11 +2095,11 @@ exit 1 # reject it permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [242]FAQ on x11vnc + * Use the description under "Continuously" in the [246]FAQ on x11vnc and Display Managers - * Use the description in the [243]FAQ on x11vnc and inetd(1) + * Use the description in the [247]FAQ on x11vnc and inetd(1) * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc) - * Although less reliable, see the [244]x11vnc_loop rc.local hack + * Although less reliable, see the [248]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the @@ -2020,7 +2117,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg plus any other options you desire. - Q-37: How can I use x11vnc to connect to an X login screen like xdm, + Q-39: 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). @@ -2032,7 +2129,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg while running x11vnc as root, e.g. for the gnome display manager, gdm: x11vnc -auth /var/gdm/:0.Xauth -display :0 - (the [245]-auth option sets the XAUTHORITY variable for you). + (the [249]-auth option sets the XAUTHORITY variable for you). There will be a similar thing for xdm using however a different auth directory path (perhaps something like @@ -2057,7 +2154,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see - [246]the example at the end of this FAQ). Then restart dtlogin, e.g.: + [250]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 @@ -2111,7 +2208,7 @@ rever -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 [247]full details + killed immediately after the user logs in. Here are [251]full details on how to configure gdm _________________________________________________________________ @@ -2153,22 +2250,22 @@ rever -bg If you do not want to deal with any display manager startup scripts, here is a kludgey script that can be run manually or out of a boot - file like rc.local: [248]x11vnc_loop It will need some local + file like rc.local: [252]x11vnc_loop It will need some local customization before running. Because the XAUTHORITY auth file must be guessed by this script, use of the display manager script method described above is greatly preferred. If the machine is a traditional Xterminal you may want to read - [249]this FAQ. + [253]this FAQ. - Q-38: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + Q-40: 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 uses the [250]-inetd + where the shell script /usr/local/bin/x11vnc_sh uses the [254]-inetd option and looks something like (you'll need to customize to your settings). #!/bin/sh @@ -2180,13 +2277,13 @@ rever -bg (otherwise the standard error 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 to a file, then you must specify the -q (aka [251]-quiet) + stderr to a file, then you must specify the -q (aka [255]-quiet) option: "/usr/local/bin/x11vnc -q -inetd ..." or use "-o logfile" to collect the output in a file. The wrapper script with 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 [252]-auth to point to the + Note also the need to set XAUTHORITY via [256]-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 @@ -2229,11 +2326,11 @@ service x11vncservice With the contents of /usr/local/bin/x11vnc_sh similar to the example given above. - Q-39: How do I make x11vnc work with the Java VNC viewer applet in a + Q-41: 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 [253]option: + that connect to it, run x11vnc with this [257]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -2256,13 +2353,13 @@ 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-40: Are reverse connections (i.e. the VNC server connecting to the + Q-42: 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 (see your documentation for Windows, etc), and then - starts up x11vnc with the [254]-connect option. To connect immediately + starts up x11vnc with the [258]-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 @@ -2270,7 +2367,7 @@ service x11vncservice hosts to connect to. To use the vncconnect(1) program (from the core VNC package at - www.realvnc.com) specify the [255]-vncconnect option to x11vnc (Note: + www.realvnc.com) specify the [259]-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 @@ -2283,7 +2380,7 @@ service x11vncservice # xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" - Q-41: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real + Q-43: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real display, but for a virtual one I keep around). You can, but you would not be doing this for performance reasons (for @@ -2311,7 +2408,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" There are some annoyances WRT Xvfb though. The default keyboard mapping seems to be very poor. One should run x11vnc with - [256]-add_keysyms option to have keysyms added automatically. Also, to + [260]-add_keysyms option to have keysyms added automatically. Also, to add the Shift_R and Control_R modifiers something like this is needed: #!/bin/sh xmodmap -e "keycode any = Shift_R" @@ -2325,21 +2422,44 @@ xmodmap -e "add Control = Control_L Control_R" One can use this sort of scheme to export other virtual X sessions, say Xnest or even Xvnc itself (useful for testing x11vnc). - - Another application of x11vnc in this vein is to let it export - displays of "headless" machines. For example, you may have some server - machines with no keyboard, mouse, or monitor, but it still has a video - card. An X server can be started on the headless machine (sometimes - this requires configuring the X server to not fail if it cannot detect - a keyboard or mouse). Then you can export that X display via x11vnc - (e.g. see [257]this FAQ). This can be quite useful for a GUI (or - other) testing setups: the engineers do not need to walk to machines - running different hardware, OS's, etc. They just connect to the test - machines over the network via VNC. + Q-44: How can I use x11vnc on "headless" machines? Why might I want + to? + + An interesting application of x11vnc is to let it export displays of + "headless" machines. For example, you may have some lab or server + machines with no keyboard, mouse, or monitor, but each one still has a + video card. One can use x11vnc to provide a simple "desktop service" + from these server machines. + + An X server can be started on the headless machine (sometimes this + requires configuring the X server to not fail if it cannot detect a + keyboard or mouse, see the next paragraph). Then you can export that X + display via x11vnc (e.g. see [261]this FAQ) and access it from + anywhere on the network via a VNC viewer. + + Some tips on getting X servers to start on machines without keyboard + or mouse: For XFree86/Xorg the Option "AllowMouseOpenFail" "true" + "ServerFlags" config file option is useful. On Solaris Xsun the + +nkeyboard and +nmouse options are useful (put them in the server + command line args in /etc/dt/config/Xservers). See Xserver(1) for more + info. + + Although this usage may sound strange it can be quite useful for a GUI + (or other) testing or QA setups: the engineers do not need to walk to + lab machines running different hardware, OS's, versions, etc (or have + many different machines in their office). They just connect to the + various test machines over the network via VNC. The advantage to + testing this way instead of using Xvnc or even Xvfb is that the test + is done using the real X server, fonts, video hardware, etc. that will + be used in the field. + + One can imagine a single server machine crammed with as many video + cards as it can hold to provide multiple simultaneous access or + testing on different kinds of video hardware. [Resource Usage and Performance] - Q-42: I have lots of memory, but why does x11vnc fail with shmget: + Q-45: 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)? @@ -2357,7 +2477,7 @@ xmodmap -e "add Control = Control_L Control_R" 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 [258]shm_clear to list and prompt for removal + Here is a shell script [262]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, @@ -2391,36 +2511,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 - [259]-onetile option (corresponds to only 3 shm segments used, and + [263]-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 - [260]-noshm option. Performance will be somewhat degraded but when + [264]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [261]earlier question discussing -noshm). + [265]earlier question discussing -noshm). - Q-43: How can I make x11vnc use less system resources? + Q-46: How can I make x11vnc use less system resources? - The [262]-nap and "[263]-wait n" (where n is the sleep between polls + The [266]-nap and "[267]-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 - [264]-onetile option will use less memory and use fewer shared memory - slots (add [265]-fs 1.0 for one less slot). + [268]-onetile option will use less memory and use fewer shared memory + slots (add [269]-fs 1.0 for one less slot). - Q-44: How can I make x11vnc use MORE system resources? + Q-47: How can I make x11vnc use MORE system resources? - You can try [266]-threads and dial down the wait time (e.g. -wait 1) - and possibly dial down [267]-defer as well. Note that if you try to + You can try [270]-threads and dial down the wait time (e.g. -wait 1) + and possibly dial down [271]-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 [268]-id option) can be streamed over a LAN or wireless at + the x11vnc [272]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. - Q-45: I use x11vnc over a slow link with high latency (e.g. dialup + Q-48: 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 @@ -2432,7 +2552,7 @@ ied) * Use a smaller desktop size (e.g. 1024x768 instead of 1280x1024) * Make sure the desktop background is a solid color (the background is resent every time it is re-exposed). Consider using the - [269]-solid [color] option. + [273]-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. @@ -2448,7 +2568,7 @@ ied) worth it, but could be of use in some situations. VNC viewer parameters: - * Use a [270]TightVNC enabled viewer! + * Use a [274]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 @@ -2466,22 +2586,22 @@ ied) vncviewer to be very slow) x11vnc parameters: - * Try using [271]-nodragging (no screen updates when dragging mouse, + * Try using [275]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Try the [272]-progressive pixelheight mode with the block + * Try the [276]-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 [273]-fs 1.0 (disables fullscreen updates) - * Try increasing [274]-wait or [275]-defer (reduces the maximum + * Set [277]-fs 1.0 (disables fullscreen updates) + * Try increasing [278]-wait or [279]-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 [276]-id (cuts + * If you just want to watch one (simple) window use [280]-id (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [277]-nosel (disables all clipboard selection exchange) - * Use [278]-nocursor and [279]-nocursorpos (repainting the remote + * Set [281]-nosel (disables all clipboard selection exchange) + * Use [282]-nocursor and [283]-nocursorpos (repainting the remote cursor position and shape takes resources and round trips) - Q-46: When I drag windows around with the mouse or scroll up and down + Q-49: 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? @@ -2489,25 +2609,25 @@ 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 "[280]-pointer_mode 1" option. + way via the "[284]-pointer_mode 1" option. - Also added was the [281]-nodragging option that disables all screen + Also added was the [285]-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 [282]-pointer_mode n option + As of Dec/2004 in the libvncserver CVS the [286]-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. - Also, in some circumstances the [283]-threads option can improve + Also, in some circumstances the [287]-threads option can improve response considerably. Be forewarned that if more than one vncviewer is connected at the same time then libvncserver may not be thread safe (try to get the viewers to use different VNC encodings, e.g. tight and ZRLE). - Q-47: Does x11vnc support the X DAMAGE Xserver extension to find + Q-50: Does x11vnc support the X DAMAGE Xserver extension to find modified regions of the screen quickly and efficiently? Yes, as of Mar/2005 in the libvncserver CVS x11vnc will use the X @@ -2541,17 +2661,17 @@ ied) DAMAGE rectangles to contain real damage. The larger rectangles are only used as hints to direct the traditional scanline polling (i.e. if a scanline doesn't intersect a recent DAMAGE rectangle, the scan is - skipped). You can use the "[284]-xd_area A" option to adjust the size + skipped). You can use the "[288]-xd_area A" option to adjust the size of the trusted DAMAGE rectangles. The default is 20000 pixels (e.g. a 140x140 square, etc). Use "-xd_area 0" to disable the cutoff and trust all DAMAGE rectangles. - The option "[285]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[286]-noxdamage". + The option "[289]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[290]-noxdamage". [Mouse Cursor Shapes] - Q-48: Why isn't the mouse cursor shape (the little icon shape where + Q-51: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it @@ -2565,16 +2685,16 @@ ied) 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 "[287]-cursor X" option that + A simple kludge is provided by the "[291]-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 "[288]-cursor some" option for + work for those cases. Also see the "[292]-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 [289]-overlay option is supplied. See [290]this FAQ + cursor when the [293]-overlay option is supplied. See [294]this FAQ for more info. Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support @@ -2582,7 +2702,7 @@ ied) 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 [291]Solaris 10. + distros and [295]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 @@ -2590,9 +2710,9 @@ ied) 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. [292]Details can be found here. + under 32bpp. [296]Details can be found here. - Q-49: When using XFIXES cursorshape mode, some of the cursors look + Q-52: 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? @@ -2622,24 +2742,24 @@ ied) 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 "[293]-alphacut n" option lets + course!) some tunable parameters. The "[297]-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 "[294]-alphafrac f" option tries to correct individual + 240. The "[298]-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 [295]-alpharemove that is useful for + Finally, there is an option [299]-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-50: In XFIXES mode, are there any hacks to handle cursor + Q-53: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? As of Jan/2005 in the CVS, libvncserver has been modified to allow an @@ -2647,11 +2767,11 @@ ied) 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 [296]-nocursorshape x11vnc option. + disabled for all clients with the [300]-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 - [297]-noalphablend option to disable this behavior (always approximate + [301]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). The CursorShapeUpdates VNC extension complicates matters because the @@ -2676,12 +2796,12 @@ ied) [Mouse Pointer] - Q-51: Why does the mouse arrow just stay in one corner in my + Q-54: 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 [298]tightvnc extension + This default takes advantage of a [302]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [299]-nocursor + the local VNC viewer. You may disable it with the [303]-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 @@ -2689,22 +2809,22 @@ ied) CursorShapeUpdates) will be to draw the moving cursor into the x11vnc framebuffer. This can also be disabled via -nocursor. - Q-52: Can I take advantage of the TightVNC extension to the VNC + Q-55: 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 [300]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [304]-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 [301]-nocursorpos - and [302]-nocursorshape. + libvncserver CVS -cursorpos is the default. See also [305]-nocursorpos + and [306]-nocursorshape. - Q-53: Is it possible to swap the mouse buttons (e.g. left-handed + Q-56: 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: [303]-buttonmap + You can remap the mouse buttons via something like: [307]-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. @@ -2712,7 +2832,7 @@ ied) 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 [304]-debug_pointer option prints out much info for + Note that the [308]-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 @@ -2734,7 +2854,7 @@ 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 [305]-buttonmap but rather configuring the X server + consider not using [309]-buttonmap but rather configuring the X server to think it has a mouse with 5 buttons even though the physical mouse does not. @@ -2752,10 +2872,10 @@ ied) (yes, this is getting a little silly). [Keyboard Issues] - Q-54: How can I get my AltGr and Shift modifiers to work between + Q-57: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [306]-modtweak should be of some use for this. It is a mode + The option [310]-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. @@ -2764,20 +2884,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 [307]this FAQ + and ">" it. This key does not exist on the keyboard (see [311]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 [308]FAQ about the -xkb option for a more powerful method + Also see the [312]FAQ about the -xkb option for a more powerful method of modifier tweaking for use on X servers with the XKEYBOARD extension. When trying to resolve keyboard mapping problems, note that the - [309]-debug_keyboard option prints out much info for every keystroke + [313]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. - Q-55: When I try to type a "<" (i.e. less than) instead I get ">" + Q-58: 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 @@ -2824,20 +2944,20 @@ ied) -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([310]-modtweak) is a mode that monitors the + settings. The former ([314]-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 ([311]-remap less-comma) is an immediate remapping of the + The latter ([315]-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 [312]FAQ about the -xkb option as a possible workaround + See also the [316]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [313]-debug_keyboard option prints out much info for + Note that the [317]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. - Q-56: I'm using an "international" keyboard (e.g. German "de", or + Q-59: 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 @@ -2858,7 +2978,7 @@ 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 [314]-modtweak + This all worked fine with x11vnc running with the [318]-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 @@ -2876,7 +2996,7 @@ ied) * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [315]-xkb option seems to fix all of the missing keys: "@", "<", + The [319]-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 @@ -2894,7 +3014,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: - [316]-skip_keycodes 93 + [320]-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 @@ -2911,14 +3031,14 @@ 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 [317]-remap x11vnc option: + created using the [321]-remap x11vnc option: -remap asciitilde-dead_tilde,asciicircum-dead_circumflex etc. Use -remap filename if the list is long. Please send us your workarounds for this problem on your keyboard. Perhaps we can have x11vnc adjust automatically at some point. Also see the - [318]-add_keysyms option in the next paragraph. - * To complement the above workaround using the [319]-remap, an - option [320]-add_keysyms was added. This option instructs x11vnc + [322]-add_keysyms option in the next paragraph. + * To complement the above workaround using the [323]-remap, an + option [324]-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 @@ -2926,7 +3046,7 @@ ied) when the Keysym is received from a VNC viewer, and only after that would -add_keysyms, or anything else, come into play. - Q-57: When typing I sometimes get double, triple, or more of my + Q-60: 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 @@ -2934,7 +3054,7 @@ 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) [321]-norepeat x11vnc option. You will still + use the new (Jul/2004) [325]-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. @@ -2956,17 +3076,17 @@ ied) 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 [322]-norepeat (which has since Dec/2004 been + needed, or to use the [326]-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-58: The x11vnc -norepeat mode is in effect, but I still get repeated + Q-61: 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 in - [323]this FAQ) If so, x11vnc is starting before your session and it + [327]this FAQ) If so, x11vnc is starting before your session and it disables autorepeat when you connect, but then after you log in your session startup (GNOME, KDE, ...) could be resetting the autorepeat to be on. Or it could be something inside your desktop trying to be @@ -2985,11 +3105,11 @@ ied) something in your desktop is automatically turning it back on you should figure out how to disable that somehow. - Q-59: The machine where I run x11vnc has an AltGr key, but the local + Q-62: 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 "[324]-remap Super_R-Mode_switch" x11vnc option may + Something like "[328]-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)). @@ -2999,7 +3119,7 @@ ied) Super_R-Mode_switch,Menu-Multi_key" or use "-remap filename" to specify remappings from a file. - Q-60: I have a Sun machine I run x11vnc on. Its Sun keyboard has just + Q-63: 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) @@ -3011,17 +3131,17 @@ 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 [325]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [329]-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-61: Can I map a keystroke to a mouse button click on the remote + Q-64: 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 [326]-remap + have x11vnc do the remapping. This can be done via the [330]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -3029,7 +3149,7 @@ ied) 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: - [327]-remap Super_R-Button2 + [331]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -3040,7 +3160,7 @@ ied) [Screen Related Issues and Features] - Q-62: The remote display is larger (in number of pixels) than the + Q-65: 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? @@ -3058,15 +3178,15 @@ 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 [328]this + local display. Especially for hand-held devices. See also [332]this FAQ on x11vnc scaling. - Q-63: Does x11vnc support server-side framebuffer scaling? (E.g. to + Q-66: 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 "[329]-scale fraction" + per-client setting. To enable it use the "[333]-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 magnified. @@ -3086,7 +3206,7 @@ ied) One can also use the ":nb" with an integer scale factor (say "-scale 2:nb") to use x11vnc as a screen magnifier for vision impaired - [330]applications. Since with integer scale factors the framebuffers + [334]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -3112,16 +3232,16 @@ 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 ([331]-rfbport option, + different scalings listening on separate ports ([335]-rfbport option, etc.). As of Mar/2005 in the libvncserver CVS x11vnc now scales the mouse cursor with the same scale factor as the screen. If you don't want - that, use the [332]"-scale_cursor frac" option to set the cursor + that, use the [336]"-scale_cursor frac" option to set the cursor scaling to a different factor (e.g. use "-scale_cursor 1" to keep the cursor at its natural unscaled size). - Q-64: Does x11vnc work with Xinerama? (i.e. multiple monitors joined + Q-67: 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 @@ -3133,22 +3253,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 [333]-blackout x11vnc option allows you + distracting to the viewer. The [337]-blackout x11vnc option allows you to blacken-out rectangles by specifying their WxH+X+Y geometries. If - your system has the libXinerama library, the [334]-xinerama x11vnc + your system has the libXinerama library, the [338]-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 [335]-xwarppointer + of the large display. If this happens try using the [339]-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-65: Can I use x11vnc on a multi-headed display that is not Xinerama + Q-68: 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 @@ -3166,29 +3286,29 @@ 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 [336]FAQ to increase the limit. It - is probably also a good idea to run with the [337]-onetile option in + /etc/system as mentioned in another [340]FAQ to increase the limit. It + is probably also a good idea to run with the [341]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [338]-noshm to use no shm segments. + [342]-noshm to use no shm segments. - Q-66: Can x11vnc show only a portion of the display? (E.g. for a + Q-69: Can x11vnc show only a portion of the display? (E.g. for a special purpose rfb application). - As of Mar/2005 in the libvncserver CVS x11vnc has the "[339]-clip + As of Mar/2005 in the libvncserver CVS x11vnc has the "[343]-clip WxH+X+Y" option to select a rectangle of width W, height H and offset (X, Y). Thus the VNC screen will be the clipped sub-region of the display and be only WxH in size. This also works to view a sub-region of a single application window if - the [340]-id or [341]-sid options are used. The offset is measured + the [344]-id or [345]-sid options are used. The offset is measured from the upper left corner of the selected window. - Q-67: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) + Q-70: 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 [342]-xrandr option to make x11vnc monitor XRANDR + enable it with the [346]-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 @@ -3197,7 +3317,7 @@ ied) 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 - [343]-padgeom option to make the region big enough to hold all resizes + [347]-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 @@ -3205,12 +3325,12 @@ ied) specify "-xrandr exit" then all will be disconnected and x11vnc will terminate. - Q-68: Why is the view in my VNC viewer completely black? Or why is + Q-71: 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-69: I use Linux Virtual Consoles (VC's) to implement 'Fast User + Q-72: 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 @@ -3237,7 +3357,7 @@ ied) x11vnc can poll it correctly), one can use the chvt(1) command, e.g. "chvt 7" for VC #7. - Q-70: Can I use x11vnc to view my VMWare session remotely? + Q-73: Can I use x11vnc to view my VMWare session remotely? Yes, since VMWare is an X application you can view it via x11vnc in the normal way. @@ -3248,7 +3368,7 @@ ied) * Fullscreen mode The way VMWare does Fullscreen mode on Linux is to display the Guest - desktop in a separate Virtual Console (e.g. VC 8) (see [344]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [348]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X server. So x11vnc cannot access it. x11vnc works fine with "Normal X application window" and "Quick-Switch mode" because these use X. @@ -3266,13 +3386,13 @@ ied) response. One can also cut the display depth (e.g. to 16bpp) in this 2nd X session to improve video performance. This 2nd X session emulates Fullscreen mode to some degree and can be viewed via x11vnc - as long as the VMWare X session [345]is in the active VC. + as long as the VMWare X session [349]is in the active VC. Also note that with a little bit of playing with "xwininfo -all -children" output one can extract the (non-toplevel) windowid of the of the Guest desktop only when VMWare is running as a normal X application. Then one can export just the guest desktop (i.e. without - the VMWare menu buttons) by use of the [346]-id windowid option. The + the VMWare menu buttons) by use of the [350]-id windowid option. The caveats are the X session VMWare is in must be in the active VC and the window must be fully visible, so this mode is not terribly convenient, but could be useful in some circumstances (e.g. running @@ -3280,7 +3400,7 @@ ied) to have a video card, (but need not have a monitor, Keyboard or mouse)). - Q-71: I am using x11vnc where my local machine has "popup/hidden + Q-74: 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 @@ -3294,21 +3414,21 @@ ied) [Misc: Clipboard, Beeps, Thanks, etc.] - Q-72: Does the Clipboard/Selection get transferred between the + Q-75: 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 [347]-nosel option. If you + the Clipboard/Selection exchanged use the [351]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [348]-noprimary option. + [352]-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-73: Why don't I hear the "Beeps" in my X session (e.g. when typing + Q-76: 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 @@ -3316,18 +3436,21 @@ ied) 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 [349]-nobell option. If + If you don't want to hear the beeps use the [353]-nobell option. If you want to hear the audio from the remote applications, consider trying a redirector such as esd. - Q-74: Thanks for your program and for your help! Can I make a + + Contributions: + + Q-77: 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 for more info. 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 - [350]email! + [354]email! [PayPal] @@ -3336,353 +3459,357 @@ References 1. http://www.karlrunge.com/x11vnc/index.html#faq 2. http://www.karlrunge.com/x11vnc/index.html#downloading 3. http://www.karlrunge.com/x11vnc/index.html#building - 4. http://www.karlrunge.com/x11vnc/index.html#faq - 5. http://www.karlrunge.com/x11vnc/index.html#contact - 6. http://www.uk.research.att.com/vnc/ - 7. http://www.realvnc.com/ - 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/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 + 4. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 5. http://www.karlrunge.com/x11vnc/index.html#faq + 6. http://www.karlrunge.com/x11vnc/index.html#contact + 7. http://www.uk.research.att.com/vnc/ + 8. http://www.realvnc.com/ + 9. http://www.tightvnc.com/ + 10. http://www.karlrunge.com/x11vnc/index.html#downloading + 11. http://www.tightvnc.com/download.html + 12. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 13. http://www.karlrunge.com/x11vnc/index.html#faq-xperms + 14. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download + 15. http://www.sun.com/software/solaris/freeware/ 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=307884 - 34. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=307884 - 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-thanks - 63. http://www.karlrunge.com/x11vnc/index.html#faq-xperms - 64. http://www.karlrunge.com/x11vnc/index.html#faq-build - 65. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build - 66. http://www.karlrunge.com/x11vnc/index.html#faq-binaries - 67. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download - 68. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts - 69. http://www.karlrunge.com/x11vnc/index.html#faq-config-file - 70. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg - 71. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe - 72. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc - 73. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp - 74. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 75. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 76. http://www.karlrunge.com/x11vnc/index.html#faq-windowid - 77. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id - 78. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp - 79. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 80. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 81. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg - 82. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control - 83. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 84. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 85. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt - 86. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared - 87. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt - 88. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 89. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface - 90. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost - 91. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix - 92. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty - 93. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt - 94. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords - 95. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt - 96. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy - 97. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock - 98. http://www.karlrunge.com/x11vnc/index.html#faq-service - 99. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 100. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 101. http://www.karlrunge.com/x11vnc/index.html#faq-java-http - 102. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect - 103. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 104. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 105. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource - 106. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource - 107. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link - 108. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode - 109. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage - 110. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape - 111. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha - 112. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 113. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow - 114. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions - 115. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt - 116. http://www.karlrunge.com/x11vnc/index.html#faq-altgr - 117. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 118. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 119. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys - 120. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still - 121. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt - 122. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta - 123. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click - 124. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars - 125. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 126. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama - 127. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen - 128. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen - 129. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr - 130. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen - 131. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 132. http://www.karlrunge.com/x11vnc/index.html#faq-vmware - 133. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars - 134. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard - 135. http://www.karlrunge.com/x11vnc/index.html#faq-beeps - 136. http://www.karlrunge.com/x11vnc/index.html#faq-thanks - 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 138. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 139. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 140. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 141. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 142. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html - 143. http://www.karlrunge.com/x11vnc/index.html#building - 144. http://www.karlrunge.com/x11vnc/index.html#faq-build - 145. http://packages.debian.org/x11vnc - 146. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc - 147. http://dag.wieers.com/packages/x11vnc/ - 148. http://www.sunfreeware.com/ - 149. http://www.bell-labs.com/project/wwexptools/packages.html - 150. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 151. http://www.karlrunge.com/x11vnc/bins - 152. http://www.tightvnc.com/download.html - 153. http://www.realvnc.com/download-free.html - 154. http://sourceforge.net/projects/cotvnc/ - 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 156. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 157. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 159. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o - 160. http://www.karlrunge.com/x11vnc/x11vnc.c - 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe - 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb - 163. http://fredrik.hubbe.net/x2vnc.html - 164. http://www.hubbe.net/~hubbe/win2vnc.html - 165. http://www.deboer.gmxhome.de/ - 166. http://sourceforge.net/projects/win2vnc/ + 17. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 18. http://www.karlrunge.com/x11vnc/index.html#faq-service + 19. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 20. http://www.karlrunge.com/x11vnc/index.html#vnc_password_file + 21. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 22. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 23. http://www.karlrunge.com/x11vnc/index.html#tightvnc_via + 24. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 25. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 26. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 28. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 29. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 31. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt + 32. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 33. http://sourceforge.net/projects/libvncserver/ + 34. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=307884 + 35. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=307884 + 36. http://www.karlrunge.com/x11vnc/x11vnc.c + 37. http://www.karlrunge.com/x11vnc/tkx11vnc.h + 38. http://www.karlrunge.com/x11vnc/index.html#faq-binaries + 39. http://www.tightvnc.com/download.html + 40. http://www.realvnc.com/download-free.html + 41. http://sourceforge.net/projects/cotvnc/ + 42. http://www.karlrunge.com/x11vnc/rx11vnc + 43. http://www.karlrunge.com/x11vnc/rx11vnc.pl + 44. http://www.sunfreeware.com/ + 45. ftp://ftp.uu.net/graphics/jpeg/ + 46. http://www.gzip.org/zlib/ + 47. http://www.sunfreeware.com/ + 48. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build + 49. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 50. http://www.tightvnc.com/ + 51. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 52. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 53. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 54. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg + 55. http://wwws.sun.com/sunray/index.html + 56. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 57. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 58. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 59. http://www.karlrunge.com/x11vnc/shm_clear + 60. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 61. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 62. mailto:xvml@karlrunge.com + 63. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 64. http://www.karlrunge.com/x11vnc/index.html#faq-xperms + 65. http://www.karlrunge.com/x11vnc/index.html#faq-build + 66. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest + 67. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build + 68. http://www.karlrunge.com/x11vnc/index.html#faq-binaries + 69. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download + 70. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts + 71. http://www.karlrunge.com/x11vnc/index.html#faq-config-file + 72. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg + 73. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe + 74. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations + 75. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc + 76. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp + 77. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 78. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 79. http://www.karlrunge.com/x11vnc/index.html#faq-windowid + 80. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id + 81. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp + 82. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 83. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 84. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg + 85. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control + 86. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 87. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 88. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt + 89. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared + 90. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt + 91. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 92. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface + 93. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost + 94. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix + 95. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty + 96. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt + 97. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords + 98. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt + 99. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy + 100. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock + 101. http://www.karlrunge.com/x11vnc/index.html#faq-service + 102. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 103. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 104. http://www.karlrunge.com/x11vnc/index.html#faq-java-http + 105. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect + 106. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 107. http://www.karlrunge.com/x11vnc/index.html#faq-headless + 108. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 109. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource + 110. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource + 111. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link + 112. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 113. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage + 114. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape + 115. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha + 116. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 117. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow + 118. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions + 119. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt + 120. http://www.karlrunge.com/x11vnc/index.html#faq-altgr + 121. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 122. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 123. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys + 124. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still + 125. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt + 126. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta + 127. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click + 128. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars + 129. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 130. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama + 131. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen + 132. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen + 133. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr + 134. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen + 135. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 136. http://www.karlrunge.com/x11vnc/index.html#faq-vmware + 137. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars + 138. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard + 139. http://www.karlrunge.com/x11vnc/index.html#faq-beeps + 140. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 144. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 145. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html + 146. http://www.karlrunge.com/x11vnc/index.html#building + 147. http://www.karlrunge.com/x11vnc/index.html#faq-build + 148. http://packages.debian.org/x11vnc + 149. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc + 150. http://dag.wieers.com/packages/x11vnc/ + 151. http://www.sunfreeware.com/ + 152. http://www.bell-labs.com/project/wwexptools/packages.html + 153. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 154. http://www.karlrunge.com/x11vnc/bins + 155. http://www.tightvnc.com/download.html + 156. http://www.realvnc.com/download-free.html + 157. http://sourceforge.net/projects/cotvnc/ + 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 159. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 163. http://www.karlrunge.com/x11vnc/x11vnc.c + 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe + 165. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb 167. http://fredrik.hubbe.net/x2vnc.html - 168. http://freshmeat.net/projects/x2x/ - 169. http://ftp.digital.com/pub/Digital/SRC/x2x/ - 170. http://zapek.com/software/zvnc/ - 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual - 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor - 174. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 179. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid - 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder - 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 186. http://www.karlrunge.com/x11vnc/index.html#xauth_pain - 187. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys - 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd - 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 199. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd - 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd - 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared - 207. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 208. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 209. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 212. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 213. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 222. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 223. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 168. http://www.hubbe.net/~hubbe/win2vnc.html + 169. http://www.deboer.gmxhome.de/ + 170. http://sourceforge.net/projects/win2vnc/ + 171. http://fredrik.hubbe.net/x2vnc.html + 172. http://freshmeat.net/projects/x2x/ + 173. http://ftp.digital.com/pub/Digital/SRC/x2x/ + 174. http://zapek.com/software/zvnc/ + 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor + 178. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 183. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid + 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder + 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 190. http://www.karlrunge.com/x11vnc/index.html#xauth_pain + 191. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys + 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd + 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 203. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd + 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd + 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared + 211. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 212. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 213. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 216. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 217. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 226. http://www.karlrunge.com/x11vnc/index.html#tunnelling 227. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly - 231. ftp://ftp.x.org/ - 232. http://www.karlrunge.com/x11vnc/dtVncPopup - 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 235. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 238. http://www.karlrunge.com/x11vnc/blockdpy.c - 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 242. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 243. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 244. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop - 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 246. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris - 247. http://www.jirka.org/gdm-documentation/x241.html - 248. http://www.karlrunge.com/x11vnc/x11vnc_loop - 249. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect - 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 257. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 258. http://www.karlrunge.com/x11vnc/shm_clear - 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 261. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 270. http://www.tightvnc.com/ - 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 290. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode - 291. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 292. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 298. http://www.tightvnc.com/ - 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer - 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 307. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 308. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 231. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly + 235. ftp://ftp.x.org/ + 236. http://www.karlrunge.com/x11vnc/dtVncPopup + 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 239. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 242. http://www.karlrunge.com/x11vnc/blockdpy.c + 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 246. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 247. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 248. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 250. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris + 251. http://www.jirka.org/gdm-documentation/x241.html + 252. http://www.karlrunge.com/x11vnc/x11vnc_loop + 253. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 261. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 262. http://www.karlrunge.com/x11vnc/shm_clear + 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 265. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 274. http://www.tightvnc.com/ + 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 294. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode + 295. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 296. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 302. http://www.tightvnc.com/ + 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 311. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless 312. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 323. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 328. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 330. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html - 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 336. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 344. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 345. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 350. mailto:xvml@karlrunge.com + 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 316. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes + 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 327. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 332. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 334. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html + 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 340. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 348. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 349. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 354. mailto:xvml@karlrunge.com ======================================================================= @@ -3862,6 +3989,7 @@ Options: also use "TrueColor", etc. see <X11/X.h> for a list. If the string ends in ":m" then for better or for worse the visual depth is forced to be m. + -overlay Handle multiple depth visuals on one screen, e.g. 8+24 and 24+8 overlay visuals (the 32 bits per pixel are packed with 8 for PseudoColor and 24 for TrueColor). @@ -3917,8 +4045,9 @@ Options: you may want to scale the cursor independently of the screen or not at all. If you specify -scale_cursor the cursor will be scaled by that factor. When using - -scale mode to keep the cursor at its "natural" - size use "-scale_cursor 1". + -scale mode to keep the cursor at its "natural" size + use "-scale_cursor 1". Most of the ":" scaling + options apply here as well. -viewonly All VNC clients can only watch (default off). -shared VNC display is shared (default off). @@ -3998,6 +4127,7 @@ Options: -storepasswd pass file Store password "pass" as the VNC password in the file "file". Once the password is stored the program exits. Use the password via "-rfbauth file" + -accept string Run a command (possibly to prompt the user at the X11 display) to decide whether an incoming client should be allowed to connect or not. "string" is @@ -4789,6 +4919,7 @@ Options: show_cursor enable showing a cursor. noshow_cursor disable showing a cursor. (same as "nocursor") + arrow:n set -arrow to alternate n. xfixes enable xfixes cursor shape mode. noxfixes disable xfixes cursor shape mode. alphacut:n set -alphacut to n. diff --git a/x11vnc/tkx11vnc b/x11vnc/tkx11vnc index f967047..3e793f5 100755 --- a/x11vnc/tkx11vnc +++ b/x11vnc/tkx11vnc @@ -167,6 +167,7 @@ Misc =D nobell =D nosel noprimary + nolookup -- bg =-C:ignore,exit sigpipe: diff --git a/x11vnc/tkx11vnc.h b/x11vnc/tkx11vnc.h index 2c62170..b64c437 100644 --- a/x11vnc/tkx11vnc.h +++ b/x11vnc/tkx11vnc.h @@ -173,6 +173,7 @@ " =D nobell\n" " =D nosel\n" " noprimary\n" +" nolookup\n" " --\n" " bg\n" " =-C:ignore,exit sigpipe:\n" diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index e1141e8..cd519d9 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "March 2005" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.7.2pre, lastmod: 2005-03-19 + version: 0.7.2pre, lastmod: 2005-03-29 .SH SYNOPSIS .B x11vnc [OPTION]... @@ -168,7 +168,7 @@ image may not be sharp and response may be slower. If \fIfraction\fR contains a decimal point "." it is taken as a floating point number, alternatively the notation "m/n" may be used to denote fractions -exactly, e.g. \fB-scale\fR 2/3. +exactly, e.g. \fB-scale\fR 2/3 .IP Scaling Options: can be added after \fIfraction\fR via ":", to supply multiple ":" options use commas. @@ -281,6 +281,13 @@ you may need to manually adjust the \fB-allow\fR list (and vice versa) to avoid situations where no connections (or too many) are allowed. .PP +\fB-nolookup\fR +.IP +Do not use gethostbyname() or gethostbyaddr() to look up +host names or IP numbers. Use this if name resolution +is incorrectly set up and leads to long pauses as name +lookup times out, etc. +.PP \fB-input\fR \fIstring\fR .IP Fine tuning of allowed user input. If \fIstring\fR does @@ -918,7 +925,7 @@ screen changes: everything will bog down when dragging or scrolling. So a scheme has to be used to "eat" much of that pointer input before re-polling the screen and sending out framebuffer updates. The mode number -\fIn\fR can be 0 to 4 and selects one of the schemes +\fIn\fR can be 0 to 5 and selects one of the schemes desribed below. .IP n=0: does the same as \fB-nodragging.\fR (all screen polling @@ -931,19 +938,24 @@ events before repolling the screen. n=2 is an improved scheme: by watching the current rate of input events it tries to detect if it should try to "eat" additional pointer events before continuing. +This mode was the default until Apr 2005. .IP -n=3 is basically a dynamic \fB-nodragging\fR mode: it detects +n=3 is basically the same as n=2 except with slightly +tweaked parameters. We made this a new one so one +could use \fB-pm\fR 2 for the old behavior. +.IP +n=4 is basically a dynamic \fB-nodragging\fR mode: it detects when the mouse motion has paused and then refreshes the display. .IP -n=4: attempts to measures network rates and latency, +n=5 attempts to measures network rates and latency, the video card read rate, and how many tiles have been changed on the screen. From this, it aggressively tries to push screen "frames" when it decides it has enough resources to do so. NOT FINISHED. .IP -The default n is 2. Note that modes 2, 3, 4 will skip -\fB-input_skip\fR keyboard events (but it will not count +The default n is 3. Note that modes 2, 3, 4, 5 will +skip \fB-input_skip\fR keyboard events (but it will not count pointer events). Also note that these modes are not available in \fB-threads\fR mode which has its own pointer event handling mechanism. @@ -973,13 +985,15 @@ milliseconds, respectively. If a value is left blank, e.g. "\fB-speeds\fR \fI,100,15\fR", then the internal scheme is used to estimate the empty value(s). .IP +Note: use this option is currently NOT FINISHED. +.IP Typical PC video cards have read rates of 5-10 MB/sec. If the framebuffer is in main memory instead of video h/w (e.g. SunRay, shadowfb, Xvfb), the read rate may be much faster. "x11perf \fB-getimage500"\fR can be used to get a lower bound (remember to factor in the bytes per pixel). It is up to you to estimate the network -bandwith to clients. For the latency the +bandwith and latency to clients. For the latency the .IR ping (1) command can be used. .IP @@ -1272,8 +1286,8 @@ disconnect:host disconnect any clients from "host" same as "close:host". Use host "all" to close all current clients. If you know the client internal hex ID, - e.g. 0x3 (returned by \fB-query\fR clients and - RFB_CLIENT_ID), you can use that too. + e.g. 0x3 (returned by "\fB-query\fR \fIclients\fR" + and RFB_CLIENT_ID) you can use that too. .IP allowonce:host For the next connection only, allow connection from "host". @@ -1290,6 +1304,10 @@ nolocalhost disable \fB-localhost\fR mode .IP listen:str set \fB-listen\fR to str, empty to disable. .IP +nolookup enable \fB-nolookup\fR mode. +.IP +lookup disable \fB-nolookup\fR mode. +.IP input:str set \fB-input\fR to "str", empty to disable. .IP client_input:str set the K, M, B \fB-input\fR on a per-client @@ -1581,9 +1599,9 @@ overlay nooverlay overlay_cursor overlay_yescursor nooverlay_nocursor nooverlay_cursor nooverlay_yescursor overlay_nocursor visual scale scale_cursor viewonly noviewonly shared noshared forever noforever once -timeout deny lock nodeny unlock connect allowonce -allow localhost nolocalhost listen accept gone -shm noshm flipbyteorder noflipbyteorder onetile +timeout deny lock nodeny unlock connect allowonce allow +localhost nolocalhost listen lookup nolookup accept +gone shm noshm flipbyteorder noflipbyteorder onetile noonetile solid_color solid nosolid blackout xinerama noxinerama xrandr noxrandr xrandr_mode padgeom quiet q noquiet modtweak nomodtweak xkb noxkb skip_keycodes @@ -1621,10 +1639,10 @@ cdpy_x cdpy_y coff_x coff_y rfbauth passwd By default \fB-remote\fR commands are run asynchronously, that is, the request is posted and the program immediately exits. Use \fB-sync\fR to have the program wait for an -acknowledgement from the x11vnc server that command -was processed. On the other hand \fB-query\fR requests are -always processed synchronously because they have wait -for the result. +acknowledgement from the x11vnc server that command was +processed (somehow). On the other hand \fB-query\fR requests +are always processed synchronously because they have +to wait for the result. .IP Also note that if both \fB-remote\fR and \fB-query\fR requests are supplied on the command line, the \fB-remote\fR is processed @@ -1642,19 +1660,21 @@ taken place. Do not process any remote control commands or queries. .IP A note about security wrt remote control commands. -If someone can connect to the X display and change the -property VNC_CONNECT, then they can remotely control -x11vnc. Normally access to the X display is protected. -Note that if they can modify VNC_CONNECT, they could -also run their own x11vnc and have complete control +If someone can connect to the X display and change +the property VNC_CONNECT, then they can remotely +control x11vnc. Normally access to the X display is +protected. Note that if they can modify VNC_CONNECT +on the X server, they have enough permissions to also +run their own x11vnc and thus have complete control of the desktop. If the "\fB-connect\fR \fI/path/to/file\fR" -channel is being used, obviously anyone who can -write to /path/to/file can remotely control x11vnc. -So be sure to protect the X display and that file's -write permissions. -.IP -To disable the VNC_CONNECT property channel completely -use \fB-novncconnect.\fR +channel is being used, obviously anyone who can write +to /path/to/file can remotely control x11vnc. So be +sure to protect the X display and that file's write +permissions. +.IP +If you are paranoid and do not think \fB-noremote\fR is +enough, to disable the VNC_CONNECT property channel +completely use \fB-novncconnect.\fR .PP \fB-unsafe\fR .IP diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index cb38347..5b670b0 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -37,11 +37,11 @@ * * Another goal is to improve performance and interactive response. * The algorithm of x0rfbserver was used as a base. Additional heuristics - * are also applied (currently there are a bit too many of these...) + * are also applied. * * Another goal is to add many features that enable and incourage creative - * Ausage and application of the tool. pologies for the large number - * Aof options! + * usage and application of the tool. Apologies for the large number + * of options! * * To build: * @@ -60,18 +60,18 @@ * The screen updates are good, but of course not perfect since the X * display must be continuously polled and read for changes and this is * slow for most hardware. This can be contrasted with receiving a change - * callback from the X server, if that were generally possible... (Update: - * this seems to be handled now with the X DAMAGE extension, but - * unfortunately that doesn't seem to address the slow read from the - * video h/w. So, e.g., opaque moves and similar window activity can - * be very painful; one has to modify one's behavior a bit. + * callback from the X server, if that were generally possible... (UPDATE: + * this is handled now with the X DAMAGE extension, but unfortunately + * that doesn't seem to address the slow read from the video h/w). So, + * e.g., opaque moves and similar window activity can be very painful; + * one has to modify one's behavior a bit. * * General audio at the remote display is lost unless one separately * sets up some audio side-channel such as esd. * * It does not appear possible to query the X server for the current * cursor shape. We can use XTest to compare cursor to current window's - * cursor, but we cannot extract what the cursor is... (Update: we now + * cursor, but we cannot extract what the cursor is... (UPDATE: we now * use XFIXES extension for this. Also on Solaris and IRIX Overlay * extensions exists that allow drawing the mouse into the framebuffer) * @@ -82,7 +82,7 @@ * currently "-cursor some" is a first hack at this) * * Under XFIXES mode for showing the cursor shape, the cursor may be - * poorly approximated if it has transparency. + * poorly approximated if it has transparency (alpha channel). * * Windows using visuals other than the default X visual may have * their colors messed up. When using 8bpp indexed color, the colormap @@ -93,9 +93,9 @@ * On Sun and Sgi hardware we can to work around this with -overlay. * * Feature -id <windowid> can be picky: it can crash for things like - * the window not sufficiently mapped into server memory, etc (Update: - * we now use the -xrandr mechanisms to trap errors for this mode). - * SaveUnders menus, popups, etc will not be seen. + * the window not sufficiently mapped into server memory, etc (UPDATE: + * we now use the -xrandr mechanisms to trap errors more robustly for + * this mode). SaveUnders menus, popups, etc will not be seen. * * Under some situations the keysym unmapping is not correct, especially * if the two keyboards correspond to different languages. The -modtweak @@ -128,11 +128,15 @@ /* -- x11vnc.h -- */ /* + *************************************************************************** * if you are inserting this file, x11vnc.c into an old CVS tree you - * may need to set OLD_TREE to 1. See below for LibVNCServer 0.7 tips. + * may need to set OLD_TREE to 1. Or use -DOLD_TREE=1 in CPPFLAGS. + * See below for LibVNCServer 0.7 tips. */ +#ifndef OLD_TREE #define OLD_TREE 0 +#endif #if OLD_TREE /* @@ -173,6 +177,10 @@ */ #endif /* OLD_TREE */ +/****************************************************************************/ + + +/* Standard includes and libvncserver */ #include <unistd.h> #include <signal.h> @@ -191,6 +199,7 @@ #include <rfb/rfb.h> #include <rfb/rfbregion.h> +/****************************************************************************/ #if OLD_TREE /* * This is another transient for building in older libvncserver trees, @@ -210,9 +219,9 @@ #define rfbHttpInitSockets httpInitSockets #define RFBUNDRAWCURSOR(s) if (s) {rfbUndrawCursor(s);} -#else +#else /* OLD_TREE */ #define RFBUNDRAWCURSOR(s) -#endif +#endif /* !OLD_TREE */ /* * To get a clean build in a LibVNCServer 0.7 source tree no need for * OLD_TREE, you just need to either download the forgotten tkx11vnc.h @@ -230,7 +239,60 @@ * that may break some usage): * #define listenInterface maxRectsPerUpdate + * + */ +/****************************************************************************/ + + +/* Build-time customization via CPPFLAGS. */ + +/* + * -DX11VNC_SHARED to have the vnc display shared by default. + */ + +/* + * -DX11VNC_FOREVER to have -forever on by default. + */ + +/* + * This can be used to disable the remote control mechanism. + * E.g. -DREMOTE_CONTROL=0 in CPPFLAGS. */ +#ifndef REMOTE_CONTROL +#define REMOTE_CONTROL 1 +#endif + +/* + * Beginning of support for small binary footprint build for embedded + * systems, PDA's etc. It currently just cuts out the low-hanging + * fruit (large text passages). Set to 2, 3 to cut out some of the + * more esoteric extensions. More tedious is to modify LDFLAGS in the + * Makefile to not link against the extension libraries... but that + * should be done too (manually for now). + * + * If there is interest more of the bloat can be removed... Currently + * these shrink the binary from 500K to about 270K. + */ +#ifndef SMALL_FOOTPRINT +#define SMALL_FOOTPRINT 0 +#endif + +#if (SMALL_FOOTPRINT > 1) +#define LIBVNCSERVER_HAVE_XKEYBOARD 0 +#define LIBVNCSERVER_HAVE_LIBXINERAMA 0 +#define LIBVNCSERVER_HAVE_LIBXRANDR 0 +#define LIBVNCSERVER_HAVE_LIBXFIXES 0 +#define LIBVNCSERVER_HAVE_LIBXDAMAGE 0 +#endif + +#if (SMALL_FOOTPRINT > 2) +#define LIBVNCSERVER_HAVE_UTMPX_H 0 +#define LIBVNCSERVER_HAVE_PWD_H 0 +#define REMOTE_CONTROL 0 +#endif + + +/* Extensions and related includes: */ #if LIBVNCSERVER_HAVE_XSHM # if defined(__hpux) && defined(__ia64) /* something weird on hp/itanic */ @@ -311,7 +373,7 @@ int overlay_present = 0; */ #if LIBVNCSERVER_HAVE_LIBXRANDR #include <X11/extensions/Xrandr.h> -static int xrandr_base_event_type; +static int xrandr_base_event_type = 0; #endif int xfixes_present = 0; @@ -326,15 +388,14 @@ int alt_arrow = 1; #if LIBVNCSERVER_HAVE_LIBXFIXES #include <X11/extensions/Xfixes.h> -static int xfixes_base_event_type; +static int xfixes_base_event_type = 0; #endif int xdamage_present = 0; -int using_xdamage = 0; -int use_xdamage_hints = 1; /* just use the xdamage rects. for scanline hints */ +int use_xdamage = 1; /* just use the xdamage rects. for scanline hints */ #if LIBVNCSERVER_HAVE_LIBXDAMAGE #include <X11/extensions/Xdamage.h> -static int xdamage_base_event_type; +static int xdamage_base_event_type = 0; Damage xdamage = 0; #endif int xdamage_max_area = 20000; /* pixels */ @@ -344,7 +405,7 @@ int xdamage_tile_count; int hack_val = 0; /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.7.2pre lastmod: 2005-03-19"; +char lastmod[] = "0.7.2pre lastmod: 2005-03-29"; /* X display info */ @@ -457,6 +518,7 @@ unsigned char *tile_has_xdamage_diff, *tile_row_has_xdamage_diff; /* times of recent events */ time_t last_event, last_input, last_client = 0; +time_t last_sendevent = 0; /* last client to move pointer */ rfbClientPtr last_pointer_client = NULL; @@ -569,6 +631,7 @@ void mark_hint(hint_t); void mark_rect_as_modified(int x1, int y1, int x2, int y2, int force); enum rfbNewClientAction new_client(rfbClientPtr client); +void set_nofb_params(void); void nofb_hook(rfbClientPtr client); void pointer(int mask, int x, int y, rfbClientPtr client); void cursor_position(int, int); @@ -661,11 +724,21 @@ char *rc_rcfile = NULL; /* -rc */ int rc_norc = 0; int opts_bg = 0; +#ifndef X11VNC_SHARED int shared = 0; /* share vnc display. */ +#else +int shared = 1; +#endif +#ifndef X11VNC_FOREVER +int connect_once = 1; /* disconnect after first connection session. */ +#else +int connect_once = 0; +#endif int deny_all = 0; /* global locking of new clients */ int accept_remote_cmds = 1; /* -noremote */ int safe_remote_only = 0; /* -safer, -unsafe */ int started_as_root = 0; +int host_lookup = 1; char *users_list = NULL; /* -users */ char *allow_list = NULL; /* for -allow and -localhost */ char *listen_str = NULL; @@ -678,7 +751,6 @@ char *allowed_input_normal = NULL; char *allowed_input_str = NULL; char *viewonly_passwd = NULL; /* view only passwd. */ int inetd = 0; /* spawned from inetd(1) */ -int connect_once = 1; /* disconnect after first connection session. */ int first_conn_timeout = 0; /* -timeout */ int flash_cmap = 0; /* follow installed colormaps */ int force_indexed_color = 0; /* whether to force indexed color for 8bpp */ @@ -721,7 +793,6 @@ int no_repeat_countdown = 2; int watch_bell = 1; /* watch for the bell using XKEYBOARD */ int sound_bell = 1; /* actually send it */ int xkbcompat = 0; /* ignore XKEYBOARD extension */ -int use_xkb = 0; /* try to open Xkb connection (for bell or other) */ int use_xkb_modtweak = 0; /* -xkb */ char *skip_keycodes = NULL; int add_keysyms = 0; /* automatically add keysyms to X server */ @@ -729,9 +800,12 @@ int add_keysyms = 0; /* automatically add keysyms to X server */ char *remap_file = NULL; /* -remap */ char *pointer_remap = NULL; /* use the various ways of updating pointer */ -#define POINTER_MODE_DEFAULT 2 +#ifndef POINTER_MODE_DEFAULT +#define POINTER_MODE_DEFAULT 3 +#endif +#define POINTER_MODE_NOFB 2 int pointer_mode = POINTER_MODE_DEFAULT; -int pointer_mode_max = 4; +int pointer_mode_max = 5; int single_copytile = 0; /* use the old way copy_tiles() */ int single_copytile_orig = 0; int single_copytile_count = 0; @@ -801,6 +875,8 @@ int quiet = 0; int got_rfbport = 0; int got_alwaysshared = 0; int got_nevershared = 0; +int got_cursorpos = 0; +int got_pointer_mode = -1; /* threaded vs. non-threaded (default) */ #if LIBVNCSERVER_X11VNC_THREADED && ! defined(X11VNC_THREADED) @@ -1112,7 +1188,7 @@ void switch_user_task_solid_bg(void) { } } -void check_switched_user (void) { +void check_switched_user(void) { static time_t sched_switched_user = 0; static int did_solid = 0; static int did_dummy = 0; @@ -1785,6 +1861,10 @@ char *host2ip(char *host) { struct sockaddr_in addr; char *str; + if (! host_lookup) { + return NULL; + } + hp = gethostbyname(host); if (!hp) { return NULL; @@ -1802,6 +1882,10 @@ char *ip2host(char *ip) { struct hostent *hp; in_addr_t iaddr; + if (! host_lookup) { + return strdup("unknown"); + } + iaddr = inet_addr(ip); if (iaddr == htonl(INADDR_NONE)) { return strdup("unknown"); @@ -3391,6 +3475,7 @@ static char t2x2_bits[] = { } if (out != -1) { ret = out; + XSelectInput(dpy, awin, 0); XUnmapWindow(dpy, awin); XFreeGC(dpy, gc); XDestroyWindow(dpy, awin); @@ -3518,7 +3603,6 @@ static int accept_client(rfbClientPtr client) { addr = "unknown-host"; } - if (strstr(accept_cmd, "popup") == accept_cmd) { /* use our builtin popup button */ @@ -6230,7 +6314,7 @@ void pointer(int mask, int x, int y, rfbClientPtr client) { */ #if LIBVNCSERVER_HAVE_XKEYBOARD -static int xkb_base_event_type; +static int xkb_base_event_type = 0; /* * check for XKEYBOARD, set up xkb_base_event_type @@ -6239,36 +6323,46 @@ void initialize_xkb(void) { int ir, reason; int op, ev, er, maj, min; - if (! XkbQueryExtension(dpy, &op, &ev, &er, &maj, &min)) { - if (! quiet && use_xkb) { + if (xkbcompat) { + xkb_present = 0; + } else if (! XkbQueryExtension(dpy, &op, &ev, &er, &maj, &min)) { + if (! quiet) { rfbLog("warning: XKEYBOARD extension not present.\n"); } xkb_present = 0; - use_xkb = 0; - return; } else { xkb_present = 1; } - if (! use_xkb) { + + if (! xkb_present) { return; } + if (! XkbOpenDisplay(DisplayString(dpy), &xkb_base_event_type, &ir, NULL, NULL, &reason) ) { if (! quiet) { rfbLog("warning: disabling XKEYBOARD. XkbOpenDisplay" " failed.\n"); } - use_xkb = 0; + xkb_base_event_type = 0; + xkb_present = 0; } } void initialize_watch_bell(void) { - if (! use_xkb) { + if (! xkb_present) { if (! quiet) { rfbLog("warning: disabling bell. XKEYBOARD ext. " "not present.\n"); } watch_bell = 0; + sound_bell = 0; + return; + } + + XkbSelectEvents(dpy, XkbUseCoreKbd, XkbBellNotifyMask, 0); + + if (! watch_bell) { return; } if (! XkbSelectEvents(dpy, XkbUseCoreKbd, XkbBellNotifyMask, @@ -6278,6 +6372,7 @@ void initialize_watch_bell(void) { " failed.\n"); } watch_bell = 0; + sound_bell = 0; } } @@ -6290,33 +6385,40 @@ void check_bell_event(void) { XkbAnyEvent *xkb_ev; int got_bell = 0; - if (! watch_bell) { + if (! xkb_base_event_type) { return; } - X_LOCK; + /* caller does X_LOCK */ if (! XCheckTypedEvent(dpy, xkb_base_event_type, &xev)) { - X_UNLOCK; return; } + if (! watch_bell) { + /* we return here to avoid xkb events piling up */ + return; + } + xkb_ev = (XkbAnyEvent *) &xev; if (xkb_ev->xkb_type == XkbBellNotify) { got_bell = 1; } - X_UNLOCK; if (got_bell && sound_bell) { if (! all_clients_initialized()) { rfbLog("check_bell_event: not sending bell: " "uninitialized clients\n"); } else { - if (screen) { + if (screen && client_count) { rfbSendBell(screen); } } } } #else +void initialize_watch_bell(void) { + watch_bell = 0; + sound_bell = 0; +} void check_bell_event(void) {} #endif @@ -6493,8 +6595,8 @@ int check_xrandr_event(char *msg) { if (! xrandr || ! xrandr_present) { return 0; } - if (XCheckTypedEvent(dpy, xrandr_base_event_type + - RRScreenChangeNotify, &xev)) { + if (xrandr_base_event_type && XCheckTypedEvent(dpy, + xrandr_base_event_type + RRScreenChangeNotify, &xev)) { int do_change; XRRScreenChangeNotifyEvent *rev; @@ -6663,6 +6765,7 @@ static void selection_request(XEvent *ev) { if (! trapped_xerror) { XSendEvent(req_event->display, req_event->requestor, False, 0, (XEvent *)¬ify_event); + last_sendevent = time(0); } if (trapped_xerror) { rfbLog("selection_request: ignored XError while sending " @@ -6836,23 +6939,25 @@ void initialize_xevents(void) { static int did_xdamage = 0; static int did_xrandr = 0; - X_LOCK; if ((watch_selection || vnc_connect) && !did_xselect_input) { /* * register desired event(s) for notification. * PropertyChangeMask is for CUT_BUFFER0 changes. * XXX: does this cause a flood of other stuff? */ + X_LOCK; XSelectInput(dpy, rootwin, PropertyChangeMask); + X_UNLOCK; did_xselect_input = 1; } if (watch_selection && !did_xcreate_simple_window) { /* create fake window for our selection ownership, etc */ + X_LOCK; selwin = XCreateSimpleWindow(dpy, rootwin, 0, 0, 1, 1, 0, 0, 0); + X_UNLOCK; did_xcreate_simple_window = 1; } - X_UNLOCK; if (xrandr && !did_xrandr) { initialize_xrandr(); @@ -6878,16 +6983,19 @@ void initialize_xevents(void) { */ void check_xevents(void) { XEvent xev; - static int first = 1, sent_some_sel = 0; + int have_clients = 0; + static int sent_some_sel = 0; static time_t last_request = 0; + static time_t last_call = 0; + static time_t last_bell = 0; + static time_t last_init_check = 0; + static time_t last_sync = 0; time_t now = time(0); - int have_clients = 0; - - if (first) { + if (now > last_init_check+1) { + last_init_check = now; initialize_xevents(); } - first = 0; if (screen && screen->clientHead) { have_clients = 1; @@ -6898,7 +7006,7 @@ void check_xevents(void) { * the client... so instead of sending right away we wait a * the few seconds. */ - if (have_clients && watch_selection && ! sent_some_sel + if (have_clients && watch_selection && !sent_some_sel && now > last_client + sel_waittime) { if (XGetSelectionOwner(dpy, XA_PRIMARY) == None) { cutbuffer_send(); @@ -6917,7 +7025,7 @@ void check_xevents(void) { } } - if (no_autorepeat && client_count && no_repeat_countdown) { + if (no_autorepeat && have_clients && no_repeat_countdown) { static time_t last_check = 0; if (now > last_check + 1) { last_check = now; @@ -6941,8 +7049,12 @@ void check_xevents(void) { } } - if (XCheckTypedEvent(dpy, MappingNotify, &xev)) { + if (now > last_call && XCheckTypedEvent(dpy, MappingNotify, &xev)) { + /* we only check this once a second or so. */ XRefreshKeyboardMapping((XMappingEvent *) &xev); + while (XCheckTypedEvent(dpy, MappingNotify, &xev)) { + XRefreshKeyboardMapping((XMappingEvent *) &xev); + } if (use_modifier_tweak) { X_UNLOCK; initialize_modtweak(); @@ -6950,6 +7062,17 @@ void check_xevents(void) { } } + if (last_sendevent && (now > last_sendevent+1 || now % 10 == 0)) { + /* + * we can get ClientMessage from our XSendEvent() call in + * selection_request(). + */ + while (XCheckTypedEvent(dpy, ClientMessage, &xev)) { + ; + } + last_sendevent = 0; + } + /* check for CUT_BUFFER0 and VNC_CONNECT changes: */ if (XCheckTypedEvent(dpy, PropertyNotify, &xev)) { if (xev.type == PropertyNotify) { @@ -6983,9 +7106,11 @@ void check_xevents(void) { } #endif #if LIBVNCSERVER_HAVE_LIBXFIXES - if (XCheckTypedEvent(dpy, xfixes_base_event_type + - XFixesCursorNotify, &xev)) { - got_xfixes_cursor_notify++; + if (xfixes_present && use_xfixes && xfixes_base_event_type) { + if (XCheckTypedEvent(dpy, xfixes_base_event_type + + XFixesCursorNotify, &xev)) { + got_xfixes_cursor_notify++; + } } #endif @@ -7044,7 +7169,63 @@ void check_xevents(void) { } } } + + if (watch_bell || now > last_bell+1) { + last_bell = now; + check_bell_event(); + } + +#ifndef DEBUG_XEVENTS +#define DEBUG_XEVENTS 0 +#endif +#if DEBUG_XEVENTS + if (hack_val) { + static time_t last_check = 0; + + if (now > last_check + 1) { + XEvent xevs[400]; + int i, tot = XEventsQueued(dpy, QueuedAlready); + + last_check = now; + if (tot) { + fprintf(stderr, "Total events queued: %d\n", + tot); + } + for (i=1; i<300; i++) { + int k, n = 0; + while (XCheckTypedEvent(dpy, i, xevs+n)) { + if (++n >= 400) { + break; + } + } + if (n) { + fprintf(stderr, "%d events of type %d " + "queued\n", n, i); + } + for (k=n-1; k >= 0; k--) { + XPutBackEvent(dpy, xevs+k); + } + } + } + } +#endif + + if (now > last_sync + 3600) { + /* kludge for any remaining event leaks */ + int bugout = use_xdamage ? 500 : 50; + if (last_sync != 0) { + int qlen = XEventsQueued(dpy, QueuedAlready); + if (qlen >= bugout) { + rfbLog("event leak: %d queued, " + " calling XSync(dpy, True)\n", qlen); + XSync(dpy, True); + } + } + last_sync = now; + } X_UNLOCK; + + last_call = now; } /* @@ -7484,6 +7665,7 @@ void reset_rfbport(int old, int new) { * -remote/-R and -query/-Q. */ char *process_remote_cmd(char *cmd, int stringonly) { +#if REMOTE_CONTROL char *p = cmd; char *co = ""; char buf[VNC_CONNECT_MAX]; @@ -7572,7 +7754,7 @@ char *process_remote_cmd(char *cmd, int stringonly) { } /* - * Add: passwdfile logfile bg nofb rfbauth passwd noshm... + * Maybe add: passwdfile logfile bg rfbauth passwd... */ if (!strcmp(p, "stop") || !strcmp(p, "quit") || !strcmp(p, "exit") || !strcmp(p, "shutdown")) { @@ -8163,7 +8345,9 @@ char *process_remote_cmd(char *cmd, int stringonly) { struct hostent *hp; in_addr_t iface = inet_addr(listen_str); if (iface == htonl(INADDR_NONE)) { - if (!(hp = gethostbyname(listen_str))) { + if (!host_lookup) { + ok = 0; + } else if (!(hp = gethostbyname(listen_str))) { ok = 0; } else { iface = *(unsigned long *)hp->h_addr; @@ -8213,6 +8397,20 @@ char *process_remote_cmd(char *cmd, int stringonly) { free(listen_str); listen_str = before; } + } else if (!strcmp(p, "lookup")) { + if (query) { + snprintf(buf, bufn, "ans=%s:%d", p, host_lookup); + goto qry; + } + rfbLog("process_remote_cmd: enabling hostname lookup.\n"); + host_lookup = 1; + } else if (!strcmp(p, "nolookup")) { + if (query) { + snprintf(buf, bufn, "ans=%s:%d", p, !host_lookup); + goto qry; + } + rfbLog("process_remote_cmd: disabling hostname lookup.\n"); + host_lookup = 0; } else if (strstr(p, "accept") == p) { COLON_CHECK("accept:") @@ -8745,6 +8943,10 @@ char *process_remote_cmd(char *cmd, int stringonly) { } if (nofb) { rfbLog("process_remote_cmd: disabling nofb mode.\n"); + rfbLog(" you may need to these turn back on:\n"); + rfbLog(" xfixes, xdamage, solid, flashcmap\n"); + rfbLog(" overlay, shm, noonetile, nap, cursor\n"); + rfbLog(" cursorpos, cursorshape, bell.\n"); nofb = 0; do_new_fb(1); } @@ -8759,6 +8961,10 @@ char *process_remote_cmd(char *cmd, int stringonly) { push_black_screen(4); } nofb = 1; + sound_bell = 0; + initialize_watch_bell(); + set_nofb_params(); + do_new_fb(1); } } else if (!strcmp(p, "bell")) { @@ -8767,6 +8973,7 @@ char *process_remote_cmd(char *cmd, int stringonly) { goto qry; } rfbLog("process_remote_cmd: enabling bell (if supported).\n"); + initialize_watch_bell(); sound_bell = 1; } else if (!strcmp(p, "nobell")) { @@ -8775,6 +8982,7 @@ char *process_remote_cmd(char *cmd, int stringonly) { goto qry; } rfbLog("process_remote_cmd: disabling bell.\n"); + initialize_watch_bell(); sound_bell = 0; } else if (!strcmp(p, "sel")) { @@ -8782,16 +8990,20 @@ char *process_remote_cmd(char *cmd, int stringonly) { snprintf(buf, bufn, "ans=%s:%d", p, watch_selection); goto qry; } - rfbLog("process_remote_cmd: enabling watch_selection.\n"); + rfbLog("process_remote_cmd: enabling watch " + "selection+primary.\n"); watch_selection = 1; + watch_primary = 1; } else if (!strcmp(p, "nosel")) { if (query) { snprintf(buf, bufn, "ans=%s:%d", p, !watch_selection); goto qry; } - rfbLog("process_remote_cmd: disabling watch_selection.\n"); + rfbLog("process_remote_cmd: disabling watch " + "selection+primary.\n"); watch_selection = 0; + watch_primary = 0; } else if (!strcmp(p, "primary")) { if (query) { @@ -8963,9 +9175,9 @@ char *process_remote_cmd(char *cmd, int stringonly) { first_cursor(); } else if (!strcmp(p, "xdamage")) { - int orig = use_xdamage_hints; + int orig = use_xdamage; if (query) { - snprintf(buf, bufn, "ans=%s:%d", p, use_xdamage_hints); + snprintf(buf, bufn, "ans=%s:%d", p, use_xdamage); goto qry; } if (! xdamage_present) { @@ -8975,15 +9187,15 @@ char *process_remote_cmd(char *cmd, int stringonly) { } rfbLog("process_remote_cmd: enabling xdamage hints" " (if supported).\n"); - use_xdamage_hints = 1; - if (use_xdamage_hints != orig) { + use_xdamage = 1; + if (use_xdamage != orig) { initialize_xdamage(); create_xdamage(); } } else if (!strcmp(p, "noxdamage")) { - int orig = use_xdamage_hints; + int orig = use_xdamage; if (query) { - snprintf(buf, bufn, "ans=%s:%d", p, !use_xdamage_hints); + snprintf(buf, bufn, "ans=%s:%d", p, !use_xdamage); goto qry; } if (! xdamage_present) { @@ -8992,8 +9204,8 @@ char *process_remote_cmd(char *cmd, int stringonly) { goto done; } rfbLog("process_remote_cmd: disabling xdamage hints.\n"); - use_xdamage_hints = 0; - if (use_xdamage_hints != orig) { + use_xdamage = 0; + if (use_xdamage != orig) { initialize_xdamage(); destroy_xdamage(); } @@ -9825,6 +10037,7 @@ char *process_remote_cmd(char *cmd, int stringonly) { set_vnc_connect_prop(buf); XFlush(dpy); } +#endif return NULL; } @@ -9877,7 +10090,6 @@ void record_desired_xdamage_rect(int x, int y, int w, int h) { nt_y1 = nfix( (y)/tile_y, ntiles_y); nt_y2 = nfix((y+h)/tile_y, ntiles_y); - /* loop over the rectangle of tiles (1 tile for a small input rect */ for (ix = nt_x1; ix <= nt_x2; ix++) { for (iy = nt_y1; iy <= nt_y2; iy++) { @@ -9896,9 +10108,6 @@ void record_desired_xdamage_rect(int x, int y, int w, int h) { void collect_xdamage(int scancnt) { #if LIBVNCSERVER_HAVE_LIBXDAMAGE XDamageNotifyEvent *dev; -#if 0 - XserverRegion xregion; -#endif XEvent ev; sraRegionPtr tmpregion; sraRegionPtr reg; @@ -9911,12 +10120,15 @@ void collect_xdamage(int scancnt) { #define DUPSZ 16 int dup_x[DUPSZ], dup_y[DUPSZ], dup_w[DUPSZ], dup_h[DUPSZ]; - if (! xdamage_present || ! using_xdamage) { + if (! xdamage_present || ! use_xdamage) { return; } if (! xdamage) { return; } + if (! xdamage_base_event_type) { + return; + } nreg = (xdamage_memory * NSCAN) + 1; xdamage_ticker = (xdamage_ticker+1) % nreg; @@ -9974,8 +10186,8 @@ void collect_xdamage(int scancnt) { /* set coords relative to fb origin */ if (0 && rootshift) { /* - * not needed because damage is relative - * to subwin, not rootwin. + * Note: not needed because damage is + * relative to subwin, not rootwin. */ x = x - off_x; y = y - off_y; @@ -10000,7 +10212,6 @@ void collect_xdamage(int scancnt) { } } - record_desired_xdamage_rect(x, y, w, h); tmpregion = sraRgnCreateRect(x, y, x + w, y + h); @@ -10024,7 +10235,6 @@ void collect_xdamage(int scancnt) { rat = ((double) XD_skip)/XD_tot; } -if (0) fprintf(stderr, "skip/tot: %04d/%04d rat=%.3f rect_count: %d desired_rects: %d\n", XD_skip, XD_tot, rat, rect_count, XD_des); XD_skip = 0; XD_tot = 0; XD_des = 0; @@ -10039,7 +10249,7 @@ int xdamage_hint_skip(int y) { sraRegionPtr reg, tmpl; int ret, i, n, nreg; - if (!xdamage_present || !using_xdamage || !use_xdamage_hints) { + if (! xdamage_present || ! use_xdamage) { return 0; /* cannot skip */ } if (! xdamage_regions) { @@ -10078,11 +10288,8 @@ void initialize_xdamage(void) { sraRegionPtr *ptr; int i, nreg; - using_xdamage = 0; - if (xdamage_present) { - if (use_xdamage_hints) { - using_xdamage = 1; - } + if (! xdamage_present) { + use_xdamage = 0; } if (xdamage_regions) { ptr = xdamage_regions; @@ -10093,7 +10300,7 @@ void initialize_xdamage(void) { free(xdamage_regions); xdamage_regions = NULL; } - if (using_xdamage) { + if (use_xdamage) { nreg = (xdamage_memory * NSCAN) + 2; xdamage_regions = (sraRegionPtr *) malloc(nreg * sizeof(sraRegionPtr)); @@ -10126,8 +10333,16 @@ void create_xdamage(void) { void destroy_xdamage(void) { #if LIBVNCSERVER_HAVE_LIBXDAMAGE if (xdamage) { + XEvent ev; X_LOCK; XDamageDestroy(dpy, xdamage); + XFlush(dpy); + if (xdamage_base_event_type) { + while (XCheckTypedEvent(dpy, + xdamage_base_event_type+XDamageNotify, &ev)) { + ; + } + } X_UNLOCK; rfbLog("destroyed xdamage object: 0x%lx\n", xdamage); xdamage = 0; @@ -10136,7 +10351,7 @@ void destroy_xdamage(void) { } void check_xdamage_state(void) { - if (! using_xdamage || ! xdamage_present) { + if (! use_xdamage || ! xdamage_present) { return; } /* @@ -11263,7 +11478,7 @@ int get_xfixes_cursor(int init) { time_t oldtime, now; XFixesCursorImage *xfc; - if (! got_xfixes_cursor_notify) { + if (! got_xfixes_cursor_notify && xfixes_base_event_type) { /* try again for XFixesCursorNotify event */ XEvent xev; X_LOCK; @@ -12128,6 +12343,35 @@ void set_visual(char *str) { visual_id = vinfo.visualid; } +void set_nofb_params(void) { + use_xfixes = 0; + use_xdamage = 0; + + use_solid_bg = 0; + overlay = 0; + overlay_cursor = 0; + + using_shm = 0; + single_copytile = 1; + + take_naps = 0; + measure_speeds = 0; + + show_cursor = 0; + show_multiple_cursors = 0; + cursor_shape_updates = 0; + if (! got_cursorpos) { + cursor_pos_updates = 0; + } + + if (! quiet) { + rfbLog("disabling: xfixes, xdamage, solid, overlay, shm,\n"); + rfbLog(" noonetile, nap, cursor, %scursorshape\n", + got_cursorpos ? "" : "cursorpos, " ); + rfbLog(" in -nofb mode.\n"); + } +} + /* * Presumably under -nofb the clients will never request the framebuffer. * However, we have gotten such a request... so let's just give them @@ -12136,18 +12380,13 @@ void set_visual(char *str) { * nearly always happens. */ void nofb_hook(rfbClientPtr cl) { - static int loaded_fb = 0; XImage *fb; - if (loaded_fb) { - return; - } rfbLog("framebuffer requested in -nofb mode by client %s\n", cl->host); /* ignore xrandr */ fb = XGetImage_wr(dpy, window, 0, 0, dpy_x, dpy_y, AllPlanes, ZPixmap); main_fb = fb->data; rfb_fb = main_fb; screen->frameBuffer = rfb_fb; - loaded_fb = 1; screen->displayHook = NULL; } @@ -12420,7 +12659,7 @@ XImage *initialize_xdisplay_fb(void) { } if (! quiet) { fprintf(stderr, " initialize_xdisplay_fb()\n"); - fprintf(stderr, " Visual*: 0x%p\n", vinfo->visual); + fprintf(stderr, " Visual*: %p\n", vinfo->visual); fprintf(stderr, " visualid: 0x%x\n", (int) vinfo->visualid); fprintf(stderr, " screen: %d\n", vinfo->screen); @@ -12731,8 +12970,7 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { /* * These are just hints wrt pixel format just to let * rfbGetScreen/rfbNewFramebuffer proceed with reasonable - * defaults. We manually set them in painful detail - * below. + * defaults. We manually set them in painful detail below. */ bits_per_color = guess_bits_per_color(fb->bits_per_pixel); @@ -12898,6 +13136,7 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { main_blue_shift = screen->serverFormat.blueShift; } +#if !SMALL_FOOTPRINT if (!quiet) { fprintf(stderr, "\n"); fprintf(stderr, "FrameBuffer Info:\n"); @@ -12954,7 +13193,6 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { fprintf(stderr, " bitmap_bit_order: %d\n", fb->bitmap_bit_order); break; } - fprintf(stderr, "\n"); } if (overlay && ! quiet) { rfbLog("\n"); @@ -12965,6 +13203,7 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { rfbLog("Xsun -su ... see Xserver(1), xinit(1) for more info.\n"); rfbLog("\n"); } +#endif /* nofb is for pointer/keyboard only handling. */ if (nofb) { @@ -12981,6 +13220,11 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { } } screen->frameBuffer = rfb_fb; + if (!quiet) { + fprintf(stderr, " main_fb: %p\n", main_fb); + fprintf(stderr, " rfb_fb: %p\n", rfb_fb); + fprintf(stderr, "\n"); + } bpp = screen->serverFormat.bitsPerPixel; depth = screen->serverFormat.depth; @@ -16006,7 +16250,7 @@ static void nap_set(int tile_cnt) { } nap_diff_count = 0; } - if (nap_ok && ! nap_in && using_xdamage) { + if (nap_ok && ! nap_in && use_xdamage) { if (XD_skip > 0.8 * XD_tot) { /* X DAMAGE is keeping load low, so skip nap */ nap_ok = 0; @@ -16237,7 +16481,7 @@ static int scan_display(int ystart, int rescan) { while (y < dpy_y) { - if (using_xdamage) { + if (use_xdamage) { XD_tot++; if (xdamage_hint_skip(y)) { XD_skip++; @@ -16364,7 +16608,7 @@ int scan_for_updates(int count_only) { /* check for changed colormap */ set_colormap(0); } - if (using_xdamage) { + if (use_xdamage) { collect_xdamage(scan_count); } } @@ -16555,7 +16799,7 @@ int scan_for_updates(int count_only) { } /* -- gui.c -- */ -#if OLD_TREE +#if OLD_TREE || SMALL_FOOTPRINT char gui_code[] = ""; #else #include "tkx11vnc.h" @@ -16877,8 +17121,6 @@ static void check_user_input2(double dt) { double quick_spin_fac = 0.40; double grind_spin_time = 0.175; - - dtime(&tm); g = g_in = got_pointer_input; if (!got_pointer_input) { @@ -16984,7 +17226,140 @@ static void check_user_input2(double dt) { } } -static void check_user_input3(double dt, double dtr, int tile_diffs) { +static void check_user_input3(double dt) { + + int eaten = 0, miss = 0, max_eat = 50; + int miss_max = 2; + int g, g_in; + double spin = 0.0, tm = 0.0; + double quick_spin_fac = 0.40, button_down_time = 0.050; + double grind_spin_time = 0.125; + + dtime(&tm); + g = g_in = got_pointer_input; + if (!got_pointer_input) { + return; + } + /* + * Try for some "quick" pointer input processing. + * + * About as fast as we can, we try to process user input calling + * rfbProcessEvents or rfbCheckFds. We do this for a time on + * order of the last scan_for_updates() time, dt, but if we stop + * getting user input we break out. We will also break out if + * we have processed max_eat inputs. + * + * Note that rfbCheckFds() does not send any framebuffer updates, + * so is more what we want here, although it is likely they have + * all be sent already. + */ + while (1) { + double spin_out; + int mcut = miss_max; + + if (show_multiple_cursors) { + rfbPE(screen, 1000); + } else { + rfbCFD(screen, 1000); + } + XFlush(dpy); + + + spin += dtime(&tm); + + spin_out = quick_spin_fac * dt; + if (button_mask && button_down_time > spin_out) { + spin_out = button_down_time; + } + + if (spin > spin_out) { + /* get out if spin time comparable to last scan time */ + break; + } + + if (got_pointer_input > g) { + g = got_pointer_input; + if (button_mask) { + miss = 0; + } + if (eaten++ < max_eat) { + continue; + } + } else { + miss++; + } + + if (button_mask) { + mcut = 4; + } + if (miss >= mcut) { + if (! button_mask || spin > button_down_time) { + break; + } + } + } + + + /* + * Probably grinding with a lot of fb I/O if dt is this large. + * (need to do this more elegantly) + * + * Current idea is to spin our wheels here *not* processing any + * fb I/O, but still processing the user input. This user input + * goes to the X display and changes it, but we don't poll it + * while we "rest" here for a time on order of dt, the previous + * scan_for_updates() time. We also break out if we miss enough + * user input. + */ + if (dt > grind_spin_time) { + int i, ms, split = 30; + double shim; + + /* + * Break up our pause into 'split' steps. We get at + * most one input per step. + */ + shim = 0.75 * dt / split; + + ms = (int) (1000 * shim); + + /* cutoff how long the pause can be */ + if (split * ms > 300) { + ms = 300 / split; + } + + spin = 0.0; + tm = 0.0; + dtime(&tm); + + g = got_pointer_input; + miss = 0; + for (i=0; i<split; i++) { + usleep(ms * 1000); + if (show_multiple_cursors) { + rfbPE(screen, 1000); + } else { + rfbCFD(screen, 1000); + } + spin += dtime(&tm); + if (got_pointer_input > g) { + XFlush(dpy); + miss = 0; + } else { + miss++; + } + g = got_pointer_input; + if (miss > 2) { + break; + } + if (1000 * spin > ms * split) { + break; + } + } + } +} + +static void check_user_input4(double dt, double dtr, int tile_diffs) { int allowed_misses, miss_tweak, i, g, g_in; int last_was_miss, consecutive_misses; @@ -16994,7 +17369,6 @@ static void check_user_input3(double dt, double dtr, int tile_diffs) { int gcnt, ginput; static int first = 1; - if (first) { char *p = getenv("SPIN"); if (p) { @@ -17110,6 +17484,10 @@ int fb_update_sent(int *count) { rfbClientIteratorPtr i; rfbClientPtr cl; + if (nofb) { + return 0; + } + i = rfbGetClientIterator(screen); while( (cl = rfbClientIteratorNext(i)) ) { sent += cl->framebufferUpdateMessagesSent; @@ -17125,7 +17503,7 @@ int fb_update_sent(int *count) { return rc; } -static void check_user_input4(double dt, double dtr, int tile_diffs) { +static void check_user_input5(double dt, double dtr, int tile_diffs) { int g, g_in, i, ginput, gcnt, tmp; int last_was_miss, consecutive_misses; @@ -17364,9 +17742,11 @@ static int check_user_input(double dt, double dtr, int tile_diffs, int *cnt) { if (pointer_mode == 2) { check_user_input2(dt); } else if (pointer_mode == 3) { - check_user_input3(dt, dtr, tile_diffs); + check_user_input3(dt); } else if (pointer_mode == 4) { check_user_input4(dt, dtr, tile_diffs); + } else if (pointer_mode == 5) { + check_user_input5(dt, dtr, tile_diffs); } return 0; } @@ -17749,15 +18129,10 @@ static void watch_loop(void) { continue; } - if (using_xdamage) { + if (use_xdamage) { check_xdamage_state(); } - if (watch_bell) { - /* n.b. assumes -nofb folks do not want bell... */ - check_bell_event(); - } - if (button_mask && (!show_dragging || pointer_mode == 0)) { /* * if any button is pressed do not update rfb @@ -17795,6 +18170,7 @@ static void watch_loop(void) { * text printed out under -help option */ static void print_help(int mode) { +#if !SMALL_FOOTPRINT char help[] = "\n" "x11vnc: allow VNC connections to real X11 displays. %s\n" @@ -17882,6 +18258,7 @@ static void print_help(int mode) { " also use \"TrueColor\", etc. see <X11/X.h> for a list.\n" " If the string ends in \":m\" then for better or for\n" " worse the visual depth is forced to be m.\n" +"\n" "-overlay Handle multiple depth visuals on one screen, e.g. 8+24\n" " and 24+8 overlay visuals (the 32 bits per pixel are\n" " packed with 8 for PseudoColor and 24 for TrueColor).\n" @@ -17919,7 +18296,7 @@ static void print_help(int mode) { " If \"fraction\" contains a decimal point \".\" it\n" " is taken as a floating point number, alternatively\n" " the notation \"m/n\" may be used to denote fractions\n" -" exactly, e.g. -scale 2/3.\n" +" exactly, e.g. -scale 2/3\n" "\n" " Scaling Options: can be added after \"fraction\" via\n" " \":\", to supply multiple \":\" options use commas.\n" @@ -17992,6 +18369,11 @@ static void print_help(int mode) { " vice versa) to avoid situations where no connections\n" " (or too many) are allowed.\n" "\n" +"-nolookup Do not use gethostbyname() or gethostbyaddr() to look up\n" +" host names or IP numbers. Use this if name resolution\n" +" is incorrectly set up and leads to long pauses as name\n" +" lookup times out, etc.\n" +"\n" "-input string Fine tuning of allowed user input. If \"string\" does\n" " not contain a comma \",\" the tuning applies only to\n" " normal clients. Otherwise the part before \",\" is\n" @@ -18019,6 +18401,7 @@ static void print_help(int mode) { "-storepasswd pass file Store password \"pass\" as the VNC password in the\n" " file \"file\". Once the password is stored the\n" " program exits. Use the password via \"-rfbauth file\"\n" +"\n" "-accept string Run a command (possibly to prompt the user at the\n" " X11 display) to decide whether an incoming client\n" " should be allowed to connect or not. \"string\" is\n" @@ -18232,6 +18615,7 @@ static void print_help(int mode) { " to the terminal. Same as \"-logfile file\". To append\n" " to the file use \"-oa file\" or \"-logappend file\".\n" "-rc filename Use \"filename\" instead of $HOME/.x11vncrc for rc file.\n" +"\n" "-norc Do not process any .x11vncrc file for options.\n" "-h, -help Print this help text.\n" "-?, -opts Only list the x11vnc options.\n" @@ -18492,19 +18876,24 @@ static void print_help(int mode) { " n=2 is an improved scheme: by watching the current rate\n" " of input events it tries to detect if it should try to\n" " \"eat\" additional pointer events before continuing.\n" +" This mode was the default until Apr 2005.\n" "\n" -" n=3 is basically a dynamic -nodragging mode: it detects\n" +" n=3 is basically the same as n=2 except with slightly\n" +" tweaked parameters. We made this a new one so one\n" +" could use -pm 2 for the old behavior.\n" +"\n" +" n=4 is basically a dynamic -nodragging mode: it detects\n" " when the mouse motion has paused and then refreshes\n" " the display.\n" "\n" -" n=4: attempts to measures network rates and latency,\n" +" n=5 attempts to measures network rates and latency,\n" " the video card read rate, and how many tiles have been\n" " changed on the screen. From this, it aggressively tries\n" " to push screen \"frames\" when it decides it has enough\n" " resources to do so. NOT FINISHED.\n" "\n" -" The default n is %d. Note that modes 2, 3, 4 will skip\n" -" -input_skip keyboard events (but it will not count\n" +" The default n is %d. Note that modes 2, 3, 4, 5 will\n" +" skip -input_skip keyboard events (but it will not count\n" " pointer events). Also note that these modes are not\n" " available in -threads mode which has its own pointer\n" " event handling mechanism.\n" @@ -18530,14 +18919,16 @@ static void print_help(int mode) { " e.g. \"-speeds ,100,15\", then the internal scheme is\n" " used to estimate the empty value(s).\n" "\n" +" Note: use this option is currently NOT FINISHED.\n" +"\n" " Typical PC video cards have read rates of 5-10 MB/sec.\n" " If the framebuffer is in main memory instead of video\n" " h/w (e.g. SunRay, shadowfb, Xvfb), the read rate may\n" " be much faster. \"x11perf -getimage500\" can be used\n" " to get a lower bound (remember to factor in the bytes\n" " per pixel). It is up to you to estimate the network\n" -" bandwith to clients. For the latency the ping(1)\n" -" command can be used.\n" +" bandwith and latency to clients. For the latency the\n" +" ping(1) command can be used.\n" "\n" " For convenience there are some aliases provided,\n" " e.g. \"-speeds modem\". The aliases are: \"modem\" for\n" @@ -18749,8 +19140,8 @@ static void print_help(int mode) { " same as \"close:host\". Use host\n" " \"all\" to close all current clients.\n" " If you know the client internal hex ID,\n" -" e.g. 0x3 (returned by -query clients and\n" -" RFB_CLIENT_ID), you can use that too.\n" +" e.g. 0x3 (returned by \"-query clients\"\n" +" and RFB_CLIENT_ID) you can use that too.\n" /* access */ " allowonce:host For the next connection only, allow\n" " connection from \"host\".\n" @@ -18763,6 +19154,8 @@ static void print_help(int mode) { " localhost enable -localhost mode\n" " nolocalhost disable -localhost mode\n" " listen:str set -listen to str, empty to disable.\n" +" nolookup enable -nolookup mode.\n" +" lookup disable -nolookup mode.\n" " input:str set -input to \"str\", empty to disable.\n" " client_input:str set the K, M, B -input on a per-client\n" " basis. select which client as for\n" @@ -18937,9 +19330,9 @@ static void print_help(int mode) { " nooverlay_nocursor nooverlay_cursor nooverlay_yescursor\n" " overlay_nocursor visual scale scale_cursor viewonly\n" " noviewonly shared noshared forever noforever once\n" -" timeout deny lock nodeny unlock connect allowonce\n" -" allow localhost nolocalhost listen accept gone\n" -" shm noshm flipbyteorder noflipbyteorder onetile\n" +" timeout deny lock nodeny unlock connect allowonce allow\n" +" localhost nolocalhost listen lookup nolookup accept\n" +" gone shm noshm flipbyteorder noflipbyteorder onetile\n" " noonetile solid_color solid nosolid blackout xinerama\n" " noxinerama xrandr noxrandr xrandr_mode padgeom quiet\n" " q noquiet modtweak nomodtweak xkb noxkb skip_keycodes\n" @@ -18975,10 +19368,10 @@ static void print_help(int mode) { "-sync By default -remote commands are run asynchronously, that\n" " is, the request is posted and the program immediately\n" " exits. Use -sync to have the program wait for an\n" -" acknowledgement from the x11vnc server that command\n" -" was processed. On the other hand -query requests are\n" -" always processed synchronously because they have wait\n" -" for the result.\n" +" acknowledgement from the x11vnc server that command was\n" +" processed (somehow). On the other hand -query requests\n" +" are always processed synchronously because they have\n" +" to wait for the result.\n" "\n" " Also note that if both -remote and -query requests are\n" " supplied on the command line, the -remote is processed\n" @@ -18994,19 +19387,21 @@ static void print_help(int mode) { "-noremote Do not process any remote control commands or queries.\n" "\n" " A note about security wrt remote control commands.\n" -" If someone can connect to the X display and change the\n" -" property VNC_CONNECT, then they can remotely control\n" -" x11vnc. Normally access to the X display is protected.\n" -" Note that if they can modify VNC_CONNECT, they could\n" -" also run their own x11vnc and have complete control\n" +" If someone can connect to the X display and change\n" +" the property VNC_CONNECT, then they can remotely\n" +" control x11vnc. Normally access to the X display is\n" +" protected. Note that if they can modify VNC_CONNECT\n" +" on the X server, they have enough permissions to also\n" +" run their own x11vnc and thus have complete control\n" " of the desktop. If the \"-connect /path/to/file\"\n" -" channel is being used, obviously anyone who can\n" -" write to /path/to/file can remotely control x11vnc.\n" -" So be sure to protect the X display and that file's\n" -" write permissions.\n" +" channel is being used, obviously anyone who can write\n" +" to /path/to/file can remotely control x11vnc. So be\n" +" sure to protect the X display and that file's write\n" +" permissions.\n" "\n" -" To disable the VNC_CONNECT property channel completely\n" -" use -novncconnect.\n" +" If you are paranoid and do not think -noremote is\n" +" enough, to disable the VNC_CONNECT property channel\n" +" completely use -novncconnect.\n" "\n" "-unsafe If x11vnc is running as root (e.g. inetd or Xsetup for\n" " a display manager) a few remote commands are disabled\n" @@ -19080,6 +19475,7 @@ static void print_help(int mode) { ); rfbUsage(); +#endif exit(1); } @@ -19436,7 +19832,6 @@ int main(int argc, char* argv[]) { int vpw_loc = -1; int dt = 0, bg = 0; int got_rfbwait = 0, got_deferupdate = 0, got_defer = 0; - int got_noxdamage = 0; /* used to pass args we do not know about to rfbGetScreen(): */ int argc_vnc = 1; char *argv_vnc[128]; @@ -19578,6 +19973,8 @@ int main(int argc, char* argv[]) { allow_list = strdup(argv[++i]); } else if (!strcmp(arg, "-localhost")) { allow_list = strdup("127.0.0.1"); + } else if (!strcmp(arg, "-nolookup")) { + host_lookup = 0; } else if (!strcmp(arg, "-input")) { CHECK_ARGC allowed_input_str = strdup(argv[++i]); @@ -19707,8 +20104,10 @@ int main(int argc, char* argv[]) { nofb = 1; } else if (!strcmp(arg, "-nobell")) { watch_bell = 0; + sound_bell = 0; } else if (!strcmp(arg, "-nosel")) { watch_selection = 0; + watch_primary = 0; } else if (!strcmp(arg, "-noprimary")) { watch_primary = 0; } else if (!strcmp(arg, "-cursor")) { @@ -19745,6 +20144,7 @@ int main(int argc, char* argv[]) { cursor_shape_updates = 0; } else if (!strcmp(arg, "-cursorpos")) { cursor_pos_updates = 1; + got_cursorpos = 1; } else if (!strcmp(arg, "-nocursorpos")) { cursor_pos_updates = 0; } else if (!strcmp(arg, "-xwarppointer")) { @@ -19769,6 +20169,7 @@ int main(int argc, char* argv[]) { pointer_mode_max, atoi(s)); } else { pointer_mode = atoi(s); + got_pointer_mode = pointer_mode; } } else if (!strcmp(arg, "-input_skip")) { CHECK_ARGC @@ -19798,9 +20199,7 @@ int main(int argc, char* argv[]) { CHECK_ARGC screen_blank = atoi(argv[++i]); } else if (!strcmp(arg, "-noxdamage")) { - using_xdamage = 0; - use_xdamage_hints = 0; - got_noxdamage = 1; + use_xdamage = 0; } else if (!strcmp(arg, "-xd_area")) { int tn; CHECK_ARGC @@ -20112,21 +20511,15 @@ int main(int argc, char* argv[]) { if (nofb) { /* disable things that do not make sense with no fb */ - using_shm = 0; - flash_cmap = 0; - show_cursor = 0; - show_multiple_cursors = 0; - overlay = 0; - overlay_cursor = 0; - if (! quiet) { - rfbLog("disabling -cursor, fb, shm, etc. in " - "-nofb mode.\n"); - } + set_nofb_params(); if (! got_deferupdate && ! got_defer) { /* reduce defer time under -nofb */ defer_update = defer_update_nofb; } + if (got_pointer_mode < 0) { + pointer_mode = POINTER_MODE_NOFB; + } } if (! got_deferupdate) { @@ -20259,7 +20652,7 @@ int main(int argc, char* argv[]) { fprintf(stderr, " waitms: %d\n", waitms); fprintf(stderr, " take_naps: %d\n", take_naps); fprintf(stderr, " sb: %d\n", screen_blank); - fprintf(stderr, " xdamage: %d\n", !got_noxdamage); + fprintf(stderr, " xdamage: %d\n", use_xdamage); fprintf(stderr, " xd_area: %d\n", xdamage_max_area); fprintf(stderr, " xd_mem: %.3f\n", xdamage_memory); fprintf(stderr, " sigpipe: %s\n", sigpipe @@ -20287,13 +20680,6 @@ int main(int argc, char* argv[]) { if (auth_file) { set_env("XAUTHORITY", auth_file); } - if (watch_bell || use_xkb_modtweak) { - /* we need XKEYBOARD for these: */ - use_xkb = 1; - } - if (xkbcompat) { - use_xkb = 0; - } #if LIBVNCSERVER_HAVE_XKEYBOARD /* * Disable XKEYBOARD before calling XOpenDisplay() @@ -20311,7 +20697,6 @@ int main(int argc, char* argv[]) { } } #else - use_xkb = 0; watch_bell = 0; use_xkb_modtweak = 0; #endif @@ -20387,11 +20772,15 @@ int main(int argc, char* argv[]) { rfbLog("Disabling XFIXES mode: display does not " "support it.\n"); } + xfixes_base_event_type = 0; xfixes_present = 0; } else { xfixes_present = 1; } #endif + if (! xfixes_present) { + use_xfixes = 0; + } #if LIBVNCSERVER_HAVE_LIBXDAMAGE if (! XDamageQueryExtension(dpy, &xdamage_base_event_type, &er)) { @@ -20399,12 +20788,16 @@ int main(int argc, char* argv[]) { rfbLog("Disabling X DAMAGE mode: display does not " "support it.\n"); } + xdamage_base_event_type = 0; xdamage_present = 0; } else { xdamage_present = 1; } #endif - if (! quiet && xdamage_present && ! got_noxdamage) { + if (! xdamage_present) { + use_xdamage = 0; + } + if (! quiet && xdamage_present && use_xdamage) { rfbLog("X DAMAGE available on display, using it for" " polling hints\n"); rfbLog(" to disable this behavior use: " @@ -20536,7 +20929,7 @@ int main(int argc, char* argv[]) { single_copytile_orig = single_copytile; /* check for MIT-SHM */ - if (! nofb && ! XShmQueryExtension_wr(dpy)) { + if (! XShmQueryExtension_wr(dpy)) { xshm_present = 0; if (! using_shm) { if (! quiet) { @@ -20565,11 +20958,9 @@ int main(int argc, char* argv[]) { #if LIBVNCSERVER_HAVE_XKEYBOARD /* check for XKEYBOARD */ - if (use_xkb) { - initialize_xkb(); - } + initialize_xkb(); initialize_watch_bell(); - if (!use_xkb && use_xkb_modtweak) { + if (!xkb_present && use_xkb_modtweak) { if (! quiet) { rfbLog("warning: disabling xkb modtweak." " XKEYBOARD ext. not present.\n"); @@ -20584,6 +20975,7 @@ int main(int argc, char* argv[]) { rfbLog("Disabling -xrandr mode: display does not" " support X RANDR.\n"); } + xrandr_base_event_type = 0; xrandr = 0; xrandr_present = 0; } else { |
