diff options
| author | runge <runge@karlrunge.com> | 2009-05-21 10:57:03 -0400 |
|---|---|---|
| committer | runge <runge@karlrunge.com> | 2009-05-21 10:57:03 -0400 |
| commit | 94d058b35f075cec2d6e8b6e37ee1a94086ea3f8 (patch) | |
| tree | 6cec0620ab70b5db6b33645dbcac1071f3c7a556 /x11vnc/README | |
| parent | 804335f9d296440bb708ca844f5d89b58b50b0c6 (diff) | |
| download | libvncserver-94d058b35f075cec2d6e8b6e37ee1a94086ea3f8.zip libvncserver-94d058b35f075cec2d6e8b6e37ee1a94086ea3f8.tar.gz | |
Thread safety. Fix -clip -in -rawfb. Try to avoid Xorg stuck
key bug.
Diffstat (limited to 'x11vnc/README')
| -rw-r--r-- | x11vnc/README | 1913 |
1 files changed, 1008 insertions, 905 deletions
diff --git a/x11vnc/README b/x11vnc/README index 216af03..651ea1f 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -2,7 +2,7 @@ Copyright (C) 2002-2009 Karl J. Runge <runge@karlrunge.com> All rights reserved. -x11vnc README file Date: Tue Mar 31 23:24:00 EDT 2009 +x11vnc README file Date: Thu May 21 10:41:49 EDT 2009 The following information is taken from these URLs: @@ -901,7 +901,22 @@ make Here are some features that will appear in the 0.9.8 release: - * Coming Soon! + * Stability improvements to [122]-threads mode. Running x11vnc this + way is more reliable now. Threaded operation sometimes gives + better interactive response and faster updates: try it out. The + threaded mode now supports multiple VNC viewers using the same VNC + encoding. The threaded mode can also yield a performance + enhancement in the many client case (e.g. class-room broadcast.) + We have tested with 30 to 50 simultaneous clients. See also + [123]-reflect. + For simultaneous clients: the ZRLE encoding is thread safe on all + platforms, and the Tight and Zlib encodings are currently only + thread safe on Linux where thread local storage, __thread, is + used. If your non-Linux system and compiler support __thread one + can supply -DTLS=__thread to enable it. When there is only one + connected client, all encodings are safe on all platforms. Note + that some features (e.g. scroll detection and -ncache) may be + disabled or run with reduced functionality in -threads mode. Here are some features that appeared in the 0.9.7 release: @@ -911,38 +926,38 @@ make case the special file /dev/vcsa2 is used to retrieve vt2's current text. Text and colors are shown, but no graphics. * Support for less than 8 bits per pixel framebuffers (e.g. 4 or 1 - bpp) in the [122]-rawfb mode. + bpp) in the [124]-rawfb mode. * The SSL enabled UltraVNC Java viewer applet now has a [Home] entry in the "drives" drop down menu. This menu can be configured with the ftpDropDown applet parameter. All of the applet parameters are documented in classes/ssl/README. - * Experimental support for [123]VirtualGL's [124]TurboVNC (an + * Experimental support for [125]VirtualGL's [126]TurboVNC (an enhanced TightVNC for fast LAN high framerate usage.) * The CUPS Terminal Services helper mode has been improved. - * Improvements to the [125]-ncache_cr that allows smooth opaque + * Improvements to the [127]-ncache_cr that allows smooth opaque window motions using the 'copyrect' encoding when using - [126]-ncache mode. - * The [127]-rmflag option enables a way to indicate to other + [128]-ncache mode. + * The [129]-rmflag option enables a way to indicate to other processes x11vnc has exited. * Reverse connections using anonymous Diffie Hellman SSL encryption now work. Here are some features that appeared in the 0.9.6 release: - * Support for [128]VeNCrypt SSL/TLS encrypted connections. It is - enabled by default in the [129]-ssl mode. VNC Viewers like + * Support for [130]VeNCrypt SSL/TLS encrypted connections. It is + enabled by default in the [131]-ssl mode. VNC Viewers like vinagre, gvncviewer/gtk-vnc, the vencrypt package, and others support this encryption mode. It can also be used with the - [130]-unixpw option to enable Unix username and password + [132]-unixpw option to enable Unix username and password authentication (VeNCrypt's "*Plain" modes.) A similar but older VNC security type "ANONTLS" (used by vino) is supported as well. - See the [131]-vencrypt and [132]-anontls options for additional + See the [133]-vencrypt and [134]-anontls options for additional control. The difference between x11vnc's normal -ssl mode and VeNCrypt is that the former wraps the entire VNC connection in SSL (like HTTPS does for HTTP, i.e. "vncs://") while VeNCrypt switches on the SSL/TLS at a certain point during the VNC handshake. Use - [133]-sslonly to disable both VeNCrypt and ANONTLS (vino). - * The "[134]-ssl ANON" option enables Anonymous Diffie-Hellman (ADH) + [135]-sslonly to disable both VeNCrypt and ANONTLS (vino). + * The "[136]-ssl ANON" option enables Anonymous Diffie-Hellman (ADH) key exchange for x11vnc's normal SSL/TLS operation. Note that Anonymous Diffie-Hellman uses encryption for privacy, but provides no authentication and so is susceptible to Man-In-The-Middle @@ -950,17 +965,17 @@ make SAVE", etc. and have the VNC viewer verify the cert.) The ANONTLS mode (vino) only supports ADH. VeNCrypt mode supports both ADH and regular X509 SSL certificates modes. For these ADH is enabled by - default. See [135]-vencrypt and [136]-anontls for how to disable + default. See [137]-vencrypt and [138]-anontls for how to disable ADH. * For x11vnc's SSL/TLS modes, one can now specify a Certificate - Revocation List (CRL) with the [137]-sslCRL option. This will only + Revocation List (CRL) with the [139]-sslCRL option. This will only be useful for wide deployments: say a company-wide x11vnc SSL access deployment using a central Certificate Authority (CA) via - [138]-sslGenCA and [139]-sslGenCert. This way if a user has his + [140]-sslGenCA and [141]-sslGenCert. This way if a user has his laptop lost or stolen, you only have to revoke his key instead of creating a new Certificate Authority and redeploying new keys to all users. - * The default SSL/TLS mode, "[140]-ssl" (no pem file parameter + * The default SSL/TLS mode, "[142]-ssl" (no pem file parameter supplied), is now the same as "-ssl SAVE" and will save the generated self-signed cert in "~/.vnc/certs/server.pem". Previously "-ssl" would create a temporary self-signed cert that @@ -970,45 +985,45 @@ make same x11vnc server. Use "-ssl TMP" to regain the previous behavior. Use "-ssl SAVE_NOPROMPT" to avoid being prompted about using passphrase when the certificate is created. - * The option [141]-http_oneport enables single-port HTTP connections + * The option [143]-http_oneport enables single-port HTTP connections via the Java VNC Viewer. So, for example, the web browser URL "http://myhost.org:5900" works the same as "http://myhost.org:5800", but with the convenience of only involving one port instead of two. This works for both unencrypted - connections and for SSH tunnels (see [142]-httpsredir if the + connections and for SSH tunnels (see [144]-httpsredir if the tunnel port differs). Note that HTTPS single-port operation in - [143]-ssl SSL encrypted mode has been available since x11vnc + [145]-ssl SSL encrypted mode has been available since x11vnc version 0.8.3. - * For the [144]-avahi/[145]-zeroconf Service Advertizing mode, if + * For the [146]-avahi/[147]-zeroconf Service Advertizing mode, if x11vnc was not compiled with the avahi-client library, then an external helper program, either avahi-publish(1) (on Unix) or dns-sd(1) (on Mac OS X), is used instead. - * The "[146]-rfbport PROMPT" option will prompt the user via the GUI + * The "[148]-rfbport PROMPT" option will prompt the user via the GUI to select the VNC port (e.g. 5901) to listen on, and a few other basic settings. This enables a handy GUI mode for naive users: x11vnc -gui tray=setpass -rfbport PROMPT -logfile $HOME/.x11vnc.log.%VNCDISP LAY suitable for putting in a launcher or menu, e.g. - [147]x11vnc.desktop. The [148]-logfile expansion is new too. In + [149]x11vnc.desktop. The [150]-logfile expansion is new too. In the GUI, the tray=setpass Properties panel has been improved. - * The [149]-solid solid background color option now works for the + * The [151]-solid solid background color option now works for the Mac OS X console. - * The [150]-reopen option instructs x11vnc to try to reopen the X + * The [152]-reopen option instructs x11vnc to try to reopen the X display if it is prematurely closed by, say, the display manager - (e.g. [151]GDM). + (e.g. [153]GDM). Here are some features that appeared in the 0.9.5 release: - * Symmetric key [152]encryption ciphers. ARC4, AES-128, AES-256, + * Symmetric key [154]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 - SSH encryption access methods. [153]SSVNC also supports these + SSH encryption access methods. [155]SSVNC also supports these encryption modes. * Scaling differently along the X- and Y-directions. E.g. - "[154]-scale 1280x1024" or "-scale 0.8x0.75" Also, - "[155]-geometry WxH" is an alias for "-scale WxH" + "[156]-scale 1280x1024" or "-scale 0.8x0.75" Also, + "[157]-geometry WxH" is an alias for "-scale WxH" * By having SSVNC version 1.0.21 or later available in your $PATH, - the [156]-chatwindow option allows a UltraVNC Text Chat window to + the [158]-chatwindow option allows a UltraVNC Text Chat window to appear on the local X11 console/display (this way the remote viewer can chat with the person at the physical display; e.g. helpdesk mode). This also works on the Mac OS X console if the @@ -1020,46 +1035,46 @@ LAY Here are some features that appeared in the 0.9.4 release: - * Improvements to the [157]-find and [158]-create X session finding + * Improvements to the [159]-find and [160]-create X session finding or creating modes: new desktop types and service redirection options. Personal cupsd daemon and SSH port redirection helper for - use with [159]SSVNC's Terminal Services feature. - * Reverse VNC connections via [160]-connect work in the [161]-find, - [162]-create and related [163]-display WAIT:... modes. + use with [161]SSVNC's Terminal Services feature. + * Reverse VNC connections via [162]-connect work in the [163]-find, + [164]-create and related [165]-display WAIT:... modes. * Reverse VNC connections (either normal or SSL) can use a Web Proxy or a SOCKS proxy, or a SSH connection, or even a CGI URL to make - the outgoing connection. See: [164]-proxy. Forward connections can - also use: [165]-ssh. - * Reverse VNC connections via the [166]UltraVNC repeater proxy + the outgoing connection. See: [166]-proxy. Forward connections can + also use: [167]-ssh. + * Reverse VNC connections via the [168]UltraVNC repeater proxy (either normal or SSL) are supported. Use either the - "[167]-connect repeater=ID:NNNN+host:port" or "[168]-connect - repeater://host:port+ID:NNNN" notation. The [169]SSVNC VNC viewer + "[169]-connect repeater=ID:NNNN+host:port" or "[170]-connect + repeater://host:port+ID:NNNN" notation. The [171]SSVNC VNC viewer also supports the UltraVNC repeater. * Support for indexed colormaps (PseudoColor) with depths other than 8 (from 1 to 16 now work) for non-standard hardware. Option - "[170]-advertise_truecolor" to handle some workaround in this + "[172]-advertise_truecolor" to handle some workaround in this mode. * Support for the ZYWRLE encoding, this is the RealVNC ZRLE encoding extended to do motion video and photo regions more efficiently by way of a Wavelet based transformation. - * The [171]-finddpy and [172]-listdpy utilities help to debug and - configure the [173]-find, [174]-create, and [175]-display WAIT:... + * The [173]-finddpy and [174]-listdpy utilities help to debug and + configure the [175]-find, [176]-create, and [177]-display WAIT:... modes. * Some automatic detection of screen resizes are handled even if the - [176]-xrandr option is not supplied. - * The [177]-autoport options gives more control over the VNC port + [178]-xrandr option is not supplied. + * The [179]-autoport options gives more control over the VNC port x11vnc chooses. - * The [178]-ping secs can be used to help keep idle connections + * The [180]-ping secs can be used to help keep idle connections alive. * Pasting of the selection/clipboard into remote applications (e.g. Java) has been improved. * Fixed a bug if a client disconnects during the 'speed-estimation' phase. * To unset Caps_Lock, Num_Lock and raise all keys in the X server - use [179]-clear_all. + use [181]-clear_all. * Usage with dvorak keyboards has been improved. See also: - [180]-xkb. - * The [181]Java Viewer applet source code is now included in the + [182]-xkb. + * The [183]Java Viewer applet source code is now included in the x11vnc-0.9.*.tar.gz tarball. This means you can now build the Java viewer applet jar files from source. If you stopped shipping the Java viewer applet jar files due to lack of source code, you can @@ -1067,7 +1082,7 @@ LAY Here are some features that appeared in the 0.9.3 release: - * [182]Viewer-side pixmap caching. A large area of pixels (at least + * [184]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 as a buffer/cache area for pixel data. The VNC CopyRect encoding @@ -1075,7 +1090,7 @@ LAY Until we start modifying viewers you will be able to see the cache area if you scroll down (this makes it easier to debug!). For testing the default is "-ncache 10". The unix Enhanced TightVNC - Viewer [183]ssvnc has a nice [184]-ycrop option to help hide the + Viewer [185]ssvnc has a nice [186]-ycrop option to help hide the pixel cache area from view. @@ -1088,14 +1103,14 @@ LAY * If UltraVNC file transfer or chat is detected, then VNC clients are "pinged" more often to prevent these side channels from becoming serviced too infrequently. - * In [185]-unixpw mode in the username and password dialog no text + * In [187]-unixpw mode in the username and password dialog no text will be echoed if the first character sent is "Escape". This enables a convenience feature in SSVNC to send the username and password automatically. Here are some features that appeared in the 0.9.1 release: - * The [186]UltraVNC Java viewer has been enhanced to support SSL (as + * The [188]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 on Unix that supports ultravnc filetransfer. It is in the @@ -1106,12 +1121,12 @@ LAY Some other bugs in the UltraVNC Java viewer were fixed and a few improvements to the UI made. * A new Unix username login mode for VNC Viewers authenticated via a - Client SSL Certificate: "[187]-users sslpeer=". The emailAddress + Client SSL Certificate: "[189]-users sslpeer=". The emailAddress subject field is inspected for username@hostname and then acts as though "-users +username" has been supplied. This way the Unix username is identified by (i.e. simply extracted from) the Client - SSL Certificate. This could be useful with [188]-find, - [189]-create and [190]-svc modes if you are also have set up and + SSL Certificate. This could be useful with [190]-find, + [191]-create and [192]-svc modes if you are also have set up and use VNC Client SSL Certificate authentication. * For external display finding/creating programs (e.g. WAIT:cmd=...) if the VNC Viewer is authenticated via a Client SSL Certificate, @@ -1120,41 +1135,41 @@ LAY Here are some features that appeared in the 0.9 release: - * [191]VNC Service advertising via mDNS / ZeroConf / BonJour with - the [192]Avahi client library. Enable via "[193]-avahi" or - "[194]-zeroconf". + * [193]VNC Service advertising via mDNS / ZeroConf / BonJour with + the [194]Avahi client library. Enable via "[195]-avahi" or + "[196]-zeroconf". * Implementations of UltraVNC's TextChat, SingleWindow, and - ServerInput extensions (requires ultravnc viewer or [195]ssvnc + ServerInput extensions (requires ultravnc viewer or [197]ssvnc Unix viewer). They toggle the selection of a single window - ([196]-id), and disable (friendly) user input and viewing (monitor + ([198]-id), and disable (friendly) user input and viewing (monitor blank) at the VNC server. - * Short aliases "[197]-find", "[198]-create", "[199]-svc", and - "[200]-xdmsvc" for commonly used FINDCREATEDISPLAY usage modes. + * Short aliases "[199]-find", "[200]-create", "[201]-svc", and + "[202]-xdmsvc" for commonly used FINDCREATEDISPLAY usage modes. * Reverse VNC connections (viewer listening) now work in SSL - ([201]-ssl) mode. + ([203]-ssl) mode. * New options to control the Monitor power state and keyboard/mouse - grabbing: [202]-forcedpms, [203]-clientdpms, [204]-noserverdpms, - and [205]-grabalways. + grabbing: [204]-forcedpms, [205]-clientdpms, [206]-noserverdpms, + and [207]-grabalways. * A simple way to emulate inetd(8) to some degree via the - "[206]-loopbg" option. - * Monitor the accuracy of XDAMAGE and apply "[207]-noxdamage" if it - is not working well. OpenGL applications like like [208]beryl and + "[208]-loopbg" option. + * Monitor the accuracy of XDAMAGE and apply "[209]-noxdamage" if it + is not working well. OpenGL applications like like [210]beryl and MythTv have been shown to make XDAMAGE not work properly. * For Java SSL connections involving a router/firewall port - redirection, an option [209]-httpsredir to spare the user from + redirection, an option [211]-httpsredir to spare the user from needing to include &PORT=NNN in the browser URL. Here are some features that appeared in the 0.8.4 release: - * Native [210]Mac OS X Aqua/Quartz support. (i.e. OSXvnc + * Native [212]Mac OS X Aqua/Quartz support. (i.e. OSXvnc alternative; some activities are faster) - * A [211]new login mode: "-display WAIT:cmd=FINDCREATEDISPLAY + * A [213]new login mode: "-display WAIT:cmd=FINDCREATEDISPLAY -unixpw ..." that will Create a new X session (either virtual or real and with or without a display manager, e.g. kdm) for the user if it cannot find the user's X session display via the FINDDISPLAY - method. See the [212]-svc and the [213]-xdmsvc aliases. - * x11vnc can act as a VNC [214]reflector/repeater using the - "[215]-reflect host:N" option. Instead of polling an X display, + method. See the [214]-svc and the [215]-xdmsvc aliases. + * x11vnc can act as a VNC [216]reflector/repeater using the + "[217]-reflect host:N" option. Instead of polling an X display, the remote VNC Server host:N is connected to and re-exported via VNC. This is intended for use in broadcasting a display to many (e.g. > 16; classroom or large demo) VNC viewers where bandwidth @@ -1162,16 +1177,16 @@ LAY number of repeaters. * Wireframe copyrect detection for local user activity (e.g. someone sitting at the physical display moving windows) Use - [216]-nowireframelocal to disable. - * The "[217]-N" option couples the VNC Display number to the X + [218]-nowireframelocal to disable. + * The "[219]-N" option couples the VNC Display number to the X Display number. E.g. if your X DISPLAY is :2 then the VNC display will be :2 (i.e. using port 5902). If that port is taken x11vnc will exit. - * Option [218]-nodpms to avoid problems with programs like KDE's + * Option [220]-nodpms to avoid problems with programs like KDE's kdesktop_lock that keep restarting the screen saver every few seconds. * To automatically fix the common mouse motion problem on XINERAMA - (multi-headed) displays, the [219]-xwarppointer option is enabled + (multi-headed) displays, the [221]-xwarppointer option is enabled by default when XINERAMA is active. If you have a Mac please try out the native Mac OS X support, build @@ -1181,62 +1196,62 @@ LAY Here are some features that appeared in the 0.8.3 release: - * The [220]-ssl option provides SSL encryption and authentication - natively via the [221]www.openssl.org library. One can use from a + * The [222]-ssl option provides SSL encryption and authentication + natively via the [223]www.openssl.org library. One can use from a simple self-signed certificate server certificate up to full CA and client certificate authentication schemes. - * Similar to -ssl, the [222]-stunnel option starts up a SSL tunnel + * Similar to -ssl, the [224]-stunnel option starts up a SSL tunnel server stunnel (that must be installed separately on the system: - [223]www.stunnel.org [224]stunnel.mirt.net ) to allow only + [225]www.stunnel.org [226]stunnel.mirt.net ) to allow only encrypted SSL connections from the network. - * The [225]-sslverify option allows for authenticating VNC clients + * The [227]-sslverify option allows for authenticating VNC clients via their certificates in either -ssl or -stunnel modes. * Certificate creation and management tools are provide in the - [226]-sslGenCert, [227]-sslGenCA, and [228]related options. + [228]-sslGenCert, [229]-sslGenCA, and [230]related options. * An SSL enabled Java applet VNC Viewer applet is provided by x11vnc in classes/ssl/VncViewer.jar. In addition to normal HTTP, the applet may be loaded into the web browser via HTTPS (HTTP over SSL). (one can use the VNC port, e.g. https://host:5900/, or also - the separate [229]-https port option). A wrapper shell script - [230]ss_vncviewer is also provided that sets up a stunnel - client-side tunnel on Unix systems. See [231]Enhanced TightVNC + the separate [231]-https port option). A wrapper shell script + [232]ss_vncviewer is also provided that sets up a stunnel + client-side tunnel on Unix systems. See [233]Enhanced TightVNC Viewer (SSVNC) for other SSL/SSH viewer possibilities. - * The [232]-unixpw option supports Unix username and password - authentication (a simpler variant is the [233]-unixpw_nis option + * The [234]-unixpw option supports Unix username and password + authentication (a simpler variant is the [235]-unixpw_nis option that works in environments where the encrypted passwords are - readable, e.g. NIS). The [234]-ssl or [235]-localhost + - [236]-stunnel options are enforced in this mode to prevent + readable, e.g. NIS). The [236]-ssl or [237]-localhost + + [238]-stunnel options are enforced in this mode to prevent password sniffing. As a convenience, these requirements are lifted if a SSH tunnel can be deduced (but -localhost still applies). - * Coupling [237]-unixpw with "[238]-display WAIT:cmd=FINDDISPLAY" or + * Coupling [239]-unixpw with "[240]-display WAIT:cmd=FINDDISPLAY" or "-display WAIT:cmd=FINDCREATEDISPLAY" provides a way to allow a user to login with their UNIX password and have their display - connected to [239]automatically. See the [240]-svc and the - [241]-xdmsvc aliases. - * Hooks are provided in the [242]-unixpw_cmd and "[243]-passwdfile + connected to [241]automatically. See the [242]-svc and the + [243]-xdmsvc aliases. + * Hooks are provided in the [244]-unixpw_cmd and "[245]-passwdfile cmd:,custom:..." options to allow you to supply your own authentication and password lookup programs. * x11vnc can be configured and built to not depend on X11 libraries - "./configure --without-x" for [244]-rawfb only operation (e.g. + "./configure --without-x" for [246]-rawfb only operation (e.g. embedded linux console devices). - * The [245]-rotate option enables you to rotate or reflect the + * The [247]-rotate option enables you to rotate or reflect the screen before exporting via VNC. This is intended for use on handhelds and other devices where the rotation orientation is not "natural". - * The "[246]-ultrafilexfer" alias is provided and improved UltraVNC + * The "[248]-ultrafilexfer" alias is provided and improved UltraVNC filetransfer rates have been achieved. - * Under the "[247]-connect_or_exit host" option x11vnc will exit + * Under the "[249]-connect_or_exit host" option x11vnc will exit immediately unless the reverse connection to host succeeds. The "-rfbport 0" option disables TCP listening for connections (useful for this mode). - * The "[248]-rawfb rand" and "-rawfb none" options are useful for + * The "[250]-rawfb rand" and "-rawfb none" options are useful for testing automation scripts, etc., without requiring a full desktop. - * Reduced spewing of information at startup, use "[249]-verbose" + * Reduced spewing of information at startup, use "[251]-verbose" (also "-v") to turn it back on for debugging or if you are going to send me a problem report. - Here are some [250]Previous Release Notes + Here are some [252]Previous Release Notes _________________________________________________________________ Some Notes: @@ -1263,13 +1278,13 @@ LAY protocol.) I suggest using xsetroot, dtstyle or similar utility to set a solid background while using x11vnc. You can turn the pretty background image back on when you are using the display directly. - Update: As of Feb/2005 x11vnc has the [251]-solid [color] option that + Update: As of Feb/2005 x11vnc has the [253]-solid [color] option that works on recent GNOME, KDE, and CDE and also on classic X (background image is on the root window). Update: As of Oct/2007 x11vnc has the - [252]-ncache option that does a reasonable job caching the background + [254]-ncache option that does a reasonable job caching the background (and other) pixmap data on the viewer side. - I also find the [253]TightVNC encoding gives the best response for my + I also find the [255]TightVNC encoding gives the best response for my usage (Unix <-> Unix over cable modem). One needs a tightvnc-aware vncviewer to take advantage of this encoding. @@ -1281,17 +1296,17 @@ LAY is X11's default listening port). Had port 5900 been taken by some other application, x11vnc would have next tried 5901. That would mean the viewer command above should be changed to vncviewer - far-away.east:1. You can force the port with the "[254]-rfbport NNNN" + far-away.east:1. You can force the port with the "[256]-rfbport NNNN" option where NNNN is the desired port number. If that port is already - taken, x11vnc will exit immediately. The "[255]-N" option will try to + taken, x11vnc will exit immediately. The "[257]-N" option will try to match the VNC display number to the X display. (also see the "SunRay Gotcha" note below) Options: x11vnc has (far too) many features that may be activated - via its [256]command line options. Useful options are, e.g., -scale to + via its [258]command line options. Useful options are, e.g., -scale to do server-side scaling, and -rfbauth passwd-file to use VNC password protection (the vncpasswd or storepasswd programs, or the x11vnc - [257]-storepasswd option can be used to create the password file). + [259]-storepasswd option can be used to create the password file). Algorithm: How does x11vnc do it? Rather brute-forcedly: it continuously polls the X11 framebuffer for changes using @@ -1319,7 +1334,7 @@ LAY first testing out the programs. You get an interesting recursive/feedback effect where vncviewer images keep popping up each one contained in the previous one and slightly shifted a bit by the - window manager decorations. There will be an [258]even more + window manager decorations. There will be an [260]even more interesting effect if -scale is used. Also, if the XKEYBOARD is supported and the XBell "beeps" once, you get an infinite loop of beeps going off. Although all of this is mildly exciting it is not @@ -1329,8 +1344,8 @@ LAY Sun Ray Notes: - You can run x11vnc on your (connected or disconnected) [259]SunRay - session. Here are some [260]notes on SunRay usage with x11vnc. + You can run x11vnc on your (connected or disconnected) [261]SunRay + session. Here are some [262]notes on SunRay usage with x11vnc. _________________________________________________________________ @@ -1342,7 +1357,7 @@ LAY than you normally do to minimize the effects (e.g. do fullpage paging rather than line-by-line scrolling, and move windows in a single, quick motion). Recent work has provided the - [261]-scrollcopyrect and [262]-wireframe speedups using the + [263]-scrollcopyrect and [264]-wireframe speedups using the CopyRect VNC encoding and other things, but they only speed up some activities, not all. * A rate limiting factor for x11vnc performance is that graphics @@ -1401,18 +1416,18 @@ LAY but we mention it because it may be of use for special purpose applications. You may need to use the "-cc 4" option to force Xvfb to use a TrueColor visual instead of DirectColor. See also the - description of the [263]-create option that does all of this + description of the [265]-create option that does all of this automatically for you. Also, a faster and more accurate way is to use the "dummy" XFree86/Xorg device driver (or our Xdummy wrapper script). See - [264]this FAQ for details. + [266]this FAQ for details. * Somewhat surprisingly, the X11 mouse (cursor) shape is write-only and cannot be queried from the X server. So traditionally in x11vnc the cursor shape stays fixed at an arrow. (see the "-cursor - X" and "-cursor some" [265]options, however, for a partial hack + X" and "-cursor some" [267]options, however, for a partial hack for the root window, etc.). However, on Solaris using the SUN_OVL overlay extension, x11vnc can show the correct mouse cursor when - the [266]-overlay option is also supplied. A similar thing is done + the [268]-overlay option is also supplied. A similar thing is done on IRIX as well when -overlay is supplied. More generally, as of Dec/2004 x11vnc supports the new XFIXES extension (in Xorg and Solaris 10) to query the X server for the @@ -1420,18 +1435,18 @@ LAY with transparency (alpha channel) need to approximated to solid RGB values (some cursors look worse than others). * Audio from applications is of course not redirected (separate - redirectors do exist, e.g. esd, see [267]the FAQ on this below.) + redirectors do exist, e.g. esd, see [269]the FAQ on this below.) The XBell() "beeps" will work if the X server supports the XKEYBOARD extension. (Note that on Solaris XKEYBOARD is disabled by default. Passing +kb to Xsun enables it). - * The scroll detection algorithm for the [268]-scrollcopyrect option + * The scroll detection algorithm for the [270]-scrollcopyrect option can give choppy or bunched up transient output and occasionally painting errors. * Using -threads can expose some bugs/crashes in libvncserver. - Please feel free to [269]contact me if you have any questions, + Please feel free to [271]contact me if you have any questions, problems, or comments about x11vnc, etc. - Also, some people ask if they can make a donation, see [270]this link + Also, some people ask if they can make a donation, see [272]this link for that. References @@ -1557,155 +1572,157 @@ References 119. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext 120. http://www.karlrunge.com/x11vnc/ssvnc.html 121. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc - 122. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 123. http://www.virtualgl.org/ - 124. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc - 125. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr - 126. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 127. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rmflag - 128. http://sourceforge.net/projects/vencrypt/ - 129. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 130. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt - 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls - 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslonly - 134. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 135. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt - 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls - 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCRL - 138. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA - 139. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert - 140. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_oneport - 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 144. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi - 145. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf - 146. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 147. http://www.karlrunge.com/x11vnc/x11vnc.desktop - 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o - 149. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen - 151. http://www.karlrunge.com/x11vnc/faq.html#infaq_gdm - 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc - 153. http://www.karlrunge.com/x11vnc/ssvnc.html - 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-geometry - 156. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-chatwindow - 157. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 159. http://www.karlrunge.com/x11vnc/ssvnc.html - 160. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect - 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 163. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 165. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh - 166. http://www.uvnc.com/addons/repeater.html - 167. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect - 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 169. http://www.karlrunge.com/x11vnc/ssvnc.html - 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-advertise_truecolor - 171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-finddpy - 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listdpy - 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 175. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 176. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr - 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport - 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ping - 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 181. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers - 182. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching - 183. http://www.karlrunge.com/x11vnc/ssvnc.html - 184. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop - 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 186. http://www.ultravnc.com/ - 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 122. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 123. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 124. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 125. http://www.virtualgl.org/ + 126. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc + 127. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 128. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 129. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rmflag + 130. http://sourceforge.net/projects/vencrypt/ + 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt + 134. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls + 135. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslonly + 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 137. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vencrypt + 138. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-anontls + 139. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslCRL + 140. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA + 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert + 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http_oneport + 144. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 145. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 146. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi + 147. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf + 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 149. http://www.karlrunge.com/x11vnc/x11vnc.desktop + 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reopen + 153. http://www.karlrunge.com/x11vnc/faq.html#infaq_gdm + 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc + 155. http://www.karlrunge.com/x11vnc/ssvnc.html + 156. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 157. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-geometry + 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-chatwindow + 159. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 161. http://www.karlrunge.com/x11vnc/ssvnc.html + 162. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect + 163. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 165. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh + 168. http://www.uvnc.com/addons/repeater.html + 169. http://www.karlrunge.com/x11vnc/faq.html#faq-reverse-connect + 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 171. http://www.karlrunge.com/x11vnc/ssvnc.html + 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-advertise_truecolor + 173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-finddpy + 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listdpy + 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 177. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 178. http://www.karlrunge.com/x11vnc/faq.html#faq-xrandr + 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport + 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ping + 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 183. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-viewers + 184. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching + 185. http://www.karlrunge.com/x11vnc/ssvnc.html + 186. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 188. http://www.ultravnc.com/ + 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 191. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi - 192. http://www.avahi.org/ - 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi - 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf - 195. http://www.karlrunge.com/x11vnc/ssvnc.html - 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms - 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms - 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabalways - 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 208. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl - 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 210. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx - 211. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 214. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect - 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect - 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nowireframelocal - 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N - 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms - 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 221. http://www.openssl.org/ - 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 223. http://www.stunnel.org/ - 224. http://stunnel.mirt.net/ - 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert - 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA - 228. http://www.karlrunge.com/x11vnc/ssl.html - 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 230. http://www.karlrunge.com/x11vnc/faq.html#infaq_ss_vncviewer - 231. http://www.karlrunge.com/x11vnc/ssvnc.html - 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis - 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 239. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin - 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd - 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate - 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer - 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit - 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-v, - 250. http://www.karlrunge.com/x11vnc/prevrels.html - 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 253. http://www.tightvnc.com/ - 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N - 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 257. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd - 258. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg - 259. http://www.sun.com/sunray/index.html - 260. http://www.karlrunge.com/x11vnc/sunray.html - 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 263. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 264. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 267. http://www.karlrunge.com/x11vnc/faq.html#faq-sound - 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 269. mailto:xvml@karlrunge.com - 270. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks + 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 193. http://www.karlrunge.com/x11vnc/faq.html#faq-avahi + 194. http://www.avahi.org/ + 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi + 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-zeroconf + 197. http://www.karlrunge.com/x11vnc/ssvnc.html + 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms + 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms + 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabalways + 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 210. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl + 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 212. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx + 213. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 216. http://www.karlrunge.com/x11vnc/faq.html#faq-reflect + 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nowireframelocal + 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N + 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 223. http://www.openssl.org/ + 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 225. http://www.stunnel.org/ + 226. http://stunnel.mirt.net/ + 227. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert + 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA + 230. http://www.karlrunge.com/x11vnc/ssl.html + 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 232. http://www.karlrunge.com/x11vnc/faq.html#infaq_ss_vncviewer + 233. http://www.karlrunge.com/x11vnc/ssvnc.html + 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis + 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 241. http://www.karlrunge.com/x11vnc/faq.html#faq-userlogin + 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd + 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit + 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-v, + 252. http://www.karlrunge.com/x11vnc/prevrels.html + 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 255. http://www.tightvnc.com/ + 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N + 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 259. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd + 260. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg + 261. http://www.sun.com/sunray/index.html + 262. http://www.karlrunge.com/x11vnc/sunray.html + 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 265. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay + 266. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 269. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 271. mailto:xvml@karlrunge.com + 272. http://www.karlrunge.com/x11vnc/faq.html#faq-thanks ======================================================================= http://www.karlrunge.com/x11vnc/faq.html: @@ -2044,7 +2061,7 @@ http://www.karlrunge.com/x11vnc/faq.html: [93]Q-91: After using x11vnc for a while, I find that I cannot type some (or any) characters or my mouse clicks and drags no longer have - any affect. What happened? + any effect, or they lead to strange effects. What happened? [94]Q-92: 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 @@ -2488,12 +2505,12 @@ typedef unsigned int in_addr_t; [152]http://www.archlinux.org/ Nokia 770 (.deb) [153]http://mike.saunby.googlepages.com/x11vncfornokia7702 Sharp Zaurus [154]http://www.focv.com/ Redhat/Fedora: (.rpm) - [155]http://dag.wieers.com/rpm/packages/x11vnc/ (N.B.: unmaintained) - [156]http://dries.ulyssis.org/rpm/packages/x11vnc Debian: (.deb) - [157]http://packages.debian.org/x11vnc (N.B: often unmaintained; might - be better to compile from source) Solaris: (pkg) - [158]http://www.sunfreeware.com/ (N.B: very old; better to compile - from source) + [155]http://packages.sw.be/x11vnc RPMforge + [156]http://dag.wieers.com/rpm/packages/x11vnc/ (N.B.: unmaintained + after 0.9.3) Debian: (.deb) [157]http://packages.debian.org/x11vnc + (N.B: often unmaintained; better to compile from source) Solaris: + (pkg) [158]http://www.sunfreeware.com/ (N.B: very old; better to + compile from source) If the above binaries don't work and building x11vnc on your OS fails (and all else fails!) you can try one of [159]My Collection of x11vnc @@ -2576,6 +2593,11 @@ display :0 [tkx11vnc.gif] + NOTE: You may need to install the "wish" or "tk" or "tk8.4" package + for the gui mode to work (the package name depends on your OS/distro.) + The tcl/tk "wish" interpreter is used. In debian (and so ubuntu too) + one would run "apt-get install tk" or perhaps "apt-get install tk8.4" + Q-9: How can I get the GUI to run in the System Tray, or at least be a smaller, simpler icon? @@ -5535,6 +5557,10 @@ t:5 and configuration. + For the general replacement of Xvnc by Xvfb+x11vnc, one user describes + a similar setup he created [465]here. + + Q-67: How can I use x11vnc on "headless" machines? Why might I want to? @@ -5547,15 +5573,16 @@ 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 [465]this FAQ) and access it from + display via x11vnc (e.g. see [466]this FAQ) and access it from anywhere on the network via a VNC viewer. Some tips on getting X servers to start on machines without keyboard or mouse: For XFree86/Xorg the Option "AllowMouseOpenFail" "true" "ServerFlags" config file option is useful. On Solaris Xsun the +nkeyboard and +nmouse options are useful (put them in the server - command line args in /etc/dt/config/Xservers). See Xserver(1) for more - info. + command line args in /etc/dt/config/Xservers). There are patches + available for Xsun at lease back to Solaris 8 that support this. See + Xserver(1) for more info. Although this usage may sound strange it can be quite useful for a GUI (or other) testing or QA setups: the engineers do not need to walk to @@ -5570,10 +5597,10 @@ t:5 cards as it can hold to provide multiple simultaneous access or testing on different kinds of video hardware. - See also the [466]FINDCREATEDISPLAY discussion of the "[467]-display + See also the [467]FINDCREATEDISPLAY discussion of the "[468]-display WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X servers are started automatically for new users connecting. The - [468]-find, [469]-create, [470]-svc, and [471]-xdmsvc aliases can also + [469]-find, [470]-create, [471]-svc, and [472]-xdmsvc aliases can also come in handy here. [Resource Usage and Performance] @@ -5596,7 +5623,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 [472]shm_clear to list and prompt for removal + Here is a shell script [473]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, @@ -5630,44 +5657,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 - [473]-onetile option (corresponds to only 3 shm segments used, and + [474]-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 - [474]-noshm option. Performance will be somewhat degraded but when + [475]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [475]earlier question discussing -noshm). + [476]earlier question discussing -noshm). Q-69: How can I make x11vnc use less system resources? - The [476]-nap (now on by default; use -nonap to disable) and - "[477]-wait n" (where n is the sleep between polls in milliseconds, + The [477]-nap (now on by default; use -nonap to disable) and + "[478]-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 "[478]-sb 15" will cause x11vnc to go into a deep-sleep + something like "[479]-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 [479]-onetile option will use less memory and use fewer shared - memory slots (add [480]-fs 1.0 for one less slot). + the [480]-onetile option will use less memory and use fewer shared + memory slots (add [481]-fs 1.0 for one less slot). Q-70: How can I make x11vnc use MORE system resources? - You can try [481]-threads (note this mode can be unstable and/or + You can try [482]-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 [482]-defer as well. Note that if you try to increase the + dial down [483]-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 [483]-id option) can be streamed over a LAN or wireless at + the x11vnc [484]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. If the graphics card's framebuffer read rate - is [484]faster than normal then the video window size and frame rate - can be much higher. The use of [485]TurboVNC and/or TurboJPEG can make + is [485]faster than normal then the video window size and frame rate + can be much higher. The use of [486]TurboVNC and/or TurboJPEG can make the frame rate somewhat higher still (but most of this hinges on the graphics card's read rate.) @@ -5684,7 +5711,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 - [486]-solid [color] option to try to do this automatically. + [487]-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 @@ -5693,9 +5720,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 [487]-scrollcopyrect is active and + problem in x11vnc 0.7.2 if [488]-scrollcopyrect is active and detecting scrolls for the application). - * If the [488]-wireframe option is not available (earlier than + * If the [489]-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) @@ -5718,7 +5745,7 @@ ied) noticed. VNC viewer parameters: - * Use a [489]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer + * Use a [490]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 @@ -5726,7 +5753,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). [490]SSVNC does too. The colors are poor, but it + even 8 colors). [491]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) @@ -5740,37 +5767,37 @@ ied) file. x11vnc parameters: - * Make sure the [491]-wireframe option is active (it should be on by + * Make sure the [492]-wireframe option is active (it should be on by default) and you have Opaque Moves/Resizes Enabled in the window manager. - * Make sure the [492]-scrollcopyrect option is active (it should be + * Make sure the [493]-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 - [493]-solid - * Specify [494]-speeds modem to force the wireframe and + [494]-solid + * Specify [495]-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 [495]-nodragging (no screen updates when dragging mouse, + drastic [496]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Set [496]-fs 1.0 (disables fullscreen updates) - * Try increasing [497]-wait or [498]-defer (reduces the maximum + * Set [497]-fs 1.0 (disables fullscreen updates) + * Try increasing [498]-wait or [499]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * Try the [499]-progressive pixelheight mode with the block + * Try the [500]-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 [500]-id (cuts + * If you just want to watch one (simple) window use [501]-id (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [501]-nosel (disables all clipboard selection exchange) - * Use [502]-nocursor and [503]-nocursorpos (repainting the remote + * Set [502]-nosel (disables all clipboard selection exchange) + * Use [503]-nocursor and [504]-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 - [504]-readtimeout n setting if it sometimes takes more than 20sec + [505]-readtimeout n setting if it sometimes takes more than 20sec to paint the full screen, etc. - * Do not use [505]-fixscreen to automatically refresh the whole + * Do not use [506]-fixscreen to automatically refresh the whole screen, tap three Alt_L's then the screen has painting errors (rare problem). @@ -5839,7 +5866,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 [506]slow (e.g. + in main memory. So reading the fb is still painfully [507]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 @@ -5857,45 +5884,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 "[507]-xd_area A" option to adjust the size + skipped). You can use the "[508]-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 "[508]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[509]-noxdamage". + The option "[509]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[510]-noxdamage". Q-73: 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 "[510]-noxdamage" option. + he uses the "[511]-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 [511]MiniMyth reports that the 'alphapulse' tag of the + A developer for [512]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 [512]this FAQ too. + Update: see [513]this FAQ too. Q-74: 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 [513]slow hardware read rates from + This problem is primarily due to [514]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 - [514]-pointer_mode option for more info. The next bottleneck is + [515]-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 @@ -5905,27 +5932,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 "[515]-pointer_mode 1" option. + the "[516]-pointer_mode 1" option. - Also added was the [516]-nodragging option that disables all screen + Also added was the [517]-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 [517]-pointer_mode n option was introduced. n=1 is + As of Dec/2004 the [518]-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 [518]-threads option can improve + Also, in some circumstances the [519]-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 [519]wireframe FAQ and - [520]scrollcopyrect FAQ below) provide schemes to sweep this problem + As of Apr/2005 two new options (see the [520]wireframe FAQ and + [521]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 @@ -5949,8 +5976,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 [521]slow video card - read rates (see [522]here too). A displacement, even a small one, of a + intermediate steps. BTW the lurching is due to [522]slow video card + read rates (see [523]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. @@ -5958,7 +5985,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 [523]-nowireframe option + with the problem. It can be disabled with the [524]-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 @@ -6004,13 +6031,13 @@ EndSection * Maximum time to show a wireframe animation. * Minimum time between sending wireframe outlines. - See the [524]"-wireframe tweaks" option for more details. On a slow + See the [525]"-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 - [525]"-wirecopyrect mode" option. It is also on by default. This + [526]"-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 @@ -6058,7 +6085,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 [526]slow). + the hardware framebuffer is [527]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. @@ -6085,10 +6112,10 @@ EndSection the X server display: if one falls too far behind it could become a mess... - The initial implementation of [527]-scrollcopyrect option is useful in + The initial implementation of [528]-scrollcopyrect option is useful in that it detects many scrolls and thus gives a much nicer working - environment (especially when combined with the [528]-wireframe - [529]-wirecopyrect [530]options, which are also on by default; and if + environment (especially when combined with the [529]-wireframe + [530]-wirecopyrect [531]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. @@ -6121,10 +6148,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: [531]-fixscreen + also: [532]-fixscreen * Some applications, notably OpenOffice, do XCopyArea scrolls in weird ways that assume ancestor window clipping is taking place. - See the [532]-scr_skip option for ways to tweak this on a + See the [533]-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 @@ -6141,7 +6168,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 [533]-scale option there will be a quick CopyRect + * When using the [534]-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 @@ -6154,7 +6181,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 [534]-noscrollcopyrect (or -noscr for short). If you find + with the [535]-noscrollcopyrect (or -noscr for short). If you find some extremely bad and repeatable behavior for -scrollcopyrect please report a bug. @@ -6179,9 +6206,9 @@ EndSection that pixel data is needed again it does not have to be retransmitted over the network. - As of Dec/2006 in the [535]0.9 development tarball there is an + As of Dec/2006 in the [536]0.9 development tarball there is an experimental client-side caching implementation enabled by the - "[536]-ncache n" option. In fact, during the test period it was on by + "[537]-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 @@ -6208,7 +6235,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. [537]SSVNC (see below) can do this + cache area cannot be seen. [538]SSVNC (see below) can do this automatically. At some point LibVNCServer may implement a "rfbFBCrop" pseudoencoding @@ -6218,7 +6245,7 @@ EndSection rendering...). The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice - [538]-ycrop option to help hide the pixel cache area from view. It + [539]-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 @@ -6249,7 +6276,7 @@ EndSection an additional factor of 2 in memory use. However, even in the smallest usage mode with n equal 2 and - [539]-ncache_no_rootpixmap set (this requires only 2X additional + [540]-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. @@ -6260,7 +6287,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 "[540]-ncache_cr". By specifying + Another option to experiment with is "[541]-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 @@ -6317,24 +6344,24 @@ EndSection As of Feb/2009 (development tarball) there is an experimental kludge to let you build x11vnc using TurboVNC's modified TightVNC encoding. - [541]TurboVNC is part of the [542]VirtualGL project. It does two main + [542]TurboVNC is part of the [543]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. [543]TurboJPEG is an + instead of the usual libjpeg implementation. [544]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. "[544]-wait 5" and "[545]-defer 5" (or even a + down the delays, e.g. "[545]-wait 5" and "[546]-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 - [546]TurboJPEG software. + [547]TurboJPEG software. In brief, the steps look like this: cd x11vnc-x.y.z/x11vnc/misc/turbovnc @@ -6346,22 +6373,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 [547]SSVNC viewer has + will be implemented. Support for TurboVNC in [548]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 [548]misc. bins directory. For other platforms + TurboVNC support in the [549]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 [549]SSVNC, both TurboVNC enabled, were able to + 6200) x11vnc and [550]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 [550]20-30 fps with the glxspheres + higher-end hardware can sustain [551]20-30 fps with the glxspheres benchmark. - Potential Slowdown: As we describe [551]elsewhere, unless you use + Potential Slowdown: As we describe [552]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) @@ -6401,23 +6428,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 "[552]-cursor X" option that + A simple kludge is provided by the "[553]-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 "[553]-cursor some" option for + work for those cases. Also see the "[554]-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 - [554]-overlay option is supplied. See [555]this FAQ for more info. + [555]-overlay option is supplied. See [556]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 - [556]Solaris 10. + [557]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 @@ -6425,7 +6452,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. [557]Details can be found here. + hidden alpha channel data under 32bpp. [558]Details can be found here. Q-80: When using XFIXES cursorshape mode, some of the cursors look @@ -6458,17 +6485,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 "[558]-alphacut n" option lets + course!) some tunable parameters. The "[559]-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 "[559]-alphafrac f" option tries to correct individual + 240. The "[560]-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 [560]-alpharemove that is useful for + Finally, there is an option [561]-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 @@ -6494,10 +6521,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 [561]-nocursorshape x11vnc option. In this case the cursor is + with the [562]-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 [562]-noalphablend option to disable this + the x11vnc side. Use the [563]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). @@ -6521,7 +6548,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 [563]Enhanced TightVNC Viewer (SSVNC) + This patch is applied to the [564]Enhanced TightVNC Viewer (SSVNC) package we provide. [Mouse Pointer] @@ -6529,9 +6556,9 @@ EndSection Q-82: 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 [564]tightvnc extension + This default takes advantage of a [565]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [565]-nocursor + the local VNC viewer. You may disable it with the [566]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -6545,17 +6572,17 @@ EndSection clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [566]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [567]-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 [567]-nocursorpos and [568]-nocursorshape. + is the default. See also [568]-nocursorpos and [569]-nocursorshape. Q-84: 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: [569]-buttonmap + You can remap the mouse buttons via something like: [570]-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. @@ -6563,7 +6590,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 [570]-debug_pointer option prints out much info for + Note that the [571]-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 @@ -6585,7 +6612,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 [571]-buttonmap but rather configuring the X server + consider not using [572]-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"'). @@ -6615,7 +6642,7 @@ EndSection Q-85: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [572]-modtweak should help here. It is a mode that monitors + The option [573]-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. @@ -6624,20 +6651,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 [573]this FAQ for more info). Without + not exist on the keyboard (see [574]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 [574]FAQ about the -xkb option for a more powerful method + Also see the [575]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 - [575]-debug_keyboard option prints out much info for every keystroke + [576]-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 [576]-nomodtweak. + His solution was to disable all of the above and use [577]-nomodtweak. This is the simplest form of keystroke insertion and it actually solved the problem. Try it if the other options don't help. @@ -6650,9 +6677,9 @@ EndSection (e.g. pc105 in the XF86Config file when it should be something else, say pc104). - Short Cut: Try the [577]-xkb or [578]-sloppy_keys options and see if + Short Cut: Try the [578]-xkb or [579]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [579]-modtweak is now the default) but it is useful reference for + [580]-modtweak is now the default) but it is useful reference for various tricks and so is kept. @@ -6695,17 +6722,17 @@ EndSection -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([580]-modtweak) is a mode that monitors the + settings. The former ([581]-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 ([581]-remap less-comma) is an immediate remapping of the + The latter ([582]-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 [582]FAQ about the -xkb option as a possible workaround + See also the [583]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [583]-debug_keyboard option prints out much info for + Note that the [584]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. @@ -6713,7 +6740,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 [584]keymapping + the Shift key before releasing the "<". Because of a [585]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. @@ -6721,9 +6748,9 @@ EndSection characters: in general it can happen whenever the Shift key is released early. - This should not happen in [585]-xkb mode, because it works hard to + This should not happen in [586]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [586]-sloppy_keys to attempt a similar type of algorithm. + option [587]-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 "." @@ -6751,7 +6778,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 [587]-modtweak + This all worked fine with x11vnc running with the [588]-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 @@ -6768,7 +6795,7 @@ EndSection * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [588]-xkb option seems to fix all of the missing keys: "@", "<", + The [589]-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 @@ -6776,7 +6803,7 @@ EndSection debugging output (send it along with any problems you report). Update: as of Jun/2005 x11vnc will try to automatically enable - [589]-xkb if it appears that would be beneficial (e.g. if it sees any + [590]-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. @@ -6791,7 +6818,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: - [590]-skip_keycodes 93 + [591]-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 @@ -6809,16 +6836,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 [591]-remap x11vnc option: + created using the [592]-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 - [592]-add_keysyms option in the next paragraph. - Update: for convenience "[593]-remap DEAD" does many of these + [593]-add_keysyms option in the next paragraph. + Update: for convenience "[594]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [594]-remap, an - option [595]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [595]-remap, an + option [596]-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 @@ -6837,7 +6864,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) [596]-norepeat x11vnc option. You will still + use the new (Jul/2004) [597]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -6861,7 +6888,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 [597]-norepeat (which has since Dec/2004 been + needed, or to use the [598]-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 @@ -6872,7 +6899,7 @@ EndSection keystrokes!! Are you using x11vnc to log in to an X session via display manager? - (as described in [598]this FAQ) If so, x11vnc is starting before your + (as described in [599]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 @@ -6894,37 +6921,50 @@ EndSection Q-91: After using x11vnc for a while, I find that I cannot type some (or any) characters or my mouse clicks and drags no longer have any - affect. What happened? + effect, or they lead to strange effects. What happened? + + Probably a modifier key, e.g. Control or Alt is "stuck" in a pressed + down state. - This happens often for VNC in general by the following mechanism. - Suppose on the Viewer side desktop there is some hot-key to switch + This happens for VNC in general by the following mechanism. Suppose on + the Viewer side desktop there is some hot-key to switch desktops/rooms/spaces, etc. E.g. suppose Alt+LeftArrow moves to the left desktop/room/space. Or suppose an Alt+hotkey combination - iconifies a window. + iconifies a window. This can leave the Alt key pressed down on the + remote side. Consider the sequence that happens. The Alt_L key and then the - LeftArrow key go down. Since you are inside the viewer these key - presses are sent to the other side (x11vnc) so they are pressed down - in the remote desktop as well. Your local desktop (where the VNC + LeftArrow key go down. Since you are inside the viewer the Alt_L key + press is sent to the other side (x11vnc) and so it is pressed down in + the remote desktop as well. (by "Alt_L" we mean the Alt key on the + left-hand side of the keyboard.) Your local desktop (where the VNC Viewer is running) then warps to the new desktop/room/space: Leaving - the Alt_L and (possibly) the LeftArrow keys still pressed down in the - remote desktop. + the Alt_L key still pressed down in the remote desktop. If someone is sitting at the desktop, or when you return in the viewer it may be very confusing because the Alt_L is still pressed down but - you (or the person sitting that the desktop) do not realize this. - Depending on the remote desktop (x11vnc side) it can act very strange. + you (or the person sitting at the desktop) do not realize this. + Depending on which remote desktop (x11vnc side) is used, it can act + very strangely. A quick workaround when you notice this is to press and release all of the Alt, Shift, Control, Windows-Flag, modifier keys to free the pressed one. You need to do this for both the left and right Shift, Alt, Control, etc. keys to be sure. - You can also use the [599]-clear_mods option to try to clear all of + Note that many VNC Viewers try to guard against this when they are + notified by the window system that the viewer app has "lost focus". + When it receives the "lost focus" event, the viewer sends VNC + Key-Release events for all modifier keys that are currently pressed + down. This does not always work, however, since it depends on how the + desktop manages these "warps". If the viewer is not notified it cannot + know it needs to release the modifiers. + + You can also use the [600]-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 [600]-remap to prevent sending all of the problem modifier + of using [601]-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: @@ -6937,16 +6977,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 [601]this FAQ on lock keys - problem. These options may help avoid the problem: [602]-skip_lockkeys - and [603]-capslock. See also [604]-clear_all. + down on the local (Viewer) side. See [602]this FAQ on lock keys + problem. These options may help avoid the problem: [603]-skip_lockkeys + and [604]-capslock. See also [605]-clear_all. Q-92: 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 "[605]-remap Super_R-Mode_switch" x11vnc option may + Something like "[606]-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)). @@ -6969,7 +7009,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 [606]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [607]-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. @@ -6989,7 +7029,7 @@ EndSection and similar triple mappings (with two in the AltGr/Mode_switch group) of a keysum to a single keycode. - Use the [607]-nomodtweak option as a workaround. You can also use + Use the [608]-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" @@ -7003,7 +7043,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 [608]-remap + have x11vnc do the remapping. This can be done via the [609]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -7012,7 +7052,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: - [609]-remap Super_R-Button2 + [610]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -7031,13 +7071,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 - [610]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[611]-remap Caps_Lock-None". + [611]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[612]-remap Caps_Lock-None". - Also try the [612]-nomodtweak and [613]-capslock options. + Also try the [613]-nomodtweak and [614]-capslock options. Another useful option that turns off any Lock keys on the remote side - at startup and end is the [614]-clear_all option. During a session you + at startup and end is the [615]-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 @@ -7066,7 +7106,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 - [615]the next FAQ on x11vnc scaling. + [616]the next FAQ on x11vnc scaling. Q-98: Does x11vnc support server-side framebuffer scaling? (E.g. to @@ -7074,7 +7114,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 "[616]-scale fraction" option. "fraction" can either be a + use the "[617]-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. @@ -7099,7 +7139,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 - [617]applications. Since with integer scale factors the framebuffers + [618]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -7125,7 +7165,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 ([618]-rfbport option, + different scalings listening on separate ports ([619]-rfbport option, etc.). Update: As of May/2006 x11vnc also supports the UltraVNC server-side @@ -7135,8 +7175,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 [619]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [620]"-connect + use the [620]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [621]"-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 @@ -7145,7 +7185,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 - [621]"-scale_cursor frac" option to set the cursor scaling to a + [622]"-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). @@ -7173,21 +7213,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 [622]-blackout x11vnc option + may be distracting to the viewer. The [623]-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 - [623]-xinerama x11vnc option can be used to have it automatically + [624]-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: - [624]-xinerama is now on by default. + [625]-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 [625]-xwarppointer + of the large display. If this happens try using the [626]-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 [626]-xwarppointer will + Xinerama is enabled). Update: As of Dec/2006 [627]-xwarppointer will be applied automatically if Xinerama is detected. To disable use: -noxwarppointer @@ -7210,23 +7250,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 [627]FAQ to increase the limit. It - is probably also a good idea to run with the [628]-onetile option in + /etc/system as mentioned in another [628]FAQ to increase the limit. It + is probably also a good idea to run with the [629]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [629]-noshm to use no shm segments. + [630]-noshm to use no shm segments. Q-101: 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 "[630]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[631]-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 [631]Xinerama screen into two + One user used -clip to split up a large [632]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [632]-id or [633]-sid options are used. The offset is measured + the [633]-id or [634]-sid options are used. The offset is measured from the upper left corner of the selected window. @@ -7235,7 +7275,7 @@ EndSection just seems to crash. As of Dec/2004 x11vnc supports XRANDR. You enable it with the - [634]-xrandr option to make x11vnc monitor XRANDR events and also trap + [635]-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. @@ -7245,9 +7285,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 [635]-padgeom option to make the region big + viewers you can try the [636]-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: [636]SSVNC + for the TightVNC Viewer on Unix: [637]SSVNC If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you @@ -7259,7 +7299,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 [637]-rotate option allow this. E.g's: + As of Jul/2006 there is the [638]-rotate option allow this. E.g's: "-rotate +90", "-rotate -90", "-rotate x", etc. @@ -7324,13 +7364,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 [638]here for how to + straight xscreensaver (see the instructions [639]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 [639]-nodpms option was added + suspend, or off). In Nov/2006 the x11vnc [640]-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 @@ -7346,21 +7386,21 @@ 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 - [640]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video + [641]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video card driver. - As a workaround apply the [641]-noxdamage option. As of Feb/2007 + As a workaround apply the [642]-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 [642]this + beryl you might as well always supply -noxdamage. Thanks to [643]this user who reported the problem and discovered the workaround. - A developer for [643]MiniMyth reports that the 'alphapulse' tag of the + A developer for [644]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. - Please report a bug or complaint to Beryl and/or Xorg about this: - running x11vnc with -noxdamage disables a nice improvement in + Please report a bug or complaint to Beryl/Compiz and/or Xorg about + this: running x11vnc with -noxdamage disables a nice improvement in responsiveness (especially for typing) and also leads to unnecessary CPU and memory I/O load due to the extra polling. @@ -7375,9 +7415,9 @@ EndSection * Fullscreen mode The way VMWare does Fullscreen mode on Linux is to display the Guest - desktop in a separate Virtual Console (e.g. VC 8) (see [644]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [645]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X - server. So x11vnc cannot access it (however, [645]see this discussion + server. So x11vnc cannot access it (however, [646]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. @@ -7398,13 +7438,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 [646]is in the active VC. + as long as the VMWare X session [647]is in the active VC. Also note that with a little bit of playing with "xwininfo -all -children" output one can extract the (non-toplevel) 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 [647]-id windowid option. The + the VMWare menu buttons) by use of the [648]-id windowid option. The caveats are the X session VMWare is in must be in the active VC and the window must be fully visible, so this mode is not terribly convenient, but could be useful in some circumstances (e.g. running @@ -7420,10 +7460,10 @@ EndSection controlled) via VNC with x11vnc? As of Apr/2005 there is support for this. Two options were added: - "[648]-rawfb string" (to indicate the raw frame buffer device, file, - etc. and its parameters) and "[649]-pipeinput command" (to provide an + "[649]-rawfb string" (to indicate the raw frame buffer device, file, + etc. and its parameters) and "[650]-pipeinput command" (to provide an external program that will inject or otherwise process mouse and - keystroke input). Some useful [650]-pipeinput schemes, VID, CONSOLE, + keystroke input). Some useful [651]-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 @@ -7463,9 +7503,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 [651]-snapfb option with + this). The "snap:" setting applies the [652]-snapfb option with "file:" type reading (this is useful for exporting webcams or TV tuner - video; see [652]the next FAQ for more info). + video; see [653]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 @@ -7510,7 +7550,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 [653]X + for the case of Xvfb x11vnc can poll it much better via the [654]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -7541,13 +7581,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 [654]Qt-embedded apps (PDAs/Handhelds). By default the + fullscreen, or [655]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 [655]this FAQ for details. If specified via "-rawfb Video" + kernel. See [656]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). @@ -7555,10 +7595,10 @@ minal #2) also useful in testing. - All of the above [656]-rawfb options are just for viewing the raw + All of the above [657]-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 [657]video camera mapped its framebuffer + this feature (e.g. suppose a [658]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 @@ -7596,7 +7636,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 VC #2 (assuming it is the [658]active VC) one + view and interact with VC #2 (assuming it is the [659]active VC) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -7651,7 +7691,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 - [659]Qt-embedded Also, for example the [660]VMWare Fullscreen mode is + [660]Qt-embedded Also, for example the [661]VMWare Fullscreen mode is actually viewable under -rawfb and can be interacted with if uinput is enabled. @@ -7715,9 +7755,9 @@ minal #2) Q-112: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - Yes, this is possible to some degree with the [661]-rawfb option. + Yes, this is possible to some degree with the [662]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [662]previous FAQ on -rawfb + used for the screen image data. See the [663]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -7729,7 +7769,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 [663]-snapfb mode which appears to be necessary. + The "snap:" enforces [664]-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. @@ -7751,7 +7791,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 [664]-24to32 option will be automatically imposed when in + etc, the [665]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -7759,7 +7799,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 [665]-wait, [666]-slow_fb, or [667]-defer + the framerate via the [666]-wait, [667]-slow_fb, or [668]-defer options. Decreasing the window size and bpp also helps. @@ -7848,7 +7888,7 @@ minal #2) format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [668]-freqtab option to supply your own xawtv channel to + See also the [669]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc). @@ -7857,7 +7897,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 [669]-rawfb scheme where the + Yes, the basic method for this is the [670]-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: @@ -7870,7 +7910,7 @@ minal #2) x11vnc -rawfb /dev/fb0@640x480x16 Also, to force usage of the uinput injection method use "-pipeinput - UINPUT". See the [670]-pipeinput description for tunable parameters, + UINPUT". See the [671]-pipeinput description for tunable parameters, etc. One problem with the x11vnc uinput scheme is that it cannot guess the @@ -7886,7 +7926,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 [671]-pipeinput UINPUT option for tuning + times a second. See the [672]-pipeinput UINPUT option for tuning parameters that can be set (there are some experimental thresh=N tuning parameters as well) @@ -7921,7 +7961,7 @@ minal #2) Q-114: 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 [672]-rawfb only + Yes, as of Jul/2006 x11vnc enables building for [673]-rawfb only support. Just do something like when building: ./configure --without-x (plus any other flags) make @@ -7937,11 +7977,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 - [673]-rawfb mechanism described above. The mouse and keyboard input is + [674]-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 [674]OSXvnc (aka Vine - Server), or [675]Apple Remote Desktop (ARD). Perhaps there is some + So you can use x11vnc as an alternative to [675]OSXvnc (aka Vine + Server), or [676]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. @@ -7951,7 +7991,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 [676]-id windowid mode (and the + only work reasonably in single window [677]-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 @@ -7969,9 +8009,9 @@ minal #2) ./configure --without-x make - Win2VNC/x2vnc: One handy use is to use the [677]-nofb mode to + Win2VNC/x2vnc: One handy use is to use the [678]-nofb mode to redirect mouse and keyboard input to a nearby Mac (i.e. one to the - side of your desk) via [678]x2vnc or Win2VNC. See [679]this FAQ for + side of your desk) via [679]x2vnc or Win2VNC. See [680]this FAQ for more info. Options: Here are the Mac OS X specific x11vnc options: @@ -8045,13 +8085,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 "[680]-reflect host:N" option to + Yes, as of Feb/2007 there is the "[681]-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 - [681]-rawfb description under "VNC HOST" for more details. + [682]-rawfb description under "VNC HOST" for more details. You can replace "host:N" with "listen" or "listen:port" for reverse connections. @@ -8112,18 +8152,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 [682]-nodragging if the + not doing wireframing somehow, consider [683]-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: - [683]http://sourceforge.net/projects/vnc-reflector/, - [684]http://www.tightvnc.com/projector/ (closed source?), + [684]http://sourceforge.net/projects/vnc-reflector/, + [685]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 "[685]"-connect host1,host2,..." option). + connections (the x11vnc "[686]"-connect host1,host2,..." option). Suppose all the clients "C" are started up in Listen mode: client1> vncviewer -listen client2> vncviewer -listen @@ -8182,7 +8222,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 [686]this FAQ. + 755 ./x11vnc.static" and then find the -auth file as in [687]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 @@ -8191,7 +8231,7 @@ rm -f $tmp wget http://192.168.0.22/x11vnc.static chmod 755 ./x11vnc.static - Find the name of the auth file as in [687]this FAQ. (maybe run "ps + Find the name of the auth file as in [688]this FAQ. (maybe run "ps wwwwaux | grep auth"). Then run it like this: ./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile @@ -8200,7 +8240,7 @@ rm -f $tmp the display being :1, etc. If there is a firewall blocking incoming connections during the - install, use the [688]"-connect hostname" option option for a reverse + install, use the [689]"-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 @@ -8249,11 +8289,11 @@ rm -f $tmp As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY and CLIPBOARD selection (Xvnc does not seem to do this). If you don't want the - Clipboard/Selection exchanged use the [689]-nosel option. If you don't + Clipboard/Selection exchanged use the [690]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [690]-noprimary option. (with a similar thing for CLIPBOARD). You can - also fine-tune it a bit with the [691]-seldir dir option and also - [692]-input. + [691]-noprimary option. (with a similar thing for CLIPBOARD). You can + also fine-tune it a bit with the [692]-seldir dir option and also + [693]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -8265,7 +8305,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 - [693]pyvnc2swf. There are a number of [694]tutorials (broken link?) on + [694]pyvnc2swf. There are a number of [695]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 @@ -8280,11 +8320,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux). - The [695]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [696]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 [696]-tightfilexfer option. + the [697]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -8307,7 +8347,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 [697]-users option, then VNC Viewers that connect are able to do + the [698]-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 @@ -8326,7 +8366,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [698]-ultrafilexfer which is an alias for the above option and + Or use [699]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -8338,14 +8378,14 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [699]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [700]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [700]-noultraext (the + To disable SingleWindow and ServerInput use [701]-noultraext (the others are managed by LibVNCServer). See this option too: - [701]-noserverdpms. + [702]-noserverdpms. - Also, the [702]UltraVNC repeater proxy is supported for use with - reverse connections: "[703]-connect repeater://host:port+ID:NNNN". Use + Also, the [703]UltraVNC repeater proxy is supported for use with + reverse connections: "[704]-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. @@ -8356,12 +8396,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [704]Single Click (SC) mode can be emulated fairly + Yes, UltraVNC's [705]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 [705]Mac OS X. + or family to use. This includes [706]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 @@ -8417,7 +8457,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 [706]this page for some variations on this method, e.g. how to add + See [707]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -8429,11 +8469,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 [707]here. + reverse connections). More info [708]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [708]router will have to be configured to + NAT/Firewall/Router the [709]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. @@ -8443,7 +8483,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. [709]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [710]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -8479,7 +8519,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 [710]Enhanced TightVNC Viewer (SSVNC) package we + better use the [711]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 @@ -8509,11 +8549,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 [711]-ssl + The only change from the "vnc" above is the addition of the [712]-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 [712]here.) + info [713]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -8522,7 +8562,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 [713]Enhanced TightVNC Viewer + The easiest way to do this is use [714]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 @@ -8552,7 +8592,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 [714]this link and [715]this one too for more info on SSL certs. + See [715]this link and [716]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 @@ -8573,7 +8613,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [716]here. + [717]here. OpenSSL libssl.so.0.9.7 problems: @@ -8583,7 +8623,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [717]details here. + You will find the [718]details here. Q-123: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -8592,7 +8632,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 [718]Samba example here. + We show a simple [719]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: @@ -8632,7 +8672,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 [719]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [720]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8642,7 +8682,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 [720]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [721]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). @@ -8724,7 +8764,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 [721]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [722]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8825,7 +8865,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 [722]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [723]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing). @@ -8837,14 +8877,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 [723]-nobell option. If + If you don't want to hear the beeps use the [724]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [724]redirector such as esd. + trying a [725]redirector such as esd. Q-127: Does x11vnc work with IPv6? - Currently the only way to do this is via [725]inetd. You configure + Currently the only way to do this is via [726]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. @@ -8853,7 +8893,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 [726]IPv6 enabled, so a + Also note that not all VNC Viewers are [727]IPv6 enabled, so a redirector could even be needed on the client side. @@ -8864,9 +8904,8 @@ or: Q-128: Thanks for your program and for your help! Can I make a donation? - Please do (any amount is appreciated; only a few people have donated - anything) and thank you for your support! Click on the PayPal button - below for more info. + Please do (any amount is appreciated; very few have donated) and thank + you for your support! Click on the PayPal button below for more info. [x-click-but04.gif]-Submit @@ -9026,8 +9065,8 @@ References 152. http://www.archlinux.org/packages/search/?q=x11vnc 153. http://mike.saunby.googlepages.com/ 154. http://www.focv.com/ipkg/ - 155. http://dag.wieers.com/rpm/packages/x11vnc/ - 156. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html + 155. http://packages.sw.be/x11vnc/ + 156. http://dag.wieers.com/rpm/packages/x11vnc/ 157. http://packages.debian.org/x11vnc 158. http://www.sunfreeware.com/ 159. http://www.karlrunge.com/x11vnc/bins @@ -9336,268 +9375,269 @@ References 462. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc 463. http://www.karlrunge.com/x11vnc/Xdummy 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 465. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously - 466. http://www.karlrunge.com/x11vnc/faq.html#infaq_findcreatedisplay - 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 472. http://www.karlrunge.com/x11vnc/shm_clear - 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 475. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm - 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb - 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 484. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 485. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc - 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 489. http://www.tightvnc.com/ - 490. http://www.karlrunge.com/x11vnc/ssvnc.html - 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds - 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout - 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 506. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 465. http://www.isc.cnrs.fr/informatique/public_notice/x11vnc + 466. http://www.karlrunge.com/x11vnc/faq.html#infaq_display-manager-continuously + 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/shm_clear + 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 476. http://www.karlrunge.com/x11vnc/faq.html#faq-noshm + 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb + 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 485. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 486. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc + 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 490. http://www.tightvnc.com/ + 491. http://www.karlrunge.com/x11vnc/ssvnc.html + 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds + 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout + 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 507. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 511. http://minimyth.org/ - 512. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl - 513. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 512. http://minimyth.org/ + 513. http://www.karlrunge.com/x11vnc/faq.html#faq-beryl + 514. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 519. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe - 520. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect - 521. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode - 522. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 520. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 521. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollcopyrect + 522. http://www.karlrunge.com/x11vnc/faq.html#faq-pointer-mode + 523. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 526. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect - 530. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe - 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip - 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 535. http://www.karlrunge.com/x11vnc/index.html#beta-test - 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 537. http://www.karlrunge.com/x11vnc/ssvnc.html - 538. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop - 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap - 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr - 541. http://www.virtualgl.org/About/TurboVNC - 542. http://www.virtualgl.org/ - 543. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 546. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 547. http://www.karlrunge.com/x11vnc/ssvnc.html - 548. http://www.karlrunge.com/x11vnc/bins - 549. http://www.karlrunge.com/x11vnc/ssvnc.html - 550. http://www.virtualgl.org/About/Reports - 551. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 527. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect + 531. http://www.karlrunge.com/x11vnc/faq.html#faq-wireframe + 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip + 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 536. http://www.karlrunge.com/x11vnc/index.html#beta-test + 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 538. http://www.karlrunge.com/x11vnc/ssvnc.html + 539. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap + 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 542. http://www.virtualgl.org/About/TurboVNC + 543. http://www.virtualgl.org/ + 544. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 547. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 548. http://www.karlrunge.com/x11vnc/ssvnc.html + 549. http://www.karlrunge.com/x11vnc/bins + 550. http://www.karlrunge.com/x11vnc/ssvnc.html + 551. http://www.virtualgl.org/About/Reports + 552. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 555. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode - 556. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 557. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks - 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 563. http://www.karlrunge.com/x11vnc/ssvnc.html - 564. http://www.tightvnc.com/ - 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer - 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 573. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 574. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 556. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode + 557. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 558. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks + 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 564. http://www.karlrunge.com/x11vnc/ssvnc.html + 565. http://www.tightvnc.com/ + 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 574. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 575. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 582. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 584. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 583. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 585. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes + 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 598. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 601. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock - 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 599. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 602. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock + 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 615. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling - 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 617. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html - 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 616. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling + 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 618. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html + 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 627. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm - 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 631. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama - 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 628. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm + 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 632. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 636. http://www.karlrunge.com/x11vnc/ssvnc.html - 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate - 638. http://www.jwz.org/xscreensaver/man1.html - 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms - 640. http://www.beryl-project.org/ - 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 642. http://www.dslinux.org/blogs/pepsiman/?p=73 - 643. http://minimyth.org/ - 644. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 645. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 646. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 637. http://www.karlrunge.com/x11vnc/ssvnc.html + 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 639. http://www.jwz.org/xscreensaver/man1.html + 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 641. http://www.beryl-project.org/ + 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 643. http://www.dslinux.org/blogs/pepsiman/?p=73 + 644. http://minimyth.org/ + 645. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 646. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 647. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 652. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 653. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 654. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 655. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 657. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 658. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 659. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 660. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware - 661. 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/x11vnc_opts.html#opt-snapfb - 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab - 669. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 653. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 654. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 655. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 656. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 658. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 659. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 660. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 661. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware + 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 663. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 670. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 674. http://www.testplant.com/products/vine_server/OS_X - 675. http://www.apple.com/remotedesktop/ - 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 675. http://www.testplant.com/products/vine_server/OS_X + 676. http://www.apple.com/remotedesktop/ 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 678. http://fredrik.hubbe.net/x2vnc.html - 679. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc - 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect - 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 683. http://sourceforge.net/projects/vnc-reflector/ - 684. http://www.tightvnc.com/projector/ - 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 686. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 679. http://fredrik.hubbe.net/x2vnc.html + 680. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc + 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 682. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 684. http://sourceforge.net/projects/vnc-reflector/ + 685. http://www.tightvnc.com/projector/ + 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect 687. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 693. http://www.unixuser.org/~euske/vnc2swf/ - 694. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ - 695. http://www.karlrunge.com/x11vnc/ssvnc.html - 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer - 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer - 699. http://www.karlrunge.com/x11vnc/ssvnc.html - 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext - 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 702. http://www.uvnc.com/addons/repeater.html - 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 704. http://www.uvnc.com/addons/singleclick.html - 705. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx - 706. http://www.karlrunge.com/x11vnc/single-click.html + 688. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 694. http://www.unixuser.org/~euske/vnc2swf/ + 695. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ + 696. http://www.karlrunge.com/x11vnc/ssvnc.html + 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 700. http://www.karlrunge.com/x11vnc/ssvnc.html + 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 703. http://www.uvnc.com/addons/repeater.html + 704. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 705. http://www.uvnc.com/addons/singleclick.html + 706. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx 707. http://www.karlrunge.com/x11vnc/single-click.html - 708. http://www.karlrunge.com/x11vnc/index.html#firewalls - 709. http://sc.uvnc.com/ - 710. http://www.karlrunge.com/x11vnc/ssvnc.html - 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 712. http://www.karlrunge.com/x11vnc/single-click.html - 713. http://www.karlrunge.com/x11vnc/ssvnc.html - 714. http://www.karlrunge.com/x11vnc/single-click.html - 715. http://www.karlrunge.com/x11vnc/ssl.html - 716. http://www.karlrunge.com/x11vnc/single-click.html - 717. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems - 718. http://www.samba.org/ - 719. http://www.karlrunge.com/x11vnc/ssvnc.html - 720. http://www.cups.org/ - 721. http://www.karlrunge.com/x11vnc/ssvnc.html + 708. http://www.karlrunge.com/x11vnc/single-click.html + 709. http://www.karlrunge.com/x11vnc/index.html#firewalls + 710. http://sc.uvnc.com/ + 711. http://www.karlrunge.com/x11vnc/ssvnc.html + 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 713. http://www.karlrunge.com/x11vnc/single-click.html + 714. http://www.karlrunge.com/x11vnc/ssvnc.html + 715. http://www.karlrunge.com/x11vnc/single-click.html + 716. http://www.karlrunge.com/x11vnc/ssl.html + 717. http://www.karlrunge.com/x11vnc/single-click.html + 718. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 719. http://www.samba.org/ + 720. http://www.karlrunge.com/x11vnc/ssvnc.html + 721. http://www.cups.org/ 722. http://www.karlrunge.com/x11vnc/ssvnc.html - 723. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 724. http://www.karlrunge.com/x11vnc/faq.html#faq-sound - 725. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd - 726. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html + 723. http://www.karlrunge.com/x11vnc/ssvnc.html + 724. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 725. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 726. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 727. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -11560,30 +11600,38 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) * ZRLE VNC encoding support (RealVNC's encoding) * Support for the ZYWRLE encoding, a wavelet based extension to ZRLE to improve compression of motion video and photo regions. - * Experimental [19]TurboVNC support ([20]VirtualGL's modified - TightVNC encoding; requires TurboJPEG library) + * [19]TurboVNC support ([20]VirtualGL's modified TightVNC encoding; + requires TurboJPEG library) + * Pipelined Updates of the framebuffer as in TurboVNC (asks for the + next update before the current one has finished downloading; this + gives some speedup on high latency connections.) * Cursor [21]alphablending with x11vnc at 32bpp (-alpha option) * Option "-unixpw ..." for use with "x11vnc -unixpw" type login dialogs. + * VeNCrypt SSL/TLS VNC encryption support (used by [22]VeNCrypt, + QEMU, ggi, libvirt/virt-manager/xen, vinagre/gvncviewer/gtk-vnc) + * ANONTLS SSL/TLS VNC encryption support (used by vino) * Support for UltraVNC extensions: 1/n Server side scaling, Text Chat, Single Window, Disable Server-side Input. Both UltraVNC and x11vnc servers support these extensions. * UltraVNC File Transfer via an auxiliary Java helper program (java must be in $PATH). Note that the x11vnc server also supports UltraVNC file transfer. - * Connection support for the [22]UltraVNC repeater proxy (-repeater + * Connection support for the [23]UltraVNC repeater proxy (-repeater option). - * Support for UltraVNC [23]Single Click operation. (both + * Support for UltraVNC [24]Single Click operation. (both unencrypted: SC I, and SSL encrypted: SC III) - * Support for UltraVNC [24]DSM Encryption Plugin symmetric + * Support for UltraVNC [25]DSM Encryption Plugin symmetric encryption mode. (ARC4, AESV2, and MSRC4) + * Support for UltraVNC [26]MS-Logon authentication (NOTE: the + UltraVNC MS-Logon key exchange implementation is very weak; an + eavesdropper on the network can recover your Windows password + easily; you need to use an additional encrypted tunnel with + MS-Logon.) * Support for symmetric encryption (including blowfish and 3des ciphers) to Non-UltraVNC Servers. Any server using the same - encryption method will work, [25]e.g.: x11vnc -enc + encryption method will work, [27]e.g.: x11vnc -enc blowfish:./my.key - * VeNCrypt SSL/TLS VNC encryption support (used by [26]VeNCrypt, - QEMU, ggi, libvirt/virt-manager/xen, vinagre/gvncviewer/gtk-vnc) - * ANONTLS SSL/TLS VNC encryption support (used by vino) * Instead of hostname:display one can also supply "exec=command args..." to connect the viewer to the stdio of an external command (e.g. stunnel or socat) rather than using a TCP/IP socket. Unix @@ -11596,7 +11644,7 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) (-use64/-bgr222, -use8/-bgr111) * Medium color mode: 16bpp mode on a 32bpp Viewer display (-16bpp/-bgr565) - * For use with x11vnc's [27]client-side caching -ncache method use + * For use with x11vnc's [28]client-side caching -ncache method use the cropping option -ycrop n. This will "hide" the large pixel buffer cache below the actual display. Set to the actual height or use -1 for autodetection (also, tall screens, H > 2*W, are @@ -11607,12 +11655,13 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) inside the viewport via Arrow keys or a mouse drag. * Scrollbar width setting: -sbwidth n, the default is very thin, 2 pixels, for less distracting -ycrop usage. - * Improvements to the [28]Popup menu, all of these can now be + * Improvements to the [29]Popup menu, all of these can now be changed dynamically via the menu: ViewOnly, Toggle Bell, CursorShape updates, X11 Cursor, Cursor Alphablending, Toggle Tight/ZRLE, Toggle JPEG, FullColor/16bpp/8bpp (256/64/8 colors), Greyscale for low color modes, Scaling the Viewer resolution, - Escape Keys, and others, including UltraVNC extensions. + Escape Keys, Pipeline Updates, and others, including UltraVNC + extensions. * Maintains its own BackingStore if the X server does not. * The default for localhost:0 connections is not raw encoding since same-machine connections are pretty rare. Default assumes you are @@ -11633,7 +11682,7 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) These are all self-contained in the bundle directory: they will not be installed on your system. Just un-zip or un-tar the file you downloaded and run the frontend ssvnc straight from its directory. - Alternatively, on Unix you can use the [29]conventional source + Alternatively, on Unix you can use the [30]conventional source tarball. Here is the Quick Start info from the README for how to do that: @@ -11753,7 +11802,7 @@ Windows: _________________________________________________________________ - You can read all of the SSVNC GUI's [30]Online Help Text here. + You can read all of the SSVNC GUI's [31]Online Help Text here. _________________________________________________________________ The bundle unpacks a directory/folder named: ssvnc. It contains these @@ -11765,14 +11814,14 @@ Windows: (the Mac OS X and Unix launchers are simply links to the bin directory). See the README for more information. - The [31]SSH-Only mode launcher program has name sshvnc. The - [32]Terminal Services mode launcher program (assumes x11vnc 0.8.4 or + The [32]SSH-Only mode launcher program has name sshvnc. The + [33]Terminal Services mode launcher program (assumes x11vnc 0.8.4 or later and Xvfb installed on the server machine) has name tsvnc. The Viewer SSL support is done via a wrapper script (bin/ssvnc_cmd that calls bin/util/ss_vncviewer) that starts up the STUNNEL tunnel first and then starts the TightVNC viewer pointed at that tunnel. The - bin/ssvnc program is a GUI front-end to that script. See [33]this FAQ + bin/ssvnc program is a GUI front-end to that script. See [34]this FAQ for more details on SSL tunnelling. In SSH connection mode, the wrappers start up SSH appropriately. @@ -11819,7 +11868,7 @@ start \ssvnc\Windows\ssvnc.exe switch from the regular SSVNC mode, click "Terminal Services" under Options. - This mode requires [34]x11vnc (0.9.3 or later) installed on the remote + This mode requires [35]x11vnc (0.9.3 or later) installed on the remote machine to find, create, and manage the user sessions. SSH is used to create the encrypted and authenticated tunnel. The Xvfb (virtual framebuffer X server) program must also be installed on the remote @@ -11837,7 +11886,7 @@ start \ssvnc\Windows\ssvnc.exe press "Connect"). Normally the Terminal Services sessions created are virtual (RAM-only) - ones (e.g. Xvfb, [35]Xdummy, or Xvnc), however a nice feature is if + ones (e.g. Xvfb, [36]Xdummy, or Xvnc), however a nice feature is if you have a regular X session (i.e displaying on the physical hardware) on the remote machine that you are ALREADY logged into, then the x11vnc run from tsvnc will find it for you as well. @@ -11858,7 +11907,7 @@ start \ssvnc\Windows\ssvnc.exe Proxies: Web proxies, SOCKS proxies, and the UltraVNC repeater proxy are supported to allow the SSVNC connection to go through the proxy to the otherwise unreachable VNC Server. SSH gateway machines can be used - in the same way. Read [36]more about SSVNC proxy support here. + in the same way. Read [37]more about SSVNC proxy support here. Dynamic VNC Server Port determination: If you are running SSVNC on @@ -11885,7 +11934,7 @@ or: PORT= vncserver :4; sleep 15 sessions if called repeatedly. If you use PORT= on Windows, a large random port is selected instead - and the [37]-rfbport option is passed to x11vnc (it does not work with + and the [38]-rfbport option is passed to x11vnc (it does not work with vncserver). @@ -11896,7 +11945,7 @@ or: PORT= vncserver :4; sleep 15 resize when the server does (e.g. "x11vnc -R scale=3/4" remote control command). - The cursor alphablending is [38]described here. + The cursor alphablending is [39]described here. The RealVNC ZRLE encoding is supported, in addition to some low colors modes (16bpp and 8bpp at 256, 64, and even 8 colors, for use on very @@ -11906,7 +11955,7 @@ or: PORT= vncserver :4; sleep 15 The Popup menu (F8) is enhanced with the ability to change many things on the fly. F9 is added as a shortcut to toggle FullScreen mode. - Client Side Caching: The x11vnc [39]client-side caching is handled + Client Side Caching: The x11vnc [40]client-side caching is handled nicely by this viewer. The very large pixel cache below the actual display in this caching method is distracting. Our Unix VNC viewer will automatically try to autodetect the actual display height if the @@ -11919,7 +11968,7 @@ or: PORT= vncserver :4; sleep 15 scrollbars are set to be very thin (2 pixels) to be less distracting. Use the -sbwidth n to make them wider. - Probably nobody is interested in the [40]grabserver patch for old + Probably nobody is interested in the [41]grabserver patch for old window managers when the viewer is in fullscreen mode... This and some other unfixed bugs have been fixed in our patches (fullscreen toggle works with KDE, -x11cursor has been fixed, and the dot cursor has been @@ -12056,8 +12105,24 @@ Enhanced TightVNC viewer (SSVNC) options: -rawlocal Prefer raw encoding for localhost, default is no, i.e. assumes you have a SSH tunnel instead. + -sendclipboard Send the X CLIPBOARD selection (i.e. Ctrl+C, + Ctrl+V) instead of the X PRIMARY selection (mouse + select and middle button paste.) + + -sendalways Whenever the mouse enters the VNC viewer main + window, send the selection to the VNC server even if + it has not changed. This is like the Xt resource + translation SelectionToVNC(always) + + -recvtext str When cut text is received from the VNC server, + ssvncviewer will set both the X PRIMARY and the + X CLIPBOARD local selections. To control which + is set, specify 'str' as 'primary', 'clipboard', + or 'both' (the default.) + -graball Grab the entire X server when in fullscreen mode, needed by some old window managers like fvwm2. + -popupfix Warp the popup back to the pointer position, needed by some old window managers like fvwm2. @@ -12143,6 +12208,17 @@ r some reason, each RFB msg type must be sent twice under DSM . + -mslogon user Use Windows MS Logon to an UltraVNC server. Supply the + username or "1" to be prompted. The default is to + autodetect the UltraVNC MS Logon server and prompt for + the username and password. + + IMPORTANT NOTE: The UltraVNC MS-Logon Diffie-Hellman + exchange is very weak and can be brute forced to recover + your username and password in a few hours or seconds of CPU + time. To be safe, be sure to use an additional encrypted + tunnel (e.g. SSL or SSH) for the entire VNC session. + -chatonly Try to be a client that only does UltraVNC text chat. This mode is used by x11vnc to present a chat window on the physical X11 console (i.e. chat with the person at the @@ -12158,6 +12234,12 @@ r keybindings and Popup menu) Then point to the file via XENVIRONMENT or XAPPLRESDIR. + -pipeline Like TurboVNC, request the next framebuffer update as soon + as possible instead of waiting until the end of the current + framebuffer update coming in. Helps 'pipeline' the updates +. + This is currently the default, use -nopipeline to disable. + -escape str This sets the 'Escape Keys' modifier sequence and enables escape keys mode. When the modifier keys escape sequence is held down, the next keystroke is interpreted locally @@ -12238,6 +12320,7 @@ r Set Y Crop (y-max) ~ -ycrop Set Scrollbar Width ~ -sbwidth XGrabServer ~ -graball + Pipeline Updates ~ -pipeline UltraVNC Extensions: @@ -12275,7 +12358,7 @@ r _________________________________________________________________ Hopefully this tool will make it convenient for people to help test - and use the [41]built-in SSL support in x11vnc. Extra testing of this + and use the [42]built-in SSL support in x11vnc. Extra testing of this feature is much appreciated!! Thanks. Please Help Test the newly added features: @@ -12288,13 +12371,13 @@ r Server machine, and to mount your local Windows or Samba shares on the remote VNC Server machine. Basically these new features try to automate the tricks described here: - [42]http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares - [43]http://www.karlrunge.com/x11vnc/faq.html#faq-cups - [44]http://www.karlrunge.com/x11vnc/faq.html#faq-sound + [43]http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares + [44]http://www.karlrunge.com/x11vnc/faq.html#faq-cups + [45]http://www.karlrunge.com/x11vnc/faq.html#faq-sound _________________________________________________________________ Downloading: Downloads for this project are hosted at - [45]Sourceforge.net. + [46]Sourceforge.net. Choose the archive file bundle that best suits you (e.g. no source code, windows only, unix only, zip, tar etc). @@ -12305,25 +12388,25 @@ r "ssvnc_unix_only" (or "ssvnc_no_windows" to recompile). On Mac OS X? Use "ssvnc_no_windows". On Windows? Use "ssvnc_windows_only". - [46]ssvnc_windows_only-1.0.22.zip Windows Binaries Only. No source incl + [47]ssvnc_windows_only-1.0.22.zip Windows Binaries Only. No source incl uded (~6MB) - [47]ssvnc_no_windows-1.0.22.tar.gz Unix and Mac OS X Only. No Windows bin + [48]ssvnc_no_windows-1.0.22.tar.gz Unix and Mac OS X Only. No Windows bin aries. Source included. (~9MB) - [48]ssvnc_unix_only-1.0.22.tar.gz Unix Binaries Only. No source incl + [49]ssvnc_unix_only-1.0.22.tar.gz Unix Binaries Only. No source incl uded. (~6.5MB) - [49]ssvnc_unix_minimal-1.0.22.tar.gz Unix Minimal. You must supply your ow + [50]ssvnc_unix_minimal-1.0.22.tar.gz Unix Minimal. You must supply your ow n vncviewer and stunnel. (~0.1MB) - [50]ssvnc-1.0.22.tar.gz All Unix, Mac OS X, and Windows binari + [51]ssvnc-1.0.22.tar.gz All Unix, Mac OS X, and Windows binari es and source TGZ. (~15MB) - [51]ssvnc-1.0.22.zip All Unix, Mac OS X, and Windows binari + [52]ssvnc-1.0.22.zip All Unix, Mac OS X, and Windows binari es and source ZIP. (~15MB) - [52]ssvnc_all-1.0.22.zip All Unix, Mac OS X, and Windows binari + [53]ssvnc_all-1.0.22.zip All Unix, Mac OS X, and Windows binari es and source AND full archives in the zip dir. (~18MB) Here is a conventional source tarball: - [53]ssvnc-1.0.22.src.tar.gz Conventional Source for SSVNC GUI and + [54]ssvnc-1.0.22.src.tar.gz Conventional Source for SSVNC GUI and Unix VNCviewer (~0.4MB) it will be of use to those who do not want the SSVNC @@ -12333,7 +12416,7 @@ Unix VNCviewer (~0.4MB) stunnel source, and so has a dependency that the system stunnel is installed. - Read the [54]README.src file for more information on using the + Read the [55]README.src file for more information on using the conventional source tarball. @@ -12343,21 +12426,21 @@ Unix VNCviewer (~0.4MB) Here are the corresponding 1.0.23 development bundles: - [55]ssvnc_windows_only-1.0.23.zip - [56]ssvnc_no_windows-1.0.23.tar.gz - [57]ssvnc_unix_only-1.0.23.tar.gz - [58]ssvnc_unix_minimal-1.0.23.tar.gz + [56]ssvnc_windows_only-1.0.23.zip + [57]ssvnc_no_windows-1.0.23.tar.gz + [58]ssvnc_unix_only-1.0.23.tar.gz + [59]ssvnc_unix_minimal-1.0.23.tar.gz - [59]ssvnc-1.0.23.tar.gz - [60]ssvnc-1.0.23.zip - [61]ssvnc_all-1.0.23.zip + [60]ssvnc-1.0.23.tar.gz + [61]ssvnc-1.0.23.zip + [62]ssvnc_all-1.0.23.zip - [62]ssvnc-1.0.23.src.tar.gz Conventional Source for SSVNC GUI and + [63]ssvnc-1.0.23.src.tar.gz Conventional Source for SSVNC GUI and Unix VNCviewer (~0.4MB) For any Unix system, a self-extracting and running file for the - "ssvnc_unix_minimal" package is here: [63]ssvnc. Save it as filename + "ssvnc_unix_minimal" package is here: [64]ssvnc. Save it as filename "ssvnc", type "chmod 755 ./ssvnc", and then launch the GUI via typing "./ssvnc". Note that this "ssvnc_unix_minimal" mode requires you install the "stunnel" and "vncviewer" programs externally (for @@ -12366,11 +12449,11 @@ Unix VNCviewer (~0.4MB) SSVNC features will be missing. Previous releases: - [64]Release 1.0.18 at Sourceforge.net - [65]Release 1.0.19 at Sourceforge.net - [66]Release 1.0.20 at Sourceforge.net - [67]Release 1.0.21 at Sourceforge.net - [68]Release 1.0.22 at Sourceforge.net + [65]Release 1.0.18 at Sourceforge.net + [66]Release 1.0.19 at Sourceforge.net + [67]Release 1.0.20 at Sourceforge.net + [68]Release 1.0.21 at Sourceforge.net + [69]Release 1.0.22 at Sourceforge.net Please help test the UltraVNC File Transfer support in the native Unix @@ -12413,16 +12496,16 @@ Unix VNCviewer (~0.4MB) redistribute the above because of cryptographic software they contain or for other reasons. Please check out your situation and information at the following and related sites: - [69]http://www.stunnel.org - [70]http://stunnel.mirt.net - [71]http://www.openssl.org - [72]http://www.chiark.greenend.org.uk/~sgtatham/putty/ - [73]http://www.tightvnc.com - [74]http://www.realvnc.com - [75]http://sourceforge.net/projects/cotvnc/ + [70]http://www.stunnel.org + [71]http://stunnel.mirt.net + [72]http://www.openssl.org + [73]http://www.chiark.greenend.org.uk/~sgtatham/putty/ + [74]http://www.tightvnc.com + [75]http://www.realvnc.com + [76]http://sourceforge.net/projects/cotvnc/ _________________________________________________________________ - README: Here is the toplevel [76]README from the bundle. + README: Here is the toplevel [77]README from the bundle. References @@ -12447,61 +12530,62 @@ References 19. http://www.karlrunge.com/x11vnc/faq.html#faq-turbovnc 20. http://www.virtualgl.org/ 21. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks - 22. http://www.uvnc.com/addons/repeater.html - 23. http://www.uvnc.com/addons/singleclick.html - 24. http://www.uvnc.com/features/encryption.html - 25. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc - 26. http://sourceforge.net/projects/vencrypt/ - 27. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching - 28. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#popup - 29. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#source - 30. http://www.karlrunge.com/x11vnc/ssvnc_help.html - 31. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc - 32. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc - 33. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext - 34. http://www.karlrunge.com/x11vnc/index.html - 35. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 36. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html - 37. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 38. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks - 39. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching - 40. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollbars - 41. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int - 42. http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares - 43. http://www.karlrunge.com/x11vnc/faq.html#faq-cups - 44. http://www.karlrunge.com/x11vnc/faq.html#faq-sound - 45. http://sourceforge.net/projects/ssvnc - 46. http://downloads.sourceforge.net/ssvnc/ssvnc_windows_only-1.0.22.zip?use_mirror= - 47. http://downloads.sourceforge.net/ssvnc/ssvnc_no_windows-1.0.22.tar.gz?use_mirror= - 48. http://downloads.sourceforge.net/ssvnc/ssvnc_unix_only-1.0.22.tar.gz?use_mirror= - 49. http://downloads.sourceforge.net/ssvnc/ssvnc_unix_minimal-1.0.22.tar.gz?use_mirror= - 50. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.22.tar.gz - 51. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.22.zip - 52. http://downloads.sourceforge.net/ssvnc/ssvnc_all-1.0.22.zip?use_mirror= - 53. http://downloads.sourceforge.net/ssvnc/ssvnc-1.0.22.src.tar.gz?use_mirror= - 54. http://www.karlrunge.com/x11vnc/etv/README.src.txt - 55. http://ssvnc.sourceforge.net/dev/ssvnc_windows_only-1.0.23.zip - 56. http://ssvnc.sourceforge.net/dev/ssvnc_no_windows-1.0.23.tar.gz - 57. http://ssvnc.sourceforge.net/dev/ssvnc_unix_only-1.0.23.tar.gz - 58. http://ssvnc.sourceforge.net/dev/ssvnc_unix_minimal-1.0.23.tar.gz - 59. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.tar.gz - 60. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.zip - 61. http://ssvnc.sourceforge.net/dev/ssvnc_all-1.0.23.zip - 62. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.src.tar.gz - 63. http://www.karlrunge.com/x11vnc/etv/ssvnc - 64. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636282 - 65. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636337 - 66. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636338 - 67. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=640923 - 68. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=652804 - 69. http://www.stunnel.org/ - 70. http://stunnel.mirt.net/ - 71. http://www.openssl.org/ - 72. http://www.chiark.greenend.org.uk/~sgtatham/putty/ - 73. http://www.tightvnc.com/ - 74. http://www.realvnc.com/ - 75. http://sourceforge.net/projects/cotvnc/ - 76. http://www.karlrunge.com/x11vnc/README.ssvnc.html + 22. http://sourceforge.net/projects/vencrypt/ + 23. http://www.uvnc.com/addons/repeater.html + 24. http://www.uvnc.com/addons/singleclick.html + 25. http://www.uvnc.com/features/encryption.html + 26. http://www.uvnc.com/features/authentication.html + 27. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-enc + 28. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching + 29. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#popup + 30. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#source + 31. http://www.karlrunge.com/x11vnc/ssvnc_help.html + 32. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc + 33. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc + 34. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-ext + 35. http://www.karlrunge.com/x11vnc/index.html + 36. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 37. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html + 38. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 39. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks + 40. http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching + 41. http://www.karlrunge.com/x11vnc/faq.html#faq-scrollbars + 42. http://www.karlrunge.com/x11vnc/faq.html#faq-ssl-tunnel-int + 43. http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares + 44. http://www.karlrunge.com/x11vnc/faq.html#faq-cups + 45. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 46. http://sourceforge.net/projects/ssvnc + 47. http://downloads.sourceforge.net/ssvnc/ssvnc_windows_only-1.0.22.zip?use_mirror= + 48. http://downloads.sourceforge.net/ssvnc/ssvnc_no_windows-1.0.22.tar.gz?use_mirror= + 49. http://downloads.sourceforge.net/ssvnc/ssvnc_unix_only-1.0.22.tar.gz?use_mirror= + 50. http://downloads.sourceforge.net/ssvnc/ssvnc_unix_minimal-1.0.22.tar.gz?use_mirror= + 51. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.22.tar.gz + 52. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.22.zip + 53. http://downloads.sourceforge.net/ssvnc/ssvnc_all-1.0.22.zip?use_mirror= + 54. http://downloads.sourceforge.net/ssvnc/ssvnc-1.0.22.src.tar.gz?use_mirror= + 55. http://www.karlrunge.com/x11vnc/etv/README.src.txt + 56. http://ssvnc.sourceforge.net/dev/ssvnc_windows_only-1.0.23.zip + 57. http://ssvnc.sourceforge.net/dev/ssvnc_no_windows-1.0.23.tar.gz + 58. http://ssvnc.sourceforge.net/dev/ssvnc_unix_only-1.0.23.tar.gz + 59. http://ssvnc.sourceforge.net/dev/ssvnc_unix_minimal-1.0.23.tar.gz + 60. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.tar.gz + 61. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.zip + 62. http://ssvnc.sourceforge.net/dev/ssvnc_all-1.0.23.zip + 63. http://ssvnc.sourceforge.net/dev/ssvnc-1.0.23.src.tar.gz + 64. http://www.karlrunge.com/x11vnc/etv/ssvnc + 65. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636282 + 66. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636337 + 67. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=636338 + 68. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=640923 + 69. http://sourceforge.net/project/showfiles.php?group_id=243486&package_id=296727&release_id=652804 + 70. http://www.stunnel.org/ + 71. http://stunnel.mirt.net/ + 72. http://www.openssl.org/ + 73. http://www.chiark.greenend.org.uk/~sgtatham/putty/ + 74. http://www.tightvnc.com/ + 75. http://www.realvnc.com/ + 76. http://sourceforge.net/projects/cotvnc/ + 77. http://www.karlrunge.com/x11vnc/README.ssvnc.html ======================================================================= http://www.karlrunge.com/x11vnc/x11vnc_opts.html: @@ -12514,7 +12598,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.8 lastmod: 2009-03-30 +x11vnc: allow VNC connections to real X11 displays. 0.9.8 lastmod: 2009-05-18 x11vnc options: -display disp -auth file -N @@ -12639,7 +12723,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.8 lastmod: 2009-03-30 +x11vnc: allow VNC connections to real X11 displays. 0.9.8 lastmod: 2009-05-18 (type "x11vnc -opts" to just list the options.) @@ -13483,6 +13567,9 @@ e if [list] starts with the "%" character. See the quick_pw() function in the source for details. + Use -nounixpw to disable unixpw mode if it was enabled + earlier in the cmd line (e.g. -svc mode) + -unixpw_nis [list] As -unixpw above, however do not use su(1) but rather use the traditional getpwnam(3) + crypt(3) method to verify passwords. All of the above -unixpw options and @@ -15327,10 +15414,13 @@ t -repeat VNC clients are connected and VNC keyboard input is not idle for more than 5 minutes. This works around a repeating keystrokes bug (triggered by long processing - delays between key down and key up client events: either - from large screen changes or high latency). + delays between key down and key up client events: + either from large screen changes or high latency). Default: -norepeat + You can set the env. var. X11VNC_IDLE_TIMEOUT to the + number of idle seconds you want (5min = 300secs). + Note: your VNC viewer side will likely do autorepeating, so this is no loss unless someone is simultaneously at the real X display. @@ -15786,7 +15876,7 @@ t to Keystroke generated scrolls (e.g. Up arrow). If it is prefixed with "MOUSE:" it only applies to Mouse induced scrolls (e.g. dragging on a scrollbar). - Default: ##Soffice.bin,##StarOffice + Default: ##Soffice.bin,##StarOffice,##OpenOffice -scr_inc list Opposite of -scr_skip: this list is consulted first and if there is a match the window will be monitored @@ -16228,12 +16318,25 @@ t -sig ignore:INT,TERM,exit:USR1 -threads Whether or not to use the threaded libvncserver --nothreads algorithm [rfbRunEventLoop] if libpthread is available - Default: -nothreads. NOTE: The -threads mode is now - disabled due to its unstable behavior. Not recommended, - but you can recompile with -DX11VNC_THREADED in - CPPFLAGS if you need to use it. You can also set the - env. variable X11VNC_THREADED=1 +-nothreads algorithm [rfbRunEventLoop] if libpthread is available. + In this mode new threads (one for input and one + for output) are created to handle each new client. + Default: -nothreads. + + NOTE: The -threads mode may be disabled due to its + unstable behavior. If it is disabled, a warning is + printed out. Stability has been improved in version + 0.9.8 and so the feature has been re-enabled. + + Multiple clients in threaded mode should be stable + for the ZRLE encoding on all platforms. The Tight and + Zlib encodings are currently only stable on Linux for + multiple clients. Compile with -DTLS=__thread if your + OS and compiler and linker support it. + + Multiple clients in threaded mode could yield better + performance for 'class-room' broadcasting usage. + See also the -reflect option. -fs f If the fraction of changed tiles in a poll is greater than f, the whole screen is updated. Default: 0.75 |
