diff options
| author | runge <runge> | 2008-09-07 04:17:33 +0000 |
|---|---|---|
| committer | runge <runge> | 2008-09-07 04:17:33 +0000 |
| commit | d5cba7a574a667f5321194cb05d0b4adcb995866 (patch) | |
| tree | 2748fd38612cc63256ee864284cd8dab19f4eba1 /x11vnc/README | |
| parent | dbfa4ad1f78f6133bc5f50e766f7f3bfdb8fa049 (diff) | |
| download | libtdevnc-d5cba7a574a667f5321194cb05d0b4adcb995866.tar.gz libtdevnc-d5cba7a574a667f5321194cb05d0b4adcb995866.zip | |
x11vnc: kill gui_pid on exit in -connect/-connect_or_exit mode.
-grablocal n experiment (not compiled by default). -macuskbd
option for macosx for orig uskdb code. keycode=N remote contol
cmd. Find dpy look at non-NFS cookies in /tmp. Fix gui tray
insertion on recent gnome dt. Fix connect_file bug. Sync SSVNC
Diffstat (limited to 'x11vnc/README')
| -rw-r--r-- | x11vnc/README | 2912 |
1 files changed, 1233 insertions, 1679 deletions
diff --git a/x11vnc/README b/x11vnc/README index 309d9ec..5fdba0c 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Fri Jun 6 23:11:50 EDT 2008 +x11vnc README file Date: Sat Sep 6 21:54:38 EDT 2008 The following information is taken from these URLs: @@ -1046,11 +1046,11 @@ make via their certificates in either -ssl or -stunnel modes. * Certificate creation and management tools are provide in the [185]-sslGenCert, [186]-sslGenCA, and [187]related options. - * An SSL enabled Java applet VNC Viewer applet is provided 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 [188]-https port option). A wrapper shell script + * 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 [188]-https port option). A wrapper shell script [189]ss_vncviewer is also provided that sets up a stunnel client-side tunnel on Unix systems. See [190]Enhanced TightVNC Viewer (SSVNC) for other SSL/SSH viewer possibilities. @@ -1587,8 +1587,8 @@ make [313]Q-84: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! - [314]Q-85: When I try to type a "<" (i.e. less than) instead I get - "<," (i.e. an extra comma). + [314]Q-85: Extra Character Inserted, E.g.: When I try to type a "<" + (i.e. less than) instead I get "<," (i.e. an extra comma). [315]Q-86: I'm using an "international" keyboard (e.g. German "de", or Danish "dk") and the -modtweak mode works well if the VNC viewer is @@ -1770,9 +1770,9 @@ make may need to set your XAUTHORITY environment variable (or use the [357]-auth option) to point to the correct MIT-MAGIC-COOKIE file (e.g. /home/joe/.Xauthority or /var/gdm/:0.Xauth or /var/lib/kdm/A:0-crWk72K - or /tmp/.gdmzndVlR, etc.), or simply be sure you run x11vnc as the - correct user (i.e. the user who is logged into the X session you wish - to view). + or /tmp/.gdmzndVlR, etc, etc.), or simply be sure you run x11vnc as + the correct user (i.e. the user who is logged into the X session you + wish to view). Note: The MIT cookie file contains the secret key that allows x11vnc to connect to the desired X display. @@ -2138,11 +2138,11 @@ display :0 smaller, simpler icon? As of Jul/2005 the gui can run in a more friendly small icon mode - "-gui icon" or in the system tray: "-gui tray". It has balloon status, - a simple menu, and a Properities dialog. The full, complicated, gui is - only available under "Advanced". Other improvements were added as - well. Try "Misc -> simple_gui" for a gui with fewer esoteric menu - items. + "[393]-gui icon" or in the system tray: "[394]-gui tray". It has + balloon status, a simple menu, and a Properities dialog. The full, + complicated, gui is only available under "Advanced". Other + improvements were added as well. Try "Misc -> simple_gui" for a gui + with fewer esoteric menu items. If the gui fails to embed itself in the system tray, do a retry via "Window View -> icon" followed by "Window View -> tray" with the popup @@ -2166,18 +2166,18 @@ display :0 PORT=59xx line to see which port it found, then subtract 5900 from it for the VNC display number to enter into the VNC Viewer(s). - The "[393]-N" option will try to match the VNC display number to the X + The "[395]-N" option will try to match the VNC display number to the X display (e.g. X11 DISPLAY of :5 (port 6005) will have VNC display :5 (port 5905)). - Also see the "[394]-autoport n" option to indicated at which value the + Also see the "[396]-autoport n" option to indicated at which value the auto probing should start at. Q-11: My Firewall/Router doesn't allow VNC Viewers to connect to x11vnc. - See the [395]Firewalls/Routers discussion. + See the [397]Firewalls/Routers discussion. Q-12: Is it possible for a VNC Viewer and a VNC Server to connect to @@ -2191,7 +2191,7 @@ display :0 In the following discussion, we will suppose port 5950 is being used on the relay machine as the VNC port for the rendezvous. - A way to rendezvous is to have the VNC Server start a [396]reverse + A way to rendezvous is to have the VNC Server start a [398]reverse connection to the relay machine: x11vnc -connect third-machine.net:5950 ... @@ -2210,11 +2210,11 @@ display :0 the owner to allow you to install this software (and he would likely need to open his server's firewall to allow the port through). - It is recommended that [397]SSL is used for encryption (e.g. - "[398]-ssl SAVE") when going over the internet. + It is recommended that [399]SSL is used for encryption (e.g. + "[400]-ssl SAVE") when going over the internet. We have a prototype for performing a rendezvous via a Web Server - acting as the relay machine. Download the [399]vncxfer CGI script and + acting as the relay machine. Download the [401]vncxfer CGI script and see the instructions at the top. Once that CGI script is set up on the website, both users go to, say, @@ -2244,7 +2244,7 @@ display :0 port requirement (e.g. use HTTP/CGI itself for the transfer... it is difficult to emulate a full-duplex TCP connection with them.) - See also the [400]Firewalls/Routers discussion and [401]Reverse + See also the [402]Firewalls/Routers discussion and [403]Reverse Connection Proxy discussion. @@ -2272,7 +2272,7 @@ display :0 vncviewer -encodings "copyrect tight zrle hextile" localhost:0 (we assume the old-style -encodings option needs to be used. See - [402]here for details.). + [404]here for details.). If the SSH machine has been configured (see sshd_config(5)) with the option GatewayPorts=yes, then the tunnel set up by the VNC Server will @@ -2282,16 +2282,16 @@ display :0 only runs: vncviewer third-machine.net:33 - In this case we recommend [403]SSL be used for encryption. + In this case we recommend [405]SSL be used for encryption. The creation of both tunnels can be automated. As of Oct/2007 the - [404]-ssh x11vnc option is available and so only this command needs to + [406]-ssh x11vnc option is available and so only this command needs to be run on the VNC Server side: x11vnc -ssh user@third-machine.net:33 ... (the SSH passphrase may need to be supplied). - To automate on the VNC Viewer side, the user can use the [405]Enhanced + To automate on the VNC Viewer side, the user can use the [407]Enhanced TightVNC Viewer (SSVNC) by: * Clicking on 'Use SSH' * Entering user@third-machine.net:33 into 'VNC Host:Display' entry @@ -2308,11 +2308,11 @@ display :0 Q-13: Can I make x11vnc more quiet and also go into the background after starting up? - Use the [406]-q and [407]-bg options, respectively. (also: -quiet is + Use the [408]-q and [409]-bg options, respectively. (also: -quiet is an alias for -q) Note that under -bg the stderr messages will be lost unless you use - the "[408]-o logfile" option. + the "[410]-o logfile" option. Q-14: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with @@ -2338,8 +2338,8 @@ display :0 Q-16: KDE's krdc VNC viewer cannot connect to x11vnc. - This has been fixed in x11vnc version 0.8.4. More info [409]here, - [410]here, and [411]here. + This has been fixed in x11vnc version 0.8.4. More info [411]here, + [412]here, and [413]here. Q-17: Are there any build-time customizations possible, e.g. change @@ -2347,7 +2347,7 @@ display :0 There are some options. They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS environment variable before running configure - (see the [412]build notes for general background). + (see the [414]build notes for general background). /* * Mar/2006 * Build-time customization via CPPFLAGS. @@ -2418,21 +2418,21 @@ display :0 dual-screen mode to pass the keystrokes and mouse motions to the X11 display? - Yes, for best response start up x11vnc with the "[413]-nofb" option + Yes, for best response start up x11vnc with the "[415]-nofb" option (disables framebuffer polling, and does other optimizations) on the secondary display (X11) machine. Then start up Win2VNC on the primary display (Windows) referring it to the secondary display. - This will also work X11 to X11 using [414]x2vnc, however you would + This will also work X11 to X11 using [416]x2vnc, however you would probably just want to avoid VNC and use x2x for that. For reference, here are some links to Win2VNC-like programs for multiple monitor setups: - * [415]Original Win2VNC - * [416]Enhanced Win2VNC and [417]sourceforge link - * [418]x2vnc - * [419]x2x also [420]here - * [421]zvnc (MorphOS) + * [417]Original Win2VNC + * [418]Enhanced Win2VNC and [419]sourceforge link + * [420]x2vnc + * [421]x2x also [422]here + * [423]zvnc (MorphOS) All of them will work with x11vnc (except x2x where it is not needed). @@ -2452,7 +2452,7 @@ display :0 on your display to be depth 24 TrueColor? Sun machines often have 8+24 overlay/multi-depth visuals, and you can make the default visual depth 24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004 x11vnc - has the [422]-visual option to allow you to force the framebuffer + has the [424]-visual option to allow you to force the framebuffer visual to whatever you want (this usually messes up the colors unless you are very clever). In this case, the option provides a convenient workaround for the Win2VNC bug: @@ -2466,7 +2466,7 @@ display :0 and keyboard input to it from Windows and X11 machines via Win2VNC and x2vnc, respectively? - Yes, as of Nov/2006 [423]you can. There may be a trick or two you'll + Yes, as of Nov/2006 [425]you can. There may be a trick or two you'll need to do to get the Clipboard exchange between the machines to work. @@ -2477,7 +2477,7 @@ display :0 PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while they are incorrect in certain windows. - Use the [424]-flashcmap option to have x11vnc watch for changes in the + Use the [426]-flashcmap option to have x11vnc watch for changes in the colormap, and propagate those changes back to connected clients. This can be slow (since the whole screen must be updated over the network whenever the colormap changes). This flashing colormap behavior often @@ -2486,13 +2486,13 @@ display :0 example of this. Consider reconfiguring the system to 16 bpp or depth 24 TrueColor if at all possible. - Also note the option [425]-8to24 (Jan/2006) can often remove the need + Also note the option [427]-8to24 (Jan/2006) can often remove the need for flashing the colormap. Everything is dynamically transformed to depth 24 at 32 bpp using the colormaps. There may be painting errors however (see the following FAQ for tips on reducing and correcting them). - In some rare cases (SCO unixware) the [426]-notruecolor option has + In some rare cases (SCO unixware) the [428]-notruecolor option has corrected colors on 8bpp displays. The red, green, and blue masks were non-zero in 8bpp PseudoColor on an obscure setup, and this option corrected the problems. @@ -2503,13 +2503,13 @@ display :0 different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - You may want to review the [427]previous question regarding 8 bpp + You may want to review the [429]previous question regarding 8 bpp PseudoColor. - On some hardware (Sun/SPARC and SGI), the [428]-overlay option + On some hardware (Sun/SPARC and SGI), the [430]-overlay option discussed a couple paragraphs down may solve this for you (you may want to skip to it directly). On other hardware the less robust - [429]-8to24 option may help (also discussed below). + [431]-8to24 option may help (also discussed below). Run xdpyinfo(1) to see what the default visual is and what the depths of the other visuals are. Does the default visual have a depth of 8 @@ -2545,7 +2545,7 @@ TrueColor defdepth 24 The -overlay mode: Another option is if the system with overlay visuals is a Sun system running Solaris or SGI running IRIX you can - use the [430]-overlay x11vnc option (Aug/2004) to have x11vnc use the + use the [432]-overlay x11vnc option (Aug/2004) to have x11vnc use the Solaris XReadScreen(3X11) function to poll the "true view" of the whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on IRIX. This is useful for Legacy applications (older versions of @@ -2570,7 +2570,7 @@ TrueColor defdepth 24 Xsun, e.g. in your /etc/dt/config/Xservers file). - The -8to24 mode: The [431]-8to24 x11vnc option (Jan/2006) is a kludge + The -8to24 mode: The [433]-8to24 x11vnc option (Jan/2006) is a kludge to try to dynamically rewrite the pixel values so that the 8bpp part of the screen is mapped onto depth 24 TrueColor. This is less robust than the -overlay mode because it is done by x11vnc outside of the X @@ -2584,11 +2584,11 @@ TrueColor defdepth 24 32bpp view is exported via VNC. Even on pure 8bpp displays it can be used as an alternative to - [432]-flashcmap to avoid color flashing completely. + [434]-flashcmap to avoid color flashing completely. This scheme is approximate and can often lead to painting errors. You can manually correct most painting errors by pressing 3 Alt_L's in a - row, or by using something like: [433]-fixscreen V=3.0 to + row, or by using something like: [435]-fixscreen V=3.0 to automatically refresh the screen every 3 seconds. Also -fixscreen 8=3.0 has been added to just refresh the non-default visual parts of the screen. @@ -2601,23 +2601,23 @@ TrueColor defdepth 24 nogetimage can give a nice speedup if the default depth 24 X server supports hiding the 8bpp bits in bits 25-32 of the framebuffer data. On very slow machines -8to24 poll=0.2,cachewin=5.0 gives an useful - speedup. See the [434]-8to24 help description for information on + speedup. See the [436]-8to24 help description for information on tunable parameters, etc. Colors still not working correctly? Run xwininfo on the application with the incorrect colors to verify that the depth of its visual is different from the default visual depth (gotten from xdpyinfo). One - possible workaround in this case is to use the [435]-id option to + possible workaround in this case is to use the [437]-id option to point x11vnc at the application window itself. If the application is complicated (lots of toplevel windows and popup menus) this may not be acceptable, and may even crash x11vnc (but not the application). It is theoretically possible to solve this problem in general (see xwd(1) for example), but it does not seem trivial or sufficiently fast - for x11vnc to be able to do so in real time. The [436]-8to24 method + for x11vnc to be able to do so in real time. The [438]-8to24 method does this approximately and is somewhat usable. Fortunately the - [437]-overlay option works for Solaris machines with overlay visuals + [439]-overlay option works for Solaris machines with overlay visuals where most of this problem occurs. @@ -2653,9 +2653,9 @@ TrueColor defdepth 24 the desired application window. After clicking, it will print out much information, including the window id (e.g. 0x6000010). Also, the visual and depth of the window printed out is often useful in - debugging x11vnc [438]color problems. + debugging x11vnc [440]color problems. - Also, as of Dec/2004 you can use "[439]-id pick" to have x11vnc run + Also, as of Dec/2004 you can use "[441]-id pick" to have x11vnc run xwininfo(1) for you and after you click the window it extracts the windowid. Besides "pick" there is also "id:root" to allow you to go back to root window when doing remote-control. @@ -2673,7 +2673,7 @@ TrueColor defdepth 24 you should be able to see these transient windows. If things are not working and you still want to do the single window - polling, try the [440]-sid windowid option ("shifted" windowid). + polling, try the [442]-sid windowid option ("shifted" windowid). Q-26: My X display is depth 24 at 24bpp (instead of the normal depth @@ -2709,7 +2709,7 @@ TrueColor defdepth 24 handle 24bpp from the server, so you may want to use those. They evidently request 32 bpp and libvncserver obliges. - Update: as of Apr/2006 you can use the [441]-24to32 option to have + Update: as of Apr/2006 you can use the [443]-24to32 option to have x11vnc dynamically transform the 24bpp pixel data to 32bpp. This extra transformation could slow things down further however. @@ -2719,7 +2719,7 @@ TrueColor defdepth 24 couldn't find suitable pixmap format" so evidently you cannot use 24bpp for the vncviewers to work on that X display. - Note, however, that the Unix viewer in the [442]Enhanced TightVNC + Note, however, that the Unix viewer in the [444]Enhanced TightVNC Viewer (SSVNC) project can handle 24bpp X displays. It does this by requesting a 16bpp pixel format (or 8bpp if the -bgr233 option has been supplied) from the VNC server, and translates that to 24bpp @@ -2734,15 +2734,15 @@ TrueColor defdepth 24 since you will be polling the X display over the network as opposed to over the local hardware. To do this, run x11vnc on a UNIX machine as close as possible network-wise (e.g. same switch) to the Xterminal - machine. Use the [443]-display option to point the display to that of + machine. Use the [445]-display option to point the display to that of the Xterminal (you'll of course need basic X11 permission to do that) - and finally supply the [444]-noshm option (this enables the polling + and finally supply the [446]-noshm option (this enables the polling over the network). The response will likely be sluggish (maybe only one "frame" per second). This mode is not recommended except for "quick checks" of hard to get to X servers. Use something like "-wait 150" to cut down - on the polling rate. You may also need [445]-flipbyteorder if the + on the polling rate. You may also need [447]-flipbyteorder if the colors get messed up due to endian byte order differences. Q-28: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct @@ -2766,7 +2766,7 @@ TrueColor defdepth 24 copied to the Xterminal. If $HOME/.Xauthority is exported via NFS (this is insecure of course, but has been going on for decades), then x11vnc can simply pick it up via NFS (you may need to use the - [446]-auth option to point to the correct file). Other options include + [448]-auth option to point to the correct file). Other options include copying the auth file using scp, or something like: central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - @@ -2778,7 +2778,7 @@ TrueColor defdepth 24 details. If the display name in the cookie file needs to be changed between the - two hosts, see [447]this note on the "xauth add ..." command. + two hosts, see [449]this note on the "xauth add ..." command. A less secure option is to run something like "xhost +127.0.0.1" while sitting at the Xterminal box to allow cookie-free local access for @@ -2792,7 +2792,7 @@ TrueColor defdepth 24 occasional app more efficiently locally on the Xterminal box (e.g. realplayer). - Not recommended, but as a last resort, you could have x11vnc [448]poll + Not recommended, but as a last resort, you could have x11vnc [450]poll the Xterminal Display over the network. For this you would run a "x11vnc -noshm ..." process on the central-server (and hope the network admin doesn't get angry...) @@ -2821,34 +2821,34 @@ TrueColor defdepth 24 Q-29: I'm having trouble using x11vnc with my Sun Ray session. - The [449]Sun Ray technology is a bit like "VNC done in hardware" (the + The [451]Sun Ray technology is a bit like "VNC done in hardware" (the Sun Ray terminal device, DTU, playing the role of the vncviewer). Completely independent of that, the SunRay user's session is still an X server that speaks the X11 protocol and so x11vnc simply talks to the X server part to export the SunRay desktop to any place in the world (i.e. not only to a Sun Ray terminal device), creating a sort of - "Soft Ray". Please see [450]this discussion of Sun Ray issues for + "Soft Ray". Please see [452]this discussion of Sun Ray issues for solutions to problems. - Also see the [451]Sun Ray Remote Control Toolkit that uses x11vnc. + Also see the [453]Sun Ray Remote Control Toolkit that uses x11vnc. [Remote Control] Q-30: How do I stop x11vnc once it is running in the background? As of Dec/2004 there is a remote control feature. It can change a huge - number of parameters on the fly: see the [452]-remote and [453]-query + number of parameters on the fly: see the [454]-remote and [455]-query options. To shut down the running x11vnc server just type "x11vnc -R stop". To disconnect all clients do "x11vnc -R disconnect:all", etc. - If the [454]-forever option has not been supplied, x11vnc will + If the [456]-forever option has not been supplied, x11vnc will automatically exit after the first client disconnects. In general if you cannot use the remote control, then you will have to kill the x11vnc process This can be done via: "kill NNNNN" (where NNNNN is the x11vnc process id number found from ps(1)), or "pkill x11vnc", or "killall x11vnc" (Linux only). - If you have not put x11vnc in the background via the [455]-bg option + If you have not put x11vnc in the background via the [457]-bg option or shell & operator, then simply press Ctrl-C in the shell where x11vnc is running to stop it. @@ -2858,16 +2858,16 @@ TrueColor defdepth 24 down state in the Xserver. Tapping the stuck key (either via a new x11vnc or at the physical console) will release it from the stuck state. If the keyboard seems to be acting strangely it is often fixed - by tapping Ctrl, Shift, and Alt. Alternatively, the [456]-clear_mods - option and [457]-clear_keys option can be used to release pressed keys - at startup and exit. The option [458]-clear_all will also try to unset + by tapping Ctrl, Shift, and Alt. Alternatively, the [458]-clear_mods + option and [459]-clear_keys option can be used to release pressed keys + at startup and exit. The option [460]-clear_all will also try to unset Caps_Lock, Num_Lock, etc. Q-31: Can I change settings in x11vnc without having to restart it? Can I remote control it? - Look at the [459]-remote (an alias is -R) and [460]-query (an alias is + Look at the [461]-remote (an alias is -R) and [462]-query (an alias is -Q) options added in Dec/2004. They allow nearly everything to be changed dynamically and settings to be queried. Examples: "x11vnc -R shared", "x11vnc -R forever", "x11vnc -R scale:3/4", "x11vnc -Q @@ -2878,8 +2878,8 @@ TrueColor defdepth 24 property) is used as the communication channel, so the X permissions and DISPLAY must be set up correctly for communication to be possible. - There is also a simple Tcl/Tk [461]gui based on this remote control - mechanism. See the [462]-gui option for more info. You will need to + There is also a simple Tcl/Tk [463]gui based on this remote control + mechanism. See the [464]-gui option for more info. You will need to have Tcl/Tk (i.e. /usr/bin/wish) installed for it to work. It can also run in the system tray: "-gui tray" or as a standalone small icon window: "-gui icon". Use "-gui tray=setpass" for a naive user "Share @@ -2895,12 +2895,12 @@ TrueColor defdepth 24 vncpasswd(1) program from those packages. As of Jun/2004 x11vnc supports the -storepasswd "pass" "file" - [463]option, which is the same functionality of storepasswd. Be sure + [465]option, which is the same functionality of storepasswd. Be sure to quote the "pass" if it contains shell meta characters, spaces, etc. Example: x11vnc -storepasswd 'sword*fish' $HOME/myvncpasswd - You then use the password via the x11vnc option: "[464]-rfbauth + You then use the password via the x11vnc option: "[466]-rfbauth $HOME/myvncpasswd" As of Jan/2006 if you do not supply any arguments: @@ -2912,11 +2912,11 @@ TrueColor defdepth 24 ~/.mypass", the password you are prompted for will be stored in that file. - x11vnc also has the [465]-passwdfile and -passwd/-viewpasswd plain + x11vnc also has the [467]-passwdfile and -passwd/-viewpasswd plain text (i.e. not obscured like the -rfbauth VNC passwords) password options. - You can use the [466]-usepw option to automatically use any password + You can use the [468]-usepw option to automatically use any password file you have in ~/.vnc/passwd or ~/.vnc/passwdfile (the latter is used with the -passwdfile option). @@ -2948,14 +2948,14 @@ TrueColor defdepth 24 Q-34: Can I have two passwords for VNC viewers, one for full access and the other for view-only access to the display? - Yes, as of May/2004 there is the [467]-viewpasswd option to supply the - view-only password. Note the full-access password option [468]-passwd + Yes, as of May/2004 there is the [469]-viewpasswd option to supply the + view-only password. Note the full-access password option [470]-passwd must be supplied at the same time. E.g.: -passwd sword -viewpasswd fish. To avoid specifying the passwords on the command line (where they could be observed via the ps(1) command by any user) you can use the - [469]-passwdfile option to specify a file containing plain text + [471]-passwdfile option to specify a file containing plain text passwords. Presumably this file is readable only by you, and ideally it is located on the machine x11vnc is run on (to avoid being snooped on over the network). The first line of this file is the full-access @@ -2963,7 +2963,7 @@ TrueColor defdepth 24 it is taken as the view-only password. (use "__EMPTY__" to supply an empty one). - View-only passwords currently do not work for the [470]-rfbauth + View-only passwords currently do not work for the [472]-rfbauth password option (standard VNC password storing mechanism). FWIW, note that although the output (usually placed in $HOME/.vnc/passwd) by the vncpasswd or storepasswd programs (or from x11vnc -storepasswd) looks @@ -2976,7 +2976,7 @@ TrueColor defdepth 24 Q-35: Can I have as many full-access and view-only passwords as I like? - Yes, as of Jan/2006 in the libvncserver CVS the [471]-passwdfile + Yes, as of Jan/2006 in the libvncserver CVS the [473]-passwdfile option has been extended to handle as many passwords as you like. You put the view-only passwords after a line __BEGIN_VIEWONLY__. @@ -2986,7 +2986,7 @@ TrueColor defdepth 24 Q-36: Does x11vnc support Unix usernames and passwords? Can I further limit the set of Unix usernames who can connect to the VNC desktop? - Update: as of Feb/2006 x11vnc has the [472]-unixpw option that does + Update: as of Feb/2006 x11vnc has the [474]-unixpw option that does this outside of the VNC protocol and libvncserver. The standard su(1) program is used to validate the user's password. A familiar "login:" and "Password:" dialog is presented to the user on a black screen @@ -2996,7 +2996,7 @@ TrueColor defdepth 24 A list of allowed Unix usernames may also be supplied along with per-user settings. - There is also the [473]-unixpw_nis option for non-shadow-password + There is also the [475]-unixpw_nis option for non-shadow-password (typically NIS environments, hence the name) systems where the traditional getpwnam() and crypt() functions are used instead of su(1). The encrypted user passwords must be accessible to the user @@ -3005,11 +3005,11 @@ TrueColor defdepth 24 shadow(5). Two settings are enforced in the -unixpw and -unixpw_nis modes to - provide extra security: the 1) [474]-localhost and 2) [475]-stunnel or - [476]-ssl options. Without these one might send the Unix username and + provide extra security: the 1) [476]-localhost and 2) [477]-stunnel or + [478]-ssl options. Without these one might send the Unix username and password data in clear text over the network which is a very bad idea. They can be relaxed if you want to provide encryption other than - stunnel or [477]-ssl (the constraint is automatically relaxed if + stunnel or [479]-ssl (the constraint is automatically relaxed if SSH_CONNECTION is set and indicates you have ssh-ed in, however the -localhost requirement is still enforced). @@ -3028,13 +3028,13 @@ TrueColor defdepth 24 approximate at best. One approximate method involves starting x11vnc with the - [478]-localhost option. This basically requires the viewer user to log + [480]-localhost option. This basically requires the viewer user to log into the workstation where x11vnc is running via their Unix username and password, and then somehow set up a port redirection of his vncviewer connection to make it appear to emanate from the local machine. As discussed above, ssh is useful for this: "ssh -L 5900:localhost:5900 user@hostname ..." See the ssh wrapper scripts - mentioned [479]elsewhere on this page. [480]stunnel does this as well. + mentioned [481]elsewhere on this page. [482]stunnel does this as well. Of course a malicious user could allow other users to get in through his channel, but that is a problem with every method. Another thing to @@ -3045,7 +3045,7 @@ TrueColor defdepth 24 traditional way would be to further require a VNC password to supplied (-rfbauth, -passwd, etc) and only tell the people allowed in what the VNC password is. A scheme that avoids a second password involves using - the [481]-accept option that runs a program to examine the connection + the [483]-accept option that runs a program to examine the connection information to determine which user is connecting from the local machine. That may be difficult to do, but, for example, the program could use the ident service on the local machine (normally ident @@ -3081,7 +3081,7 @@ exit 1 # reject it method (e.g. Dynamic/One-time passwords or non-Unix (LDAP) usernames and passwords)? Yes, there are several possibilities. For background see the FAQ on - the [482]-accept where an external program may be run to decide if a + the [484]-accept where an external program may be run to decide if a VNC client should be allowed to try to connect and log in. If the program (or local user prompted by a popup) answers "yes", then -accept proceeds to the normal VNC and x11vnc authentication methods, @@ -3089,26 +3089,26 @@ exit 1 # reject it To provide more direct coupling to the VNC client's username and/or supplied password the following options were added in Sep/2006: - * [483]-unixpw_cmd command - * [484]-passwdfile cmd:command - * [485]-passwdfile custom:command + * [485]-unixpw_cmd command + * [486]-passwdfile cmd:command + * [487]-passwdfile custom:command In each case "command" is an external command run by x11vnc. You supply it. For example, it may couple to your LDAP system or other servers you set up. - For [486]-unixpw_cmd the normal [487]-unixpw Login: and Password: + For [488]-unixpw_cmd the normal [489]-unixpw Login: and Password: prompts are supplied to the VNC viewer and the strings the client returns are then piped into "command" as the first two lines of its standard input. If the command returns success, i.e. exit(0), the VNC client is accepted, otherwise it is rejected. - For "[488]-passwdfile cmd:command" the command is run and it returns a - password list (like a password file, see the [489]-passwdfile + For "[490]-passwdfile cmd:command" the command is run and it returns a + password list (like a password file, see the [491]-passwdfile read:filename mode). Perhaps a dynamic, one-time password is retrieved from a server this way. - For "[490]-passwdfile custom:command" one gets complete control over + For "[492]-passwdfile custom:command" one gets complete control over the VNC challenge-response dialog with the VNC client. x11vnc sends out a string of random bytes (16 by the VNC spec) and the client returns the same number of bytes in a way the server can verify only @@ -3122,7 +3122,7 @@ exit 1 # reject it accepted, otherwise it is rejected. In all cases the "RFB_*" environment variables are set as under - [491]-accept. These variables can provide useful information for the + [493]-accept. These variables can provide useful information for the externally supplied program to use. @@ -3132,15 +3132,15 @@ exit 1 # reject it These defaults are simple safety measures to avoid someone unknowingly leaving his X11 desktop exposed (to the internet, say) for long - periods of time. Use the [492]-forever option (aka -many) to have + periods of time. Use the [494]-forever option (aka -many) to have x11vnc wait for more connections after the first client disconnects. - Use the [493]-shared option to have x11vnc allow multiple clients to + Use the [495]-shared option to have x11vnc allow multiple clients to connect simultaneously. - Recommended additional safety measures include using ssh ([494]see - above), stunnel, [495]-ssl, or a VPN to authenticate and encrypt the + Recommended additional safety measures include using ssh ([496]see + above), stunnel, [497]-ssl, or a VPN to authenticate and encrypt the viewer connections or to at least use the -rfbauth passwd-file - [496]option to use VNC password protection (or [497]-passwdfile) It is + [498]option to use VNC password protection (or [499]-passwdfile) It is up to YOU to apply these security measures, they will not be done for you automatically. @@ -3148,7 +3148,7 @@ exit 1 # reject it Q-39: Can I limit which machines incoming VNC clients can connect from? - Yes, look at the [498]-allow and [499]-localhost options to limit + Yes, look at the [500]-allow and [501]-localhost options to limit connections by hostname or IP address. E.g. x11vnc -allow 192.168.0.1,192.168.0.2 @@ -3160,7 +3160,7 @@ exit 1 # reject it Note that -localhost achieves the same thing as "-allow 127.0.0.1" For more control, build libvncserver with libwrap support - [500](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) + [502](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) for complete details. @@ -3180,7 +3180,7 @@ exit 1 # reject it is "vnc", e.g.: vnc: 192.168.100.3 .example.com - Note that if you run x11vnc out of [501]inetd you do not need to build + Note that if you run x11vnc out of [503]inetd you do not need to build x11vnc with libwrap support because the /usr/sbin/tcpd reference in /etc/inetd.conf handles the tcp_wrappers stuff. @@ -3189,15 +3189,15 @@ exit 1 # reject it internal LAN) rather than having it listen on all network interfaces and relying on -allow to filter unwanted connections out? - As of Mar/2005 there is the "[502]-listen ipaddr" option that enables + As of Mar/2005 there is the "[504]-listen ipaddr" option that enables this. For ipaddr either supply the desired network interface's IP address (or use a hostname that resolves to it) or use the string "localhost". For additional filtering simultaneously use the - "[503]-allow host1,..." option to allow only specific hosts in. + "[505]-allow host1,..." option to allow only specific hosts in. This option is useful if you want to insure that no one can even begin a dialog with x11vnc from untrusted network interfaces (e.g. ppp0). - The option [504]-localhost now implies "-listen localhost" since that + The option [506]-localhost now implies "-listen localhost" since that is what most people expect it to do. @@ -3205,7 +3205,7 @@ exit 1 # reject it interface, how I can occasionally allow in a non-localhost via the -R allowonce remote control command? - To do this specify "[505]-allow localhost". Unlike [506]-localhost + To do this specify "[507]-allow localhost". Unlike [508]-localhost this will leave x11vnc listening on all interfaces (but of course only allowing in local connections, e.g. ssh redirs). Then you can later run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot @@ -3216,7 +3216,7 @@ exit 1 # reject it some users just be able to move the mouse, but not click or type anything? - As of Feb/2005, the [507]-input option allows you to do this. "K", + As of Feb/2005, the [509]-input option allows you to do this. "K", "M", "B", "C", and "F" stand for Keystroke, Mouse-motion, Button-clicks, Clipboard, and File-Transfer, respectively. The setting: "-input M" makes attached viewers only able to move the @@ -3232,7 +3232,7 @@ exit 1 # reject it some clients view-only? How about running an arbitrary program to make the decisions? - Yes, look at the "[508]-accept command" option, it allows you to + Yes, look at the "[510]-accept command" option, it allows you to specify an external command that is run for each new client. (use quotes around the command if it contains spaces, etc.). If the external command returns 0 (success) the client is accepted, otherwise @@ -3253,7 +3253,7 @@ exit 1 # reject it client press "y" or click mouse on the "Yes" button. To reject the client press "n" or click mouse on the "No" button. To accept the client View-only, press "v" or click mouse on the "View" button. If - the [509]-viewonly option has been supplied, the "View" action will + the [511]-viewonly option has been supplied, the "View" action will not be present: the whole display is view only in that case. The popup window times out after 120 seconds, to change this behavior @@ -3268,7 +3268,7 @@ exit 1 # reject it program to prompt the user whether the client should be accepted or not. This requires that you have xmessage installed and available via PATH. In case it is not already on your system, the xmessage program - is available at [510]ftp://ftp.x.org/ + is available at [512]ftp://ftp.x.org/ (End of Built-in Popup Window:) To include view-only decisions for the external commands, prefix the @@ -3308,7 +3308,7 @@ elif [ $rc = 4 ]; then fi exit 1 - Stefan Radman has written a nice dtksh script [511]dtVncPopup for use + Stefan Radman has written a nice dtksh script [513]dtVncPopup for use in CDE environments to do the same sort of thing. Information on how to use it is found at the top of the file. He encourages you to provide feedback to him to help improve the script. @@ -3317,13 +3317,13 @@ exit 1 popup is being run, so attached clients will not receive screen updates, etc during this period. - To run a command when a client disconnects, use the "[512]-gone + To run a command when a client disconnects, use the "[514]-gone command" option. This is for the user's convenience only: the return code of the command is not interpreted by x11vnc. The same environment variables are set as in "-accept command" (except that RFB_MODE will be "gone"). - As of Jan/2006 the "[513]-afteraccept command" option will run the + As of Jan/2006 the "[515]-afteraccept command" option will run the command only after the VNC client has been accepted and authenticated. Like -gone the return code is not interpreted. RFB_MODE will be "afteraccept"). @@ -3333,7 +3333,7 @@ exit 1 display manager like gdm(1). Can I have x11vnc later switch to a different user? - As of Feb/2005 x11vnc has the [514]-users option that allows things + As of Feb/2005 x11vnc has the [516]-users option that allows things like this. Please read the documentation on it (also in the x11vnc -help output) carefully for features and caveats. It's use can often decrease security unless care is taken. @@ -3358,7 +3358,7 @@ exit 1 In any event, as of Jun/2004 there is an experimental utility to make it more difficult for nosey people to see your x11vnc activities. The - source for it is [515]blockdpy.c The idea behind it is simple (but + source for it is [517]blockdpy.c The idea behind it is simple (but obviously not bulletproof): when a VNC client attaches to x11vnc put the display monitor in the DPMS "off" state, if the DPMS state ever changes immediately start up the screen-lock program. The x11vnc user @@ -3374,8 +3374,8 @@ exit 1 bulletproof. A really robust solution would likely require X server and perhaps even video hardware support. - The blockdpy utility is launched by the [516]-accept option and told - to exit via the [517]-gone option (the vnc client user should + The blockdpy utility is launched by the [518]-accept option and told + to exit via the [519]-gone option (the vnc client user should obviously re-lock the screen before disconnecting!). Instructions can be found in the source code for the utility at the above link. Roughly it is something like this: @@ -3384,17 +3384,17 @@ exit 1 but please read the top of the file. Update: As of Feb/2007 there is some builtin support for this: - [518]-forcedpms and [519]-clientdpms however, they are probably less + [520]-forcedpms and [521]-clientdpms however, they are probably less robust than the above blockdpy.c scheme, since if the person floods the physical machine with mouse or pointer input he can usually see flashes of the screen before the monitor is powered off again. See - also the [520]-grabkbd, [521]-grabptr, and [522]-grabalways options. + also the [522]-grabkbd, [523]-grabptr, and [524]-grabalways options. Q-47: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? - Yes, a user mentions he uses the [523]-gone option under CDE to run a + Yes, a user mentions he uses the [525]-gone option under CDE to run a screen lock program: x11vnc -display :0 -forever -gone 'dtaction LockDisplay' @@ -3404,7 +3404,7 @@ exit 1 x11vnc -display :0 -forever -gone 'xlock &' x11vnc -display :0 -forever -gone 'xlock -mode blank &' - Here is a scheme using the [524]-afteraccept option (in version 0.8) + Here is a scheme using the [526]-afteraccept option (in version 0.8) to unlock the screen after the first valid VNC login and to lock the screen after the last valid VNC login disconnects: x11vnc -display :0 -forever -shared -afteraccept ./myxlocker -gone ./myxlocke @@ -3445,21 +3445,21 @@ exec @ARGV; Q-48: How can I tunnel my connection to x11vnc via an encrypted SSH channel between two Unix machines? - See the description earlier on this page on [525]how to tunnel VNC via + See the description earlier on this page on [527]how to tunnel VNC via SSH from Unix to Unix. A number of ways are described along with some issues you may encounter. Other secure encrypted methods exists, e.g. stunnel, IPSEC, various VPNs, etc. - See also the [526]Enhanced TightVNC Viewer (SSVNC) page where much of + See also the [528]Enhanced TightVNC Viewer (SSVNC) page where much of this is now automated. Q-49: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [527]Above we described how to tunnel VNC via SSH from Unix to Unix, + [529]Above we described how to tunnel VNC via SSH from Unix to Unix, you may want to review it. To do this from Windows using Putty it would go something like this: * In the Putty dialog window under 'Session' enter the hostname or @@ -3480,11 +3480,11 @@ exec @ARGV; :0 (plus other cmdline options) in the 'Remote command' Putty setting under 'Connections/SSH'. - See also the [528]Enhanced TightVNC Viewer (SSVNC) page where much of + See also the [530]Enhanced TightVNC Viewer (SSVNC) page where much of this is now automated via the Putty plink utility. - For extra protection feel free to run x11vnc with the [529]-localhost - and [530]-rfbauth/[531]-passwdfile options. + For extra protection feel free to run x11vnc with the [531]-localhost + and [532]-rfbauth/[533]-passwdfile options. If the machine you SSH into via Putty is not the same machine with the X display you wish to view (e.g. your company provides incoming SSH @@ -3492,11 +3492,11 @@ exec @ARGV; dialog setting to: 'Destination: otherhost:5900', Once logged in, you'll need to do a second login (ssh or rsh) to the workstation machine 'otherhost' and then start up x11vnc on it. This can also be - automated by [532]Chaining SSH's. + automated by [534]Chaining SSH's. - As discussed [533]above another option is to first start the VNC + As discussed [535]above another option is to first start the VNC viewer in "listen" mode, and then launch x11vnc with the - "[534]-connect localhost" option to establish the reverse connection. + "[536]-connect localhost" option to establish the reverse connection. In this case a Remote port redirection (not Local) is needed for port 5500 instead of 5900 (i.e. 'Source port: 5500' and 'Destination: localhost:5500' for a Remote connection). @@ -3506,7 +3506,7 @@ exec @ARGV; channel using an external tool like stunnel? It is possible to use a "lighter weight" encryption setup than SSH or - IPSEC. SSL tunnels such as [535]stunnel (also [536]stunnel.mirt.net) + IPSEC. SSL tunnels such as [537]stunnel (also [538]stunnel.mirt.net) provide an encrypted channel without the need for Unix users, passwords, and key passphrases required for ssh (and at the other extreme SSL can also provide a complete signed certificate chain of @@ -3514,12 +3514,12 @@ exec @ARGV; often let its port through, ssh is frequently the path of least resistance (it also nicely manages public keys for you). - Update: As of Feb/2006 x11vnc has the options [537]-ssl, - [538]-stunnel, and [539]-sslverify to provide integrated SSL schemes. - They are discussed [540]in the Next FAQ (you may want to skip to it + Update: As of Feb/2006 x11vnc has the options [539]-ssl, + [540]-stunnel, and [541]-sslverify to provide integrated SSL schemes. + They are discussed [542]in the Next FAQ (you may want to skip to it now). - Here are some basic examples using [541]stunnel but the general idea + Here are some basic examples using [543]stunnel but the general idea for any SSL tunnel utility is the same: * Start up x11vnc and constrain it to listen on localhost. * Then start up the SSL tunnel running on the same machine to @@ -3543,7 +3543,7 @@ exec @ARGV; The above two commands are run on host "far-away.east". The stunnel.pem is the self-signed PEM file certificate created when - stunnel is built. One can also create certificates [542]signed by + stunnel is built. One can also create certificates [544]signed by Certificate Authorities or self-signed if desired using the x11vnc utilities described there. @@ -3557,21 +3557,21 @@ exec @ARGV; Then point the viewer to the local tunnel on port 5902: vncviewer -encodings "copyrect tight zrle hextile" localhost:2 - That's it. Note that the [543]ss_vncviewer script can automate this - easily, and so can the [544]Enhanced TightVNC Viewer (SSVNC) package. + That's it. Note that the [545]ss_vncviewer script can automate this + easily, and so can the [546]Enhanced TightVNC Viewer (SSVNC) package. Be sure to use a VNC password because unlike ssh by default the encrypted SSL channel provides no authentication (only privacy). With some extra configuration one could also set up certificates to provide authentication of either or both sides as well (and hence avoid man-in-the-middle attacks). See the stunnel and openssl documentation - and also [545]the key management section for details. + and also [547]the key management section for details. stunnel has also been ported to Windows, and there are likely others to choose from for that OS. Much info for using it on Windows can be - found at the stunnel site and in this [546]article The article also + found at the stunnel site and in this [548]article The article also shows the detailed steps to set up all the authentication - certificates. (for both server and clients, see also the [547]x11vnc + certificates. (for both server and clients, see also the [549]x11vnc utilities that do this). The default Windows client setup (no certs) is simpler and only 4 files are needed in a folder: stunnel.exe, stunnel.conf, libssl32.dll, libeay32.dll. We used an stunnel.conf @@ -3592,7 +3592,7 @@ connect = far-away.east:5901 As an aside, if you don't like the little "gap" of unencrypted TCP traffic (and a localhost listening socket) on the local machine between stunnel and x11vnc it can actually be closed by having stunnel - start up x11vnc in [548]-inetd mode: + start up x11vnc in [550]-inetd mode: stunnel -p /path/to/stunnel.pem -P none -d 5900 -l ./x11vnc_sh Where the script x11vnc_sh starts up x11vnc: @@ -3630,28 +3630,28 @@ connect = 5900 Regarding VNC viewers that "natively" do SSL unfortunately there do not seem to be many. UltraVNC has an encryption plugin, but we have - not tried it (it does not seem to be SSL, however the [549]SingleClick - UltraVNC Java Viewer is SSL and is compatible with x11vnc's [550]-ssl + not tried it (it does not seem to be SSL, however the [551]SingleClick + UltraVNC Java Viewer is SSL and is compatible with x11vnc's [552]-ssl option and stunnel.) Commercial versions of VNC seem to have some SSL built in, but we haven't tried those either and they probably wouldn't work since the SSL negotiation is likely embedded in the VNC protocol unlike our case where it is external. - Note: as of Mar/2006 libvncserver/x11vnc provides a [551]SSL-enabled - Java applet that can be served up via the [552]-httpdir or [553]-http - options when [554]-ssl is enabled. It will also be served via HTTPS + Note: as of Mar/2006 libvncserver/x11vnc provides a [553]SSL-enabled + Java applet that can be served up via the [554]-httpdir or [555]-http + options when [556]-ssl is enabled. It will also be served via HTTPS via either the VNC port (e.g. https://host:5900/) or a 2nd port via - the [555]-https option. + the [557]-https option. In general current SSL VNC solutions are not particularly "seemless". But it can be done, and with a wrapper script on the viewer side and - the [556]-stunnel or [557]-ssl option on the server side it works well - and is convenient. Here is a simple script [558]ss_vncviewer that + the [558]-stunnel or [559]-ssl option on the server side it works well + and is convenient. Here is a simple script [560]ss_vncviewer that automates running stunnel on the VNC viewer side on Unix a little more carefully than the commands printed above. (One could probably do a similar thing with a .BAT file on Windows in the stunnel folder.) - Update Jul/2006: we now provide an [559]Enhanced TightVNC Viewer + Update Jul/2006: we now provide an [561]Enhanced TightVNC Viewer (SSVNC) package that starts up STUNNEL automatically along with some other features. All binaries (stunnel, vncviewer, and some utilities) are provided in the package. It works on Unix, Mac OS X, and Windows. @@ -3659,7 +3659,7 @@ connect = 5900 Q-51: Does x11vnc have built-in SSL tunneling? - You can read about non-built-in methods [560]in the Previous FAQ for + You can read about non-built-in methods [562]in the Previous FAQ for background. SSL tunnels provide an encrypted channel without the need for Unix @@ -3671,14 +3671,14 @@ connect = 5900 Built-in SSL x11vnc options: - As of Feb/2006 the x11vnc [561]-ssl and [562]-stunnel options automate - the SSL tunnel creation on the x11vnc server side. An [563]SSL-enabled + As of Feb/2006 the x11vnc [563]-ssl and [564]-stunnel options automate + the SSL tunnel creation on the x11vnc server side. An [565]SSL-enabled Java Viewer applet is also provided that can be served via HTTP or HTTPS to automate SSL on the client side. - The [564]-ssl mode uses the [565]www.openssl.org library if available - at build time. The [566]-stunnel mode requires the - [567]www.stunnel.org command stunnel(8) to be installed on the system. + The [566]-ssl mode uses the [567]www.openssl.org library if available + at build time. The [568]-stunnel mode requires the + [569]www.stunnel.org command stunnel(8) to be installed on the system. Both modes require an SSL certificate and key (i.e. .pem file). These are usually created via the openssl(1) program (in fact in for options @@ -3721,7 +3721,7 @@ connect = 5900 SSL VNC Viewers:. Viewer-side will need to use SSL as well. See the - [568]next FAQ and [569]here for SSL enabled VNC Viewers to connect to + [570]next FAQ and [571]here for SSL enabled VNC Viewers to connect to the above x11vnc via SSL. @@ -3737,12 +3737,12 @@ connect = 5900 is to encrypt the key with a passphrase (note however this requires supplying the passphrase each time x11vnc is started up). - See the discussion on [570]x11vnc Key Management for some utilities + See the discussion on [572]x11vnc Key Management for some utilities provided for creating and managing certificates and keys and even for creating your own Certificate Authority (CA) for signing VNC server and client certificates. This may be done by importing the certificate into Web Browser or Java plugin keystores, or pointing stunnel to it. - The wrapper script [571]ss_vncviewer provides an example on unix + The wrapper script [573]ss_vncviewer provides an example on unix (-verify option). Here are some notes on the simpler default (non-CA) operation. To have @@ -3758,7 +3758,7 @@ connect = 5900 to machines where the VNC Viewer will be run to enable authenticating the x11vnc SSL VNC server to the clients. When authentication takes place this way (or via the more sophisticated CA signing described - [572]here), then Man-In-The-Middle-Attacks are prevented. Otherwise, + [574]here), then Man-In-The-Middle-Attacks are prevented. Otherwise, the SSL encryption only provides protection against passive network traffic "sniffing" (i.e. you are not protected agains M-I-T-M attacks). Nowadays, most people seem mostly concerned mainly about @@ -3793,12 +3793,12 @@ connect = 5900 There aren't any native VNC Viewers that do SSL (ask your VNC viewer developer to add the feature). So a tunnel must be setup that you point the VNC Viewer to. This is often STUNNEL. You can do this - [573]manually, or use the [574]ss_vncviewer script on Unix, or the - [575]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or + [575]manually, or use the [576]ss_vncviewer script on Unix, or the + [577]Enhanced TightVNC Viewer (SSVNC) package on Unix, Windows, or MacOSX. See the next section for Java Web browser SSL VNC Viewers (you only need a Java-enabled Web browser for it to work). - Notes on the SSL enabled Java VNC Viewer provided in + Notes on the SSL enabled Java VNC Viewer provided in x11vnc classes/ssl/VncViewer.jar: A Java applet VNC Viewer allows you to connect to a VNC Server from a @@ -3806,13 +3806,13 @@ connect = 5900 The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package supports only SSL based connections by default. As mentioned above the - [576]-httpdir can be used to specify the path to .../classes/ssl. A + [578]-httpdir can be used to specify the path to .../classes/ssl. A typical location might be /usr/local/share/x11vnc/classes/ssl. Or - [577]-http can be used to try to have it find the directory + [579]-http can be used to try to have it find the directory automatically. - Also note that the [578]SingleClick UltraVNC Java Viewer is compatible - with x11vnc's [579]-ssl SSL mode. (We tested it this way: "java -cp + Also note that the [580]SingleClick UltraVNC Java Viewer is compatible + with x11vnc's [581]-ssl SSL mode. (We tested it this way: "java -cp ./VncViewer.jar VncViewer HOST far-away.east PORT 5900 USESSL 1 TRUSTALL 1") @@ -3839,13 +3839,17 @@ connect = 5900 or: https://far-away.east:5900/ - into your Java-enabled Web browser: + into your Java-enabled Web browser. + + If you are using a router/firewall with port-redirection, and you are + redirecting ports other than the default ones (5800, 5900) listed + above [582]see here. The https service provided thru the actual VNC port (5900 in the above example) can occasionally be slow or unreliable (it has to read some input and try to guess if the connection is VNC or HTTP). If it is unreliable for you and you still want to serve the Java applet via - https, use the [580]-https option to get an additional port dedicated + https, use the [583]-https option to get an additional port dedicated to https (its URL will also be printed in the output). Another possibility is to add the GET applet parameter: @@ -3858,7 +3862,7 @@ connect = 5900 You may also use "urlPrefix=somestring" to have /somestring prepended to /request.https.vnc.connection". Perhaps you are using a web server - [581]proxy scheme to enter a firewall or otherwise have rules applied + [584]proxy scheme to enter a firewall or otherwise have rules applied to the URL. If you need to have any slashes "/" in "somestring" use "_2F_" (a deficiency in libvncserver prevents using the more natural "%2F".) @@ -3948,12 +3952,12 @@ connect = 5900 Then, if you plan to use them, enable "fancy stuff" like "-svc" or "-unixpw", etc, etc. Be sure to add a password either "-rfbauth" or "-unixpw" or both. If you need to have the web browser use a corporate - [582]Web Proxy (i.e. it cannot connect directly) work on that last. - Ditto for the [583]Apache portal. + [585]Web Proxy (i.e. it cannot connect directly) work on that last. + Ditto for the [586]Apache portal. Router/Firewall port redirs: If you are doing port redirection at - your [584]router to an internal machine running x11vnc AND the + your [587]router to an internal machine running x11vnc AND the internet facing port is different from the internal machine's VNC port, you will need to apply the PORT applet parameter to indicate to the applet the Internet facing port number (otherwise by default the @@ -3963,7 +3967,7 @@ connect = 5900 So in this example the user configures his router to redirect connections to port 443 on his Internet side to, say, port 5900 on the - internal machine running x11vnc. See also the [585]-httpsredir option + internal machine running x11vnc. See also the [588]-httpsredir option that will try to automate this for you. To configure your router to do port redirection, see its instructions. @@ -3974,6 +3978,10 @@ connect = 5900 or Unix system acting as your firewall/router, see its firewall configuration. + You can also use x11vnc options [589]-rfbport NNNNN and [590]-httpport + NNNNN to match the ports that your firewall will be redirecting to the + machine where x11vnc is run. + Tedious Dialogs: If you do serve the SSL enabled Java viewer via https be prepared for quite a number of "are you sure you trust this site?" @@ -3999,11 +4007,11 @@ connect = 5900 NOT linger at. If you see in the x11vnc output a request for VncViewer.class instead of VncViewer.jar it is too late... you may need to restart the Web browser to get it to try for the jar again. - You can use the [586]-https option if you want a dedicated port for + You can use the [591]-https option if you want a dedicated port for HTTPS connections instead of sharing the VNC port. To see example x11vnc output for a successful https://host:5900/ - connection with the Java Applet see [587]This Page. + connection with the Java Applet see [592]This Page. Notes on the VNC Viewer ss_vncviewer wrapper script: @@ -4011,10 +4019,10 @@ connect = 5900 If you want to use a native VNC Viewer with the SSL enabled x11vnc you will need to run an external SSL tunnel on the Viewer side. There do not seem to be any native SSL VNC Viewers outside of our x11vnc and - [588]SSVNC packages. The basic ideas of doing this were discussed - [589]for external tunnel utilities here. + [593]SSVNC packages. The basic ideas of doing this were discussed + [594]for external tunnel utilities here. - The [590]ss_vncviewer script provided with x11vnc and SSVNC can set up + The [595]ss_vncviewer script provided with x11vnc and SSVNC can set up the stunnel tunnel automatically on unix as long as the stunnel command is installed on the Viewer machine and available in PATH (and vncviewer too of course). Note that on a Debian based system you will @@ -4046,14 +4054,14 @@ connect = 5900 The fifth one shows that Web proxies can be used if that is the only way to get out of the firewall. If the "double proxy" situation arises - separate the two by commas. See [591]this page for more information on + separate the two by commas. See [596]this page for more information on how Web proxies come into play. - If one uses a Certificate Authority (CA) scheme described [592]here, + If one uses a Certificate Authority (CA) scheme described [597]here, the wrapper script would use the CA cert instead of the server cert: 3') ss_vncviewer -verify ./cacert.crt far-away.east:0 - Update Jul/2006: we now provide an [593]Enhanced TightVNC Viewer + Update Jul/2006: we now provide an [598]Enhanced TightVNC Viewer (SSVNC) package that starts up STUNNEL automatically along with some other features. All binaries (stunnel, vncviewer, and some utilities) are provided in the package. It works on Unix, Mac OS X, and Windows. @@ -4116,14 +4124,14 @@ connect = 5900 https://yourmachine.com/proxy.vnc?PORT=443 this is cleaner because it avoids editing the file, but requires more - parameters in the URL. See also the [594]-httpsredir option that will - try to automate this for you. To use the GET [595]trick discussed + parameters in the URL. See also the [599]-httpsredir option that will + try to automate this for you. To use the GET [600]trick discussed above, do: https://yourmachine.com/proxy.vnc?GET=1&PORT=443 - Note that both the [596]ss_vncviewer stunnel Unix wrapper script and - [597]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even + Note that both the [601]ss_vncviewer stunnel Unix wrapper script and + [602]Enhanced TightVNC Viewer (SSVNC) can use Web proxies as well even though they do not involve a Web browser. @@ -4131,7 +4139,7 @@ connect = 5900 SSL from the Internet with a Web browser to x11vnc running on their workstations behind a firewall? Yes. You will need to configure apache to forward these connections. - It is discussed [598]here. This provides a clean alternative to the + It is discussed [603]here. This provides a clean alternative to the traditional method where the user uses SSH to log in through the gateway to create the encrypted port redirection to x11vnc running on her desktop. @@ -4139,7 +4147,7 @@ connect = 5900 Q-55: Can I create and use my own SSL Certificate Authority (CA) with x11vnc? - Yes, see [599]this page for how to do this and the utility commands + Yes, see [604]this page for how to do this and the utility commands x11vnc provides to create and manage many types of certificates and private keys. @@ -4158,14 +4166,14 @@ connect = 5900 need to have sufficient permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [600]FAQ on x11vnc + * Use the description under "Continuously" in the [605]FAQ on x11vnc and Display Managers - * Use the description in the [601]FAQ on x11vnc and inetd(8) - * Use the description in the [602]FAQ on Unix user logins and + * Use the description in the [606]FAQ on x11vnc and inetd(8) + * Use the description in the [607]FAQ on Unix user logins and inetd(8) * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc or autostart script or ...) - * Although less reliable, see the [603]x11vnc_loop rc.local hack + * Although less reliable, see the [608]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the @@ -4187,9 +4195,9 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg X startup scripts (traditionally .xsession/.xinitrc) may have to be in a different directory or have a different basename. One user recommends the description under 'Running Scripts Automatically' at - [604]this link. + [609]this link. - Firewalls: note all methods will require the host-level [605]firewall + Firewalls: note all methods will require the host-level [610]firewall to be configured to allow connections in on a port. E.g. 5900 (default VNC port) or 22 (default SSH port for tunnelling VNC). Most systems these days have firewalls turned on by default, so you will actively @@ -4201,6 +4209,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg Q-57: How can I use x11vnc to connect to an X login screen like xdm, GNOME gdm, KDE kdm, or CDE dtlogin? (i.e. nobody is logged into an X session yet). + _________________________________________________________________ One time only: If the X login screen is running and you just want to connect to it once (i.e. a one-shot): @@ -4210,17 +4219,18 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg while running x11vnc as root, e.g. for the gnome display manager, gdm: x11vnc -auth /var/gdm/:0.Xauth -display :0 - (the [606]-auth option sets the XAUTHORITY variable for you). + (the [611]-auth option sets the XAUTHORITY variable for you). There will be a similar thing for xdm using however a different auth directory path (perhaps something like /var/lib/xdm/authdir/authfiles/A:0-XQvaJk for xdm or - /var/lib/kdm/A:0-crWk72 for kdm, where the random characters in - basename will vary a bit). Read your system docs to find out where the - display manager cookie files are kept. + /var/lib/kdm/A:0-crWk72 (or /var/run/xauth/A:0-qQPftr, etc. etc) for + kdm, where the random characters in the basename will vary). Read your + system docs to find out where the display manager cookie files are + kept. Trick: sometimes ps(1) can reveal the X server process -auth argument - (e.g. "ps wwwwaux | grep auth"). + (e.g. "ps wwwwaux | grep auth") and hence the path to the auth file. You next connect to x11vnc with a VNC viewer, give your username and password to the X login prompt to start your session. @@ -4237,8 +4247,9 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg (BTW, the auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see - [607]the example at the end of this FAQ). Then restart dtlogin, e.g.: + [612]the example at the end of this FAQ). Then restart dtlogin, e.g.: /etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot. + _________________________________________________________________ Continuously: Have x11vnc reattach each time the X server is restarted (i.e. after each logout): @@ -4247,16 +4258,17 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg screen you will need to add a command to a display manager startup script. - Please consider the security implications of this! Besides having the - VNC display for the X session always accessible (but hopefully - password protected), there may other issues. + Please consider the security implications of this! The VNC display for + the X session always accessible (but hopefully password protected). + Add [613]-localhost if you only plan to access via a [614]SSH tunnel. The name of the display manager startup script file depends on desktop used and seem to be: - GNOME /etc/X11/gdm/Init/Default (or Init/:0) - KDE /etc/kde*/kdm/Xsetup - XDM /etc/X11/xdm/Xsetup (or xdm/Xsetup_0) - CDE /etc/dt/config/Xsetup + GDM (GNOME) /etc/X11/gdm/Init/Default (or sometimes Init/:0) + /etc/gdm/Init/Default + KDM (KDE) /etc/kde*/kdm/Xsetup + XDM /etc/X11/xdm/Xsetup (or sometimes xdm/Xsetup_0) + CDE /etc/dt/config/Xsetup although the exact location can depend on operating system and distribution. See the documentation for your display manager: gdm(1), @@ -4264,27 +4276,29 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg display number specific scripts: e.g. Xsetup_0 vs. Xsetup, you need to watch out for. - Note: The above gdm setting of KillInitClients=false in - /etc/X11/gdm/gdm.conf (or /etc/gdm/gdm.conf, etc.) for GDM is needed - here as well. Other display managers (KDM, etc) may also have a - similar problem. + Note: The above (in 'One time only') gdm setting of + KillInitClients=false in /etc/X11/gdm/gdm.conf (or /etc/gdm/gdm.conf, + etc.) for GDM is needed here as well. Other display managers (KDM, + etc) may also have a similar problem. - Note: The above Dtlogin*grabServer:False step for Solaris will be - needed for dtlogin here as well. + Note: The above (in 'One time only') Dtlogin*grabServer:False step + for Solaris will be needed for dtlogin here as well. In any event, the line you will add to the display manager script - (Xsetup or whatever) will look something like: + (Xsetup, Default, or whatever) will look something like: /usr/local/bin/x11vnc -rfbauth /path/to/the/vnc/passwd -o /var/log/x11vnc.log -forever -bg - where you should customize the exact command to your needs. + where you should customize the exact command to your needs (e.g. + [615]-localhost for SSH tunnel-only access; [616]-ssl SAVE for SSL + access; etc.) Happy, happy, joy, joy: Note that we do not need to specify -display or -auth because happily they are already set for us in the DISPLAY and XAUTHORITY environment variables for the Xsetup script!!! You may also want to force the VNC port with something like "-rfbport - 5900" (or [608]-N) to avoid autoselecting one if 5900 is already + 5900" (or [617]-N) to avoid autoselecting one if 5900 is already taken. _________________________________________________________________ @@ -4300,7 +4314,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg Then restart: /usr/sbin/gdm-restart (or reboot). The KillInitClients=false setting is important: without it x11vnc will be - killed immediately after the user logs in. Here are [609]full details + killed immediately after the user logs in. Here are [618]full details on how to configure gdm _________________________________________________________________ @@ -4342,16 +4356,16 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg If you do not want to deal with any display manager startup scripts, here is a kludgey script that can be run manually or out of a boot - file like rc.local: [610]x11vnc_loop It will need some local + file like rc.local: [619]x11vnc_loop It will need some local customization before running. Because the XAUTHORITY auth file must be guessed by this script, use of the display manager script method - described above is greatly preferred. There is also the [611]-loop + described above is greatly preferred. There is also the [620]-loop option that does something similar. If the machine is a traditional Xterminal you may want to read - [612]this FAQ. + [621]this FAQ. - Firewalls: note all methods will require the host-level [613]firewall + Firewalls: note all methods will require the host-level [622]firewall to be configured to allow connections in on a port. E.g. 5900 (default VNC port) or 22 (default SSH port for tunnelling VNC). Most systems these days have firewalls turned on by default, so you will actively @@ -4367,7 +4381,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh - where the shell script /usr/local/bin/x11vnc_sh uses the [614]-inetd + where the shell script /usr/local/bin/x11vnc_sh uses the [623]-inetd option and looks something like (you'll need to customize to your settings). #!/bin/sh @@ -4380,7 +4394,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg and that confuses it greatly, causing it to abort). If you do not use a wrapper script as above but rather call x11vnc directly in /etc/inetd.conf and do not redirect stderr to a file, then you must - specify the -q (aka [615]-quiet) option: "/usr/local/bin/x11vnc -q + specify the -q (aka [624]-quiet) option: "/usr/local/bin/x11vnc -q -inetd ...". When you supply both -q and -inet and no "-o logfile" then stderr will automatically be closed (to prevent, e.g. library stderr messages leaking out to the viewer). The recommended practice @@ -4388,12 +4402,12 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg script with "2>logfile" redirection because the errors and warnings printed out are very useful in troubleshooting problems. - Note also the need to set XAUTHORITY via [616]-auth to point to the + Note also the need to set XAUTHORITY via [625]-auth to point to the MIT-COOKIE auth file to get permission to connect to the X display (setting and exporting the XAUTHORITY variable accomplishes the same thing). See the x11vnc_loop file in the previous question for more ideas on what that auth file may be, etc. The scheme described in the - [617]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY + [626]FAQ on Unix user logins and inetd(8) works around the XAUTHORITY issue nicely. Note: On Solaris you cannot have the bare number 5900 in @@ -4478,9 +4492,9 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 it automatically? Yes, as of Feb/2007 x11vnc supports mDNS / Zeroconf advertising of its - service via the Avahi client library. Use the option [618]-avahi (same - as [619]-mdns) to enable it. Depending on your setup you may need to - install [620]Avahi (including the development packages), enable the + service via the Avahi client library. Use the option [627]-avahi (same + as [628]-mdns) to enable it. Depending on your setup you may need to + install [629]Avahi (including the development packages), enable the server: avahi-daemon and avahi-dnsconfd, and possibly open up UDP port 5353 on your firewall. @@ -4505,32 +4519,32 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 machine and then connect to it? How about starting an X session if one cannot be found? - The easiest way to do this is via [621]inetd(8) using the [622]-unixpw - and [623]-display WAIT options. The reason inetd(8) makes this easier + The easiest way to do this is via [630]inetd(8) using the [631]-unixpw + and [632]-display WAIT options. The reason inetd(8) makes this easier is that it starts a new x11vnc process for each new user connection. Otherwise a wrapper would have to listen for connections and spawn new - x11vnc's (see [624]this example and also the [625]-loopbg option). + x11vnc's (see [633]this example and also the [634]-loopbg option). Also with inetd(8) users always connect to a fixed VNC display, say hostname:0, and do not need to memorize a special VNC display number just for their personal use, etc. - Update: Use the [626]-find, [627]-create, [628]-svc, and [629]-xdmsvc + Update: Use the [635]-find, [636]-create, [637]-svc, and [638]-xdmsvc options that are shorthand for common FINDCREATEDISPLAY usage modes (e.g. terminal services) described below. (i.e. just use "-svc" instead of "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb -unixpw -users unixpw= -ssl SAVE") - The [630]-display WAIT option makes x11vnc wait until a VNC viewer is + The [639]-display WAIT option makes x11vnc wait until a VNC viewer is connected before attaching to the X display. Additionally it can be used to run an external command that returns the DISPLAY and XAUTHORITY data. We provide some useful builtin ones (FINDDISPLAY and FINDCREATEDISPLAY below), but in principle one could supply "-display WAIT:cmd=/path/to/find_display" where the script find_display might - look something like [631]this. + look something like [640]this. A default script somewhat like the above is used under "-display - WAIT:cmd=FINDDISPLAY" (same as [632]-find) (use + WAIT:cmd=FINDDISPLAY" (same as [641]-find) (use "WAIT:cmd=FINDDISPLAY-print" to print out the gnarly script). The format for any such command is that it returns DISPLAY=:disp as the first line and any remaining lines are either XAUTHORITY=file or raw @@ -4542,10 +4556,10 @@ exec /usr/local/bin/x11vnc -inetd -o /var/log/x11vnc.log -find -env FD_XDM=1 Or if you only know the X server process ID and suspect a chvt will be needed append ",XPID=n". - Tip: Note that the [633]-find option is an alias for "-display + Tip: Note that the [642]-find option is an alias for "-display WAIT:cmd=FINDDISPLAY". Use it! - The [634]-unixpw option allows [635]UNIX password logins. It + The [643]-unixpw option allows [644]UNIX password logins. It conveniently knows the Unix username whose X display should be found. Here are a couple /etc/inetd.conf examples for this: 5900 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd @@ -4559,16 +4573,16 @@ xpw= Note the very long lines have been split. An alternative is to use a wrapper script, e.g. /usr/local/bin/x11vnc.sh that has all of the - options. (see also the [636]-svc alias). + options. (see also the [645]-svc alias). In the first one x11vnc is run as user "nobody" and stays user nobody during the whole session. The permissions of the log files and certs directory will need to be set up to allow "nobody" to use them. In the second one x11vnc is run as root and switches to the user that - logs in due to the "[637]-users unixpw=" option. + logs in due to the "[646]-users unixpw=" option. - Note that [638]SSL is required for this mode because otherwise the + Note that [647]SSL is required for this mode because otherwise the Unix password would be passed in clear text over the network. In general -unixpw is not required for this sort of scheme, but it is convenient because it determines exactly who the Unix user is whose @@ -4576,17 +4590,17 @@ xpw= to use some method to work out DISPLAY, XAUTHORITY, etc (perhaps you use multiple inetd ports and hardwire usernames for different ports). - If you really want to disable the SSL or SSH [639]-localhost + If you really want to disable the SSL or SSH [648]-localhost constraints (this is not recommended unless you really know what you are doing: Unix passwords sent in clear text is a very bad idea...) - read the [640]-unixpw documentation. + read the [649]-unixpw documentation. A inetd(8) scheme for a fixed user that doesn't use SSL or unix passwds could be: /usr/local/bin/x11vnc -inetd -users =fred -find -rfbauth /home/fred/.vnc/passwd -o /var/log/x11vnc.log - The "[641]-users =fred" option will cause x11vnc to switch to user + The "[650]-users =fred" option will cause x11vnc to switch to user fred and then find his X display. @@ -4595,7 +4609,7 @@ xpw= FINDDISPLAY method it will create an X server session for the user (i.e. desktop/terminal server). This is the only time x11vnc actually tries to start up an X server. By default it will only try to start up - virtual (non-hardware) X servers: first [642]Xdummy and if that is not + virtual (non-hardware) X servers: first [651]Xdummy and if that is not available then Xvfb. Note that Xdummy requires root permission and only works on Linux whereas Xvfb works just about everywhere. @@ -4605,19 +4619,19 @@ xpw= -display WAIT:cmd=FINDCREATEDISPLAY -prog /usr/local/bin/x11vnc Where the very long lines have been split. This will allow direct SSL - (e.g. [643]ss_vncviewer) access and also Java Web browers access via: + (e.g. [652]ss_vncviewer) access and also Java Web browers access via: https://hostname:5900/. - Tip: Note that the [644]-create option is an alias for "-display + Tip: Note that the [653]-create option is an alias for "-display WAIT:cmd=FINDCREATEDISPLAY-Xvfb". - Tip: Note that [645]-svc is a short hand for the long "-ssl SAVE + Tip: Note that [654]-svc is a short hand for the long "-ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY" part. Unlike -create, this alias also sets up SSL encryption and Unix password login. Tip: In addition to the usual unixpw parameters, the user can specify - after his username (following a ":" see [646]-display WAIT for + after his username (following a ":" see [655]-display WAIT for details) for FINDCREATEDISPLAY they can add "geom=WxH" or "geom=WxHxD" to specify the width, height, and optionally the color depth. E.g. "fred:geom=800x600" at the login: prompt. Also if the env. var @@ -4654,7 +4668,7 @@ service x11vnc WAIT:cmd=FINDCREATEDISPLAY-X,Xvfb,Xdummy". The "X" one means to try to start up a real, hardware X server, e.g. startx(1) (if there is already a real X server running this may only work on Linux and the - chvt program may [647]need to be run to switch to the correct Linux + chvt program may [656]need to be run to switch to the correct Linux virtual terminal). x11vnc will try to run chvt automatically if it can determine which VT should be switched to. @@ -4681,7 +4695,7 @@ service x11vnc will also typically block UDP (port 177 for XDMCP) by default effectively limiting the UDP connections to localhost. - Tip: Note that [648]-xdmsvc is a short hand for the long "-ssl SAVE + Tip: Note that [657]-xdmsvc is a short hand for the long "-ssl SAVE -unixpw -users unixpw= -display WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp" part. E.g.: service x11vnc @@ -4748,15 +4762,15 @@ t:5 Q-61: Can I have x11vnc restart itself after it terminates? One could do this in a shell script, but now there is an option - [649]-loop that makes it easier. Of course when x11vnc restarts it + [658]-loop that makes it easier. Of course when x11vnc restarts it needs to have permissions to connect to the (potentially new) X display. This mode could be useful if the X server restarts often. Use e.g. "-loop5000" to sleep 5000 ms between restarts. Also "-loop2000,5" to sleep 2000 ms and only restart 5 times. - One can also use the [650]-loopbg to emulate inetd(8) to some degree, + One can also use the [659]-loopbg to emulate inetd(8) to some degree, where each connected process runs in the background. It could be - combined, say, with the [651]-svc option to provide simple terminal + combined, say, with the [660]-svc option to provide simple terminal services without using inetd(8). @@ -4764,7 +4778,7 @@ t:5 web browser? To have x11vnc serve up a Java VNC viewer applet to any web browsers - that connect to it, run x11vnc with this [652]option: + that connect to it, run x11vnc with this [661]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -4783,7 +4797,7 @@ t:5 then you can connect to that URL with any Java enabled browser. Feel free to customize the default index.vnc file in the classes directory. - As of May/2005 the [653]-http option will try to guess where the Java + As of May/2005 the [662]-http option will try to guess where the Java classes jar file is by looking in expected locations and ones relative to the x11vnc binary. @@ -4792,7 +4806,7 @@ t:5 either the java or appletviewer commands to run the program. java -cp ./VncViewer.jar VncViewer HOST far-away.east PORT 5900 - Proxies: See the [654]discussion here if the web browser must use a + Proxies: See the [663]discussion here if the web browser must use a web proxy to connect to the internet. It is tricky to get Java applets to work in this case: a signed applet must be used so it can connect to the proxy and ask for the redirection to the VNC server. One way to @@ -4808,7 +4822,7 @@ t:5 As of Mar/2004 x11vnc supports reverse connections. On Unix one starts the VNC viewer in listen mode: "vncviewer -listen" (see your documentation for Windows, etc), and then starts up x11vnc with the - [655]-connect option. To connect immediately at x11vnc startup time + [664]-connect option. To connect immediately at x11vnc startup time use the "-connect host:port" option (use commas for a list of hosts to connect to). The ":port" is optional (default is VNC listening port is 5500). @@ -4817,11 +4831,11 @@ t:5 file is checked periodically (about once a second) for new hosts to connect to. - The [656]-remote control option (aka -R) can also be used to do this + The [665]-remote control option (aka -R) can also be used to do this during an active x11vnc session, e.g.: x11vnc -display :0 -R connect:hostname.domain - Use the "[657]-connect_or_exit" option to have x11vnc exit if the + Use the "[666]-connect_or_exit" option to have x11vnc exit if the reverse connection fails. Also, note the "-rfbport 0" option disables TCP listening for connections (potentially useful for reverse connection mode, assuming you do not want any "forward" connections). @@ -4834,7 +4848,7 @@ x11vnc -display :0 -R connect:hostname.domain X11VNC_REVERSE_CONNECTION_NO_AUTH=1" to x11vnc. Vncconnect command: To use the vncconnect(1) program (from the core - VNC package at www.realvnc.com) specify the [658]-vncconnect option to + VNC package at www.realvnc.com) specify the [667]-vncconnect option to x11vnc (Note: as of Dec/2004 -vncconnect is now the default). vncconnect(1) must be pointed to the same X11 DISPLAY as x11vnc (since it uses X properties to communicate with x11vnc). If you do not have @@ -4853,7 +4867,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" proxy or SSH? Yes, as of Oct/2007 x11vnc supports reverse connections through - proxies: use the "[659]-proxy host:port" option. The default is to + proxies: use the "[668]-proxy host:port" option. The default is to assume the proxy is a Web proxy. Note that most Web proxies only allow proxy destination connections to ports 443 (HTTPS) and 563 (SNEWS) and so this might not be too useful unless the proxy has been modified @@ -4873,11 +4887,11 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" connections. An experimental mode is "-proxy http://host:port/..." where the URL - (e.g. a CGI script) is retrieved via the GET method. See [660]-proxy + (e.g. a CGI script) is retrieved via the GET method. See [669]-proxy for more info. Another experimental mode is "-proxy ssh://user@host" in which case a - SSH tunnel is used for the proxying. See [661]-proxy for more info. + SSH tunnel is used for the proxying. See [670]-proxy for more info. Up to 3 proxies may be chained together by listing them by commas e.g.: "-proxy http://host1:port1,socks5://host2:port2" in case one @@ -4900,10 +4914,10 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" Driver in XFree86/Xorg (see below). In either case, one can view this desktop both remotely and also - [662]locally using vncviewer. Make sure vncviewer's "-encodings raw" + [671]locally using vncviewer. Make sure vncviewer's "-encodings raw" is in effect for local viewing (compression seems to slow things down locally). For local viewing you set up a "bare" window manager that - just starts up vncviewer and nothing else ([663]See how below). + just starts up vncviewer and nothing else ([672]See how below). Here is one way to start up Xvfb: xinit -- /usr/X11R6/bin/Xvfb :1 -cc 4 -screen 0 1024x768x16 @@ -4923,19 +4937,19 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" "screen scrape" it very efficiently (more than, say, 100X faster than normal video hardware). - Update Nov/2006: See the [664]FINDCREATEDISPLAY discussion of the - "[665]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or + Update Nov/2006: See the [673]FINDCREATEDISPLAY discussion of the + "[674]-display WAIT:cmd=FINDDISPLAY" option where virtual (Xvfb or Xdummy, or even real ones by changing an option) X servers are started automatically for new users connecting. This provides a "desktop service" for the machine. You either get your real X session or your virtual (Xvfb/Xdummy) one whenever you connect to the machine - (inetd(8) is a nice way to provide this service). The [666]-find, - [667]-create, [668]-svc, and [669]-xdmsvc aliases can also come in + (inetd(8) is a nice way to provide this service). The [675]-find, + [676]-create, [677]-svc, and [678]-xdmsvc aliases can also come in handy here. There are some annoyances WRT Xvfb however. The default keyboard mapping seems to be very poor. One should run x11vnc with - [670]-add_keysyms option to have keysyms added automatically. Also, to + [679]-add_keysyms option to have keysyms added automatically. Also, to add the Shift_R and Control_R modifiers something like this is needed: #!/bin/sh xmodmap -e "keycode any = Shift_R" @@ -4947,7 +4961,7 @@ xmodmap -e "keycode any = Alt_R" xmodmap -e "keycode any = Meta_L" xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L" - (note: these are applied automatically in the [671]FINDCREATEDISPLAY + (note: these are applied automatically in the [680]FINDCREATEDISPLAY mode of x11vnc). Perhaps the Xvfb options -xkbdb or -xkbmap could be used to get a better default keyboard mapping... @@ -4962,11 +4976,11 @@ xmodmap -e "add Mod1 = Alt_L Alt_R Meta_L" The main drawback to this method (besides requiring extra configuration and possibly root permission) is that it also does the - Linux Virtual Console/Terminal (VC/VT) [672]switching even though it + Linux Virtual Console/Terminal (VC/VT) [681]switching even though it does not need to (since it doesn't use a real framebuffer). There are some "dual headed" (actually multi-headed/multi-user) patches to the X server that turn off the VT usage in the X server. Update: As of - Jul/2005 we have an LD_PRELOAD script [673]Xdummy that allows you to + Jul/2005 we have an LD_PRELOAD script [682]Xdummy that allows you to use a stock (i.e. unpatched) Xorg or XFree86 server with the "dummy" driver and not have any VT switching problems! Currently Xdummy needs to be run as root, but with some luck that may be relaxed in the @@ -4994,7 +5008,7 @@ x11vnc -display :5 -rfbport 5905 -bg vncviewer -geometry +0+0 -encodings raw -passwd $HOME/.vnc/passwd localhost:5 The display numbers (VNC and X) will likely be different (you could - also try [674]-find), and you may not need the -passwd. Recent RealVNC + also try [683]-find), and you may not need the -passwd. Recent RealVNC viewers might be this: #!/bin/sh x11vnc -display :5 -rfbport 5905 -bg @@ -5021,7 +5035,7 @@ t:5 An X server can be started on the headless machine (sometimes this requires configuring the X server to not fail if it cannot detect a keyboard or mouse, see the next paragraph). Then you can export that X - display via x11vnc (e.g. see [675]this FAQ) and access it from + display via x11vnc (e.g. see [684]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 @@ -5044,10 +5058,10 @@ t:5 cards as it can hold to provide multiple simultaneous access or testing on different kinds of video hardware. - See also the [676]FINDCREATEDISPLAY discussion of the "[677]-display + See also the [685]FINDCREATEDISPLAY discussion of the "[686]-display WAIT:cmd=FINDDISPLAY" option where virtual Xvfb or Xdummy, or real X servers are started automatically for new users connecting. The - [678]-find, [679]-create, [680]-svc, and [681]-xdmsvc aliases can also + [687]-find, [688]-create, [689]-svc, and [690]-xdmsvc aliases can also come in handy here. [Resource Usage and Performance] @@ -5070,7 +5084,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 [682]shm_clear to list and prompt for removal + Here is a shell script [691]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, @@ -5104,40 +5118,41 @@ ied) in /etc/system. See the next paragraph for more workarounds. To minimize the number of shm segments used by x11vnc try using the - [683]-onetile option (corresponds to only 3 shm segments used, and + [692]-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 - [684]-noshm option. Performance will be somewhat degraded but when + [693]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [685]earlier question discussing -noshm). + [694]earlier question discussing -noshm). Q-68: How can I make x11vnc use less system resources? - The [686]-nap (now on by default) and "[687]-wait n" (where n is the - sleep between polls in milliseconds, the default is 30 or so) option - are good places to start. Something like "[688]-sb 15" will cause - x11vnc to go into a deep-sleep mode after 15 seconds of no activity - (instead of the default 60). + The [695]-nap (now on by default; use -nonap to disable) and + "[696]-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 "[697]-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 [689]-onetile option will use less memory and use fewer shared - memory slots (add [690]-fs 1.0 for one less slot). + the [698]-onetile option will use less memory and use fewer shared + memory slots (add [699]-fs 1.0 for one less slot). Q-69: How can I make x11vnc use MORE system resources? - You can try [691]-threads (note this mode can be unstable and/or - crash) or dial down the wait time (e.g. -wait 1) and possibly dial - down [692]-defer as well. Note that if you try to increase the "frame - rate" too much you can bog down the server end with the extra work it - needs to do compressing the framebuffer data, etc. + You can try [700]-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 [701]-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 [693]-id option) can be streamed over a LAN or wireless at + the x11vnc [702]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. @@ -5153,7 +5168,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 - [694]-solid [color] option to try to do this automatically. + [703]-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 @@ -5162,9 +5177,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 [695]-scrollcopyrect is active and + problem in x11vnc 0.7.2 if [704]-scrollcopyrect is active and detecting scrolls for the application). - * If the [696]-wireframe option is not available (earlier than + * If the [705]-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) @@ -5187,7 +5202,7 @@ ied) noticed. VNC viewer parameters: - * Use a [697]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer + * Use a [706]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 @@ -5195,7 +5210,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). [698]SSVNC does too. The colors are poor, but it + even 8 colors). [707]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) @@ -5209,37 +5224,37 @@ ied) file. x11vnc parameters: - * Make sure the [699]-wireframe option is active (it should be on by + * Make sure the [708]-wireframe option is active (it should be on by default) and you have Opaque Moves/Resizes Enabled in the window manager. - * Make sure the [700]-scrollcopyrect option is active (it should be + * Make sure the [709]-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 - [701]-solid - * Specify [702]-speeds modem to force the wireframe and + [710]-solid + * Specify [711]-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 [703]-nodragging (no screen updates when dragging mouse, + drastic [712]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Set [704]-fs 1.0 (disables fullscreen updates) - * Try increasing [705]-wait or [706]-defer (reduces the maximum + * Set [713]-fs 1.0 (disables fullscreen updates) + * Try increasing [714]-wait or [715]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * Try the [707]-progressive pixelheight mode with the block + * Try the [716]-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 [708]-id (cuts + * If you just want to watch one (simple) window use [717]-id (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [709]-nosel (disables all clipboard selection exchange) - * Use [710]-nocursor and [711]-nocursorpos (repainting the remote + * Set [718]-nosel (disables all clipboard selection exchange) + * Use [719]-nocursor and [720]-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 - [712]-readtimeout n setting if it sometimes takes more than 20sec + [721]-readtimeout n setting if it sometimes takes more than 20sec to paint the full screen, etc. - * Do not use [713]-fixscreen to automatically refresh the whole + * Do not use [722]-fixscreen to automatically refresh the whole screen, tap three Alt_L's then the screen has painting errors (rare problem). @@ -5308,7 +5323,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 [714]slow (e.g. + in main memory. So reading the fb is still painfully [723]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 @@ -5326,45 +5341,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 "[715]-xd_area A" option to adjust the size + skipped). You can use the "[724]-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 "[716]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[717]-noxdamage". + The option "[725]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[726]-noxdamage". Q-72: 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 "[718]-noxdamage" option. + he uses the "[727]-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 [719]MiniMyth reports that the 'alphapulse' tag of the + A developer for [728]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 [720]this FAQ too. + Update: see [729]this FAQ too. Q-73: 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 [721]slow hardware read rates from + This problem is primarily due to [730]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 - [722]-pointer_mode option for more info. The next bottleneck is + [731]-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 @@ -5374,27 +5389,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 "[723]-pointer_mode 1" option. + the "[732]-pointer_mode 1" option. - Also added was the [724]-nodragging option that disables all screen + Also added was the [733]-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 [725]-pointer_mode n option was introduced. n=1 is + As of Dec/2004 the [734]-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 [726]-threads option can improve + Also, in some circumstances the [735]-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 [727]wireframe FAQ and - [728]scrollcopyrect FAQ below) provide schemes to sweep this problem + As of Apr/2005 two new options (see the [736]wireframe FAQ and + [737]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 @@ -5418,8 +5433,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 [729]slow video card - read rates (see [730]here too). A displacement, even a small one, of a + intermediate steps. BTW the lurching is due to [738]slow video card + read rates (see [739]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. @@ -5427,7 +5442,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 [731]-nowireframe option + with the problem. It can be disabled with the [740]-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 @@ -5473,13 +5488,13 @@ EndSection * Maximum time to show a wireframe animation. * Minimum time between sending wireframe outlines. - See the [732]"-wireframe tweaks" option for more details. On a slow + See the [741]"-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 - [733]"-wirecopyrect mode" option. It is also on by default. This + [742]"-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 @@ -5527,7 +5542,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 [734]slow). + the hardware framebuffer is [743]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. @@ -5554,10 +5569,10 @@ EndSection the X server display: if one falls too far behind it could become a mess... - The initial implementation of [735]-scrollcopyrect option is useful in + The initial implementation of [744]-scrollcopyrect option is useful in that it detects many scrolls and thus gives a much nicer working - environment (especially when combined with the [736]-wireframe - [737]-wirecopyrect [738]options, which are also on by default; and if + environment (especially when combined with the [745]-wireframe + [746]-wirecopyrect [747]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. @@ -5590,10 +5605,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: [739]-fixscreen + also: [748]-fixscreen * Some applications, notably OpenOffice, do XCopyArea scrolls in weird ways that assume ancestor window clipping is taking place. - See the [740]-scr_skip option for ways to tweak this on a + See the [749]-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 @@ -5610,7 +5625,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 [741]-scale option there will be a quick CopyRect + * When using the [750]-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 @@ -5623,7 +5638,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 [742]-noscrollcopyrect (or -noscr for short). If you find + with the [751]-noscrollcopyrect (or -noscr for short). If you find some extremely bad and repeatable behavior for -scrollcopyrect please report a bug. @@ -5648,9 +5663,9 @@ EndSection that pixel data is needed again it does not have to be retransmitted over the network. - As of Dec/2006 in the [743]0.9 development tarball there is an + As of Dec/2006 in the [752]0.9 development tarball there is an experimental client-side caching implementation enabled by the - "[744]-ncache n" option. In fact, during the test period it was on by + "[753]-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 @@ -5684,7 +5699,7 @@ EndSection rendering...). The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice - [745]-ycrop option to help hide the pixel cache area from view. It + [754]-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 resized by scaling, etc, the ycrop value @@ -5713,7 +5728,7 @@ EndSection an additional factor of 2 in memory use. However, even in the smallest usage mode with n equal 2 and - [746]-ncache_no_rootpixmap set (this requires only 2X additional + [755]-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. @@ -5724,7 +5739,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 "[747]-ncache_cr". By specifying + Another option to experiment with is "[756]-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 @@ -5794,23 +5809,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 "[748]-cursor X" option that + A simple kludge is provided by the "[757]-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 "[749]-cursor some" option for + work for those cases. Also see the "[758]-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 - [750]-overlay option is supplied. See [751]this FAQ for more info. + [759]-overlay option is supplied. See [760]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 - [752]Solaris 10. + [761]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 @@ -5818,7 +5833,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. [753]Details can be found here. + hidden alpha channel data under 32bpp. [762]Details can be found here. Q-78: When using XFIXES cursorshape mode, some of the cursors look @@ -5851,17 +5866,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 "[754]-alphacut n" option lets + course!) some tunable parameters. The "[763]-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 "[755]-alphafrac f" option tries to correct individual + 240. The "[764]-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 [756]-alpharemove that is useful for + Finally, there is an option [765]-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 @@ -5887,10 +5902,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 [757]-nocursorshape x11vnc option. In this case the cursor is + with the [766]-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 [758]-noalphablend option to disable this + the x11vnc side. Use the [767]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). @@ -5914,7 +5929,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 [759]Enhanced TightVNC Viewer (SSVNC) + This patch is applied to the [768]Enhanced TightVNC Viewer (SSVNC) package we provide. [Mouse Pointer] @@ -5922,9 +5937,9 @@ EndSection Q-80: 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 [760]tightvnc extension + This default takes advantage of a [769]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [761]-nocursor + the local VNC viewer. You may disable it with the [770]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -5938,17 +5953,17 @@ EndSection clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [762]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [771]-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 [763]-nocursorpos and [764]-nocursorshape. + is the default. See also [772]-nocursorpos and [773]-nocursorshape. Q-82: 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: [765]-buttonmap + You can remap the mouse buttons via something like: [774]-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. @@ -5956,7 +5971,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 [766]-debug_pointer option prints out much info for + Note that the [775]-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 @@ -5978,7 +5993,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 [767]-buttonmap but rather configuring the X server + consider not using [776]-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"'). @@ -6008,7 +6023,7 @@ EndSection Q-83: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [768]-modtweak should help here. It is a mode that monitors + The option [777]-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. @@ -6017,16 +6032,16 @@ 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 [769]this FAQ for more info). Without + not exist on the keyboard (see [778]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 [770]FAQ about the -xkb option for a more powerful method + Also see the [779]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 - [771]-debug_keyboard option prints out much info for every keystroke + [780]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. @@ -6038,9 +6053,9 @@ EndSection (e.g. pc105 in the XF86Config file when it should be something else, say pc104). - Short Cut: Try the [772]-xkb or [773]-sloppy_keys options and see if + Short Cut: Try the [781]-xkb or [782]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [774]-modtweak is now the default) but it is useful reference for + [783]-modtweak is now the default) but it is useful reference for various tricks and so is kept. @@ -6083,31 +6098,39 @@ EndSection -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([775]-modtweak) is a mode that monitors the + settings. The former ([784]-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 ([776]-remap less-comma) is an immediate remapping of the + The latter ([785]-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 [777]FAQ about the -xkb option as a possible workaround + See also the [786]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [778]-debug_keyboard option prints out much info for + Note that the [787]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. - Q-85: When I try to type a "<" (i.e. less than) instead I get "<," - (i.e. an extra comma). + Q-85: Extra Character Inserted, E.g.: When I try to type a "<" (i.e. + 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 [779]keymapping + the Shift key before releasing the "<". Because of a [788]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. - This should not happen in [780]-xkb mode, because it works hard to + This extra character insertion will happen for other combinations of + characters: in general it can happen whenever the Shift key is + released early. + + This should not happen in [789]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [781]-sloppy_keys to attempt a similar type of algorithm. + option [790]-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 "." + inserted after the ":". The solution was -sloppy_keys. Q-86: I'm using an "international" keyboard (e.g. German "de", or @@ -6131,7 +6154,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 [782]-modtweak + This all worked fine with x11vnc running with the [791]-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 @@ -6148,7 +6171,7 @@ EndSection * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [783]-xkb option seems to fix all of the missing keys: "@", "<", + The [792]-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 @@ -6156,7 +6179,7 @@ EndSection debugging output (send it along with any problems you report). Update: as of Jun/2005 x11vnc will try to automatically enable - [784]-xkb if it appears that would be beneficial (e.g. if it sees any + [793]-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. @@ -6171,7 +6194,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: - [785]-skip_keycodes 93 + [794]-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 @@ -6189,16 +6212,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 [786]-remap x11vnc option: + created using the [795]-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 - [787]-add_keysyms option in the next paragraph. - Update: for convenience "[788]-remap DEAD" does many of these + [796]-add_keysyms option in the next paragraph. + Update: for convenience "[797]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [789]-remap, an - option [790]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [798]-remap, an + option [799]-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 @@ -6217,7 +6240,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) [791]-norepeat x11vnc option. You will still + use the new (Jul/2004) [800]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -6241,7 +6264,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 [792]-norepeat (which has since Dec/2004 been + needed, or to use the [801]-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 @@ -6252,7 +6275,7 @@ EndSection keystrokes!! Are you using x11vnc to log in to an X session via display manager? - (as described in [793]this FAQ) If so, x11vnc is starting before your + (as described in [802]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 @@ -6300,11 +6323,11 @@ EndSection 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 [794]-clear_mods option to try to clear all of + You can also use the [803]-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 [795]-remap to prevent sending all of the problem modifier + of using [804]-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: @@ -6317,16 +6340,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 [796]this FAQ on lock keys - problem. These options may help avoid the problem: [797]-skip_lockkeys - and [798]-capslock. See also [799]-clear_all. + down on the local (Viewer) side. See [805]this FAQ on lock keys + problem. These options may help avoid the problem: [806]-skip_lockkeys + and [807]-capslock. See also [808]-clear_all. Q-90: 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 "[800]-remap Super_R-Mode_switch" x11vnc option may + Something like "[809]-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)). @@ -6349,7 +6372,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 [801]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [810]-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. @@ -6369,7 +6392,7 @@ EndSection and similar triple mappings (with two in the AltGr/Mode_switch group) of a keysum to a single keycode. - Use the [802]-nomodtweak option as a workaround. You can also use + Use the [811]-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" @@ -6383,7 +6406,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 [803]-remap + have x11vnc do the remapping. This can be done via the [812]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -6392,7 +6415,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: - [804]-remap Super_R-Button2 + [813]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -6411,13 +6434,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 - [805]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[806]-remap Caps_Lock-None". + [814]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[815]-remap Caps_Lock-None". - Also try the [807]-nomodtweak and [808]-capslock options. + Also try the [816]-nomodtweak and [817]-capslock options. Another useful option that turns off any Lock keys on the remote side - at startup and end is the [809]-clear_all option. During a session you + at startup and end is the [818]-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 @@ -6446,7 +6469,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 - [810]the next FAQ on x11vnc scaling. + [819]the next FAQ on x11vnc scaling. Q-96: Does x11vnc support server-side framebuffer scaling? (E.g. to @@ -6454,7 +6477,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 "[811]-scale fraction" option. "fraction" can either be a + use the "[820]-scale fraction" option. "fraction" can either be a floating point number (e.g. -scale 0.5) or the alternative m/n fraction notation (e.g. -scale 3/4). Note that if fraction is greater than one the display is magnified. @@ -6479,7 +6502,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 - [812]applications. Since with integer scale factors the framebuffers + [821]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -6505,7 +6528,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 ([813]-rfbport option, + different scalings listening on separate ports ([822]-rfbport option, etc.). Update: As of May/2006 x11vnc also supports the UltraVNC server-side @@ -6515,8 +6538,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 [814]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [815]"-connect + use the [823]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [824]"-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 @@ -6525,7 +6548,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 - [816]"-scale_cursor frac" option to set the cursor scaling to a + [825]"-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). @@ -6543,25 +6566,31 @@ EndSection to split the big screen into two and used two VNC viewers to access them. + As of Jun/2008: Use "-clip xinerama0" to clip to the first xinerama + sub-screen (if xinerama is active). xinerama1 for the 2nd sub-screen, + etc. This way you don't need to figure out the WxH+X+Y of the desired + xinerama sub-screen. screens are sorted in increasing distance from + the (0,0) origin (I.e. not the Xserver's order). + There are a couple potential issues with Xinerama however. If the 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 [817]-blackout x11vnc option + may be distracting to the viewer. The [826]-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 - [818]-xinerama x11vnc option can be used to have it automatically + [827]-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: - [819]-xinerama is now on by default. + [828]-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 [820]-xwarppointer + of the large display. If this happens try using the [829]-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 [821]-xwarppointer will + Xinerama is enabled). Update: As of Dec/2006 [830]-xwarppointer will be applied automatically if Xinerama is detected. To disable use: -noxwarppointer @@ -6584,38 +6613,32 @@ 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 [822]FAQ to increase the limit. It - is probably also a good idea to run with the [823]-onetile option in + /etc/system as mentioned in another [831]FAQ to increase the limit. It + is probably also a good idea to run with the [832]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [824]-noshm to use no shm segments. + [833]-noshm to use no shm segments. Q-99: 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 "[825]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[834]-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 [826]Xinerama screen into two + One user used -clip to split up a large [835]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [827]-id or [828]-sid options are used. The offset is measured + the [836]-id or [837]-sid options are used. The offset is measured from the upper left corner of the selected window. - As of Jun/2008: Use "-clip xinerama0" to clip to the first xinerama - sub-screen (if xinerama is active). xinerama1 for the 2nd sub-screen, - etc. This way you don't need to figure out the WxH+X+Y of the desired - xinerama sub-screen. screens are sorted in increasing distance from - the (0,0) origin (I.e. not the Xserver's order). - Q-100: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) extension? Whenever I rotate or resize the screen x11vnc just seems to crash. As of Dec/2004 x11vnc supports XRANDR. You enable it with the - [829]-xrandr option to make x11vnc monitor XRANDR events and also trap + [838]-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. @@ -6625,9 +6648,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 [830]-padgeom option to make the region big + viewers you can try the [839]-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: [831]SSVNC + for the TightVNC Viewer on Unix: [840]SSVNC If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you @@ -6639,7 +6662,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 [832]-rotate option allow this. E.g's: + As of Jul/2006 there is the [841]-rotate option allow this. E.g's: "-rotate +90", "-rotate -90", "-rotate x", etc. @@ -6704,13 +6727,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 [833]here for how to + straight xscreensaver (see the instructions [842]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 [834]-nodpms option was added + suspend, or off). In Nov/2006 the x11vnc [843]-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 @@ -6726,16 +6749,16 @@ EndSection This appears to be because the 3D OpenGL/GLX hardware screen updates do not get reported via the XDAMAGE mechanism. So this is a bug in - [835]beryl or XDAMAGE/Xorg or the (possibly 3rd party) video card + [844]beryl or XDAMAGE/Xorg or the (possibly 3rd party) video card driver. - As a workaround apply the [836]-noxdamage option. As of Feb/2007 + As a workaround apply the [845]-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 [837]this + beryl you might as well always supply -noxdamage. Thanks to [846]this user who reported the problem and discovered the workaround. - A developer for [838]MiniMyth reports that the 'alphapulse' tag of the + A developer for [847]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. @@ -6755,9 +6778,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 [839]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [848]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X - server. So x11vnc cannot access it (however, [840]see this discussion + server. So x11vnc cannot access it (however, [849]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. @@ -6778,13 +6801,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 [841]is in the active VC. + as long as the VMWare X session [850]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 [842]-id windowid option. The + the VMWare menu buttons) by use of the [851]-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 @@ -6800,10 +6823,10 @@ EndSection controlled) via VNC with x11vnc? As of Apr/2005 there is support for this. Two options were added: - "[843]-rawfb string" (to indicate the raw frame buffer device, file, - etc. and its parameters) and "[844]-pipeinput command" (to provide an + "[852]-rawfb string" (to indicate the raw frame buffer device, file, + etc. and its parameters) and "[853]-pipeinput command" (to provide an external program that will inject or otherwise process mouse and - keystroke input). Some useful [845]-pipeinput schemes, VID, CONSOLE, + keystroke input). Some useful [854]-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 @@ -6841,9 +6864,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 [846]-snapfb option with + this). The "snap:" setting applies the [855]-snapfb option with "file:" type reading (this is useful for exporting webcams or TV tuner - video; see [847]the next FAQ for more info). + video; see [856]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 @@ -6887,7 +6910,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 [848]X + for the case of Xvfb x11vnc can poll it much better via the [857]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -6916,13 +6939,13 @@ EndSection 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 [849]Qt-embedded apps (PDAs/Handhelds). By default the + fullscreen, or [858]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 [850]this FAQ for details. If specified via "-rawfb Video" + kernel. See [859]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). @@ -6930,10 +6953,10 @@ EndSection also useful in testing. - All of the above [851]-rawfb options are just for viewing the raw + All of the above [860]-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 [852]video camera mapped its framebuffer + this feature (e.g. suppose a [861]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 @@ -6971,7 +6994,7 @@ EndSection 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 [853]active VC) one + view and interact with VC #2 (assuming it is the [862]active VC) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -7026,7 +7049,7 @@ EndSection 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 - [854]Qt-embedded Also, for example the [855]VMWare Fullscreen mode is + [863]Qt-embedded Also, for example the [864]VMWare Fullscreen mode is actually viewable under -rawfb and can be interacted with if uinput is enabled. @@ -7046,9 +7069,9 @@ EndSection Q-109: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - Yes, this is possible to some degree with the [856]-rawfb option. + Yes, this is possible to some degree with the [865]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [857]previous FAQ on -rawfb + used for the screen image data. See the [866]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -7060,7 +7083,7 @@ EndSection snapshot to a file that you point -rawfb to; ask me if it is not clear what to do). - The "snap:" enforces [858]-snapfb mode which appears to be necessary. + The "snap:" enforces [867]-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. @@ -7082,7 +7105,7 @@ EndSection 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 [859]-24to32 option will be automatically imposed when in + etc, the [868]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -7090,7 +7113,7 @@ EndSection 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 [860]-wait, [861]-slow_fb, or [862]-defer + the framerate via the [869]-wait, [870]-slow_fb, or [871]-defer options. Decreasing the window size and bpp also helps. @@ -7179,7 +7202,7 @@ EndSection format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [863]-freqtab option to supply your own xawtv channel to + See also the [872]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc). @@ -7188,7 +7211,7 @@ EndSection running on my handheld or PC using the Linux console framebuffer (i.e. not X11)? - Yes, the basic method for this is the [864]-rawfb scheme where the + Yes, the basic method for this is the [873]-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: @@ -7201,7 +7224,7 @@ EndSection x11vnc -rawfb /dev/fb0@640x480x16 Also, to force usage of the uinput injection method use "-pipeinput - UINPUT". See the [865]-pipeinput description for tunable parameters, + UINPUT". See the [874]-pipeinput description for tunable parameters, etc. One problem with the x11vnc uinput scheme is that it cannot guess the @@ -7217,7 +7240,7 @@ EndSection 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 [866]-pipeinput UINPUT option for tuning + times a second. See the [875]-pipeinput UINPUT option for tuning parameters that can be set (there are some experimental thresh=N tuning parameters as well) @@ -7252,7 +7275,7 @@ EndSection Q-111: 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 [867]-rawfb only + Yes, as of Jul/2006 x11vnc enables building for [876]-rawfb only support. Just do something like when building: ./configure --without-x (plus any other flags) make @@ -7268,11 +7291,11 @@ EndSection 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 - [868]-rawfb mechanism described above. The mouse and keyboard input is + [877]-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 [869]OSXvnc (aka Vine - Server), or [870]Apple Remote Desktop (ARD). Perhaps there is some + So you can use x11vnc as an alternative to [878]OSXvnc (aka Vine + Server), or [879]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. @@ -7282,7 +7305,7 @@ EndSection (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 [871]-id windowid mode (and the + only work reasonably in single window [880]-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 @@ -7300,9 +7323,9 @@ EndSection ./configure --without-x make - Win2VNC/x2vnc: One handy use is to use the [872]-nofb mode to + Win2VNC/x2vnc: One handy use is to use the [881]-nofb mode to redirect mouse and keyboard input to a nearby Mac (i.e. one to the - side of your desk) via [873]x2vnc or Win2VNC. See [874]this FAQ for + side of your desk) via [882]x2vnc or Win2VNC. See [883]this FAQ for more info. Options: Here are the Mac OS X specific x11vnc options: @@ -7376,13 +7399,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 "[875]-reflect host:N" option to + Yes, as of Feb/2007 there is the "[884]-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 - [876]-rawfb description under "VNC HOST" for more details. + [885]-rawfb description under "VNC HOST" for more details. You can replace "host:N" with "listen" or "listen:port" for reverse connections. @@ -7443,18 +7466,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 [877]-nodragging if the + not doing wireframing somehow, consider [886]-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: - [878]http://sourceforge.net/projects/vnc-reflector/, - [879]http://www.tightvnc.com/projector/ (closed source?), + [887]http://sourceforge.net/projects/vnc-reflector/, + [888]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 "[880]"-connect host1,host2,..." option). + connections (the x11vnc "[889]"-connect host1,host2,..." option). Suppose all the clients "C" are started up in Listen mode: client1> vncviewer -listen client2> vncviewer -listen @@ -7505,7 +7528,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 [881]this FAQ. + 755 ./x11vnc.static" and then find the -auth file as in [890]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 @@ -7514,7 +7537,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 [882]this FAQ. (maybe run "ps + Find the name of the auth file as in [891]this FAQ. (maybe run "ps wwwwaux | grep auth"). Then run it like this: ./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile @@ -7561,11 +7584,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 [883]-nosel option. If you don't + Clipboard/Selection exchanged use the [892]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [884]-noprimary option. (with a similar thing for CLIPBOARD). You can - also fine-tune it a bit with the [885]-seldir dir option and also - [886]-input. + [893]-noprimary option. (with a similar thing for CLIPBOARD). You can + also fine-tune it a bit with the [894]-seldir dir option and also + [895]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -7577,7 +7600,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 - [887]pyvnc2swf. There are a number of [888]tutorials on how to do + [896]pyvnc2swf. There are a number of [897]tutorials 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 @@ -7592,11 +7615,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux). - The [889]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [898]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 [890]-tightfilexfer option. + the [899]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -7619,7 +7642,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 [891]-users option, then VNC Viewers that connect are able to do + the [900]-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 @@ -7638,7 +7661,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [892]-ultrafilexfer which is an alias for the above option and + Or use [901]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -7650,14 +7673,14 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [893]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [902]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [894]-noultraext (the + To disable SingleWindow and ServerInput use [903]-noultraext (the others are managed by LibVNCServer). See this option too: - [895]-noserverdpms. + [904]-noserverdpms. - Also, the [896]UltraVNC repeater proxy is supported for use with - reverse connections: "[897]-connect repeater://host:port+ID:NNNN". Use + Also, the [905]UltraVNC repeater proxy is supported for use with + reverse connections: "[906]-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. @@ -7668,12 +7691,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [898]Single Click (SC) mode can be done fairly well on + Yes, UltraVNC's [907]Single Click (SC) mode can be done 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 [899]Mac OS X. + or family to use. This includes [908]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 @@ -7729,7 +7752,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 [900]this page for some variations on this method, e.g. how to add + See [909]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -7741,11 +7764,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 [901]here. + reverse connections). More info [910]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [902]router will have to be configured to + NAT/Firewall/Router the [911]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. @@ -7755,7 +7778,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. [903]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [912]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -7791,7 +7814,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 [904]Enhanced TightVNC Viewer (SSVNC) package we + better use the [913]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 @@ -7821,11 +7844,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 [905]-ssl + The only change from the "vnc" above is the addition of the [914]-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 [906]here.) + info [915]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -7834,7 +7857,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 [907]Enhanced TightVNC Viewer + The easiest way to do this is use [916]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 @@ -7864,7 +7887,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 [908]this link and [909]this one too for more info on SSL certs. + See [917]this link and [918]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 @@ -7885,7 +7908,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [910]here. + [919]here. OpenSSL libssl.so.0.9.7 problems: @@ -7895,7 +7918,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [911]details here. + You will find the [920]details here. Q-120: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -7904,7 +7927,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 [912]Samba example here. + We show a simple [921]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: @@ -7944,7 +7967,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 [913]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [922]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -7954,7 +7977,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 [914]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [923]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). @@ -8026,7 +8049,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 [915]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [924]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8127,7 +8150,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 [916]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [925]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing). @@ -8139,14 +8162,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 [917]-nobell option. If + If you don't want to hear the beeps use the [926]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [918]redirector such as esd. + trying a [927]redirector such as esd. Q-124: Does x11vnc work with IPv6? - Currently the only way to do this is via [919]inetd. You configure + Currently the only way to do this is via [928]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. @@ -8155,7 +8178,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 [920]IPv6 enabled, so a + Also note that not all VNC Viewers are [929]IPv6 enabled, so a redirector could even be needed on the client side. @@ -8166,9 +8189,9 @@ or: Q-125: Thanks for your program and for your help! Can I make a donation? - Please do (any amount is appreciated; only a handful of 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; only a few people have donated + anything) and thank you for your support! Click on the PayPal button + below for more info. [PayPal] @@ -8566,534 +8589,543 @@ References 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui 392. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray - 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N - 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport - 395. http://www.karlrunge.com/x11vnc/index.html#firewalls - 396. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect - 397. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel - 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 399. http://www.karlrunge.com/x11vnc/vncxfer - 400. http://www.karlrunge.com/x11vnc/index.html#firewalls - 401. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect-proxy - 402. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 403. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel - 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh - 405. http://www.karlrunge.com/x11vnc/ssvnc.html - 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o - 409. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389750 - 410. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399408 - 411. http://bugs.kde.org/show_bug.cgi?id=136924 - 412. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb - 414. http://fredrik.hubbe.net/x2vnc.html - 415. http://www.hubbe.net/~hubbe/win2vnc.html - 416. http://www.deboer.gmxhome.de/ - 417. http://sourceforge.net/projects/win2vnc/ - 418. http://fredrik.hubbe.net/x2vnc.html - 419. http://freshmeat.net/projects/x2x/ - 420. http://ftp.digital.com/pub/Digital/SRC/x2x/ - 421. http://zapek.com/software/zvnc/ - 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual - 423. http://www.karlrunge.com/x11vnc/index.html#faq-macosx - 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor - 427. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N + 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-autoport + 397. http://www.karlrunge.com/x11vnc/index.html#firewalls + 398. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect + 399. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel + 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 401. http://www.karlrunge.com/x11vnc/vncxfer + 402. http://www.karlrunge.com/x11vnc/index.html#firewalls + 403. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect-proxy + 404. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 405. http://www.karlrunge.com/x11vnc/index.html#ssl-tunnel + 406. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssh + 407. http://www.karlrunge.com/x11vnc/ssvnc.html + 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 411. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389750 + 412. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399408 + 413. http://bugs.kde.org/show_bug.cgi?id=136924 + 414. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 416. http://fredrik.hubbe.net/x2vnc.html + 417. http://www.hubbe.net/~hubbe/win2vnc.html + 418. http://www.deboer.gmxhome.de/ + 419. http://sourceforge.net/projects/win2vnc/ + 420. http://fredrik.hubbe.net/x2vnc.html + 421. http://freshmeat.net/projects/x2x/ + 422. http://ftp.digital.com/pub/Digital/SRC/x2x/ + 423. http://zapek.com/software/zvnc/ + 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 425. http://www.karlrunge.com/x11vnc/index.html#faq-macosx + 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor + 429. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 438. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid - 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 442. http://www.karlrunge.com/x11vnc/ssvnc.html - 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder - 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 447. http://www.karlrunge.com/x11vnc/index.html#xauth_pain - 448. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 449. http://wwws.sun.com/sunray/index.html - 450. http://www.karlrunge.com/x11vnc/sunray.html - 451. http://wiki.sun-rays.org/index.php/Remote_Control_Toolkit - 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys - 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 461. http://www.karlrunge.com/x11vnc/index.html#faq-config-file - 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd - 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 465. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw - 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd - 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd - 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 440. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid + 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 444. http://www.karlrunge.com/x11vnc/ssvnc.html + 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 446. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 447. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder + 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 449. http://www.karlrunge.com/x11vnc/index.html#xauth_pain + 450. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 451. http://wwws.sun.com/sunray/index.html + 452. http://www.karlrunge.com/x11vnc/sunray.html + 453. http://wiki.sun-rays.org/index.php/Remote_Control_Toolkit + 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys + 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 463. http://www.karlrunge.com/x11vnc/index.html#faq-config-file + 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 465. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd + 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 467. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw + 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd + 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis - 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 479. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 480. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel - 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 482. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt - 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd - 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd - 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis + 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 481. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 482. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel + 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 484. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt + 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd + 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_cmd + 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw 490. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 491. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt - 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared - 494. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 496. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 497. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 500. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 501. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 493. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt + 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared + 496. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 498. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 499. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 502. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 503. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly - 510. ftp://ftp.x.org/ - 511. http://www.karlrunge.com/x11vnc/dtVncPopup - 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept - 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 515. http://www.karlrunge.com/x11vnc/blockdpy.c - 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms - 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms - 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd - 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr - 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr - 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept - 525. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 526. http://www.karlrunge.com/x11vnc/ssvnc.html + 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly + 512. ftp://ftp.x.org/ + 513. http://www.karlrunge.com/x11vnc/dtVncPopup + 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 515. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept + 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 517. http://www.karlrunge.com/x11vnc/blockdpy.c + 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forcedpms + 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clientdpms + 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabkbd + 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr + 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-grabptr + 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept 527. http://www.karlrunge.com/x11vnc/index.html#tunnelling 528. http://www.karlrunge.com/x11vnc/ssvnc.html - 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 532. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh - 533. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 535. http://www.stunnel.org/ - 536. http://stunnel.mirt.net/ - 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 540. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 541. http://www.stunnel.org/ - 542. http://www.karlrunge.com/x11vnc/ssl.html - 543. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer - 544. http://www.karlrunge.com/x11vnc/ssvnc.html - 545. http://www.karlrunge.com/x11vnc/ssl.html - 546. http://www.securityfocus.com/infocus/1677 + 529. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 530. http://www.karlrunge.com/x11vnc/ssvnc.html + 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 534. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh + 535. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 537. http://www.stunnel.org/ + 538. http://stunnel.mirt.net/ + 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 541. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 542. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 543. http://www.stunnel.org/ + 544. http://www.karlrunge.com/x11vnc/ssl.html + 545. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 546. http://www.karlrunge.com/x11vnc/ssvnc.html 547. http://www.karlrunge.com/x11vnc/ssl.html - 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 549. http://sc.uvnc.com/javaviewer/index.html - 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 551. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 558. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer - 559. http://www.karlrunge.com/x11vnc/ssvnc.html - 560. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 563. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 565. http://www.openssl.org/ - 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 567. http://www.stunnel.org/ - 568. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 569. http://www.karlrunge.com/x11vnc/index.html#ssl-vnc-viewers - 570. http://www.karlrunge.com/x11vnc/ssl.html - 571. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 548. http://www.securityfocus.com/infocus/1677 + 549. http://www.karlrunge.com/x11vnc/ssl.html + 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 551. http://sc.uvnc.com/javaviewer/index.html + 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 553. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 560. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 561. http://www.karlrunge.com/x11vnc/ssvnc.html + 562. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 565. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 567. http://www.openssl.org/ + 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 569. http://www.stunnel.org/ + 570. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 571. http://www.karlrunge.com/x11vnc/index.html#ssl-vnc-viewers 572. http://www.karlrunge.com/x11vnc/ssl.html - 573. http://www.karlrunge.com/x11vnc/index.html#viewer-side-stunnel - 574. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer - 575. http://www.karlrunge.com/x11vnc/ssvnc.html - 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 578. http://sc.uvnc.com/javaviewer/index.html - 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 580. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 581. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal - 582. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy - 583. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal - 584. http://www.karlrunge.com/x11vnc/index.html#firewalls - 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 587. http://www.karlrunge.com/x11vnc/ssl-output.html - 588. http://www.karlrunge.com/x11vnc/ssvnc.html - 589. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 590. http://www.karlrunge.com/x11vnc/ss_vncviewer - 591. http://www.karlrunge.com/x11vnc/ssl-portal.html - 592. http://www.karlrunge.com/x11vnc/ssl.html + 573. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 574. http://www.karlrunge.com/x11vnc/ssl.html + 575. http://www.karlrunge.com/x11vnc/index.html#viewer-side-stunnel + 576. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 577. http://www.karlrunge.com/x11vnc/ssvnc.html + 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 580. http://sc.uvnc.com/javaviewer/index.html + 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 582. http://www.karlrunge.com/x11vnc/index.html#ssl-router-redir + 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 584. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal + 585. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy + 586. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal + 587. http://www.karlrunge.com/x11vnc/index.html#firewalls + 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpport + 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 592. http://www.karlrunge.com/x11vnc/ssl-output.html 593. http://www.karlrunge.com/x11vnc/ssvnc.html - 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir - 595. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 596. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer - 597. http://www.karlrunge.com/x11vnc/ssvnc.html - 598. http://www.karlrunge.com/x11vnc/ssl-portal.html - 599. http://www.karlrunge.com/x11vnc/ssl.html - 600. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 601. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 602. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin - 603. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop - 604. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset - 605. http://www.karlrunge.com/x11vnc/index.html#firewalls - 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 607. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris - 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N - 609. http://www.jirka.org/gdm-documentation/x241.html - 610. http://www.karlrunge.com/x11vnc/x11vnc_loop - 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 612. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 613. http://www.karlrunge.com/x11vnc/index.html#firewalls - 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 617. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin - 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi - 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns - 620. http://www.avahi.org/ - 621. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 624. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd - 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 631. http://www.karlrunge.com/x11vnc/find_display.html - 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 635. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords - 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 638. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 640. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 642. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 643. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer - 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 594. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 595. http://www.karlrunge.com/x11vnc/ss_vncviewer + 596. http://www.karlrunge.com/x11vnc/ssl-portal.html + 597. http://www.karlrunge.com/x11vnc/ssl.html + 598. http://www.karlrunge.com/x11vnc/ssvnc.html + 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpsredir + 600. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 601. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 602. http://www.karlrunge.com/x11vnc/ssvnc.html + 603. http://www.karlrunge.com/x11vnc/ssl-portal.html + 604. http://www.karlrunge.com/x11vnc/ssl.html + 605. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 606. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 607. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin + 608. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 609. http://club.mandriva.com/xwiki/bin/view/KB/XwinXset + 610. http://www.karlrunge.com/x11vnc/index.html#firewalls + 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 612. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris + 613. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 614. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-N + 618. http://www.jirka.org/gdm-documentation/x241.html + 619. http://www.karlrunge.com/x11vnc/x11vnc_loop + 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 621. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 622. http://www.karlrunge.com/x11vnc/index.html#firewalls + 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 626. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin + 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-avahi + 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-mdns + 629. http://www.avahi.org/ + 630. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 633. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd + 634. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 636. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 638. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 640. http://www.karlrunge.com/x11vnc/find_display.html + 641. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 642. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 644. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 647. http://www.karlrunge.com/x11vnc/faq-linuxvc - 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 651. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 654. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy - 655. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 656. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit - 658. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect - 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 660. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy - 662. http://www.karlrunge.com/x11vnc/index.html#localaccess - 663. http://www.karlrunge.com/x11vnc/index.html#localaccess - 664. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay - 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 671. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay - 672. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 673. http://www.karlrunge.com/x11vnc/Xdummy - 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 675. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 676. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay - 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT - 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find - 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create - 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc - 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc - 682. http://www.karlrunge.com/x11vnc/shm_clear - 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 684. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 685. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb - 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 691. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 697. http://www.tightvnc.com/ - 698. http://www.karlrunge.com/x11vnc/ssvnc.html - 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds - 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 704. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 706. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 708. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 710. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout - 713. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 714. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 717. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 718. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 719. http://linpvr.org/minimyth/ - 720. http://www.karlrunge.com/x11vnc/index.html#faq-beryl - 721. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 722. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 723. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 724. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 725. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 726. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 727. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 728. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect - 729. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 647. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 650. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 651. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 652. http://www.karlrunge.com/x11vnc/index.html#ss_vncviewer + 653. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 655. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 656. http://www.karlrunge.com/x11vnc/faq-linuxvc + 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 658. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 660. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 663. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy + 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect_or_exit + 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-proxy + 671. http://www.karlrunge.com/x11vnc/index.html#localaccess + 672. http://www.karlrunge.com/x11vnc/index.html#localaccess + 673. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay + 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 680. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay + 681. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 682. http://www.karlrunge.com/x11vnc/Xdummy + 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 684. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 685. http://www.karlrunge.com/x11vnc/index.html#findcreatedisplay + 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-find + 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-create + 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-svc + 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xdmsvc + 691. http://www.karlrunge.com/x11vnc/shm_clear + 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 694. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sb + 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 700. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 702. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 703. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 704. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 705. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 706. http://www.tightvnc.com/ + 707. http://www.karlrunge.com/x11vnc/ssvnc.html + 708. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 710. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 711. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds + 712. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 713. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 714. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 715. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 716. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 717. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 718. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 719. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 720. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 721. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout + 722. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 723. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 724. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 725. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 726. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 727. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 728. http://linpvr.org/minimyth/ + 729. http://www.karlrunge.com/x11vnc/index.html#faq-beryl 730. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 731. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 732. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 733. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 734. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 735. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 736. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 737. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect - 738. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 739. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 740. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip - 741. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 742. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 743. http://www.karlrunge.com/x11vnc/index.html#beta-test - 744. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 745. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop - 746. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap - 747. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr - 748. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 749. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 750. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 751. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode - 752. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 753. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 754. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 755. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 756. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 757. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 758. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 759. http://www.karlrunge.com/x11vnc/ssvnc.html - 760. http://www.tightvnc.com/ - 761. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 762. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 763. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 764. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 765. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 766. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer - 767. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 768. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 769. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 770. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 771. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 772. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 773. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 774. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 775. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 776. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 777. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 778. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 779. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 780. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 781. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 782. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 783. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 784. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 785. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 786. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 787. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 788. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 789. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 790. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 791. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 792. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 793. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 794. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 731. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 732. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 733. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 734. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 735. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 736. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe + 737. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect + 738. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 739. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 740. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 741. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 742. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 743. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 744. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 745. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 746. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect + 747. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe + 748. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 749. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip + 750. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 751. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 752. http://www.karlrunge.com/x11vnc/index.html#beta-test + 753. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache + 754. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 755. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap + 756. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 757. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 758. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 759. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 760. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode + 761. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 762. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 763. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 764. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 765. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 766. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 767. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 768. http://www.karlrunge.com/x11vnc/ssvnc.html + 769. http://www.tightvnc.com/ + 770. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 771. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 772. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 773. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 774. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 775. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 776. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 777. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 778. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 779. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 780. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 781. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 782. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 783. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 784. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 785. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 786. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 787. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 788. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 789. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 790. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 791. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 792. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 793. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 794. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes 795. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 796. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock - 797. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 798. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 799. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 800. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 801. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 802. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 803. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 796. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 797. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 798. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 799. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 800. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 801. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 802. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 803. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods 804. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 805. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 806. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 807. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 808. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 809. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 810. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 811. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 812. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html - 813. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 814. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 815. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 816. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 817. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 818. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 819. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 820. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 821. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 822. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 823. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 824. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 825. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 826. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama - 827. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 828. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 829. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 830. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 831. http://www.karlrunge.com/x11vnc/ssvnc.html - 832. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate - 833. http://www.jwz.org/xscreensaver/man1.html - 834. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms - 835. http://www.beryl-project.org/ - 836. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 837. http://www.dslinux.org/blogs/pepsiman/?p=73 - 838. http://linpvr.org/minimyth/ - 839. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 840. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb - 841. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 842. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 843. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 844. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 845. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 846. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 847. http://www.karlrunge.com/x11vnc/index.html#faq-video - 848. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 849. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded - 850. http://www.karlrunge.com/x11vnc/index.html#faq-video - 851. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 852. http://www.karlrunge.com/x11vnc/index.html#faq-video - 853. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 854. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded - 855. http://www.karlrunge.com/x11vnc/index.html#faq-vmware - 856. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 857. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb - 858. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 859. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 860. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 861. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 862. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 863. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab - 864. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb - 865. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 866. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 867. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 868. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 869. http://www.redstonesoftware.com/vnc.html - 870. http://www.apple.com/remotedesktop/ - 871. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 872. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 873. http://fredrik.hubbe.net/x2vnc.html - 874. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc - 875. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 805. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock + 806. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 807. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 808. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 809. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 810. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 811. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 812. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 813. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 814. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 815. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 816. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 817. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 818. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 819. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 820. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 821. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html + 822. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 823. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 824. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 825. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 826. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 827. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 828. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 829. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 830. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 831. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 832. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 833. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 834. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 835. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama + 836. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 837. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 838. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 839. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 840. http://www.karlrunge.com/x11vnc/ssvnc.html + 841. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 842. http://www.jwz.org/xscreensaver/man1.html + 843. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 844. http://www.beryl-project.org/ + 845. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 846. http://www.dslinux.org/blogs/pepsiman/?p=73 + 847. http://linpvr.org/minimyth/ + 848. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 849. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 850. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 851. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 852. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 853. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 854. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 855. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 856. http://www.karlrunge.com/x11vnc/index.html#faq-video + 857. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 858. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded + 859. http://www.karlrunge.com/x11vnc/index.html#faq-video + 860. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 861. http://www.karlrunge.com/x11vnc/index.html#faq-video + 862. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 863. http://www.karlrunge.com/x11vnc/index.html#faq-qt-embedded + 864. http://www.karlrunge.com/x11vnc/index.html#faq-vmware + 865. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 866. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 867. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 868. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 869. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 870. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 871. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 872. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 873. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 874. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 875. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput 876. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 877. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 878. http://sourceforge.net/projects/vnc-reflector/ - 879. http://www.tightvnc.com/projector/ - 880. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 881. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 882. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 883. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 884. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 885. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 886. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 887. http://www.unixuser.org/~euske/vnc2swf/ - 888. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ - 889. http://www.karlrunge.com/x11vnc/ssvnc.html - 890. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer - 891. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 892. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer - 893. http://www.karlrunge.com/x11vnc/ssvnc.html - 894. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext - 895. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 896. http://www.uvnc.com/addons/repeater.html - 897. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 898. http://www.uvnc.com/addons/singleclick.html - 899. http://www.karlrunge.com/x11vnc/index.html#faq-macosx - 900. http://www.karlrunge.com/x11vnc/single-click.html - 901. http://www.karlrunge.com/x11vnc/single-click.html - 902. http://www.karlrunge.com/x11vnc/index.html#firewalls - 903. http://sc.uvnc.com/ - 904. http://www.karlrunge.com/x11vnc/ssvnc.html - 905. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 906. http://www.karlrunge.com/x11vnc/single-click.html - 907. http://www.karlrunge.com/x11vnc/ssvnc.html - 908. http://www.karlrunge.com/x11vnc/single-click.html - 909. http://www.karlrunge.com/x11vnc/ssl.html + 877. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 878. http://www.redstonesoftware.com/vnc.html + 879. http://www.apple.com/remotedesktop/ + 880. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 881. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 882. http://fredrik.hubbe.net/x2vnc.html + 883. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc + 884. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 885. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 886. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 887. http://sourceforge.net/projects/vnc-reflector/ + 888. http://www.tightvnc.com/projector/ + 889. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 890. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 891. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 892. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 893. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 894. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 895. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 896. http://www.unixuser.org/~euske/vnc2swf/ + 897. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ + 898. http://www.karlrunge.com/x11vnc/ssvnc.html + 899. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 900. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 901. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 902. http://www.karlrunge.com/x11vnc/ssvnc.html + 903. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 904. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 905. http://www.uvnc.com/addons/repeater.html + 906. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 907. http://www.uvnc.com/addons/singleclick.html + 908. http://www.karlrunge.com/x11vnc/index.html#faq-macosx + 909. http://www.karlrunge.com/x11vnc/single-click.html 910. http://www.karlrunge.com/x11vnc/single-click.html - 911. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems - 912. http://www.samba.org/ + 911. http://www.karlrunge.com/x11vnc/index.html#firewalls + 912. http://sc.uvnc.com/ 913. http://www.karlrunge.com/x11vnc/ssvnc.html - 914. http://www.cups.org/ - 915. http://www.karlrunge.com/x11vnc/ssvnc.html + 914. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 915. http://www.karlrunge.com/x11vnc/single-click.html 916. http://www.karlrunge.com/x11vnc/ssvnc.html - 917. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 918. http://www.karlrunge.com/x11vnc/index.html#faq-sound - 919. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 920. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html + 917. http://www.karlrunge.com/x11vnc/single-click.html + 918. http://www.karlrunge.com/x11vnc/ssl.html + 919. http://www.karlrunge.com/x11vnc/single-click.html + 920. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 921. http://www.samba.org/ + 922. http://www.karlrunge.com/x11vnc/ssvnc.html + 923. http://www.cups.org/ + 924. http://www.karlrunge.com/x11vnc/ssvnc.html + 925. http://www.karlrunge.com/x11vnc/ssvnc.html + 926. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 927. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 928. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 929. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -10946,6 +10978,9 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) [9]http://www.debian.org/security/2008/dsa-1571 for details. The same applies to SSH keys. + Please read this information on using SSVNC on workstations with + [10]Untrusted Local Users. + _________________________________________________________________ Wrappers and a tcl/tk GUI were written and patches were created for @@ -10956,7 +10991,7 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) * Ability to Save and Load VNC profiles for different hosts. * Create or Import SSL Certificates and Private Keys. * Reverse (viewer listening) VNC connections via SSL and SSH. - * Support for Web [10]Proxies, SOCKS Proxies, and the [11]UltraVNC + * Support for Web [11]Proxies, SOCKS Proxies, and the [12]UltraVNC repeater proxy (e.g. repeater://host:port+ID:1234). Multiple proxies may be chained together (3 max). * Support for SSH Gateway connections and non-standard SSH ports. @@ -10972,20 +11007,20 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) * Support for native MacOS X usage with bundled Chicken of the VNC viewer (the Unix X11 viewer is also provided for MacOS X, and is better IMHO). - * [12]Dynamic VNC Server Port determination and redirection (using + * [13]Dynamic VNC Server Port determination and redirection (using ssh's builtin SOCKS proxy, ssh -D) for servers like x11vnc that print out PORT= at startup. * Unix Username and Password entry for use with "x11vnc -unixpw" type login dialogs. - * Simplified mode launched by command "[13]sshvnc" that is SSH Only. - * Simplified mode launched by command "[14]tsvnc" that provides a + * Simplified mode launched by command "[14]sshvnc" that is SSH Only. + * Simplified mode launched by command "[15]tsvnc" that provides a VNC "Terminal Services" mode (uses x11vnc on the remote side). - [15]Unix TightVNC Viewer improvements (these only apply to the Unix + [16]Unix TightVNC Viewer improvements (these only apply to the Unix VNC viewer): * rfbNewFBSize VNC support (dynamic screen resizing) * ZRLE VNC encoding support (RealVNC's encoding) - * Cursor [16]alphablending with x11vnc at 32bpp (-alpha option) + * Cursor [17]alphablending with x11vnc at 32bpp (-alpha option) * Option "-unixpw ..." for use with "x11vnc -unixpw" type login dialogs. * Support for UltraVNC extensions: 1/n Server side scaling, Text @@ -10994,20 +11029,26 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) * UltraVNC File Transfer via an auxiliary Java helper program (java must be in $PATH). Note that x11vnc supports UltraVNC file transfer. - * Connection support for the [17]UltraVNC repeater proxy (-repeater + * Connection support for the [18]UltraVNC repeater proxy (-repeater option). + * Support for UltraVNC [19]Single Click operation. (both + unencrypted: SC I, and SSL encrypted: SC III) + * 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 + domain sockets, e.g. /path/to/unix/socket, work too. * Extremely low color modes: 64 and 8 colors in 8bpp (-use64/-bgr222, -use8/-bgr111) * Medium color mode: 16bpp mode on a 32bpp Viewer display (-16bpp/-bgr565) - * For use with x11vnc's [18]client-side caching -ncache method use + * For use with x11vnc's [20]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 autodetected by default). * Scrollbar width setting: -sbwidth n, the default is very thin, 2 pixels, for less distracting -ycrop usage. - * Improvements to the [19]Popup menu, all of these can now be + * Improvements to the [21]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), @@ -11149,14 +11190,14 @@ Windows: (the Mac OS X and Unix launchers are simply links to the bin directory). See the README for more information. - The [20]SSH-Only mode launcher program has name sshvnc. The - [21]Terminal Services mode launcher program (assumes x11vnc 0.8.4 or + The [22]SSH-Only mode launcher program has name sshvnc. The + [23]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 [22]this FAQ + bin/ssvnc program is a GUI front-end to that script. See [24]this FAQ for more details on SSL tunnelling. In SSH connection mode, the wrappers start up SSH appropriately. @@ -11203,7 +11244,7 @@ start \ssvnc\Windows\ssvnc.exe switch from the regular SSVNC mode, click "Terminal Services" under Options. - This mode requires [23]x11vnc (0.9.3 or later) installed on the remote + This mode requires [25]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 @@ -11221,7 +11262,7 @@ start \ssvnc\Windows\ssvnc.exe press "Connect"). Normally the Terminal Services sessions created are virtual (RAM-only) - ones (e.g. Xvfb, [24]Xdummy, or Xvnc), however a nice feature is if + ones (e.g. Xvfb, [26]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. @@ -11242,7 +11283,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 [25]more about SSVNC proxy support here. + in the same way. Read [27]more about SSVNC proxy support here. Dynamic VNC Server Port determination: If you are running SSVNC on @@ -11269,7 +11310,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 [26]-rfbport option is passed to x11vnc (it does not work with + and the [28]-rfbport option is passed to x11vnc (it does not work with vncserver). @@ -11280,7 +11321,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 [27]described here. + The cursor alphablending is [29]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 @@ -11290,7 +11331,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 [28]client-side caching is handled + Client Side Caching: The x11vnc [30]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 @@ -11303,17 +11344,19 @@ 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 [29]grabserver patch for old + Probably nobody is interested in the [31]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 made smaller). From the -help output: -TightVNC viewer version 1.3.9 (SSVNC) +SSVNC Viewer (based on TightVNC viewer version 1.3.9) Usage: ./vncviewer [<OPTIONS>] [<HOST>][:<DISPLAY#>] ./vncviewer [<OPTIONS>] [<HOST>][::<PORT#>] + ./vncviewer [<OPTIONS>] exec=[CMD ARGS...] + ./vncviewer [<OPTIONS>] /path/to/unix/socket ./vncviewer [<OPTIONS>] -listen [<DISPLAY#>] ./vncviewer -help @@ -11350,6 +11393,21 @@ Enhanced TightVNC viewer (SSVNC) options: Note: F9 is shortcut to Toggle FullScreen mode. + Note: In -listen mode set the env var. SSVNC_MULTIPLE_LISTEN=1 + to allow more than one incoming VNC server at a time. + + Note: If the host:port is specified as "exec=command args..." + then instead of making a TCP/IP socket connection to the + remote VNC server, "command args..." is executed and the + viewer is attached to its stdio. This enables tunnelling + established via an external command, e.g. an stunnel(8) + that does not involve a listening socket. This mode does + not work for -listen reverse connections. + + Note: If the host:port contains a '/' it is interpreted as a + unix-domain socket (AF_LOCAL insead of AF_INET) + + -use64 In -bgr233 mode, use 64 colors instead of 256. -bgr222 Same as -use64. @@ -11444,8 +11502,18 @@ Enhanced TightVNC viewer (SSVNC) options: -repeater str This is for use with UltraVNC repeater proxy described here: http://www.uvnc.com/addons/repeater.html. The "str" is the ID string to be sent to the repeater. E.g. ID:1234 - In this case host:dpy on the command line is the repeater - server, not the VNC server. The repeater will connect you. + It can also be the hostname and port or display of the VNC + server, e.g. 12.34.56.78:0 or snoopy.com:1. Note that when + using -repeater, the host:dpy on the cmdline is the repeate +r + server, NOT the VNC server. The repeater will connect you. + Example: vncviewer ... -repeater ID:3333 repeat.host:5900 + Example: vncviewer ... -repeater vhost:0 repeat.host:5900 + + -printres Print out the Ssvnc X resources (appdefaults) and then exit + You can save them to a file and customize them (e.g. the + keybindings and Popup menu) Then point to the file via + XENVIRONMENT or XAPPLRESDIR. New Popup actions: @@ -11505,7 +11573,7 @@ Enhanced TightVNC viewer (SSVNC) options: _________________________________________________________________ Hopefully this tool will make it convenient for people to help test - and use the [30]built-in SSL support in x11vnc. Extra testing of this + and use the [32]built-in SSL support in x11vnc. Extra testing of this feature is much appreciated!! Thanks. Please Help Test the newly added features: @@ -11518,41 +11586,53 @@ Enhanced TightVNC viewer (SSVNC) options: 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: - [31]http://www.karlrunge.com/x11vnc/#faq-smb-shares - [32]http://www.karlrunge.com/x11vnc/#faq-cups - [33]http://www.karlrunge.com/x11vnc/#faq-sound + [33]http://www.karlrunge.com/x11vnc/#faq-smb-shares + [34]http://www.karlrunge.com/x11vnc/#faq-cups + [35]http://www.karlrunge.com/x11vnc/#faq-sound _________________________________________________________________ Downloading: This project can be downloaded here, choose the archive file bundle that best suits you (e.g. no source code, windows only, unix only, zip, tar etc): - [34]ssvnc_windows_only-1.0.20.zip Windows Binaries Only. No source incl + [36]ssvnc_windows_only-1.0.20.zip Windows Binaries Only. No source incl uded (~6MB) - [35]ssvnc_no_windows-1.0.20.tar.gz Unix and Mac OS X Only. No Windows bin + [37]ssvnc_no_windows-1.0.20.tar.gz Unix and Mac OS X Only. No Windows bin aries. Source included. (~6MB) - [36]ssvnc_unix_only-1.0.20.tar.gz Unix Binaries Only. No source incl + [38]ssvnc_unix_only-1.0.20.tar.gz Unix Binaries Only. No source incl uded. (~3.5MB) - [37]ssvnc_unix_minimal-1.0.20.tar.gz Unix Minimal. You must supply your ow + [39]ssvnc_unix_minimal-1.0.20.tar.gz Unix Minimal. You must supply your ow n vncviewer and stunnel. (~0.1MB) - [38]ssvnc-1.0.20.tar.gz All Unix, Mac OS X, and Windows binari + [40]ssvnc-1.0.20.tar.gz All Unix, Mac OS X, and Windows binari es and source TGZ. (~11MB) - [39]ssvnc-1.0.20.zip All Unix, Mac OS X, and Windows binari + [41]ssvnc-1.0.20.zip All Unix, Mac OS X, and Windows binari es and source ZIP. (~11MB) - [40]ssvnc_all-1.0.20.zip All Unix, Mac OS X, and Windows binari + [42]ssvnc_all-1.0.20.zip All Unix, Mac OS X, and Windows binari es and source AND full archives in the zip dir. (~15MB) - You can try for an older one by replacing, e.g. ".20" by ".15", etc. + You can try for an older one by replacing, e.g. ".20" by ".19", etc. + + Here is a conventional source tarball: + [43]ssvnc-1.0.20.src.tar.gz Conventional Source for Unix VNCviewer + (~0.4MB) + + it will be of use to those who do not want the SSVNC + "one-size-fits-all" bundles. For example, package/distro maintainers + will find this more familiar and useful to them (i.e. they run: "make + config; make all; make install"). Note that it does not include the + stunnel source, and so has a dependency that the system stunnel is + installed. Read the [44]README.src file for more information on using + the source tarball. Here are the corresponding development bundles: - Coming soon... + Coming soon... 1.0.21... Please help test the UltraVNC File Transfer support in the native Unix VNC viewer! Let us know how it went. A self-extracting and running file for the "ssvnc_unix_minimal" - package is here: [41]ssvnc. Save it as filename "ssvnc", type "chmod + package is here: [45]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 example, install your distros' @@ -11593,558 +11673,16 @@ es and source AND full archives in the zip dir. (~15MB) 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: - [42]http://www.stunnel.org - [43]http://stunnel.mirt.net - [44]http://www.openssl.org - [45]http://www.chiark.greenend.org.uk/~sgtatham/putty/ - [46]http://www.tightvnc.com - [47]http://www.realvnc.com - [48]http://sourceforge.net/projects/cotvnc/ + [46]http://www.stunnel.org + [47]http://stunnel.mirt.net + [48]http://www.openssl.org + [49]http://www.chiark.greenend.org.uk/~sgtatham/putty/ + [50]http://www.tightvnc.com + [51]http://www.realvnc.com + [52]http://sourceforge.net/projects/cotvnc/ _________________________________________________________________ - Here is the toplevel README from the bundle: - Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) - -Copyright (c) 2006-2008 Karl J. Runge -All rights reserved. - -These bundles provide 1) An enhanced TightVNC Viewer on Unix, 2) Binaries -for many Operating Systems (including Windows and Mac OS X) for your -convenience, 3) Wrapper scripts and a GUI for gluing them all together. - -One can straight-forwardly download all of the components and get them -to work together by oneself: this bundle is mostly for your convenience -to combine and wrap together the freely available software. - -Bundled software co-shipped is copyright and licensed by others. -See these sites and related ones for more information: - - http://www.tightvnc.com - http://www.realvnc.com - http://www.stunnel.org - http://stunnel.mirt.net - http://www.openssl.org - http://www.chiark.greenend.org.uk/~sgtatham/putty/ - http://sourceforge.net/projects/cotvnc/ - -Note: Some of the binaries included contain cryptographic software that -you may not be allowed to download, use, or redistribute. Please check -your situation first before downloading any of these bundles. See the -survey http://rechten.uvt.nl/koops/cryptolaw/index.htm for useful -information. - -All work done by Karl J. Runge in this project is -Copyright (c) 2006-2007 Karl J. Runge and is licensed under the GPL as -described in the file COPYING in this directory. - -All the files and information in this project are provided "AS IS" -without any warranty of any kind. Use them at your own risk. - - -============================================================================= - -This bundle contains a convenient collection of enhanced TightVNC -viewers and stunnel binaries for different flavors of Unix and wrapper -scripts and a GUI front-end to glue them together. Automatic SSL and -SSH encryption tunnelling is provided. - -A Windows SSL wrapper for the bundled TightVNC binary and other utilities -are provided. (Launch ssvnc.exe in the Windows subdirectory). - -The short name of the project is "ssvnc" for SSL/SSH VNC Viewer. - -It is a self-contained bundle, you could carry it around on, say, -a USB memory stick for secure VNC viewing from almost any machine, -Unix, Mac, or Windows. - -Features: --------- - -The enhanced TightVNC viewer features are: - - - SSL support for connections using the bundled stunnel program. - - - Automatic SSH connections from the GUI (ssh must already be - installed on Unix; bundled plink is used on Windows) - - - Ability to Save and Load VNC profiles for different hosts. - - - Create or Import SSL Certificates and Private Keys. - - - Automatic Service tunnelling via SSH for CUPS and SMB Printing, - ESD/ARTSD Audio, and SMB (Windows/Samba) filesystem mounting. - - - Port Knocking for "closed port" SSH/SSL connections. In addition - to a simple fixed port sequence and one-time-pad implementation, - a hook is also provided to run any port knocking client before a - connecting. - - - You can also use your own VNC Viewer, e.g. UltraVNC or RealVNC, - with the front-end GUI or scripts if you like. - - - Sets up any additional SSH port redirections that you want. - - - Support for native MacOS X usage with bundled Chicken of the - VNC viewer. - - - Reverse (viewer listening) VNC connections via SSL and SSH. - - - Dynamic VNC Server Port determination and redirection (using - ssh's builtin SOCKS proxy, -D) for servers like x11vnc that - print out PORT= at startup. - - - Unix Username and Password entry for use with "x11vnc -unixpw" - type login dialogs. - - - Simplified mode launched by command "sshvnc" that is SSH Only. - - - Simplified mode launched by command "tsvnc" that provides a VNC - "Terminal Services" mode (uses x11vnc on the remote side). - - - (the following features only apply to the bundled Unix tightvnc viewer) - - - rfbNewFBSize VNC support (screen resizing) - - - ZRLE VNC encoding support (RealVNC's encoding) - - - Cursor alphablending with x11vnc at 32bpp (-alpha option) - - - Option "-unixpw ..." for use with "x11vnc -unixpw" login dialogs. - - - Support for UltraVNC extensions: Single Window, Disable - Server-side Input, 1/n Server side scaling, Text Chat (shell - terminal UI). Both UltraVNC and x11vnc servers support these - extensions - - - UltraVNC File Transfer via an auxiliary Java helper program - (java must be in $PATH). Note that x11vnc supports UltraVNC - file transfer. - - - Extremely low color modes: 64 and 8 colors in 8bpp - (-use64/-bgr222, -use8/-bgr111) - - - Medium color mode: 16bpp mode even for 32bpp Viewer display - (-16bpp/-bgr565) - - - x11vnc's client-side caching -ncache method cropping option - (-ycrop n). This will "hide" the large pixel buffer cache - below the actual display. Set to actual height or use -1 for - autodetection (tall screens are autodetected by default). - - - Scrollbar width setting: -sbwidth n, the default is very thin, - 2 pixels, for less distracting -ycrop usage. - - - Improvements to the 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. - - - Maintains its own BackingStore if the X server does not - - - The default for localhost:0 connections is not raw encoding - (local machine). Default assumes you are using SSH tunnel. Use - -rawlocal to revert. - - - Support for the ZYWRLE encoding, a wavelet based extension to - ZRLE to improve compression of motion video and photo regions. - - - XGrabServer support for fullscreen mode, for old window managers - (-grab/-graball option). - - - Fix for Popup menu positioning for old window managers - (-popupfix option). - - - Run vncviewer -help for all options. - - - -The list of software bundled in the archive files: - - TightVNC Viewer (windows, unix, macosx) - Chicken of the VNC Viewer (macosx) - Stunnel (windows, unix, macosx) - Putty/Plink/Pageant (windows) - OpenSSL (windows) - esound (windows) - -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 it straight from its directory. - - -Quick Start: ------------ - -Unix and Mac OS X: - - Inside a Terminal do something like the following. - - Unpack the archive: - - % gzip -dc ssvnc-1.0.20.tar.gz | tar xvf - - - Run the GUI: - - % ./ssvnc/Unix/ssvnc (for Unix) - - % ./ssvnc/MacOSX/ssvnc (for Mac OS X) - - The smaller file "ssvnc_no_windows-1.0.20.tar.gz" - could have been used as well. - - On MacOSX you could also click on the SSVNC app icon in the Finder. - - On MacOSX if you don't like the Chicken of the VNC (e.g. no local - cursors, no screen size rescaling, and no password prompting), and you - have the XDarwin X server installed, you can set DISPLAY before starting - ssvnc (or type DISPLAY=... in Host:Disp and hit Return). Then our - enhanced TightVNC viewer will be used instead of COTVNC. - Update: there is now a 'Use X11 vncviewer on MacOSX' under Options ... - - - If you want a SSH-only tool (without the distractions of SSL) run - the command: - - sshvnc - - instead of "ssvnc". Or click "SSH-Only Mode" under Options. - Control-h will toggle between the two modes. - - - If you want a simple VNC Terminal Services only mode (requires x11vnc - on the remote server) run the command: - - tsvnc - - instead of "ssvnc". Or click "Terminal Services" under Options. - Control-t will toggle between the two modes. - - "tsvnc profile-name" and "tsvnc user@hostname" work too. - - -Unix/MacOSX Install: - - There is no standard install, but you can make symlinks like so: - - cd /a/directory/in/PATH - ln -s /path/to/ssvnc/bin/{s,t}* . - - Or put /path/to/ssvnc/bin, /path/to/ssvnc/Unix, or /path/to/ssvnc/MacOSX - in your PATH. - - -Windows: - - Unzip, using WinZip or a similar utility, the zip file: - - ssvnc-1.0.20.zip - - Run the GUI, e.g.: - - Start -> Run -> Browse - - and then navigate to - - .../ssvnc/Windows/ssvnc.exe - - select Open, and then OK to launch it. - - The smaller file "ssvnc_windows_only-1.0.20.zip" - could have been used as well. - - You can make a Windows shortcut to this program if you want to. - - See the Windows/README.txt for more info. - - - If you want a SSH-only tool (without the distractions of SSL) run - the command: - - sshvnc.bat - - Or click "SSH-Only Mode" under Options. - - - If you want a simple VNC Terminal Services only mode (requires x11vnc - on the remote server) run the command: - - tsvnc.bat - - Or click "Terminal Services" under Options. Control-t will toggle - between the two modes. "tsvnc profile-name" and "tsvnc user@hostname" - work too. - - - -Important Note for Windows Vista: One user reports that on Windows Vista -if you move or extract the "ssvnc" folder down to the "Program Files" -folder you will be prompted to do this as the Administrator. But then -when you start up ssvnc, as a regular user, it cannot create files in -that folder and so it fails to run properly. We recommend to not copy -or extract the "ssvnc" folder into "Program Files". Rather, extract -it to somewhere you have write permission (e.g. C:\ or your User dir) -and create a Shortcut to ssvnc.exe on the desktop. - -If you must put a launcher file down in "Program Files", perhaps an -"ssvnc.bat" that looks like this: - -C: -cd \ssvnc\Windows -ssvnc.exe - - -SSH-ONLY Mode: --------------- - -If you don't care for SSL and the distractions it provides in the GUI, -run "sshvnc" (unix/macosx) or "sshvnc.bat" (windows) to run an SSH only -version of the GUI. - -Terminal Services Mode ----------------------- - -There is an even simpler mode that uses x11vnc on the remote side for the -session finding and management. Run "tsvnc" (unix/macosx) or "tsvnc.bat" -(windows) to run the Terminal Services version of the GUI. - - -Bundle Info: ------------- - -The bundle files unpack a directory/folder named: ssvnc - -It contains these programs to launch the GUI: - - Windows/ssvnc.exe for Windows - MacOSX/ssvnc for Mac OS X - Unix/ssvnc for Unix - -(the Mac OS X and Unix launchers are simply links to the bin directory). - - -Your bundle file should have included binaries for many OS's: Linux, -Solaris, FreeBSD, etc. Unpack your archive and see the subdirectories of - - ./bin - -for the ones that were shipped in this project, e.g. ./bin/Linux.i686 -Run "uname -sm" to see your OS+arch combination (n.b. all Linux x86 are -mapped to Linux.i686). (See the ./bin/ssvnc_cmd -h output for how to -override platform autodection via the UNAME env. var). - - -Memory Stick Usage: -------------------- - -If you create a directory named "Home" in that toplevel ssvnc directory -then that will be used as the base for storing VNC profiles and -certificates. Also, for convenience, if you first run the command with -"." as an argument (e.g. "ssvnc .") it will automatically create that -"Home" directory for you. This is handy if you want to place SSVNC -on a USB flash drive that you carry around for mobile use and you want -the profiles you create to stay with the drive (otherwise you'd have to -browse to the drive directory each time you load or save). - -One user on Windows created a BAT file to launch SSVNC and needed to -do this to get the Home directory correct: - -cd \ssvnc\Windows -start \ssvnc\Windows\ssvnc.exe - -(an optional profile name can be supplied to the ssvnc.exe line) - -WARNING: if you use ssvnc from an "Internet Cafe", i.e. an untrusted -computer, an intruder may be capturing keystrokes etc. - - -External Dependencies: ----------------------- - -On Windows everything is included. Let us know if you find otherwise. - -On Unix depending on what you do you need these programs installed: - - - basic unix utilities (sh, ls, cat, awk, sed, etc..) - - tcl/tk (wish interpreter) - - xterm - - perl - - ssh - - openssl - - Lesser used ones: netcat, esd/artsd, smbclient, smbmount, cups - -On Mac OS X depending on what you do you need these programs installed: - - - basic unix utilities (sh, ls, cat, awk, sed, etc..) - - tcl/tk (wish interpreter) - - Terminal - - perl - - ssh - - openssl - - Lesser used ones: netcat, smbclient, cups - - -Most Mac OS X and Unix OS come with the main components installed. - - -If you need to Build: --------------------- - -If your OS/arch is not included or the provided binary has the wrong -library dependencies, etc. the script "build.unix" may be able to -successfully build on for you and deposit the binaries down in ./bin/... -using the included source code. - -You MUST run the build.unix script from this directory (that this toplevel -README is in, i.e "ssvnc") and like this: - - ./build.unix - -To use custom locations for libraries see the LDFLAGS_OS and CPPFLAGS_OS -description at the top of the build.unix script. - -Feel free to ask us if you need help running ./build.unix - - -The programs: ------------- - -Unpack your archive, and you will see "bin", "Windows", "src" directories -and other files. The command line wrapper scripts: - - ./bin/ssvnc_cmd - ./bin/tightvncviewer - -are the main programs that are run and will try to autodetect your OS+arch -combination and if binaries are present for it automatically use them. -(if not found try the running the build.unix script). - -If you prefer a GUI to prompt for parameters and then start ssvnc_cmd -you can run this instead: - - ./bin/ssvnc - -this is the same GUI that is run on Windows (the ssvnc.exe). -There are also: - - ./bin/sshvnc (SSH-Only) - ./bin/tsvnc (Terminal Services Mode) - -For convenience, you can make symlinks from a directory in your PATH to -any of the 3 programs above you wish to run. That is all you usually -need to do for it to pick up all of the binaries, utils, etc. E.g. -assuming $HOME/bin is in your $PATH: - - cd $HOME/bin - ln -s /path/to/ssvnc/bin/{s,t}* . - -(note the "." at the end). The above commands is basically the way to -"install" this on Unix or MacOS X. - -Also links to the GUI launcher script are provided in: - - MacOSX/ssvnc - Unix/ssvnc - -and sshvnc and tsvnc. You could also put the Unix or MacOSX directory -in your PATH. - - -On Windows unpack your archive and run: - - Windows/ssvnc.exe - - -Examples: --------- - -The following assume you are in the toplevel directory of the -archive you unpacked. - -Use enhanced TightVNC unix viewer to connect to x11vnc via SSL: - - ./bin/ssvnc_cmd far-away.east:0 - - ./bin/tightvncviewer -ssl far-away.east:0 (same) - - ./bin/ssvnc (start GUI launcher) - -Use enhanced TightVNC unix viewer without SSL: - - ./bin/tightvncviewer far-away.east:0 - -Use SSL to connect to a x11vnc server, and also verify the server's -identity using the SSL Certificate in the file ./x11vnc.pem: - - ./bin/ssvnc_cmd -alpha -verify ./x11vnc.pem far-away.east:0 - -(also turns on the viewer-side cursor alphablending hack). - - -Brief description of the subdirectories: ---------------------------------------- - - ./bin/util some utility scripts, e.g. ss_vncviewer - and ssvnc.tcl - - ./src source code and patches. - ./src/zips zip files of source code and binaries. - - ./src/vnc_unixsrc unpacked tightvnc source code tree. - ./src/stunnel-4.14 unpacked stunnel source code tree. - ./src/patches patches to TightVNC viewer for the new - features on Unix (used by build.unix). - ./src/tmp temporary build dir for build.unix - (the last four are used by build.unix) - - - ./man man pages for TightVNC viewer and stunnel. - - ./Windows Stock TightVNC viewer and Stunnel, Openssl - etc Windows binaries. ssvnc.exe is the - program to run. - - ./MacOSX contains an unpacked Chicken of the VNC - viewer and a symlink to ssvnc. - - ./Unix contains a symlink to ssvnc. - -Depending on which bundle you use not all of the above may be present. -The smallest bundles with binaries are: - - ssvnc_windows_only-1.x.y.zip Windows - ssvnc_no_windows-1.x.y.tar.gz Unix and MacOSX - -however, the tiny scripts only one (only 60KB) will run properly on Unix -as long as you install external vncviewer and stunnel packages: - - ssvnc_unix_minimal-1.x.y.tar.gz - - -Help and Info: -------------- - -For more help on other options and usage patterns run these: - - ./bin/ssvnc_cmd -h - ./bin/util/ss_vncviewer -h - -See also: - - http://www.karlrunge.com/x11vnc - http://www.karlrunge.com/x11vnc/#faq - x11vnc -h | more - - http://www.stunnel.org - http://stunnel.mirt.net - http://www.openssl.org - http://www.tightvnc.com - http://www.realvnc.com - http://www.chiark.greenend.org.uk/~sgtatham/putty/ - http://sourceforge.net/projects/cotvnc/ + README: Here is the toplevel [53]README from the bundle. References @@ -12157,45 +11695,50 @@ References 7. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc 8. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#memory-stick 9. http://www.debian.org/security/2008/dsa-1571 - 10. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html - 11. http://www.uvnc.com/addons/repeater.html - 12. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#dynamic-port - 13. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc - 14. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc - 15. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#unix-patches - 16. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 17. http://www.uvnc.com/addons/repeater.html - 18. http://www.karlrunge.com/x11vnc/index.html#faq-client-caching - 19. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#popup - 20. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc - 21. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc - 22. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 23. http://www.karlrunge.com/x11vnc/index.html - 24. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 25. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html - 26. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 27. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 28. http://www.karlrunge.com/x11vnc/index.html#faq-client-caching - 29. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars - 30. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 31. http://www.karlrunge.com/x11vnc/index.html#faq-smb-shares - 32. http://www.karlrunge.com/x11vnc/index.html#faq-cups - 33. http://www.karlrunge.com/x11vnc/index.html#faq-sound - 34. http://www.karlrunge.com/x11vnc/etv/ssvnc_windows_only-1.0.20.zip - 35. http://www.karlrunge.com/x11vnc/etv/ssvnc_no_windows-1.0.20.tar.gz - 36. http://www.karlrunge.com/x11vnc/etv/ssvnc_unix_only-1.0.20.tar.gz - 37. http://www.karlrunge.com/x11vnc/etv/ssvnc_unix_minimal-1.0.20.tar.gz - 38. http://www.karlrunge.com/x11vnc/etv/ssvnc-1.0.20.tar.gz - 39. http://www.karlrunge.com/x11vnc/etv/ssvnc-1.0.20.zip - 40. http://www.karlrunge.com/x11vnc/etv/ssvnc_all-1.0.20.zip - 41. http://www.karlrunge.com/x11vnc/etv/ssvnc - 42. http://www.stunnel.org/ - 43. http://stunnel.mirt.net/ - 44. http://www.openssl.org/ - 45. http://www.chiark.greenend.org.uk/~sgtatham/putty/ - 46. http://www.tightvnc.com/ - 47. http://www.realvnc.com/ - 48. http://sourceforge.net/projects/cotvnc/ + 10. http://www.karlrunge.com/x11vnc/ssvnc_untrusted_local_users.html + 11. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html + 12. http://www.uvnc.com/addons/repeater.html + 13. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#dynamic-port + 14. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc + 15. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc + 16. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#unix-patches + 17. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 18. http://www.uvnc.com/addons/repeater.html + 19. http://www.uvnc.com/addons/singleclick.html + 20. http://www.karlrunge.com/x11vnc/index.html#faq-client-caching + 21. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#popup + 22. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#sshvnc + 23. http://www.karlrunge.com/x11vnc/enhanced_tightvnc_viewer.html#tsvnc + 24. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 25. http://www.karlrunge.com/x11vnc/index.html + 26. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 27. http://www.karlrunge.com/x11vnc/ssvnc-proxies.html + 28. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 29. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 30. http://www.karlrunge.com/x11vnc/index.html#faq-client-caching + 31. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars + 32. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 33. http://www.karlrunge.com/x11vnc/index.html#faq-smb-shares + 34. http://www.karlrunge.com/x11vnc/index.html#faq-cups + 35. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 36. http://www.karlrunge.com/x11vnc/etv/ssvnc_windows_only-1.0.20.zip + 37. http://www.karlrunge.com/x11vnc/etv/ssvnc_no_windows-1.0.20.tar.gz + 38. http://www.karlrunge.com/x11vnc/etv/ssvnc_unix_only-1.0.20.tar.gz + 39. http://www.karlrunge.com/x11vnc/etv/ssvnc_unix_minimal-1.0.20.tar.gz + 40. http://www.karlrunge.com/x11vnc/etv/ssvnc-1.0.20.tar.gz + 41. http://www.karlrunge.com/x11vnc/etv/ssvnc-1.0.20.zip + 42. http://www.karlrunge.com/x11vnc/etv/ssvnc_all-1.0.20.zip + 43. http://www.karlrunge.com/x11vnc/etv/ssvnc-1.0.20.src.tar.gz + 44. http://www.karlrunge.com/x11vnc/etv/README.src.txt + 45. http://www.karlrunge.com/x11vnc/etv/ssvnc + 46. http://www.stunnel.org/ + 47. http://stunnel.mirt.net/ + 48. http://www.openssl.org/ + 49. http://www.chiark.greenend.org.uk/~sgtatham/putty/ + 50. http://www.tightvnc.com/ + 51. http://www.realvnc.com/ + 52. http://sourceforge.net/projects/cotvnc/ + 53. http://www.karlrunge.com/x11vnc/README.ssvnc.html ======================================================================= http://www.karlrunge.com/x11vnc/x11vnc_opts.html: @@ -12208,7 +11751,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.4 lastmod: 2008-06-06 +x11vnc: allow VNC connections to real X11 displays. 0.9.4 lastmod: 2008-09-06 x11vnc options: -display disp -auth file -N @@ -12289,11 +11832,12 @@ x11vnc options: -pipeinput cmd -macnodim -macnosleep -macnosaver -macnowait -macwheel n -macnoswap -macnoresize -maciconanim n - -macmenu -gui [gui-opts] -remote command - -query variable -QD variable -sync - -noremote -yesremote -unsafe - -safer -privremote -nocmds - -allowedcmds list -deny_all + -macmenu -macuskbd -gui [gui-opts] + -remote command -query variable -QD variable + -sync -noremote -yesremote + -unsafe -safer -privremote + -nocmds -allowedcmds list -deny_all + libvncserver options: -rfbport port TCP port for RFB protocol @@ -12327,7 +11871,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.4 lastmod: 2008-06-06 +x11vnc: allow VNC connections to real X11 displays. 0.9.4 lastmod: 2008-09-06 (type "x11vnc -opts" to just list the options.) @@ -12792,7 +12336,7 @@ e to plumb reverse connections. -connect_or_exit str As with -connect, except if none of the reverse - connections succeed, then x11vnc shutdowns immediately. + connections succeed, then x11vnc shuts down immediately By the way, if you do not want x11vnc to listen on ANY interface use -rfbport 0 which is handy for the @@ -15934,25 +15478,27 @@ t You can also set the env. var X11VNC_UINPUT_DEBUG=1 or higher to get debugging output for UINPUT mode. --macnodim For the native Mac OS X server, disable dimming. --macnosleep For the native Mac OS X server, disable display sleep. --macnosaver For the native Mac OS X server, disable screensaver. --macnowait For the native Mac OS X server, do not wait for the +-macnodim For the native MacOSX server, disable dimming. +-macnosleep For the native MacOSX server, disable display sleep. +-macnosaver For the native MacOSX server, disable screensaver. +-macnowait For the native MacOSX server, do not wait for the user to switch back to his display. --macwheel n For the native Mac OS X server, set the mouse wheel +-macwheel n For the native MacOSX server, set the mouse wheel speed to n (default 5). --macnoswap For the native Mac OS X server, do not swap mouse +-macnoswap For the native MacOSX server, do not swap mouse buttons 2 and 3. --macnoresize For the native Mac OS X server, do not resize or reset +-macnoresize For the native MacOSX server, do not resize or reset the framebuffer even if it is detected that the screen resolution or depth has changed. --maciconanim n For the native Mac OS X server, set n to the number +-maciconanim n For the native MacOSX server, set n to the number of milliseconds that the window iconify/deiconify animation takes. In -ncache mode this value will be used to skip the animation if possible. (default 400) --macmenu For the native Mac OS X server, in -ncache client-side +-macmenu For the native MacOSX server, in -ncache client-side caching mode, try to cache pull down menus (not perfect because they have animated fades, etc.) +-macuskbd For the native MacOSX server, use the original + keystroke insertion code based on a US keyboard. -gui [gui-opts] Start up a simple tcl/tk gui based on the the remote control options -remote/-query described below. @@ -16010,6 +15556,14 @@ t fully functional, the gui mode should be "start" (the default). + Note that tray or icon mode will imply the -forever + x11vnc option (if the x11vnc server is started along + with the gui) unless -connect or -connect_or_exit has + been specified. So x11vnc (and the tray/icon gui) + will wait for more connections after the first client + disconnects. If you want only one viewer connection + include the -once option. + For "icon" the gui just a small standalone window. For "tray" it will attempt to embed itself in the "system tray" if possible. If "=setpass" is appended the |