diff options
Diffstat (limited to 'x11vnc')
| -rw-r--r-- | x11vnc/ChangeLog | 4 | ||||
| -rw-r--r-- | x11vnc/README | 1434 | ||||
| -rw-r--r-- | x11vnc/help.c | 3 | ||||
| -rwxr-xr-x | x11vnc/misc/Xdummy | 334 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 5 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 2 | ||||
| -rw-r--r-- | x11vnc/x11vnc_defs.c | 2 |
7 files changed, 955 insertions, 829 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index e1cfed1..e42a180 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,7 @@ +2009-12-29 Karl Runge <runge@karlrunge.com> + * x11vnc: rename -create_x to -create_xsrv. Hopefully + done fixing Xdummy. + 2009-12-28 Karl Runge <runge@karlrunge.com> * x11vnc: Fix problems in --without-x builds. Fix crash with -QD query for dbus info. Adjust window size for diff --git a/x11vnc/README b/x11vnc/README index 359f034..38ff057 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -2,7 +2,7 @@ Copyright (C) 2002-2009 Karl J. Runge <runge@karlrunge.com> All rights reserved. -x11vnc README file Date: Mon Dec 28 00:07:34 EST 2009 +x11vnc README file Date: Tue Dec 29 18:50:35 EST 2009 The following information is taken from these URLs: @@ -918,9 +918,9 @@ make Here are some features that appeared in the 0.9.9 release: * The [123]-unixpw_system_greeter option, when used in combined - unixpw and XDMCP FINDCREATEDISPLAY mode (e.g. [124]-xdmsvc), - enables the user to press Escape to jump directly to the - XDM/GDM/KDM login greeter screen. This way the user avoids + unixpw and XDMCP FINDCREATEDISPLAY mode (for example: + [124]-xdmsvc), enables the user to press Escape to jump directly + to the XDM/GDM/KDM login greeter screen. This way the user avoids entering his unix password twice at X session creation time. Also, the unixpw login panel now has a short help displayed if the user presses 'F1'. @@ -2082,8 +2082,8 @@ http://www.karlrunge.com/x11vnc/faq.html: [64]Q-62: Can I have x11vnc allow a user to log in with her UNIX username and password and then have it find her X session display on - that machine and then connect to it? How about starting an X session - if one cannot be found? + that machine and then attach to it? How about starting an X session if + one cannot be found? [65]Q-63: Can I have x11vnc restart itself after it terminates? @@ -5229,7 +5229,7 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 Q-62: Can I have x11vnc allow a user to log in with her UNIX username and password and then have it find her X session display on that - machine and then connect to it? How about starting an X session if one + machine and then attach to it? How about starting an X session if one cannot be found? The easiest way to do this is via [418]inetd(8) using the [419]-unixpw @@ -5237,6 +5237,8 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 is that it starts a new x11vnc process for each new user connection. Otherwise a wrapper would have to listen for connections and spawn new x11vnc's (see [421]this example and also the [422]-loopbg option.) + inetd(8) is not required for this, but it makes some aspects more + general. Also with inetd(8) users always connect to a fixed VNC display, say hostname:0, and do not need to memorize a special VNC display number @@ -5244,58 +5246,57 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 Update: Use the [423]-find, [424]-create, [425]-svc, and [426]-xdmsvc options that are shorthand for common FINDCREATEDISPLAY usage modes - (e.g. terminal services) described below. (i.e. just use "-svc" - instead of "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb -unixpw -users - unixpw= -ssl SAVE") + (e.g. terminal services) described below. (i.e. simply use "-svc" + instead of the cumbersome "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb + -unixpw -users unixpw= -ssl SAVE") The [427]-display WAIT option makes x11vnc wait until a VNC viewer is - connected before attaching to the X display. Additionally it can be - used to run an external command that returns the DISPLAY and - XAUTHORITY data. We provide some useful builtin ones (FINDDISPLAY and - FINDCREATEDISPLAY below), but in principle one could supply "-display - WAIT:cmd=/path/to/find_display" where the script find_display might - look something like [428]this. + connected before attaching to the X display. + + Additionally it can be used to run an external command that returns + the DISPLAY and XAUTHORITY data. We provide some useful builtin ones + (FINDDISPLAY and FINDCREATEDISPLAY below), but in principle one could + supply his own script: "-display WAIT:cmd=/path/to/find_display" where + the script find_display might look something like [428]this. A default script somewhat like the above is used under "-display - WAIT:cmd=FINDDISPLAY" (same as [429]-find) (use - "WAIT:cmd=FINDDISPLAY-print" to print out the gnarly script.) The - format for any such command is that it returns DISPLAY=:disp as the - first line and any remaining lines are either XAUTHORITY=file or raw - xauth data (the above example does the latter.) If applicable (-unixpw - mode), the program is run as the Unix user name who logged in. + WAIT:cmd=FINDDISPLAY" (same as [429]-find) The format for any such + command is that it returns DISPLAY=:disp as the first line and any + remaining lines are either XAUTHORITY=file or raw xauth data (the + above example does the latter.) If applicable (-unixpw mode), the + program is run as the Unix user name who logged in. On Linux if the virtual terminal is known the program appends ",VT=n" to the DISPLAY line; a chvt n will be attempted automatically. Or if - only X server process ID is known it appends ",XPID=n" (a chvt will be - attempted by x11vnc.) + only the X server process ID is known it appends ",XPID=n" (a chvt + will be attempted by x11vnc.) Tip: Note that the [430]-find option is an alias for "-display WAIT:cmd=FINDDISPLAY". Use it! The [431]-unixpw option allows [432]UNIX password logins. It conveniently knows the Unix username whose X display should be found. - Here are a couple /etc/inetd.conf examples for this: + Here are a couple /etc/inetd.conf examples of this usage: 5900 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd -unixpw \ - -display WAIT:cmd=FINDDISPLAY -o /var/log/x11vnc.log -ssl SAVE -ssldir /u -sr/local/certs + -find -o /var/log/x11vnc.log -ssl SAVE -ssldir /usr/local/certs 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd -unixpw \ - -display WAIT:cmd=FINDDISPLAY -o /var/log/x11vnc.log -ssl SAVE -users uni -xpw= + -find -o /var/log/x11vnc.log -ssl SAVE -users unixpw= - Note the very long lines have been split. An alternative is to use a - wrapper script, e.g. /usr/local/bin/x11vnc.sh that has all of the - options. (see also the [433]-svc alias.) + Note we have used the [433]-find alias and the very long lines have + been split. An alternative is to use a wrapper script, e.g. + /usr/local/bin/x11vnc.sh that has all of the options. (see also the + [434]-svc alias.) - In the first one x11vnc is run as user "nobody" and stays user nobody - during the whole session. The permissions of the log files and certs - directory will need to be set up to allow "nobody" to use them. + In the first inetd line x11vnc is run as user "nobody" and stays user + nobody during the whole session. The permissions of the log files and + certs directory will need to be set up to allow "nobody" to use them. In the second one x11vnc is run as root and switches to the user that - logs in due to the "[434]-users unixpw=" option. + logs in due to the "[435]-users unixpw=" option. - Note that [435]SSL is required for this mode because otherwise the + Note that [436]SSL is required for this mode because otherwise the Unix password would be passed in clear text over the network. In general -unixpw is not required for this sort of scheme, but it is convenient because it determines exactly who the Unix user is whose @@ -5303,61 +5304,79 @@ xpw= to use some method to work out DISPLAY, XAUTHORITY, etc (perhaps you use multiple inetd ports and hardwire usernames for different ports.) - If you really want to disable the SSL or SSH [436]-localhost + If you really want to disable the SSL or SSH [437]-localhost constraints (this is not recommended unless you really know what you are doing: Unix passwords sent in clear text is a very bad idea...) - read the [437]-unixpw documentation. + read the [438]-unixpw documentation. A inetd(8) scheme for a fixed user that doesn't use SSL or unix passwds could be: -/usr/local/bin/x11vnc -inetd -users =fred -find -rfbauth /home/fred/.vnc/passwd - -o /var/log/x11vnc.log + /usr/local/bin/x11vnc -inetd -users =fred -find -rfbauth /home/fred/.vnc/pass +wd -o /var/log/x11vnc.log + + The "[439]-users =fred" option will cause x11vnc to switch to user + fred and then find his X display. The VNC password (-rfbauth) as + opposed to Unix password (-unixpw) is used to authenticate the VNC + client. - The "[438]-users =fred" option will cause x11vnc to switch to user - fred and then find his X display. + Similar looking commands to the above examples can be run directly and + do not use inetd (just remove the -inetd option and run from the + cmdline, etc.) - A recently (Nov/2006) added extension to FINDDISPLAY is - FINDCREATEDISPLAY where if it does not find a display via the + X Session Creation: An added (Nov/2006) extension to FINDDISPLAY is + FINDCREATEDISPLAY where if it does not find an X display via the FINDDISPLAY method it will create an X server session for the user (i.e. desktop/terminal server.) This is the only time x11vnc actually - tries to start up an X server. By default it will only try to start up - virtual (non-hardware) X servers: first [439]Xvfb and if that is not - available then Xdummy. Note that Xdummy only works on Linux whereas - Xvfb works just about everywhere (and in some situations Xdummy must - be run as root.) An advantage of Xdummy over Xvfb is that Xdummy - supports RANDR dynamic screen resizing. + tries to start up an X server (normally it just attaches to an + existing one.) + + By default it will only try to start up virtual (non-hardware) X + servers: first [440]Xvfb and if that is not available then Xdummy + (included in the x11vnc source code.) Note that Xdummy only works on + Linux whereas Xvfb works just about everywhere (and in some situations + Xdummy must be run as root.) An advantage of Xdummy over Xvfb is that + Xdummy supports RANDR dynamic screen resizing, which can be handy if + the user accesses the desktop from different sized screens (e.g. + workstation and laptop.) So an inetd(8) example might look like: 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd \ -o /var/log/x11vnc.log -http -prog /usr/local/bin/x11vnc \ -ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY - Where the very long lines have been split. This will allow direct SSL - (e.g. [440]ss_vncviewer) access and also Java Web browers access via: + Where the very long lines have been split. See below where that long + and cumbersome last line is replaced by the [441]-svc alias. + + The above mode will allow direct SSL (e.g. [442]ss_vncviewer or + [443]SSVNC) access and also Java Web browers access via: https://hostname:5900/. - Tip: Note that the [441]-create option is an alias for "-display + Tip: Note that the [444]-create option is an alias for "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb". - Tip: Note that [442]-svc is a short hand for the long "-ssl SAVE + Tip: Note that [445]-svc is a short hand for the long "-ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY" part. Unlike -create, this alias also sets up SSL encryption and Unix - password login. The above example then simplifies to: + password login. + + The above inetd example then simplifies to: 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd \ - -o /var/log/x11vnc.log -http -prog /usr/local/bin/x11vnc -svc + -o /var/log/x11vnc.log -http -prog /usr/local/bin/x11vnc \ + -svc - Tip: In addition to the usual unixpw parameters, the user can specify - after his username (following a ":" see [443]-display WAIT for - details) for FINDCREATEDISPLAY they can add "geom=WxH" or "geom=WxHxD" - to specify the width, height, and optionally the color depth. E.g. - "fred:geom=800x600" at the login: prompt. Also if the env. var - X11VNC_CREATE_GEOM is set to the desired WxH or WxHxD that will be - used by x11vnc. + Tip: In addition to the usual unixpw parameters, inside the VNC viewer + the user can specify after his username (following a ":" see + [446]-display WAIT for details) for FINDCREATEDISPLAY they can add + "geom=WxH" or "geom=WxHxD" to specify the width, height, and + optionally the color depth. E.g. "fred:geom=800x600" at the login: + prompt. Also if the env. var X11VNC_CREATE_GEOM is set to the desired + WxH or WxHxD that will be used by x11vnc. You can set the env. var X11VNC_SKIP_DISPLAY to a comma separated list of displays to ignore in the FINDDISPLAY process (to force creation of - new displays in some cases.) + new displays in some cases.) The user logging in via the vncviewer can + also set this via username:nodisplay=...) If you do not plan on using the Java Web browser applet you can remove the -http (and -prog) option since this will speed up logging-in by a @@ -5375,28 +5394,26 @@ service x11vnc user = root server = /usr/local/bin/x11vnc server_args = -inetd -o /var/log/x11vnc.log -http -prog /usr/local/ -bin/x11vnc -ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY +bin/x11vnc -svc disable = no } - Or more simply the server_args becomes: - server_args = -inetd -o /var/log/x11vnc.log -http -prog /usr/local/ -bin/x11vnc -svc - To print out the script in this case use "-display WAIT:cmd=FINDCREATEDISPLAY-print". To change the preference of Xservers and which to try list them, e.g.: "-display - WAIT:cmd=FINDCREATEDISPLAY-X,Xvfb,Xdummy". The "X" one means to try to - start up a real, hardware X server, e.g. startx(1) (if there is - already a real X server running this may only work on Linux and the - chvt program may [444]need to be run to switch to the correct Linux - virtual terminal.) x11vnc will try to run chvt automatically if it can - determine which VT should be switched to. - - If you want to present the user with a xdm/gdm/kdm display manager - login you can use Xvfb.xdmcp instead of Xvfb, etc in the above list. - However, you need to configure xdm/gdm/kdm to accept localhost XDMCP - messages, this can be done by (from -help output): + WAIT:cmd=FINDCREATEDISPLAY-X,Xvfb,Xdummy" or use "[447]-create_xsrv + X,Xvfb,Xdummy". The "X" one means to try to start up a real, hardware + X server, e.g. startx(1) (if there is already a real X server running + this may only work on Linux and the chvt program may [448]need to be + run to switch to the correct Linux virtual terminal.) x11vnc will try + to run chvt automatically if it can determine which VT should be + switched to. + + XDM/GDM/KDM Login Greeter Panel: If you want to present the user with + a xdm/gdm/kdm display manager "greeter" login you can use Xvfb.xdmcp + instead of Xvfb, etc in the above list. However, you need to configure + xdm/gdm/kdm to accept localhost XDMCP messages, this can be done by + (from -help output): If you want the FINDCREATEDISPLAY session to contact an XDMCP login manager (xdm/gdm/kdm) on the same machine, then use "Xvfb.xdmcp" instead of "Xvfb", etc. The user will have to supply his username @@ -5416,9 +5433,9 @@ bin/x11vnc -svc will also typically block UDP (port 177 for XDMCP) by default effectively limiting the UDP connections to localhost. - Tip: Note that [445]-xdmsvc is a short hand for the long "-ssl SAVE - -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp" - part. E.g.: + Tip: Note that [449]-xdmsvc is a short hand alias for the long "-ssl + SAVE -unixpw -users unixpw= -display + WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp". So we simply use: service x11vnc { type = UNLISTED @@ -5432,12 +5449,13 @@ service x11vnc disable = no } - (or "-svc" instead of "-xdmsvc" for no XDMCP.) + (Note: use "-svc" instead of "-xdmsvc" for no XDMCP login greeter.) - Local access: To access your virtual X display locally (i.e. while - sitting at the same machine it is running on) one can perhaps have - something like this in their $HOME/.xinitrc + Local access (VNC Server and VNC Viewer on the same machine): To + access your virtual X display session locally (i.e. while sitting at + the same machine it is running on) one can perhaps have something like + this in their $HOME/.xinitrc #!/bin/sh x11vnc -create -rfbport 5905 -env WAITBG=1 vncviewer -geometry +0+0 -encodings raw -passwd $HOME/.vnc/passwd localhost:5 @@ -5468,30 +5486,31 @@ t:5 _________________________________________________________________ Summary: The "-display WAIT:cmd=FINDCREATEDISPLAY" scheme can be used - to provide a "desktop service" (i.e. terminal service) on the machine: - you always get some desktop there, either a real hardware X server or - a virtual one (depending on how you set things up.) So it provides - simple "terminal services" based on Unix username and password. The - created X server sessions (virtual or real hardware) will remain - running after you disconnect the VNC viewer and will be found again on - reconnecting via VNC and logging in. To terminate them use the normal - way to Exit/LogOut from inside your X session. The user does not have - to memorize which VNC display number is his. They all go the same one - (e.g. :0) and it switches based on username. + to provide a "desktop service" (i.e. terminal service) on the server + machine: you always get some desktop there, either a real hardware X + server or a virtual one (depending on how you set things up.) + + So it provides simple "terminal services" based on Unix username and + password. The created X server sessions (virtual or real hardware) + will remain running after you disconnect the VNC viewer and will be + found again on reconnecting via VNC and logging in. To terminate them + use the normal way to Exit/LogOut from inside your X session. The user + does not have to memorize which VNC display number is his. They all go + the same one (e.g. hostname:0) and it switches based on username. Q-63: Can I have x11vnc restart itself after it terminates? One could do this in a shell script, but now there is an option - [446]-loop that makes it easier. Of course when x11vnc restarts it + [450]-loop that makes it easier. Of course when x11vnc restarts it needs to have permissions to connect to the (potentially new) X display. This mode could be useful if the X server restarts often. Use e.g. "-loop5000" to sleep 5000 ms between restarts. Also "-loop2000,5" to sleep 2000 ms and only restart 5 times. - One can also use the [447]-loopbg to emulate inetd(8) to some degree, + One can also use the [451]-loopbg to emulate inetd(8) to some degree, where each connected process runs in the background. It could be - combined, say, with the [448]-svc option to provide simple terminal + combined, say, with the [452]-svc option to provide simple terminal services without using inetd(8). @@ -5499,7 +5518,7 @@ t:5 web browser? To have x11vnc serve up a Java VNC viewer applet to any web browsers - that connect to it, run x11vnc with this [449]option: + that connect to it, run x11vnc with this [453]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -5518,7 +5537,7 @@ t:5 then you can connect to that URL with any Java enabled browser. Feel free to customize the default index.vnc file in the classes directory. - As of May/2005 the [450]-http option will try to guess where the Java + As of May/2005 the [454]-http option will try to guess where the Java classes jar file is by looking in expected locations and ones relative to the x11vnc binary. @@ -5527,7 +5546,7 @@ t:5 either the java or appletviewer commands to run the program. java -cp ./VncViewer.jar VncViewer HOST far-away.east PORT 5900 - Proxies: See the [451]discussion here if the web browser must use a + Proxies: See the [455]discussion here if the web browser must use a web proxy to connect to the internet. It is tricky to get Java applets to work in this case: a signed applet must be used so it can connect to the proxy and ask for the redirection to the VNC server. One way to @@ -5543,7 +5562,7 @@ t:5 As of Mar/2004 x11vnc supports reverse connections. On Unix one starts the VNC viewer in listen mode: "vncviewer -listen" (see your documentation for Windows, etc), and then starts up x11vnc with the - [452]-connect option. To connect immediately at x11vnc startup time + [456]-connect option. To connect immediately at x11vnc startup time use the "-connect host:port" option (use commas for a list of hosts to connect to.) The ":port" is optional (default is VNC listening port is 5500.) @@ -5552,11 +5571,11 @@ t:5 file is checked periodically (about once a second) for new hosts to connect to. - The [453]-remote control option (aka -R) can also be used to do this + The [457]-remote control option (aka -R) can also be used to do this during an active x11vnc session, e.g.: x11vnc -display :0 -R connect:hostname.domain - Use the "[454]-connect_or_exit" option to have x11vnc exit if the + Use the "[458]-connect_or_exit" option to have x11vnc exit if the reverse connection fails. Also, note the "-rfbport 0" option disables TCP listening for connections (potentially useful for reverse connection mode, assuming you do not want any "forward" connections.) @@ -5569,7 +5588,7 @@ x11vnc -display :0 -R connect:hostname.domain X11VNC_REVERSE_CONNECTION_NO_AUTH=1" to x11vnc. Vncconnect command: To use the vncconnect(1) program (from the core - VNC package at www.realvnc.com) specify the [455]-vncconnect option to + VNC package at www.realvnc.com) specify the [459]-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 @@ -5588,7 +5607,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" proxy or SSH? Yes, as of Oct/2007 x11vnc supports reverse connections through - proxies: use the "[456]-proxy host:port" option. The default is to + proxies: use the "[460]-proxy host:port" option. The default is to assume the proxy is a Web proxy. Note that most Web proxies only allow proxy destination connections to ports 443 (HTTPS) and 563 (SNEWS) and so this might not be too useful unless the proxy has been modified @@ -5608,11 +5627,11 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" connections. An experimental mode is "-proxy http://host:port/..." where the URL - (e.g. a CGI script) is retrieved via the GET method. See [457]-proxy + (e.g. a CGI script) is retrieved via the GET method. See [461]-proxy for more info. Another experimental mode is "-proxy ssh://user@host" in which case a - SSH tunnel is used for the proxying. See [458]-proxy for more info. + SSH tunnel is used for the proxying. See [462]-proxy for more info. Up to 3 proxies may be chained together by listing them by commas e.g.: "-proxy http://host1:port1,socks5://host2:port2" in case one @@ -5635,10 +5654,10 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" Driver in XFree86/Xorg (see below.) In either case, one can view this desktop both remotely and also - [459]locally using vncviewer. Make sure vncviewer's "-encodings raw" + [463]locally using vncviewer. Make sure vncviewer's "-encodings raw" is in effect for local viewing (compression seems to slow things down locally.) For local viewing you set up a "bare" window manager that - just starts up vncviewer and nothing else ([460]See how below.) + just starts up vncviewer and nothing else ([464]See how below.) Here is one way to start up Xvfb: xinit -- /usr/X11R6/bin/Xvfb :1 -cc 4 -screen 0 1024x768x16 @@ -5658,19 +5677,19 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" "screen scrape" it very efficiently (more than, say, 100X faster than normal video hardware.) - Update Nov/2006: See the [461]FINDCREATEDISPLAY discussion of the - "[462]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or + Update Nov/2006: See the [465]FINDCREATEDISPLAY discussion of the + "[466]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or Xdummy, or even real ones by changing an option) X servers are started automatically for new users connecting. This provides a "desktop service" for the machine. You either get your real X session or your virtual (Xvfb/Xdummy) one whenever you connect to the machine - (inetd(8) is a nice way to provide this service.) The [463]-find, - [464]-create, [465]-svc, and [466]-xdmsvc aliases can also come in + (inetd(8) is a nice way to provide this service.) The [467]-find, + [468]-create, [469]-svc, and [470]-xdmsvc aliases can also come in handy here. There are some annoyances WRT Xvfb however. The default keyboard mapping seems to be very poor. One should run x11vnc with - [467]-add_keysyms option to have keysyms added automatically. Also, to + [471]-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" @@ -5682,7 +5701,7 @@ xmodmap -e "keycode any = Alt_R" xmodmap -e "keycode any = Meta_L" xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L" - (note: these are applied automatically in the [468]FINDCREATEDISPLAY + (note: these are applied automatically in the [472]FINDCREATEDISPLAY mode of x11vnc.) Perhaps the Xvfb options -xkbdb or -xkbmap could be used to get a better default keyboard mapping... @@ -5697,11 +5716,11 @@ xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L" The main drawback to this method (besides requiring extra configuration and possibly root permission) is that it also does the - Linux Virtual Console/Terminal (VC/VT) [469]switching even though it + Linux Virtual Console/Terminal (VC/VT) [473]switching even though it does not need to (since it doesn't use a real framebuffer.) There are some "dual headed" (actually multi-headed/multi-user) patches to the X server that turn off the VT usage in the X server. Update: As of - Jul/2005 we have an LD_PRELOAD script [470]Xdummy that allows you to + Jul/2005 we have an LD_PRELOAD script [474]Xdummy that allows you to use a stock (i.e. unpatched) Xorg or XFree86 server with the "dummy" driver and not have any VT switching problems! An advantage of Xdummy over Xvfb is that Xdummy supports RANDR dynamic screen resizing. @@ -5719,16 +5738,16 @@ startx -- /path/to/Xdummy :1 other virtual X sessions, say Xnest or even Xvnc itself (useful for testing x11vnc.) - Local access: You use a VNC viewer to access the display remotely; to - access your virtual X display locally (i.e. while sitting at the same - machine it is running on) one can perhaps have something like this in - their $HOME/.xinitrc + Local access (VNC Server and VNC Viewer on the same machine): You use + a VNC viewer to access the display remotely; to access your virtual X + display locally (i.e. while sitting at the same machine it is running + on) one can perhaps have something like this in their $HOME/.xinitrc #!/bin/sh x11vnc -display :5 -rfbport 5905 -bg vncviewer -geometry +0+0 -encodings raw -passwd $HOME/.vnc/passwd localhost:5 The display numbers (VNC and X) will likely be different (you could - also try [471]-find), and you may not need the -passwd. Recent RealVNC + also try [475]-find), and you may not need the -passwd. Recent RealVNC viewers might be this: #!/bin/sh x11vnc -display :5 -rfbport 5905 -bg @@ -5743,8 +5762,10 @@ t:5 and configuration. - For the general replacement of Xvnc by Xvfb+x11vnc, one user describes - a similar setup he created [472]here. + XDM/GDM/KDM One-Shot X sessions: For the general replacement of Xvnc + by Xvfb+x11vnc, one user describes a similar setup he created where + the X sessions are one-shot's (destroyed after the vncviewer + disconnects) and it uses the XDM/GDM/KDM login greeter [476]here. Q-68: How can I use x11vnc on "headless" machines? Why might I want @@ -5759,7 +5780,7 @@ t:5 An X server can be started on the headless machine (sometimes this requires configuring the X server to not fail if it cannot detect a keyboard or mouse, see the next paragraph.) Then you can export that X - display via x11vnc (e.g. see [473]this FAQ) and access it from + display via x11vnc (e.g. see [477]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 @@ -5783,10 +5804,10 @@ t:5 cards as it can hold to provide multiple simultaneous access or testing on different kinds of video hardware. - See also the [474]FINDCREATEDISPLAY discussion of the "[475]-display + See also the [478]FINDCREATEDISPLAY discussion of the "[479]-display WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X servers are started automatically for new users connecting. The - [476]-find, [477]-create, [478]-svc, and [479]-xdmsvc aliases can also + [480]-find, [481]-create, [482]-svc, and [483]-xdmsvc aliases can also come in handy here. [Resource Usage and Performance] @@ -5809,7 +5830,7 @@ t:5 19/03/2004 10:10:58 error creating tile-row shm for len=4 19/03/2004 10:10:58 reverting to single_copytile mode - Here is a shell script [480]shm_clear to list and prompt for removal + Here is a shell script [484]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, @@ -5843,44 +5864,44 @@ ied) in /etc/system. See the next paragraph for more workarounds. To minimize the number of shm segments used by x11vnc try using the - [481]-onetile option (corresponds to only 3 shm segments used, and + [485]-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 - [482]-noshm option. Performance will be somewhat degraded but when + [486]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [483]earlier question discussing -noshm.) + [487]earlier question discussing -noshm.) Q-70: How can I make x11vnc use less system resources? - The [484]-nap (now on by default; use -nonap to disable) and - "[485]-wait n" (where n is the sleep between polls in milliseconds, + The [488]-nap (now on by default; use -nonap to disable) and + "[489]-wait n" (where n is the sleep between polls in milliseconds, the default is 30 or so) option are good places to start. In addition, - something like "[486]-sb 15" will cause x11vnc to go into a deep-sleep + something like "[490]-sb 15" will cause x11vnc to go into a deep-sleep mode after 15 seconds of no activity (instead of the default 60.) Reducing the X server bits per pixel depth (e.g. to 16bpp or even 8bpp) will further decrease memory I/O and network I/O. The ShadowFB X server setting will make x11vnc's screen polling less severe. Using - the [487]-onetile option will use less memory and use fewer shared - memory slots (add [488]-fs 1.0 for one less slot.) + the [491]-onetile option will use less memory and use fewer shared + memory slots (add [492]-fs 1.0 for one less slot.) Q-71: How can I make x11vnc use MORE system resources? - You can try [489]-threads (note this mode can be unstable and/or + You can try [493]-threads (note this mode can be unstable and/or crash; and as of May/2008 is strongly discouraged, see the option description) or dial down the wait time (e.g. -wait 1) and possibly - dial down [490]-defer as well. Note that if you try to increase the + dial down [494]-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 [491]-id option) can be streamed over a LAN or wireless at + the x11vnc [495]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. If the graphics card's framebuffer read rate - is [492]faster than normal then the video window size and frame rate - can be much higher. The use of [493]TurboVNC and/or TurboJPEG can make + is [496]faster than normal then the video window size and frame rate + can be much higher. The use of [497]TurboVNC and/or TurboJPEG can make the frame rate somewhat higher still (but most of this hinges on the graphics card's read rate.) @@ -5897,7 +5918,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 - [494]-solid [color] option to try to do this automatically. + [498]-solid [color] option to try to do this automatically. * Configure your window manager or desktop "theme" to not use fancy images, shading, and gradients for the window decorations, etc. Disable window animations, etc. Maybe your desktop has a "low @@ -5906,9 +5927,9 @@ ied) -> Use Smooth Scrolling (deselect it.) * Avoid small scrolls of large windows using the Arrow keys or scrollbar. Try to use PageUp/PageDown instead. (not so much of a - problem in x11vnc 0.7.2 if [495]-scrollcopyrect is active and + problem in x11vnc 0.7.2 if [499]-scrollcopyrect is active and detecting scrolls for the application.) - * If the [496]-wireframe option is not available (earlier than + * If the [500]-wireframe option is not available (earlier than x11vnc 0.7.2 or you have disabled it via -nowireframe) then Disable Opaque Moves and Resizes in the window manager/desktop. * However if -wireframe is active (on by default in x11vnc 0.7.2) @@ -5931,7 +5952,7 @@ ied) noticed. VNC viewer parameters: - * Use a [497]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer + * Use a [501]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer with ZRLE encoding is not too bad either; some claim it is faster.) * Make sure the tight (or zrle) encoding is being used (look at @@ -5939,7 +5960,7 @@ ied) * Request 8 bits per pixel using -bgr233 (up to 4X speedup over depth 24 TrueColor (32bpp), but colors will be off) * RealVNC 4.x viewer has some extremely low color modes (only 64 and - even 8 colors.) [498]SSVNC does too. The colors are poor, but it + even 8 colors.) [502]SSVNC does too. The colors are poor, but it is usually noticeably faster than bgr233 (256 colors.) * Try increasing the TightVNC -compresslevel (compresses more on server side before sending, but uses more CPU) @@ -5953,39 +5974,39 @@ ied) file. x11vnc parameters: - * Make sure the [499]-wireframe option is active (it should be on by + * Make sure the [503]-wireframe option is active (it should be on by default) and you have Opaque Moves/Resizes Enabled in the window manager. - * Make sure the [500]-scrollcopyrect option is active (it should be + * Make sure the [504]-scrollcopyrect option is active (it should be on by default.) This detects scrolls in many (but not all) applications an applies the CopyRect encoding for a big speedup. * Enforce a solid background when VNC viewers are connected via - [501]-solid - * Try x11vnc's client-side caching [502]client-side caching scheme: - [503]-ncache - * Specify [504]-speeds modem to force the wireframe and + [505]-solid + * Try x11vnc's client-side caching [506]client-side caching scheme: + [507]-ncache + * Specify [508]-speeds modem to force the wireframe and scrollcopyrect heuristic parameters (and any future ones) to those of a dialup modem connection (or supply the rd,bw,lat numerical values that characterize your link.) * If wireframe and scrollcopyrect aren't working, try using the more - drastic [505]-nodragging (no screen updates when dragging mouse, + drastic [509]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Set [506]-fs 1.0 (disables fullscreen updates) - * Try increasing [507]-wait or [508]-defer (reduces the maximum + * Set [510]-fs 1.0 (disables fullscreen updates) + * Try increasing [511]-wait or [512]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * Try the [509]-progressive pixelheight mode with the block + * Try the [513]-progressive pixelheight mode with the block pixelheight 100 or so (delays sending vertical blocks since they may change while viewer is receiving earlier ones) - * If you just want to watch one (simple) window use [510]-id or - [511]-appshare (cuts down extraneous polling and updates, but can + * If you just want to watch one (simple) window use [514]-id or + [515]-appshare (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [512]-nosel (disables all clipboard selection exchange) - * Use [513]-nocursor and [514]-nocursorpos (repainting the remote + * Set [516]-nosel (disables all clipboard selection exchange) + * Use [517]-nocursor and [518]-nocursorpos (repainting the remote cursor position and shape takes resources and round trips) * On very slow links (e.g. <= 28.8) you may need to increase the - [515]-readtimeout n setting if it sometimes takes more than 20sec + [519]-readtimeout n setting if it sometimes takes more than 20sec to paint the full screen, etc. - * Do not use [516]-fixscreen to automatically refresh the whole + * Do not use [520]-fixscreen to automatically refresh the whole screen, tap three Alt_L's then the screen has painting errors (rare problem.) @@ -6054,7 +6075,7 @@ ied) Note that the DAMAGE extension does not speed up the actual reading of pixels from the video card framebuffer memory, by, say, mirroring them - in main memory. So reading the fb is still painfully [517]slow (e.g. + in main memory. So reading the fb is still painfully [521]slow (e.g. 5MB/sec), and so even using X DAMAGE when large changes occur on the screen the bulk of the time is still spent retrieving them. Not ideal, but use of the ShadowFB XFree86/Xorg option speeds up the reading @@ -6072,45 +6093,45 @@ ied) DAMAGE rectangles to contain real damage. The larger rectangles are only used as hints to focus the traditional scanline polling (i.e. if a scanline doesn't intersect a recent DAMAGE rectangle, the scan is - skipped.) You can use the "[518]-xd_area A" option to adjust the size + skipped.) You can use the "[522]-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 "[519]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[520]-noxdamage". + The option "[523]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[524]-noxdamage". Q-74: My OpenGL application shows no screen updates unless I supply the -noxdamage option to x11vnc. One user reports in his environment (MythTV using the NVIDIA OpenGL drivers) he gets no updates after the initial screen is drawn unless - he uses the "[521]-noxdamage" option. + he uses the "[525]-noxdamage" option. This seems to be a bug in the X DAMAGE implementation of that driver. You may have to use -noxdamage as well. A way to autodetect this will be tried, probably the best it will do is automatically stop using X DAMAGE. - A developer for [522]MiniMyth reports that the 'alphapulse' tag of the + A developer for [526]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. - Update: see [523]this FAQ too. + Update: see [527]this FAQ too. Q-75: When I drag windows around with the mouse or scroll up and down things really bog down (unless I do the drag in a single, quick motion.) Is there anything to do to improve things? - This problem is primarily due to [524]slow hardware read rates from + This problem is primarily due to [528]slow hardware read rates from video cards: as you scroll or move a large window around the screen changes are much too rapid for x11vnc to keep up them (it can usually only read the video card at about 5-10 MB/sec, so it can take a good fraction of a second to read the changes induce from moving a large window, if this to be done a number of times in succession the window or scroll appears to "lurch" forward.) See the description in the - [525]-pointer_mode option for more info. The next bottleneck is + [529]-pointer_mode option for more info. The next bottleneck is compressing all of these changes and sending them out to connected viewers, however the VNC protocol is pretty much self-adapting with respect to that (updates are only packaged and sent when viewers ask @@ -6120,27 +6141,27 @@ ied) default should now be much better than before and dragging small windows around should no longer be a huge pain. If for some reason these changes make matters worse, you can go back to the old way via - the "[526]-pointer_mode 1" option. + the "[530]-pointer_mode 1" option. - Also added was the [527]-nodragging option that disables all screen + Also added was the [531]-nodragging option that disables all screen updates while dragging with the mouse (i.e. mouse motion with a button held down.) This gives the snappiest response, but might be undesired in some circumstances when you want to see the visual feedback while dragging (e.g. menu traversal or text selection.) - As of Dec/2004 the [528]-pointer_mode n option was introduced. n=1 is + As of Dec/2004 the [532]-pointer_mode n option was introduced. n=1 is the original mode, n=2 an improvement, etc.. See the -pointer_mode n help for more info. - Also, in some circumstances the [529]-threads option can improve + Also, in some circumstances the [533]-threads option can improve response considerably. Be forewarned that if more than one vncviewer is connected at the same time then libvncserver may not be thread safe (try to get the viewers to use different VNC encodings, e.g. tight and ZRLE.) This option can be unstable and so as of Feb/2008 it is disabled by default. Set env. X11VNC_THREADED=1 to re-enable. - As of Apr/2005 two new options (see the [530]wireframe FAQ and - [531]scrollcopyrect FAQ below) provide schemes to sweep this problem + As of Apr/2005 two new options (see the [534]wireframe FAQ and + [535]scrollcopyrect FAQ below) provide schemes to sweep this problem under the rug for window moves or resizes and for some (but not all) window scrolls. These are the preferred way of avoiding the "lurching" problem, contact me if they are not working. Note on SuSE and some @@ -6164,8 +6185,8 @@ EndSection the window move/resize stops, it returns to normal processing: you should only see the window appear in the new position. This spares you from interacting with a "lurching" window between all of the - intermediate steps. BTW the lurching is due to [532]slow video card - read rates (see [533]here too.) A displacement, even a small one, of a + intermediate steps. BTW the lurching is due to [536]slow video card + read rates (see [537]here too.) A displacement, even a small one, of a large window requires a non-negligible amount of time, a good fraction of a second, to read in from the hardware framebuffer. @@ -6173,7 +6194,7 @@ EndSection for -wireframe to do any good. The mode is currently on by default because most people are afflicted - with the problem. It can be disabled with the [534]-nowireframe option + with the problem. It can be disabled with the [538]-nowireframe option (aka -nowf.) Why might one want to turn off the wireframing? Since x11vnc is merely guessing when windows are being moved/resized, it may guess poorly for your window-manager or desktop, or even for the way @@ -6219,13 +6240,13 @@ EndSection * Maximum time to show a wireframe animation. * Minimum time between sending wireframe outlines. - See the [535]"-wireframe tweaks" option for more details. On a slow + See the [539]"-wireframe tweaks" option for more details. On a slow link, e.g. dialup modem, the parameters may be automatically adjusted for better response. CopyRect encoding: In addition to the above there is the - [536]"-wirecopyrect mode" option. It is also on by default. This + [540]"-wirecopyrect mode" option. It is also on by default. This instructs x11vnc to not only show the wireframe animation, but to also instruct all connected VNC viewers to locally translate the window image data from the original position to the new position on the @@ -6273,7 +6294,7 @@ EndSection requiring the image data to be transmitted over the network. For fast links the speedup is primarily due to x11vnc not having to read the scrolled framebuffer data from the X server (recall that reading from - the hardware framebuffer is [537]slow.) + the hardware framebuffer is [541]slow.) To do this x11vnc uses the RECORD X extension to snoop the X11 protocol between the X client with the focus window and the X server. @@ -6300,10 +6321,10 @@ EndSection the X server display: if one falls too far behind it could become a mess... - The initial implementation of [538]-scrollcopyrect option is useful in + The initial implementation of [542]-scrollcopyrect option is useful in that it detects many scrolls and thus gives a much nicer working - environment (especially when combined with the [539]-wireframe - [540]-wirecopyrect [541]options, which are also on by default; and if + environment (especially when combined with the [543]-wireframe + [544]-wirecopyrect [545]options, which are also on by default; and if you are willing to enable the ShadowFB things are very fast.) The fact that there aren't long delays or lurches during scrolling is the primary improvement. @@ -6336,10 +6357,10 @@ EndSection One can tap the Alt_L key (Left "Alt" key) 3 times in a row to signal x11vnc to refresh the screen to all viewers. Your VNC-viewer may have its own screen refresh hot-key or button. See - also: [542]-fixscreen + also: [546]-fixscreen * Some applications, notably OpenOffice, do XCopyArea scrolls in weird ways that assume ancestor window clipping is taking place. - See the [543]-scr_skip option for ways to tweak this on a + See the [547]-scr_skip option for ways to tweak this on a per-application basis. * Selecting text while dragging the mouse may be slower, especially if the Button-down event happens near the window's edge. This is @@ -6356,7 +6377,7 @@ EndSection because it fails to detect scrolls in it. Sometimes clicking inside the application window or selecting some text in it to force the focus helps. - * When using the [544]-scale option there will be a quick CopyRect + * When using the [548]-scale option there will be a quick CopyRect scroll, but it needs to be followed by a slower "cleanup" update. This is because for a fixed finite screen resolution (e.g. 75 dpi) scaling and copyrect-ing are not exactly independent. Scaling @@ -6369,7 +6390,7 @@ EndSection If you find the -scrollcopyrect behavior too approximate or distracting you can go back to the standard polling-only update method - with the [545]-noscrollcopyrect (or -noscr for short.) If you find + with the [549]-noscrollcopyrect (or -noscr for short.) If you find some extremely bad and repeatable behavior for -scrollcopyrect please report a bug. @@ -6394,9 +6415,9 @@ EndSection that pixel data is needed again it does not have to be retransmitted over the network. - As of Dec/2006 in the [546]0.9 development tarball there is an + As of Dec/2006 in the [550]0.9 development tarball there is an experimental client-side caching implementation enabled by the - "[547]-ncache n" option. In fact, during the test period it was on by + "[551]-ncache n" option. In fact, during the test period it was on by default with n set to 10. To disable it use "-noncache". It is a simple scheme where a (very large) lower portion of the @@ -6423,7 +6444,7 @@ EndSection there is a bug: you can scroll down in your viewer and see a strange "history" of windows on your desktop. This is working as intended. One will need to try to adjust the size of his VNC Viewer window so the - cache area cannot be seen. [548]SSVNC (see below) can do this + cache area cannot be seen. [552]SSVNC (see below) can do this automatically. At some point LibVNCServer may implement a "rfbFBCrop" pseudoencoding @@ -6433,7 +6454,7 @@ EndSection rendering...) The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice - [549]-ycrop option to help hide the pixel cache area from view. It + [553]-ycrop option to help hide the pixel cache area from view. It will turn on automatically if the framebuffer appears to be very tall (height more than twice the width), or you can supply the actual value for the height. If the screen is resized by scaling, etc, the ycrop @@ -6464,7 +6485,7 @@ EndSection an additional factor of 2 in memory use. However, even in the smallest usage mode with n equal 2 and - [550]-ncache_no_rootpixmap set (this requires only 2X additional + [554]-ncache_no_rootpixmap set (this requires only 2X additional framebuffer memory) there is still a noticable improvement for many activities, although it is not as dramatic as with, say n equal 12 and rootpixmap (desktop background) caching enabled. @@ -6475,7 +6496,7 @@ EndSection be tuned to use less, or the VNC community will extend the protocol to allow caching and replaying of compressed blobs of data. - Another option to experiment with is "[551]-ncache_cr". By specifying + Another option to experiment with is "[555]-ncache_cr". By specifying it, x11vnc will try to do smooth opaque window moves instead of its wireframe. This can give a very nice effect (note: on Unix the realvnc viewer seems to be smoother than the tightvnc viewer), but can lead to @@ -6532,24 +6553,24 @@ EndSection As of Feb/2009 (development tarball) there is an experimental kludge to let you build x11vnc using TurboVNC's modified TightVNC encoding. - [552]TurboVNC is part of the [553]VirtualGL project. It does two main + [556]TurboVNC is part of the [557]VirtualGL project. It does two main things to speed up the TightVNC encoding: * It eliminates bottlenecks, overheads, wait-times in the TightVNC encoding implementation and instead only worries about sending very well (and quickly) compressed JPEG data. * A fast proprietary JPEG implemention is used (Intel IPP on x86) - instead of the usual libjpeg implementation. [554]TurboJPEG is an + instead of the usual libjpeg implementation. [558]TurboJPEG is an interface library, libturbojpeg, provided by the project that achieves this. TurboVNC works very well over LAN and evidently fast Broadband too. When using it with x11vnc in such a situation you may want to dial - down the delays, e.g. "[555]-wait 5" and "[556]-defer 5" (or even a + down the delays, e.g. "[559]-wait 5" and "[560]-defer 5" (or even a smaller setting) to poll and pump things out more quickly. See the instructions in "x11vnc/misc/turbovnc/README" for how to build x11vnc with TurboVNC support. You will also need to download the - [557]TurboJPEG software. + [561]TurboJPEG software. In brief, the steps look like this: cd x11vnc-x.y.z/x11vnc/misc/turbovnc @@ -6561,22 +6582,22 @@ EndSection where you replace "/DIR" with the directory containing libturbojpeg.so you downloaded separately. If it works out well enough TurboVNC support will be integrated into x11vnc and more of its tuning features - will be implemented. Support for TurboVNC in [558]SSVNC viewer has + will be implemented. Support for TurboVNC in [562]SSVNC viewer has been added as an experiment as well. If you try either one, let us know how it went. There also may be some Linux.i686 and Darwin.i386 x11vnc binaries with - TurboVNC support in the [559]misc. bins directory. For other platforms + TurboVNC support in the [563]misc. bins directory. For other platforms you will need to compile yourself. On relatively cheap and old hardware (Althon64 X2 5000+ / GeForce - 6200) x11vnc and [560]SSVNC, both TurboVNC enabled, were able to + 6200) x11vnc and [564]SSVNC, both TurboVNC enabled, were able to sustain 13.5 frames/sec (fps) and 15 Megapixels/sec using the VirtualGL supplied OpenGL benchmark program glxspheres. VirtualGL on - higher-end hardware can sustain [561]20-30 fps with the glxspheres + higher-end hardware can sustain [565]20-30 fps with the glxspheres benchmark. - Potential Slowdown: As we describe [562]elsewhere, unless you use + Potential Slowdown: As we describe [566]elsewhere, unless you use x11vnc with an X server using, say, NVidia proprietary drivers (or a virtual X server like Xvfb or Xdummy, or in ShadowFB mode), then the read rate from the graphics card can be rather slow (e.g. 10 MB/sec) @@ -6616,23 +6637,23 @@ EndSection this is because the cursor shape is often downloaded to the graphics hardware (video card), but I could be mistaken. - A simple kludge is provided by the "[563]-cursor X" option that + A simple kludge is provided by the "[567]-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 "[564]-cursor some" option for + work for those cases. Also see the "[568]-cursor some" option for additional kludges. Note that as of Aug/2004 on Solaris using the SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse cursor when the - [565]-overlay option is supplied. See [566]this FAQ for more info. + [569]-overlay option is supplied. See [570]this FAQ for more info. Also as of Dec/2004 XFIXES X extension support has been added to allow exact extraction of the mouse cursor shape. XFIXES fixes the problem of the cursor-shape being write-only: x11vnc can now query the X server for the current shape and send it back to the connected viewers. XFIXES is available on recent Linux Xorg based distros and - [567]Solaris 10. + [571]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 @@ -6640,7 +6661,7 @@ EndSection situations where the cursor transparency can also handled exactly: when the VNC Viewer requires the cursor shape be drawn into the VNC framebuffer or if you apply a patch to your VNC Viewer to extract - hidden alpha channel data under 32bpp. [568]Details can be found here. + hidden alpha channel data under 32bpp. [572]Details can be found here. Q-81: When using XFIXES cursorshape mode, some of the cursors look @@ -6673,17 +6694,17 @@ EndSection for most cursor themes and you don't have to worry about it. In case it still looks bad for your cursor theme, there are (of - course!) some tunable parameters. The "[569]-alphacut n" option lets + course!) some tunable parameters. The "[573]-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 "[570]-alphafrac f" option tries to correct individual + 240. The "[574]-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 [571]-alpharemove that is useful for + Finally, there is an option [575]-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 @@ -6709,10 +6730,10 @@ EndSection alpha channel data to libvncserver. However, this data will only be used for VNC clients that do not support the CursorShapeUpdates VNC extension (or have disabled it.) It can be disabled for all clients - with the [572]-nocursorshape x11vnc option. In this case the cursor is + with the [576]-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 [573]-noalphablend option to disable this + the x11vnc side. Use the [577]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values.) @@ -6736,7 +6757,7 @@ EndSection example on how to change the Windows TightVNC viewer to achieve the same thing (send me the patch if you get that working.) - This patch is applied to the [574]Enhanced TightVNC Viewer (SSVNC) + This patch is applied to the [578]Enhanced TightVNC Viewer (SSVNC) package we provide. [Mouse Pointer] @@ -6744,9 +6765,9 @@ EndSection Q-83: Why does the mouse arrow just stay in one corner in my vncviewer, whereas my cursor (that does move) is just a dot? - This default takes advantage of a [575]tightvnc extension + This default takes advantage of a [579]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [576]-nocursor + the local VNC viewer. You may disable it with the [580]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -6760,17 +6781,17 @@ EndSection clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [577]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [581]-cursorpos option when starting x11vnc. A VNC viewer must support the Cursor Positions Updates for the user to see the mouse motions (the TightVNC viewers support this.) As of Aug/2004 -cursorpos - is the default. See also [578]-nocursorpos and [579]-nocursorshape. + is the default. See also [582]-nocursorpos and [583]-nocursorshape. Q-85: Is it possible to swap the mouse buttons (e.g. left-handed operation), or arbitrarily remap them? How about mapping button clicks to keystrokes, e.g. to partially emulate Mouse wheel scrolling? - You can remap the mouse buttons via something like: [580]-buttonmap + You can remap the mouse buttons via something like: [584]-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. @@ -6778,7 +6799,7 @@ EndSection One user had an X server with only one mouse button(!) and was able to map all of the VNC client mouse buttons to it via: -buttonmap 123-111. - Note that the [581]-debug_pointer option prints out much info for + Note that the [585]-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 @@ -6800,7 +6821,7 @@ EndSection Exactly what keystroke "scrolling" events they should be bound to depends on one's taste. If this method is too approximate, one could - consider not using [582]-buttonmap but rather configuring the X server + consider not using [586]-buttonmap but rather configuring the X server to think it has a mouse with 5 buttons even though the physical mouse does not. (e.g. 'Option "ZAxisMapping" "4 5"'.) @@ -6830,7 +6851,7 @@ EndSection Q-86: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [583]-modtweak should help here. It is a mode that monitors + The option [587]-modtweak should help here. It is a mode that monitors the state of the Shift and AltGr Modifiers and tries to deduce the correct keycode to send, possibly by sending fake modifier key presses and releases in addition to the actual keystroke. @@ -6839,20 +6860,20 @@ EndSection to get the old behavior.) This was done because it was noticed on newer XFree86 setups even on bland "us" keyboards like "pc104 us" XFree86 included a "ghost" key with both "<" and ">" it. This key does - not exist on the keyboard (see [584]this FAQ for more info.) Without + not exist on the keyboard (see [588]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 [585]FAQ about the -xkb option for a more powerful method + Also see the [589]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 - [586]-debug_keyboard option prints out much info for every keystroke + [590]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. Note that one user had a strange setup and none of the above helped. - His solution was to disable all of the above and use [587]-nomodtweak. + His solution was to disable all of the above and use [591]-nomodtweak. This is the simplest form of keystroke insertion and it actually solved the problem. Try it if the other options don't help. @@ -6865,9 +6886,9 @@ EndSection (e.g. pc105 in the XF86Config file when it should be something else, say pc104.) - Short Cut: Try the [588]-xkb or [589]-sloppy_keys options and see if + Short Cut: Try the [592]-xkb or [593]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [590]-modtweak is now the default) but it is useful reference for + [594]-modtweak is now the default) but it is useful reference for various tricks and so is kept. @@ -6910,17 +6931,17 @@ EndSection -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([591]-modtweak) is a mode that monitors the + settings. The former ([595]-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 ([592]-remap less-comma) is an immediate remapping of the + The latter ([596]-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 [593]FAQ about the -xkb option as a possible workaround + See also the [597]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [594]-debug_keyboard option prints out much info for + Note that the [598]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. @@ -6928,7 +6949,7 @@ EndSection less than) instead I get "<," (i.e. an extra comma.) This is likely because you press "Shift" then "<" but then released - the Shift key before releasing the "<". Because of a [595]keymapping + the Shift key before releasing the "<". Because of a [599]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. @@ -6936,9 +6957,9 @@ EndSection characters: in general it can happen whenever the Shift key is released early. - This should not happen in [596]-xkb mode, because it works hard to + This should not happen in [600]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [597]-sloppy_keys to attempt a similar type of algorithm. + option [601]-sloppy_keys to attempt a similar type of algorithm. One user had this problem for Italian and German keyboards with the key containing ":" and "." When he typed ":" he would get an extra "." @@ -6966,7 +6987,7 @@ EndSection In both cases no AltGr is sent to the VNC server, but we know AltGr is needed on the physical international keyboard to type a "@". - This all worked fine with x11vnc running with the [598]-modtweak + This all worked fine with x11vnc running with the [602]-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 @@ -6983,7 +7004,7 @@ EndSection * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [599]-xkb option seems to fix all of the missing keys: "@", "<", + The [603]-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 @@ -6991,7 +7012,7 @@ EndSection debugging output (send it along with any problems you report.) Update: as of Jun/2005 x11vnc will try to automatically enable - [600]-xkb if it appears that would be beneficial (e.g. if it sees any + [604]-xkb if it appears that would be beneficial (e.g. if it sees any of "@", "<", ">", "[" and similar keys are mapped in a way that needs the -xkb to access them.) To disable this automatic check use -noxkb. @@ -7006,7 +7027,7 @@ EndSection was attached to keycode 93 (no physical key generates this keycode) while ISO_Level3_Shift was attached to keycode 113. The keycode skipping option was used to disable the ghost key: - [601]-skip_keycodes 93 + [605]-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 @@ -7024,16 +7045,16 @@ EndSection What to do? In general the VNC protocol has not really solved this problem: what should be done if the VNC viewer sends a keysym not recognized by the VNC server side? Workarounds can possibly be - created using the [602]-remap x11vnc option: + created using the [606]-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 - [603]-add_keysyms option in the next paragraph. - Update: for convenience "[604]-remap DEAD" does many of these + [607]-add_keysyms option in the next paragraph. + Update: for convenience "[608]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [605]-remap, an - option [606]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [609]-remap, an + option [610]-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 @@ -7052,7 +7073,7 @@ EndSection Short answer: disable key autorepeating by running the command "xset r off" on the Xserver where x11vnc is run (restore via "xset r on") or - use the new (Jul/2004) [607]-norepeat x11vnc option. You will still + use the new (Jul/2004) [611]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -7076,7 +7097,7 @@ EndSection off", does the problem go away? The workaround is to manually apply "xset r off" and "xset r on" as - needed, or to use the [608]-norepeat (which has since Dec/2004 been + needed, or to use the [612]-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 @@ -7087,7 +7108,7 @@ EndSection keystrokes!! Are you using x11vnc to log in to an X session via display manager? - (as described in [609]this FAQ) If so, x11vnc is starting before your + (as described in [613]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 @@ -7148,11 +7169,11 @@ EndSection desktop manages these "warps". If the viewer is not notified it cannot know it needs to release the modifiers. - You can also use the [610]-clear_mods option to try to clear all of + You can also use the [614]-clear_mods option to try to clear all of the modifier keys at x11vnc startup. You will still have to be careful that you do not leave the modifier key pressed down during your session. It is difficult to prevent this problem from occurring (short - of using [611]-remap to prevent sending all of the problem modifier + of using [615]-remap to prevent sending all of the problem modifier keys, which would make the destkop pretty unusable.) During a session these x11vnc remote control commands can also help: @@ -7165,16 +7186,16 @@ EndSection Num_Lock down. When these are locked on the remote side it can sometimes lead to strange desktop behavior (e.g. cannot drag or click on windows.) As above you may not notice this because the lock isn't - down on the local (Viewer) side. See [612]this FAQ on lock keys - problem. These options may help avoid the problem: [613]-skip_lockkeys - and [614]-capslock. See also [615]-clear_all. + down on the local (Viewer) side. See [616]this FAQ on lock keys + problem. These options may help avoid the problem: [617]-skip_lockkeys + and [618]-capslock. See also [619]-clear_all. Q-93: The machine where I run x11vnc has an AltGr key, but the local machine where I run the VNC viewer does not. Is there a way I can map a local unused key to send an AltGr? How about a Compose key as well? - Something like "[616]-remap Super_R-Mode_switch" x11vnc option may + Something like "[620]-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).) @@ -7197,7 +7218,7 @@ EndSection Since xmodmap(1) modifies the X server mappings you may not want to do this (because it affects local work on that machine.) Something like - the [617]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [621]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones needs, and does not modify the X server environment. Note that you cannot send Alt_L in this case, maybe -remap Super_L-Meta_L would be a better choice if the Super_L key is typically unused in Unix. @@ -7217,7 +7238,7 @@ EndSection and similar triple mappings (with two in the AltGr/Mode_switch group) of a keysum to a single keycode. - Use the [618]-nomodtweak option as a workaround. You can also use + Use the [622]-nomodtweak option as a workaround. You can also use xmodmap to correct these mappings in the server, e.g.: xmodmap -e "keycode 47 = 3 numbersign" @@ -7231,7 +7252,7 @@ EndSection This can be done directly in some X servers using AccessX and Pointer_EnableKeys, but is a bit awkward. It may be more convenient to - have x11vnc do the remapping. This can be done via the [619]-remap + have x11vnc do the remapping. This can be done via the [623]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -7240,7 +7261,7 @@ EndSection button "paste" because (using XFree86/Xorg Emulate3Buttons) you have to click both buttons on the touch pad at the same time. This remapping: - [620]-remap Super_R-Button2 + [624]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -7259,13 +7280,13 @@ EndSection Caps_Lock in the viewer your local machine goes into the Caps_Lock on state and sends keysym "A" say when you press "a". x11vnc will then fake things up so that Shift is held down to generate "A". The - [621]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[622]-remap Caps_Lock-None". + [625]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[626]-remap Caps_Lock-None". - Also try the [623]-nomodtweak and [624]-capslock options. + Also try the [627]-nomodtweak and [628]-capslock options. Another useful option that turns off any Lock keys on the remote side - at startup and end is the [625]-clear_all option. During a session you + at startup and end is the [629]-clear_all option. During a session you can run these remote control commands to modify the Lock keys: x11vnc -R clear_locks x11vnc -R clear_all @@ -7294,7 +7315,7 @@ EndSection There may also be scaling viewers out there (e.g. TightVNC or UltraVNC on Windows) that automatically shrink or expand the remote framebuffer to fit the local display. Especially for hand-held devices. See also - [626]the next FAQ on x11vnc scaling. + [630]the next FAQ on x11vnc scaling. Q-99: Does x11vnc support server-side framebuffer scaling? (E.g. to @@ -7302,7 +7323,7 @@ EndSection As of Jun/2004 x11vnc provides basic server-side scaling. It is a global scaling of the desktop, not a per-client setting. To enable it - use the "[627]-scale fraction" option. "fraction" can either be a + use the "[631]-scale fraction" option. "fraction" can either be a floating point number (e.g. -scale 0.75) or the alternative m/n fraction notation (e.g. -scale 3/4.) Note that if fraction is greater than one the display is magnified. @@ -7327,7 +7348,7 @@ EndSection One can also use the ":nb" with an integer scale factor (say "-scale 2:nb") to use x11vnc as a screen magnifier for vision impaired - [628]applications. Since with integer scale factors the framebuffers + [632]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -7353,7 +7374,7 @@ EndSection If one desires per-client scaling for something like 1:1 from a workstation and 1:2 from a smaller device (e.g. handheld), currently the only option is to run two (or more) x11vnc processes with - different scalings listening on separate ports ([629]-rfbport option, + different scalings listening on separate ports ([633]-rfbport option, etc.) Update: As of May/2006 x11vnc also supports the UltraVNC server-side @@ -7363,8 +7384,8 @@ EndSection "-rfbversion 3.6" for this to be recognized by UltraVNC viewers. BTW, whenever you run two or more x11vnc's on the same X display and - use the [630]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [631]"-connect + use the [634]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [635]"-connect file1 -gui ..." with different connect files for each x11vnc you want to control via the gui (or remote-control.) The "-connect file1" usage gives separate communication channels between a x11vnc process and the @@ -7373,7 +7394,7 @@ EndSection Update: As of Mar/2005 x11vnc now scales the mouse cursor with the same scale factor as the screen. If you don't want that, use the - [632]"-scale_cursor frac" option to set the cursor scaling to a + [636]"-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.) @@ -7401,21 +7422,21 @@ EndSection screen is not rectangular (e.g. 1280x1024 and 1024x768 monitors joined together), then there will be "non-existent" areas on the screen. The X server will return "garbage" image data for these areas and so they - may be distracting to the viewer. The [633]-blackout x11vnc option + may be distracting to the viewer. The [637]-blackout x11vnc option allows you to blacken-out rectangles by manually specifying their WxH+X+Y geometries. If your system has the libXinerama library, the - [634]-xinerama x11vnc option can be used to have it automatically + [638]-xinerama x11vnc option can be used to have it automatically determine the rectangles to be blackened out. (Note on 8bpp PseudoColor displays the fill color may not be black.) Update: - [635]-xinerama is now on by default. + [639]-xinerama is now on by default. Some users have reported that the mouse does not behave properly for their Xinerama display: i.e. the mouse cannot be moved to all regions - of the large display. If this happens try using the [636]-xwarppointer + of the large display. If this happens try using the [640]-xwarppointer option. This instructs x11vnc to fake mouse pointer motions using the XWarpPointer function instead of the XTestFakeMotionEvent XTEST function. (This may be due to a bug in the X server for XTEST when - Xinerama is enabled.) Update: As of Dec/2006 [637]-xwarppointer will + Xinerama is enabled.) Update: As of Dec/2006 [641]-xwarppointer will be applied automatically if Xinerama is detected. To disable use: -noxwarppointer @@ -7438,23 +7459,23 @@ EndSection Note: if you are running on Solaris 8 or earlier you can easily hit up against the maximum of 6 shm segments per process (for Xsun in this case) from running multiple x11vnc processes. You should modify - /etc/system as mentioned in another [638]FAQ to increase the limit. It - is probably also a good idea to run with the [639]-onetile option in + /etc/system as mentioned in another [642]FAQ to increase the limit. It + is probably also a good idea to run with the [643]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [640]-noshm to use no shm segments. + [644]-noshm to use no shm segments. Q-102: Can x11vnc show only a portion of the display? (E.g. for a special purpose application or a very large screen.) - As of Mar/2005 x11vnc has the "[641]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[645]-clip WxH+X+Y" option to select a rectangle of width W, height H and offset (X, Y). Thus the VNC screen will be the clipped sub-region of the display and be only WxH in size. - One user used -clip to split up a large [642]Xinerama screen into two + One user used -clip to split up a large [646]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [643]-id or [644]-sid options are used. The offset is measured + the [647]-id or [648]-sid options are used. The offset is measured from the upper left corner of the selected window. @@ -7463,7 +7484,7 @@ EndSection just seems to crash. As of Dec/2004 x11vnc supports XRANDR. You enable it with the - [645]-xrandr option to make x11vnc monitor XRANDR events and also trap + [649]-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. @@ -7473,9 +7494,9 @@ EndSection then the viewer will automatically resize. Otherwise, the new framebuffer is fit as best as possible into the original viewer size (portions of the screen may be clipped, unused, etc.) For these - viewers you can try the [646]-padgeom option to make the region big + viewers you can try the [650]-padgeom option to make the region big enough to hold all resizes and rotations. We have fixed this problem - for the TightVNC Viewer on Unix: [647]SSVNC + for the TightVNC Viewer on Unix: [651]SSVNC If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you @@ -7487,7 +7508,7 @@ EndSection reflect the screen that the VNC viewers see? (e.g. for a handheld whose screen is rotated 90 degrees.) - As of Jul/2006 there is the [648]-rotate option allow this. E.g's: + As of Jul/2006 there is the [652]-rotate option allow this. E.g's: "-rotate +90", "-rotate -90", "-rotate x", etc. @@ -7552,13 +7573,13 @@ EndSection This may be a bug in kdesktop_lock. For now the only workaround is to disable the screensaver. You can try using another one such as - straight xscreensaver (see the instructions [649]here for how to + straight xscreensaver (see the instructions [653]here for how to disable kdesktop_lock.) If you have more info on this or see it outside of KDE please let us know. Update: It appears this is due to kdesktop_lock enabling the screen saver when the Monitor is in DPMS low-power state (e.g. standby, - suspend, or off.) In Nov/2006 the x11vnc [650]-nodpms option was added + suspend, or off.) In Nov/2006 the x11vnc [654]-nodpms option was added as a workaround. Normally it is a good thing that the monitor powers down (since x11vnc can still poll the framebuffer in this state), but if you experience the kdesktop_lock problem you can specify the @@ -7574,16 +7595,16 @@ EndSection This appears to be because the 3D OpenGL/GLX hardware screen updates do not get reported via the XDAMAGE mechanism. So this is a bug in - [651]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video + [655]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video card driver. - As a workaround apply the [652]-noxdamage option. As of Feb/2007 + As a workaround apply the [656]-noxdamage option. As of Feb/2007 x11vnc will try to autodetect the problem and disable XDAMAGE if is appears to be missing a lot of updates. But if you know you are using - beryl you might as well always supply -noxdamage. Thanks to [653]this + beryl you might as well always supply -noxdamage. Thanks to [657]this user who reported the problem and discovered the workaround. - A developer for [654]MiniMyth reports that the 'alphapulse' tag of the + A developer for [658]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. @@ -7603,9 +7624,9 @@ EndSection * Fullscreen mode The way VMWare does Fullscreen mode on Linux is to display the Guest - desktop in a separate Virtual Terminal (e.g. VT 8) (see [655]this FAQ + desktop in a separate Virtual Terminal (e.g. VT 8) (see [659]this FAQ on VT's for background.) Unfortunately, this Fullscreen VT is not an X - server. So x11vnc cannot access it (however, [656]see this discussion + server. So x11vnc cannot access it (however, [660]see this discussion of -rawfb for a possible workaround.) x11vnc works fine with "Normal X application window" and "Quick-Switch mode" because these use X. @@ -7626,13 +7647,13 @@ EndSection improve response. One can also cut the display depth (e.g. to 16bpp) in this 2nd X session to improve video performance. This 2nd X session emulates Fullscreen mode to some degree and can be viewed via x11vnc - as long as the VMWare X session [657]is in the active VT. + as long as the VMWare X session [661]is in the active VT. Also note that with a little bit of playing with "xwininfo -all -children" output one can extract the (non-toplevel) window-id of the of the Guest desktop only when VMWare is running as a normal X application. Then one can export just the guest desktop (i.e. without - the VMWare menu buttons) by use of the [658]-id windowid option. The + the VMWare menu buttons) by use of the [662]-id windowid option. The caveats are the X session VMWare is in must be in the active VT and the window must be fully visible, so this mode is not terribly convenient, but could be useful in some circumstances (e.g. running @@ -7648,10 +7669,10 @@ EndSection controlled) via VNC with x11vnc? As of Apr/2005 there is support for this. Two options were added: - "[659]-rawfb string" (to indicate the raw frame buffer device, file, - etc. and its parameters) and "[660]-pipeinput command" (to provide an + "[663]-rawfb string" (to indicate the raw frame buffer device, file, + etc. and its parameters) and "[664]-pipeinput command" (to provide an external program that will inject or otherwise process mouse and - keystroke input.) Some useful [661]-pipeinput schemes, VID, CONSOLE, + keystroke input.) Some useful [665]-pipeinput schemes, VID, CONSOLE, and UINPUT, have since been built into x11vnc for convenience. This non-X mode for x11vnc is somewhat experimental because it is so @@ -7691,9 +7712,9 @@ EndSection access method.) Only use file if map isn't working. BTW, "mmap" is an alias for "map" and if you do not supply a type and the file exists, map is assumed (see the -help output and below for some exceptions to - this.) The "snap:" setting applies the [662]-snapfb option with + this.) The "snap:" setting applies the [666]-snapfb option with "file:" type reading (this is useful for exporting webcams or TV tuner - video; see [663]the next FAQ for more info.) + video; see [667]the next FAQ for more info.) Also, if the string is of the form "setup:cmd" then cmd is run and the first line of its output retrieved and used as the rawfb string. This @@ -7738,7 +7759,7 @@ EndSection screen to either shm or a mapped file. The format of these is XWD and so the initial header should be skipped. BTW, since XWD is not strictly RGB the view will only be approximate, but usable. Of course - for the case of Xvfb x11vnc can poll it much better via the [664]X + for the case of Xvfb x11vnc can poll it much better via the [668]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -7769,13 +7790,13 @@ minal #2) tty1-tty6), or X graphical display (usually starting at tty7.) In addition to the text console other graphical ones may be viewed and interacted with as well, e.g. DirectFB or SVGAlib apps, VMWare non-X - fullscreen, or [665]Qt-embedded apps (PDAs/Handhelds.) By default the + fullscreen, or [669]Qt-embedded apps (PDAs/Handhelds.) By default the pipeinput mechanisms UINPUT and CONSOLE (keystrokes only) are automatically attempted in this mode under "-rawfb console". The Video4Linux Capture device, /dev/video0, etc is either a Webcam or a TV capture device and needs to have its driver enabled in the - kernel. See [666]this FAQ for details. If specified via "-rawfb Video" + kernel. See [670]this FAQ for details. If specified via "-rawfb Video" then the pipeinput method "VID" is applied (it lets you change video parameters dynamically via keystrokes.) @@ -7783,10 +7804,10 @@ minal #2) also useful in testing. - All of the above [667]-rawfb options are just for viewing the raw + All of the above [671]-rawfb options are just for viewing the raw framebuffer (although some of the aliases do imply keystroke and mouse pipeinput methods.) That may be enough for certain applications of - this feature (e.g. suppose a [668]video camera mapped its framebuffer + this feature (e.g. suppose a [672]video camera mapped its framebuffer into memory and you just wanted to look at it via VNC.) To handle the pointer and keyboard input from the viewer users the "-pipeinput cmd" option was added to indicate a helper program to @@ -7824,7 +7845,7 @@ minal #2) keystrokes into the Linux console (e.g. the virtual consoles: /dev/tty1, /dev/tty2, etc) in x11vnc/misc/vcinject.pl. It is based on the vncterm/LinuxVNC.c program also in the libvncserver CVS. So to - view and interact with VT #2 (assuming it is the [669]active VT) one + view and interact with VT #2 (assuming it is the [673]active VT) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -7879,7 +7900,7 @@ minal #2) better to use the more accurate and faster LinuxVNC program. The advantage x11vnc -rawfb might have is that it can allow interaction with a non-text application, e.g. one based on SVGAlib or - [670]Qt-embedded Also, for example the [671]VMWare Fullscreen mode is + [674]Qt-embedded Also, for example the [675]VMWare Fullscreen mode is actually viewable under -rawfb and can be interacted with if uinput is enabled. @@ -7944,9 +7965,9 @@ minal #2) Q-113: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - Yes, this is possible to some degree with the [672]-rawfb option. + Yes, this is possible to some degree with the [676]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [673]previous FAQ on -rawfb + used for the screen image data. See the [677]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -7958,7 +7979,7 @@ minal #2) snapshot to a file that you point -rawfb to; ask me if it is not clear what to do.) - The "snap:" enforces [674]-snapfb mode which appears to be necessary. + The "snap:" enforces [678]-snapfb mode which appears to be necessary. The read pointer for video capture devices cannot be repositioned (which would be needed for scanline polling), but you can read a full frame of data from the device. @@ -7980,7 +8001,7 @@ minal #2) Many video4linux drivers tend to set the framebuffer to be 24bpp (as opposed to 32bpp.) Since this can cause problems with VNC viewers, - etc, the [675]-24to32 option will be automatically imposed when in + etc, the [679]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -7988,7 +8009,7 @@ minal #2) wavering in brightness is always happening. This can lead to much network bandwidth consumption for the VNC traffic and also local CPU and I/O resource usage. You may want to experiment with "dialing down" - the framerate via the [676]-wait, [677]-slow_fb, or [678]-defer + the framerate via the [680]-wait, [681]-slow_fb, or [682]-defer options. Decreasing the window size and bpp also helps. @@ -8077,7 +8098,7 @@ minal #2) format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [679]-freqtab option to supply your own xawtv channel to + See also the [683]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc.) @@ -8086,7 +8107,7 @@ minal #2) running on my handheld or PC using the Linux console framebuffer (i.e. not X11)? - Yes, the basic method for this is the [680]-rawfb scheme where the + Yes, the basic method for this is the [684]-rawfb scheme where the Linux console framebuffer (usually /dev/fb0) is polled and the uinput driver is used to inject keystrokes and mouse input. Often you will just have to type: @@ -8099,7 +8120,7 @@ minal #2) x11vnc -rawfb /dev/fb0@640x480x16 Also, to force usage of the uinput injection method use "-pipeinput - UINPUT". See the [681]-pipeinput description for tunable parameters, + UINPUT". See the [685]-pipeinput description for tunable parameters, etc. One problem with the x11vnc uinput scheme is that it cannot guess the @@ -8115,7 +8136,7 @@ minal #2) Even with the correct acceleration setting there is still some drift (probably because of the mouse threshold where the acceleration kicks in) and so x11vnc needs to reposition the cursor from 0,0 about 5 - times a second. See the [682]-pipeinput UINPUT option for tuning + times a second. See the [686]-pipeinput UINPUT option for tuning parameters that can be set (there are some experimental thresh=N tuning parameters as well) @@ -8150,7 +8171,7 @@ minal #2) Q-115: Now that non-X11 devices can be exported via VNC using x11vnc, can I build it with no dependencies on X11 header files and libraries? - Yes, as of Jul/2006 x11vnc enables building for [683]-rawfb only + Yes, as of Jul/2006 x11vnc enables building for [687]-rawfb only support. Just do something like when building: ./configure --without-x (plus any other flags) make @@ -8166,11 +8187,11 @@ minal #2) Yes, since Nov/2006 in the development tree (x11vnc-0.8.4 tarball) there is support for native Mac OS X Aqua/Quartz displays using the - [684]-rawfb mechanism described above. The mouse and keyboard input is + [688]-rawfb mechanism described above. The mouse and keyboard input is achieved via Mac OS X API's. - So you can use x11vnc as an alternative to [685]OSXvnc (aka Vine - Server), or [686]Apple Remote Desktop (ARD). Perhaps there is some + So you can use x11vnc as an alternative to [689]OSXvnc (aka Vine + Server), or [690]Apple Remote Desktop (ARD). Perhaps there is some x11vnc feature you'd like to use on Mac OS X, etc. For a number of activities (e.g. window drags) it seems to be faster than OSXvnc. @@ -8180,7 +8201,7 @@ minal #2) (XDarwin) running on Mac OS X (people often install this software to display remote X11 apps on their Mac OS X system, or use some old favorites locally such as xterm.) However in this case x11vnc will - only work reasonably in single window [687]-id windowid mode (and the + only work reasonably in single window [691]-id windowid mode (and the window may need to have mouse focus.) If you do not have the DISPLAY env. variable set, x11vnc will assume @@ -8198,9 +8219,9 @@ minal #2) ./configure --without-x make - Win2VNC/x2vnc: One handy use is to use the [688]-nofb mode to + Win2VNC/x2vnc: One handy use is to use the [692]-nofb mode to redirect mouse and keyboard input to a nearby Mac (i.e. one to the - side of your desk) via [689]x2vnc or Win2VNC. See [690]this FAQ for + side of your desk) via [693]x2vnc or Win2VNC. See [694]this FAQ for more info. Options: Here are the Mac OS X specific x11vnc options: @@ -8274,13 +8295,13 @@ rm -f $tmp performance for the case of a large number of simultaneous VNC viewers (e.g. classroom broadcasting or a large demo)? - Yes, as of Feb/2007 there is the "[691]-reflect host:N" option to + Yes, as of Feb/2007 there is the "[695]-reflect host:N" option to connect to the VNC server "host:N" (either another x11vnc or any other VNC server) and re-export it. VNC viewers then connect to the x11vnc(s) running -reflect. The -reflect option is the same as: "-rawfb vnc:host:N". See the - [692]-rawfb description under "VNC HOST" for more details. + [696]-rawfb description under "VNC HOST" for more details. You can replace "host:N" with "listen" or "listen:port" for reverse connections. @@ -8341,18 +8362,18 @@ rm -f $tmp re-exports via VNC to its clients C.) However, CopyRect and CursorShape encodings are preserved in the reflection and that helps. Dragging windows with the mouse can be a problem (especially if S is - not doing wireframing somehow, consider [693]-nodragging if the + not doing wireframing somehow, consider [697]-nodragging if the problem is severe) For a really fast reflector/repeater it would have to be implemented from scratch with performance in mind. See these other projects: - [694]http://sourceforge.net/projects/vnc-reflector/, - [695]http://www.tightvnc.com/projector/ (closed source?), + [698]http://sourceforge.net/projects/vnc-reflector/, + [699]http://www.tightvnc.com/projector/ (closed source?), Automation via Reverse Connections: Instead of having the R's connect directly to S and then the C's connect directly to the R they should use, some convenience can be achieved by using reverse - connections (the x11vnc "[696]"-connect host1,host2,..." option.) + connections (the x11vnc "[700]"-connect host1,host2,..." option.) Suppose all the clients "C" are started up in Listen mode: client1> vncviewer -listen client2> vncviewer -listen @@ -8411,7 +8432,7 @@ rm -f $tmp If the Solaris install is an older X-based one, there will be a menu for you to get a terminal window. From that window you might be able to retrieve x11vnc.static via wget, scp, or ftp. Remember to do "chmod - 755 ./x11vnc.static" and then find the -auth file as in [697]this FAQ. + 755 ./x11vnc.static" and then find the -auth file as in [701]this FAQ. If it is a Linux install that uses an X server (e.g. SuSE and probably Fedora), then you can often get a shell by pressing Ctrl-Alt-F2 or @@ -8420,7 +8441,7 @@ rm -f $tmp wget http://192.168.0.22/x11vnc.static chmod 755 ./x11vnc.static - Find the name of the auth file as in [698]this FAQ. (maybe run "ps + Find the name of the auth file as in [702]this FAQ. (maybe run "ps wwwwaux | grep auth".) Then run it like this: ./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile @@ -8429,7 +8450,7 @@ rm -f $tmp the display being :1, etc. If there is a firewall blocking incoming connections during the - install, use the [699]"-connect hostname" option option for a reverse + install, use the [703]"-connect hostname" option option for a reverse connection to the hostname running the VNC viewer in listen mode. Debian based installs are either console-text or console-framebuffer @@ -8491,7 +8512,7 @@ rm -f $tmp as 'for power users' or 'an Easter Egg'. As soon as text is highlighted it is set to the PRIMARY selection and so it is immediately ready for pasting, usually via the Middle Mouse Button or - "Shift+Insert". See [700]this jwz link for more information. + "Shift+Insert". See [704]this jwz link for more information. x11vnc's default behavior is to watch both CLIPBOARD and PRIMARY and whenever one of them changes, it sends the new text to connected @@ -8508,18 +8529,18 @@ rm -f $tmp You may not like these defaults. Here are ways to change the behavior: * If you don't want the Clipboard/Selection exchanged at all use the - [701]-nosel option. + [705]-nosel option. * If you want changes in PRIMARY to be ignored use the - [702]-noprimary option. + [706]-noprimary option. * If you want changes in CLIPBOARD to be ignored use the - [703]-noclipboard option. + [707]-noclipboard option. * If you don't want x11vnc to set PRIMARY to the "CutText" received - from viewers use the [704]-nosetprimary option. + from viewers use the [708]-nosetprimary option. * If you don't want x11vnc to set CLIPBOARD to the "CutText" - received from viewers use the [705]-nosetclipboard option. + received from viewers use the [709]-nosetclipboard option. - You can also fine-tune it a bit with the [706]-seldir dir option and - also [707]-input. + You can also fine-tune it a bit with the [710]-seldir dir option and + also [711]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -8531,7 +8552,7 @@ rm -f $tmp Yes, it is possible with a number of tools that record VNC and transform it to swf format or others. One such popular tool is - [708]pyvnc2swf. There are a number of [709]tutorials (broken link?) on + [712]pyvnc2swf. There are a number of [713]tutorials (broken link?) on how to do this. Another option is to use the vnc2mpg that comes in the LibVNCServer package. An important thing to remember when doing this is that tuning @@ -8546,11 +8567,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux.) - The [710]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [714]SSVNC Unix VNC viewer supports UltraVNC file transfer by use of a Java helper program. TightVNC file transfer is off by default, if you want to enable it use - the [711]-tightfilexfer option. + the [715]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -8573,7 +8594,7 @@ rm -f $tmp IMPORTANT: please understand if -ultrafilexfer or -tightfilexfer is specified and you run x11vnc as root for, say, inetd or display manager (gdm, kdm, ...) access and you do not have it switch users via - the [712]-users option, then VNC Viewers that connect are able to do + the [716]-users option, then VNC Viewers that connect are able to do filetransfer reads and writes as *root*. The UltraVNC and TightVNC settings can be toggled on and off inside @@ -8592,7 +8613,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [713]-ultrafilexfer which is an alias for the above option and + Or use [717]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -8604,18 +8625,18 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [714]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [718]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [715]-noultraext (the + To disable SingleWindow and ServerInput use [719]-noultraext (the others are managed by LibVNCServer.) See this option too: - [716]-noserverdpms. + [720]-noserverdpms. - Also, the [717]UltraVNC repeater proxy is supported for use with - reverse connections: "[718]-connect repeater://host:port+ID:NNNN". Use + Also, the [721]UltraVNC repeater proxy is supported for use with + reverse connections: "[722]-connect repeater://host:port+ID:NNNN". Use it for both plaintext and SSL connections. This mode can send any string before switching to the VNC protocol, and so could be used with other proxy/gateway tools. Also, a perl repeater implemention is here: - [719]ultravnc_repeater.pl + [723]ultravnc_repeater.pl Q-123: Can x11vnc emulate UltraVNC's Single Click helpdesk mode for @@ -8623,12 +8644,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [720]Single Click (SC) mode can be emulated fairly + Yes, UltraVNC's [724]Single Click (SC) mode can be emulated fairly well on Unix. We use the term "helpdesk" below, but it could be any sort of remote assistance you want to set up, e.g. something for Unix-using friends - or family to use. This includes [721]Mac OS X. + or family to use. This includes [725]Mac OS X. Assume you create a helpdesk directory "hd" on your website: http://www.mysite.com/hd (any website that you can upload files to @@ -8684,7 +8705,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc So I guess this is about 3-4 clicks (start a terminal and paste) and pressing "Enter" instead of "single click"... - See [722]this page for some variations on this method, e.g. how to add + See [726]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -8696,11 +8717,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc A bit of obscurity security could be put in with a -passwd, -rfbauth options, etc. (note that x11vnc will require a password even for - reverse connections.) More info [723]here. + reverse connections.) More info [727]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [724]router will have to be configured to + NAT/Firewall/Router the [728]router will have to be configured to redirect a port (i.e. 5500 or maybe different one if you like) to the vncviewer machine. If the vncviewer machine also has its own host-level firewall, you will have to open up the port there as well. @@ -8710,7 +8731,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc configuring a router to do a port redirection (i.e. on your side, the HelpDesk.) To avoid modifying either firewall/router, one would need some public (IP address reachable on the internet) redirection/proxy - service. Perhaps such a thing exists. [725]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [729]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -8746,7 +8767,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc As of Apr/2007 x11vnc supports reverse connections in SSL and so we can do this. On the Helpdesk side (Viewer) you will need STUNNEL or - better use the [726]Enhanced TightVNC Viewer (SSVNC) package we + better use the [730]Enhanced TightVNC Viewer (SSVNC) package we provide that automates all of the SSL for you. To do this create a file named "vncs" in the website "hd" directory @@ -8776,11 +8797,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc with the hostnames or IP addresses customized to your case. - The only change from the "vnc" above is the addition of the [727]-ssl + The only change from the "vnc" above is the addition of the [731]-ssl option to x11vnc. This will create a temporary SSL cert: openssl(1) will need to be installed on the user's end. A fixed SSL cert file could be used to avoid this (and provide some authentication; more - info [728]here.) + info [732]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -8789,7 +8810,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc But before that, the helpdesk operator needs to have "vncviewer -listen" running as before, however he needs an SSL tunnel at his end. - The easiest way to do this is use [729]Enhanced TightVNC Viewer + The easiest way to do this is use [733]Enhanced TightVNC Viewer (SSVNC). Start it, and select Options -> 'Reverse VNC Connection (-listen)'. Then UN-select 'Verify All Certs' (this can be enabled later if you want; you'll need the x11vnc SSL certificate), and click @@ -8819,7 +8840,7 @@ connect = localhost:5501 answer the prompts with whatever you want; you can take the default for all of them if you like. The openssl(1) package must be installed. - See [730]this link and [731]this one too for more info on SSL certs. + See [734]this link and [735]this one too for more info on SSL certs. This creates $HOME/.vnc/certs/server-self:mystunnel.pem, then you would change the "stunnel.cfg" to look something like: foreground = yes @@ -8840,7 +8861,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [732]here. + [736]here. OpenSSL libssl.so.0.9.7 problems: @@ -8850,7 +8871,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [733]details here. + You will find the [737]details here. Q-124: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -8859,7 +8880,7 @@ connect = localhost:5501 You will have to use an external network redirection for this. Filesystem mounting is not part of the VNC protocol. - We show a simple [734]Samba example here. + We show a simple [738]Samba example here. First you will need a tunnel to redirect the SMB requests from the remote machine to the one you sitting at. We use an ssh tunnel: @@ -8899,7 +8920,7 @@ d,ip=127.0.0.1,port=1139 far-away> smbumount /home/fred/smb-haystack-pub At some point we hope to fold some automation for SMB ssh redir setup - into the [735]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [739]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing.) @@ -8909,7 +8930,7 @@ d,ip=127.0.0.1,port=1139 You will have to use an external network redirection for this. Printing is not part of the VNC protocol. - We show a simple Unix to Unix [736]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [740]CUPS example here. Non-CUPS port redirections (e.g. LPD) should also be possible, but may be a bit more tricky. If you are viewing on Windows SMB and don't have a local cups server it may be trickier still (see below.) @@ -8991,7 +9012,7 @@ d,ip=127.0.0.1,port=1139 "localhost". At some point we hope to fold some automation for CUPS ssh redir setup - into the [737]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [741]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing.) @@ -9092,7 +9113,7 @@ or: the applications will fail to run because LD_PRELOAD will point to libraries of the wrong wordsize. * At some point we hope to fold some automation for esd or artsd ssh - redir setup into the [738]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [742]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing.) @@ -9104,14 +9125,14 @@ or: in Solaris, see Xserver(1) for how to turn it on via +kb), and so you won't hear them if the extension is not present. - If you don't want to hear the beeps use the [739]-nobell option. If + If you don't want to hear the beeps use the [743]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [740]redirector such as esd. + trying a [744]redirector such as esd. Q-128: Does x11vnc work with IPv6? - Currently the only way to do this is via [741]inetd. You configure + Currently the only way to do this is via [745]inetd. You configure x11vnc to be run from inetd or xinetd and instruct it to listen on an IPv6 address. For xinetd the setting "flags = IPv6" will be needed. @@ -9120,7 +9141,7 @@ or: connection.) Some sort of ipv4-to-ipv6 redirector tool (perhaps even a perl script) could be useful to avoid this. - Also note that not all VNC Viewers are [742]IPv6 enabled, so a + Also note that not all VNC Viewers are [746]IPv6 enabled, so a redirector could even be needed on the client side. @@ -9570,316 +9591,320 @@ References 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw 432. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords - 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 435. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int - 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 439. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 440. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer - 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 444. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 451. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy - 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit - 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect - 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 459. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess - 460. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess - 461. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 465. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 468. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 469. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 470. http://www.karlrunge.com/x11vnc/Xdummy - 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 472. http://www.karlrunge.com/x11vnc/xdm_one_shot.html - 473. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously - 474. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 480. http://www.karlrunge.com/x11vnc/shm_clear - 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 483. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm - 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb - 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 492. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 493. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc - 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 497. http://www.tightvnc.com/ - 498. http://www.karlrunge.com/x11vnc/ssvnc.html - 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 502. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching - 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds - 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-appshare - 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout - 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 517. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 522. http://minimyth.org/ - 523. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl - 524. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 530. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe - 531. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect - 532. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode - 533. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 436. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int + 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 440. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 442. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 443. http://www.karlrunge.com/x11vnc/ssvnc.html + 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create_xsrv + 448. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 455. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy + 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit + 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 463. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess + 464. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess + 465. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 472. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 473. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 474. http://www.karlrunge.com/x11vnc/Xdummy + 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 476. http://www.karlrunge.com/x11vnc/xdm_one_shot.html + 477. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously + 478. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 484. http://www.karlrunge.com/x11vnc/shm_clear + 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 487. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm + 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb + 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 496. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 497. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc + 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 501. http://www.tightvnc.com/ + 502. http://www.karlrunge.com/x11vnc/ssvnc.html + 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 506. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching + 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds + 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-appshare + 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout + 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 521. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 526. http://minimyth.org/ + 527. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl + 528. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 534. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 535. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect + 536. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode 537. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect - 541. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe - 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip - 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 546. http://www.karlrunge.com/x11vnc/index.html#beta-test - 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 548. http://www.karlrunge.com/x11vnc/ssvnc.html - 549. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop - 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap - 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr - 552. http://www.virtualgl.org/About/TurboVNC - 553. http://www.virtualgl.org/ - 554. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 557. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 558. http://www.karlrunge.com/x11vnc/ssvnc.html - 559. http://www.karlrunge.com/x11vnc/bins - 560. http://www.karlrunge.com/x11vnc/ssvnc.html - 561. http://www.virtualgl.org/About/Reports - 562. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 566. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode - 567. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 568. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks - 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 574. http://www.karlrunge.com/x11vnc/ssvnc.html - 575. http://www.tightvnc.com/ - 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer - 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 584. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 585. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 541. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect + 545. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip + 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 550. http://www.karlrunge.com/x11vnc/index.html#beta-test + 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 552. http://www.karlrunge.com/x11vnc/ssvnc.html + 553. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap + 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 556. http://www.virtualgl.org/About/TurboVNC + 557. http://www.virtualgl.org/ + 558. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 561. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 562. http://www.karlrunge.com/x11vnc/ssvnc.html + 563. http://www.karlrunge.com/x11vnc/bins + 564. http://www.karlrunge.com/x11vnc/ssvnc.html + 565. http://www.virtualgl.org/About/Reports + 566. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 570. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode + 571. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 572. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks + 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 578. http://www.karlrunge.com/x11vnc/ssvnc.html + 579. http://www.tightvnc.com/ + 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 588. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 589. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 593. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 595. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 597. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 599. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 609. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 612. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock - 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes + 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 613. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 616. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock + 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 626. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling - 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 628. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html - 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 638. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm - 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 642. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama - 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 647. http://www.karlrunge.com/x11vnc/ssvnc.html - 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate - 649. http://www.jwz.org/xscreensaver/man1.html - 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms - 651. http://www.beryl-project.org/ - 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 653. http://www.dslinux.org/blogs/pepsiman/?p=73 - 654. http://minimyth.org/ - 655. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 656. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 657. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 658. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 660. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 663. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 664. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 665. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 666. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 668. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 669. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 670. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 671. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware - 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 673. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab - 680. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 684. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 685. http://www.testplant.com/products/vine_server/OS_X - 686. http://www.apple.com/remotedesktop/ - 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb - 689. http://fredrik.hubbe.net/x2vnc.html - 690. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc - 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect - 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 694. http://sourceforge.net/projects/vnc-reflector/ - 695. http://www.tightvnc.com/projector/ - 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 697. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 698. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 700. http://www.jwz.org/doc/x-cut-and-paste.html - 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noclipboard - 704. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetprimary - 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetclipboard - 706. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 708. http://www.unixuser.org/~euske/vnc2swf/ - 709. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ - 710. http://www.karlrunge.com/x11vnc/ssvnc.html - 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer - 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 713. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 630. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling + 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 632. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html + 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 642. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm + 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 646. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama + 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 651. http://www.karlrunge.com/x11vnc/ssvnc.html + 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 653. http://www.jwz.org/xscreensaver/man1.html + 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 655. http://www.beryl-project.org/ + 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 657. http://www.dslinux.org/blogs/pepsiman/?p=73 + 658. http://minimyth.org/ + 659. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 660. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 661. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 663. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 667. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 668. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 669. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 670. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 672. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 673. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 674. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 675. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware + 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 677. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 684. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 689. http://www.testplant.com/products/vine_server/OS_X + 690. http://www.apple.com/remotedesktop/ + 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 693. http://fredrik.hubbe.net/x2vnc.html + 694. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc + 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 698. http://sourceforge.net/projects/vnc-reflector/ + 699. http://www.tightvnc.com/projector/ + 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 701. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 702. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 704. http://www.jwz.org/doc/x-cut-and-paste.html + 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 706. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noclipboard + 708. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetprimary + 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetclipboard + 710. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 712. http://www.unixuser.org/~euske/vnc2swf/ + 713. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ 714. http://www.karlrunge.com/x11vnc/ssvnc.html - 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext - 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 717. http://www.uvnc.com/addons/repeater.html - 718. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 719. http://www.karlrunge.com/x11vnc/ultravnc_repeater.pl - 720. http://www.uvnc.com/addons/singleclick.html - 721. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx - 722. http://www.karlrunge.com/x11vnc/single-click.html - 723. http://www.karlrunge.com/x11vnc/single-click.html - 724. http://www.karlrunge.com/x11vnc/index.html#firewalls - 725. http://sc.uvnc.com/ - 726. http://www.karlrunge.com/x11vnc/ssvnc.html - 727. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 728. http://www.karlrunge.com/x11vnc/single-click.html - 729. http://www.karlrunge.com/x11vnc/ssvnc.html - 730. http://www.karlrunge.com/x11vnc/single-click.html - 731. http://www.karlrunge.com/x11vnc/ssl.html + 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 717. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 718. http://www.karlrunge.com/x11vnc/ssvnc.html + 719. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 720. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 721. http://www.uvnc.com/addons/repeater.html + 722. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 723. http://www.karlrunge.com/x11vnc/ultravnc_repeater.pl + 724. http://www.uvnc.com/addons/singleclick.html + 725. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx + 726. http://www.karlrunge.com/x11vnc/single-click.html + 727. http://www.karlrunge.com/x11vnc/single-click.html + 728. http://www.karlrunge.com/x11vnc/index.html#firewalls + 729. http://sc.uvnc.com/ + 730. http://www.karlrunge.com/x11vnc/ssvnc.html + 731. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl 732. http://www.karlrunge.com/x11vnc/single-click.html - 733. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems - 734. http://www.samba.org/ - 735. http://www.karlrunge.com/x11vnc/ssvnc.html - 736. http://www.cups.org/ - 737. http://www.karlrunge.com/x11vnc/ssvnc.html - 738. http://www.karlrunge.com/x11vnc/ssvnc.html - 739. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 740. http://www.karlrunge.com/x11vnc/faq.html#faq-sound - 741. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd - 742. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html + 733. http://www.karlrunge.com/x11vnc/ssvnc.html + 734. http://www.karlrunge.com/x11vnc/single-click.html + 735. http://www.karlrunge.com/x11vnc/ssl.html + 736. http://www.karlrunge.com/x11vnc/single-click.html + 737. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 738. http://www.samba.org/ + 739. http://www.karlrunge.com/x11vnc/ssvnc.html + 740. http://www.cups.org/ + 741. http://www.karlrunge.com/x11vnc/ssvnc.html + 742. http://www.karlrunge.com/x11vnc/ssvnc.html + 743. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 744. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 745. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 746. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -11521,17 +11546,19 @@ stAllVncCerts=yes [R,NE,L] /usr/local/bin/x11vnc -inetd -oa /var/log/x11vnc-15.log \ -ssl SAVE -http -unixpw -localhost -users unixpw= \ - -display WAIT:cmd=FINDDISPLAY - - this way the user must supply his Unix username and password and then - his display and Xauthority data on that machine will be located and - returned to x11vnc to allow it to attach. If he doesn't have a display - running on that machine or he fails to log in correctly, the - connection will be dropped. - - The variant "[30]-display WAIT:cmd=FINDCREATEDISPLAY" will actually - create a (virtual or real) X server session for the user if one - doesn't already exist. See [31]for details. + -find + + (we have used the alias [30]-find for "-display + WAIT:cmd=FINDDISPLAY".) This way the user must supply his Unix + username and password and then his display and Xauthority data on that + machine will be located and returned to x11vnc to allow it to attach. + If he doesn't have a display running on that machine or he fails to + log in correctly, the connection will be dropped. + + The variant "[31]-display WAIT:cmd=FINDCREATEDISPLAY" (aliased by + "[32]-create") will actually create a (virtual or real) X server + session for the user if one doesn't already exist. See [33]here for + details. To enable inetd operation for the non-HTTPS Java viewer download (port 5815 in the above httpd.conf example) you will need to run x11vnc in @@ -11542,8 +11569,8 @@ stAllVncCerts=yes [R,NE,L] -http_ssl -display WAIT:cmd=HTTPONCE where the long inetd.conf line has been split. Note how the - [32]-http_ssl tries to automatically find the .../classes/ssl - subdirectory. This requires the [33]-prog option available in x11vnc + [34]-http_ssl tries to automatically find the .../classes/ssl + subdirectory. This requires the [35]-prog option available in x11vnc 0.8.4 (a shell script wrapper, e.g. /usr/local/bin/x11vnc_http.sh can be used to work around this). @@ -11602,7 +11629,7 @@ stAllVncCerts=yes [R,NE,L] - The redirection could also be done at the application level using a TCP redirect program (e.g. ip_relay or fancier ones). Evidently more careful internal hostname checking, etc., could be performed by the - special purpose application to add security. See [34]connect_switch + special purpose application to add security. See [36]connect_switch which is somewhat related. - One might imagine the ProxyPass could be done for the VNC traffic as @@ -11734,11 +11761,13 @@ References 27. http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#selfcert 28. http://www.karlrunge.com/x11vnc/ssl-portal.html#tricks 29. http://www.karlrunge.com/x11vnc/ssl-single-443.html - 30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 31. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin - 32. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_ssl - 33. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-prog - 34. http://www.karlrunge.com/x11vnc/ssl-single-443.html + 30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 31. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 32. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 33. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 34. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_ssl + 35. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-prog + 36. http://www.karlrunge.com/x11vnc/ssl-single-443.html ======================================================================= http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html: @@ -12923,7 +12952,7 @@ x11vnc: a VNC server for real X displays Here are all of x11vnc command line options: % x11vnc -opts (see below for -help long descriptions) -x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2009-12-27 +x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2009-12-28 x11vnc options: -display disp -auth file -N @@ -12947,7 +12976,7 @@ x11vnc options: -unixpw_nis [list] -unixpw_cmd cmd -find -finddpy -listdpy -findauth [disp] -create -xdummy -xvnc - -xvnc_redirect -xdummy_xvfb -create_x str + -xvnc_redirect -xdummy_xvfb -create_xsrv str -svc -svc_xdummy -svc_xvnc -svc_xdummy_xvfb -xdmsvc -sshxdmsvc -unixpw_system_greeter -redirect port -display WAIT:... @@ -13051,7 +13080,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2009-12-27 +x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2009-12-28 (type "x11vnc -opts" to just list the options.) @@ -14103,9 +14132,10 @@ Options: -xvnc_redirect As in -create, except Xvnc.redirect instead of Xvfb. -xdummy_xvfb Sets WAIT:cmd=FINDCREATEDISPLAY-Xdummy,Xvfb --create_x str Sets WAIT:cmd=FINDCREATEDISPLAY-<str> Can be on cmdline +-create_xsrv str Sets WAIT:cmd=FINDCREATEDISPLAY-<str> Can be on cmdline after anything that sets WAIT:.. and other things (e.g. -svc, -xdmsvc) to adjust the X server list. + Example: -svc ... -create_xsrv Xdummy,X -svc Terminal services mode based on SSL access. Alias for -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb -unixpw -users diff --git a/x11vnc/help.c b/x11vnc/help.c index 40fd3ec..0de7fc7 100644 --- a/x11vnc/help.c +++ b/x11vnc/help.c @@ -1119,9 +1119,10 @@ void print_help(int mode) { "-xvnc_redirect As in -create, except Xvnc.redirect instead of Xvfb.\n" "-xdummy_xvfb Sets WAIT:cmd=FINDCREATEDISPLAY-Xdummy,Xvfb\n" "\n" -"-create_x str Sets WAIT:cmd=FINDCREATEDISPLAY-<str> Can be on cmdline\n" +"-create_xsrv str Sets WAIT:cmd=FINDCREATEDISPLAY-<str> Can be on cmdline\n" " after anything that sets WAIT:.. and other things\n" " (e.g. -svc, -xdmsvc) to adjust the X server list.\n" +" Example: -svc ... -create_xsrv Xdummy,X\n" "\n" "-svc Terminal services mode based on SSL access. Alias for\n" " -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb -unixpw -users\n" diff --git a/x11vnc/misc/Xdummy b/x11vnc/misc/Xdummy index 3abc199..452eb4d 100755 --- a/x11vnc/misc/Xdummy +++ b/x11vnc/misc/Xdummy @@ -5,17 +5,19 @@ # # Run "Xdummy -help" for more info. # -xserver="" -geom="" -geom="" install="" uninstall="" +runit=1 +prconf="" +notweak="" root="" +nosudo="" +xserver="" +geom="" +depth="" debug="" strace="" -runit=1 -prconf="" -noconf="" +cmdline_config="" PATH=$PATH:/bin:/usr/bin export PATH @@ -24,55 +26,62 @@ program=`basename "$0"` help () { ${PAGER:-more} << END +$program: -$program: a hack to run a stock Xorg(1) or XFree86(1) X server with the -"dummy" video driver such that it AVOIDS the Linux VT switching, keyboard -mouse conflicts, etc associated with normal use of "dummy". + A hack to run a stock Xorg(1) or XFree86(1) X server with the "dummy" + (RAM-only framebuffer) video driver such that it AVOIDS the Linux VT + switching, opening device files in /dev, keyboard and mouse conflicts, + and other problems associated with the normal use of "dummy". -In other words, try to make Xorg/XFree86 with the Device "dummy" driver -act more like Xvfb(1). + In other words, it tries to make Xorg/XFree86 with the "dummy" + device driver act more like Xvfb(1). -To achieve this, while running the real Xserver $program intercepts system -and library calls via the LD_PRELOAD method and modifies the behavior -to make it work correctly (i.e. avoid the VT stuff). LD_PRELOAD tricks -are usually "clever hacks" and so might not work in all situations or -break when something changes. + The primary motivation for the Xdummy script is to provide a virtual X + server for x11vnc but with more features than Xvfb (or Xvnc); however + it could be used for other reasons (e.g. better automated testing + than with Xvfb.) One nice thing is the dummy server supports RANDR + dynamic resizing while Xvfb does not. -The primary motivation for the Xdummy script is to provide a virtual X -server for x11vnc but with more features than Xvfb (or Xvnc), however -it could be used for other reasons (e.g. better automated testing than -with Xvfb). A nice by-product is the dummy server supports RANDR dynamic -resizing while Xvfb does not. So, for example x11vnc+Xdummy terminal -services are a little better than x11vnc+Xvfb. + So, for example, x11vnc+Xdummy terminal services are a little better + than x11vnc+Xvfb. -This program does not need to be run as root as of 12/2009. However, -if there are problems for certain situations it may perform better -if run as root (-root option.) + To achieve this, while running the real Xserver $program intercepts + system and library calls via the LD_PRELOAD method and modifies + the behavior to make it work correctly (e.g. avoid the VT stuff.) + LD_PRELOAD tricks are usually "clever hacks" and so might not work + in all situations or break when something changes. -Also, gcc/cc is required to compile the LD_PRELOAD shared object. -See -install and -uninstall described below. + This program does not need to be run as root as of 12/2009. However, + if there are problems for certain situations (usually older servers) + it may perform better if run as root (use the -root option.) + Also, gcc/cc and other build tools are required for this script to + be able to compile the LD_PRELOAD shared object. Be sure they are + installed on the system. See -install and -uninstall described below. -Your Linux distribution may not install the dummy driver by default, e.g: - - /usr/lib/xorg/modules/drivers/dummy_drv.so - -some have it in a package named xserver-xorg-video-dummy you need -to install. + Your Linux distribution may not install the dummy driver by default, + e.g: + /usr/lib/xorg/modules/drivers/dummy_drv.so + + some have it in a package named xserver-xorg-video-dummy you that + need to install. Usage: - $program <${program}-args> [--] <Xserver-args> + $program <${program}-args> <Xserver-args> + (actually, the arguments can be supplied in any order.) Examples: + $program -install + $program :1 - $program -debug -tmpdir ~/mytmp :1 + $program -debug :1 - $program -install + $program -tmpdir ~/mytmp :1 -nolisten tcp startx example: @@ -95,6 +104,8 @@ xdm example: :1 local /usr/local/dummy/Xdummy :1 -debug :2 local /usr/local/dummy/Xdummy :2 -debug + (-debug is optional) + gdm/kdm example: TBD. @@ -102,11 +113,12 @@ gdm/kdm example: Root permission and x11vnc: Update: as of 12/2009 this program no longer must be run as root. + So try it as non-root before running it as root and/or the + following schemes. - However, in some circumstances program may need to be run as - root. If so, one could run x11vnc as root with -unixpw (it - switches to the user that logs in) and that may be OK, some - other ideas: + In some circumstances X server program may need to be run as root. + If so, one could run x11vnc as root with -unixpw (it switches + to the user that logs in) and that may be OK, some other ideas: - add this to sudo via visudo: @@ -145,25 +157,38 @@ Options: ${program}-args: -install Compile the LD_PRELOAD shared object and install it - next to the $program script file as: $0.so + next to the $program script file as: + + $0.so When that file exists it is used as the LD_PRELOAD shared object without recompiling. Otherwise, each time $program is run the LD_PRELOAD shared - object is compiled as a file in /tmp (or -tmpdir). + object is compiled as a file in /tmp (or -tmpdir) + + If you set the environment variable + INTERPOSE_GETUID=1 when building, then when + $program is run as an ordinary user, the shared + object will interpose getuid() calls and pretend + to be root. Otherwise it doesn't pretend to + be root. + + You can also set the CFLAGS environment variable + to anything else you want on the compile cmdline. + + -uninstall Remove the file: + + $0.so - -uninstall Remove the file: $0.so The LD_PRELOAD shared object will then be compiled each time this program is run. - Note: the X server is not started under -install or -uninstall. + The X server is not started under -install, -uninstall, or -prconf. - :N The DISPLAY can be the first $program argument. - It is passed to the real X server. This is to - aid use with startx(1), xinit(1), xdm(1), etc. - If one is not provided it tries to choose one - automatically. + :N The DISPLAY (e.g. :15) is often the first + argument. It is passed to the real X server and + also used by the Xdummy script as an identifier. -geom geom1[,geom2...] Take the geometry (e.g. 1024x768) or list of geometries and insert them into the @@ -171,6 +196,13 @@ Options: config file. Use this to have a smaller geometry than the one in the system config file. + -depth n Use pixel color depth n (e.g. 8, 16, or 24). This + makes sure the X config file has a Screen.Display + subsection of this depth. Note this option is + ALSO passed to the X server. + + -DEPTH n Same as -depth, except not passed to X server. + -tmpdir dir Specify a temporary directory, owned by you and only writable by you. This is used in place of /tmp/Xdummy.\$USER/.. to place the $program.so @@ -179,56 +211,70 @@ Options: -nonroot Run in non-root mode (working 12/2009, now default) -root Run as root (may still be needed in some - environments.) + environments.) Same as XDUMMY_RUN_AS_ROOT=1. -nosudo Do not try to use sudo(1) when re-running as root, use su(1) instead. -xserver path Specify the path to the Xserver to use. Default is to try "Xorg" first and then "XFree86". If - those are not in \$PATH, use these locations: + those are not in \$PATH, it tries these locations: + /usr/bin/Xorg /usr/X11R6/bin/Xorg /usr/X11R6/bin/XFree86 -n Do not run the command to start the X server, just show the command that $program would run. The LD_PRELOAD shared object will be built, - if needed. + if needed. Also note any XDUMMY* environment + variables that need to be set. - -prconf Print, to stdout, the tweaked Xorg or XFree86 + -prconf Print, to stdout, the tweaked Xorg/XFree86 config file (-config and -xf86config server - options, respectively). The Xserver is not + options, respectively.) The Xserver is not started. - -noconf Do not tweak the Xorg or XFree86 config file - (system or server command line) at all. It is - up to you to make sure it is a working config - file (e.g. "dummy" driver, etc). Perhaps you - want to use a file based on -prconf output. + -notweak Do not tweak (modify) the Xorg/XFree86 config file + (system or server command line) at all. The -geom + and similar config file modifications are ignored. + + It is up to you to make sure it is a working + config file (e.g. "dummy" driver, etc.) + Perhaps you want to use a file based on the + -prconf output. -debug Extra debugging output. - -strace strace(1) the Xserver process (for troubleshooting). + -strace strace(1) the Xserver process (for troubleshooting.) + -ltrace ltrace(1) instead of strace (can be slow.) -h, -help Print out this help. Xserver-args: - Most of the Xorg and XFree86 options will work. Important ones - that may be supplied if missing: + Most of the Xorg and XFree86 options will work and are simply + passed along if you supply them. Important ones that may be + supplied if missing: :N X Display number for server to use. vtNN Linux virtual terminal (VT) to use (a VT is currently - still used, just not switched to and from). + still used, just not switched to and from.) -config file Driver "dummy" tweaked config file, a -xf86config file number of settings are tweaked besides Driver. - If -config/-xf86config is not given, the system one is used. - Any settings in the config file that are not consistent with - "dummy" mode will be overwritten (unless -noconf is used). + If -config/-xf86config is not given, the system one + (e.g. /etc/X11/xorg.conf) is used. If the system one cannot be + found, a built-in one is used. Any settings in the config file + that are not consistent with "dummy" mode will be overwritten + (unless -notweak is specified.) + + If "file" is only a basename (e.g. "xorg.dummy.conf") with no /'s, + then no tweaking of it is done: the X server will look for that + basename via its normal search algorithm. If the found file does + not refer to the "dummy" driver, etc, then the X server will fail. Notes: @@ -236,17 +282,20 @@ Notes: well in this mode, but it is evidently not intended for end-users. So it could be removed or broken at any time. - If the display Xserver-arg (e.g. :1) is not given, or ":" or ":9999" - is given that indicates $program should try to find a free one. + If the display Xserver-arg (e.g. :1) is not given, or ":" is given + that indicates $program should try to find a free one (based on + tcp ports.) If the display virtual terminal, VT, (e.g. vt9) is not given that - indicates $program should try to find a free one (or guess a high one). + indicates $program should try to find a free one (or guess a high one.) This program is not completely secure WRT files in /tmp (but it tries - to a good degree). Better is to use the -tmpdir option to supply a + to a good degree.) Better is to use the -tmpdir option to supply a directory only writable by you. Even better is to get rid of users on the local machine you do not trust :-) + Set XDUMMY_SET_XV=1 to turn on debugging output for this script. + END } @@ -311,8 +360,6 @@ if [ "X$XDUMMY_SU_EXEC" = "X" -a "X$root" = "X1" -a "X`id -u`" != "X0" ]; then dosu="" elif [ "X$arg" = "X-prconf" ]; then dosu="" - elif [ "X$arg" = "X--" ]; then - break fi done if [ $dosu ]; then @@ -337,6 +384,7 @@ if [ "X$XDUMMY_SU_EXEC" = "X" -a "X$root" = "X1" -a "X`id -u`" != "X0" ]; then exec su -c "$0 $*" fi fi + # DONE: exit fi fi @@ -345,17 +393,21 @@ fi # disp="" args="" +cmdline_config="" # Process Xdummy args: # while [ "X$1" != "X" ] do + if [ "X$1" = "X-config" -o "X$1" = "X-xf86config" ]; then + cmdline_config="$2" + fi case $1 in ":"*) disp=$1 ;; - "-install") install=1 + "-install") install=1; runit="" ;; - "-uninstall") uninstall=1 + "-uninstall") uninstall=1; runit="" ;; "-n") runit="" ;; @@ -363,9 +415,11 @@ do ;; "-norun") runit="" ;; - "-prconf") prconf=1 + "-prconf") prconf=1; runit="" ;; - "-noconf") noconf=1 + "-notweak") notweak=1 + ;; + "-noconf") notweak=1 ;; "-nonroot") root="" ;; @@ -378,21 +432,26 @@ do "-uid") XDUMMY_UID="$2"; shift export XDUMMY_UID ;; - "-geom"*) geom="$2"; shift + "-geom") geom="$2"; shift + ;; + "-depth") depth="$2"; args="$args -depth $2"; + shift ;; - "-depth") depth="$2"; shift + "-DEPTH") depth="$2"; shift ;; "-tmpdir") XDUMMY_TMPDIR="$2"; shift ;; - "-debug") debug=1 + "-debug") debug=1 ;; "-nodebug") debug="" ;; "-strace") strace=1 ;; - "-h"*) help; exit 0 + "-ltrace") strace=2 + ;; + "-h") help; exit 0 ;; - "--") shift; break + "-help") help; exit 0 ;; *) args="$args $1" ;; @@ -433,32 +492,45 @@ fi # Function to compile the LD_PRELOAD shared object: # make_so() { - # extract code embedded in this script into a tmp C file: n1=`grep -n '^#code_begin' $0 | head -1 | awk -F: '{print $1}'` n2=`grep -n '^#code_end' $0 | head -1 | awk -F: '{print $1}'` n1=`expr $n1 + 1` dn=`expr $n2 - $n1` - tmp=$tdir/Xdummy.$$.c + tmp=$tdir/Xdummy.$RANDOM$$.c rm -f $tmp if [ -e $tmp -o -h $tmp ]; then warn "$tmp still exists." exit 1 fi + touch $tmp || exit 1 tail -n +$n1 $0 | head -n $dn > $tmp # compile it to Xdummy.so: + if [ -f $SO ]; then + mv $SO $SO.$$ + rm -f $SO.$$ + fi rm -f $SO touch $SO if [ ! -f $SO ]; then SO=$tdir/Xdummy.$user.so warn "warning switching LD_PRELOAD shared object to: $SO" fi + + if [ -f $SO ]; then + mv $SO $SO.$$ + rm -f $SO.$$ + fi rm -f $SO # we assume gcc: - cc -shared -fPIC -o $SO $tmp + if [ "X$INTERPOSE_GETUID" = "X1" ]; then + CFLAGS="$CFLAGS -DINTERPOSE_GETUID" + fi + echo "$program:" cc -shared -fPIC $CFLAGS -o $SO $tmp + cc -shared -fPIC $CFLAGS -o $SO $tmp rc=$? rm -f $tmp if [ $rc != 0 ]; then @@ -485,6 +557,10 @@ if [ "X$install" != "X" -o "X$uninstall" != "X" ]; then if [ -e $SO -o -h $SO ]; then warn "$program: removing $SO" fi + if [ -f $SO ]; then + mv $SO $SO.$$ + rm -f $SO.$$ + fi rm -f $SO if [ -e $SO -o -h $SO ]; then warn "warning: $SO still exists." @@ -736,37 +812,12 @@ fi # Decide flavor of Xserver: # stype=`basename "$xserver"` -if echo "$stype" | grep -i xorg > /dev/null; then - stype=xorg -else +if echo "$stype" | grep -i xfree86 > /dev/null; then stype=xfree86 +else + stype=xorg fi -# Work out config file and tweak it. -# -next="" -config="" -got_config="" -for arg in $* -do - if [ $next ]; then - config="$arg" - got_config=1 - break - fi - if [ "X$arg" = "X-xf86config" ]; then - if [ "X$stype" = "X" ]; then - stype="xfree86" - fi - next=1 - elif [ "X$arg" = "X-config" ]; then - if [ "X$stype" = "X" ]; then - stype="xorg" - fi - next=1 - fi -done - tweak_config() { in="$1" config2="$XDUMMY_TMPDIR/xdummy_modified_xconfig.conf" @@ -795,6 +846,10 @@ tweak_config() { $geom = $tmp; } while (<>) { + if ($ENV{XDUMMY_NOTWEAK}) { + print $_; + next; + } $n++; if (/^\s*#/) { # pass comments straight thru @@ -967,6 +1022,9 @@ tweak_config() { } print; } + if ($ENV{XDUMMY_NOTWEAK}) { + exit; + } # create any crucial sections that are missing: if (! exists($sects{serverflags})) { print "\n##Xdummy:##\n"; @@ -1021,14 +1079,31 @@ tweak_config() { '; } -if [ ! $noconf ]; then +# Work out config file and tweak it. +# +if [ "X$cmdline_config" = "X" ]; then + : +elif echo "$cmdline_config" | grep '/' > /dev/null; then + : +else + # ignore basename only case (let server handle it) + cmdline_config="" + notweak=1 +fi + +config=$cmdline_config + +if [ "X$notweak" = "X1" -a "X$root" = "X" -a -f "$cmdline_config" ]; then + # if not root we need to copy (but not tweak) the specified config. + XDUMMY_NOTWEAK=1 + export XDUMMY_NOTWEAK + notweak="" +fi + +if [ ! $notweak ]; then # tweaked config will be put in $config2: config2="" - if [ "X$config" != "X" ]; then - if [ ! -f $config ]; then - config="/etc/X11/$config" - fi - else + if [ "X$config" = "X" ]; then # use the default one: if [ "X$stype" = "Xxorg" ]; then config=/etc/X11/xorg.conf @@ -1052,6 +1127,7 @@ if [ ! $noconf ]; then if [ ! -f $config ]; then config="$XDUMMY_TMPDIR/xorg.conf" + warn "$program: using minimal built-in xorg.conf settings." cat > $config <<END Section "ServerLayout" @@ -1119,7 +1195,7 @@ END fi # now we need to get our tweaked config file onto the command line: - if [ ! $got_config ]; then + if [ "X$cmdline_config" = "X" ]; then # append to cmdline (FUBAR will be substituted below.) if [ "X$stype" = "Xxorg" ]; then args="$args -config FUBAR" @@ -1142,7 +1218,7 @@ fi if [ $prconf ]; then warn "" - warn "The Xorg/XFree86 server config file is:" + warn "Printing out the Xorg/XFree86 server config file:" warn "" if [ "X$config2" = "X" ]; then warn "NO CONFIG GENERATED." @@ -1195,7 +1271,11 @@ if [ "X$debug" != "X" -o "X$runit" = "X" ]; then fi if [ $strace ]; then - strace -f env LD_PRELOAD=$SO $xserver $disp $args $vt + if [ "X$strace" = "X2" ]; then + ltrace -f env LD_PRELOAD=$SO $xserver $disp $args $vt + else + strace -f env LD_PRELOAD=$SO $xserver $disp $args $vt + fi else exec env LD_PRELOAD=$SO $xserver $disp $args $vt fi @@ -1597,6 +1677,10 @@ int chown(const char *path, uid_t owner, gid_t group) { return(real_chown(path, owner, group)); } +extern int *__errno_location (void); +#ifndef ENODEV +#define ENODEV 19 +#endif int ioperm(unsigned long from, unsigned long num, int turn_on) { static int (*real_ioperm)(unsigned long, unsigned long, int) = NULL; @@ -1610,6 +1694,12 @@ int ioperm(unsigned long from, unsigned long num, int turn_on) { if (root) { return(real_ioperm(from, num, turn_on)); } + if (from == 0 && num == 1024 && turn_on == 1) { + /* we want xf86EnableIO to fail */ + if (debug) fprintf(stderr, "IOPERM: setting ENODEV.\n"); + *__errno_location() = ENODEV; + return -1; + } return 0; } @@ -1627,7 +1717,7 @@ int iopl(int level) { return 0; } -#if 0 +#ifdef INTERPOSE_GETUID /* * we got things to work w/o pretending to be root. diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index f40e5e7..8678aaa 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "December 2009" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.9.10, lastmod: 2009-12-27 + version: 0.9.10, lastmod: 2009-12-28 .SH SYNOPSIS .B x11vnc [OPTION]... @@ -1251,11 +1251,12 @@ As in \fB-create,\fR except Xvnc.redirect instead of Xvfb. .IP Sets WAIT:cmd=FINDCREATEDISPLAY-Xdummy,Xvfb .PP -\fB-create_x\fR \fIstr\fR +\fB-create_xsrv\fR \fIstr\fR .IP Sets WAIT:cmd=FINDCREATEDISPLAY-<str> Can be on cmdline after anything that sets WAIT:.. and other things (e.g. \fB-svc,\fR \fB-xdmsvc)\fR to adjust the X server list. +Example: \fB-svc\fR ... \fB-create_xsrv\fR Xdummy,X .PP \fB-svc\fR .IP diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index b4c0602..87fdb1a 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -2221,7 +2221,7 @@ int main(int argc, char* argv[]) { use_dpy = strdup("WAIT:cmd=FINDCREATEDISPLAY-Xvfb"); continue; } - if (!strcmp(arg, "-create_x")) { + if (!strcmp(arg, "-create_xsrv")) { CHECK_ARGC use_dpy = (char *) malloc(strlen(argv[i+1])+100); sprintf(use_dpy, "WAIT:cmd=FINDCREATEDISPLAY-%s", argv[++i]); diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c index ce31d67..6673771 100644 --- a/x11vnc/x11vnc_defs.c +++ b/x11vnc/x11vnc_defs.c @@ -47,7 +47,7 @@ int xtrap_base_event_type = 0; int xdamage_base_event_type = 0; /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.9.10 lastmod: 2009-12-27"; +char lastmod[] = "0.9.10 lastmod: 2009-12-28"; /* X display info */ |