diff options
| author | runge <runge@karlrunge.com> | 2010-02-22 22:33:50 -0500 |
|---|---|---|
| committer | runge <runge@karlrunge.com> | 2010-02-22 22:33:50 -0500 |
| commit | 521b9d98a4b772689061b24bcfd57dcce976aacc (patch) | |
| tree | a0e4ed61ae608dd0bdca48d95d3e5960f46253c2 /x11vnc/README | |
| parent | 909683fd970fa842a12d2437ea30a624caf2e761 (diff) | |
| download | libtdevnc-521b9d98a4b772689061b24bcfd57dcce976aacc.tar.gz libtdevnc-521b9d98a4b772689061b24bcfd57dcce976aacc.zip | |
classes/ssl: Java SSL applet viewer now works with certificate chains.
x11vnc: Printout option -sslScripts. Suggest -auth guess in error message. Set fake_screen width and height. Test for +kb in Xvfb.
Diffstat (limited to 'x11vnc/README')
| -rw-r--r-- | x11vnc/README | 2259 |
1 files changed, 1258 insertions, 1001 deletions
diff --git a/x11vnc/README b/x11vnc/README index dc3b995..6aa88b4 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -2,7 +2,7 @@ Copyright (C) 2002-2010 Karl J. Runge <runge@karlrunge.com> All rights reserved. -x11vnc README file Date: Thu Jan 7 23:16:08 EST 2010 +x11vnc README file Date: Mon Feb 22 22:22:33 EST 2010 The following information is taken from these URLs: @@ -916,7 +916,7 @@ make created. - Here are some features that appeared in the 0.9.9 release: + Here are some features that appeared in the 0.9.9 release (Dec/2009): * The [123]-unixpw_system_greeter option, when used in combined unixpw and XDMCP FINDCREATEDISPLAY mode (for example: [124]-xdmsvc), enables the user to press Escape to jump directly @@ -988,7 +988,7 @@ make item's active zone. More information [146]can be found here. - Here are some features that appeared in the 0.9.8 release: + Here are some features that appeared in the 0.9.8 release (Jul/2009): * Stability improvements to [147]-threads mode. Running x11vnc this way is more reliable now. Threaded operation sometimes gives better interactive response and faster updates: try it out. The @@ -1013,7 +1013,7 @@ make * The [151]-clip mode works under [152]-rawfb. - Here are some features that appeared in the 0.9.7 release: + Here are some features that appeared in the 0.9.7 release (Mar/2009): * Support for polling Linux Virtual Terminals (also called virtual consoles) directly instead of using /dev/fb. The option to use is, for example, "-rawfb vt2" for Virtual Terminal 2, etc. In this @@ -1037,7 +1037,7 @@ make now work. - Here are some features that appeared in the 0.9.6 release: + Here are some features that appeared in the 0.9.6 release (Dec/2008): * Support for [159]VeNCrypt SSL/TLS encrypted connections. It is enabled by default in the [160]-ssl mode. VNC Viewers like vinagre, gvncviewer/gtk-vnc, the vencrypt package, [161]SSVNC, and @@ -1107,7 +1107,7 @@ LAY (e.g. [183]GDM.) - Here are some features that appeared in the 0.9.5 release: + Here are some features that appeared in the 0.9.5 release (Oct/2008): * Symmetric key [184]encryption ciphers. ARC4, AES-128, AES-256, blowfish, and 3des are supported. Salt and initialization vector seeding is provided. These compliment the more widely used SSL and @@ -1128,7 +1128,7 @@ LAY the classes/ssl applets. - Here are some features that appeared in the 0.9.4 release: + Here are some features that appeared in the 0.9.4 release (Sep/2008): * Improvements to the [189]-find and [190]-create X session finding or creating modes: new desktop types and service redirection options. Personal cupsd daemon and SSH port redirection helper for @@ -1176,7 +1176,7 @@ LAY start again. - Here are some features that appeared in the 0.9.3 release: + Here are some features that appeared in the 0.9.3 release (Oct/2007): * [215]Viewer-side pixmap caching. A large area of pixels (at least 2-3 times as big as the framebuffer itself; the bigger the better... default is 10X) is placed below the framebuffer to act @@ -1189,7 +1189,7 @@ LAY pixel cache area from view. - Here are some features that appeared in the 0.9.2 release: + Here are some features that appeared in the 0.9.2 release (Jun/2007): * Building with no OpenSSL libssl available (or with --without-ssl) has been fixed. * One can configure x11vnc via "./configure @@ -1204,7 +1204,7 @@ LAY password automatically. - Here are some features that appeared in the 0.9.1 release: + Here are some features that appeared in the 0.9.1 release (May/2007): * The [219]UltraVNC Java viewer has been enhanced to support SSL (as the TightVNC viewer had been previously.) The UltraVNC Java supports ultravnc filetransfer, and so can be used as a VNC viewer @@ -1229,7 +1229,7 @@ LAY RFB_SSL_CLIENT_CERT. - Here are some features that appeared in the 0.9 release: + Here are some features that appeared in the 0.9 release (Apr/2007): * [224]VNC Service advertising via mDNS / ZeroConf / BonJour with the [225]Avahi client library. Enable via "[226]-avahi" or "[227]-zeroconf". @@ -1255,7 +1255,7 @@ LAY needing to include &PORT=NNN in the browser URL. - Here are some features that appeared in the 0.8.4 release: + Here are some features that appeared in the 0.8.4 release (Feb/2007): * Native [243]Mac OS X Aqua/Quartz support. (i.e. OSXvnc alternative; some activities are faster) * A [244]new login mode: "-display WAIT:cmd=FINDCREATEDISPLAY @@ -1290,7 +1290,7 @@ LAY know how it went. Thanks. - Here are some features that appeared in the 0.8.3 release: + Here are some features that appeared in the 0.8.3 release (Nov/2006): * The [253]-ssl option provides SSL encryption and authentication natively via the [254]www.openssl.org library. One can use from a simple self-signed certificate server certificate up to full CA @@ -2467,12 +2467,16 @@ libssl.so libcrypto.so libcrypt.so libx11-dev libxext-dev libxrandr-dev + libxinerama-dev libxtst-dev x-dev xlibs-static-dev zlib1g-dev libssl-dev + (note that depending on your OS version the above names may have been + changed and/or additional packages may be needed.) + For Redhat the list seems to be: gcc make @@ -2482,6 +2486,9 @@ libssl.so libcrypto.so libcrypt.so zlib-devel openssl097a + (there are probably some more now; send us a list for recent Redhat if + you have it building and see the need to add more -devel packages.) + For other distros or OS's the package names may not be the same but will look similar. Also, distros tend to rename packages as well so the above list may be out of date. So only use the above lists as @@ -4325,7 +4332,7 @@ connect = 5900 The mode requires an SSL certificate and key (i.e. .pem file.) These are usually created via the openssl(1) program (in fact in for "-ssl" (same as "-ssl SAVE") it will run openssl for you automatically.) So - the SSL is not completely "built-in" since this external tool need to + the SSL is not completely "built-in" since this external tool needs to be installed, but at least x11vnc runs it for you automatically. An -ssl example: @@ -4348,8 +4355,8 @@ connect = 5900 Update: As of Nov/2008 x11vnc also supports the [348]VeNCrypt SSL/TLS tunnel extension to the VNC protocol. The older ANONTLS method (vino) is also supported. This support is on by default when the -ssl option - is in use and can be fine-tuned using these options: [349]-vencrypt - and [350]-anontls. + is in use and can be fine-tuned using these options: [349]-vencrypt, + [350]-anontls, and [351]-sslonly. The normal x11vnc -ssl operation is somewhat like a URL method vncs://hostname if vnc://hostname indicates a standard unencrypted VNC @@ -4361,7 +4368,7 @@ connect = 5900 SSL VNC Viewers:. Viewer-side will need to use SSL as well. See the - [351]next FAQ and [352]here for SSL enabled VNC Viewers, including + [352]next FAQ and [353]here for SSL enabled VNC Viewers, including SSVNC, to connect to the above x11vnc via SSL. @@ -4376,12 +4383,12 @@ connect = 5900 is to encrypt the key with a passphrase (note however this requires supplying the passphrase each time x11vnc is started up.) - See the discussion on [353]x11vnc Key Management for some utilities + See the discussion on [354]x11vnc Key Management for some utilities provided for creating and managing certificates and keys and even for creating your own Certificate Authority (CA) for signing VNC server and client certificates. This may be done by importing the certificate into Web Browser or Java plugin keystores, or pointing stunnel to it. - The wrapper script [354]ss_vncviewer provides an example on unix (see + The wrapper script [355]ss_vncviewer provides an example on unix (see the -verify option.) Here are some notes on the simpler default (non-CA) operation. To have @@ -4395,7 +4402,7 @@ connect = 5900 the possibility of copying the server.crt to machines where the VNC Viewer will be run to enable authenticating the x11vnc SSL VNC server to the clients. When authentication takes place this way (or via the - more sophisticated CA signing described [355]here), then + more sophisticated CA signing described [356]here), then Man-In-The-Middle-Attacks are prevented. Otherwise, the SSL encryption only provides protection against passive network traffic "sniffing" (i.e. you are not protected against M-I-T-M attacks.) Nowadays, most @@ -4427,11 +4434,11 @@ connect = 5900 The older -stunnel option: Before the -ssl option there was a - convenience option [356]-stunnel that would start an external SSL + convenience option [357]-stunnel that would start an external SSL tunnel for you using stunnel. The -ssl method is the preferred way, but for historical reference we keep the -stunnel info here. - The [357]-stunnel mode requires the [358]www.stunnel.org command + The [358]-stunnel mode requires the [359]www.stunnel.org command stunnel(8) to be installed on the system. Some -stunnel examples: @@ -4462,8 +4469,8 @@ connect = 5900 There aren't any native VNC Viewers that do SSL (ask your VNC viewer developer to add the feature.) So a tunnel must be setup that you point the VNC Viewer to. This is often STUNNEL. You can do this - [359]manually, or use the [360]ss_vncviewer script on Unix, or our - [361]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or + [360]manually, or use the [361]ss_vncviewer script on Unix, or our + [362]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or MacOSX. See the next section for Java Web browser SSL VNC Viewers (you only need a Java-enabled Web browser for it to work.) @@ -4475,13 +4482,13 @@ connect = 5900 The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package supports only SSL based connections by default. As mentioned above the - [362]-httpdir can be used to specify the path to .../classes/ssl. A + [363]-httpdir can be used to specify the path to .../classes/ssl. A typical location might be /usr/local/share/x11vnc/classes/ssl. Or - [363]-http can be used to try to have it find the directory + [364]-http can be used to try to have it find the directory automatically. - Also note that the [364]SingleClick UltraVNC Java Viewer is compatible - with x11vnc's [365]-ssl SSL mode. (We tested it this way: "java -cp + Also note that the [365]SingleClick UltraVNC Java Viewer is compatible + with x11vnc's [366]-ssl SSL mode. (We tested it this way: "java -cp ./VncViewer.jar VncViewer HOST far-away.east PORT 5900 USESSL 1 TRUSTALL 1") @@ -4516,13 +4523,13 @@ connect = 5900 If you are using a router/firewall with port-redirection, and you are redirecting ports other than the default ones (5800, 5900) listed - above [366]see here. + above [367]see here. The https service provided thru the actual VNC port (5900 in the above example) can occasionally be slow or unreliable (it has to read some input and try to guess if the connection is VNC or HTTP.) If it is unreliable for you and you still want to serve the Java applet via - https, use the [367]-https option to get an additional port dedicated + https, use the [368]-https option to get an additional port dedicated to https (its URL will also be printed in the output.) Another possibility is to add the GET applet parameter: @@ -4535,7 +4542,7 @@ connect = 5900 You may also use "urlPrefix=somestring" to have /somestring prepended to /request.https.vnc.connection". Perhaps you are using a web server - [368]proxy scheme to enter a firewall or otherwise have rules applied + [369]proxy scheme to enter a firewall or otherwise have rules applied to the URL. If you need to have any slashes "/" in "somestring" use "_2F_" (a deficiency in libvncserver prevents using the more natural "%2F".) @@ -4628,12 +4635,12 @@ connect = 5900 Then, if you plan to use them, enable "fancy stuff" like "-svc" or "-unixpw", etc, etc. Be sure to add a password either "-rfbauth" or "-unixpw" or both. If you need to have the web browser use a corporate - [369]Web Proxy (i.e. it cannot connect directly) work on that last. - Ditto for the [370]Apache portal. + [370]Web Proxy (i.e. it cannot connect directly) work on that last. + Ditto for the [371]Apache portal. Router/Firewall port redirs: If you are doing port redirection at - your [371]router to an internal machine running x11vnc AND the + your [372]router to an internal machine running x11vnc AND the internet facing port is different from the internal machine's VNC port, you will need to apply the PORT applet parameter to indicate to the applet the Internet facing port number (otherwise by default the @@ -4643,7 +4650,7 @@ connect = 5900 So in this example the user configures his router to redirect connections to port 443 on his Internet side to, say, port 5900 on the - internal machine running x11vnc. See also the [372]-httpsredir option + internal machine running x11vnc. See also the [373]-httpsredir option that will try to automate this for you. To configure your router to do port redirection, see its instructions. @@ -4654,7 +4661,7 @@ connect = 5900 or Unix system acting as your firewall/router, see its firewall configuration. - You can also use x11vnc options [373]-rfbport NNNNN and [374]-httpport + You can also use x11vnc options [374]-rfbport NNNNN and [375]-httpport NNNNN to match the ports that your firewall will be redirecting to the machine where x11vnc is run. @@ -4683,12 +4690,12 @@ connect = 5900 NOT linger at. If you see in the x11vnc output a request for VncViewer.class instead of VncViewer.jar it is too late... you will need to completely restart the Web browser to get it to try for the - jar again. You can use the [375]-https option if you want a dedicated + jar again. You can use the [376]-https option if you want a dedicated port for HTTPS connections instead of sharing the VNC port. To see example x11vnc output for a successful https://host:5900/ - connection with the Java Applet see [376]This Page. And here is a - newer example [377]including the Java Console output. + connection with the Java Applet see [377]This Page. And here is a + newer example [378]including the Java Console output. All of the x11vnc Java Viewer applet parameters are described in the file classes/ssl/README @@ -4699,10 +4706,10 @@ connect = 5900 If you want to use a native VNC Viewer with the SSL enabled x11vnc you will need to run an external SSL tunnel on the Viewer side. There do not seem to be any native SSL VNC Viewers outside of our x11vnc and - [378]SSVNC packages. The basic ideas of doing this were discussed - [379]for external tunnel utilities here. + [379]SSVNC packages. The basic ideas of doing this were discussed + [380]for external tunnel utilities here. - The [380]ss_vncviewer script provided with x11vnc and SSVNC can set up + The [381]ss_vncviewer script provided with x11vnc and SSVNC can set up the stunnel tunnel automatically on unix as long as the stunnel command is installed on the Viewer machine and available in PATH (and vncviewer too of course.) Note that on a Debian based system you will @@ -4736,14 +4743,14 @@ connect = 5900 The fifth one shows that Web proxies can be used if that is the only way to get out of the firewall. If the "double proxy" situation arises - separate the two by commas. See [381]this page for more information on + separate the two by commas. See [382]this page for more information on how Web proxies come into play. - If one uses a Certificate Authority (CA) scheme described [382]here, + If one uses a Certificate Authority (CA) scheme described [383]here, the wrapper script would use the CA cert instead of the server cert: 3') ss_vncviewer -verify ./cacert.crt far-away.east:0 - Update Jul/2006: we now provide an [383]Enhanced TightVNC Viewer + Update Jul/2006: we now provide an [384]Enhanced TightVNC Viewer (SSVNC) package that starts up STUNNEL automatically along with some other features. All binaries (stunnel, vncviewer, and some utilities) are provided in the package. It works on Unix, Mac OS X, and Windows. @@ -4806,20 +4813,20 @@ connect = 5900 https://yourmachine.com/proxy.vnc?PORT=443 this is cleaner because it avoids editing the file, but requires more - parameters in the URL. See also the [384]-httpsredir x11vnc option - that will try to automate this for you. To use the GET [385]trick + parameters in the URL. See also the [385]-httpsredir x11vnc option + that will try to automate this for you. To use the GET [386]trick discussed above, do: https://yourmachine.com/proxy.vnc?GET=1&PORT=443 All of the x11vnc Java Viewer applet parameters are described in the file classes/ssl/README - Here is an example of Java Console and x11vnc output for the [386]Web + Here is an example of Java Console and x11vnc output for the [387]Web proxy case. - Note that both the [387]ss_vncviewer stunnel Unix wrapper script and - [388]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even + Note that both the [388]ss_vncviewer stunnel Unix wrapper script and + [389]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even though they do not involve a Web browser. @@ -4827,7 +4834,7 @@ connect = 5900 SSL from the Internet with a Web browser to x11vnc running on their workstations behind a firewall? Yes. You will need to configure apache to forward these connections. - It is discussed [389]here. This provides a clean alternative to the + It is discussed [390]here. This provides a clean alternative to the traditional method where the user uses SSH to log in through the gateway to create the encrypted port redirection to x11vnc running on her desktop. @@ -4835,7 +4842,7 @@ connect = 5900 Q-57: Can I create and use my own SSL Certificate Authority (CA) with x11vnc? - Yes, see [390]this page for how to do this and the utility commands + Yes, see [391]this page for how to do this and the utility commands x11vnc provides to create and manage many types of certificates and private keys. @@ -4854,14 +4861,14 @@ connect = 5900 need to have sufficient permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [391]FAQ on x11vnc + * Use the description under "Continuously" in the [392]FAQ on x11vnc and Display Managers - * Use the description in the [392]FAQ on x11vnc and inetd(8) - * Use the description in the [393]FAQ on Unix user logins and + * Use the description in the [393]FAQ on x11vnc and inetd(8) + * Use the description in the [394]FAQ on Unix user logins and inetd(8) * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc or autostart script or ...) - * Although less reliable, see the [394]x11vnc_loop rc.local hack + * Although less reliable, see the [395]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the @@ -4883,9 +4890,9 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg X startup scripts (traditionally .xsession/.xinitrc) may have to be in a different directory or have a different basename. One user recommends the description under 'Running Scripts Automatically' at - [395]this link. + [396]this link. - Firewalls: note all methods will require the host-level [396]firewall + Firewalls: note all methods will require the host-level [397]firewall to be configured to allow connections in on a port. E.g. 5900 (default VNC port) or 22 (default SSH port for tunnelling VNC.) Most systems these days have firewalls turned on by default, so you will actively @@ -4897,6 +4904,11 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg Q-59: How can I use x11vnc to connect to an X login screen like xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X session yet.) + + We describe two scenarios here. The first is called 'One time only' + meaning you just need to do it quickly once and don't want to repeat; + and the second is called 'Continuously' meaning you want the access to + be available after every reboot and after every desktop logout. _________________________________________________________________ One time only: If the X login screen is running and you just want to @@ -4907,7 +4919,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg while running x11vnc as root, e.g. for the gnome display manager, gdm: x11vnc -auth /var/gdm/:0.Xauth -display :0 - (the [397]-auth option sets the XAUTHORITY variable for you.) + (the [398]-auth option sets the XAUTHORITY variable for you.) There will be a similar thing for xdm using however a different auth directory path (perhaps something like @@ -4918,7 +4930,10 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg kept. Trick: sometimes ps(1) can reveal the X server process -auth argument - (e.g. "ps wwwwaux | grep auth") and hence the path to the auth file. + (e.g. "ps wwwaux | grep auth") and hence the path to the auth file. + + Update Dec/2009: use "[399]-auth guess" to have x11vnc try to guess + the location of the auth file for you. You next connect to x11vnc with a VNC viewer, give your username and password to the X login prompt to start your session. @@ -4935,10 +4950,10 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg (BTW, the auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see - [398]the example at the end of this FAQ.) Then restart dtlogin, e.g.: + [400]the example at the end of this FAQ.) Then restart dtlogin, e.g.: /etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot. - Update Nov/2008: Regarding GDM KillInitClients: see the [399]-reopen + Update Nov/2008: Regarding GDM KillInitClients: see the [401]-reopen option for another possible workaround. Update Oct/2009: Regarding GDM KillInitClients: starting with x11vnc @@ -4957,7 +4972,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg _________________________________________________________________ Continuously: Have x11vnc reattach each time the X server is - restarted (i.e. after each logout): + restarted (i.e. after each logout and reboot): To make x11vnc always attached to the X server including the login screen you will need to add a command to a display manager startup @@ -4965,11 +4980,11 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg Please consider the security implications of this! The VNC display for the X session always accessible (but hopefully password protected.) - Add [400]-localhost if you only plan to access via a [401]SSH tunnel. + Add [402]-localhost if you only plan to access via a [403]SSH tunnel. The name of the display manager startup script file depends on desktop used and seem to be: - GDM (GNOME) /etc/X11/gdm/Init/Default (or sometimes Init/:0) + GDM (GNOME) /etc/X11/gdm/Init/Default /etc/gdm/Init/Default KDM (KDE) /etc/kde*/kdm/Xsetup XDM /etc/X11/xdm/Xsetup (or sometimes xdm/Xsetup_0) @@ -4981,6 +4996,10 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg also be display number specific scripts: e.g. Xsetup_0 vs. Xsetup, you need to watch out for. + Note: You should read and understand all of the Note's and Update's + in the 'One time only' section above. All of the GDM topics apply here + as well: + Note: GDM: The above (in 'One time only') gdm setting of KillInitClients=false in /etc/X11/gdm/gdm.conf (or /etc/gdm/gdm.conf, etc.) for GDM is needed here as well. Other display managers (KDM, @@ -4999,7 +5018,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg -forever -bg where you should customize the exact command to your needs (e.g. - [402]-localhost for SSH tunnel-only access; [403]-ssl SAVE for SSL + [404]-localhost for SSH tunnel-only access; [405]-ssl SAVE for SSL access; etc.) Happy, happy, joy, joy: Note that we do not need to specify -display @@ -5007,7 +5026,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg and XAUTHORITY environment variables for the Xsetup script!!! You may also want to force the VNC port with something like "-rfbport - 5900" (or [404]-N) to avoid autoselecting one if 5900 is already + 5900" (or [406]-N) to avoid autoselecting one if 5900 is already taken. _________________________________________________________________ @@ -5023,7 +5042,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg Then restart: /usr/sbin/gdm-restart (or reboot.) The KillInitClients=false setting is important: without it x11vnc will be - killed immediately after the user logs in. Here are [405]full details + killed immediately after the user logs in. Here are [407]full details on how to configure gdm _________________________________________________________________ @@ -5065,16 +5084,16 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg If you do not want to deal with any display manager startup scripts, here is a kludgey script that can be run manually or out of a boot - file like rc.local: [406]x11vnc_loop It will need some local + file like rc.local: [408]x11vnc_loop It will need some local customization before running. Because the XAUTHORITY auth file must be guessed by this script, use of the display manager script method - described above is greatly preferred. There is also the [407]-loop + described above is greatly preferred. There is also the [409]-loop option that does something similar. If the machine is a traditional Xterminal you may want to read - [408]this FAQ. + [410]this FAQ. - Firewalls: note all methods will require the host-level [409]firewall + Firewalls: note all methods will require the host-level [411]firewall to be configured to allow connections in on a port. E.g. 5900 (default VNC port) or 22 (default SSH port for tunnelling VNC.) Most systems these days have firewalls turned on by default, so you will actively @@ -5090,7 +5109,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh - where the shell script /usr/local/bin/x11vnc_sh uses the [410]-inetd + where the shell script /usr/local/bin/x11vnc_sh uses the [412]-inetd option and looks something like (you'll need to customize to your settings.) #!/bin/sh @@ -5103,7 +5122,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg and that confuses it greatly, causing it to abort.) If you do not use a wrapper script as above but rather call x11vnc directly in /etc/inetd.conf and do not redirect stderr to a file, then you must - specify the -q (aka [411]-quiet) option: "/usr/local/bin/x11vnc -q + specify the -q (aka [413]-quiet) option: "/usr/local/bin/x11vnc -q -inetd ...". When you supply both -q and -inet and no "-o logfile" then stderr will automatically be closed (to prevent, e.g. library stderr messages leaking out to the viewer.) The recommended practice @@ -5111,12 +5130,12 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg script with "2>logfile" redirection because the errors and warnings printed out are very useful in troubleshooting problems. - Note also the need to set XAUTHORITY via [412]-auth to point to the + Note also the need to set XAUTHORITY via [414]-auth to point to the MIT-COOKIE auth file to get permission to connect to the X display (setting and exporting the XAUTHORITY variable accomplishes the same thing.) See the x11vnc_loop file in the previous question for more ideas on what that auth file may be, etc. The scheme described in the - [413]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY + [415]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY issue nicely. Note: On Solaris you cannot have the bare number 5900 in @@ -5182,8 +5201,8 @@ service x11vncservice #!/bin/sh COLUMNS=256 export COLUMNS -authfile=`ps wwwwwaux | grep '/X.*-auth' | grep -v grep | sed -e 's/^.*-auth */ -/' -e 's/ .*$//' | head -n 1` +authfile=`ps wwwaux | grep '/X.*-auth' | grep -v grep | sed -e 's/^.*-auth *//' + -e 's/ .*$//' | head -n 1` if [ -r "$authfile" ]; then exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -display :0 -a @@ -5201,9 +5220,9 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 it automatically? Yes, as of Feb/2007 x11vnc supports mDNS / Zeroconf advertising of its - service via the Avahi client library. Use the option [414]-avahi (same - as [415]-mdns or [416]-zeroconf) to enable it. Depending on your setup - you may need to install [417]Avahi (including the development/build + service via the Avahi client library. Use the option [416]-avahi (same + as [417]-mdns or [418]-zeroconf) to enable it. Depending on your setup + you may need to install [419]Avahi (including the development/build packages), enable the server: avahi-daemon and avahi-dnsconfd, and possibly open up UDP port 5353 on your firewall. @@ -5232,11 +5251,11 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 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 - and [420]-display WAIT options. The reason inetd(8) makes this easier + The easiest way to do this is via [420]inetd(8) using the [421]-unixpw + and [422]-display WAIT options. The reason inetd(8) makes this easier is that it starts a new x11vnc process for each new user connection. Otherwise a wrapper would have to listen for connections and spawn new - x11vnc's (see [421]this example and also the [422]-loopbg option.) + x11vnc's (see [423]this example and also the [424]-loopbg option.) inetd(8) is not required for this, but it makes some aspects more general. @@ -5244,23 +5263,23 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 hostname:0, and do not need to memorize a special VNC display number just for their personal use, etc. - Update: Use the [423]-find, [424]-create, [425]-svc, and [426]-xdmsvc + Update: Use the [425]-find, [426]-create, [427]-svc, and [428]-xdmsvc options that are shorthand for common FINDCREATEDISPLAY usage modes (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 + The [429]-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 his own script: "-display WAIT:cmd=/path/to/find_display" where - the script find_display might look something like [428]this. + the script find_display might look something like [430]this. A default script somewhat like the above is used under "-display - WAIT:cmd=FINDDISPLAY" (same as [429]-find) The format for any such + WAIT:cmd=FINDDISPLAY" (same as [431]-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 @@ -5271,10 +5290,10 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 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 + Tip: Note that the [432]-find option is an alias for "-display WAIT:cmd=FINDDISPLAY". Use it! - The [431]-unixpw option allows [432]UNIX password logins. It + The [433]-unixpw option allows [434]UNIX password logins. It conveniently knows the Unix username whose X display should be found. Here are a couple /etc/inetd.conf examples of this usage: 5900 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd @@ -5284,19 +5303,19 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 -unixpw \ -find -o /var/log/x11vnc.log -ssl SAVE -users unixpw= - Note we have used the [433]-find alias and the very long lines have + Note we have used the [435]-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.) + [436]-svc alias.) 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 "[435]-users unixpw=" option. + logs in due to the "[437]-users unixpw=" option. - Note that [436]SSL is required for this mode because otherwise the + Note that [438]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 @@ -5304,17 +5323,17 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 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 [437]-localhost + If you really want to disable the SSL or SSH [439]-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 [438]-unixpw documentation. + read the [440]-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/pass wd -o /var/log/x11vnc.log - The "[439]-users =fred" option will cause x11vnc to switch to user + The "[441]-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. @@ -5332,7 +5351,7 @@ wd -o /var/log/x11vnc.log 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 + servers: first [442]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 @@ -5346,16 +5365,16 @@ wd -o /var/log/x11vnc.log -ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY Where the very long lines have been split. See below where that long - and cumbersome last line is replaced by the [441]-svc alias. + and cumbersome last line is replaced by the [443]-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: + The above mode will allow direct SSL (e.g. [444]ss_vncviewer or + [445]SSVNC) access and also Java Web browers access via: https://hostname:5900/. - Tip: Note that the [444]-create option is an alias for "-display + Tip: Note that the [446]-create option is an alias for "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb". - Tip: Note that [445]-svc is a short hand for the long "-ssl SAVE + Tip: Note that [447]-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. @@ -5367,7 +5386,7 @@ wd -o /var/log/x11vnc.log 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 + [448]-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 @@ -5401,10 +5420,10 @@ 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" or use "[447]-create_xsrv + WAIT:cmd=FINDCREATEDISPLAY-X,Xvfb,Xdummy" or use "[449]-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 + this may only work on Linux and the chvt program may [450]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. @@ -5433,7 +5452,7 @@ bin/x11vnc -svc will also typically block UDP (port 177 for XDMCP) by default effectively limiting the UDP connections to localhost. - Tip: Note that [449]-xdmsvc is a short hand alias for the long "-ssl + Tip: Note that [451]-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 @@ -5502,15 +5521,15 @@ t:5 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 - [450]-loop that makes it easier. Of course when x11vnc restarts it + [452]-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 [451]-loopbg to emulate inetd(8) to some degree, + One can also use the [453]-loopbg to emulate inetd(8) to some degree, where each connected process runs in the background. It could be - combined, say, with the [452]-svc option to provide simple terminal + combined, say, with the [454]-svc option to provide simple terminal services without using inetd(8). @@ -5518,7 +5537,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 [453]option: + that connect to it, run x11vnc with this [455]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -5537,7 +5556,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 [454]-http option will try to guess where the Java + As of May/2005 the [456]-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. @@ -5546,7 +5565,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 [455]discussion here if the web browser must use a + Proxies: See the [457]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 @@ -5562,7 +5581,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 - [456]-connect option. To connect immediately at x11vnc startup time + [458]-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.) @@ -5571,11 +5590,11 @@ t:5 file is checked periodically (about once a second) for new hosts to connect to. - The [457]-remote control option (aka -R) can also be used to do this + The [459]-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 "[458]-connect_or_exit" option to have x11vnc exit if the + Use the "[460]-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.) @@ -5588,7 +5607,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 [459]-vncconnect option to + VNC package at www.realvnc.com) specify the [461]-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 @@ -5607,7 +5626,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 "[460]-proxy host:port" option. The default is to + proxies: use the "[462]-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 @@ -5627,11 +5646,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 [461]-proxy + (e.g. a CGI script) is retrieved via the GET method. See [463]-proxy for more info. Another experimental mode is "-proxy ssh://user@host" in which case a - SSH tunnel is used for the proxying. See [462]-proxy for more info. + SSH tunnel is used for the proxying. See [464]-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 @@ -5654,10 +5673,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 - [463]locally using vncviewer. Make sure vncviewer's "-encodings raw" + [465]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 ([464]See how below.) + just starts up vncviewer and nothing else ([466]See how below.) Here is one way to start up Xvfb: xinit -- /usr/X11R6/bin/Xvfb :1 -cc 4 -screen 0 1024x768x16 @@ -5677,19 +5696,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 [465]FINDCREATEDISPLAY discussion of the - "[466]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or + Update Nov/2006: See the [467]FINDCREATEDISPLAY discussion of the + "[468]-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 [467]-find, - [468]-create, [469]-svc, and [470]-xdmsvc aliases can also come in + (inetd(8) is a nice way to provide this service.) The [469]-find, + [470]-create, [471]-svc, and [472]-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 - [471]-add_keysyms option to have keysyms added automatically. Also, to + [473]-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" @@ -5701,7 +5720,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 [472]FINDCREATEDISPLAY + (note: these are applied automatically in the [474]FINDCREATEDISPLAY mode of x11vnc.) Perhaps the Xvfb options -xkbdb or -xkbmap could be used to get a better default keyboard mapping... @@ -5716,11 +5735,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) [473]switching even though it + Linux Virtual Console/Terminal (VC/VT) [475]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 [474]Xdummy that allows you to + Jul/2005 we have an LD_PRELOAD script [476]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. @@ -5747,7 +5766,7 @@ x11vnc -display :5 -rfbport 5905 -bg vncviewer -geometry +0+0 -encodings raw -passwd $HOME/.vnc/passwd localhost:5 The display numbers (VNC and X) will likely be different (you could - also try [475]-find), and you may not need the -passwd. Recent RealVNC + also try [477]-find), and you may not need the -passwd. Recent RealVNC viewers might be this: #!/bin/sh x11vnc -display :5 -rfbport 5905 -bg @@ -5765,7 +5784,7 @@ t:5 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. + disconnects) and it uses the XDM/GDM/KDM login greeter [478]here. Q-68: How can I use x11vnc on "headless" machines? Why might I want @@ -5780,7 +5799,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 [477]this FAQ) and access it from + display via x11vnc (e.g. see [479]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 @@ -5804,10 +5823,10 @@ t:5 cards as it can hold to provide multiple simultaneous access or testing on different kinds of video hardware. - See also the [478]FINDCREATEDISPLAY discussion of the "[479]-display + See also the [480]FINDCREATEDISPLAY discussion of the "[481]-display WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X servers are started automatically for new users connecting. The - [480]-find, [481]-create, [482]-svc, and [483]-xdmsvc aliases can also + [482]-find, [483]-create, [484]-svc, and [485]-xdmsvc aliases can also come in handy here. [Resource Usage and Performance] @@ -5830,7 +5849,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 [484]shm_clear to list and prompt for removal + Here is a shell script [486]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, @@ -5864,44 +5883,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 - [485]-onetile option (corresponds to only 3 shm segments used, and + [487]-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 - [486]-noshm option. Performance will be somewhat degraded but when + [488]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [487]earlier question discussing -noshm.) + [489]earlier question discussing -noshm.) Q-70: How can I make x11vnc use less system resources? - 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 [490]-nap (now on by default; use -nonap to disable) and + "[491]-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 "[490]-sb 15" will cause x11vnc to go into a deep-sleep + something like "[492]-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 [491]-onetile option will use less memory and use fewer shared - memory slots (add [492]-fs 1.0 for one less slot.) + the [493]-onetile option will use less memory and use fewer shared + memory slots (add [494]-fs 1.0 for one less slot.) Q-71: How can I make x11vnc use MORE system resources? - You can try [493]-threads (note this mode can be unstable and/or + You can try [495]-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 [494]-defer as well. Note that if you try to increase the + dial down [496]-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 [495]-id option) can be streamed over a LAN or wireless at + the x11vnc [497]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. If the graphics card's framebuffer read rate - 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 + is [498]faster than normal then the video window size and frame rate + can be much higher. The use of [499]TurboVNC and/or TurboJPEG can make the frame rate somewhat higher still (but most of this hinges on the graphics card's read rate.) @@ -5918,7 +5937,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 - [498]-solid [color] option to try to do this automatically. + [500]-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 @@ -5927,9 +5946,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 [499]-scrollcopyrect is active and + problem in x11vnc 0.7.2 if [501]-scrollcopyrect is active and detecting scrolls for the application.) - * If the [500]-wireframe option is not available (earlier than + * If the [502]-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) @@ -5952,7 +5971,7 @@ ied) noticed. VNC viewer parameters: - * Use a [501]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer + * Use a [503]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 @@ -5960,7 +5979,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.) [502]SSVNC does too. The colors are poor, but it + even 8 colors.) [504]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) @@ -5974,39 +5993,39 @@ ied) file. x11vnc parameters: - * Make sure the [503]-wireframe option is active (it should be on by + * Make sure the [505]-wireframe option is active (it should be on by default) and you have Opaque Moves/Resizes Enabled in the window manager. - * Make sure the [504]-scrollcopyrect option is active (it should be + * Make sure the [506]-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 - [505]-solid - * Try x11vnc's client-side caching [506]client-side caching scheme: - [507]-ncache - * Specify [508]-speeds modem to force the wireframe and + [507]-solid + * Try x11vnc's client-side caching [508]client-side caching scheme: + [509]-ncache + * Specify [510]-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 [509]-nodragging (no screen updates when dragging mouse, + drastic [511]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Set [510]-fs 1.0 (disables fullscreen updates) - * Try increasing [511]-wait or [512]-defer (reduces the maximum + * Set [512]-fs 1.0 (disables fullscreen updates) + * Try increasing [513]-wait or [514]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * Try the [513]-progressive pixelheight mode with the block + * Try the [515]-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 [514]-id or - [515]-appshare (cuts down extraneous polling and updates, but can + * If you just want to watch one (simple) window use [516]-id or + [517]-appshare (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [516]-nosel (disables all clipboard selection exchange) - * Use [517]-nocursor and [518]-nocursorpos (repainting the remote + * Set [518]-nosel (disables all clipboard selection exchange) + * Use [519]-nocursor and [520]-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 - [519]-readtimeout n setting if it sometimes takes more than 20sec + [521]-readtimeout n setting if it sometimes takes more than 20sec to paint the full screen, etc. - * Do not use [520]-fixscreen to automatically refresh the whole + * Do not use [522]-fixscreen to automatically refresh the whole screen, tap three Alt_L's then the screen has painting errors (rare problem.) @@ -6075,7 +6094,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 [521]slow (e.g. + in main memory. So reading the fb is still painfully [523]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 @@ -6093,45 +6112,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 "[522]-xd_area A" option to adjust the size + skipped.) You can use the "[524]-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 "[523]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[524]-noxdamage". + The option "[525]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[526]-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 "[525]-noxdamage" option. + he uses the "[527]-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 [526]MiniMyth reports that the 'alphapulse' tag of the + A developer for [528]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 [527]this FAQ too. + Update: see [529]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 [528]slow hardware read rates from + This problem is primarily due to [530]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 - [529]-pointer_mode option for more info. The next bottleneck is + [531]-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 @@ -6141,27 +6160,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 "[530]-pointer_mode 1" option. + the "[532]-pointer_mode 1" option. - Also added was the [531]-nodragging option that disables all screen + Also added was the [533]-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 [532]-pointer_mode n option was introduced. n=1 is + As of Dec/2004 the [534]-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 [533]-threads option can improve + Also, in some circumstances the [535]-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 [534]wireframe FAQ and - [535]scrollcopyrect FAQ below) provide schemes to sweep this problem + As of Apr/2005 two new options (see the [536]wireframe FAQ and + [537]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 @@ -6185,8 +6204,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 [536]slow video card - read rates (see [537]here too.) A displacement, even a small one, of a + intermediate steps. BTW the lurching is due to [538]slow video card + read rates (see [539]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. @@ -6194,7 +6213,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 [538]-nowireframe option + with the problem. It can be disabled with the [540]-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 @@ -6240,13 +6259,13 @@ EndSection * Maximum time to show a wireframe animation. * Minimum time between sending wireframe outlines. - See the [539]"-wireframe tweaks" option for more details. On a slow + See the [541]"-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 - [540]"-wirecopyrect mode" option. It is also on by default. This + [542]"-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 @@ -6294,7 +6313,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 [541]slow.) + the hardware framebuffer is [543]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. @@ -6321,10 +6340,10 @@ EndSection the X server display: if one falls too far behind it could become a mess... - The initial implementation of [542]-scrollcopyrect option is useful in + The initial implementation of [544]-scrollcopyrect option is useful in that it detects many scrolls and thus gives a much nicer working - environment (especially when combined with the [543]-wireframe - [544]-wirecopyrect [545]options, which are also on by default; and if + environment (especially when combined with the [545]-wireframe + [546]-wirecopyrect [547]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. @@ -6357,10 +6376,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: [546]-fixscreen + also: [548]-fixscreen * Some applications, notably OpenOffice, do XCopyArea scrolls in weird ways that assume ancestor window clipping is taking place. - See the [547]-scr_skip option for ways to tweak this on a + See the [549]-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 @@ -6377,7 +6396,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 [548]-scale option there will be a quick CopyRect + * When using the [550]-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 @@ -6390,7 +6409,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 [549]-noscrollcopyrect (or -noscr for short.) If you find + with the [551]-noscrollcopyrect (or -noscr for short.) If you find some extremely bad and repeatable behavior for -scrollcopyrect please report a bug. @@ -6415,9 +6434,9 @@ EndSection that pixel data is needed again it does not have to be retransmitted over the network. - As of Dec/2006 in the [550]0.9 development tarball there is an + As of Dec/2006 in the [552]0.9 development tarball there is an experimental client-side caching implementation enabled by the - "[551]-ncache n" option. In fact, during the test period it was on by + "[553]-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 @@ -6444,7 +6463,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. [552]SSVNC (see below) can do this + cache area cannot be seen. [554]SSVNC (see below) can do this automatically. At some point LibVNCServer may implement a "rfbFBCrop" pseudoencoding @@ -6454,7 +6473,7 @@ EndSection rendering...) The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice - [553]-ycrop option to help hide the pixel cache area from view. It + [555]-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 @@ -6485,7 +6504,7 @@ EndSection an additional factor of 2 in memory use. However, even in the smallest usage mode with n equal 2 and - [554]-ncache_no_rootpixmap set (this requires only 2X additional + [556]-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. @@ -6496,7 +6515,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 "[555]-ncache_cr". By specifying + Another option to experiment with is "[557]-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 @@ -6553,24 +6572,24 @@ EndSection As of Feb/2009 (development tarball) there is an experimental kludge to let you build x11vnc using TurboVNC's modified TightVNC encoding. - [556]TurboVNC is part of the [557]VirtualGL project. It does two main + [558]TurboVNC is part of the [559]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. [558]TurboJPEG is an + instead of the usual libjpeg implementation. [560]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. "[559]-wait 5" and "[560]-defer 5" (or even a + down the delays, e.g. "[561]-wait 5" and "[562]-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 - [561]TurboJPEG software. + [563]TurboJPEG software. In brief, the steps look like this: cd x11vnc-x.y.z/x11vnc/misc/turbovnc @@ -6582,22 +6601,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 [562]SSVNC viewer has + will be implemented. Support for TurboVNC in [564]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 [563]misc. bins directory. For other platforms + TurboVNC support in the [565]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 [564]SSVNC, both TurboVNC enabled, were able to + 6200) x11vnc and [566]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 [565]20-30 fps with the glxspheres + higher-end hardware can sustain [567]20-30 fps with the glxspheres benchmark. - Potential Slowdown: As we describe [566]elsewhere, unless you use + Potential Slowdown: As we describe [568]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) @@ -6637,23 +6656,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 "[567]-cursor X" option that + A simple kludge is provided by the "[569]-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 "[568]-cursor some" option for + work for those cases. Also see the "[570]-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 - [569]-overlay option is supplied. See [570]this FAQ for more info. + [571]-overlay option is supplied. See [572]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 - [571]Solaris 10. + [573]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 @@ -6661,7 +6680,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. [572]Details can be found here. + hidden alpha channel data under 32bpp. [574]Details can be found here. Q-81: When using XFIXES cursorshape mode, some of the cursors look @@ -6694,17 +6713,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 "[573]-alphacut n" option lets + course!) some tunable parameters. The "[575]-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 "[574]-alphafrac f" option tries to correct individual + 240. The "[576]-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 [575]-alpharemove that is useful for + Finally, there is an option [577]-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 @@ -6730,10 +6749,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 [576]-nocursorshape x11vnc option. In this case the cursor is + with the [578]-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 [577]-noalphablend option to disable this + the x11vnc side. Use the [579]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values.) @@ -6757,7 +6776,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 [578]Enhanced TightVNC Viewer (SSVNC) + This patch is applied to the [580]Enhanced TightVNC Viewer (SSVNC) package we provide. [Mouse Pointer] @@ -6765,9 +6784,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 [579]tightvnc extension + This default takes advantage of a [581]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [580]-nocursor + the local VNC viewer. You may disable it with the [582]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -6781,17 +6800,17 @@ EndSection clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [581]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [583]-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 [582]-nocursorpos and [583]-nocursorshape. + is the default. See also [584]-nocursorpos and [585]-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: [584]-buttonmap + You can remap the mouse buttons via something like: [586]-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. @@ -6799,7 +6818,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 [585]-debug_pointer option prints out much info for + Note that the [587]-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 @@ -6821,7 +6840,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 [586]-buttonmap but rather configuring the X server + consider not using [588]-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"'.) @@ -6851,7 +6870,7 @@ EndSection Q-86: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [587]-modtweak should help here. It is a mode that monitors + The option [589]-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. @@ -6860,20 +6879,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 [588]this FAQ for more info.) Without + not exist on the keyboard (see [590]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 [589]FAQ about the -xkb option for a more powerful method + Also see the [591]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 - [590]-debug_keyboard option prints out much info for every keystroke + [592]-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 [591]-nomodtweak. + His solution was to disable all of the above and use [593]-nomodtweak. This is the simplest form of keystroke insertion and it actually solved the problem. Try it if the other options don't help. @@ -6886,9 +6905,9 @@ EndSection (e.g. pc105 in the XF86Config file when it should be something else, say pc104.) - Short Cut: Try the [592]-xkb or [593]-sloppy_keys options and see if + Short Cut: Try the [594]-xkb or [595]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [594]-modtweak is now the default) but it is useful reference for + [596]-modtweak is now the default) but it is useful reference for various tricks and so is kept. @@ -6931,17 +6950,17 @@ EndSection -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([595]-modtweak) is a mode that monitors the + settings. The former ([597]-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 ([596]-remap less-comma) is an immediate remapping of the + The latter ([598]-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 [597]FAQ about the -xkb option as a possible workaround + See also the [599]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [598]-debug_keyboard option prints out much info for + Note that the [600]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. @@ -6949,7 +6968,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 [599]keymapping + the Shift key before releasing the "<". Because of a [601]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. @@ -6957,9 +6976,9 @@ EndSection characters: in general it can happen whenever the Shift key is released early. - This should not happen in [600]-xkb mode, because it works hard to + This should not happen in [602]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [601]-sloppy_keys to attempt a similar type of algorithm. + option [603]-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 "." @@ -6987,7 +7006,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 [602]-modtweak + This all worked fine with x11vnc running with the [604]-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 @@ -7004,7 +7023,7 @@ EndSection * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [603]-xkb option seems to fix all of the missing keys: "@", "<", + The [605]-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 @@ -7012,7 +7031,7 @@ EndSection debugging output (send it along with any problems you report.) Update: as of Jun/2005 x11vnc will try to automatically enable - [604]-xkb if it appears that would be beneficial (e.g. if it sees any + [606]-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. @@ -7027,7 +7046,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: - [605]-skip_keycodes 93 + [607]-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 @@ -7045,16 +7064,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 [606]-remap x11vnc option: + created using the [608]-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 - [607]-add_keysyms option in the next paragraph. - Update: for convenience "[608]-remap DEAD" does many of these + [609]-add_keysyms option in the next paragraph. + Update: for convenience "[610]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [609]-remap, an - option [610]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [611]-remap, an + option [612]-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 @@ -7073,7 +7092,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) [611]-norepeat x11vnc option. You will still + use the new (Jul/2004) [613]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -7097,7 +7116,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 [612]-norepeat (which has since Dec/2004 been + needed, or to use the [614]-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 @@ -7108,7 +7127,7 @@ EndSection keystrokes!! Are you using x11vnc to log in to an X session via display manager? - (as described in [613]this FAQ) If so, x11vnc is starting before your + (as described in [615]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 @@ -7169,11 +7188,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 [614]-clear_mods option to try to clear all of + You can also use the [616]-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 [615]-remap to prevent sending all of the problem modifier + of using [617]-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: @@ -7186,16 +7205,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 [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. + down on the local (Viewer) side. See [618]this FAQ on lock keys + problem. These options may help avoid the problem: [619]-skip_lockkeys + and [620]-capslock. See also [621]-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 "[620]-remap Super_R-Mode_switch" x11vnc option may + Something like "[622]-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).) @@ -7218,7 +7237,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 [621]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [623]-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. @@ -7238,7 +7257,7 @@ EndSection and similar triple mappings (with two in the AltGr/Mode_switch group) of a keysum to a single keycode. - Use the [622]-nomodtweak option as a workaround. You can also use + Use the [624]-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" @@ -7252,7 +7271,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 [623]-remap + have x11vnc do the remapping. This can be done via the [625]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -7261,7 +7280,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: - [624]-remap Super_R-Button2 + [626]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -7280,13 +7299,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 - [625]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[626]-remap Caps_Lock-None". + [627]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[628]-remap Caps_Lock-None". - Also try the [627]-nomodtweak and [628]-capslock options. + Also try the [629]-nomodtweak and [630]-capslock options. Another useful option that turns off any Lock keys on the remote side - at startup and end is the [629]-clear_all option. During a session you + at startup and end is the [631]-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 @@ -7315,7 +7334,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 - [630]the next FAQ on x11vnc scaling. + [632]the next FAQ on x11vnc scaling. Q-99: Does x11vnc support server-side framebuffer scaling? (E.g. to @@ -7323,7 +7342,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 "[631]-scale fraction" option. "fraction" can either be a + use the "[633]-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. @@ -7348,7 +7367,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 - [632]applications. Since with integer scale factors the framebuffers + [634]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -7374,7 +7393,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 ([633]-rfbport option, + different scalings listening on separate ports ([635]-rfbport option, etc.) Update: As of May/2006 x11vnc also supports the UltraVNC server-side @@ -7384,8 +7403,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 [634]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [635]"-connect + use the [636]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [637]"-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 @@ -7394,7 +7413,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 - [636]"-scale_cursor frac" option to set the cursor scaling to a + [638]"-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.) @@ -7422,21 +7441,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 [637]-blackout x11vnc option + may be distracting to the viewer. The [639]-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 - [638]-xinerama x11vnc option can be used to have it automatically + [640]-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: - [639]-xinerama is now on by default. + [641]-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 [640]-xwarppointer + of the large display. If this happens try using the [642]-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 [641]-xwarppointer will + Xinerama is enabled.) Update: As of Dec/2006 [643]-xwarppointer will be applied automatically if Xinerama is detected. To disable use: -noxwarppointer @@ -7459,23 +7478,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 [642]FAQ to increase the limit. It - is probably also a good idea to run with the [643]-onetile option in + /etc/system as mentioned in another [644]FAQ to increase the limit. It + is probably also a good idea to run with the [645]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [644]-noshm to use no shm segments. + [646]-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 "[645]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[647]-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 [646]Xinerama screen into two + One user used -clip to split up a large [648]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [647]-id or [648]-sid options are used. The offset is measured + the [649]-id or [650]-sid options are used. The offset is measured from the upper left corner of the selected window. @@ -7484,7 +7503,7 @@ EndSection just seems to crash. As of Dec/2004 x11vnc supports XRANDR. You enable it with the - [649]-xrandr option to make x11vnc monitor XRANDR events and also trap + [651]-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. @@ -7494,9 +7513,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 [650]-padgeom option to make the region big + viewers you can try the [652]-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: [651]SSVNC + for the TightVNC Viewer on Unix: [653]SSVNC If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you @@ -7508,7 +7527,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 [652]-rotate option allow this. E.g's: + As of Jul/2006 there is the [654]-rotate option allow this. E.g's: "-rotate +90", "-rotate -90", "-rotate x", etc. @@ -7573,13 +7592,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 [653]here for how to + straight xscreensaver (see the instructions [655]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 [654]-nodpms option was added + suspend, or off.) In Nov/2006 the x11vnc [656]-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 @@ -7595,16 +7614,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 - [655]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video + [657]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video card driver. - As a workaround apply the [656]-noxdamage option. As of Feb/2007 + As a workaround apply the [658]-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 [657]this + beryl you might as well always supply -noxdamage. Thanks to [659]this user who reported the problem and discovered the workaround. - A developer for [658]MiniMyth reports that the 'alphapulse' tag of the + A developer for [660]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. @@ -7624,9 +7643,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 [659]this FAQ + desktop in a separate Virtual Terminal (e.g. VT 8) (see [661]this FAQ on VT's for background.) Unfortunately, this Fullscreen VT is not an X - server. So x11vnc cannot access it (however, [660]see this discussion + server. So x11vnc cannot access it (however, [662]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. @@ -7647,13 +7666,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 [661]is in the active VT. + as long as the VMWare X session [663]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 [662]-id windowid option. The + the VMWare menu buttons) by use of the [664]-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 @@ -7669,10 +7688,10 @@ EndSection controlled) via VNC with x11vnc? As of Apr/2005 there is support for this. Two options were added: - "[663]-rawfb string" (to indicate the raw frame buffer device, file, - etc. and its parameters) and "[664]-pipeinput command" (to provide an + "[665]-rawfb string" (to indicate the raw frame buffer device, file, + etc. and its parameters) and "[666]-pipeinput command" (to provide an external program that will inject or otherwise process mouse and - keystroke input.) Some useful [665]-pipeinput schemes, VID, CONSOLE, + keystroke input.) Some useful [667]-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 @@ -7712,9 +7731,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 [666]-snapfb option with + this.) The "snap:" setting applies the [668]-snapfb option with "file:" type reading (this is useful for exporting webcams or TV tuner - video; see [667]the next FAQ for more info.) + video; see [669]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 @@ -7759,7 +7778,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 [668]X + for the case of Xvfb x11vnc can poll it much better via the [670]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -7790,13 +7809,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 [669]Qt-embedded apps (PDAs/Handhelds.) By default the + fullscreen, or [671]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 [670]this FAQ for details. If specified via "-rawfb Video" + kernel. See [672]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.) @@ -7804,10 +7823,10 @@ minal #2) also useful in testing. - All of the above [671]-rawfb options are just for viewing the raw + All of the above [673]-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 [672]video camera mapped its framebuffer + this feature (e.g. suppose a [674]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 @@ -7845,7 +7864,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 [673]active VT) one + view and interact with VT #2 (assuming it is the [675]active VT) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -7900,7 +7919,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 - [674]Qt-embedded Also, for example the [675]VMWare Fullscreen mode is + [676]Qt-embedded Also, for example the [677]VMWare Fullscreen mode is actually viewable under -rawfb and can be interacted with if uinput is enabled. @@ -7965,9 +7984,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 [676]-rawfb option. + Yes, this is possible to some degree with the [678]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [677]previous FAQ on -rawfb + used for the screen image data. See the [679]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -7979,7 +7998,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 [678]-snapfb mode which appears to be necessary. + The "snap:" enforces [680]-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. @@ -8001,7 +8020,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 [679]-24to32 option will be automatically imposed when in + etc, the [681]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -8009,7 +8028,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 [680]-wait, [681]-slow_fb, or [682]-defer + the framerate via the [682]-wait, [683]-slow_fb, or [684]-defer options. Decreasing the window size and bpp also helps. @@ -8098,7 +8117,7 @@ minal #2) format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [683]-freqtab option to supply your own xawtv channel to + See also the [685]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc.) @@ -8107,7 +8126,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 [684]-rawfb scheme where the + Yes, the basic method for this is the [686]-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: @@ -8120,7 +8139,7 @@ minal #2) x11vnc -rawfb /dev/fb0@640x480x16 Also, to force usage of the uinput injection method use "-pipeinput - UINPUT". See the [685]-pipeinput description for tunable parameters, + UINPUT". See the [687]-pipeinput description for tunable parameters, etc. One problem with the x11vnc uinput scheme is that it cannot guess the @@ -8136,7 +8155,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 [686]-pipeinput UINPUT option for tuning + times a second. See the [688]-pipeinput UINPUT option for tuning parameters that can be set (there are some experimental thresh=N tuning parameters as well) @@ -8171,7 +8190,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 [687]-rawfb only + Yes, as of Jul/2006 x11vnc enables building for [689]-rawfb only support. Just do something like when building: ./configure --without-x (plus any other flags) make @@ -8187,11 +8206,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 - [688]-rawfb mechanism described above. The mouse and keyboard input is + [690]-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 [689]OSXvnc (aka Vine - Server), or [690]Apple Remote Desktop (ARD). Perhaps there is some + So you can use x11vnc as an alternative to [691]OSXvnc (aka Vine + Server), or [692]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. @@ -8201,7 +8220,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 [691]-id windowid mode (and the + only work reasonably in single window [693]-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 @@ -8219,9 +8238,9 @@ minal #2) ./configure --without-x make - Win2VNC/x2vnc: One handy use is to use the [692]-nofb mode to + Win2VNC/x2vnc: One handy use is to use the [694]-nofb mode to redirect mouse and keyboard input to a nearby Mac (i.e. one to the - side of your desk) via [693]x2vnc or Win2VNC. See [694]this FAQ for + side of your desk) via [695]x2vnc or Win2VNC. See [696]this FAQ for more info. Options: Here are the Mac OS X specific x11vnc options: @@ -8295,13 +8314,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 "[695]-reflect host:N" option to + Yes, as of Feb/2007 there is the "[697]-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 - [696]-rawfb description under "VNC HOST" for more details. + [698]-rawfb description under "VNC HOST" for more details. You can replace "host:N" with "listen" or "listen:port" for reverse connections. @@ -8362,18 +8381,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 [697]-nodragging if the + not doing wireframing somehow, consider [699]-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: - [698]http://sourceforge.net/projects/vnc-reflector/, - [699]http://www.tightvnc.com/projector/ (closed source?), + [700]http://sourceforge.net/projects/vnc-reflector/, + [701]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 "[700]"-connect host1,host2,..." option.) + connections (the x11vnc "[702]"-connect host1,host2,..." option.) Suppose all the clients "C" are started up in Listen mode: client1> vncviewer -listen client2> vncviewer -listen @@ -8432,7 +8451,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 [701]this FAQ. + 755 ./x11vnc.static" and then find the -auth file as in [703]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 @@ -8441,8 +8460,8 @@ rm -f $tmp wget http://192.168.0.22/x11vnc.static chmod 755 ./x11vnc.static - Find the name of the auth file as in [702]this FAQ. (maybe run "ps - wwwwaux | grep auth".) Then run it like this: + Find the name of the auth file as in [704]this FAQ. (maybe run "ps + wwwaux | grep auth".) Then run it like this: ./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile then press Alt-F7 to go back to the X install. You should now be able @@ -8450,7 +8469,7 @@ rm -f $tmp the display being :1, etc. If there is a firewall blocking incoming connections during the - install, use the [703]"-connect hostname" option option for a reverse + install, use the [705]"-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 @@ -8512,7 +8531,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 [704]this jwz link for more information. + "Shift+Insert". See [706]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 @@ -8529,18 +8548,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 - [705]-nosel option. + [707]-nosel option. * If you want changes in PRIMARY to be ignored use the - [706]-noprimary option. + [708]-noprimary option. * If you want changes in CLIPBOARD to be ignored use the - [707]-noclipboard option. + [709]-noclipboard option. * If you don't want x11vnc to set PRIMARY to the "CutText" received - from viewers use the [708]-nosetprimary option. + from viewers use the [710]-nosetprimary option. * If you don't want x11vnc to set CLIPBOARD to the "CutText" - received from viewers use the [709]-nosetclipboard option. + received from viewers use the [711]-nosetclipboard option. - You can also fine-tune it a bit with the [710]-seldir dir option and - also [711]-input. + You can also fine-tune it a bit with the [712]-seldir dir option and + also [713]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -8552,7 +8571,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 - [712]pyvnc2swf. There are a number of [713]tutorials (broken link?) on + [714]pyvnc2swf. There are a number of [715]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 @@ -8567,11 +8586,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux.) - The [714]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [716]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 [715]-tightfilexfer option. + the [717]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -8594,7 +8613,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 [716]-users option, then VNC Viewers that connect are able to do + the [718]-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 @@ -8613,7 +8632,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [717]-ultrafilexfer which is an alias for the above option and + Or use [719]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -8625,18 +8644,18 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [718]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [720]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [719]-noultraext (the + To disable SingleWindow and ServerInput use [721]-noultraext (the others are managed by LibVNCServer.) See this option too: - [720]-noserverdpms. + [722]-noserverdpms. - Also, the [721]UltraVNC repeater proxy is supported for use with - reverse connections: "[722]-connect repeater://host:port+ID:NNNN". Use + Also, the [723]UltraVNC repeater proxy is supported for use with + reverse connections: "[724]-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: - [723]ultravnc_repeater.pl + [725]ultravnc_repeater.pl Q-123: Can x11vnc emulate UltraVNC's Single Click helpdesk mode for @@ -8644,12 +8663,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [724]Single Click (SC) mode can be emulated fairly + Yes, UltraVNC's [726]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 [725]Mac OS X. + or family to use. This includes [727]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 @@ -8705,7 +8724,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 [726]this page for some variations on this method, e.g. how to add + See [728]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -8717,11 +8736,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 [727]here. + reverse connections.) More info [729]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [728]router will have to be configured to + NAT/Firewall/Router the [730]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. @@ -8731,7 +8750,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. [729]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [731]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -8767,7 +8786,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 [730]Enhanced TightVNC Viewer (SSVNC) package we + better use the [732]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 @@ -8797,11 +8816,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 [731]-ssl + The only change from the "vnc" above is the addition of the [733]-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 [732]here.) + info [734]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -8810,7 +8829,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 [733]Enhanced TightVNC Viewer + The easiest way to do this is use [735]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 @@ -8840,7 +8859,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 [734]this link and [735]this one too for more info on SSL certs. + See [736]this link and [737]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 @@ -8861,7 +8880,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [736]here. + [738]here. OpenSSL libssl.so.0.9.7 problems: @@ -8871,7 +8890,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [737]details here. + You will find the [739]details here. Q-124: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -8880,7 +8899,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 [738]Samba example here. + We show a simple [740]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: @@ -8920,7 +8939,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 [739]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.) @@ -8930,7 +8949,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 [740]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [742]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.) @@ -9012,7 +9031,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 [741]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [743]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing.) @@ -9113,7 +9132,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 [742]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [744]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing.) @@ -9125,14 +9144,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 [743]-nobell option. If + If you don't want to hear the beeps use the [745]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [744]redirector such as esd. + trying a [746]redirector such as esd. Q-128: Does x11vnc work with IPv6? - Currently the only way to do this is via [745]inetd. You configure + Currently the only way to do this is via [747]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. @@ -9141,7 +9160,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 [746]IPv6 enabled, so a + Also note that not all VNC Viewers are [748]IPv6 enabled, so a redirector could even be needed on the client side. @@ -9509,402 +9528,404 @@ References 348. http://sourceforge.net/projects/vencrypt/ 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls - 351. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers - 352. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-vnc-viewers - 353. http://www.karlrunge.com/x11vnc/ssl.html - 354. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer - 355. http://www.karlrunge.com/x11vnc/ssl.html - 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslonly + 352. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers + 353. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-vnc-viewers + 354. http://www.karlrunge.com/x11vnc/ssl.html + 355. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 356. http://www.karlrunge.com/x11vnc/ssl.html 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 358. http://www.stunnel.org/ - 359. http://www.karlrunge.com/x11vnc/faq.html#infaq_viewer-side-stunnel - 360. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer - 361. http://www.karlrunge.com/x11vnc/ssvnc.html - 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 364. http://sc.uvnc.com/javaviewer/index.html - 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 366. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-router-redir - 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 368. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal - 369. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy - 370. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal - 371. http://www.karlrunge.com/x11vnc/index.html#firewalls - 372. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpport - 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 376. http://www.karlrunge.com/x11vnc/ssl-output.html - 377. http://www.karlrunge.com/x11vnc/java_console_direct.html - 378. http://www.karlrunge.com/x11vnc/ssvnc.html - 379. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext - 380. http://www.karlrunge.com/x11vnc/ss_vncviewer - 381. http://www.karlrunge.com/x11vnc/ssl-portal.html - 382. http://www.karlrunge.com/x11vnc/ssl.html - 383. http://www.karlrunge.com/x11vnc/ssvnc.html - 384. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 385. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers - 386. http://www.karlrunge.com/x11vnc/java_console_proxy.html - 387. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer - 388. http://www.karlrunge.com/x11vnc/ssvnc.html - 389. http://www.karlrunge.com/x11vnc/ssl-portal.html - 390. http://www.karlrunge.com/x11vnc/ssl.html - 391. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously - 392. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd - 393. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin - 394. http://www.karlrunge.com/x11vnc/faq.html#infaq_x11vnc_loop - 395. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset - 396. http://www.karlrunge.com/x11vnc/index.html#firewalls - 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 398. http://www.karlrunge.com/x11vnc/faq.html#infaq_dtlogin_solaris - 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen - 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 401. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 359. http://www.stunnel.org/ + 360. http://www.karlrunge.com/x11vnc/faq.html#infaq_viewer-side-stunnel + 361. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 362. http://www.karlrunge.com/x11vnc/ssvnc.html + 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 364. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 365. http://sc.uvnc.com/javaviewer/index.html + 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 367. http://www.karlrunge.com/x11vnc/faq.html#infaq_ssl-router-redir + 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 369. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal + 370. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy + 371. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-portal + 372. http://www.karlrunge.com/x11vnc/index.html#firewalls + 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpport + 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 377. http://www.karlrunge.com/x11vnc/ssl-output.html + 378. http://www.karlrunge.com/x11vnc/java_console_direct.html + 379. http://www.karlrunge.com/x11vnc/ssvnc.html + 380. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext + 381. http://www.karlrunge.com/x11vnc/ss_vncviewer + 382. http://www.karlrunge.com/x11vnc/ssl-portal.html + 383. http://www.karlrunge.com/x11vnc/ssl.html + 384. http://www.karlrunge.com/x11vnc/ssvnc.html + 385. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 386. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers + 387. http://www.karlrunge.com/x11vnc/java_console_proxy.html + 388. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 389. http://www.karlrunge.com/x11vnc/ssvnc.html + 390. http://www.karlrunge.com/x11vnc/ssl-portal.html + 391. http://www.karlrunge.com/x11vnc/ssl.html + 392. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously + 393. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 394. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 395. http://www.karlrunge.com/x11vnc/faq.html#infaq_x11vnc_loop + 396. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset + 397. http://www.karlrunge.com/x11vnc/index.html#firewalls + 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 400. http://www.karlrunge.com/x11vnc/faq.html#infaq_dtlogin_solaris + 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N - 405. http://www.jirka.org/gdm-documentation/x241.html - 406. http://www.karlrunge.com/x11vnc/x11vnc_loop - 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 408. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth - 409. http://www.karlrunge.com/x11vnc/index.html#firewalls - 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q, - 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 413. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin - 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi - 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns - 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf - 417. http://www.avahi.org/ - 418. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd - 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 421. http://www.karlrunge.com/x11vnc/faq.html#infaq_stunnel-inetd - 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 428. http://www.karlrunge.com/x11vnc/find_display.html - 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 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-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 + 403. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 405. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N + 407. http://www.jirka.org/gdm-documentation/x241.html + 408. http://www.karlrunge.com/x11vnc/x11vnc_loop + 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 410. http://www.karlrunge.com/x11vnc/faq.html#faq-xterminal-xauth + 411. http://www.karlrunge.com/x11vnc/index.html#firewalls + 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q, + 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 415. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi + 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns + 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf + 419. http://www.avahi.org/ + 420. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 423. http://www.karlrunge.com/x11vnc/faq.html#infaq_stunnel-inetd + 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 430. http://www.karlrunge.com/x11vnc/find_display.html + 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 434. http://www.karlrunge.com/x11vnc/faq.html#faq-unix-passwords + 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 438. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int + 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 442. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 444. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 445. http://www.karlrunge.com/x11vnc/ssvnc.html + 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create_xsrv + 450. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 457. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy + 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit + 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect 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 + 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 465. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess + 466. http://www.karlrunge.com/x11vnc/faq.html#infaq_localaccess + 467. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 474. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 475. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 476. http://www.karlrunge.com/x11vnc/Xdummy + 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 478. http://www.karlrunge.com/x11vnc/xdm_one_shot.html + 479. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously + 480. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 486. http://www.karlrunge.com/x11vnc/shm_clear + 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 489. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm + 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb + 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 498. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 499. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc + 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 503. http://www.tightvnc.com/ + 504. http://www.karlrunge.com/x11vnc/ssvnc.html + 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 508. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching + 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds + 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-appshare + 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout + 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 523. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 528. http://minimyth.org/ + 529. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl + 530. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode 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-wireframe - 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 536. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 537. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect + 538. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode + 539. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow 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 + 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 543. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect + 547. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip + 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 552. http://www.karlrunge.com/x11vnc/index.html#beta-test + 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 554. http://www.karlrunge.com/x11vnc/ssvnc.html + 555. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap + 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 558. http://www.virtualgl.org/About/TurboVNC + 559. http://www.virtualgl.org/ + 560. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 563. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 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 + 565. http://www.karlrunge.com/x11vnc/bins + 566. http://www.karlrunge.com/x11vnc/ssvnc.html + 567. http://www.virtualgl.org/About/Reports + 568. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 572. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode + 573. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 574. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks + 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 580. http://www.karlrunge.com/x11vnc/ssvnc.html + 581. http://www.tightvnc.com/ + 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape 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/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-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-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 + 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 590. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 591. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 599. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 601. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes 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-remap - 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 615. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 618. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock + 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 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 + 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 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 + 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 632. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling + 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 634. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html + 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 644. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm + 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 648. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama + 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 653. http://www.karlrunge.com/x11vnc/ssvnc.html + 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 655. http://www.jwz.org/xscreensaver/man1.html + 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 657. http://www.beryl-project.org/ + 658. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 659. http://www.dslinux.org/blogs/pepsiman/?p=73 + 660. http://minimyth.org/ 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 + 662. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 663. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 669. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 670. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 671. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded 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-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/ssvnc.html + 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 674. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 675. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 676. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 677. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware + 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 679. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 684. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 686. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 691. http://www.testplant.com/products/vine_server/OS_X + 692. http://www.apple.com/remotedesktop/ + 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 695. http://fredrik.hubbe.net/x2vnc.html + 696. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc + 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 700. http://sourceforge.net/projects/vnc-reflector/ + 701. http://www.tightvnc.com/projector/ + 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 703. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 704. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 706. http://www.jwz.org/doc/x-cut-and-paste.html + 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 708. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noclipboard + 710. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetprimary + 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetclipboard + 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 713. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 714. http://www.unixuser.org/~euske/vnc2swf/ + 715. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ + 716. http://www.karlrunge.com/x11vnc/ssvnc.html + 717. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 718. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 719. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 720. http://www.karlrunge.com/x11vnc/ssvnc.html + 721. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 722. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 723. http://www.uvnc.com/addons/repeater.html + 724. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 725. http://www.karlrunge.com/x11vnc/ultravnc_repeater.pl + 726. http://www.uvnc.com/addons/singleclick.html + 727. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx + 728. http://www.karlrunge.com/x11vnc/single-click.html + 729. http://www.karlrunge.com/x11vnc/single-click.html + 730. http://www.karlrunge.com/x11vnc/index.html#firewalls + 731. http://sc.uvnc.com/ + 732. http://www.karlrunge.com/x11vnc/ssvnc.html + 733. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl 734. http://www.karlrunge.com/x11vnc/single-click.html - 735. http://www.karlrunge.com/x11vnc/ssl.html + 735. http://www.karlrunge.com/x11vnc/ssvnc.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/ + 737. http://www.karlrunge.com/x11vnc/ssl.html + 738. http://www.karlrunge.com/x11vnc/single-click.html + 739. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 740. http://www.samba.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 + 742. http://www.cups.org/ + 743. http://www.karlrunge.com/x11vnc/ssvnc.html + 744. http://www.karlrunge.com/x11vnc/ssvnc.html + 745. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 746. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 747. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 748. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -10401,32 +10422,32 @@ http://www.karlrunge.com/x11vnc/ssl.html: The encryption this provides protects against all passive sniffing of the VNC traffic and passwords on the network and so it is quite good, - but it does not prevent a Man-In-The-Middle attack: e.g. an attacker - intercepts the VNC client stream and sends it his own Public key for - SSL negotiation (pretending to be the server). Then it makes a + but it does not prevent a Man-In-The-Middle active attack: e.g. an + attacker intercepts the VNC client stream and sends it his own Public + key for SSL negotiation (pretending to be the server). Then it makes a connection to SSL x11vnc itself and forwards the data back and forth. He can see all the traffic and modify it as well. Most people don't seem to worry about Man-In-The-Middle attacks these - days; they are more concerned about passive sniffing. Perhaps someday - that will change if attack tools are used more widely to perform the - attack. There are hacker tools like dsniff/webmitm and cain that - implement SSL Man-In-The-Middle attacks. They rely on the client not - bothering to check the cert. + days; they are more concerned about passive sniffing of passwords, + etc. Perhaps someday that will change if attack tools are used more + widely to perform the attack. NOTE: There are hacker tools like + dsniff/webmitm and cain that implement SSL Man-In-The-Middle attacks. + They all rely on the client not bothering to check that the cert is + valid. If you are not worried about Man-In-The-Middle attacks you do not have - to read the techniques described in the rest of this page. + to read the techniques described in the rest of this document. To prevent Man-In-The-Middle attacks, certificates must somehow be verified. This requires the VNC client side have some piece of information that can be used to verify the SSL x11vnc server. - Alternatively, although rarely done, x11vnc could verify VNC Clients' - certificates, see the [1]-sslverify option that is discussed briefly - below. + Alternatively, although rarely done, x11vnc can verify VNC Clients' + certificates, see the [1]-sslverify option that is discussed below. - There are a number of ways to have the client authenticate x11vnc. The - quickest way perhaps would be to copy (safely) the certificate x11vnc - prints out: + There are a number of ways to have the client authenticate the SSL + x11vnc server. The quickest way perhaps would be to copy (safely) the + certificate x11vnc prints out: 26/03/2006 21:12:00 Creating a temporary, self-signed PEM certificate... ... -----BEGIN CERTIFICATE----- @@ -10446,7 +10467,7 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM browser on the viewing side. If he gets a dialog that the certificate is not verified he knows something is wrong. It may be a Man-In-The-Middle attack, but more likely x11vnc certificate has - changed or expired or his browser was reinstalled and lost the + changed or expired or his browser was reinstalled and/or lost the certificate, etc, etc. As another example, if the user was using [2]stunnel with his VNC @@ -10467,15 +10488,17 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM certificate file you safely copied there. Note that in principle the copying of the certificate to the client - machine(s) itself could be altered in a Man-In-The-Middle attack! You - can't win. It is unlikely the attacker could predict how you were - going to send it unless you had, say, done it many times before the - same way. SSH is a very good way to send it (but of course it too - depends on public keys being sent unaltered between the two - machines!). If you are really paranoid, I'm sure you'll figure out a - really good way to transport the certificates. See the Certificate - Authority scheme below for a way to make this easier (you just have to - do it once). + machine(s) itself could be altered by a Man-In-The-Middle attack! You + can't win; it is very difficult to be completely secure. It is + unlikely the attacker could predict how you were going to send it + unless you had, say, done it many times before the same way. SSH is a + very good way to send it (but of course it too depends on public keys + being sent unaltered between the two machines!). + + If you are really paranoid, I'm sure you'll figure out a really good + way to transport the certificates. See the Certificate Authority + scheme below for a way to make this easier (you just have to do it + once). _________________________________________________________________ @@ -10483,21 +10506,22 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM Now, it would be very inconvenient to copy the new temporary certificate every time x11vnc is run in SSL mode. So for convenience - there is the "SAVE" keyword (this is now the default) to instruct - x11vnc to save the certificate it creates: + there is the "SAVE" keyword to instruct x11vnc to save the certificate + it creates: x11vnc -ssl SAVE -display :0 ... - This way it will save the certificate and private key in these files: + This behavior is now the default, you must use "TMP" for a temporary + one. It will save the certificate and private key in these files: ~/.vnc/certs/server.crt ~/.vnc/certs/server.pem - The ".crt" file contains only the certificate and should be copied to - the VNC Viewer machine(s) that will be authenticating the x11vnc - server. The ".pem" file contains both the certificate and the private - key and should be kept secret. (If you don't like the default location - ~/.vnc/certs, e.g. it is on an NFS share and you are worried about - local network sniffing, use the [6]-ssldir dir option to point to a - different directory.) + The ".crt" file contains only the certificate and should be safely + copied to the VNC Viewer machine(s) that will be authenticating the + x11vnc server. The ".pem" file contains both the certificate and the + private key and should be kept secret. (If you don't like the default + location ~/.vnc/certs, e.g. it is on an NFS share and you are worried + about local network sniffing, use the [6]-ssldir dir option to point + to a different directory.) So the next time you run "x11vnc -ssl SAVE ..." it will read the server.pem file directly instead of creating a new one. @@ -10533,7 +10557,7 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM to make it harder for an untrusted user to copy the file. A better way is to also encrypt the private key with a passphrase. You are prompted whether you want to do this or not when the key is first created under - "-ssl SAVE" mode ("Protect key with a passphrase? [y]/n"). It is + "-ssl SAVE" mode ("Protect key with a passphrase? y/n"). It is suggested that you use a passphrase. The inconvenience is every time you run "x11vnc -ssl SAVE ..." you will need to supply the passphrase to access the private key: @@ -10594,32 +10618,31 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM the x11vnc server. Once distributed to the client machines, there is no need to keep the client key on the CA machine that generated and signed it. You can keep the client certs if you like because they are - public, and they could also be used let in only a subset of all the - clients. (see [9]-sslverify) + public. _________________________________________________________________ How to do the above CA steps with x11vnc: Some utility commands are provided to ease the cert+key creation, - signing, and management: [10]-sslGenCA, [11]-sslGenCert, - [12]-sslDelCert, [13]-sslEncKey, [14]-sslCertInfo. They basically run + signing, and management: [9]-sslGenCA, [10]-sslGenCert, + [11]-sslDelCert, [12]-sslEncKey, [13]-sslCertInfo. They basically run the openssl(1) command for you to manage the certs/keys. It is required that openssl(1) is installed on the machine and available in PATH. All commands can be pointed to an alternate toplevel certificate - directory via the [15]-ssldir option if you don't want to use the + directory via the [14]-ssldir option if you don't want to use the default ~/.vnc/certs. 1) To generate your Certificate Authority (CA) cert and key run this: x11vnc -sslGenCA - Follow the prompts, you can modify any information strings you care + Follow the prompts, you can modify any informational strings you care to. You will also be required to encrypt the CA private key with a passphrase. This generates these files: ~/.vnc/certs/CA/cacert.pem (the CA public certificate) - ~/.vnc/certs/CA/private/cakey.pem (the CA private key) + ~/.vnc/certs/CA/private/cakey.pem (the encrypted CA private key) - If you want to use a different directory use [16]-ssldir It must + If you want to use a different directory use [15]-ssldir It must supplied with all subsequent SSL utility options to point them to the correct directory. @@ -10627,7 +10650,7 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM x11vnc -sslGenCert server As with the CA generation, follow the prompts and you can modify any - information strings you care to. This will create the files: + informational strings that you care to. This will create the files: ~/.vnc/certs/server.crt (the server public certificate) ~/.vnc/certs/server.pem (the server private key + public cert) @@ -10638,7 +10661,7 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM 3) Start up x11vnc using this server key: x11vnc -ssl SAVE -display :0 ... - (SAVE corresponds to server.pem, see [17]-sslGenCert server somename + (SAVE corresponds to server.pem, see [16]-sslGenCert server somename info on creating additional server keys, server-somename.crt ...) 4) Next, safely copy the CA certificate to the VNC viewer (client) @@ -10646,7 +10669,7 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM scp ~/.vnc/CA/cacert.pem clientmachine:. 5) Then the tricky part, make it so the SSL VNC Viewer uses this - certificate. There are a number of ways this might be done, it depends + certificate! There are a number of ways this might be done, it depends on what your client and/or SSL tunnel is. Some examples: For the SSL Java VNC viewer supplied with x11vnc in @@ -10677,13 +10700,13 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM (then point the VNC viewer to localhost:1). Here is an example for the Unix stunnel wrapper script - [18]ss_vncviewer: + [17]ss_vncviewer in our SSVNC package: ss_vncviewer -verify ./cacert.pem far-away.east:0 - Our [19]SSVNC enhanced tightvnc viewer can also use the certificate - file for server authentication. You can load it via the SSVNC - 'Certs...' dialog and set 'ServerCert' to the cacert.pem file you - safely copied there. + Our [18]SSVNC enhanced tightvnc viewer GUI can also use the + certificate file for server authentication. You can load it via the + SSVNC 'Certs...' dialog and set 'ServerCert' to the cacert.pem file + you safely copied there. _________________________________________________________________ @@ -10711,18 +10734,19 @@ NTIwLjQxMTE2OTEPMA0GA1UEChMGeDExdm5jMS4wLAYDVQQDEyV4MTF2bmMtU0VM Using external CA's: - You don't have to use your own CA cert+key you can use a third - party's. Perhaps you have a company-wide CA or you can even have your - x11vnc certificate signed by a professional CA (e.g. www.thawte.com or - www.verisign.com or perhaps the free certificate service - www.startcom.org or www.cacert.org). + You don't have to use your own CA cert+key, you can use a third + party's instead. Perhaps you have a company-wide CA or you can even + have your x11vnc certificate signed by a professional CA (e.g. + www.thawte.com or www.verisign.com or perhaps the free certificate + service www.startcom.org or www.cacert.org). The advantage to doing this is that the VNC client machines will already have the CA certificates installed and you don't have to install it on each machine. To generate an x11vnc server cert+key this way you should generate a - "request" for a certicate signing something like this: + "request" for a certicate signing something like this (we use the name + "external" in this example, it could be anything you want): x11vnc -sslGenCert server req:external This will create the request file: @@ -10740,7 +10764,14 @@ pem pem You also rename the two files (.crt and .pem) to have a shorter - basename if you like. + basename if you like. E.g.: + mv ~/.vnc/certs/server-req:external.pem ~/.vnc/certs/server-ext.pem + mv ~/.vnc/certs/server-req:external.crt ~/.vnc/certs/server-ext.crt + + and the use via "x11vnc -ssl SAVE-ext ...", etc. + + On the viewer side make sure the external CA's certificate is + installed an available for the VNC viewer software you plan to use. _________________________________________________________________ @@ -10756,8 +10787,8 @@ pem ... As usual, follow the prompts if you want to change any of the info - field values. As always, it is a good idea to protect the private keys - with a passphrase. These files are created: + field values. As always, it is a good idea (although inconvenient) to + protect the private keys with a passphrase. These files are created: ~/.vnc/certs/clients/dilbert.crt ~/.vnc/certs/clients/dilbert.pem ... @@ -10774,14 +10805,16 @@ pem After copying them you can delete the clients/*.pem files for extra safety because the private keys are not needed by the x11vnc server. You don't really need the clients/*.crt files either (because they - have been signed by the CA). But they could come in handy if you - wanted to let in just one client and are necessary for self-signed - client certificates. + have been signed by the CA). But they could come in handy for tracking + or troubleshooting, etc. Now start up x11vnc and instruct it to verify connecting clients via SSL and the CA cert: x11vnc -ssl SAVE -sslverify CA + The "CA" special token instructs x11vnc to use its CA signed certs for + verification. + For arbitrary self-signed client certificates (no CA) it might be something like this: x11vnc -ssl SAVE -sslverify path/to/client.crt @@ -10790,19 +10823,19 @@ pem Where client.crt would be an individual client certificate; client-hash-dir a directory of file names based on md5 hashes of the - certs (see [20]-sslverify); and certs.txt signifies a single file full + certs (see [19]-sslverify); and certs.txt signifies a single file full of client certificates. Finally, connect with your VNC viewer using the key. Here is an - example for the Unix stunnel wrapper script [21]ss_vncviewer: using + example for the Unix stunnel wrapper script [20]ss_vncviewer: using client authentication (and the standard server authentication with the CA cert): ss_vncviewer -mycert ./dilbert.pem -verify ./cacert.pem far-away.east:0 - Our [22]SSVNC enhanced tightvnc viewer can also use these openssl .pem + Our [21]SSVNC enhanced tightvnc viewer can also use these openssl .pem files (you can load them via Certs... -> MyCert dialog). - It is also possible to use [23]-sslverify on a per-client key basis, + It is also possible to use [22]-sslverify on a per-client key basis, and also using self-signed client keys (x11vnc -sslGenCert client self:dilbert) @@ -10824,9 +10857,9 @@ pem sufficient and can be read by Mozilla/Firefox and Java... If you have trouble getting your Java Runtime to import and use the - cert+key, there is a workaround for the [24]SSL-enabled Java applet. + cert+key, there is a workaround for the [23]SSL-enabled Java applet. On the Web browser URL that retrieves the VNC applet, simply add a - "/?oneTimeKey=..." applet parameter (see [25]ssl-portal for more + "/?oneTimeKey=..." applet parameter (see [24]ssl-portal for more details on applet parameters; you don't need to do the full portal setup though). The value of the oneTimeKey will be the very long string that is output of the onetimekey program found in the @@ -10837,19 +10870,29 @@ pem HTTPS site via password. A cgi program then makes a one time key for the logged in user to use: it is passed back over HTTPS as the applet parameter in the URL and so cannot be sniffed. x11vnc is run to use - that key via [26]-sslverify. + that key via [25]-sslverify. Update: as of Apr 2007 in the 0.9.1 x11vnc tarball there is a new - option setting "[27]-users sslpeer=" that will do a switch user much - like [28]-unixpw does, but this time using the emailAddress field of + option setting "[26]-users sslpeer=" that will do a switch user much + like [27]-unixpw does, but this time using the emailAddress field of the Certificate subject of the verified Client. This mode requires - [29]-sslverify turned on to verify the clients via SSL. This mode can - be useful in situations using [30]-create or [31]-svc where a new X + [28]-sslverify turned on to verify the clients via SSL. This mode can + be useful in situations using [29]-create or [30]-svc where a new X server needs to be started up as the authenticated user (but unlike in -unixpw mode, the unix username is not obviously known). _________________________________________________________________ + Revoking Certificates: + + A large, scaled-up installation may benefit from being able to revoke + certificates (e.g. suppose a user's laptop with a vnc client or server + key is compromised.) You can use this option with x11vnc: [31]-sslCRL. + See the info at that link for a guide on what openssl(1) commands you + will need to run to revoke a certificate. + + _________________________________________________________________ + Additional utlities: You can get information about your keys via [32]-sslCertInfo. These @@ -10879,11 +10922,215 @@ pem _________________________________________________________________ + Chained Certificates: + + There is increasing interest in using chained CA's instead of a single + CA. The merits of using chained CA's are not described here besides to + say its use may make some things easier when a certificate needs to be + revoked. + + x11vnc supports chained CA certificates. We describe a basic use case + here. + + Background: Of course the most straight forward way to use SSL with + x11vnc is to use no CA at all (see above): a self-signed certificate + and key is used and its certificate needs to be safely copied to the + client side. This is basically the same as the SSH style of managing + keys. Next level up, one can use a single CA to sign server keys: then + only the CA's certificate needs to be safely copied to the client + side, this can happen even before any server certs are created (again, + see all of the discussion above.) + + With a certificate chain there are two or more CA's involved. Perhaps + it looks like this: + root_CA ---> intermediate_CA ---> server_cert + + Where the arrow basically means "signs". + + In this usage mode the client (viewer-side) will have root_CA's + certificate available for verifying (and nothing else.) If the viewer + only received server_cert's certificate, it would not have enough info + to verify the server. The client needs to have intermediate_CA's cert + as well. The way to do this with x11vnc (i.e. an OpenSSL using app) is + to concatenate the server_cert's pem and the intermediate_CA's + certificate together. + + For example, suppose the file intermediate_CA.crt had + intermediate_CA's certificate. And suppose the file server_cert.pem + had the server's certificate and private key pair as described above + on this page. We need to do this: + cat intermediate_CA.crt >> server_cert.pem + + (Note: the order of the items inside the file matters; intermediate_CA + must be after the server key and cert) and then we run x11vnc like + this: + x11vnc -ssl ./server_cert.pem ... + + Then, on the VNC viewer client side, the viewer authenticates the + x11vnc server by using root_CA's certificate. Suppose that is in a + file named root_CA.crt, then using the SSVNC wrapper script + [33]ss_vncviewer (which is also included in the [34]SSVNC package) as + our example, we have: + ss_vncviewer -verify ./root_CA.crt hostname:0 + + (where "hostname" is the machine where x11vnc is running.) One could + also use the SSVNC GUI setting Certs -> ServerCert to the root_CA.crt + file. Any other SSL enabled VNC viewer would use root_CA.crt in a + similar way. + _________________________________________________________________ + + Creating Chained Certificates: + + Here is a fun example using VeriSign's "Trial Certificate" program. + Note that VeriSign has a Root CA and also an Intermediate CA and uses + the latter to sign customers certificates. So this provides an easy + way to test out the chained certificates mechanism with x11vnc. + + First we created a test x11vnc server key: + openssl genrsa -out V1.key 1024 + + then we created a certificate signing request (CSR) for it: + openssl req -new -key V1.key -out V1.csr + + (we followed the prompts and supplied information for the various + fields.) + + Then we went to VeriSign's page http://www.verisign.com/ssl/index.html + and clicked on "FREE TRIAL" (the certificate is good for 14 days.) We + filled in the forms and got to the point where it asked for the CSR + and so we pasted in the contents of the above V1.csr file. Then, after + a few more steps, VeriSign signed and emailed us our certificate. + + The VeriSign Trial certificates were found here: + http://www.verisign.com/support/verisign-intermediate-ca/Trial_Secure_Server_ +Root/index.html + http://www.verisign.com/support/verisign-intermediate-ca/trial-secure-server- +intermediate/index.html + + The former was pasted into a file V-Root.crt and the latter was pasted + into V-Intermediate.crt + + We pasted our Trial certificate that VeriSign signed and emailed to us + into a file named V1.crt and then we typed: + cat V1.key V1.crt > V1.pem + cat V1.pem V-Intermediate.crt > V1-combined.pem + chmod 600 V1.pem V1-combined.pem + + So now the file V1-combined.pem has our private key and (VeriSign + signed) certificate and VeriSign's Trial Intermediate certificate. + + Next, we start x11vnc: + x11vnc -ssl ./V1-combined.pem ... + + and finally, on the viewer side (SSVNC wrapper script example): + ss_vncviewer -verify ./V-Root.crt hostname:0 + + One will find that only that combination of certs and keys will work, + i.e. allow the SSL connection to be established. Every other + combination we tried failed (note that ss_vncviewer uses the external + stunnel command to handle the SSL so we are really testing stunnel's + SSL implementation on the viewer side); and so the system works as + expected. + _________________________________________________________________ + + VNC Client Authentication using Certificate Chains: + + Now, going the other way around with the client authenticating himself + via this chain of SSL certificates, x11vnc is run this way: + x11vnc -ssl SAVE -sslverify ./V-Root.crt ... + + (note since the server must always supply a cert, we use its normal + self-signed, etc., one via "-ssl SAVE" and use the VeriSign root cert + for client authentication via [35]-sslverify. The viewer must now + supply the combined certificates, e.g.: + ss_vncviewer -mycert ./V1-combined.pem hostname:0 + _________________________________________________________________ + + Using OpenSSL and x11vnc to create Certificate Chains: + + Although the x11vnc CA mechanism (-sslGenCA and -sslGenCert; see + above) was designed to only handle a single root CA (to sign server + and/or client certs) it can be coerced into creating a certificate + chain by way of an extra openssl(1) command. + + We will first create two CA's via -sslGenCA; then use one of these CA + to sign the other; create a new (non-CA) server cert; and append the + intermediate CA's cert to the server cert to have everything needed in + the one file. + + Here are the commands we ran to do what the previous paragraph + outlines. + + First we create the two CA's, called CA_root and CA_Intermediate here, + in separate directories via x11vnc: + x11vnc -ssldir ~/CA_Root -sslGenCA + (follow the prompts, we included "CA_Root", e.g. Common Name, to aid ident +ifying it) + + x11vnc -ssldir ~/CA_Intermediate -sslGenCA + (follow the prompts, we included "CA_Intermediate", e.g. Common Name, to a +id identifying it) + + Next backup CA_Intermediate's cert and then sign it with CA_Root: + mv ~/CA_Intermediate/CA/cacert.pem ~/CA_Intermediate/CA/cacert.pem.ORIG + cd ~/CA_Root + openssl ca -config ./CA/ssl.cnf -policy policy_anything -extensions v3_ca -no +text -ss_cert ~/CA_Intermediate/CA/cacert.pem.ORIG -out ~/CA_Intermediate/CA/ca +cert.pem + + Note that it is required to cd to the ~/CA_Root directory and run the + openssl command from there. + + You can print out info about the cert you just modified by: + openssl x509 -noout -text -in ~/CA_Intermediate/CA/cacert.pem + + Now we create an x11vnc server cert named "test_chain" that is signed + by CA_Intermediate: + x11vnc -ssldir ~/CA_Intermediate -sslGenCert server test_chain + (follow the prompts) + + You can print out information about this server cert just created via + this command: + x11vnc -ssldir ~/CA_Intermediate -sslCertInfo SAVE-test_chain + + This will tell you the full path to the server certificate, which is + needed because we need to manually append the CA_Intermediate cert for + the chain to work: + cat ~/CA_Intermediate/CA/cacert.pem >> ~/CA_Intermediate/server-test_chain.pe +m + + Now we are finally ready to use it. We can run x11vnc using this + server cert+key by either this command: + x11vnc -ssldir ~/CA_Intermediate -ssl SAVE-test_chain ... + + or this command: + x11vnc -ssl ~/CA_Intermediate/server-test_chain.pem ... + + since they are equivalent (both load the same pem file.) + + Finally we connect via VNC viewer that uses CA_Root to verify the + server. As before we use ss_vncviewer: + ss_vncviewer -verify ~/CA_Root/CA/cacert.pem hostname:0 + + Client Certificates (see above) work in a similar manner. + + So although it is a little awkward with the extra steps (e.g. + appending the CA_Intermediate cert) it is possible. If you want to do + this entirely with openssl(1) you will have to learn the openssl + commands corresponding to -genCA and -genCert. You may be able to find + guides on the Internet to do this. Starting with x11vnc 0.9.10, you + can have it print out the wrapper scripts it uses via: [36]-sslScripts + (you will still need to fill in a few pieces of information; ask if it + is not clear from the source code.) + + _________________________________________________________________ + More info: - See also this [33]article for some some general info and examples + See also this [37]article for some some general info and examples using stunnel and openssl on Windows with VNC. Also - [34]http://www.stunnel.org/faq/certs.html + [38]http://www.stunnel.org/faq/certs.html is a very good source of + information on SSL certificate creation and management. References @@ -10895,32 +11142,36 @@ References 6. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssldir 7. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl 8. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 9. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 10. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA - 11. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert - 12. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslDelCert - 13. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslEncKey - 14. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCertInfo + 9. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA + 10. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert + 11. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslDelCert + 12. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslEncKey + 13. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCertInfo + 14. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssldir 15. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssldir 16. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssldir - 17. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssldir - 18. http://www.karlrunge.com/x11vnc/ss_vncviewer - 19. http://www.karlrunge.com/x11vnc/ssvnc.html - 20. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 21. http://www.karlrunge.com/x11vnc/ss_vncviewer - 22. http://www.karlrunge.com/x11vnc/ssvnc.html - 23. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 24. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers - 25. http://www.karlrunge.com/x11vnc/ssl-portal.html - 26. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 28. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 29. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 31. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 17. http://www.karlrunge.com/x11vnc/ss_vncviewer + 18. http://www.karlrunge.com/x11vnc/ssvnc.html + 19. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 20. http://www.karlrunge.com/x11vnc/ss_vncviewer + 21. http://www.karlrunge.com/x11vnc/ssvnc.html + 22. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 23. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers + 24. http://www.karlrunge.com/x11vnc/ssl-portal.html + 25. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 26. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 28. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 29. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 30. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 31. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCRL 32. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCertInfo - 33. http://www.securityfocus.com/infocus/1677 - 34. http://www.stunnel.org/faq/certs.html + 33. http://www.karlrunge.com/x11vnc/ss_vncviewer + 34. http://www.karlrunge.com/x11vnc/ssvnc.html + 35. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 36. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslScripts + 37. http://www.securityfocus.com/infocus/1677 + 38. http://www.stunnel.org/faq/certs.html ======================================================================= http://www.karlrunge.com/x11vnc/ssl-portal.html: @@ -11008,7 +11259,7 @@ http://www.karlrunge.com/x11vnc/ssl-portal.html: It is the last item that makes it tricky (otherwise the method described on this page will work). If you are interested in such a solution and are willing to run a separate helper program - (connect_switch) [5]look here. + (connect_switch) [5]look here. Also, see [6]this apache patch. _________________________________________________________________ Example: @@ -11025,7 +11276,7 @@ http://www.karlrunge.com/x11vnc/ssl-portal.html: In this example suppose the gateway machine running apache is named "www.gateway.east" (e.g. it may also provide normal web service). We also choose the Internet-facing port for this VNC service to be port - 563. One could choose any port, including the [6]default HTTP port 80. + 563. One could choose any port, including the [7]default HTTP port 80. Detail: We choose 563 because it is the rarely used SNEWS port that is often allowed by Web proxies for the CONNECT method. The idea is the @@ -11050,9 +11301,9 @@ http://www.karlrunge.com/x11vnc/ssl-portal.html: i.e. we force SSL VNC connections, port 5915, serve the Java VNC viewer applet, and require a VNC password (another option would be - [7]-unixpw). The above command could also be run out of [8]inetd(8). - It can also be used to [9]autodetect the user's display and Xauthority - data. + [8]-unixpw). The above command could also be run out of [9]inetd(8). + It can also be used to [10]autodetect the user's display and + Xauthority data. These sections are added to the httpd.conf apache configuration file @@ -11183,7 +11434,7 @@ hostname2 15 This will involve downloading a signed java viewer applet jar file that is able to interact with the internal proxy for the VNC - connection. See [10]this FAQ for more info on how this works. Note: + connection. See [11]this FAQ for more info on how this works. Note: sometimes with the Proxy case if you see 'Bad Gateway' error you will have to wait 10 or so seconds and then hit reload. This seems to be due to having to wait for a Connection Keepalive to terminate... @@ -11255,7 +11506,7 @@ blah,blah... of a outgoing proxy socket connection. Use it only if the Web browser is inside a separate Web proxying environment (i.e. large corporation) - The rewrites with parameter urlPrefix are described under [11]Tricks + The rewrites with parameter urlPrefix are described under [12]Tricks for Better Response. The "trust" ones (also described under Tricks) with trustAllVncCerts tell the Java VNC applet to skip a dialog asking about the VNC Certificate. They are a bit faster and more reliable @@ -11284,7 +11535,7 @@ blah,blah... are not encrypted via SSL, and so in principle could be tampered with by a really bad guy. The subsequent VNC connection, however, is encrypted through a single SSL connection (it makes a CONNECT straight - to x11vnc). [12]See below for how to have these initial downloads + to x11vnc). [13]See below for how to have these initial downloads encrypted as well (if the apache web server has SSL/mod_ssl, i.e. https, enabled and configured). @@ -11293,14 +11544,14 @@ blah,blah... certificate 'always'). This is because an applet it cannot open local files, etc. Sadly, the applet cannot even remember certificates in the same browser session because it is completely reinitialized for each - connection (see [13]below). + connection (see [14]below). _________________________________________________________________ Too Much? If these apache rules are a little too much for you, there is a little - bit [14]simpler scheme where you have to list each of the individual + bit [15]simpler scheme where you have to list each of the individual machines in the httpd.conf and ssl.conf files. It may be a little more typing to maintain, but perhaps being more straight forward (less RewriteRule's) is desirable. @@ -11310,19 +11561,19 @@ blah,blah... Problems: To see example x11vnc output for a successful https://host:5900/ - connection with the Java Applet see [15]This Page. + connection with the Java Applet see [16]This Page. _________________________________________________________________ Some Ideas for adding extra authentication, etc. for the paranoid: - * VNC passwords: [16]-rfbauth, [17]-passwdfile, or [18]-usepw. Even + * VNC passwords: [17]-rfbauth, [18]-passwdfile, or [19]-usepw. Even adding a simple company-wide VNC password helps block unwanted access. - * Unix passwords: [19]-unixpw - * SSL Client certificates: [20]-sslverify + * Unix passwords: [20]-unixpw + * SSL Client certificates: [21]-sslverify * Apache AuthUserFile directive: .htaccess, etc. * Filter connections based on IP address or hostname. - * Use Port-knocking on your firewall as described in: [21]Enhanced + * Use Port-knocking on your firewall as described in: [22]Enhanced TightVNC Viewer (ssvnc). * Add proxy password authentication (requires Viewer changes?) * Run a separate instance of Apache that provides this VNC service @@ -11337,7 +11588,7 @@ blah,blah... Using non-Java viewers with this scheme: - The [22]ss_vncviewer stunnel wrapper script for VNC viewers has the + The [23]ss_vncviewer stunnel wrapper script for VNC viewers has the -proxy option that can take advantage of this method. ss_vncviewer -proxy www.gateway.east:563 host1:15 @@ -11345,7 +11596,7 @@ blah,blah... separated by a comma. ss_vncviewer -proxy proxy1.foobar.com:8080,www.gateway.east:563 host1:15 - For the [23]Enhanced TightVNC Viewer (ssvnc) GUI (it uses ss_vncviewer + For the [24]Enhanced TightVNC Viewer (ssvnc) GUI (it uses ss_vncviewer on Unix) put 'host1:15' into the 'VNC Server' entry box, and here are possible Proxy/Gateway entries Proxy/Gateway: www.gateway.east:563 @@ -11359,10 +11610,10 @@ blah,blah... To have the Java applet downloaded to the user's Web Browser via an encrypted (and evidently safer) SSL connection the Apache webserver - should be configured for SSL via [24]mod_ssl. + should be configured for SSL via [25]mod_ssl. - It is actually possible to use the x11vnc [25]Key Management utility - "[26]-sslGenCert" to generate your Apache/SSL .crt and .key files. (In + It is actually possible to use the x11vnc [26]Key Management utility + "[27]-sslGenCert" to generate your Apache/SSL .crt and .key files. (In brief, run something like "x11vnc -sslGenCert server self:apache" then copy the resulting self:apache.crt file to conf/ssl.crt/server.crt and extract the private key part from self:apache.pem and paste it into @@ -11370,7 +11621,7 @@ blah,blah... before running x11vnc will bump up the expiration date (3 years in this case). - Or you can use the standard methods described in the [27]Apache + Or you can use the standard methods described in the [28]Apache mod_ssl documentation to create your keys. Then restart Apache, usually something like "apachectl stop" followed by "apachectl startssl" @@ -11487,7 +11738,7 @@ stAllVncCerts=yes [R,NE,L] The "vncs/trust" ones are like the "trust" ones described earlier https://www.gateway.east/vncs/trust/mach2 - and similarly for the httpsPort ones. See [28]Tricks for Better + and similarly for the httpsPort ones. See [29]Tricks for Better Response. In all of the above cases the VNC traffic from Viewer to x11vnc is @@ -11509,7 +11760,7 @@ stAllVncCerts=yes [R,NE,L] The special entries "/vnc443" are only used for the special helper program (connect_switch) for the https port 443 only mode - [29]discussed here. + [30]discussed here. _________________________________________________________________ @@ -11548,16 +11799,16 @@ stAllVncCerts=yes [R,NE,L] -ssl SAVE -http -unixpw -localhost -users unixpw= \ -find - (we have used the alias [30]-find for "-display + (we have used the alias [31]-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 + The variant "[32]-display WAIT:cmd=FINDCREATEDISPLAY" (aliased by + "[33]-create") will actually create a (virtual or real) X server + session for the user if one doesn't already exist. See [34]here for details. To enable inetd operation for the non-HTTPS Java viewer download (port @@ -11569,8 +11820,8 @@ stAllVncCerts=yes [R,NE,L] -http_ssl -display WAIT:cmd=HTTPONCE where the long inetd.conf line has been split. Note how the - [34]-http_ssl tries to automatically find the .../classes/ssl - subdirectory. This requires the [35]-prog option available in x11vnc + [35]-http_ssl tries to automatically find the .../classes/ssl + subdirectory. This requires the [36]-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). @@ -11629,7 +11880,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 [36]connect_switch + special purpose application to add security. See [37]connect_switch which is somewhat related. - One might imagine the ProxyPass could be done for the VNC traffic as @@ -11737,37 +11988,38 @@ References 3. http://www.karlrunge.com/x11vnc/ssl-portal.html#no-apache 4. http://www.karlrunge.com/x11vnc/ssl-portal.html#precautions 5. http://www.karlrunge.com/x11vnc/ssl-single-443.html - 6. http://www.karlrunge.com/x11vnc/ssl-portal.html#port-variations - 7. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 8. http://www.karlrunge.com/x11vnc/ssl-portal.html#inetd - 9. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin - 10. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy - 11. http://www.karlrunge.com/x11vnc/ssl-portal.html#tricks - 12. http://www.karlrunge.com/x11vnc/ssl-portal.html#https-applet - 13. http://www.karlrunge.com/x11vnc/ssl-portal.html#https-applet" - 14. http://www.karlrunge.com/x11vnc/ssl-portal-orig.html - 15. http://www.karlrunge.com/x11vnc/ssl-output.html - 16. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 17. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 18. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw - 19. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 20. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 21. http://www.karlrunge.com/x11vnc/ssvnc.html - 22. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer - 23. http://www.karlrunge.com/x11vnc/ssvnc.html - 24. http://httpd.apache.org/docs/2.0/mod/mod_ssl.html - 25. http://www.karlrunge.com/x11vnc/ssl.html - 26. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert - 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-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 + 6. https://issues.apache.org/bugzilla/show_bug.cgi?id=29744 + 7. http://www.karlrunge.com/x11vnc/ssl-portal.html#port-variations + 8. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 9. http://www.karlrunge.com/x11vnc/ssl-portal.html#inetd + 10. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 11. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-java-viewer-proxy + 12. http://www.karlrunge.com/x11vnc/ssl-portal.html#tricks + 13. http://www.karlrunge.com/x11vnc/ssl-portal.html#https-applet + 14. http://www.karlrunge.com/x11vnc/ssl-portal.html#https-applet" + 15. http://www.karlrunge.com/x11vnc/ssl-portal-orig.html + 16. http://www.karlrunge.com/x11vnc/ssl-output.html + 17. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 18. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 19. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw + 20. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 21. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 22. http://www.karlrunge.com/x11vnc/ssvnc.html + 23. http://www.karlrunge.com/x11vnc/faq.html#ss_vncviewer + 24. http://www.karlrunge.com/x11vnc/ssvnc.html + 25. http://httpd.apache.org/docs/2.0/mod/mod_ssl.html + 26. http://www.karlrunge.com/x11vnc/ssl.html + 27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert + 28. http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#selfcert + 29. http://www.karlrunge.com/x11vnc/ssl-portal.html#tricks + 30. http://www.karlrunge.com/x11vnc/ssl-single-443.html + 31. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 32. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 33. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 34. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 35. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_ssl + 36. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-prog + 37. http://www.karlrunge.com/x11vnc/ssl-single-443.html ======================================================================= http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html: @@ -12954,7 +13206,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: 2010-01-07 +x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2010-02-21 x11vnc options: -display disp -auth file -N @@ -12984,71 +13236,71 @@ x11vnc options: -unixpw_system_greeter -redirect port -display WAIT:... -vencrypt mode -anontls mode -sslonly -dhparams file -nossl -ssl [pem] - -ssltimeout n -sslnofail -ssldir [dir] - -sslverify [path] -sslCRL path -sslGenCA [dir] - -sslGenCert type name -sslEncKey [pem] -sslCertInfo [pem] - -sslDelCert [pem] -stunnel [pem] -stunnel3 [pem] - -enc cipher:keyfile -https [port] -httpsredir [port] - -http_oneport -ssh user@host:disp -usepw - -storepasswd pass file -nopw -accept string - -afteraccept string -gone string -users list - -noshm -flipbyteorder -onetile - -solid [color] -blackout string -xinerama - -noxinerama -xtrap -xrandr [mode] - -rotate string -padgeom WxH -o logfile - -flag file -rmflag file -rc filename - -norc -env VAR=VALUE -prog /path/to/x11vnc - -h, -help -?, -opts -V, -version - -license -dbg -q, -quiet - -v, -verbose -bg -modtweak - -nomodtweak -xkb -noxkb - -capslock -skip_lockkeys -noskip_lockkeys - -skip_keycodes string -sloppy_keys -skip_dups - -noskip_dups -add_keysyms -noadd_keysyms - -clear_mods -clear_keys -clear_all - -remap string -norepeat -repeat - -nofb -nobell -nosel - -noprimary -nosetprimary -noclipboard - -nosetclipboard -seldir string -cursor [mode] - -nocursor -cursor_drag -arrow n - -noxfixes -alphacut n -alphafrac fraction - -alpharemove -noalphablend -nocursorshape - -cursorpos -nocursorpos -xwarppointer - -noxwarppointer -buttonmap string -nodragging - -ncache n -ncache_cr -ncache_no_moveraise - -ncache_no_dtchange -ncache_no_rootpixmap -ncache_keep_anims - -ncache_old_wm -ncache_pad n -debug_ncache - -wireframe [str] -nowireframe -nowireframelocal - -wirecopyrect mode -nowirecopyrect -debug_wireframe - -scrollcopyrect mode -noscrollcopyrect -scr_area n - -scr_skip list -scr_inc list -scr_keys list - -scr_term list -scr_keyrepeat lo-hi -scr_parms string - -fixscreen string -debug_scroll -noxrecord - -grab_buster -nograb_buster -debug_grabs - -debug_sel -pointer_mode n -input_skip n - -allinput -speeds rd,bw,lat -wmdt string - -debug_pointer -debug_keyboard -defer time - -wait time -extra_fbur n -wait_ui factor - -setdefer n -nowait_bog -slow_fb time - -xrefresh time -nap -nonap - -sb time -readtimeout n -ping n - -nofbpm -fbpm -nodpms - -dpms -forcedpms -clientdpms - -noserverdpms -noultraext -chatwindow - -noxdamage -xd_area A -xd_mem f - -sigpipe string -threads -nothreads - -fs f -gaps n -grow n - -fuzz n -debug_tiles -snapfb - -rawfb string -freqtab file -pipeinput cmd - -macnodim -macnosleep -macnosaver - -macnowait -macwheel n -macnoswap - -macnoresize -maciconanim n -macmenu - -macuskbd -gui [gui-opts] -remote command - -query variable -QD variable -sync - -query_retries str -remote_prefix str -noremote - -yesremote -unsafe -safer - -privremote -nocmds -allowedcmds list - -deny_all + -ssltimeout n -sslnofail -ssldir dir + -sslverify path -sslCRL path -sslGenCA [dir] + -sslGenCert type name -sslEncKey pem -sslCertInfo pem + -sslDelCert pem -sslScripts -stunnel [pem] + -stunnel3 [pem] -enc cipher:keyfile -https [port] + -httpsredir [port] -http_oneport -ssh user@host:disp + -usepw -storepasswd pass file -nopw + -accept string -afteraccept string -gone string + -users list -noshm -flipbyteorder + -onetile -solid [color] -blackout string + -xinerama -noxinerama -xtrap + -xrandr [mode] -rotate string -padgeom WxH + -o logfile -flag file -rmflag file + -rc filename -norc -env VAR=VALUE + -prog /path/to/x11vnc -h, -help -?, -opts + -V, -version -license -dbg + -q, -quiet -v, -verbose -bg + -modtweak -nomodtweak -xkb + -noxkb -capslock -skip_lockkeys + -noskip_lockkeys -skip_keycodes string -sloppy_keys + -skip_dups -noskip_dups -add_keysyms + -noadd_keysyms -clear_mods -clear_keys + -clear_all -remap string -norepeat + -repeat -nofb -nobell + -nosel -noprimary -nosetprimary + -noclipboard -nosetclipboard -seldir string + -cursor [mode] -nocursor -cursor_drag + -arrow n -noxfixes -alphacut n + -alphafrac fraction -alpharemove -noalphablend + -nocursorshape -cursorpos -nocursorpos + -xwarppointer -noxwarppointer -buttonmap string + -nodragging -ncache n -ncache_cr + -ncache_no_moveraise -ncache_no_dtchange -ncache_no_rootpixmap + -ncache_keep_anims -ncache_old_wm -ncache_pad n + -debug_ncache -wireframe [str] -nowireframe + -nowireframelocal -wirecopyrect mode -nowirecopyrect + -debug_wireframe -scrollcopyrect mode -noscrollcopyrect + -scr_area n -scr_skip list -scr_inc list + -scr_keys list -scr_term list -scr_keyrepeat lo-hi + -scr_parms string -fixscreen string -debug_scroll + -noxrecord -grab_buster -nograb_buster + -debug_grabs -debug_sel -pointer_mode n + -input_skip n -allinput -speeds rd,bw,lat + -wmdt string -debug_pointer -debug_keyboard + -defer time -wait time -extra_fbur n + -wait_ui factor -setdefer n -nowait_bog + -slow_fb time -xrefresh time -nap + -nonap -sb time -readtimeout n + -ping n -nofbpm -fbpm + -nodpms -dpms -forcedpms + -clientdpms -noserverdpms -noultraext + -chatwindow -noxdamage -xd_area A + -xd_mem f -sigpipe string -threads + -nothreads -fs f -gaps n + -grow n -fuzz n -debug_tiles + -snapfb -rawfb string -freqtab file + -pipeinput cmd -macnodim -macnosleep + -macnosaver -macnowait -macwheel n + -macnoswap -macnoresize -maciconanim n + -macmenu -macuskbd -gui [gui-opts] + -remote command -query variable -QD variable + -sync -query_retries str -remote_prefix str + -noremote -yesremote -unsafe + -safer -privremote -nocmds + -allowedcmds list -deny_all libvncserver options: -rfbport port TCP port for RFB protocol @@ -13082,7 +13334,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2010-01-07 +x11vnc: allow VNC connections to real X11 displays. 0.9.10 lastmod: 2010-02-21 (type "x11vnc -opts" to just list the options.) @@ -14769,14 +15021,14 @@ Options: ssh) and you do not want x11vnc waiting around for more connections, tying up ports, etc. --ssldir [dir] Use [dir] as an alternate ssl certificate and key +-ssldir dir Use "dir" as an alternate ssl certificate and key management toplevel directory. The default is ~/.vnc/certs This directory is used to store server and other certificates and keys and also other materials. E.g. in the simplest case, "-ssl SAVE" will store the x11vnc - server cert in [dir]/server.pem + server cert in dir/server.pem Use of alternate directories via -ssldir allows you to manage multiple VNC Certificate Authority (CA) keys. @@ -14788,14 +15040,14 @@ Options: -ssldir affects nearly all of the other -ssl* options, e.g. -ssl SAVE, -sslGenCert, etc.. --sslverify [path] For either of the -ssl or -stunnel modes, use [path] +-sslverify path For either of the -ssl or -stunnel modes, use "path" to provide certificates to authenticate incoming VNC *Client* connections (normally only the server is authenticated in SSL.) This can be used as a method to replace standard password authentication of clients. - If [path] is a directory it contains the client (or CA) - certificates in separate files. If [path] is a file, + If "path" is a directory it contains the client (or CA) + certificates in separate files. If path is a file, it contains one or more certificates. See special tokens below. These correspond to the "CApath = dir" and "CAfile = file" stunnel options. See the stunnel(8) @@ -14805,7 +15057,7 @@ Options: x11vnc -ssl -sslverify ~/my.crt x11vnc -ssl -sslverify ~/my_pem_dir/ - Note that if [path] is a directory, it must contain + Note that if path is a directory, it must contain the certs in separate files named like <HASH>.0, where the value of <HASH> is found by running the command "openssl x509 -hash -noout -in file.crt". Evidently @@ -14817,7 +15069,7 @@ Options: subdirs it manages. Then you can point -sslverify to the HASH subdir. - Special tokens: in -ssl mode, if [path] is not a file or + Special tokens: in -ssl mode, if "path" is not a file or a directory, it is taken as a comma separated list of tokens that are interpreted as follows: @@ -15105,7 +15357,7 @@ Options: REQ_ARGS='-days 1095' to bump up the expiration date (3 years in this case). --sslEncKey [pem] Utility to encrypt an existing PEM file with a +-sslEncKey pem Utility to encrypt an existing PEM file with a passphrase you supply when prompted. For that key to be used (e.g. by x11vnc) the passphrase must be supplied each time. @@ -15123,7 +15375,7 @@ Options: x11vnc -sslEncKey SAVE x11vnc -sslEncKey SAVE-charlie --sslCertInfo [pem] Prints out information about an existing PEM file. +-sslCertInfo pem Prints out information about an existing PEM file. In addition the public certificate is also printed. The openssl(1) program must be in PATH. Basically the command "openssl x509 -text" is run on the pem. @@ -15152,10 +15404,15 @@ Options: The LIST, LISTL, LL, ALL, HASHON, HASHOFF words can also be lowercase, e.g. "list". --sslDelCert [pem] Prompts you to delete all .crt .pem .key .req files +-sslDelCert pem Prompts you to delete all .crt .pem .key .req files associated with [pem]. "SAVE" and lookups as in -sslCertInfo apply as well. +-sslScripts Prints out both the 'genCA' and 'genCert' x11vnc + openssl wrapper scripts for you to examine, modify, etc. + The scripts are printed to stdout and then the program + exits. + -stunnel [pem] Use the stunnel(8) (www.stunnel.org) to provide an encrypted SSL tunnel between viewers and x11vnc. |