diff options
| author | runge <runge> | 2006-06-08 23:06:26 +0000 |
|---|---|---|
| committer | runge <runge> | 2006-06-08 23:06:26 +0000 |
| commit | 1776a3a55f59052bd69509c889e4370973305f0d (patch) | |
| tree | e77c3c0b53a1f15c03bba215c60982bc3e28c727 | |
| parent | a60ee2ee9f73d21c4407136d7a2878a34be2f7ed (diff) | |
| download | libtdevnc-1776a3a5.tar.gz libtdevnc-1776a3a5.zip | |
x11vnc: -display WAIT:..., -users unixpw=, su_verify dpy command.
| -rw-r--r-- | ChangeLog | 5 | ||||
| -rw-r--r-- | prepare_x11vnc_dist.sh | 2 | ||||
| -rw-r--r-- | x11vnc/ChangeLog | 5 | ||||
| -rw-r--r-- | x11vnc/README | 3099 | ||||
| -rw-r--r-- | x11vnc/cleanup.c | 3 | ||||
| -rw-r--r-- | x11vnc/connections.c | 1 | ||||
| -rw-r--r-- | x11vnc/gui.c | 18 | ||||
| -rw-r--r-- | x11vnc/help.c | 170 | ||||
| -rw-r--r-- | x11vnc/options.c | 2 | ||||
| -rw-r--r-- | x11vnc/pointer.c | 1 | ||||
| -rw-r--r-- | x11vnc/remote.c | 4 | ||||
| -rw-r--r-- | x11vnc/screen.c | 10 | ||||
| -rw-r--r-- | x11vnc/solid.c | 1 | ||||
| -rw-r--r-- | x11vnc/sslcmds.c | 1 | ||||
| -rw-r--r-- | x11vnc/sslhelper.c | 3 | ||||
| -rwxr-xr-x | x11vnc/tkx11vnc | 12 | ||||
| -rw-r--r-- | x11vnc/tkx11vnc.h | 12 | ||||
| -rw-r--r-- | x11vnc/unixpw.c | 144 | ||||
| -rw-r--r-- | x11vnc/unixpw.h | 5 | ||||
| -rw-r--r-- | x11vnc/user.c | 237 | ||||
| -rw-r--r-- | x11vnc/user.h | 1 | ||||
| -rw-r--r-- | x11vnc/v4l.c | 1 | ||||
| -rw-r--r-- | x11vnc/win_utils.c | 1 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 839 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 55 | ||||
| -rw-r--r-- | x11vnc/x11vnc.h | 4 | ||||
| -rw-r--r-- | x11vnc/x11vnc_defs.c | 4 | ||||
| -rw-r--r-- | x11vnc/xevents.c | 6 | ||||
| -rw-r--r-- | x11vnc/xkb_bell.c | 5 | ||||
| -rw-r--r-- | x11vnc/xrecord.c | 42 | ||||
| -rw-r--r-- | x11vnc/xwrappers.c | 74 | ||||
| -rw-r--r-- | x11vnc/xwrappers.h | 4 |
32 files changed, 3433 insertions, 1338 deletions
@@ -1,10 +1,13 @@ +2006-06-08 Karl Runge <runge@karlrunge.com> + * prepare_x11vnc_dist.sh: to 0.8.2 + 2006-05-29 Steven Carr <scarr@jsa-usa.com> * Identified and removed some memory leaks associated with the Encodings RRE, CoRRE, ZLIB, and Ultra. * KeyboardLedState now has portable masks defined. * rfb >= 3.7 Security Type Handler list would grow 1 entry for each new client connection. - + 2006-05-16 Steven Carr <scarr@jsa-usa.com> * Statistics output now fits in 80-column output * Corrected Cursor Statistics reporting as messages diff --git a/prepare_x11vnc_dist.sh b/prepare_x11vnc_dist.sh index 08e03a4..3e1afce 100644 --- a/prepare_x11vnc_dist.sh +++ b/prepare_x11vnc_dist.sh @@ -1,6 +1,6 @@ #!/bin/bash -VERSION="0.8.1" +VERSION="0.8.2" cd "$(dirname "$0")" diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index be04a65..ff444e9 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,8 @@ +2006-06-08 Karl Runge <runge@karlrunge.com> + * x11vnc: XOpenDisplay wrapper for raw xauth data, -unixpw + su_verify() to run any cmd, -users unixpw= mode. -display WAIT:... + modes for delayed X display opening and dynamic choosing. + 2006-06-03 Karl Runge <runge@karlrunge.com> * x11vnc: -capslock and -skip_lockkeys options. map some Alt keys to Latin under linuxfb. switch to new stats API. Handle more diff --git a/x11vnc/README b/x11vnc/README index 9d1bac1..643bbdb 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Sat Jun 3 15:45:12 EDT 2006 +x11vnc README file Date: Thu Jun 8 18:47:45 EDT 2006 The following information is taken from these URLs: @@ -24,7 +24,7 @@ x11vnc: a VNC server for real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. It has also been extended to work with - [7]webcams and tv tuner capture devices. + [7]webcams and TV tuner capture devices. I wrote x11vnc because x0rfbserver was basically impossible to build on Solaris and had poor performance. The primary x0rfbserver build @@ -206,7 +206,7 @@ splay :0' Some VNC viewers will do the ssh tunnelling for you automatically, the TightVNC vncviewer does this when the "-via far-away.east" option is supplied to it (this requires x11vnc to be already running on - far-away.east or having it started by [29]inetd(1)). See the 3rd + far-away.east or having it started by [29]inetd(8)). See the 3rd script example [30]below for more info. If the machine you SSH into is not the same machine with the X display @@ -298,7 +298,7 @@ export VNC_VIA_CMD vncviewer -via $host localhost:0 # must be TightVNC vncviewer. Of course if you already have the x11vnc running waiting for - connections (or have it started out of [34]inetd(1)), you can simply + connections (or have it started out of [34]inetd(8)), you can simply use the TightVNC "vncviewer -via gateway host:port" in its default mode to provide secure ssh tunnelling. _________________________________________________________________ @@ -341,12 +341,12 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. SourceForge.net. I use libvncserver for all of the VNC aspects; I couldn't have done without it. The full source code may be found and downloaded (either file-release tarball or CVS tree) from the above - link. As of Feb 2006, the [45]x11vnc-0.8.tar.gz source package is - released (recommended download). The [46]x11vnc 0.8 release notes. + link. As of Jun 2006, the [45]x11vnc-0.8.1.tar.gz source package is + released (recommended download). The [46]x11vnc 0.8.1 release notes. The x11vnc package is the subset of the libvncserver package needed to build the x11vnc program. Also, you can get a copy of my latest, - bleeding edge [47]x11vnc-0.8.1.tar.gz tarball to build the most up to + bleeding edge [47]x11vnc-0.8.2.tar.gz tarball to build the most up to date one. Precompiled Binaries/Packages: See the [48]FAQ below for information @@ -377,13 +377,13 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. Building x11vnc: If your OS has libjpeg.so and libz.so in standard locations you can - build as follows (example given for the 0.8 release of x11vnc: replace - with the version you downloaded): + build as follows (example given for the 0.8.1 release of x11vnc: + replace with the version you downloaded): (un-tar the x11vnc+libvncserver tarball) -# gzip -dc x11vnc-0.8.tar.gz | tar -xvf - +# gzip -dc x11vnc-0.8.1.tar.gz | tar -xvf - (cd to the source directory) -# cd x11vnc-0.8 +# cd x11vnc-0.8.1 (run configure and then run make) # ./configure @@ -577,102 +577,75 @@ make I don't have any formal beta-testers for the releases of x11vnc, so I'd appreciate any additional testing very much! - Thanks to those who helped beta test x11vnc 0.8 released in Feb 2006! + Thanks to those who helped beta test x11vnc 0.8.1 released in Jun + 2006! - Please help test and debug the 0.8.1 version for release sometime in - Spring 2006. + Please help test and debug the 0.8.2 version for release sometime in + Summer 2006. - The version 0.8.1 beta tarball is kept here: - [63]x11vnc-0.8.1.tar.gz + The version 0.8.2 beta tarball is kept here: + [63]x11vnc-0.8.2.tar.gz There are also some Linux, Solaris, and other OS test binaries [64]here. Please kick the tires and report bugs, performance regressions, undesired behavior, etc. to [65]me. - Here are some features that will appear in the 0.8.1 release: + Here are some features that appeared in the 0.8.1 release: + * Improved support for Webcams and TV tuner devices (/dev/video) + with the [66]-rawfb option. E.g. "-rawfb video0" will autodetect + the video WxHxB (requires Video4Linux buildtime or the v4l-info + utility). Use "-rawfb video -pipeinput VID" for a simple keystroke + utility to configure the capture device. + * Convenience utility [67]-rawfb cons to connect to the linux + console (/dev/fb0) and inject keystrokes into it (/dev/ttyX). Like + LinuxVNC or -pipeinput vcinject.pl, but now built in. + * The [68]-24to32 option provides automatic translation from 24bpp + to 32bpp framebuffers to avoid problems with viewers, etc (often + needed for webcams). + * The [69]-usepw option will try to use your existing ~/.vnc/passwd + or ~/.vnc/passwdfile passwords or otherwise prompt you to create + one (the server exits unless a password file is found and used). + Use "x11vnc -storepasswd" to prompt for a password without echoing + and save it in ~/.vnc/passwd + * The X CLIPBOARD selection is now managed in addition to PRIMARY. + Use [70]-noclipboard and [71]-nosetclipboard for the previous + PRIMARY-only behavior. + * Use [72]-capslock and [73]-skip_lockkeys to help manage CapsLocks + behavior better. + * The [74]-fbpm option provides FBPM support for hardware that + provides framebuffer power management (it needs to be disabled + when vnc clients are connected). + * The [75]-xinerama option is now on by default. Use -noxinerama + option to disable. + * Bug fixes and speedups. - * The [66]-ssl option provides SSL encryption and authentication - natively via the [67]www.openssl.org library. One can use from a + Here are some features that will appear in the 0.8.2 release: + * The [76]-ssl option provides SSL encryption and authentication + natively via the [77]www.openssl.org library. One can use from a simple self-signed certificate server certificate up to full CA and client certificate authentication schemes. - * The [68]-stunnel option starts up a SSL tunnel server stunnel + * The [78]-stunnel option starts up a SSL tunnel server stunnel (that must be installed separately on the system: - [69]www.stunnel.org) to allow only encrypted SSL connections from + [79]www.stunnel.org) to allow only encrypted SSL connections from the network. - * The [70]-sslverify option allows for authenticating VNC clients + * The [80]-sslverify option allows for authenticating VNC clients via their certificates in either -ssl or -stunnel modes. * An SSL enabled Java applet VNC Viewer applet is provided in classes/ssl/VncViewer.jar. It may also be loaded into the web browser via https (http over SSL) in addition to http. (via the - VNC port or also by the separate [71]-https port option). A - wrapper shell script [72]ssl_vncviewer is also provided that sets + VNC port or also by the separate [81]-https port option). A + wrapper shell script [82]ssl_vncviewer is also provided that sets up a stunnel client-side tunnel on Unix systems. - * The [73]-unixpw option supports Unix username and password - authentication (a variant is the [74]-unixpw_nis option that works - in NIS environments). The [75]-ssl or [76]-localhost + - [77]-stunnel options are enforced in this mode to prevent password + * The [83]-unixpw option supports Unix username and password + authentication (a variant is the [84]-unixpw_nis option that works + in NIS environments). The [85]-ssl or [86]-localhost + + [87]-stunnel options are enforced in this mode to prevent password sniffing. As a convenience, the -ssl or -stunnel requirements are lifted if a SSH tunnel can be deduced (but -localhost still applies). - * The [78]-usepw option will try to use your existing ~/.vnc/passwd - or ~/.vnc/passwfile passwords or otherwise prompt you to create - one (the server exits unless a password file is found and used). - * Improved support for Webcams and TV tuner devices (/dev/video) - with the [79]-rawfb option. E.g. "-rawfb video0" will autodetect - the video WxHxB (requires Video4Linux buildtime or the v4l-info - utility). Use "-rawfb video -pipeinput VID" for a simple keystroke - utility to configure the capture device. - * Convenience utility [80]-rawfb cons to connect to the linux - console (/dev/fb0) and inject keystrokes into it (/dev/ttyX). Like - LinuxVNC or -pipeinput vcinject.pl, but now built in. - * The [81]-24to32 option provides automatic translation from 24bpp - to 32bpp framebuffers to avoid problems with viewers, etc (often - needed for webcams). - * The X CLIPBOARD selection is now managed in addition to PRIMARY. - Use [82]-noclipboard and [83]-nosetclipboard for the previous - PRIMARY-only behavior. - * The [84]-xinerama option is now on by default. Use -noxinerama - option to disable. - - - Here are the release notes for the recent 0.8 release: - * TightVNC file transfer added to libvncserver by Rohit Kumar is - enabled (use [85]-nofilexfer to disable). - * The [86]-passwdfile option has been enhanced to handle any number - of full-access and view only passwords in an easy to maintain - format. Automatic rereading or file removal can be enabled. - * The [87]-8to24 option enables some multi-depth viewing on systems - that don't support [88]-overlay. The 8bpp regions are transformed - to depth 24 TrueColor. - * The [89]-loop option will run x11vnc in an outer loop restarting - each time (useful for situations where the X server restarts - often). - * The [90]-afteraccept option is like [91]-accept however it enables - running a user supplied command after client authentication has - taken place. The RFB_* environment variables have been extended. - * The [92]-slow_fb allows for slow polling for special purpose - applications (e.g. video). - * [93]-blackout noptr,WxH+X+Y,... will prevent the pointer from - going into a blacked out region. - * The x11vnc source code has gone through a major reorganization. - The build has been enhanced and many bugs fixed. - - Here are some notes about features added in 0.7.2. Checking/Testing - them is still useful and appreciated! - - Note that the [94]X DAMAGE feature will be on by default and so I - am interested if that causes any problems. I'd also like to have - the new [95]wireframe move/resize, the [96]wireframe copyrect - translation, and the [97]scroll detection+copyrect features all on - by default as well since when they work they give a great speedup! - (CopyRect is a VNC encoding and is very fast because the viewer - already has the image data that needs to be copied: e.g. it just - moves it to another part of its screen). The scroll copyrect is - currently the least stable, you can toggle it off via "-noscr" or - via the gui (all of the other new features can also be toggled by - cmdline option or gui, see -help output for more info). + Here are some [88]previous release notes _________________________________________________________________ Some Notes: @@ -699,11 +672,11 @@ make protocol.) I suggest using xsetroot, dtstyle or similar utility to set a solid background while using x11vnc. You can turn the pretty background image back on when you are using the display directly. - Update: As of Feb/2005 x11vnc has the [98]-solid [color] option that + Update: As of Feb/2005 x11vnc has the [89]-solid [color] option that works on recent GNOME, KDE, and CDE and also on classic X (background image is on the root window). - I also find the [99]TightVNC encoding gives the best response for my + I also find the [90]TightVNC encoding gives the best response for my usage (Unix <-> Unix over cable modem). One needs a tightvnc-aware vncviewer to take advantage of this encoding. @@ -715,16 +688,16 @@ make is X11's default listening port). Had port 5900 been taken by some other application, x11vnc would have next tried 5901. That would mean the viewer command above should be changed to vncviewer - far-away.east:1. You can force the port with the "[100]-rfbport NNNN" + far-away.east:1. You can force the port with the "[91]-rfbport NNNN" option where NNNN is the desired port number. If that port is already taken, x11vnc will exit immediately. (also see the "SunRay Gotcha" note below) Options: x11vnc has (far too) many features that may be activated - via its [101]command line options. Useful options are, e.g., -scale to + via its [92]command line options. Useful options are, e.g., -scale to do server-side scaling, and -rfbauth passwd-file to use VNC password protection (the vncpasswd or storepasswd programs, or the x11vnc - [102]-storepasswd option can be used to create the password file). + [93]-storepasswd option can be used to create the password file). Algorithm: How does x11vnc do it? Rather brute-forcedly: it continuously polls the X11 framebuffer for changes using @@ -751,18 +724,17 @@ make first testing out the programs. You get an interesting recursive/feedback effect where vncviewer images keep popping up each one contained in the previous one and slightly shifted a bit by the - window manager decorations. There will be an [103]even more - interesting effect if -scale is used. Also, if the XKEYBOARD is - supported and the XBell "beeps" once, you get an infinite loop of - beeps going off. Although all of this is mildly exciting it is not - much use: you will normally run and display the viewer on a different - machine! + window manager decorations. There will be an [94]even more interesting + effect if -scale is used. Also, if the XKEYBOARD is supported and the + XBell "beeps" once, you get an infinite loop of beeps going off. + Although all of this is mildly exciting it is not much use: you will + normally run and display the viewer on a different machine! _________________________________________________________________ Sun Ray Notes: - You can run x11vnc on your (connected or disconnected) [104]SunRay - session. Here are some [105]notes on SunRay usage with x11vnc. + You can run x11vnc on your (connected or disconnected) [95]SunRay + session. Here are some [96]notes on SunRay usage with x11vnc. _________________________________________________________________ @@ -774,9 +746,9 @@ make than you normally do to minimize the effects (e.g. do fullpage paging rather than line-by-line scrolling, and move windows in a single, quick motion). Recent work has provided the - [106]-scrollcopyrect and [107]-wireframe speedups using the - CopyRect VNC encoding and other things, but they only speed up - certain activities, not all. + [97]-scrollcopyrect and [98]-wireframe speedups using the CopyRect + VNC encoding and other things, but they only speed up certain + activities, not all. * A rate limiting factor for x11vnc performance is that video hardware is optimized for writing, not reading (x11vnc reads the video framebuffer for the screen image data). The difference can @@ -821,14 +793,14 @@ make be of use for special purpose applications. Also, a faster and more accurate way is to use the "dummy" XFree86/Xorg device driver (or our Xdummy wrapper script). See - [108]this FAQ for details. + [99]this FAQ for details. * Somewhat surprisingly, the X11 mouse (cursor) shape is write-only and cannot be queried from the X server. So traditionally in x11vnc the cursor shape stays fixed at an arrow. (see the "-cursor - X" and "-cursor some" [109]options, however, for a partial hack + X" and "-cursor some" [100]options, however, for a partial hack for the root window, etc.). However, on Solaris using the SUN_OVL overlay extension, x11vnc can show the correct mouse cursor when - the [110]-overlay option is also supplied. A similar thing is done + the [101]-overlay option is also supplied. A similar thing is done on IRIX as well when -overlay is supplied. More generally, as of Dec/2004 x11vnc supports the new XFIXES extension (in Xorg and Solaris 10) to query the X server for the @@ -836,20 +808,20 @@ make with transparency (alpha channel) need to approximated to solid RGB values (some cursors look worse than others). * Audio from applications is of course not redirected (separate - redirectors do exist, e.g. esd [111]the FAQ on this below.) The + redirectors do exist, e.g. esd [102]the FAQ on this below.) The XBell() "beeps" will work if the X server supports the XKEYBOARD extension. (Note that on Solaris XKEYBOARD is disabled by default. Passing +kb to Xsun enables it). - * The scroll detection algorithm for the [112]-scrollcopyrect option + * The scroll detection algorithm for the [103]-scrollcopyrect option can give choppy or bunched up transient output and occasionally painting errors. * Occasionally a patch of tiles will not get updated correctly. Evidently a timing related bug and difficult to reproduce... * Using -threads can expose some bugs in libvncserver. - Please feel free to [113]contact me if you have any questions, + Please feel free to [104]contact me if you have any questions, problems, or comments about x11vnc, etc. - Also, some people ask if they can make a donation, see [114]this link + Also, some people ask if they can make a donation, see [105]this link for that. _________________________________________________________________ @@ -858,323 +830,327 @@ make [Building and Starting] - [115]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed + [106]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed (null)" or "Xlib: connection to ":0.0" refused by server Xlib: No protocol specified" and then exits. What do I need to do? - [116]Q-2: I can't get x11vnc and/or libvncserver to compile. + [107]Q-2: I can't get x11vnc and/or libvncserver to compile. - [117]Q-3: I just built x11vnc successfully, but when I use it my + [108]Q-3: I just built x11vnc successfully, but when I use it my keystrokes and mouse button clicks are ignored (I am able to move the mouse though). - [118]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old + [109]Q-4: Help, I need to run x11vnc on Solaris 2.5.1 (or other old Unix/Linux) and it doesn't compile! - [119]Q-5: Where can I get a precompiled x11vnc binary for my Operating + [110]Q-5: Where can I get a precompiled x11vnc binary for my Operating System? - [120]Q-6: Where can I get a VNC Viewer binary (or source code) for the + [111]Q-6: Where can I get a VNC Viewer binary (or source code) for the Operating System I will be viewing from? - [121]Q-7: How can I see all of x11vnc's command line options and + [112]Q-7: How can I see all of x11vnc's command line options and documentation on how to use them? - [122]Q-8: I don't like typing arcane command line options every time I + [113]Q-8: I don't like typing arcane command line options every time I start x11vnc. What can I do? Is there a config file? Or a GUI? - [123]Q-9: How can I get the GUI to run in the System Tray, or at least + [114]Q-9: How can I get the GUI to run in the System Tray, or at least be a smaller, simpler icon? - [124]Q-10: Can I make x11vnc more quiet and also go into the + [115]Q-10: Can I make x11vnc more quiet and also go into the background after starting up? - [125]Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies + [116]Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with the error message like: "Broken pipe". I'm using the -forever mode and I want x11vnc to keep running. - [126]Q-12: Are there any build-time customizations possible, e.g. + [117]Q-12: Are there any build-time customizations possible, e.g. change defaults, create a smaller binary, etc? [Win2VNC Related] - [127]Q-13: I have two separate machine displays in front of me, one + [118]Q-13: I have two separate machine displays in front of me, one Windows the other X11: can I use x11vnc in combination with Win2VNC in dual-screen mode to pass the keystrokes and mouse motions to the X11 display? - [128]Q-14: I am running Win2VNC on my Windows machine and "x11vnc + [119]Q-14: I am running Win2VNC on my Windows machine and "x11vnc -nofb" on Unix to pass keyboard and mouse to the Unix monitor. Whenever I start Win2VNC it quickly disconnects and x11vnc says: rfbProcessClientNormalMessage: read: Connection reset by peer [Color Issues] - [129]Q-15: The X display I run x11vnc on is only 8 bits per pixel + [120]Q-15: The X display I run x11vnc on is only 8 bits per pixel (bpp) PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while they are incorrect in certain windows. - [130]Q-16: Color problems: Why are the colors for some windows + [121]Q-16: Color problems: Why are the colors for some windows incorrect in x11vnc? BTW, my X display has nice overlay/multi-depth visuals of different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - [131]Q-17: How do I figure out the window id to supply to the -id + [122]Q-17: How do I figure out the window id to supply to the -id windowid option? - [132]Q-18: Why don't menus or other transient windows come up when I + [123]Q-18: Why don't menus or other transient windows come up when I am using the -id windowid option to view a single application window? - [133]Q-19: My X display is depth 24 at 24bpp (instead of the normal + [124]Q-19: My X display is depth 24 at 24bpp (instead of the normal depth 24 at 32bpp). I'm having lots of color and visual problems with x11vnc and/or vncviewer. What's up? [Xterminals] - [134]Q-20: Can I use x11vnc to view and interact with an Xterminal + [125]Q-20: Can I use x11vnc to view and interact with an Xterminal (e.g. NCD) that is not running UNIX and so x11vnc cannot be run on it directly? - [135]Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file) + [126]Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct for a Unix/Linux machine acting as an Xterminal? [Sun Rays] - [136]Q-22: I'm having trouble using x11vnc with my Sun Ray session. + [127]Q-22: I'm having trouble using x11vnc with my Sun Ray session. [Remote Control] - [137]Q-23: How do I stop x11vnc once it is running in the background? + [128]Q-23: How do I stop x11vnc once it is running in the background? - [138]Q-24: Can I change settings in x11vnc without having to restart + [129]Q-24: Can I change settings in x11vnc without having to restart it? Can I remote control it? [Security and Permissions] - [139]Q-25: How do I create a VNC password for use with x11vnc? + [130]Q-25: How do I create a VNC password for use with x11vnc? - [140]Q-26: Can I make it so -storepasswd doesn't show my password on + [131]Q-26: Can I make it so -storepasswd doesn't show my password on the screen? - [141]Q-27: Can I have two passwords for VNC viewers, one for full + [132]Q-27: Can I have two passwords for VNC viewers, one for full access and the other for view-only access to the display? - [142]Q-28: Can I have as many full-access and view-only passwords as I + [133]Q-28: Can I have as many full-access and view-only passwords as I like? - [143]Q-29: Does x11vnc support Unix usernames and passwords? Can I + [134]Q-29: Does x11vnc support Unix usernames and passwords? Can I further limit the set of Unix usernames who can connect to the VNC desktop? - [144]Q-30: Why does x11vnc exit as soon as the VNC viewer disconnects? + [135]Q-30: Why does x11vnc exit as soon as the VNC viewer disconnects? And why doesn't it allow more than one VNC viewer to connect at the same time? - [145]Q-31: Can I limit which machines incoming VNC clients can connect + [136]Q-31: Can I limit which machines incoming VNC clients can connect from? - [146]Q-32: How do I build x11vnc/libvncserver with libwrap + [137]Q-32: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers) support? - [147]Q-33: Can I have x11vnc only listen on one network interface + [138]Q-33: Can I have x11vnc only listen on one network interface (e.g. internal LAN) rather than having it listen on all network interfaces and relying on -allow to filter unwanted connections out? - [148]Q-34: Now that -localhost implies listening only on the loopback + [139]Q-34: Now that -localhost implies listening only on the loopback interface, how I can occasionally allow in a non-localhost via the -R allowonce remote control command? - [149]Q-35: Can I fine tune what types of user input are allowed? E.g. + [140]Q-35: Can I fine tune what types of user input are allowed? E.g. have some users just be able to move the mouse, but not click or type anything? - [150]Q-36: Can I prompt the user at the local X display whether the + [141]Q-36: Can I prompt the user at the local X display whether the incoming VNC client should be accepted or not? Can I decide to make some clients view-only? How about running an arbitrary program to make the decisions? - [151]Q-37: I start x11vnc as root because it is launched via inetd(1) + [142]Q-37: I start x11vnc as root because it is launched via inetd(8) or a display manager like gdm(1). Can I have x11vnc later switch to a different user? - [152]Q-38: I use a screen-lock when I leave my workstation (e.g. + [143]Q-38: I use a screen-lock when I leave my workstation (e.g. xscreensaver or xlock). When I remotely access my workstation desktop via x11vnc I can unlock the desktop fine, but I am worried people will see my activities on the physical monitor. What can I do to prevent this, or at least make it more difficult? - [153]Q-39: Can I have x11vnc automatically lock the screen when I + [144]Q-39: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? [Encrypted Connections] - [154]Q-40: How can I tunnel my connection to x11vnc via an encrypted + [145]Q-40: How can I tunnel my connection to x11vnc via an encrypted SSH channel between two Unix machines? - [155]Q-41: How can I tunnel my connection to x11vnc via an encrypted + [146]Q-41: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [156]Q-42: How can I tunnel my connection to x11vnc via an encrypted + [147]Q-42: How can I tunnel my connection to x11vnc via an encrypted SSL channel using an external tool like stunnel? - [157]Q-43: Does x11vnc have built-in SSL tunneling? + [148]Q-43: Does x11vnc have built-in SSL tunneling? - [158]Q-44: How do I use VNC Viewers with built-in SSL tunneling? + [149]Q-44: How do I use VNC Viewers with built-in SSL tunneling? - [159]Q-45: How do I use VNC Viewers with built-in SSL tunneling when + [150]Q-45: How do I use VNC Viewers with built-in SSL tunneling when going through a Web Proxy? - [160]Q-46: Can Apache web server act as a gateway for users to connect + [151]Q-46: Can Apache web server act as a gateway for users to connect via SSL from the Internet with a Web browser to x11vnc running on their workstations behind a firewall? - [161]Q-47: Can I create and use my own SSL Certificate Authority (CA) + [152]Q-47: Can I create and use my own SSL Certificate Authority (CA) with x11vnc? [Display Managers and Services] - [162]Q-48: How can I run x11vnc as a "service" that is always + [153]Q-48: How can I run x11vnc as a "service" that is always available? - [163]Q-49: How can I use x11vnc to connect to an X login screen like + [154]Q-49: 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). - [164]Q-50: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + [155]Q-50: Can I run x11vnc out of inetd(8)? How about xinetd(8)? + + [156]Q-51: Can I have x11vnc allow a user to log in with her UNIX + password and then have it find her X display on that machine and + connect to it? - [165]Q-51: Can I have x11vnc restart itself after it terminates? + [157]Q-52: Can I have x11vnc restart itself after it terminates? - [166]Q-52: How do I make x11vnc work with the Java VNC viewer applet + [158]Q-53: How do I make x11vnc work with the Java VNC viewer applet in a web browser? - [167]Q-53: Are reverse connections (i.e. the VNC server connecting to + [159]Q-54: Are reverse connections (i.e. the VNC server connecting to the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported? - [168]Q-54: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a + [160]Q-55: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real display, but for a virtual one I keep around). - [169]Q-55: How can I use x11vnc on "headless" machines? Why might I + [161]Q-56: How can I use x11vnc on "headless" machines? Why might I want to? [Resource Usage and Performance] - [170]Q-56: I have lots of memory, but why does x11vnc fail with + [162]Q-57: I have lots of memory, but why does x11vnc fail with shmget: No space left on device or Minor opcode of failed request: 1 (X_ShmAttach)? - [171]Q-57: How can I make x11vnc use less system resources? + [163]Q-58: How can I make x11vnc use less system resources? - [172]Q-58: How can I make x11vnc use MORE system resources? + [164]Q-59: How can I make x11vnc use MORE system resources? - [173]Q-59: I use x11vnc over a slow link with high latency (e.g. + [165]Q-60: I use x11vnc over a slow link with high latency (e.g. dialup modem), is there anything I can do to speed things up? - [174]Q-60: Does x11vnc support the X DAMAGE Xserver extension to find + [166]Q-61: Does x11vnc support the X DAMAGE Xserver extension to find modified regions of the screen quickly and efficiently? - [175]Q-61: When I drag windows around with the mouse or scroll up and + [167]Q-62: 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? - [176]Q-62: Why not do something like wireframe animations to avoid the + [168]Q-63: Why not do something like wireframe animations to avoid the windows "lurching" when being moved or resized? - [177]Q-63: Can x11vnc try to apply heuristics to detect when an window + [169]Q-64: Can x11vnc try to apply heuristics to detect when an window is scrolling its contents and use the CopyRect encoding for a speedup? [Mouse Cursor Shapes] - [178]Q-64: Why isn't the mouse cursor shape (the little icon shape + [170]Q-65: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? - [179]Q-65: When using XFIXES cursorshape mode, some of the cursors + [171]Q-66: When using XFIXES cursorshape mode, some of the cursors look really bad with extra black borders around the cursor and other cruft. How can I improve their appearance? - [180]Q-66: In XFIXES mode, are there any hacks to handle cursor + [172]Q-67: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? [Mouse Pointer] - [181]Q-67: Why does the mouse arrow just stay in one corner in my + [173]Q-68: Why does the mouse arrow just stay in one corner in my vncviewer, whereas my cursor (that does move) is just a dot? - [182]Q-68: Can I take advantage of the TightVNC extension to the VNC + [174]Q-69: Can I take advantage of the TightVNC extension to the VNC protocol where Cursor Positions Updates are sent back to all connected clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - [183]Q-69: Is it possible to swap the mouse buttons (e.g. left-handed + [175]Q-70: Is it possible to swap the mouse buttons (e.g. left-handed operation), or arbitrarily remap them? How about mapping button clicks to keystrokes, e.g. to partially emulate Mouse wheel scrolling? [Keyboard Issues] - [184]Q-70: How can I get my AltGr and Shift modifiers to work between + [176]Q-71: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - [185]Q-71: When I try to type a "<" (i.e. less than) instead I get ">" + [177]Q-72: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! - [186]Q-72: When I try to type a "<" (i.e. less than) instead I get + [178]Q-73: When I try to type a "<" (i.e. less than) instead I get "<," (i.e. an extra comma). - [187]Q-73: I'm using an "international" keyboard (e.g. German "de", or + [179]Q-74: I'm using an "international" keyboard (e.g. German "de", or Danish "dk") and the -modtweak mode works well if the VNC viewer is run on a Unix/Linux machine with a similar keyboard. But if I run the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or Windows with any keyboard, I can't type some keys like: "@", "$", "<", ">", etc. How can I fix this? - [188]Q-74: When typing I sometimes get double, triple, or more of my + [180]Q-75: When typing I sometimes get double, triple, or more of my keystrokes repeated. I'm sure I only typed them once, what can I do? - [189]Q-75: The x11vnc -norepeat mode is in effect, but I still get + [181]Q-76: The x11vnc -norepeat mode is in effect, but I still get repeated keystrokes!! - [190]Q-76: The machine where I run x11vnc has an AltGr key, but the + [182]Q-77: 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? - [191]Q-77: I have a Sun machine I run x11vnc on. Its Sun keyboard has + [183]Q-78: I have a Sun machine I run x11vnc on. Its Sun keyboard has just one Alt key labelled "Alt" and two Meta keys labelled with little diamonds. The machine where I run the VNC viewer only has Alt keys. How can I send a Meta keypress? (e.g. emacs needs this) - [192]Q-78: Can I map a keystroke to a mouse button click on the remote + [184]Q-79: Can I map a keystroke to a mouse button click on the remote machine? - [193]Q-79: How can I get Caps_Lock to work between my VNC viewer and + [185]Q-80: How can I get Caps_Lock to work between my VNC viewer and x11vnc? [Screen Related Issues and Features] - [194]Q-80: The remote display is larger (in number of pixels) than the + [186]Q-81: The remote display is larger (in number of pixels) than the local display I am running the vncviewer on. I don't like the vncviewer scrollbars, what I can do? - [195]Q-81: Does x11vnc support server-side framebuffer scaling? (E.g. + [187]Q-82: Does x11vnc support server-side framebuffer scaling? (E.g. to make the desktop smaller). - [196]Q-82: Does x11vnc work with Xinerama? (i.e. multiple monitors + [188]Q-83: Does x11vnc work with Xinerama? (i.e. multiple monitors joined together to form one big, single screen). - [197]Q-83: Can I use x11vnc on a multi-headed display that is not + [189]Q-84: Can I use x11vnc on a multi-headed display that is not Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? - [198]Q-84: Can x11vnc show only a portion of the display? (E.g. for a + [190]Q-85: Can x11vnc show only a portion of the display? (E.g. for a special purpose rfb application). - [199]Q-85: Does x11vnc support the XRANDR (X Resize, Rotate and + [191]Q-86: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) extension? Whenever I rotate or resize the screen x11vnc just seems to crash. - [200]Q-86: Why is the view in my VNC viewer completely black? Or why + [192]Q-87: Why is the view in my VNC viewer completely black? Or why is everything flashing around randomly? - [201]Q-87: I use Linux Virtual Consoles (VC's) to implement 'Fast User + [193]Q-88: I use Linux Virtual Consoles (VC's) to implement 'Fast User Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7, Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those keystrokes to switch between their sessions). How come the view in a @@ -1182,15 +1158,15 @@ make otherwise all messed up unless the X session x11vnc is attached to is in the active VC? - [202]Q-88: Can I use x11vnc to view my VMWare session remotely? + [194]Q-89: Can I use x11vnc to view my VMWare session remotely? - [203]Q-89: Can non-X devices (e.g. a raw framebuffer) be viewed (and + [195]Q-90: Can non-X devices (e.g. a raw framebuffer) be viewed (and even controlled) with VNC via x11vnc? - [204]Q-90: Can I export via VNC a Webcam or TV tuner framebuffer using + [196]Q-91: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - [205]Q-91: I am using x11vnc where my local machine has "popup/hidden + [197]Q-92: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars @@ -1198,18 +1174,18 @@ make [Misc: Clipboard, File Transfer, Sound, Beeps, Thanks, etc.] - [206]Q-92: Does the Clipboard/Selection get transferred between the + [198]Q-93: Does the Clipboard/Selection get transferred between the vncviewer and the X display? - [207]Q-93: Can I transfer files back and forth with x11vnc? + [199]Q-94: Can I transfer files back and forth with x11vnc? - [208]Q-94: How can I hear the sound (audio) from the remote + [200]Q-95: How can I hear the sound (audio) from the remote applications on the desktop I am viewing via x11vnc? - [209]Q-95: Why don't I hear the "Beeps" in my X session (e.g. when + [201]Q-96: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? - [210]Q-96: Thanks for your program and for your help! Can I make a + [202]Q-97: Thanks for your program and for your help! Can I make a donation? _________________________________________________________________ @@ -1222,7 +1198,7 @@ make For the former error, you need to specify the X display to connect to (it also needs to be on the same machine the x11vnc process is to run - on). Set your DISPLAY environment variable or use the [211]-display + on). Set your DISPLAY environment variable or use the [203]-display option to specify it. Nearly always the correct value will be ":0" @@ -1239,7 +1215,7 @@ make How to Solve: See the xauth(1), Xsecurity(7), and xhost(1) man pages for much info on X11 permissions. For example, you may need to set - your XAUTHORITY environment variable or use the [212]-auth option to + your XAUTHORITY environment variable or use the [204]-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), or simply be sure you run x11vnc as the correct user (i.e. the user @@ -1261,7 +1237,7 @@ make x11vnc -display :0 -auth /var/gdm/:0.Xauth (this is for the display manager gdm and requires root permission to - read the gdm cookie file, see [213]this faq for other display manager + read the gdm cookie file, see [205]this faq for other display manager cookie file names). While running x11vnc as root, remember it comes with no warranty ;-). @@ -1271,7 +1247,7 @@ make (from the same machine). The person could then type "xhost -localhost" after x11vnc has connected to go back to the default permissions. Also, for some situations the "-users lurk=" option may be of use - (please read the documentation on the [214]-users option). + (please read the documentation on the [206]-users option). To test out your X11 permissions from a remote shell, set DISPLAY and possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on @@ -1383,7 +1359,7 @@ h earlier and perhaps non-Solaris): First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the - above [215]Solaris build script to run the configure command. That + above [207]Solaris build script to run the configure command. That should succeed without failure. Then you have to hand edit the autogenerated rfb/rfbconfig.h file in the source tree, and just before the last #endif at the bottom of that file insert these workaround @@ -1409,7 +1385,7 @@ typedef unsigned int in_addr_t; on other older OS (Solaris, Linux, ...) releases. Here are some notes for similar steps that need to be done to build on - [216]SunOS 4.x + [208]SunOS 4.x Please let us know if you had to use the above workaround (and whether it worked or not). If there is enough demand we will try to push clean @@ -1419,28 +1395,28 @@ typedef unsigned int in_addr_t; Q-5: Where can I get a precompiled x11vnc binary for my Operating System? - Hopefully the [217]build steps above and [218]FAQ provide enough info + Hopefully the [209]build steps above and [210]FAQ provide enough info for a painless compile for most environments. Please report problems with the x11vnc configure, make, etc. on your system (if your system is known to compile other GNU packages successfully). There are precompiled x11vnc binaries built by other groups that are available at the following locations: - Debian: (.deb) [219]http://packages.debian.org/x11vnc - - Slackware: (.tgz) [220]http://www.linuxpackages.net/ Redhat/Fedora: - (.rpm) [221]http://dag.wieers.com/packages/x11vnc/ - [222]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm) - [223]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg) - [224]http://www.sunfreeware.com/ FreeBSD: (.tbz) - [225]http://www.freebsd.org/ OpenBSD: (.tgz) - [226]http://www.openbsd.org/ NetBSD: (src) - [227]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb) - [228]http://mike.saunby.net/770/x11vnc/ Sharp Zaurus - [229]http://www.pdaxrom.org/ and [230]http://www.focv.com/ + Debian: (.deb) [211]http://packages.debian.org/x11vnc + + Slackware: (.tgz) [212]http://www.linuxpackages.net/ Redhat/Fedora: + (.rpm) [213]http://dag.wieers.com/packages/x11vnc/ + [214]http://dries.ulyssis.org/rpm/packages/x11vnc SuSE: (.rpm) + [215]http://linux01.gwdg.de/~pbleser/ Solaris: (pkg) + [216]http://www.sunfreeware.com/ FreeBSD: (.tbz) + [217]http://www.freebsd.org/ OpenBSD: (.tgz) + [218]http://www.openbsd.org/ NetBSD: (src) + [219]http://pkgsrc.se/x11/x11vnc Nokia 770 (.deb) + [220]http://mike.saunby.net/770/x11vnc/ Sharp Zaurus + [221]http://www.pdaxrom.org/ and [222]http://www.focv.com/ If the above binaries don't work and building x11vnc on your OS fails - (and all else fails!) you can try one of [231]my collection of + (and all else fails!) you can try one of [223]my collection of binaries for various OS's and x11vnc releases. As a general note, the x11vnc program is simple enough you don't @@ -1461,10 +1437,10 @@ typedef unsigned int in_addr_t; To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix) try here: - * [232]http://www.tightvnc.com/download.html - * [233]http://www.realvnc.com/download-free.html - * [234]http://sourceforge.net/projects/cotvnc/ - * [235]http://www.ultravnc.com/ + * [224]http://www.tightvnc.com/download.html + * [225]http://www.realvnc.com/download-free.html + * [226]http://sourceforge.net/projects/cotvnc/ + * [227]http://www.ultravnc.com/ Q-7: How can I see all of x11vnc's command line options and @@ -1472,7 +1448,7 @@ typedef unsigned int in_addr_t; Run: x11vnc -opts to list just the option names or run: x11vnc -help for long descriptions about each option. The output is listed - [236]here as well. + [228]here as well. Q-8: I don't like typing arcane command line options every time I @@ -1502,10 +1478,10 @@ display :0 remote-control functionality ("-R") that was added. The /usr/bin/wish program is needed for operation. The gui is not particularly user-friendly, it just provides a point and click mode to set all the - many x11vnc parameters and obtain help on them. See the [237]-gui + many x11vnc parameters and obtain help on them. See the [229]-gui option for more info. Examples: "x11vnc ... -gui" and "x11vnc ... -gui other:0" in the latter case the gui is displayed on other:0, not the X - display x11vnc is polling. There is also a "[238]-gui tray" system + display x11vnc is polling. There is also a "[230]-gui tray" system tray mode. @@ -1533,11 +1509,11 @@ display :0 Q-10: Can I make x11vnc more quiet and also go into the background after starting up? - Use the [239]-q and [240]-bg options, respectively. (also: -quiet is + Use the [231]-q and [232]-bg options, respectively. (also: -quiet is an alias for -q) Note that under -bg the stderr messages will be lost unless you use - the "[241]-o logfile" option. + the "[233]-o logfile" option. Q-11: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with @@ -1558,7 +1534,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 [242]build notes for general background). + (see the [234]build notes for general background). /* * Mar/2006 * Build-time customization via CPPFLAGS. @@ -1629,21 +1605,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 "[243]-nofb" option + Yes, for best response start up x11vnc with the "[235]-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 [244]x2vnc, however you would + This will also work X11 to X11 using [236]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: - * [245]Original Win2VNC - * [246]Enhanced Win2VNC and [247]sourceforge link - * [248]x2vnc - * [249]x2x also [250]here - * [251]zvnc (MorphOS) + * [237]Original Win2VNC + * [238]Enhanced Win2VNC and [239]sourceforge link + * [240]x2vnc + * [241]x2x also [242]here + * [243]zvnc (MorphOS) All of them will work with x11vnc (except x2x where it is not needed). @@ -1663,7 +1639,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 [252]-visual option to allow you to force the framebuffer + has the [244]-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: @@ -1678,7 +1654,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 [253]-flashcmap option to have x11vnc watch for changes in the + Use the [245]-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 @@ -1687,13 +1663,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 [254]-8to24 (Jan/2006) can often remove the need + Also note the option [246]-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 the [255]-notruecolor option has corrected colors + In some rare cases the [247]-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. @@ -1704,13 +1680,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 [256]previous question regarding 8 bpp + You may want to review the [248]previous question regarding 8 bpp PseudoColor. - On some hardware (Sun/SPARC and SGI), the [257]-overlay option + On some hardware (Sun/SPARC and SGI), the [249]-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 - [258]-8to24 option may help (also discussed below). + [250]-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 @@ -1746,7 +1722,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 [259]-overlay x11vnc option (Aug/2004) to have x11vnc use the + use the [251]-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 @@ -1771,7 +1747,7 @@ TrueColor defdepth 24 Xsun, e.g. in your /etc/dt/config/Xservers file). - The -8to24 mode: The [260]-8to24 x11vnc option (Jan/2006) is a kludge + The -8to24 mode: The [252]-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 @@ -1785,11 +1761,11 @@ TrueColor defdepth 24 32bpp view is exported via VNC. Even on pure 8bpp displays it can be used as an alternative to - [261]-flashcmap to avoid color flashing completely. + [253]-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: [262]-fixscreen V=3.0 to + row, or by using something like: [254]-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. @@ -1802,23 +1778,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 [263]-8to24 help description for information on + speedup. See the [255]-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 [264]-id option to + possible workaround in this case is to use the [256]-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 [265]-8to24 method + for x11vnc to be able to do so in real time. The [257]-8to24 method does this approximately and is somewhat usable. Fortunately the - [266]-overlay option works for Solaris machines with overlay visuals + [258]-overlay option works for Solaris machines with overlay visuals where most of this problem occurs. @@ -1829,9 +1805,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 [267]color problems. + debugging x11vnc [259]color problems. - Also, as of Dec/2004 you can use "[268]-id pick" to have x11vnc run + Also, as of Dec/2004 you can use "[260]-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. @@ -1849,7 +1825,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 [269]-sid windowid option ("shifted" windowid). + polling, try the [261]-sid windowid option ("shifted" windowid). Q-19: My X display is depth 24 at 24bpp (instead of the normal depth @@ -1884,7 +1860,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 [270]-24to32 option to have + Update: as of Apr/2006 you can use the [262]-24to32 option to have x11vnc dynamically transform the 24bpp pixel data to 32bpp. This extra transformation could slow things down further. @@ -1903,15 +1879,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 [271]-display option to point the display to that of + machine. Use the [263]-display option to point the display to that of the Xterminal (you'll of course need basic X11 permission to do that) - and also supply the [272]-noshm option (this enables the polling over + and also supply the [264]-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 [273]-flipbyteorder if the + on the polling rate. You may also need [265]-flipbyteorder if the colors get messed up due to endian byte order differences. Q-21: How do I get my X permissions (MIT-MAGIC-COOKIE file) correct @@ -1935,7 +1911,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 - [274]-auth option to point to the correct file). Other options include + [266]-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 - @@ -1947,7 +1923,7 @@ TrueColor defdepth 24 details. If the display name in the cookie file needs to be changed between the - two hosts, see [275]this note on the "xauth add ..." command. + two hosts, see [267]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 @@ -1961,7 +1937,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 [276]poll + Not recommended, but as a last resort, you could have x11vnc [268]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...) @@ -1990,13 +1966,13 @@ TrueColor defdepth 24 Q-22: I'm having trouble using x11vnc with my Sun Ray session. - The [277]Sun Ray technology is a bit like "VNC done in hardware" (the + The [269]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 [278]this discussion of Sun Ray issues for + "Soft Ray". Please see [270]this discussion of Sun Ray issues for solutions to problems. [Remote Control] @@ -2004,17 +1980,17 @@ TrueColor defdepth 24 Q-23: 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 - amount of things on the fly: see the [279]-remote and [280]-query + amount of things on the fly: see the [271]-remote and [272]-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 [281]-forever option has not been supplied, x11vnc will + If the [273]-forever option has not been supplied, x11vnc will automatically exit after the first client disconnects. In general you will have to kill the x11vnc process This can be done via: "kill NNNNN" (where NNNNN is the x11vnc process id number found from ps(1)), or "pkill x11vnc", or "killall x11vnc" (Linux only). - If you have not put x11vnc in the background via the [282]-bg option + If you have not put x11vnc in the background via the [274]-bg option or shell & operator, then simply press Ctrl-C in the shell where x11vnc is running to stop it. @@ -2024,15 +2000,15 @@ 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 [283]-clear_mods - option and [284]-clear_keys option can be used to release pressed keys + by tapping Ctrl, Shift, and Alt. Alternatively, the [275]-clear_mods + option and [276]-clear_keys option can be used to release pressed keys at startup and exit. Q-24: Can I change settings in x11vnc without having to restart it? Can I remote control it? - Look at the [285]-remote (same as -R) and [286]-query (same as -Q) + Look at the [277]-remote (same as -R) and [278]-query (same as -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 modtweak", @@ -2043,7 +2019,7 @@ TrueColor defdepth 24 correctly for communication to be possible. There is also a simple Tcl/Tk gui based on this remote control - mechanism. See the [287]-gui option for more info. You will need to + mechanism. See the [279]-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 icon window: "-gui icon". @@ -2058,12 +2034,12 @@ TrueColor defdepth 24 vncpasswd(1) program from those packages. As of Jun/2004 x11vnc supports the -storepasswd "pass" "file" - [288]option, which is the same functionality of storepasswd. Be sure + [280]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: "[289]-rfbauth + You then use the password via the x11vnc option: "[281]-rfbauth $HOME/myvncpasswd" If you do not supply any arguments: @@ -2071,13 +2047,15 @@ TrueColor defdepth 24 you will be prompted for a password to save to ~/.vnc/passwd (your keystrokes when entering the password will not be echoed to the - screen). + screen). If you supply one argument, e.g. "x11vnc -storepasswd + ~/.mypass", the password you are prompted for will be stored in that + file. - x11vnc also has the [290]-passwdfile and -passwd/-viewpasswd plain + x11vnc also has the [282]-passwdfile and -passwd/-viewpasswd plain text (i.e. not obscured like the -rfbauth VNC passwords) password options. - You can use the [291]-usepw option to automatically use any password + You can use the [283]-usepw option to automatically use any password file you have in ~/.vnc/passwd or ~/.vnc/passwdfile (the latter is used with the -passwdfile option). @@ -2101,18 +2079,21 @@ TrueColor defdepth 24 Write password to /home/myname/.vnc/passwd? [y]/n Password written to: /home/myname/.vnc/passwd + You can also give it an alternate filename, e.g. "x11vnc -storepasswd + ~/.mypass" + Q-27: 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 [292]-viewpasswd option to supply the - view-only password. Note the full-access password option [293]-passwd + Yes, as of May/2004 there is the [284]-viewpasswd option to supply the + view-only password. Note the full-access password option [285]-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 - [294]-passwdfile option to specify a file containing plain text + [286]-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 @@ -2120,7 +2101,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 [295]-rfbauth + View-only passwords currently do not work for the [287]-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 @@ -2133,7 +2114,7 @@ TrueColor defdepth 24 Q-28: Can I have as many full-access and view-only passwords as I like? - Yes, as of Jan/2006 in the libvncserver CVS the [296]-passwdfile + Yes, as of Jan/2006 in the libvncserver CVS the [288]-passwdfile option has been extended to handle as many passwords as you like. You put the view-only passwords after a line __BEGIN_VIEWONLY__. @@ -2147,7 +2128,7 @@ TrueColor defdepth 24 Until the VNC protocol and libvncserver support this things will be approximate at best. - Update: as of Feb/2006 x11vnc has the [297]-unixpw option that does + Update: as of Feb/2006 x11vnc has the [289]-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 @@ -2157,7 +2138,7 @@ TrueColor defdepth 24 A list of allowed Unix usernames may also be supplied along with per-user settings. - There is also the [298]-unixpw_nis option for non-shadow-password + There is also the [290]-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 @@ -2166,7 +2147,7 @@ TrueColor defdepth 24 shadow(5). Two settings are enforced in the -unixpw and -unixpw_nis modes to - provide extra security: the 1) [299]-localhost and 2) [300]-stunnel + provide extra security: the 1) [291]-localhost and 2) [292]-stunnel 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 (the @@ -2184,13 +2165,13 @@ TrueColor defdepth 24 Previous discussion: One approximate method involves starting x11vnc - with the [301]-localhost option. This basically requires the viewer + with the [293]-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 [302]elsewhere on this page. [303]stunnel does this as well. + mentioned [294]elsewhere on this page. [295]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 @@ -2201,7 +2182,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 [304]-accept option that runs a program to examine the connection + the [296]-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 @@ -2240,15 +2221,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 [305]-forever option (aka -many) to have + periods of time. Use the [297]-forever option (aka -many) to have x11vnc wait for more connections after the first client disconnects. - Use the [306]-shared option to have x11vnc allow multiple clients to + Use the [298]-shared option to have x11vnc allow multiple clients to connect simultaneously. - Recommended additional safety measures include using ssh ([307]see + Recommended additional safety measures include using ssh ([299]see above), stunnel, or a VPN to authenticate and encrypt the viewer - connections or to at least use the -rfbauth passwd-file [308]option to - use VNC password protection (or [309]-passwdfile) It is up to YOU to + connections or to at least use the -rfbauth passwd-file [300]option to + use VNC password protection (or [301]-passwdfile) It is up to YOU to apply these security measures, they will not be done for you automatically. @@ -2256,7 +2237,7 @@ exit 1 # reject it Q-31: Can I limit which machines incoming VNC clients can connect from? - Yes, look at the [310]-allow and [311]-localhost options to limit + Yes, look at the [302]-allow and [303]-localhost options to limit connections by hostname or IP address. E.g. x11vnc -allow 192.168.0.1,192.168.0.2 @@ -2268,7 +2249,7 @@ exit 1 # reject it Note that -localhost is the same as "-allow 127.0.0.1" For more control, build libvncserver with libwrap support - [312](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) + [304](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) for complete details. @@ -2288,7 +2269,7 @@ exit 1 # reject it is "vnc", e.g.: vnc: 192.168.100.3 .example.com - Note that if you run x11vnc out of [313]inetd you do not need to build + Note that if you run x11vnc out of [305]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. @@ -2297,15 +2278,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 "[314]-listen ipaddr" option that enables + As of Mar/2005 there is the "[306]-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 - "[315]-allow host1,..." option to allow only specific hosts in. + "[307]-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 [316]-localhost now implies "-listen localhost" since that + The option [308]-localhost now implies "-listen localhost" since that is what most people expect it to do. @@ -2313,17 +2294,17 @@ 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 "[317]-allow localhost". Unlike [318]-localhost + To do this specify "[309]-allow localhost". Unlike [310]-localhost this will leave x11vnc listening on all interfaces (but of course only allowing in local connections, e.g. ssh redirs). Then you can later run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot connection from a remote host. Note that if you do a lot of changing of the listening interface - ([319]-listen option) via remote control or gui, you may need to also - manually adjust the [320]-allow list if you unexpectedly get into a + ([311]-listen option) via remote control or gui, you may need to also + manually adjust the [312]-allow list if you unexpectedly get into a state where the allow list cannot match any hosts that would be coming - in on the listening interface. If you just toggle [321]-localhost on + in on the listening interface. If you just toggle [313]-localhost on and off x11vnc should see to it that you never get into such a state. @@ -2331,7 +2312,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 [322]-input option allows you to do this. "K", + As of Feb/2005, the [314]-input option allows you to do this. "K", "M", and "B" stand for Keystroke, Mouse-motion, and Button-clicks, respectively. The setting: "-input M" makes attached viewers only able to move the mouse. "-input KMB,M" lets normal clients do everything @@ -2346,7 +2327,7 @@ exit 1 # reject it some clients view-only? How about running an arbitrary program to make the decisions? - Yes, look at the "[323]-accept command" option, it allows you to + Yes, look at the "[315]-accept command" option, it allows you to specify an external command that is run for each new client. (use quotes around the command if it contains spaces, etc.). If the external command returns 0 the client is accepted, otherwise the @@ -2365,7 +2346,7 @@ exit 1 # reject it own simple popup window. To accept the client press "y" or click mouse on the "Yes" button. To reject the client press "n" or click mouse on the "No" button. To accept the client View-only, press "v" or click - mouse on the "View" button. If the [324]-viewonly option has been + mouse on the "View" button. If the [316]-viewonly option has been supplied, the "View" action will not be present: the whole display is view only in that case. @@ -2381,7 +2362,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 [325]ftp://ftp.x.org/ + is available at [317]ftp://ftp.x.org/ To include view-only decisions for the external commands, prefix the command something like this: "yes:0,no:*,view:3 mycommand ..." This @@ -2420,7 +2401,7 @@ elif [ $rc = 4 ]; then fi exit 1 - Stefan Radman has written a nice dtksh script [326]dtVncPopup for use + Stefan Radman has written a nice dtksh script [318]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. @@ -2429,18 +2410,18 @@ 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 "[327]-gone + To run a command when a client disconnects, use the "[319]-gone command" option. This is for the user's convenience only: the return code of the command is not interpreted by x11vnc. The same environment variables are set as in "-accept command" (except that RFB_MODE will be "gone"). - Q-37: I start x11vnc as root because it is launched via inetd(1) or a + Q-37: I start x11vnc as root because it is launched via inetd(8) or a display manager like gdm(1). Can I have x11vnc later switch to a different user? - As of Feb/2005 x11vnc has the [328]-users option that allows things + As of Feb/2005 x11vnc has the [320]-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. @@ -2465,7 +2446,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 [329]blockdpy.c The idea behind it is simple (but + source for it is [321]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 @@ -2481,8 +2462,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 [330]-accept option and told - to exit via the [331]-gone option (the vnc client user should + The blockdpy utility is launched by the [322]-accept option and told + to exit via the [323]-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. @@ -2490,7 +2471,7 @@ exit 1 Q-39: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? - Yes, a user mentions he uses the [332]-gone option under CDE to run a + Yes, a user mentions he uses the [324]-gone option under CDE to run a screen lock program: x11vnc -display :0 -forever -gone 'dtaction LockDisplay' @@ -2499,7 +2480,7 @@ exit 1 x11vnc -display :0 -forever -gone 'kdesktop_lock' x11vnc -display :0 -forever -gone 'xlock &' - Here is a scheme using the [333]-afteraccept option (in version 0.7.3) + Here is a scheme using the [325]-afteraccept option (in version 0.7.3) 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 @@ -2530,7 +2511,7 @@ fi Q-40: 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 [334]how to tunnel VNC via + See the description earlier on this page on [326]how to tunnel VNC via SSH from Unix to Unix. A number of ways are described along with some issues you may encounter. @@ -2541,7 +2522,7 @@ fi Q-41: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [335]Above we described how to tunnel VNC via SSH from Unix to Unix, + [327]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 @@ -2564,8 +2545,8 @@ fi process in a BAT file including launching the VNC viewer by using the plink Putty utility. Send us the script if you get that working. - For extra protection feel free to run x11vnc with the [336]-localhost - and [337]-rfbauth/[338]-passwdfile options. + For extra protection feel free to run x11vnc with the [328]-localhost + and [329]-rfbauth/[330]-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 @@ -2573,11 +2554,11 @@ fi 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 [339]chaining ssh's. + automated by [331]chaining ssh's. - As discussed [340]above another option is to first start the VNC + As discussed [332]above another option is to first start the VNC viewer in "listen" mode, and then launch x11vnc with the - "[341]-connect localhost" option to establish the reverse connection. + "[333]-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). @@ -2587,7 +2568,7 @@ fi 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 [342]stunnel provide an encrypted channel + IPSEC. SSL tunnels such as [334]stunnel provide an encrypted channel without the need for Unix users, passwords, and key passphrases required for ssh (and at the other extreme can also provide a complete signed certificate chain of trust). OTOH, since SSH is usually @@ -2595,12 +2576,12 @@ fi frequently the path of least resistance (it also nicely manages public keys for you). - Update: As of Feb/2006 x11vnc has the options [343]-ssl, - [344]-stunnel, and [345]-sslverify to provide integrated SSL schemes. - They are discussed [346]in the Next FAQ (you may want to skip to it + Update: As of Feb/2006 x11vnc has the options [335]-ssl, + [336]-stunnel, and [337]-sslverify to provide integrated SSL schemes. + They are discussed [338]in the Next FAQ (you may want to skip to it now). - Here are some basic examples using [347]stunnel but the general idea + Here are some basic examples using [339]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 @@ -2624,7 +2605,7 @@ fi 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 [348]signed by + stunnel is built. One can also create certificates [340]signed by Certificate Authorities or self-signed if desired using the x11vnc utilities described there. @@ -2638,7 +2619,7 @@ fi 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 [349]ssl_vncviewer script can automate + That's it. (note that the [341]ssl_vncviewer script can automate this.) Be sure to use a VNC password because unlike ssh by default the @@ -2646,13 +2627,13 @@ fi 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 [350]the key management section for details. + and also [342]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 [351]article The article also + found at the stunnel site and in this [343]article The article also shows the detailed steps to set up all the authentication - certificates. (for both server and clients, see also the [352]x11vnc + certificates. (for both server and clients, see also the [344]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 @@ -2673,7 +2654,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 [353]-inetd mode: + start up x11vnc in [345]-inetd mode: stunnel -p /path/to/stunnel.pem -P none -d 5900 -l ./x11vnc_sh Where the script x11vnc_sh starts up x11vnc: @@ -2716,16 +2697,16 @@ connect = 5900 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 [354]SSL-enabled - Java applet that can be served up via the [355]-httpdir or [356]-http - options when [357]-ssl is enabled. It will also be served via HTTPS + Note: as of Mar/2006 libvncserver/x11vnc provides a [346]SSL-enabled + Java applet that can be served up via the [347]-httpdir or [348]-http + options when [349]-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 [358]-https option. + the [350]-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 [359]-stunnel option on the server side it works well and is - convenient. Here is a simple script [360]ssl_vncviewer that automates + the [351]-stunnel option on the server side it works well and is + convenient. Here is a simple script [352]ssl_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.) @@ -2733,7 +2714,7 @@ connect = 5900 Q-43: Does x11vnc have built-in SSL tunneling? - You can read about non-built-in methods [361]in the Previous FAQ + You can read about non-built-in methods [353]in the Previous FAQ SSL tunnels provide an encrypted channel without the need for Unix users, passwords, and key passphrases required for ssh (and at the @@ -2744,14 +2725,14 @@ connect = 5900 Built-in SSL x11vnc options: - As of Feb/2006 the x11vnc [362]-ssl and [363]-stunnel options automate - the SSL tunnel creation on the x11vnc server side. An [364]SSL-enabled + As of Feb/2006 the x11vnc [354]-ssl and [355]-stunnel options automate + the SSL tunnel creation on the x11vnc server side. An [356]SSL-enabled Java Viewer applet also provided that can be served via http or https to automate SSL on the client side. - The [365]-ssl mode uses the [366]www.openssl.org library if available - at build time. The [367]-stunnel mode requires the - [368]www.stunnel.org command stunnel(8) to be installed on the system. + The [357]-ssl mode uses the [358]www.openssl.org library if available + at build time. The [359]-stunnel mode requires the + [360]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) (in fact in for options "-ssl" @@ -2803,12 +2784,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 [369]x11vnc Key Management for some utilities + See the discussion on [361]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 [370]ssl_vncviewer provides an example on unix + The wrapper script [362]ssl_vncviewer provides an example on unix (-verify option). Here are some notes on the simpler default (non-CA) operation. To have @@ -2824,7 +2805,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 - [371]here), then Man-In-The-Middle-Attacks are prevented. Otherwise, + [363]here), then Man-In-The-Middle-Attacks are prevented. Otherwise, the SSL encryption only provides protection against passive network traffic "sniffing". Nowadays, most people seem mostly concerned about only the latter (and the default x11vnc SSL modes protect against it.) @@ -2849,7 +2830,7 @@ connect = 5900 including using https to download it into the browser and connect to x11vnc. - See the [372]next FAQ for SSL enabled VNC Viewers. + See the [364]next FAQ for SSL enabled VNC Viewers. Q-44: How do I use VNC Viewers with built-in SSL tunneling? @@ -2860,9 +2841,9 @@ connect = 5900 The SSL enabled Java VNC Viewer (VncViewer.jar) in the x11vnc package supports only SSL based connections by default (set the applet parameter disableSSL=yes in index.vnc to override). As mentioned above - the [373]-httpdir can be used to specify the path to .../classes/ssl. + the [365]-httpdir can be used to specify the path to .../classes/ssl. A typical location might be /usr/local/share/x11vnc/classes/ssl. Or - the [374]-http can be used to try to have it find the directory + the [366]-http can be used to try to have it find the directory automatically. The Java viewer uses SSL to communicate securely with x11vnc. Note @@ -2887,7 +2868,7 @@ connect = 5900 example) can be slow or unreliable at times (it has to read some input and try to guess if the connection is VNC or HTTP). If it is unreliable and you still want to serve the Java applet via https, use - the [375]-https option to get an additional port dedicated to https + the [367]-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: @@ -2922,7 +2903,7 @@ connect = 5900 connection is VNC instead of the HTTPS it actually is (but since you have paused too long at the dialog the GET request comes too late). Often hitting Reload and going through the dialogs more quickly will - let you connect. Use the [376]-https option if you want a dedicated + let you connect. Use the [368]-https option if you want a dedicated port for HTTPS connections instead of sharing the VNC port. @@ -2931,10 +2912,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 the x11vnc - package. The basic ideas of doing this were discussed [377]for + package. The basic ideas of doing this were discussed [369]for external tunnel utilities here. - The [378]ssl_vncviewer script provided with x11vnc can set up the + The [370]ssl_vncviewer script provided with x11vnc 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 Debian based system you will need to @@ -2966,10 +2947,10 @@ 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 [379]this page for more information on + separate the two by commas. See [371]this page for more information on how Web proxies come into play. - If one uses a Certificate Authority (CA) scheme described [380]here, + If one uses a Certificate Authority (CA) scheme described [372]here, the wrapper script would use the CA cert instead of the server cert: 3') ssl_vncviewer -verify ./cacert.crt far-away.east:0 @@ -3005,7 +2986,7 @@ connect = 5900 (instead of the unsigned one in https://yourmachine.com:5900/ that gives the default index.vnc) - Note that the [381]ssl_vncviewer stunnel wrapper script can use Web + Note that the [373]ssl_vncviewer stunnel wrapper script can use Web proxies as well. Proxies that limit CONNECT to ports 443 and 563: @@ -3034,7 +3015,7 @@ 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. To use the GET [382]trick discussed above, do: + parameters in the URL. To use the GET [374]trick discussed above, do: https://yourmachine.com/proxy.vnc?PORT=443&GET=1 @@ -3042,7 +3023,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 [383]here. This provides a clean alternative to the + It is discussed [375]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. @@ -3050,7 +3031,7 @@ connect = 5900 Q-47: Can I create and use my own SSL Certificate Authority (CA) with x11vnc? - Yes, see [384]this page for how to do this and the utility commands + Yes, see [376]this page for how to do this and the utility commands x11vnc provides to create and manage many types of certificates and private keys. @@ -3069,16 +3050,18 @@ connect = 5900 need to have sufficient permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [385]FAQ on x11vnc + * Use the description under "Continuously" in the [377]FAQ on x11vnc and Display Managers - * Use the description in the [386]FAQ on x11vnc and inetd(1) + * Use the description in the [378]FAQ on x11vnc and inetd(8) + * Use the description in the [379]FAQ on Unix user logins and + inetd(8) * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc) - * Although less reliable, see the [387]x11vnc_loop rc.local hack + * Although less reliable, see the [380]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the X session unless a test is specifically put into the display startup - script (often named Xsetup). The inetd(1) scheme may or may not be + script (often named Xsetup). The inetd(8) scheme may or may not be specific to which user has the X session (and it may not be able to do all users via the XAUTHORITY permission issues). @@ -3104,7 +3087,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg while running x11vnc as root, e.g. for the gnome display manager, gdm: x11vnc -auth /var/gdm/:0.Xauth -display :0 - (the [388]-auth option sets the XAUTHORITY variable for you). + (the [381]-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 @@ -3129,7 +3112,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see - [389]the example at the end of this FAQ). Then restart dtlogin, e.g.: + [382]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 @@ -3192,7 +3175,7 @@ rever -bg Then restart: /usr/sbin/gdm-restart (or reboot). The KillInitClients=false setting is important: without it x11vnc will be - killed immediately after the user logs in. Here are [390]full details + killed immediately after the user logs in. Here are [383]full details on how to configure gdm _________________________________________________________________ @@ -3234,23 +3217,23 @@ rever -bg If you do not want to deal with any display manager startup scripts, here is a kludgey script that can be run manually or out of a boot - file like rc.local: [391]x11vnc_loop It will need some local + file like rc.local: [384]x11vnc_loop It will need some local customization before running. Because the XAUTHORITY auth file must be guessed by this script, use of the display manager script method described above is greatly preferred. If the machine is a traditional Xterminal you may want to read - [392]this FAQ. + [385]this FAQ. - Q-50: Can I run x11vnc out of inetd(1)? How about xinetd(1)? + Q-50: Can I run x11vnc out of inetd(8)? How about xinetd(8)? Yes, perhaps a line something like this in /etc/inetd.conf will do it for you: 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh - where the shell script /usr/local/bin/x11vnc_sh uses the [393]-inetd + where the shell script /usr/local/bin/x11vnc_sh uses the [386]-inetd option and looks something like (you'll need to customize to your settings). #!/bin/sh @@ -3263,7 +3246,7 @@ rever -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 [394]-quiet) option: "/usr/local/bin/x11vnc -q + specify the -q (aka [387]-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 @@ -3271,7 +3254,7 @@ rever -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 [395]-auth to point to the + Note also the need to set XAUTHORITY via [388]-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 @@ -3298,7 +3281,7 @@ rever -bg connecting to it. Always use a VNC password to further protect against unwanted access. - For xinetd(1), one user reports he created the file + For xinetd(8), one user reports he created the file /etc/xinetd.d/x11vncservice containing the following: # default: off # description: @@ -3336,21 +3319,104 @@ service x11vncservice capture a log) - Q-51: Can I have x11vnc restart itself after it terminates? + Q-51: Can I have x11vnc allow a user to log in with her UNIX password + and then have it find her X display on that machine and connect to it? + + The easiest way to do this is via [389]inetd(8) using the [390]-unixpw + and [391]-display WAIT options. The reason inetd(8) makes this easier + is that is 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 [392]this example). + + The [393]-display WAIT option waits until a VNC viewer is connected + before connecting to the X display, and can also be used to run a + command that returns the DISPLAY and XAUTHORITY data. So one could + supply "-display WAIT:find_display" where the script find_display + might look something like: +#!/bin/sh + +PATH=$PATH:/bin:/usr/bin:/usr/X11R6/bin:/usr/bin/X11:/usr/openwin/bin:/usr/ucb +export PATH + +if [ "X$user" = "X" ]; then + user=$USER +fi +if [ "X$user" = "X" ]; then + user=$LOGNAME +fi +if [ "X$user" = "X" ]; then + user=`whoami 2>dev/null` +fi +if [ "X$user" = "X" ]; then + echo "" + exit 1 +fi + +display=`who | grep "^${user}[ ][ ]*:[0-9]" | head -1 | awk '{print $2}'` +if [ "X$display" = "X" ]; then + display=`who | grep "^${user}[ ]" | awk '{print $NF}' | grep '(:[0-9]' + | sed -e 's/[()]//g' | head -1` + if [ "X$display" = "X" ]; then + echo "" + exit 1 + fi +fi + +echo "DISPLAY=$display" +xauth extract - "$display" 2>/dev/null + +exit 0 + + A some point a standard script created and will be used by default + under "-display WAIT:cmd=FINDDISPLAY". The format the script returns + is the first line is DISPLAY=:disp and any remaining lines are either + XAUTHORITY=file or raw xauth data (the above example does the latter). + + The [394]-unixpw option allows [395]UNIX password logins. Here are a + couple /etc/inetd.conf examples for this: +5900 stream tcp nowait nobody /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd +-unixpw \ + -display WAIT:cmd=/path/to/find_display -o /var/log/x11vnc.log -ssl SAVE +-ssldir /usr/local/certs +5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc -inetd +-unixpw \ + -display WAIT:cmd=/path/to/find_display -o /var/log/x11vnc.log -ssl SAVE +-users unixpw= + + Note the very long lines have been split. An alternative is to use a + wrapper script, e.g. /usr/local/bin/x11vnc.sh that has all of the + options. + + 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 "[396]-users unixpw=" option. + + Note that [397]SSL is required for this mode because otherwise the + unix password would be passed in clear text. In general -unixpw is not + required for this scheme, but it is convenient because it determines + who the user is whose display should be sought. Otherwise the + find_display script would have to use some scheme to work all of this + out. + + + Q-52: Can I have x11vnc restart itself after it terminates? One could do this in a shell script, but now there is an option - [396]-loop that makes it easier. Of course when x11vnc restarts it + [398]-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. - Q-52: How do I make x11vnc work with the Java VNC viewer applet in a + Q-53: How do I make x11vnc work with the Java VNC viewer applet in a web browser? To have x11vnc serve up a Java VNC viewer applet to any web browsers - that connect to it, run x11vnc with this [397]option: + that connect to it, run x11vnc with this [399]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -3369,7 +3435,7 @@ service x11vncservice 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 [398]-http option will try to guess where the Java + As of May/2005 the [400]-http option will try to guess where the Java classes jar file is by looking a expected locations. Also note that if you wanted to, you could also start the Java viewer @@ -3377,13 +3443,13 @@ service x11vncservice either the java or appletviewer commands to run the program. - Q-53: Are reverse connections (i.e. the VNC server connecting to the + Q-54: Are reverse connections (i.e. the VNC server connecting to the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported? 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 - [399]-connect option. To connect immediately at x11vnc startup time + [401]-connect option. To connect immediately at x11vnc startup time use the "-connect host:port" option (use commas for a list of hosts to connect to). The ":port" is optional (default is 5500). @@ -3391,7 +3457,7 @@ service x11vncservice file is checked periodically (about once a second) for new hosts to connect to. - The [400]-remote control option (aka -R) can also be used to do this + The [402]-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 @@ -3403,7 +3469,7 @@ x11vnc -display :0 -R connect:hostname.domain starting x11vnc. To use the vncconnect(1) program (from the core VNC package at - www.realvnc.com) specify the [401]-vncconnect option to x11vnc (Note: + www.realvnc.com) specify the [403]-vncconnect option to x11vnc (Note: as of Dec/2004 -vncconnect is now the default). vncconnect(1) must be pointed to the same X11 DISPLAY as x11vnc (since it uses X properties to communicate with x11vnc). If you do not have or do not want to get @@ -3417,7 +3483,7 @@ x11vnc -display :0 -R connect:hostname.domain xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" - Q-54: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real + Q-55: Can I use x11vnc as a replacement for Xvnc? (i.e. not for a real display, but for a virtual one I keep around). You can, but you would not be doing this for performance reasons (for @@ -3448,7 +3514,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" There are some annoyances WRT Xvfb though. The default keyboard mapping seems to be very poor. One should run x11vnc with - [402]-add_keysyms option to have keysyms added automatically. Also, to + [404]-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" @@ -3470,11 +3536,11 @@ xmodmap -e "add Control = Control_L Control_R" 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) [403]switching even though it + Linux Virtual Console/Terminal (VC/VT) [405]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 [404]Xdummy that allows you to + Jul/2005 we have an LD_PRELOAD script [406]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 @@ -3494,7 +3560,7 @@ startx -- /path/to/Xdummy :1 testing x11vnc). - Q-55: How can I use x11vnc on "headless" machines? Why might I want + Q-56: How can I use x11vnc on "headless" machines? Why might I want to? An interesting application of x11vnc is to let it export displays of @@ -3506,7 +3572,7 @@ startx -- /path/to/Xdummy :1 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 [405]this FAQ) and access it from + display via x11vnc (e.g. see [407]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 @@ -3531,7 +3597,7 @@ startx -- /path/to/Xdummy :1 [Resource Usage and Performance] - Q-56: I have lots of memory, but why does x11vnc fail with shmget: + Q-57: I have lots of memory, but why does x11vnc fail with shmget: No space left on device or Minor opcode of failed request: 1 (X_ShmAttach)? @@ -3549,7 +3615,7 @@ startx -- /path/to/Xdummy :1 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 [406]shm_clear to list and prompt for removal + Here is a shell script [408]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, @@ -3583,40 +3649,40 @@ ied) in /etc/system. See the next paragraph for more workarounds. To minimize the number of shm segments used by x11vnc try using the - [407]-onetile option (corresponds to only 3 shm segments used, and + [409]-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 - [408]-noshm option. Performance will be somewhat degraded but when + [410]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [409]earlier question discussing -noshm). + [411]earlier question discussing -noshm). - Q-57: How can I make x11vnc use less system resources? + Q-58: How can I make x11vnc use less system resources? - The [410]-nap and "[411]-wait n" (where n is the sleep between polls + The [412]-nap and "[413]-wait n" (where n is the sleep between polls in milliseconds, the default is 30 or so) option are good places to start. Reducing the X server bits per pixel depth (e.g. to 16bpp or even 8bpp) will further decrease memory I/O and network I/O. The ShadowFB will make x11vnc's screen polling less severe. Using the - [412]-onetile option will use less memory and use fewer shared memory - slots (add [413]-fs 1.0 for one less slot). + [414]-onetile option will use less memory and use fewer shared memory + slots (add [415]-fs 1.0 for one less slot). - Q-58: How can I make x11vnc use MORE system resources? + Q-59: How can I make x11vnc use MORE system resources? - You can try [414]-threads and dial down the wait time (e.g. -wait 1) - and possibly dial down [415]-defer as well. Note that if you try to + You can try [416]-threads and dial down the wait time (e.g. -wait 1) + and possibly dial down [417]-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 [416]-id option) can be streamed over a LAN or wireless at + the x11vnc [418]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. - Q-59: I use x11vnc over a slow link with high latency (e.g. dialup + Q-60: I use x11vnc over a slow link with high latency (e.g. dialup modem), is there anything I can do to speed things up? Some things you might want to experiment with (many of which will help @@ -3628,7 +3694,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 - [417]-solid [color] option to try to do this automatically. + [419]-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 @@ -3637,9 +3703,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 [418]-scrollcopyrect is active and + problem in x11vnc 0.7.2 if [420]-scrollcopyrect is active and detecting scrolls for the application). - * If the [419]-wireframe option is not available (earlier than + * If the [421]-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) @@ -3659,7 +3725,7 @@ ied) noticed. VNC viewer parameters: - * Use a [420]TightVNC enabled viewer! (Actually, RealVNC 4.x viewer + * Use a [422]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 @@ -3682,37 +3748,37 @@ ied) file. x11vnc parameters: - * Make sure the [421]-wireframe option is active (it should be on by + * Make sure the [423]-wireframe option is active (it should be on by default) and you have Opaque Moves/Resizes Enabled in the window manager. - * Make sure the [422]-scrollcopyrect option is active (it should be + * Make sure the [424]-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. - * Specify [423]-speeds modem to force the wireframe and + * Specify [425]-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 [424]-nodragging (no screen updates when dragging mouse, + drastic [426]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Set [425]-fs 1.0 (disables fullscreen updates) - * Try increasing [426]-wait or [427]-defer (reduces the maximum + * Set [427]-fs 1.0 (disables fullscreen updates) + * Try increasing [428]-wait or [429]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * Try the [428]-progressive pixelheight mode with the block + * Try the [430]-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 [429]-id (cuts + * If you just want to watch one (simple) window use [431]-id (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [430]-nosel (disables all clipboard selection exchange) - * Use [431]-nocursor and [432]-nocursorpos (repainting the remote + * Set [432]-nosel (disables all clipboard selection exchange) + * Use [433]-nocursor and [434]-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 - [433]-readtimeout n setting if it sometimes takes more than 20sec + [435]-readtimeout n setting if it sometimes takes more than 20sec to paint the full screen, etc. - Q-60: Does x11vnc support the X DAMAGE Xserver extension to find + Q-61: Does x11vnc support the X DAMAGE Xserver extension to find modified regions of the screen quickly and efficiently? Yes, as of Mar/2005 x11vnc will use the X DAMAGE extension by default @@ -3730,7 +3796,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 [434]slow (e.g. + in main memory. So reading the fb is still painfully [436]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 @@ -3748,27 +3814,27 @@ 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 "[435]-xd_area A" option to adjust the size + skipped). You can use the "[437]-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 "[436]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[437]-noxdamage". + The option "[438]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[439]-noxdamage". - Q-61: When I drag windows around with the mouse or scroll up and down + Q-62: 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 [438]slow hardware read rates from + This problem is primarily due to [440]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 - [439]-pointer_mode option for more info. The next bottleneck is + [441]-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 @@ -3778,31 +3844,31 @@ 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 "[440]-pointer_mode 1" option. + the "[442]-pointer_mode 1" option. - Also added was the [441]-nodragging option that disables all screen + Also added was the [443]-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 [442]-pointer_mode n option was introduced. n=1 is + As of Dec/2004 the [444]-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 [443]-threads option can improve + Also, in some circumstances the [445]-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). - As of Apr/2005 two new options (see the [444]wireframe FAQ and - [445]scrollcopyrect FAQ below) provide schemes to sweep this problem + As of Apr/2005 two new options (see the [446]wireframe FAQ and + [447]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. - Q-62: Why not do something like wireframe animations to avoid the + Q-63: Why not do something like wireframe animations to avoid the windows "lurching" when being moved or resized? Nice idea for a hack! As of Apr/2005 x11vnc by default will apply @@ -3813,8 +3879,8 @@ ied) 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 [446]slow video card - read rates (see [447]here too). A displacement, even a small one, of a + intermediate steps. BTW the lurching is due to [448]slow video card + read rates (see [449]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. @@ -3822,7 +3888,7 @@ ied) for -wireframe to do any good. The mode is currently on by default because most people are inflicted - with the problem. It can be disabled with the [448]-nowireframe option + with the problem. It can be disabled with the [450]-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 @@ -3867,13 +3933,13 @@ ied) * Maximum time to show a wireframe animation. * Minimum time between sending wireframe outlines. - See the [449]"-wireframe tweaks" option for more details. On a slow + See the [451]"-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 - [450]"-wirecopyrect mode" option. It is also on by default. This + [452]"-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 @@ -3904,7 +3970,7 @@ ied) -nowirecopyrect if this or other painting errors are unacceptable. - Q-63: Can x11vnc try to apply heuristics to detect when an window is + Q-64: Can x11vnc try to apply heuristics to detect when an window is scrolling its contents and use the CopyRect encoding for a speedup? Another nice idea for a hack! As of May/2005 x11vnc will by default @@ -3921,7 +3987,7 @@ ied) 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 [451]slow). + the hardware framebuffer is [453]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. @@ -3943,10 +4009,10 @@ ied) the X server display: if one falls too far behind it could become a mess... - The initial implementation of [452]-scrollcopyrect option is useful in + The initial implementation of [454]-scrollcopyrect option is useful in that it detects many scrolls and thus gives a much nicer working - environment (especially when combined with the [453]-wireframe - [454]-wirecopyrect [455]options, which are also on by default; and if + environment (especially when combined with the [455]-wireframe + [456]-wirecopyrect [457]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. @@ -3979,10 +4045,10 @@ ied) 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: [456]-fixscreen + also: [458]-fixscreen * Some applications, notably OpenOffice, do XCopyArea scrolls in weird ways that assume ancestor window clipping is taking place. - See the [457]-scr_skip option for ways to tweak this on a + See the [459]-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 @@ -3999,7 +4065,7 @@ ied) 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 [458]-scale option there will be a quick CopyRect + * When using the [460]-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 @@ -4012,7 +4078,7 @@ ied) If you find the -scrollcopyrect behavior too approximate or distracting you can go back to the standard polling-only update method - with the [459]-noscrollcopyrect (or -noscr for short). If you find + with the [461]-noscrollcopyrect (or -noscr for short). If you find some extremely bad and repeatable behavior for -scrollcopyrect please report a bug. @@ -4036,7 +4102,7 @@ ied) [Mouse Cursor Shapes] - Q-64: Why isn't the mouse cursor shape (the little icon shape where + Q-65: Why isn't the mouse cursor shape (the little icon shape where the mouse pointer is) correct as I move from window to window? On X servers supporting XFIXES or Solaris/IRIX Overlay extensions it @@ -4051,23 +4117,23 @@ ied) this is because the cursor shape is often downloaded to the graphics hardware (video card), but I could be mistaken. - A simple kludge is provided by the "[460]-cursor X" option that + A simple kludge is provided by the "[462]-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 "[461]-cursor some" option for + work for those cases. Also see the "[463]-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 - [462]-overlay option is supplied. See [463]this FAQ for more info. + [464]-overlay option is supplied. See [465]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 - [464]Solaris 10. + [466]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 @@ -4075,10 +4141,10 @@ ied) 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. [465]Details can be found here. + hidden alpha channel data under 32bpp. [467]Details can be found here. - Q-65: When using XFIXES cursorshape mode, some of the cursors look + Q-66: When using XFIXES cursorshape mode, some of the cursors look really bad with extra black borders around the cursor and other cruft. How can I improve their appearance? @@ -4108,17 +4174,17 @@ ied) for most cursor themes and you don't have to worry about it. In case it still looks bad for your cursor theme, there are (of - course!) some tunable parameters. The "[466]-alphacut n" option lets + course!) some tunable parameters. The "[468]-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 "[467]-alphafrac f" option tries to correct individual + 240. The "[469]-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 [468]-alpharemove that is useful for + Finally, there is an option [470]-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 @@ -4136,7 +4202,7 @@ ied) heavily on redglass) look fine with the apparent default of alphacut:255. - Q-66: In XFIXES mode, are there any hacks to handle cursor + Q-67: In XFIXES mode, are there any hacks to handle cursor transparency ("alpha channel") exactly? As of Jan/2005 libvncserver has been modified to allow an alpha @@ -4144,10 +4210,10 @@ ied) 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 [469]-nocursorshape x11vnc option. In this case the cursor is + with the [471]-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 [470]-noalphablend option to disable this + the x11vnc side. Use the [472]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). @@ -4173,12 +4239,12 @@ ied) [Mouse Pointer] - Q-67: Why does the mouse arrow just stay in one corner in my + Q-68: 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 [471]tightvnc extension + This default takes advantage of a [473]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [472]-nocursor + the local VNC viewer. You may disable it with the [474]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -4187,22 +4253,22 @@ ied) can also be disabled via -nocursor. - Q-68: Can I take advantage of the TightVNC extension to the VNC + Q-69: Can I take advantage of the TightVNC extension to the VNC protocol where Cursor Positions Updates are sent back to all connected clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [473]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [475]-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 [474]-nocursorpos and [475]-nocursorshape. + is the default. See also [476]-nocursorpos and [477]-nocursorshape. - Q-69: Is it possible to swap the mouse buttons (e.g. left-handed + Q-70: 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: [476]-buttonmap + You can remap the mouse buttons via something like: [478]-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. @@ -4210,7 +4276,7 @@ ied) One user had an X server with only one mouse button(!) and was able to map all of the VNC client mouse buttons to it via: -buttonmap 123-111. - Note that the [477]-debug_pointer option prints out much info for + Note that the [479]-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 @@ -4232,7 +4298,7 @@ ied) Exactly what keystroke "scrolling" events they should be bound to depends on one's taste. If this method is too approximate, one could - consider not using [478]-buttonmap but rather configuring the X server + consider not using [480]-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"'). @@ -4259,10 +4325,10 @@ ied) "click" usually gives a multi-line scroll). [Keyboard Issues] - Q-70: How can I get my AltGr and Shift modifiers to work between + Q-71: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [479]-modtweak should help here. It is a mode that monitors + The option [481]-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. @@ -4271,20 +4337,20 @@ ied) 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 [480]this FAQ for more info). Without + not exist on the keyboard (see [482]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 [481]FAQ about the -xkb option for a more powerful method + Also see the [483]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 - [482]-debug_keyboard option prints out much info for every keystroke + [484]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. - Q-71: When I try to type a "<" (i.e. less than) instead I get ">" + Q-72: When I try to type a "<" (i.e. less than) instead I get ">" (i.e. greater than)! Strangely, typing ">" works OK!! Does your keyboard have a single key with both "<" and ">" on it? Even @@ -4292,9 +4358,9 @@ ied) (e.g. pc105 in the XF86Config file when it should be something else, say pc104). - Short Cut: Try the [483]-xkb or [484]-sloppy_keys options and see if + Short Cut: Try the [485]-xkb or [486]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [485]-modtweak is now the default) but is useful reference for various + [487]-modtweak is now the default) but is useful reference for various tricks and so is kept. @@ -4337,34 +4403,34 @@ ied) -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([486]-modtweak) is a mode that monitors the + settings. The former ([488]-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 ([487]-remap less-comma) is an immediate remapping of the + The latter ([489]-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 [488]FAQ about the -xkb option as a possible workaround + See also the [490]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [489]-debug_keyboard option prints out much info for + Note that the [491]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. - Q-72: When I try to type a "<" (i.e. less than) instead I get "<," + Q-73: 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 [490]keymapping + the Shift key before releasing the "<". Because of a [492]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. - This should not happen in [491]-xkb mode, because it works hard to + This should not happen in [493]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [492]-sloppy_keys to attempt a similar type of algorithm. + option [494]-sloppy_keys to attempt a similar type of algorithm. - Q-73: I'm using an "international" keyboard (e.g. German "de", or + Q-74: I'm using an "international" keyboard (e.g. German "de", or Danish "dk") and the -modtweak mode works well if the VNC viewer is run on a Unix/Linux machine with a similar keyboard. But if I run the VNC viewer on Unix/Linux with a different keyboard (e.g. "us") or @@ -4385,7 +4451,7 @@ ied) In both cases no AltGr is sent to the VNC server, but we know AltGr is needed on the physical international keyboard to type a "@". - This all worked fine with x11vnc running with the [493]-modtweak + This all worked fine with x11vnc running with the [495]-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 @@ -4402,7 +4468,7 @@ ied) * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [494]-xkb option seems to fix all of the missing keys: "@", "<", + The [496]-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 @@ -4410,7 +4476,7 @@ ied) debugging output (send it along with any problems you report). Update: as of Jun/2005 x11vnc will try to automatically enable - [495]-xkb if it appears that would be beneficial (e.g. if it sees any + [497]-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. @@ -4425,7 +4491,7 @@ ied) was attached to keycode 93 (no physical key generates this keycode) while ISO_Level3_Shift was attached to keycode 113. The keycode skipping option was used to disable the ghost key: - [496]-skip_keycodes 93 + [498]-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 @@ -4442,16 +4508,16 @@ ied) What to do? In general the VNC protocol has not really solved this problem: what should be done if the VNC viewer sends a keysym not recognized by the VNC server side? Workarounds can possibly be - created using the [497]-remap x11vnc option: + created using the [499]-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 - [498]-add_keysyms option in the next paragraph. - Update: for convenience "[499]-remap DEAD" does many of these + [500]-add_keysyms option in the next paragraph. + Update: for convenience "[501]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [500]-remap, an - option [501]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [502]-remap, an + option [503]-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 @@ -4462,7 +4528,7 @@ ied) disable. - Q-74: When typing I sometimes get double, triple, or more of my + Q-75: When typing I sometimes get double, triple, or more of my keystrokes repeated. I'm sure I only typed them once, what can I do? This may be due to an interplay between your X server's key autorepeat @@ -4470,7 +4536,7 @@ ied) Short answer: disable key autorepeating by running the command "xset r off" on the Xserver where x11vnc is run (restore via "xset r on") or - use the new (Jul/2004) [502]-norepeat x11vnc option. You will still + use the new (Jul/2004) [504]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -4494,18 +4560,18 @@ ied) off", does the problem go away? The workaround is to manually apply "xset r off" and "xset r on" as - needed, or to use the [503]-norepeat (which has since Dec/2004 been + needed, or to use the [505]-norepeat (which has since Dec/2004 been made the default). Note that with X server autorepeat turned off the VNC viewer side of the connection will (nearly always) do its own autorepeating so there is no big loss here, unless someone is also working at the physical display and misses his autorepeating. - Q-75: The x11vnc -norepeat mode is in effect, but I still get repeated + Q-76: The x11vnc -norepeat mode is in effect, but I still get repeated keystrokes!! Are you using x11vnc to log in to an X session? (as described in - [504]this FAQ) If so, x11vnc is starting before your session and it + [506]this FAQ) If so, x11vnc is starting before your session and it disables autorepeat when you connect, but then after you log in your session startup (GNOME, KDE, ...) could be resetting the autorepeat to be on. Or it could be something inside your desktop trying to be @@ -4525,11 +4591,11 @@ ied) should figure out how to disable that somehow. - Q-76: The machine where I run x11vnc has an AltGr key, but the local + Q-77: 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 "[505]-remap Super_R-Mode_switch" x11vnc option may + Something like "[507]-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)). @@ -4540,7 +4606,7 @@ ied) specify remappings from a file. - Q-77: I have a Sun machine I run x11vnc on. Its Sun keyboard has just + Q-78: I have a Sun machine I run x11vnc on. Its Sun keyboard has just one Alt key labelled "Alt" and two Meta keys labelled with little diamonds. The machine where I run the VNC viewer only has Alt keys. How can I send a Meta keypress? (e.g. emacs needs this) @@ -4552,18 +4618,18 @@ ied) Since xmodmap(1) modifies the X server mappings you may not want to do this (because it affects local work on that machine). Something like - the [506]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [508]-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. - Q-78: Can I map a keystroke to a mouse button click on the remote + Q-79: Can I map a keystroke to a mouse button click on the remote machine? This can be done directly in some X servers using AccessX and Pointer_EnableKeys, but is a bit awkward. It may be more convenient to - have x11vnc do the remapping. This can be done via the [507]-remap + have x11vnc do the remapping. This can be done via the [509]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -4572,7 +4638,7 @@ ied) button "paste" because (using XFree86/Xorg Emulate3Buttons) you have to click both buttons on the touch pad at the same time. This remapping: - [508]-remap Super_R-Button2 + [510]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -4581,7 +4647,7 @@ ied) are generated immediately on the x11vnc side. When the key is released (i.e. goes up) no events are generated. - Q-79: How can I get Caps_Lock to work between my VNC viewer and + Q-80: How can I get Caps_Lock to work between my VNC viewer and x11vnc? This is a little tricky because it is possible to get the Caps_Lock @@ -4591,14 +4657,14 @@ ied) 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 - [509]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[510]-remap Caps_Lock-None". + [511]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[512]-remap Caps_Lock-None". - Also try the [511]-nomodtweak and [512]-capslock options. + Also try the [513]-nomodtweak and [514]-capslock options. [Screen Related Issues and Features] - Q-80: The remote display is larger (in number of pixels) than the + Q-81: The remote display is larger (in number of pixels) than the local display I am running the vncviewer on. I don't like the vncviewer scrollbars, what I can do? @@ -4617,15 +4683,15 @@ ied) 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 - [513]this FAQ on x11vnc scaling. + [515]this FAQ on x11vnc scaling. - Q-81: Does x11vnc support server-side framebuffer scaling? (E.g. to + Q-82: Does x11vnc support server-side framebuffer scaling? (E.g. to make the desktop smaller). 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 "[514]-scale fraction" option. "fraction" can either be a + use the "[516]-scale fraction" option. "fraction" can either be a floating point number (e.g. -scale 0.5) or the alternative m/n fraction notation (e.g. -scale 2/3). Note that if fraction is greater than one the display is magnified. @@ -4646,7 +4712,7 @@ ied) One can also use the ":nb" with an integer scale factor (say "-scale 2:nb") to use x11vnc as a screen magnifier for vision impaired - [515]applications. Since with integer scale factors the framebuffers + [517]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -4672,12 +4738,12 @@ ied) If one desires per-client scaling for something like 1:1 from a workstation and 1:2 from a smaller device (e.g. handheld), currently the only option is to run two (or more) x11vnc processes with - different scalings listening on separate ports ([516]-rfbport option, + different scalings listening on separate ports ([518]-rfbport option, etc.). BTW, whenever you run two or more x11vnc's on the same X display and - use the [517]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [518]"-connect + use the [519]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [520]"-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 proces and the @@ -4686,12 +4752,12 @@ ied) 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 - [519]"-scale_cursor frac" option to set the cursor scaling to a + [521]"-scale_cursor frac" option to set the cursor scaling to a different factor (e.g. use "-scale_cursor 1" to keep the cursor at its natural unscaled size). - Q-82: Does x11vnc work with Xinerama? (i.e. multiple monitors joined + Q-83: Does x11vnc work with Xinerama? (i.e. multiple monitors joined together to form one big, single screen). Yes, it should generally work because it simply polls the big @@ -4708,23 +4774,23 @@ ied) 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 [520]-blackout x11vnc option + may be distracting to the viewer. The [522]-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 - [521]-xinerama x11vnc option can be used to have it automatically + [523]-xinerama x11vnc option can be used to have it automatically determine the rectangles to be blackened out. (Note on 8bpp PseudoColor displays the fill color may not be black). Some users have reported that the mouse does not behave properly for their Xinerama display: i.e. the mouse cannot be moved to all regions - of the large display. If this happens try using the [522]-xwarppointer + of the large display. If this happens try using the [524]-xwarppointer option. This instructs x11vnc to fake mouse pointer motions using the XWarpPointer function instead of the XTestFakeMotionEvent XTEST function. (This may be due to a bug in the X server for XTEST when Xinerama is enabled). - Q-83: Can I use x11vnc on a multi-headed display that is not Xinerama + Q-84: Can I use x11vnc on a multi-headed display that is not Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)? You can, but it is a little bit awkward: you must start separate @@ -4742,32 +4808,32 @@ ied) Note: if you are running on Solaris 8 or earlier you can easily hit up against the maximum of 6 shm segments per process (for Xsun in this case) from running multiple x11vnc processes. You should modify - /etc/system as mentioned in another [523]FAQ to increase the limit. It - is probably also a good idea to run with the [524]-onetile option in + /etc/system as mentioned in another [525]FAQ to increase the limit. It + is probably also a good idea to run with the [526]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [525]-noshm to use no shm segments. + [527]-noshm to use no shm segments. - Q-84: Can x11vnc show only a portion of the display? (E.g. for a + Q-85: Can x11vnc show only a portion of the display? (E.g. for a special purpose rfb application). - As of Mar/2005 x11vnc has the "[526]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[528]-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 [527]Xinerama screen into two + One user used -clip to split up a large [529]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [528]-id or [529]-sid options are used. The offset is measured + the [530]-id or [531]-sid options are used. The offset is measured from the upper left corner of the selected window. - Q-85: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection) + Q-86: 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 - [530]-xrandr option to make x11vnc monitor XRANDR events and also trap + [532]-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. @@ -4777,7 +4843,7 @@ ied) 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 [531]-padgeom option to make the region big + viewers you can try the [533]-padgeom option to make the region big enough to hold all resizes and rotations. If you specify "-xrandr newfbsize" then vnc viewers that do not @@ -4786,13 +4852,13 @@ ied) terminate. - Q-86: Why is the view in my VNC viewer completely black? Or why is + Q-87: Why is the view in my VNC viewer completely black? Or why is everything flashing around randomly? See the next FAQ for a possible explanation. - Q-87: I use Linux Virtual Consoles (VC's) to implement 'Fast User + Q-88: I use Linux Virtual Consoles (VC's) to implement 'Fast User Switching' between users' sessions (e.g. Betty is on Ctrl-Alt-F7, Bobby is on Ctrl-Alt-F8, and Sid is on Ctrl-Alt-F1: they use those keystrokes to switch between their sessions). How come the view in a @@ -4821,7 +4887,7 @@ ied) "chvt 7" for VC #7. - Q-88: Can I use x11vnc to view my VMWare session remotely? + Q-89: Can I use x11vnc to view my VMWare session remotely? Yes, since VMWare is an X application you can view it via x11vnc in the normal way. @@ -4832,9 +4898,9 @@ ied) * Fullscreen mode The way VMWare does Fullscreen mode on Linux is to display the Guest - desktop in a separate Virtual Console (e.g. VC 8) (see [532]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [534]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X - server. So x11vnc cannot access it (however, [533]see this for a + server. So x11vnc cannot access it (however, [535]see this for a possible partial workaround). x11vnc works fine with "Normal X application window" and "Quick-Switch mode" because these use X. @@ -4855,13 +4921,13 @@ ied) response. One can also cut the display depth (e.g. to 16bpp) in this 2nd X session to improve video performance. This 2nd X session emulates Fullscreen mode to some degree and can be viewed via x11vnc - as long as the VMWare X session [534]is in the active VC. + as long as the VMWare X session [536]is in the active VC. Also note that with a little bit of playing with "xwininfo -all -children" output one can extract the (non-toplevel) windowid of the of the Guest desktop only when VMWare is running as a normal X application. Then one can export just the guest desktop (i.e. without - the VMWare menu buttons) by use of the [535]-id windowid option. The + the VMWare menu buttons) by use of the [537]-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 @@ -4870,7 +4936,7 @@ ied) mouse)). - Q-89: Can non-X devices (e.g. a raw framebuffer) be viewed (and even + Q-90: Can non-X devices (e.g. a raw framebuffer) be viewed (and even controlled) with VNC via x11vnc? As of Apr/2005 there is rudimentary support for this. Two options were @@ -4906,9 +4972,9 @@ ied) memory and is preferred over "file" (that uses the slower lseek(2) 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. The "snap:" setting applies the [536]-snapfb option - with "file:" type reading (this is useful for exporting webcams or tv - tuner video; see [537]the next FAQ for more info). + map is assumed. The "snap:" setting applies the [538]-snapfb option + with "file:" type reading (this is useful for exporting webcams or TV + tuner video; see [539]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 @@ -4948,7 +5014,7 @@ ied) 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. Of course for the case - of Xvfb x11vnc can poll it much better via the [538]X API, but you get + of Xvfb x11vnc can poll it much better via the [540]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -4967,7 +5033,7 @@ ied) All of the above was just for viewing the raw framebuffer. That may be enough for certain applications of this feature (e.g. suppose a - [539]video camera mapped its framebuffer into memory). To handle the + [541]video camera mapped its framebuffer into memory). To handle the pointer and keyboard input from the viewer users the "-pipeinput cmd" option was added to indicate a helper program to process the user input. The input is streamed to it and looks something like this: @@ -5002,7 +5068,7 @@ ied) 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 [540]active VC) one + view and interact with VC #2 (assuming it is the [542]active VC) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -5043,7 +5109,7 @@ ied) more accurate and faster LinuxVNC program. The only advantage x11vnc -rawfb might have is that it can presumably allow interaction with a non-text application, e.g. one based on svgalib. For example the - [541]VMWare Fullscreen mode is actually viewable under -rawfb. But + [543]VMWare Fullscreen mode is actually viewable under -rawfb. But this isn't much use until one figures out how to inject keystrokes and mouse events... @@ -5054,12 +5120,12 @@ ied) program that passes the framebuffer to libvncserver. - Q-90: Can I export via VNC a Webcam or TV tuner framebuffer using + Q-91: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - Yes, this is possible to some degree with the [542]-rawfb option. + Yes, this is possible to some degree with the [544]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [543]previous FAQ on -rawfb + used for the screen image data. See the [545]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -5071,7 +5137,7 @@ ied) snapshot to a file that you point -rawfb to; ask me if it is not clear what to do). - The "snap:" enforces [544]-snapfb mode which appears to be necessary. + The "snap:" enforces [546]-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. @@ -5093,7 +5159,7 @@ ied) 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 [545]-24to32 option will be automatically imposed when in + etc, the [547]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -5101,7 +5167,7 @@ ied) 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 [546]-wait, [547]-slow_fb, or [548]-defer + the framerate via the [548]-wait, [549]-slow_fb, or [550]-defer options. Decreasing the window size and bpp also helps. @@ -5138,7 +5204,7 @@ ied) RGB24, and RGB32 (with bpp 8, 8, 16, 16, 24, and 32 respectively). See http://www.linuxtv.org for more info (V4L api). - For tv/rf tuner cards one can set the tuning mode via tun=XXX where + For TV/rf tuner cards one can set the tuning mode via tun=XXX where XXX can be one of PAL, NTSC, SECAM, or AUTO. One can switch the input channel by the inp=XXX setting, where XXX @@ -5189,12 +5255,12 @@ ied) format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [549]-freqtab option to supply your own xawtv channel to + See also the [551]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc). - Q-91: I am using x11vnc where my local machine has "popup/hidden + Q-92: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars @@ -5209,30 +5275,30 @@ ied) [Misc: Clipboard, File Transfer, Sound, Beeps, Thanks, etc.] - Q-92: Does the Clipboard/Selection get transferred between the + Q-93: Does the Clipboard/Selection get transferred between the vncviewer and the X display? As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY selection (Xvnc does not seem to do this). If you don't want the Clipboard/Selection - exchanged use the [550]-nosel option. If you don't want the PRIMARY - selection to be polled for changes use the [551]-noprimary option. You - can also fine-tune it a bit with the [552]-seldir dir option. + exchanged use the [552]-nosel option. If you don't want the PRIMARY + selection to be polled for changes use the [553]-noprimary option. You + can also fine-tune it a bit with the [554]-seldir dir option. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and cutbuffers. - Q-93: Can I transfer files back and forth with x11vnc? + Q-94: Can I transfer files back and forth with x11vnc? As of Oct/2005 x11vnc enables the TightVNC file transfer implementation that was added to libvncserver. This currently only works with TightVNC viewers (and Windows only it appears). It is on by - default, to disable it use the [553]-nofilexfer option. + default, to disable it use the [555]-nofilexfer option. - Q-94: How can I hear the sound (audio) from the remote applications on + Q-95: How can I hear the sound (audio) from the remote applications on the desktop I am viewing via x11vnc? You will have to use an external network audio mechanism for this. @@ -5318,12 +5384,16 @@ or: mechanisms, but many are. * The audio is not compressed so you probably need a broadband or faster connection. Listening to music may not be very pleasant... + (Although we found streaming music from across the US over cable + modem worked OK, but took 200 KB/sec, to use less bandwidth + consider something like "ssh far-away.east 'cat favorite.mp3' | + mpg123 -b 4000 -") * Linux does not seem to have the concept of LD_PRELOAD_64 so if you run on a mixed 64- and 32-bit ABI system (e.g. AMD x86_64) some of the applications will fail to run because LD_PRELOAD will point to libraries of the wrong wordsize. - Q-95: Why don't I hear the "Beeps" in my X session (e.g. when typing + Q-96: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? As of Dec/2003 "Beep" XBell events are tracked by default. The X @@ -5331,16 +5401,16 @@ 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 [554]-nobell option. If + If you don't want to hear the beeps use the [556]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [555]redirector such as esd. + trying a [557]redirector such as esd. Contributions: - Q-96: Thanks for your program and for your help! Can I make a + Q-97: Thanks for your program and for your help! Can I make a donation? Please do (any amount is appreciated) and thank you for your support! @@ -5394,9 +5464,9 @@ References 42. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl 43. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int 44. http://sourceforge.net/projects/libvncserver/ - 45. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=393257 - 46. http://sourceforge.net/project/shownotes.php?release_id=393257&group_id=32584 - 47. http://www.karlrunge.com/x11vnc/x11vnc-0.8.1.tar.gz + 45. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=422738 + 46. http://sourceforge.net/project/shownotes.php?release_id=422738&group_id=32584 + 47. http://www.karlrunge.com/x11vnc/x11vnc-0.8.2.tar.gz 48. http://www.karlrunge.com/x11vnc/index.html#faq-binaries 49. http://www.tightvnc.com/download.html 50. http://www.realvnc.com/download-free.html @@ -5412,499 +5482,501 @@ References 60. http://www.gzip.org/zlib/ 61. http://www.sunfreeware.com/ 62. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build - 63. http://www.karlrunge.com/x11vnc/x11vnc-0.8.1.tar.gz + 63. http://www.karlrunge.com/x11vnc/x11vnc-0.8.2.tar.gz 64. http://www.karlrunge.com/x11vnc/bins 65. mailto:x11vnc-beta@karlrunge.com - 66. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 67. http://www.openssl.org/ - 68. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 69. http://www.stunnel.org/ - 70. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 71. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 72. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 73. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 74. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis - 75. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 76. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 77. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 78. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw - 79. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 80. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 81. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 82. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noclipboard - 83. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetclipboard - 84. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 85. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer - 86. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 87. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 88. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 89. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 90. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept - 91. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 92. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 93. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 94. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage - 95. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 96. http://www.karlrunge.com/x11vnc/index.html#wirecopyrect - 97. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect - 98. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 99. http://www.tightvnc.com/ - 100. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 101. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 102. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 103. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg - 104. http://wwws.sun.com/sunray/index.html - 105. http://www.karlrunge.com/x11vnc/sunray.html - 106. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 107. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 108. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 109. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 110. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 111. http://www.karlrunge.com/x11vnc/index.html#faq-sound - 112. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 113. mailto:xvml@karlrunge.com - 114. http://www.karlrunge.com/x11vnc/index.html#faq-thanks - 115. http://www.karlrunge.com/x11vnc/index.html#faq-xperms - 116. http://www.karlrunge.com/x11vnc/index.html#faq-build - 117. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest - 118. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build - 119. http://www.karlrunge.com/x11vnc/index.html#faq-binaries - 120. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download - 121. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts - 122. http://www.karlrunge.com/x11vnc/index.html#faq-config-file - 123. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray - 124. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg - 125. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe - 126. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations - 127. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc - 128. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp - 129. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 130. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 131. http://www.karlrunge.com/x11vnc/index.html#faq-windowid - 132. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id - 133. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp - 134. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 135. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 136. http://www.karlrunge.com/x11vnc/index.html#faq-sunrays - 137. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg - 138. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control - 139. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 140. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho - 141. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 142. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd - 143. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords - 144. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared - 145. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt - 146. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 147. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface - 148. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost - 149. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt - 150. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt - 151. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt - 152. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy - 153. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock - 154. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix - 155. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty - 156. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 157. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 158. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 159. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy - 160. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal - 161. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-ca - 162. http://www.karlrunge.com/x11vnc/index.html#faq-service - 163. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 164. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 165. http://www.karlrunge.com/x11vnc/index.html#faq-loop - 166. http://www.karlrunge.com/x11vnc/index.html#faq-java-http - 167. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect - 168. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb - 169. http://www.karlrunge.com/x11vnc/index.html#faq-headless - 170. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 171. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource - 172. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource - 173. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link - 174. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage - 175. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode - 176. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 177. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect - 178. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape - 179. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha - 180. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 181. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow - 182. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions - 183. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt - 184. http://www.karlrunge.com/x11vnc/index.html#faq-altgr - 185. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 186. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy - 187. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 188. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys - 189. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still - 190. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt - 191. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta - 192. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click - 193. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock - 194. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars - 195. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 196. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama - 197. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen - 198. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen - 199. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr - 200. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen - 201. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 202. http://www.karlrunge.com/x11vnc/index.html#faq-vmware - 203. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb - 204. http://www.karlrunge.com/x11vnc/index.html#faq-video - 205. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars - 206. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard - 207. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer - 208. http://www.karlrunge.com/x11vnc/index.html#faq-sound - 209. http://www.karlrunge.com/x11vnc/index.html#faq-beeps - 210. http://www.karlrunge.com/x11vnc/index.html#faq-thanks - 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 213. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 215. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 216. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html - 217. http://www.karlrunge.com/x11vnc/index.html#building - 218. http://www.karlrunge.com/x11vnc/index.html#faq-build - 219. http://packages.debian.org/x11vnc - 220. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc - 221. http://dag.wieers.com/packages/x11vnc/ - 222. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html - 223. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/ - 224. http://www.sunfreeware.com/ - 225. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all - 226. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html - 227. http://pkgsrc.se/x11/x11vnc - 228. http://mike.saunby.net/770/x11vnc/ - 229. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc - 230. http://www.focv.com/ipkg/ - 231. http://www.karlrunge.com/x11vnc/bins - 232. http://www.tightvnc.com/download.html - 233. http://www.realvnc.com/download-free.html - 234. http://sourceforge.net/projects/cotvnc/ - 235. http://www.ultravnc.com/ - 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 238. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray - 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o - 242. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb - 244. http://fredrik.hubbe.net/x2vnc.html - 245. http://www.hubbe.net/~hubbe/win2vnc.html - 246. http://www.deboer.gmxhome.de/ - 247. http://sourceforge.net/projects/win2vnc/ - 248. http://fredrik.hubbe.net/x2vnc.html - 249. http://freshmeat.net/projects/x2x/ - 250. http://ftp.digital.com/pub/Digital/SRC/x2x/ - 251. http://zapek.com/software/zvnc/ - 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 66. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 67. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 68. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 69. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw + 70. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noclipboard + 71. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosetclipboard + 72. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 73. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 74. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fbpm + 75. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 76. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 77. http://www.openssl.org/ + 78. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 79. http://www.stunnel.org/ + 80. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 81. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 82. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 83. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 84. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis + 85. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 86. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 87. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 88. http://www.karlrunge.com/x11vnc/prevrels.html + 89. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 90. http://www.tightvnc.com/ + 91. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 92. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 93. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 94. http://www.karlrunge.com/x11vnc/recurse_x11vnc.jpg + 95. http://wwws.sun.com/sunray/index.html + 96. http://www.karlrunge.com/x11vnc/sunray.html + 97. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 98. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 99. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 100. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 101. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 102. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 103. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 104. mailto:xvml@karlrunge.com + 105. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 106. http://www.karlrunge.com/x11vnc/index.html#faq-xperms + 107. http://www.karlrunge.com/x11vnc/index.html#faq-build + 108. http://www.karlrunge.com/x11vnc/index.html#faq-missing-xtest + 109. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build + 110. http://www.karlrunge.com/x11vnc/index.html#faq-binaries + 111. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download + 112. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts + 113. http://www.karlrunge.com/x11vnc/index.html#faq-config-file + 114. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray + 115. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg + 116. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe + 117. http://www.karlrunge.com/x11vnc/index.html#faq-build-customizations + 118. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc + 119. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp + 120. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 121. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 122. http://www.karlrunge.com/x11vnc/index.html#faq-windowid + 123. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id + 124. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp + 125. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 126. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 127. http://www.karlrunge.com/x11vnc/index.html#faq-sunrays + 128. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg + 129. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control + 130. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 131. http://www.karlrunge.com/x11vnc/index.html#faq-passwd-noecho + 132. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 133. http://www.karlrunge.com/x11vnc/index.html#faq-multipasswd + 134. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords + 135. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared + 136. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt + 137. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 138. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface + 139. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost + 140. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt + 141. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt + 142. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt + 143. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy + 144. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock + 145. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix + 146. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty + 147. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 148. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 149. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 150. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy + 151. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-portal + 152. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-ca + 153. http://www.karlrunge.com/x11vnc/index.html#faq-service + 154. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 155. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 156. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin + 157. http://www.karlrunge.com/x11vnc/index.html#faq-loop + 158. http://www.karlrunge.com/x11vnc/index.html#faq-java-http + 159. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect + 160. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 161. http://www.karlrunge.com/x11vnc/index.html#faq-headless + 162. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 163. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource + 164. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource + 165. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link + 166. http://www.karlrunge.com/x11vnc/index.html#faq-xdamage + 167. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 168. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe + 169. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect + 170. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape + 171. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha + 172. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 173. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow + 174. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions + 175. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt + 176. http://www.karlrunge.com/x11vnc/index.html#faq-altgr + 177. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 178. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless-sloppy + 179. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 180. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys + 181. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still + 182. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt + 183. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta + 184. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click + 185. http://www.karlrunge.com/x11vnc/index.html#faq-remap-capslock + 186. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars + 187. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 188. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama + 189. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen + 190. http://www.karlrunge.com/x11vnc/index.html#faq-clip-screen + 191. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr + 192. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen + 193. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 194. http://www.karlrunge.com/x11vnc/index.html#faq-vmware + 195. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 196. http://www.karlrunge.com/x11vnc/index.html#faq-video + 197. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars + 198. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard + 199. http://www.karlrunge.com/x11vnc/index.html#faq-filexfer + 200. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 201. http://www.karlrunge.com/x11vnc/index.html#faq-beeps + 202. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 205. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager + 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 207. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 208. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html + 209. http://www.karlrunge.com/x11vnc/index.html#building + 210. http://www.karlrunge.com/x11vnc/index.html#faq-build + 211. http://packages.debian.org/x11vnc + 212. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc + 213. http://dag.wieers.com/packages/x11vnc/ + 214. http://dries.ulyssis.org/rpm/packages/x11vnc/info.html + 215. http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=Network/x11vnc/ + 216. http://www.sunfreeware.com/ + 217. http://www.freebsd.org/cgi/ports.cgi?query=x11vnc&stype=all + 218. http://www.openbsd.org/3.9_packages/i386/x11vnc-0.6.2.tgz-long.html + 219. http://pkgsrc.se/x11/x11vnc + 220. http://mike.saunby.net/770/x11vnc/ + 221. http://www.pdaxrom.org/ipk_feed.php?menuid=11&showfeed=unstable#x11vnc + 222. http://www.focv.com/ipkg/ + 223. http://www.karlrunge.com/x11vnc/bins + 224. http://www.tightvnc.com/download.html + 225. http://www.realvnc.com/download-free.html + 226. http://sourceforge.net/projects/cotvnc/ + 227. http://www.ultravnc.com/ + 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 230. http://www.karlrunge.com/x11vnc/index.html#faq-gui-tray + 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 234. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 236. http://fredrik.hubbe.net/x2vnc.html + 237. http://www.hubbe.net/~hubbe/win2vnc.html + 238. http://www.deboer.gmxhome.de/ + 239. http://sourceforge.net/projects/win2vnc/ + 240. http://fredrik.hubbe.net/x2vnc.html + 241. http://freshmeat.net/projects/x2x/ + 242. http://ftp.digital.com/pub/Digital/SRC/x2x/ + 243. http://zapek.com/software/zvnc/ + 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor + 248. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp + 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor - 256. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 - 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 267. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid - 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder - 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 275. http://www.karlrunge.com/x11vnc/index.html#xauth_pain - 276. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 277. http://wwws.sun.com/sunray/index.html - 278. http://www.karlrunge.com/x11vnc/sunray.html - 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys - 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd - 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 290. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw - 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd - 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd - 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis - 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 302. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 303. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel - 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared - 307. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 308. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 309. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 312. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 313. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly - 325. ftp://ftp.x.org/ - 326. http://www.karlrunge.com/x11vnc/dtVncPopup - 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 329. http://www.karlrunge.com/x11vnc/blockdpy.c - 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept - 334. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 335. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 339. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh - 340. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 342. http://www.stunnel.org/ - 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 346. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 347. http://www.stunnel.org/ - 348. http://www.karlrunge.com/x11vnc/ssl.html - 349. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 350. http://www.karlrunge.com/x11vnc/ssl.html - 351. http://www.securityfocus.com/infocus/1677 - 352. http://www.karlrunge.com/x11vnc/ssl.html - 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 354. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-8to24 + 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 259. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid + 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder + 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 267. http://www.karlrunge.com/x11vnc/index.html#xauth_pain + 268. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 269. http://wwws.sun.com/sunray/index.html + 270. http://www.karlrunge.com/x11vnc/sunray.html + 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys + 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd + 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 282. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw + 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd + 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd + 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw_nis + 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 294. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 295. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel + 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared + 299. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 300. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 301. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 304. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 305. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly + 317. ftp://ftp.x.org/ + 318. http://www.karlrunge.com/x11vnc/dtVncPopup + 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 321. http://www.karlrunge.com/x11vnc/blockdpy.c + 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-afteraccept + 326. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 327. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 331. http://www.karlrunge.com/x11vnc/index.html#gateway_double_ssh + 332. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 334. http://www.stunnel.org/ + 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 338. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 339. http://www.stunnel.org/ + 340. http://www.karlrunge.com/x11vnc/ssl.html + 341. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 342. http://www.karlrunge.com/x11vnc/ssl.html + 343. http://www.securityfocus.com/infocus/1677 + 344. http://www.karlrunge.com/x11vnc/ssl.html + 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 346. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 349. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 352. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 353. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 354. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 355. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 356. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 358. http://www.openssl.org/ 359. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 360. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 361. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 362. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 363. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel + 360. http://www.stunnel.org/ + 361. http://www.karlrunge.com/x11vnc/ssl.html + 362. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 363. http://www.karlrunge.com/x11vnc/ssl.html 364. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 366. http://www.openssl.org/ - 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-stunnel - 368. http://www.stunnel.org/ - 369. http://www.karlrunge.com/x11vnc/ssl.html - 370. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 371. http://www.karlrunge.com/x11vnc/ssl.html - 372. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 373. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 374. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 375. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 376. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https - 377. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext - 378. http://www.karlrunge.com/x11vnc/ssl_vncviewer - 379. http://www.karlrunge.com/x11vnc/ssl-portal.html - 380. http://www.karlrunge.com/x11vnc/ssl.html - 381. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 382. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers - 383. http://www.karlrunge.com/x11vnc/ssl-portal.html - 384. http://www.karlrunge.com/x11vnc/ssl.html - 385. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 386. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 387. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 365. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 366. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 367. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 368. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-https + 369. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-ext + 370. http://www.karlrunge.com/x11vnc/ssl_vncviewer + 371. http://www.karlrunge.com/x11vnc/ssl-portal.html + 372. http://www.karlrunge.com/x11vnc/ssl.html + 373. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 374. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-viewers + 375. http://www.karlrunge.com/x11vnc/ssl-portal.html + 376. http://www.karlrunge.com/x11vnc/ssl.html + 377. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 378. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 379. http://www.karlrunge.com/x11vnc/index.html#faq-userlogin + 380. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 381. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 382. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris + 383. http://www.jirka.org/gdm-documentation/x241.html + 384. http://www.karlrunge.com/x11vnc/x11vnc_loop + 385. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 386. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 387. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q 388. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 389. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris - 390. http://www.jirka.org/gdm-documentation/x241.html - 391. http://www.karlrunge.com/x11vnc/x11vnc_loop - 392. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 395. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop - 397. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http - 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect - 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 403. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 404. http://www.karlrunge.com/x11vnc/Xdummy - 405. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 406. http://www.karlrunge.com/x11vnc/shm_clear - 407. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 408. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 409. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 411. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 420. http://www.tightvnc.com/ + 389. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 390. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 391. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 392. http://www.karlrunge.com/x11vnc/index.html#stunnel-inetd + 393. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display_WAIT + 394. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 395. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords + 396. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 397. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int + 398. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-loop + 399. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 400. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-http + 401. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 402. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 403. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 404. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 405. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 406. http://www.karlrunge.com/x11vnc/Xdummy + 407. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 408. http://www.karlrunge.com/x11vnc/shm_clear + 409. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 410. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 411. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 412. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 413. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 414. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 415. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 416. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 417. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 418. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 419. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 420. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect 421. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 422. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds - 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout - 434. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 436. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 438. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 440. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 422. http://www.tightvnc.com/ + 423. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 424. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 425. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-speeds + 426. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 427. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 428. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 429. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 430. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 431. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 432. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 433. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 434. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 435. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-readtimeout + 436. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 437. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 438. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 439. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 440. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 441. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode 442. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 444. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 445. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect - 446. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode - 447. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 448. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 449. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 443. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 444. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 445. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 446. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe + 447. http://www.karlrunge.com/x11vnc/index.html#faq-scrollcopyrect + 448. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode + 449. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow 450. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 451. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 453. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe - 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect - 455. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe - 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen - 457. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip - 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect - 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 463. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode - 464. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 465. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 466. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 467. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 471. http://www.tightvnc.com/ - 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 473. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 451. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 452. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 453. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 454. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 455. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wireframe + 456. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wirecopyrect + 457. http://www.karlrunge.com/x11vnc/index.html#faq-wireframe + 458. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fixscreen + 459. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scr_skip + 460. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 461. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect + 462. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 463. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 464. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 465. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode + 466. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 467. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 468. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 469. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 470. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 471. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 472. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 473. http://www.tightvnc.com/ + 474. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 475. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 476. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 477. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape 478. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 480. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 481. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 482. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 483. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 488. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 490. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 492. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 479. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 480. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 481. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 482. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 483. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 484. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 485. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 486. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 487. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 488. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 489. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 490. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 491. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 492. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 493. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 494. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 495. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 496. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 497. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 498. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes 499. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 504. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 506. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 500. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 501. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 502. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 503. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 504. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 505. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 506. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager 507. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 508. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 509. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 510. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 513. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 515. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html - 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 517. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 523. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 525. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 527. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama - 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 529. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 532. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 533. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 511. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 512. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 513. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 514. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 515. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 516. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 517. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html + 518. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 519. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 520. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 521. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 522. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 523. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 524. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 525. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 526. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 527. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 528. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 529. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama + 530. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 531. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 532. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 533. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom 534. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 535. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 537. http://www.karlrunge.com/x11vnc/index.html#faq-video - 538. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 535. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 536. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 537. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb 539. http://www.karlrunge.com/x11vnc/index.html#faq-video - 540. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 541. http://www.karlrunge.com/x11vnc/index.html#faq-vmware - 542. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 543. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb - 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab - 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer - 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 555. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 540. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 541. http://www.karlrunge.com/x11vnc/index.html#faq-video + 542. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 543. http://www.karlrunge.com/x11vnc/index.html#faq-vmware + 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 545. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 546. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 547. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 553. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofilexfer + 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 557. http://www.karlrunge.com/x11vnc/index.html#faq-sound ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -6702,7 +6774,9 @@ http://www.karlrunge.com/x11vnc/ssl-portal.html: add to it the ability to act as a gateway for SSL VNC connections. The only thing needed on the Viewer side is a Java enabled Web Browser. The stunnel VNC viewer wrapper script provided (ssl_vncviewer) can - also take advantage of the method described here. + also take advantage of the method described here. The apache solution + may be overkill for you (e.g. home system) see below for some simpler + setups. There are numerous ways to do this. We present the simplest one here. Important: these schemes allow incoming connections from anywhere on @@ -6740,7 +6814,7 @@ http://www.karlrunge.com/x11vnc/ssl-portal.html: i.e. we force SSL VNC connections, port 5915, serve the Java VNC viewer applet, and require a VNC password (another option would be - [1]-unixpw). + [1]-unixpw). The above command could also be run out of [2]inetd(8). These sections are added to the httpd.conf apache configuration file @@ -6798,7 +6872,7 @@ t:563/ another firewall that requires proxying) then use this URL: http://www.gateway.east:563/x11vnc/proxy/mach2 - See [2]this FAQ for more info on how this works. + See [3]this FAQ for more info on how this works. Let's go through the httpd.conf additions in detail. @@ -6835,9 +6909,9 @@ t:563/ Some Ideas for adding extra authentication for the paranoid: - * VNC passwords: [3]-rfbauth, [4]-passwdfile, or [5]-usepw. - * Unix passwords: [6]-unixpw - * SSL Client certificates: [7]-sslverify + * VNC passwords: [4]-rfbauth, [5]-passwdfile, or [6]-usepw. + * Unix passwords: [7]-unixpw + * SSL Client certificates: [8]-sslverify * Apache AuthUserFile directive: .htaccess, etc. * Add proxy password authentication (requires Viewer changes?) @@ -6845,7 +6919,7 @@ t:563/ Using non-Java viewers with this scheme: - The [8]ssl_vncviewer stunnel wrapper script for VNC viewers has the + The [9]ssl_vncviewer stunnel wrapper script for VNC viewers has the -proxy option that can take advantage of this method. For the case of the "double proxy" situation (see below) supply both separated by a comma. @@ -6857,11 +6931,11 @@ t:563/ To have the Java applet downloaded to the user's Web Browswer via an encrypted (and evidently safer) SSL connection the Apache webserver - should be configured for SSL via [9]mod_ssl (this is probably not + should be configured for SSL via [10]mod_ssl (this is probably not absolutely necessary; show us how you did it). - It is actually possible to use the x11vnc [10]Key Management utility - "[11]-sslGenCert" to generate your Apache/SSL .crt and .key files. (In + It is actually possible to use the x11vnc [11]Key Management utility + "[12]-sslGenCert" to generate your Apache/SSL .crt and .key files. (In brief, run something like "x11vnc -sslGenCert server self:apache" then copy the resulting self:apache.crt file to conf/ssl.crt/server.crt and extract the private key part from self:apache.pem and paste it into @@ -6957,7 +7031,9 @@ ProxyPass /S11vnc/mach4/ https://mach4:5915/ typically using the display on that machine. One could imagine giving different users different ports, 5915, 5916, etc. to distinguish (then the script would need to be passed the username). mod_rewrite could be - used to automatically map username in the URL to his port number. + used to automatically map username in the URL to his port number. The + -display WAIT:cmd=FINDDISPLAY could also be of use to allieviate some + of the problems here. Also note the use of "-ssl SAVE". This way a saved server.pem is used for each inetd invocation (rather generating a new one each time). @@ -7018,16 +7094,17 @@ ProxyPass /S11vnc/mach4/ https://mach4:5915/ References 1. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 2. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy - 3. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 4. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 5. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw - 6. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw - 7. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify - 8. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer - 9. http://httpd.apache.org/docs/2.0/mod/mod_ssl.html - 10. http://www.karlrunge.com/x11vnc/ssl.html - 11. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert + 2. http://www.karlrunge.com/x11vnc/ssl-portal.html#inetd + 3. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-java-viewer-proxy + 4. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 5. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 6. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-usepw + 7. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-unixpw + 8. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslverify + 9. http://www.karlrunge.com/x11vnc/index.html#ssl_vncviewer + 10. http://httpd.apache.org/docs/2.0/mod/mod_ssl.html + 11. http://www.karlrunge.com/x11vnc/ssl.html + 12. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert ======================================================================= http://www.karlrunge.com/x11vnc/x11vnc_opts.html: @@ -7040,7 +7117,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.8.1 lastmod: 2006-06-03 +x11vnc: allow VNC connections to real X11 displays. 0.8.2 lastmod: 2006-06-08 x11vnc options: -display disp -auth file -id windowid @@ -7054,50 +7131,55 @@ x11vnc options: -connect string -vncconnect -novncconnect -allow host1[,host2..] -localhost -nolookup -input string -viewpasswd string -passwdfile filename - -usepw -storepasswd pass file -nopw - -accept string -afteraccept string -gone string - -users list -noshm -flipbyteorder - -onetile -solid [color] -blackout string - -xinerama -noxinerama -xtrap - -xrandr [mode] -padgeom WxH -o logfile - -flag file -rc filename -norc - -h, -help -?, -opts -V, -version - -dbg -q -bg - -modtweak -nomodtweak -xkb - -noxkb -capslock -skip_lockkeys - -skip_keycodes string -sloppy_keys -skip_dups - -noskip_dups -add_keysyms -noadd_keysyms - -clear_mods -clear_keys -remap string - -norepeat -repeat -nofb - -nobell -nosel -noprimary - -nosetprimary -noclipboard -nosetclipboard - -seldir string -cursor [mode] -nocursor - -arrow n -noxfixes -alphacut n - -alphafrac fraction -alpharemove -noalphablend - -nocursorshape -cursorpos -nocursorpos - -xwarppointer -buttonmap string -nodragging - -wireframe [str] -nowireframe -wirecopyrect mode - -nowirecopyrect -debug_wireframe -scrollcopyrect mode - -noscrollcopyrect -scr_area n -scr_skip list - -scr_inc list -scr_keys list -scr_term list - -scr_keyrepeat lo-hi -scr_parms string -fixscreen string - -debug_scroll -noxrecord -grab_buster - -nograb_buster -debug_grabs -debug_sel - -pointer_mode n -input_skip n -speeds rd,bw,lat - -wmdt string -debug_pointer -debug_keyboard - -defer time -wait time -wait_ui factor - -nowait_bog -slow_fb time -readtimeout n - -nap -nonap -sb time - -nofbpm -fbpm -noxdamage - -xd_area A -xd_mem f -sigpipe string - -threads -nothreads -fs f - -gaps n -grow n -fuzz n - -debug_tiles -snapfb -rawfb string - -freqtab file -pipeinput cmd -gui [gui-opts] - -remote command -query variable -QD variable - -sync -noremote -yesremote - -unsafe -safer -privremote - -nocmds -deny_all + -unixpw [list] -unixpw_nis [list] -display WAIT:... + -ssl [pem] -ssldir [dir] -sslverify [path] + -sslGenCA [dir] -sslGenCert type name -sslEncKey [pem] + -sslCertInfo [pem] -sslDelCert [pem] -stunnel [pem] + -stunnel3 [pem] -https [port] -usepw + -storepasswd pass file -nopw -accept string + -afteraccept string -gone string -users list + -noshm -flipbyteorder -onetile + -solid [color] -blackout string -xinerama + -noxinerama -xtrap -xrandr [mode] + -padgeom WxH -o logfile -flag file + -rc filename -norc -h, -help + -?, -opts -V, -version -dbg + -q -bg -modtweak + -nomodtweak -xkb -noxkb + -capslock -skip_lockkeys -skip_keycodes string + -sloppy_keys -skip_dups -noskip_dups + -add_keysyms -noadd_keysyms -clear_mods + -clear_keys -remap string -norepeat + -repeat -nofb -nobell + -nosel -noprimary -nosetprimary + -noclipboard -nosetclipboard -seldir string + -cursor [mode] -nocursor -arrow n + -noxfixes -alphacut n -alphafrac fraction + -alpharemove -noalphablend -nocursorshape + -cursorpos -nocursorpos -xwarppointer + -buttonmap string -nodragging -wireframe [str] + -nowireframe -wirecopyrect mode -nowirecopyrect + -debug_wireframe -scrollcopyrect mode -noscrollcopyrect + -scr_area n -scr_skip list -scr_inc list + -scr_keys list -scr_term list -scr_keyrepeat lo-hi + -scr_parms string -fixscreen string -debug_scroll + -noxrecord -grab_buster -nograb_buster + -debug_grabs -debug_sel -pointer_mode n + -input_skip n -speeds rd,bw,lat -wmdt string + -debug_pointer -debug_keyboard -defer time + -wait time -wait_ui factor -nowait_bog + -slow_fb time -readtimeout n -nap + -nonap -sb time -nofbpm + -fbpm -noxdamage -xd_area A + -xd_mem f -sigpipe string -threads + -nothreads -fs f -gaps n + -grow n -fuzz n -debug_tiles + -snapfb -rawfb string -freqtab file + -pipeinput cmd -gui [gui-opts] -remote command + -query variable -QD variable -sync + -noremote -yesremote -unsafe + -safer -privremote -nocmds + -deny_all libvncserver options: -rfbport port TCP port for RFB protocol @@ -7131,7 +7213,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.8.1 lastmod: 2006-06-03 +x11vnc: allow VNC connections to real X11 displays. 0.8.2 lastmod: 2006-06-08 (type "x11vnc -opts" to just list the options.) @@ -7183,7 +7265,8 @@ Options: -display disp X11 server display to connect to, usually :0. The X server process must be running on same machine and support MIT-SHM. Equivalent to setting the DISPLAY - environment variable to "disp". + environment variable to "disp". See the description + below of the "-display WAIT:..." extensions. -auth file Set the X authority file to be "file", equivalent to setting the XAUTHORITY environment variable to "file" before startup. Same as -xauth file. See Xsecurity(7), @@ -7412,7 +7495,7 @@ Options: and only loop 5 times. -timeout n Exit unless a client connects within the first n seconds after startup. --inetd Launched by inetd(1): stdio instead of listening socket. +-inetd Launched by inetd(8): stdio instead of listening socket. Note: if you are not redirecting stderr to a log file (via shell 2> or -o option) you MUST also specify the -q option, otherwise the stderr goes to the viewer which @@ -7539,6 +7622,691 @@ Options: and last line be "__BEGIN_VIEWONLY__" to have 2 full-access passwords) +-unixpw [list] Use Unix username and password authentication. x11vnc + uses the su(1) program to verify the user's password. + [list] is an optional comma separated list of allowed + Unix usernames. See below for per-user options that + can be applied. + + A familiar "login:" and "Password:" dialog is + presented to the user on a black screen inside the + vncviewer. The connection is dropped if the user fails + to supply the correct password in 3 tries or does not + send one before a 25 second timeout. Existing clients + are view-only during this period. + + Since the detailed behavior of su(1) can vary from + OS to OS and for local configurations, test the mode + carefully on your systems before using it in production. + Test different combinations of valid/invalid usernames + and valid/invalid passwords to see if it behaves as + expected. x11vnc will attempt to be conservative and + reject a login if anything abnormal occurs. + + On FreeBSD and the other BSD's by default it is + impossible for the user running x11vnc to validate + his *own* password via su(1) (evidently commenting out + the pam_self.so entry in /etc/pam.d/su eliminates this + problem). So the x11vnc login will always *fail* for + this case (even when the correct password is supplied). + + A possible workaround for this would be to start + x11vnc as root with the "-users +nobody" option to + immediately switch to user nobody. Another source of + problems are PAM modules that prompt for extra info, + e.g. password aging modules. These logins will fail + as well even when the correct password is supplied. + + **IMPORTANT**: to prevent the Unix password being sent + in *clear text* over the network, one of two schemes + will be enforced: 1) the -ssl builtin SSL mode, or 2) + require both -localhost and -stunnel be enabled. + + Method 1) ensures the traffic is encrypted between + viewer and server. A PEM file will be required, see the + discussion under -ssl below (under some circumstances + a temporary one can be automatically generated). + + Method 2) requires the viewer connection to appear + to come from the same machine x11vnc is running on + (e.g. from a ssh -L port redirection). And that the + -stunnel SSL mode be used for encryption over the + network.(see the description of -stunnel below). + + Note: as a convenience, if you ssh(1) in and start + x11vnc it will check if the environment variable + SSH_CONNECTION is set and appears reasonable. If it + does, then the -ssl or -stunnel requirement will be + dropped since it is assumed you are using ssh for the + encrypted tunnelling. -localhost is still enforced. + Use -ssl or -stunnel to force SSL usage even if + SSH_CONNECTION is set. + + To override the above restrictions you can set + environment variables before starting x11vnc: + + Set UNIXPW_DISABLE_SSL=1 to disable requiring either + -ssl or -stunnel. Evidently you will be using a + different method to encrypt the data between the + vncviewer and x11vnc: perhaps ssh(1) or an IPSEC VPN. + + Note that use of -localhost with ssh(1) is roughly + the same as requiring a Unix user login (since a Unix + password or the user's public key authentication is + used by sshd on the machine where x11vnc runs and only + local connections from that machine are accepted) + + Set UNIXPW_DISABLE_LOCALHOST=1 to disable the -localhost + requirement in Method 2). One should never do this + (i.e. allow the Unix passwords to be sniffed on the + network). + + Regarding reverse connections (e.g. -R connect:host + and -connect host), when the -localhost constraint is + in effect then reverse connections can only be used + to connect to the same machine x11vnc is running on + (default port 5500). Please use a ssh or stunnel port + redirection to the viewer machine to tunnel the reverse + connection over an encrypted channel. Note that in -ssl + mode reverse connection are disabled (see below). + + In -inetd mode the Method 1) will be enforced (not + Method 2). With -ssl in effect reverse connections + are disabled. If you override this via env. var, be + sure to also use encryption from the viewer to inetd. + Tip: you can also have your own stunnel spawn x11vnc + in -inetd mode (thereby bypassing inetd). See the FAQ + for details. + + The user names in the comma separated [list] can have + per-user options after a ":", e.g. "fred:opts" + where "opts" is a "+" separated list of + "viewonly", "fullaccess", "input=XXXX", or + "deny", e.g. "karl,fred:viewonly,boss:input=M". + For "input=" it is the K,M,B,C described under -input. + + If a user in the list is "*" that means those + options apply to all users. It also means all users + are allowed to log in after supplying a valid password. + Use "deny" to explicitly deny some users if you use + "*" to set a global option. + + There are also some utilities for testing password + if [list] starts with the "%" character. See the + quick_pw() function in the source for details. + +-unixpw_nis [list] As -unixpw above, however do not use su(1) but rather + use the traditional getpwnam(3) + crypt(3) method to + verify passwords instead. This requires that the + encrypted passwords be readable. Passwords stored + in /etc/shadow will be inaccessible unless x11vnc + is run as root. + + This is called "NIS" mode simply because in most + NIS setups the user encrypted passwords are accessible + (e.g. "ypcat passwd"). NIS is not required for this + mode to work (only that getpwnam(3) return the encrypted + password is required), but it is unlikely it will work + for any other modern environment. All of the -unixpw + options and contraints apply. + +-display_WAIT :... A special usage mode for the normal -display option. + Useful with -unixpw, but can be used independently + of it. If the display string begins with WAIT: then + x11vnc waits until a VNC client connects before opening + the X display (or -rawfb device). + + This could be useful for delaying opening the display + for certain usage modes (say if x11vnc is started at + boot time and no X server is running or users logged + in yet). + + If the string is, e.g. WAIT:0.0 or WAIT:1, i.e. "WAIT" + in front of a normal X display, then that indicated + display is used. A more interesting case is like this: + + WAIT:cmd=/usr/local/bin/find_display + + in which case the command after "cmd=" is run to + dynamically work out the DISPLAY and optionally the + XAUTHORITY data. The first line of the command output + must be of the form DISPLAY=<xdisplay>. Any remaining + output is taken as XAUTHORITY data. It can be either + of the form XAUTHORITY=<file> or raw xauthority data for + the display (e.g. "xauth extract - $DISPLAY" output). + + In the case of -unixpw, then the above command is run + as the user who just authenticated via the login and + password prompt. + + Thus the combination of -display WAIT:cmd=... and + -unixpw allows automatic pairing of an unix + authenticated VNC user with his desktop. This could + be very useful on SunRays and also any system where + multiple users share a given machine. The user does + not need to remember special ports or passwords set up + for his desktop and VNC. + + A nice way to use WAIT:cmd=... is out of inetd(8) + (it automatically forks a new x11vnc for each user). + You can have the x11vnc inetd spawned process run as, + say, root or nobody. When run as root (for either + inetd or display manager), you can also supply the + option "-users unixpw=" to have the x11vnc process + switch to the user as well. Note: there will be a 2nd + SSL helper process that will not switch, but it is only + encoding and decoding the stream at that point. + + As a special case, WAIT:cmd=FINDDISPLAY will run a + script that works on most Unixes to determine a user's + DISPLAY variable and xauthority data. this is TBD. + + Finally, one can insert a geometry between colons, + e.g. WAIT:1280x1024:... to set the size of the display + the VNC client first attaches to since some VNC viewers + will not automatically adjust to a new framebuffer size. + +-ssl [pem] Use the openssl library (www.openssl.org) to provide a + built-in encrypted SSL tunnel between VNC viewers and + x11vnc. This requires libssl support to be compiled + into x11vnc at build time. If x11vnc is not built + with libssl support it will exit immediately when -ssl + is prescribed. + + [pem] is optional, use "-ssl /path/to/mycert.pem" + to specify a PEM certificate file to use to identify + and provide a key for this server. See openssl(1) for + more info about PEMs and the -sslGenCert option below. + + The connecting VNC viewer SSL tunnel can optionally + authenticate this server if they have the public + key part of the certificate (or a common certificate + authority, CA, is a more sophisicated way to verify + this server's cert, see -sslGenCA below). This is + used to prevent man-in-the-middle attacks. Otherwise, + if the VNC viewer accepts this server's key without + verification, at least the traffic is protected + from passive sniffing on the network (but NOT from + man-in-the-middle attacks). + + If [pem] is not supplied and the openssl(1) utility + command exists in PATH, then a temporary, self-signed + certificate will be generated for this session (this + may take 5-30 seconds on slow machines). If openssl(1) + cannot be used to generate a temporary certificate + x11vnc exits immediately. + + If successful in using openssl(1) to generate a + temporary certificate, the public part of it will be + displayed to stderr (e.g. one could copy it to the + client-side to provide authentication of the server to + VNC viewers.) See following paragraphs for how to save + keys to reuse when x11vnc is restarted. + + Set the env. var. X11VNC_SHOW_TMP_PEM=1 to have x11vnc + print out the entire certificate, including the PRIVATE + KEY part, to stderr. One could reuse this cert if saved + in a [pem] file. Similarly, set X11VNC_KEEP_TMP_PEM=1 + to not delete the temporary PEM file: the file name + will be printed to stderr (so one could move it to + a safe place for reuse). You will be prompted for a + passphrase for the private key. + + If [pem] is "SAVE" then the certificate will be saved + to the file ~/.vnc/certs/server.pem, or if that file + exists it will be used directly. Similarly, if [pem] + is "SAVE_PROMPT" the server.pem certificate will be + made based on your answers to its prompts for info such + as OrganizationalName, CommonName, etc. + + Use "SAVE-<string>" and "SAVE_PROMPT-<string>" + to refer to the file ~/.vnc/certs/server-<string>.pem + instead. E.g. "SAVE-charlie" will store to the file + ~/.vnc/certs/server-charlie.pem + + See -ssldir below to use a directory besides the + default ~/.vnc/certs + + Example: x11vnc -ssl SAVE -display :0 ... + + Reverse connections are disabled in -ssl mode because + there is no way to ensure that data channel will + be encrypted. Set X11VNC_SSL_ALLOW_REVERSE=1 to + override this. + + Your VNC viewer will also need to be able to connect + via SSL. See the discussion below under -stunnel and + the FAQ (ssl_vncviewer script) for how this might be + achieved. E.g. on Unix it is easy to write a shell + script that starts up stunnel and then vncviewer. + Also in the x11vnc source a SSL enabled Java VNC Viewer + applet is provided in the classes/ssl directory. + +-ssldir [dir] Use [dir] as an alternate ssl certificate and key + management toplevel directory. The default is + ~/.vnc/certs + + This directory is used to store server and other + certificates and keys and also other materials. E.g. in + the simplest case, "-ssl SAVE" will store the x11vnc + server cert in [dir]/server.pem + + Use of alternate directories via -ssldir allows you to + manage multiple VNC Certificate Authority (CA) keys. + Another use is if ~/.vnc/cert is on an NFS share you + might want your certificates and keys to be on a local + filesystem to prevent network snooping (for example + -ssldir /var/lib/x11vnc-certs). + + -ssldir affects nearly all of the other -ssl* options, + e.g. -ssl SAVE, -sslGenCert, etc.. + +-sslverify [path] For either of the -ssl or -stunnel modes, use [path] + to provide certificates to authenticate incoming VNC + *Client* connections (normally only the server is + authenticated in SSL.) This can be used as a method + to replace standard password authentication of clients. + + If [path] is a directory it contains the client (or CA) + certificates in separate files. If [path] is a file, + it contains multiple certificates. See special tokens + below. These correspond to the "CApath = dir" and + "CAfile = file" stunnel options. See the stunnel(8) + manpage for details. + + Examples: + x11vnc -ssl -sslverify ~/my.pem + x11vnc -ssl -sslverify ~/my_pem_dir/ + + Note that if [path] is a directory, it must contain + the certs in separate files named like <HASH>.0, where + the value of <HASH> is found by running the command + "openssl x509 -hash -noout -in file.crt". Evidently + one uses <HASH>.1 if there is a collision... + + The the key-management utility "-sslCertInfo HASHON" + and "-sslCertInfo HASHOFF" will create/delete these + hashes for you automatically (via symlink) in the HASH + subdirs it manages. Then you can point -sslverify to + the HASH subdir. + + Special tokens: in -ssl mode, if [path] is not a file or + a directory, it is taken as a comma separated list of + tokens that are interpreted as follows: + + If a token is "CA" that means load the CA/cacert.pem + file from the ssl directory. If a token is "clients" + then all the files clients/*.crt in the ssl directory + are loaded. Otherwise the file clients/token.crt + is attempted to be loaded. As a kludge, use a token + like ../server-foo to load a server cert if you find + that necessary. + + Use -ssldir to use a directory different from the + ~/.vnc/certs default. + + Note that if the "CA" cert is loaded you do not need + to load any of the certs that have been signed by it. + You will need to load any additional self-signed certs + however. + + Examples: + x11vnc -ssl -sslverify CA + x11vnc -ssl -sslverify self:fred,self:jim + x11vnc -ssl -sslverify CA,clients + + Usually "-sslverify CA" is the most effective. + See the -sslGenCA and -sslGenCert options below for + how to set up and manage the CA framework. + + + + NOTE: the following utilities, -sslGenCA, -sslGenCert, + -sslEncKey, and -sslCertInfo are provided for + completeness, but for casual usage they are overkill. + + They provide VNC Certificate Authority (CA) key creation + and server / client key generation and signing. So they + provide a basic Public Key management framework for + VNC-ing with x11vnc. (note that they require openssl(1) + be installed on the system) + + However, the simplest usage mode (where x11vnc + automatically generates its own, self-signed, temporary + key and the VNC viewers always accept it, e.g. accepting + via a dialog box) is probably safe enough for most + scenarios. CA management is not needed. + + To protect against Man-In-The-Middle attacks the + simplest mode can be improved by using "-ssl SAVE" + to have x11vnc create a longer term self-signed + certificate, and then (safely) copy the corresponding + public key cert to the desired client machines (care + must be taken the private key part is not stolen; + you will be prompted for a passphrase). + + So keep in mind no CA key creation or management + (-sslGenCA and -sslGenCert) is needed for either of + the above two common usage modes. + + One might want to use -sslGenCA and -sslGenCert + if you had a large number of VNC client and server + workstations. That way the administrator could generate + a single CA key with -sslGenCA and distribute its + certificate part to all of the workstations. + + Next, he could create signed VNC server keys + (-sslGenCert server ...) for each workstation or user + that then x11vnc would use to authenticate itself to + any VNC client that has the CA cert. + + Optionally, the admin could also make it so the + VNC clients themselves are authenticated to x11vnc + (-sslGenCert client ...) For this -sslverify would be + pointed to the CA cert (and/or self-signed certs). + + x11vnc will be able to use all of these cert and + key files. On the VNC client side, they will need to + be "imported" somehow. Web browsers have "Manage + Certificates" actions as does the Java applet plugin + Control Panel. stunnel can also use these files (see + the ssl_vncviewer example script in the FAQ.) + +-sslGenCA [dir] Generate your own Certificate Authority private key, + certificate, and other files in directory [dir]. + + If [dir] is not supplied, a -ssldir setting is used, + or otherwise ~/.vnc/certs is used. + + This command also creates directories where server and + client certs and keys will be stored. The openssl(1) + program must be installed on the system and available + in PATH. + + After the CA files and directories are created the + command exits; the VNC server is not run. + + You will be prompted for information to put into the CA + certificate. The info does not have to be accurate just + as long as clients accept the cert for VNC connections. + You will also need to supply a passphrase of at least + 4 characters for the CA private key. + + Once you have generated the CA you can distribute + its certificate part, [dir]/CA/cacert.pem, to other + workstations where VNC viewers will be run. One will + need to "import" this certicate in the applications, + e.g. Web browser, Java applet plugin, stunnel, etc. + Next, you can create and sign keys using the CA with + the -sslGenCert option below. + + Examples: + x11vnc -sslGenCA + x11vnc -sslGenCA ~/myCAdir + x11vnc -ssldir ~/myCAdir -sslGenCA + + (the last two lines are equivalent) + +-sslGenCert type name Generate a VNC server or client certificate and private + key pair signed by the CA created previously with + -sslGenCA. The openssl(1) program must be installed + on the system and available in PATH. + + After the Certificate is generated the command exits; + the VNC server is not run. + + The type of key to be generated is the string "type". + It is either "server" (i.e. for use by x11vnc) or + "client" (for a VNC viewer). Note that typically + only "server" is used: the VNC clients authenticate + themselves by a non-public-key method (e.g. VNC or + unix password). "type" is required. + + An arbitrary default name you want to associate with + the key is supplied by the "name" string. You can + change it at the various prompts when creating the key. + "name" is optional. + + If name is left blank for clients keys then "nobody" + is used. If left blank for server keys, then the + primary server key: "server.pem" is created (this + is the saved one referenced by "-ssl SAVE" when the + server is started) + + If "name" begins with the string "self:" then + a self-signed certificate is created instead of one + signed by your CA key. + + If "name" begins with the string "req:" then only a + key (.key) and a certificate signing *request* (.req) + are generated. You can then send the .req file to + an external CA (even a professional one, e.g. Thawte) + and then combine the .key and the received cert into + the .pem file with the same basename. + + The distinction between "server" and "client" is + simply the choice of output filenames and sub-directory. + This makes it so the -ssl SAVE-name option can easily + pick up the x11vnc PEM file this option generates. + And similarly makes it easy for the -sslverify option + to pick up your client certs. + + There is nothing special about the filename or directory + location of either the "server" and "client" certs. + You can rename the files or move them to wherever + you like. + + Precede this option with -ssldir [dir] to use a + directory other than the default ~/.vnc/certs You will + need to run -sslGenCA on that directory first before + doing any -sslGenCert key creation. + + Note you cannot recreate a cert with exactly the same + distiguished name (DN) as an existing one. To do so, + you will need to edit the [dir]/CA/index.txt file to + delete the line. + + Similar to -sslGenCA, you will be prompted to fill + in some information that will be recorded in the + certificate when it is created. Tip: if you know + the fully-quailified hostname other people will be + connecting to you can use that as the CommonName "CN" + to avoid some applications (e.g. web browsers and java + plugin) complaining it does not match the hostname. + + You will also need to supply the CA private key + passphrase to unlock the private key created from + -sslGenCA. This private key is used to sign the server + or client certicate. + + The "server" certs can be used by x11vnc directly by + pointing to them via the -ssl [pem] option. The default + file will be ~/.vnc/certs/server.pem. This one would + be used by simply typing -ssl SAVE. The pem file + contains both the certificate and the private key. + server.crt file contains the cert only. + + The "client" cert + private key file will need + to be copied and imported into the VNC viewer + side applications (Web browser, Java plugin, + stunnel, etc.) Once that is done you can delete the + "client" private key file on this machine since + it is only needed on the VNC viewer side. The, + e.g. ~/.vnc/certs/clients/<name>.pem contains both + the cert and private key. The <name>.crt contains the + certificate only. + + NOTE: It is very important to know one should always + generate new keys with a passphrase. Otherwise if an + untrusted user steals the key file he could use it to + masquerade as the x11vnc server (or VNC viewer client). + You will be prompted whether to encrypt the key with + a passphrase or not. It is recommended that you do. + One inconvenience to a passphrase is that it must + be suppled every time x11vnc or the client app is + started up. + + Examples: + + x11vnc -sslGenCert server + x11vnc -ssl SAVE -display :0 ... + + and then on viewer using ssl_vncviewer stunnel wrapper + (see the FAQ): + ssl_vncviewer -verify ./cacert.crt hostname:0 + + (this assumes the cacert.crt cert from -sslGenCA + was safely copied to the VNC viewer machine where + ssl_vncviewer is run) + + Example using a name: + + x11vnc -sslGenCert server charlie + x11vnc -ssl SAVE-charlie -display :0 ... + + Example for a client certificate (rarely used): + + x11vnc -sslGenCert client roger + scp ~/.vnc/certs/clients/roger.pem somehost:. + rm ~/.vnc/certs/clients/roger.pem + + x11vnc is then started with the the option -sslverify + ~/.vnc/certs/clients/roger.crt (or simply -sslverify + roger), and on the viewer user on somehost could do + for example: + + ssl_vncviewer -mycert ./roger.pem hostname:0 + +-sslEncKey [pem] Utility to encrypt an existing PEM file with a + passphrase you supply when prompted. For that key to be + used (e.g. by x11vnc) the passphrase must be supplied + each time. + + The "SAVE" notation described under -ssl applies as + well. (precede this option with -ssldir [dir] to refer + a directory besides the default ~/.vnc/certs) + + The openssl(1) program must be installed on the system + and available in PATH. After the Key file is encrypted + the command exits; the VNC server is not run. + + Examples: + x11vnc -sslEncKey /path/to/foo.pem + x11vnc -sslEncKey SAVE + x11vnc -sslEncKey SAVE-charlie + +-sslCertInfo [pem] Prints out information about an existing PEM file. + In addition the public certificate is also printed. + The openssl(1) program must be in PATH. Basically the + command "openssl x509 -text" is run on the pem. + + The "SAVE" notation described under -ssl applies + as well. + + Using "LIST" will give a list of all certs being + managed (in the ~/.vnc/certs dir, use -ssldir to refer + to another dir). "ALL" will print out the info for + every managed key (this can be very long). Giving a + client or server cert shortname will also try a lookup + (e.g. -sslCertInfo charlie). Use "LISTL" or "LL" + for a long (ls -l style) listing. + + Using "HASHON" will create subdirs [dir]/HASH and + [dir]/HASH with OpenSSL hash filenames (e.g. 0d5fbbf1.0) + symlinks pointing up to the corresponding *.crt file. + ([dir] is ~/.vnc/certs or one given by -ssldir.) + This is a useful way for other OpenSSL applications + (e.g. stunnel) to access all of the certs without + having to concatenate them. x11vnc will not use them + unless you specifically reference them. "HASHOFF" + removes these HASH subdirs. + + The LIST, LISTL, LL, ALL, HASHON, HASHOFF words can + also be lowercase, e.g. "list". + +-sslDelCert [pem] Prompts you to delete all .crt .pem .key .req files + associated with [pem]. "SAVE" and lookups as in + -sslCertInfo apply as well. + + +-stunnel [pem] Use the stunnel(8) (www.stunnel.org) to provide an + encrypted SSL tunnel between viewers and x11vnc. + + This external tunnel method was implemented prior to the + integrated -ssl encryption described above. It still + works well. This requires stunnel to be installed + on the system and available via PATH (n.b. stunnel is + often installed in sbin directories). Version 4.x of + stunnel is assumed (but see -stunnel3 below.) + + [pem] is optional, use "-stunnel /path/to/stunnel.pem" + to specify a PEM certificate file to pass to stunnel. + Whether one is needed or not depends on your stunnel + configuration. stunnel often generates one at install + time. See the stunnel documentation for details. + + stunnel is started up as a child process of x11vnc and + any SSL connections stunnel receives are decrypted and + sent to x11vnc over a local socket. The strings + "The SSL VNC desktop is ..." and "SSLPORT=..." + are printed out at startup to indicate this. + + The -localhost option is enforced by default + to avoid people routing around the SSL channel. + Set STUNNEL_DISABLE_LOCALHOST=1 before starting x11vnc + to disable the requirement. + + Your VNC viewer will also need to be able to connect via + SSL. Unfortunately not too many do this. UltraVNC has + an encryption plugin but it does not seem to be SSL. + + Also, in the x11vnc distribution, a patched TightVNC + Java applet is provided in classes/ssl that does SSL + connections (only). + + It is also not too difficult to set up an stunnel or + other SSL tunnel on the viewer side. A simple example + on Unix using stunnel 3.x is: + + % stunnel -c -d localhost:5901 -r remotehost:5900 + % vncviewer localhost:1 + + For Windows, stunnel has been ported to it and there + are probably other such tools available. See the FAQ + for more examples. + +-stunnel3 [pem] Use version 3.x stunnel command line syntax instead of + version 4.x + +-https [port] Choose a separate HTTPS port (-ssl mode only). + + In -ssl mode, it turns out you can use the + single VNC port (e.g. 5900) for both VNC and HTTPS + connections. (HTTPS is used to retrieve a SSL-aware + VncViewer.jar applet that is provided with x11vnc). + Since both use SSL the implementation was extended to + detect if HTTP traffic (i.e. GET) is taking place and + handle it accordingly. The URL would be, e.g.: + + https://mymachine.org:5900/ + + This is convenient for firewalls, etc, because only one + port needs to be allowed in. However, this heuristic + adds a few seconds delay to each connection and can be + unreliable (especially if the user takes much time to + ponder the Certificate dialogs in his browser, Java VM, + or VNC Viewer applet. That's right 3 separate "Are + you sure you want to connect" dialogs!) + + So use the -https option to provide a separate, more + reliable HTTPS port that x11vnc will listen on. If + [port] is not provided (or is 0), one is autoselected. + The URL to use is printed out at startup. + + The SSL Java applet directory is specified via the + -httpdir option. If not supplied it will try to guess + the directory as though the -http option was supplied. + -usepw If no other password method was supplied on the command line, first look for ~/.vnc/passwd and if found use it with -rfbauth; next, look for ~/.vnc/passwdfile and @@ -7547,6 +8315,9 @@ Options: the -rfbauth option. If none of these succeed x11vnc exits immediately. + Note: -unixpw currently does not count as a password + method by this option. + -storepasswd pass file Store password "pass" as the VNC password in the file "file". Once the password is stored the program exits. Use the password via "-rfbauth file" @@ -7569,7 +8340,7 @@ Options: otherwise the client is rejected. See below for an extension to accept a client view-only. - If x11vnc is running as root (say from inetd(1) or from + If x11vnc is running as root (say from inetd(8) or from display managers xdm(1), gdm(1), etc), think about the security implications carefully before supplying this option (likewise for the -gone option). @@ -7640,7 +8411,7 @@ Options: Unlike -accept, the command return code is not interpreted by x11vnc. Example: -gone 'xlock &' --users list If x11vnc is started as root (say from inetd(1) or from +-users list If x11vnc is started as root (say from inetd(8) or from display managers xdm(1), gdm(1), etc), then as soon as possible after connections to the X display are established try to switch to one of the users in the @@ -7653,38 +8424,47 @@ Options: to make some of the *external* utility commands x11vnc occasionally runs work properly. In particular under GNOME and KDE to implement the "-solid color" feature - external commands (gconftool-2 and dcop) must be run - as the user owning the desktop session. Since this - option switches userid it also affects the userid used - to run the processes for the -accept and -gone options. - It also affects the ability to read files for options - such as -connect, -allow, and -remap. Note that the - -connect file is also sometimes written to. - - So be careful with this option since in many situations + external commands (gconftool-2 and dcop) unfortunately + must be run as the user owning the desktop session. + Since this option switches userid it also affects the + userid used to run the processes for the -accept and + -gone options. It also affects the ability to read + files for options such as -connect, -allow, and -remap. + Note that the -connect file is also sometimes written + to. + + So be careful with this option since in some situations its use can decrease security. - The switch to a user will only take place if the - display can still be successfully opened as that user - (this is primarily to try to guess the actual owner + In general the switch to a user will only take place + if the display can still be successfully opened as that + user (this is primarily to try to guess the actual owner of the session). Example: "-users fred,wilma,betty". Note that a malicious user "barney" by quickly using - "xhost +" when logging in may get x11vnc to switch - to user "fred". What happens next? + "xhost +" when logging in may possibly get the x11vnc + process to switch to user "fred". What happens next? Under display managers it may be a long time before - the switch succeeds (i.e. a user logs in). To make - it switch immediately regardless if the display + the switch succeeds (i.e. a user logs in). To instead + make it switch immediately regardless if the display can be reopened prefix the username with the "+" character. E.g. "-users +bob" or "-users +nobody". + The latter (i.e. switching immediately to user "nobody") is probably the only use of this option that increases security. + In -unixpw mode, if "-users unixpw=" is supplied + then after a user authenticates himself via the + -unixpw mechanism, x11vnc will try to switch to that + user as though "-users +username" had been supplied. + If you want to limit which users this will be done for, + provide them as a comma separated list after "unixpw=" + To immediately switch to a user *before* connections to the X display are made or any files opened use the "=" character: "-users =bob". That user needs to - be able to open the X display of course. + be able to open the X display and any files of course. The special user "guess=" means to examine the utmpx database (see who(1)) looking for a user attached to @@ -7692,18 +8472,18 @@ Options: and try him/her. To limit the list of guesses, use: "-users guess=bob,betty". - Even more sinister is the special user "lurk=" that - means to try to guess the DISPLAY from the utmpx login - database as well. So it "lurks" waiting for anyone - to log into an X session and then connects to it. - Specify a list of users after the = to limit which - users will be tried. To enable a different searching - mode, if the first user in the list is something like - ":0" or ":0-2" that indicates a range of DISPLAY - numbers that will be tried (regardless of whether - they are in the utmpx database) for all users that - are logged in. Examples: "-users lurk=" and also - "-users lurk=:0-1,bob,mary" + Even more sinister is the special user "lurk=" + that means to try to guess the DISPLAY from the utmpx + login database as well. So it "lurks" waiting for + anyone to log into an X session and then connects to it. + Specify a list of users after the = to limit which users + will be tried. To enable a different searching mode, if + the first user in the list is something like ":0" or + ":0-2" that indicates a range of DISPLAY numbers that + will be tried (regardless of whether they are in the + utmpx database) for all users that are logged in. Also + see the "-display WAIT:..." functionality. Examples: + "-users lurk=" and also "-users lurk=:0-1,bob,mary" Be especially careful using the "guess=" and "lurk=" modes. They are not recommended for use on machines @@ -7732,7 +8512,7 @@ Options: commands are run for GNOME and KDE respectively. Other desktops won't work, e.g. Xfce (send us the corresponding commands if you find them). If x11vnc is - running as root (inetd(1) or gdm(1)), the -users option + running as root (inetd(8) or gdm(1)), the -users option may be needed for GNOME and KDE. If x11vnc guesses your desktop incorrectly, you can force it by prefixing color with "gnome:", "kde:", "cde:" or "root:". @@ -8748,7 +9528,7 @@ Options: mode if the bpp is 24. video4linux: on Linux some attempt is made to handle - video devices (webcams or tv tuners) automatically. + video devices (webcams or TV tuners) automatically. The idea is the WxHxB will be extracted from the device itself. So if you do not supply "@WxHxB... parameters x11vnc will try to determine them. It first @@ -8795,7 +9575,7 @@ Options: 24, and 32 respectively). See http://www.linuxtv.org for more info (V4L api). - For tv/rf tuner cards one can set the tuning mode + For TV/rf tuner cards one can set the tuning mode via tun=XXX where XXX can be one of PAL, NTSC, SECAM, or AUTO. @@ -9383,7 +10163,8 @@ n scale_str scaled_x scaled_y scale_numer scale_denom scale_fac scaling_blend scaling_nomult4 scaling_pad scaling_interpolate inetd privremote unsafe safer nocmds - passwdfile usepw using_shm + passwdfile unixpw unixpw_nis unixpw_list ssl ssl_pem + sslverify stunnel stunnel_pem https usepw using_shm logfile o flag rc norc h help V version lastmod bg sigpipe threads readrate netrate netlatency pipeinput clients client_count pid ext_xtest ext_xtrap ext_xrecord diff --git a/x11vnc/cleanup.c b/x11vnc/cleanup.c index f162b37..0d5926e 100644 --- a/x11vnc/cleanup.c +++ b/x11vnc/cleanup.c @@ -155,7 +155,7 @@ void clean_up_exit (int ret) { } #endif /* XXX rdpy_ctrl, etc. cannot close w/o blocking */ - XCloseDisplay(dpy); + XCloseDisplay_wr(dpy); X_UNLOCK; fflush(stderr); @@ -311,6 +311,7 @@ static void crash_shell(void) { crash_shell_help(); } else if (*str == 's' && *(str+1) == '\0') { sprintf(cmd, "sh -c '(%s) &'", crash_stack_command1); + /* crash */ if (no_external_cmds) { fprintf(stderr, "\nno_external_cmds=%d\n", no_external_cmds); diff --git a/x11vnc/connections.c b/x11vnc/connections.c index e1c9e88..ec77101 100644 --- a/x11vnc/connections.c +++ b/x11vnc/connections.c @@ -448,6 +448,7 @@ static int run_user_command(char *cmd, rfbClientPtr client, char *mode) { sprintf(str, "%d", client_count); set_env("RFB_CLIENT_COUNT", str); + /* gone, accept, afteraccept */ if (no_external_cmds) { rfbLogEnable(1); rfbLog("cannot run external commands in -nocmds mode:\n"); diff --git a/x11vnc/gui.c b/x11vnc/gui.c index 5c69b91..99d35ba 100644 --- a/x11vnc/gui.c +++ b/x11vnc/gui.c @@ -5,6 +5,7 @@ #include "win_utils.h" #include "remote.h" #include "cleanup.h" +#include "xwrappers.h" #include "tkx11vnc.h" @@ -229,15 +230,15 @@ if (0) fprintf(stderr, "run_gui: %s -- %d %d\n", gui_xdisplay, connect_to_x11vnc } else { old_xauth = strdup(""); } - dpy = XOpenDisplay(x11vnc_xdisplay); + dpy = XOpenDisplay_wr(x11vnc_xdisplay); if (! dpy && auth_file) { set_env("XAUTHORITY", auth_file); - dpy = XOpenDisplay(x11vnc_xdisplay); + dpy = XOpenDisplay_wr(x11vnc_xdisplay); } if (! dpy && ! x11vnc_xdisplay) { /* worstest case */ x11vnc_xdisplay = strdup(":0"); - dpy = XOpenDisplay(x11vnc_xdisplay); + dpy = XOpenDisplay_wr(x11vnc_xdisplay); } if (! dpy) { rfbLog("gui: could not open x11vnc " @@ -310,7 +311,7 @@ if (0) fprintf(stderr, "run_gui: %s -- %d %d\n", gui_xdisplay, connect_to_x11vnc set_env("X11VNC_CONNECT_FILE", client_connect_file); } if (dpy) { - XCloseDisplay(dpy); + XCloseDisplay_wr(dpy); dpy = NULL; } if (old_xauth) { @@ -418,6 +419,7 @@ if (0) fprintf(stderr, "run_gui: %s -- %d %d\n", gui_xdisplay, connect_to_x11vnc set_env("X11VNC_ICON_FONT", icon_mode_font); } + /* gui */ if (no_external_cmds) { fprintf(stderr, "cannot run external commands in -nocmds " "mode:\n"); @@ -576,20 +578,20 @@ void do_gui(char *opts, int sleep) { fprintf(stderr, "starting gui, trying display: %s\n", gui_xdisplay); } - test_dpy = XOpenDisplay(gui_xdisplay); + test_dpy = XOpenDisplay_wr(gui_xdisplay); if (! test_dpy && auth_file) { if (getenv("XAUTHORITY") != NULL) { old_xauth = strdup(getenv("XAUTHORITY")); } set_env("XAUTHORITY", auth_file); - test_dpy = XOpenDisplay(gui_xdisplay); + test_dpy = XOpenDisplay_wr(gui_xdisplay); } if (! test_dpy) { if (! old_xauth && getenv("XAUTHORITY") != NULL) { old_xauth = strdup(getenv("XAUTHORITY")); } set_env("XAUTHORITY", ""); - test_dpy = XOpenDisplay(gui_xdisplay); + test_dpy = XOpenDisplay_wr(gui_xdisplay); } if (! test_dpy) { fprintf(stderr, "error: cannot connect to gui X DISPLAY: %s\n", @@ -603,7 +605,7 @@ void do_gui(char *opts, int sleep) { tray_manager_ok = 0; } } - XCloseDisplay(test_dpy); + XCloseDisplay_wr(test_dpy); if (start_x11vnc) { diff --git a/x11vnc/help.c b/x11vnc/help.c index 14713c2..dc89c68 100644 --- a/x11vnc/help.c +++ b/x11vnc/help.c @@ -69,7 +69,8 @@ void print_help(int mode) { "-display disp X11 server display to connect to, usually :0. The X\n" " server process must be running on same machine and\n" " support MIT-SHM. Equivalent to setting the DISPLAY\n" -" environment variable to \"disp\".\n" +" environment variable to \"disp\". See the description\n" +" below of the \"-display WAIT:...\" extensions.\n" "-auth file Set the X authority file to be \"file\", equivalent to\n" " setting the XAUTHORITY environment variable to \"file\"\n" " before startup. Same as -xauth file. See Xsecurity(7),\n" @@ -298,7 +299,7 @@ void print_help(int mode) { " and only loop 5 times.\n" "-timeout n Exit unless a client connects within the first n seconds\n" " after startup.\n" -"-inetd Launched by inetd(1): stdio instead of listening socket.\n" +"-inetd Launched by inetd(8): stdio instead of listening socket.\n" " Note: if you are not redirecting stderr to a log file\n" " (via shell 2> or -o option) you MUST also specify the -q\n" " option, otherwise the stderr goes to the viewer which\n" @@ -554,6 +555,62 @@ void print_help(int mode) { " for any other modern environment. All of the -unixpw\n" " options and contraints apply.\n" "\n" +"-display WAIT:... A special usage mode for the normal -display option.\n" +" Useful with -unixpw, but can be used independently\n" +" of it. If the display string begins with WAIT: then\n" +" x11vnc waits until a VNC client connects before opening\n" +" the X display (or -rawfb device).\n" +"\n" +" This could be useful for delaying opening the display\n" +" for certain usage modes (say if x11vnc is started at\n" +" boot time and no X server is running or users logged\n" +" in yet).\n" +"\n" +" If the string is, e.g. WAIT:0.0 or WAIT:1, i.e. \"WAIT\"\n" +" in front of a normal X display, then that indicated\n" +" display is used. A more interesting case is like this:\n" +"\n" +" WAIT:cmd=/usr/local/bin/find_display\n" +"\n" +" in which case the command after \"cmd=\" is run to\n" +" dynamically work out the DISPLAY and optionally the\n" +" XAUTHORITY data. The first line of the command output\n" +" must be of the form DISPLAY=<xdisplay>. Any remaining\n" +" output is taken as XAUTHORITY data. It can be either\n" +" of the form XAUTHORITY=<file> or raw xauthority data for\n" +" the display (e.g. \"xauth extract - $DISPLAY\" output).\n" +"\n" +" In the case of -unixpw, then the above command is run\n" +" as the user who just authenticated via the login and\n" +" password prompt.\n" +"\n" +" Thus the combination of -display WAIT:cmd=... and\n" +" -unixpw allows automatic pairing of an unix\n" +" authenticated VNC user with his desktop. This could\n" +" be very useful on SunRays and also any system where\n" +" multiple users share a given machine. The user does\n" +" not need to remember special ports or passwords set up\n" +" for his desktop and VNC.\n" +"\n" +" A nice way to use WAIT:cmd=... is out of inetd(8)\n" +" (it automatically forks a new x11vnc for each user).\n" +" You can have the x11vnc inetd spawned process run as,\n" +" say, root or nobody. When run as root (for either\n" +" inetd or display manager), you can also supply the\n" +" option \"-users unixpw=\" to have the x11vnc process\n" +" switch to the user as well. Note: there will be a 2nd\n" +" SSL helper process that will not switch, but it is only\n" +" encoding and decoding the stream at that point.\n" +"\n" +" As a special case, WAIT:cmd=FINDDISPLAY will run a\n" +" script that works on most Unixes to determine a user's\n" +" DISPLAY variable and xauthority data. this is TBD.\n" +"\n" +" Finally, one can insert a geometry between colons,\n" +" e.g. WAIT:1280x1024:... to set the size of the display\n" +" the VNC client first attaches to since some VNC viewers\n" +" will not automatically adjust to a new framebuffer size.\n" +"\n" "-ssl [pem] Use the openssl library (www.openssl.org) to provide a\n" " built-in encrypted SSL tunnel between VNC viewers and\n" " x11vnc. This requires libssl support to be compiled\n" @@ -689,24 +746,24 @@ void print_help(int mode) { " is attempted to be loaded. As a kludge, use a token\n" " like ../server-foo to load a server cert if you find\n" " that necessary.\n" -" \n" +"\n" " Use -ssldir to use a directory different from the\n" " ~/.vnc/certs default.\n" -" \n" +"\n" " Note that if the \"CA\" cert is loaded you do not need\n" " to load any of the certs that have been signed by it.\n" " You will need to load any additional self-signed certs\n" " however.\n" -" \n" +"\n" " Examples:\n" " x11vnc -ssl -sslverify CA\n" " x11vnc -ssl -sslverify self:fred,self:jim\n" " x11vnc -ssl -sslverify CA,clients\n" -" \n" +"\n" " Usually \"-sslverify CA\" is the most effective.\n" " See the -sslGenCA and -sslGenCert options below for\n" " how to set up and manage the CA framework.\n" -" \n" +"\n" "\n" "\n" " NOTE: the following utilities, -sslGenCA, -sslGenCert,\n" @@ -1092,7 +1149,7 @@ void print_help(int mode) { " otherwise the client is rejected. See below for an\n" " extension to accept a client view-only.\n" "\n" -" If x11vnc is running as root (say from inetd(1) or from\n" +" If x11vnc is running as root (say from inetd(8) or from\n" " display managers xdm(1), gdm(1), etc), think about the\n" " security implications carefully before supplying this\n" " option (likewise for the -gone option).\n" @@ -1163,75 +1220,84 @@ void print_help(int mode) { " Unlike -accept, the command return code is not\n" " interpreted by x11vnc. Example: -gone 'xlock &'\n" "\n" -"-users list If x11vnc is started as root (say from inetd(1) or from\n" +"-users list If x11vnc is started as root (say from inetd(8) or from\n" " display managers xdm(1), gdm(1), etc), then as soon\n" " as possible after connections to the X display are\n" " established try to switch to one of the users in the\n" " comma separated \"list\". If x11vnc is not running as\n" " root this option is ignored.\n" -" \n" +"\n" " Why use this option? In general it is not needed since\n" " x11vnc is already connected to the X display and can\n" " perform its primary functions. The option was added\n" " to make some of the *external* utility commands x11vnc\n" " occasionally runs work properly. In particular under\n" " GNOME and KDE to implement the \"-solid color\" feature\n" -" external commands (gconftool-2 and dcop) must be run\n" -" as the user owning the desktop session. Since this\n" -" option switches userid it also affects the userid used\n" -" to run the processes for the -accept and -gone options.\n" -" It also affects the ability to read files for options\n" -" such as -connect, -allow, and -remap. Note that the\n" -" -connect file is also sometimes written to.\n" -" \n" -" So be careful with this option since in many situations\n" +" external commands (gconftool-2 and dcop) unfortunately\n" +" must be run as the user owning the desktop session.\n" +" Since this option switches userid it also affects the\n" +" userid used to run the processes for the -accept and\n" +" -gone options. It also affects the ability to read\n" +" files for options such as -connect, -allow, and -remap.\n" +" Note that the -connect file is also sometimes written\n" +" to.\n" +"\n" +" So be careful with this option since in some situations\n" " its use can decrease security.\n" -" \n" -" The switch to a user will only take place if the\n" -" display can still be successfully opened as that user\n" -" (this is primarily to try to guess the actual owner\n" +"\n" +" In general the switch to a user will only take place\n" +" if the display can still be successfully opened as that\n" +" user (this is primarily to try to guess the actual owner\n" " of the session). Example: \"-users fred,wilma,betty\".\n" " Note that a malicious user \"barney\" by quickly using\n" -" \"xhost +\" when logging in may get x11vnc to switch\n" -" to user \"fred\". What happens next?\n" -" \n" +" \"xhost +\" when logging in may possibly get the x11vnc\n" +" process to switch to user \"fred\". What happens next?\n" +"\n" " Under display managers it may be a long time before\n" -" the switch succeeds (i.e. a user logs in). To make\n" -" it switch immediately regardless if the display\n" +" the switch succeeds (i.e. a user logs in). To instead\n" +" make it switch immediately regardless if the display\n" " can be reopened prefix the username with the \"+\"\n" " character. E.g. \"-users +bob\" or \"-users +nobody\".\n" +"\n" " The latter (i.e. switching immediately to user\n" " \"nobody\") is probably the only use of this option\n" " that increases security.\n" -" \n" +"\n" +" In -unixpw mode, if \"-users unixpw=\" is supplied\n" +" then after a user authenticates himself via the\n" +" -unixpw mechanism, x11vnc will try to switch to that\n" +" user as though \"-users +username\" had been supplied.\n" +" If you want to limit which users this will be done for,\n" +" provide them as a comma separated list after \"unixpw=\"\n" +"\n" " To immediately switch to a user *before* connections\n" " to the X display are made or any files opened use the\n" " \"=\" character: \"-users =bob\". That user needs to\n" -" be able to open the X display of course.\n" -" \n" +" be able to open the X display and any files of course.\n" +"\n" " The special user \"guess=\" means to examine the utmpx\n" " database (see who(1)) looking for a user attached to\n" " the display number (from DISPLAY or -display option)\n" " and try him/her. To limit the list of guesses, use:\n" " \"-users guess=bob,betty\".\n" -" \n" -" Even more sinister is the special user \"lurk=\" that\n" -" means to try to guess the DISPLAY from the utmpx login\n" -" database as well. So it \"lurks\" waiting for anyone\n" -" to log into an X session and then connects to it.\n" -" Specify a list of users after the = to limit which\n" -" users will be tried. To enable a different searching\n" -" mode, if the first user in the list is something like\n" -" \":0\" or \":0-2\" that indicates a range of DISPLAY\n" -" numbers that will be tried (regardless of whether\n" -" they are in the utmpx database) for all users that\n" -" are logged in. Examples: \"-users lurk=\" and also\n" -" \"-users lurk=:0-1,bob,mary\"\n" -" \n" +"\n" +" Even more sinister is the special user \"lurk=\"\n" +" that means to try to guess the DISPLAY from the utmpx\n" +" login database as well. So it \"lurks\" waiting for\n" +" anyone to log into an X session and then connects to it.\n" +" Specify a list of users after the = to limit which users\n" +" will be tried. To enable a different searching mode, if\n" +" the first user in the list is something like \":0\" or\n" +" \":0-2\" that indicates a range of DISPLAY numbers that\n" +" will be tried (regardless of whether they are in the\n" +" utmpx database) for all users that are logged in. Also\n" +" see the \"-display WAIT:...\" functionality. Examples:\n" +" \"-users lurk=\" and also \"-users lurk=:0-1,bob,mary\"\n" +"\n" " Be especially careful using the \"guess=\" and \"lurk=\"\n" " modes. They are not recommended for use on machines\n" " with untrustworthy local users.\n" -" \n" +"\n" "-noshm Do not use the MIT-SHM extension for the polling.\n" " Remote displays can be polled this way: be careful this\n" " can use large amounts of network bandwidth. This is\n" @@ -1255,7 +1321,7 @@ void print_help(int mode) { " commands are run for GNOME and KDE respectively.\n" " Other desktops won't work, e.g. Xfce (send us the\n" " corresponding commands if you find them). If x11vnc is\n" -" running as root (inetd(1) or gdm(1)), the -users option\n" +" running as root (inetd(8) or gdm(1)), the -users option\n" " may be needed for GNOME and KDE. If x11vnc guesses\n" " your desktop incorrectly, you can force it by prefixing\n" " color with \"gnome:\", \"kde:\", \"cde:\" or \"root:\".\n" @@ -1554,7 +1620,7 @@ void print_help(int mode) { " default (see -noxfixes below). This can be disabled\n" " with -nocursor, and also some values of the \"mode\"\n" " option below.\n" -" \n" +"\n" " Note that under XFIXES cursors with transparency (alpha\n" " channel) will usually not be exactly represented and one\n" " may find Overlay preferable. See also the -alphacut\n" @@ -1606,7 +1672,7 @@ void print_help(int mode) { " pixel with alpha value less than n becomes completely\n" " transparent. Otherwise the pixel is completely opaque.\n" " Default %d\n" -" \n" +"\n" "-alphafrac fraction With the threshold in -alphacut some cursors will become\n" " almost completely transparent because their alpha values\n" " are not high enough. For those cursors adjust the\n" @@ -1872,7 +1938,7 @@ void print_help(int mode) { " So for a short time there are two (or more) block\n" " cursors on the screen. There are similar scenarios,\n" " (e.g. an output line is duplicated).\n" -" \n" +"\n" " These transients are induced by the approximation of\n" " scroll detection (e.g. it detects the scroll, but not\n" " the fact that the block cursor was cleared just before\n" @@ -2279,7 +2345,7 @@ void print_help(int mode) { " mode if the bpp is 24.\n" "\n" " video4linux: on Linux some attempt is made to handle\n" -" video devices (webcams or tv tuners) automatically.\n" +" video devices (webcams or TV tuners) automatically.\n" " The idea is the WxHxB will be extracted from the\n" " device itself. So if you do not supply \"@WxHxB...\n" " parameters x11vnc will try to determine them. It first\n" @@ -2326,7 +2392,7 @@ void print_help(int mode) { " 24, and 32 respectively). See http://www.linuxtv.org\n" " for more info (V4L api).\n" "\n" -" For tv/rf tuner cards one can set the tuning mode\n" +" For TV/rf tuner cards one can set the tuning mode\n" " via tun=XXX where XXX can be one of PAL, NTSC, SECAM,\n" " or AUTO.\n" "\n" diff --git a/x11vnc/options.c b/x11vnc/options.c index a22edec..f01f0c7 100644 --- a/x11vnc/options.c +++ b/x11vnc/options.c @@ -93,7 +93,7 @@ char *allowed_input_str = NULL; char *viewonly_passwd = NULL; /* view only passwd. */ char **passwd_list = NULL; /* for -passwdfile */ int begin_viewonly = -1; -int inetd = 0; /* spawned from inetd(1) */ +int inetd = 0; /* spawned from inetd(8) */ #ifndef FILEXFER #define FILEXFER 1 #endif diff --git a/x11vnc/pointer.c b/x11vnc/pointer.c index 5abd843..1ad10e9 100644 --- a/x11vnc/pointer.c +++ b/x11vnc/pointer.c @@ -941,6 +941,7 @@ if (0) fprintf(stderr, "initialize_pipeinput: %s -- %s\n", pipeinput_str, p); } set_child_info(); + /* pipeinput */ if (no_external_cmds) { rfbLogEnable(1); rfbLog("cannot run external commands in -nocmds mode:\n"); diff --git a/x11vnc/remote.c b/x11vnc/remote.c index cebd00f..0716a81 100644 --- a/x11vnc/remote.c +++ b/x11vnc/remote.c @@ -585,7 +585,7 @@ int remote_control_access_ok(void) { "XAUTHORITY\n", dpy_str); fprintf(stderr, " -- (ignore any Xlib: errors that" " follow) --\n"); - dpy2 = XOpenDisplay(dpy_str); + dpy2 = XOpenDisplay_wr(dpy_str); fflush(stderr); fprintf(stderr, " -- (done checking) --\n\n"); @@ -601,7 +601,7 @@ int remote_control_access_ok(void) { if (dpy2) { rfbLog("XAUTHORITY is not required on display.\n"); rfbLog(" %s\n", DisplayString(dpy)); - XCloseDisplay(dpy2); + XCloseDisplay_wr(dpy2); dpy2 = NULL; return 0; } diff --git a/x11vnc/screen.c b/x11vnc/screen.c index 231cf62..1a76036 100644 --- a/x11vnc/screen.c +++ b/x11vnc/screen.c @@ -541,7 +541,7 @@ void set_raw_fb_params(int restore) { multiple_cursors_mode = mc0; if (! dpy && raw_fb_orig_dpy) { - dpy = XOpenDisplay(raw_fb_orig_dpy); + dpy = XOpenDisplay_wr(raw_fb_orig_dpy); if (dpy) { if (! quiet) rfbLog("reopened DISPLAY: %s\n", raw_fb_orig_dpy); @@ -881,6 +881,7 @@ if (db) fprintf(stderr, "initialize_raw_fb reset\n"); set_child_info(); q += strlen("setup:"); + /* rawfb-setup */ if (no_external_cmds) { rfbLogEnable(1); rfbLog("cannot run external commands in -nocmds " @@ -988,7 +989,7 @@ if (db) fprintf(stderr, "initialize_raw_fb reset\n"); if (dpy) { rfbLog("closing X DISPLAY: %s in rawfb mode.\n", DisplayString(dpy)); - XCloseDisplay(dpy); /* yow! */ + XCloseDisplay_wr(dpy); /* yow! */ } dpy = NULL; } @@ -1974,7 +1975,7 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { have_masks = 0; } - if (cmap8to24 && depth == 8) { + if (cmap8to24 && depth == 8 && dpy) { XVisualInfo vinfo; /* more cooking up... */ have_masks = 2; @@ -2042,6 +2043,8 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { rfbLog("Raw fb at addr %p is %dbpp depth=%d " "true color\n", raw_fb_addr, fb_bpp, fb_depth); + } else if (! dpy) { + ; } else if (have_masks == 2) { rfbLog("\n"); rfbLog("X display %s is %dbpp depth=%d indexed " @@ -2206,6 +2209,7 @@ void initialize_screen(int *argc, char **argv, XImage *fb) { fprintf(stderr, " 8to24_fb: %p\n", cmap8to24_fb); fprintf(stderr, " snap_fb: %p\n", snap_fb); fprintf(stderr, " raw_fb: %p\n", raw_fb); + fprintf(stderr, " fake_fb: %p\n", fake_fb); fprintf(stderr, "\n"); } diff --git a/x11vnc/solid.c b/x11vnc/solid.c index a40d0fd..25d92e2 100644 --- a/x11vnc/solid.c +++ b/x11vnc/solid.c @@ -53,6 +53,7 @@ static int dt_cmd(char *cmd) { return 0; } + /* dt */ if (no_external_cmds) { rfbLog("cannot run external commands in -nocmds mode:\n"); rfbLog(" \"%s\"\n", cmd); diff --git a/x11vnc/sslcmds.c b/x11vnc/sslcmds.c index a7bc290..db31b5e 100644 --- a/x11vnc/sslcmds.c +++ b/x11vnc/sslcmds.c @@ -113,6 +113,7 @@ int start_stunnel(int stunnel_port, int x11vnc_port) { return 0; } + /* stunnel */ if (no_external_cmds) { rfbLogEnable(1); rfbLog("start_stunnel: cannot run external commands in -nocmds mode:\n"); diff --git a/x11vnc/sslhelper.c b/x11vnc/sslhelper.c index 95bca1a..1d31e77 100644 --- a/x11vnc/sslhelper.c +++ b/x11vnc/sslhelper.c @@ -246,6 +246,7 @@ static char *create_tmp_pem(char *pathin, int prompt) { CN = strdup(line); EM = strdup("x11vnc@server.nowhere"); + /* ssl */ if (no_external_cmds) { rfbLog("create_tmp_pem: cannot run external commands.\n"); return NULL; @@ -818,7 +819,7 @@ void openssl_port(void) { rfbLog("openssl_port: could not reopen port %d\n", port); clean_up_exit(1); } - if (db) fprintf(stderr, "listen on port/sock %d/%d\n", port, sock); + rfbLog("openssl_port: listen on port/sock %d/%d\n", port, sock); openssl_sock = sock; openssl_port_num = port; diff --git a/x11vnc/tkx11vnc b/x11vnc/tkx11vnc index bb2b5ae..4eaa665 100755 --- a/x11vnc/tkx11vnc +++ b/x11vnc/tkx11vnc @@ -316,6 +316,12 @@ Tuning =D-C:0,1,2,3,4 pointer_mode: input_skip: =D nodragging + -- D + speeds: + =D wait: + defer: + =D nap + screen_blank: -- =GAL WireFrame:: wireframe @@ -337,12 +343,6 @@ Tuning xd_area: xd_mem: =GAL LOFF - -- D - speeds: - =D wait: - defer: - =D nap - screen_blank: -- =GAL SharedMemory:: noshm diff --git a/x11vnc/tkx11vnc.h b/x11vnc/tkx11vnc.h index 46ed039..98749ac 100644 --- a/x11vnc/tkx11vnc.h +++ b/x11vnc/tkx11vnc.h @@ -327,6 +327,12 @@ char gui_code[] = ""; " =D-C:0,1,2,3,4 pointer_mode:\n" " input_skip:\n" " =D nodragging\n" +" -- D\n" +" speeds:\n" +" =D wait:\n" +" defer:\n" +" =D nap\n" +" screen_blank:\n" " --\n" " =GAL WireFrame::\n" " wireframe\n" @@ -348,12 +354,6 @@ char gui_code[] = ""; " xd_area:\n" " xd_mem:\n" " =GAL LOFF\n" -" -- D\n" -" speeds:\n" -" =D wait:\n" -" defer:\n" -" =D nap\n" -" screen_blank:\n" " --\n" " =GAL SharedMemory::\n" " noshm\n" diff --git a/x11vnc/unixpw.c b/x11vnc/unixpw.c index 4730219..4bca127 100644 --- a/x11vnc/unixpw.c +++ b/x11vnc/unixpw.c @@ -49,7 +49,7 @@ void unixpw_screen(int init); void unixpw_keystroke(rfbBool down, rfbKeySym keysym, int init); void unixpw_accept(char *user); void unixpw_deny(void); -int su_verify(char *user, char *pass); +int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size); int crypt_verify(char *user, char *pass); static int white(void); @@ -63,6 +63,10 @@ int unixpw_login_viewonly = 0; time_t unixpw_last_try_time = 0; rfbClientPtr unixpw_client = NULL; +int keep_unixpw = 0; +char *keep_unixpw_user = NULL; +char *keep_unixpw_pass = NULL; + static int in_login = 0, in_passwd = 0, tries = 0; static int char_row = 0, char_col = 0; static int char_x = 0, char_y = 0, char_w = 8, char_h = 16; @@ -352,11 +356,11 @@ int crypt_verify(char *user, char *pass) { #endif /* UNIXPW_CRYPT */ } -int su_verify(char *user, char *pass) { +int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size) { #ifndef UNIXPW_SU return 0; #else - int i, j, status, fd = -1, sfd, tfd; + int i, j, status, fd = -1, sfd, tfd, drain_size = 4096, rsize; int slow_pw = 1; char *slave, *bin_true = NULL, *bin_su = NULL; pid_t pid, pidw; @@ -389,6 +393,7 @@ int su_verify(char *user, char *pass) { return 0; } } + /* unixpw */ if (no_external_cmds) { rfbLog("su_verify: cannot run external commands.\n"); clean_up_exit(1); @@ -417,6 +422,10 @@ int su_verify(char *user, char *pass) { } if (stat("/usr/bin/true", &sbuf) == 0) { bin_true = "/usr/bin/true"; } + if (cmd != NULL && cmd[0] != '\0') { + /* this is for ext. cmd su -c "my cmd" */ + bin_true = cmd; + } if (bin_true == NULL) { rfbLogPerror("existence /bin/true"); return 0; @@ -617,13 +626,13 @@ if (db) fprintf(stderr, "slave is: %s fd=%d\n", slave, fd); if (db) fprintf(stderr, "%s", buf); if (db > 3 && n == 1 && buf[0] == ':') { - char cmd[32]; + char cmd0[32]; usleep( 100 * 1000 ); fprintf(stderr, "\n\n"); - sprintf(cmd, "ps wu %d", pid); - system(cmd); - sprintf(cmd, "stty -a < %s", slave); - system(cmd); + sprintf(cmd0, "ps wu %d", pid); + system(cmd0); + sprintf(cmd0, "stty -a < %s", slave); + system(cmd0); fprintf(stderr, "\n\n"); } @@ -675,7 +684,12 @@ if (db) { * if we don't drain we may block at waitpid. If we close(fd), the * make cause child to die by signal. */ - for (i = 0; i<4096; i++) { + if (rbuf && *rbuf_size > 0) { + /* asked to return output of command */ + drain_size = *rbuf_size; + rsize = 0; + } + for (i = 0; i< drain_size; i++) { int n; buf[0] = '\0'; @@ -691,6 +705,48 @@ if (db) fprintf(stderr, "%s", buf); if (n <= 0) { break; } + + if (rbuf) { + rbuf[i] = buf[0]; + rsize++; + } + } + if (rbuf) { + char *s = rbuf; + char *p = strdup(pass); + int n, o = 0; + + n = strlen(p); + if (p[n-1] == '\n') { + p[n-1] = '\0'; + } + /* + * usually is: Password: mypassword\r\n\r\n<output-of-command> + * and output will have \n -> \r\n + */ + if (rbuf[0] == ' ') { + s++; + o++; + } + if (strstr(s, p) == s) { + s += strlen(p); + o += strlen(p); + for (n = 0; n < 4; n++) { + if (s[0] == '\r' || s[0] == '\n') { + s++; + o++; + } + } + } + if (o > 0) { + int i = 0; + rsize -= o; + while (o < drain_size) { + rbuf[i++] = rbuf[o++]; + } + } + *rbuf_size = rsize; + strzero(p); } if (db) fprintf(stderr, "\n"); @@ -730,14 +786,39 @@ if (db) fprintf(stderr, "unixpw_verify: '%s' '%s'\n", user, db > 1 ? pass : "*** if (unixpw_nis) { if (crypt_verify(user, pass)) { unixpw_accept(user); + if (keep_unixpw) { + keep_unixpw_user = strdup(user); + keep_unixpw_pass = strdup(pass); + } return; } else { rfbLog("unixpw_verify: crypt_verify login for %s failed.\n", user); usleep(3000*1000); } + } else if (0) { + char buf[8192]; + int n = 8000; + int res = su_verify(user, pass, "/home/runge/wallycom yegg 33", buf, &n); + + fprintf(stderr, "su_verify ret: n=%d ", n); + write(2, buf, n); + + if (res) { + unixpw_accept(user); + if (keep_unixpw) { + keep_unixpw_user = strdup(user); + keep_unixpw_pass = strdup(pass); + } + return; + } + rfbLog("unixpw_verify: su_verify login for %s failed.\n", user); } else { - if (su_verify(user, pass)) { + if (su_verify(user, pass, NULL, NULL, NULL)) { unixpw_accept(user); + if (keep_unixpw) { + keep_unixpw_user = strdup(user); + keep_unixpw_pass = strdup(pass); + } return; } rfbLog("unixpw_verify: su_verify login for %s failed.\n", user); @@ -803,6 +884,14 @@ void unixpw_keystroke(rfbBool down, rfbKeySym keysym, int init) { user[i] = '\0'; pass[i] = '\0'; } + if (keep_unixpw_user) { + free(keep_unixpw_user); + keep_unixpw_user = NULL; + } + if (keep_unixpw_pass) { + free(keep_unixpw_pass); + keep_unixpw_pass = NULL; + } return; } @@ -1027,6 +1116,41 @@ static void apply_opts (char *user) { void unixpw_accept(char *user) { apply_opts(user); + if (started_as_root == 1 && users_list + && strstr(users_list, "unixpw=") == users_list) { + if (getuid() && geteuid()) { + rfbLog("unixpw_accept: unixpw= but not root\n"); + started_as_root = 2; + } else { + char *u = (char *)malloc(strlen(user)+1); + + u[0] = '\0'; + if (!strcmp(users_list, "unixpw=")) { + sprintf(u, "+%s", user); + } else { + char *p, *str = strdup(users_list); + p = strtok(str + strlen("unixpw="), ","); + while (p) { + if (!strcmp(p, user)) { + sprintf(u, "+%s", user); + break; + } + p = strtok(NULL, ","); + } + free(str); + } + + if (u[0] == '\0') { + rfbLog("unixpw_accept skipping switch to user: %s\n", user); + } else if (switch_user(u, 0)) { + rfbLog("unixpw_accept switched to user: %s\n", user); + } else { + rfbLog("unixpw_accept failed to switched to user: %s\n", user); + } + free(u); + } + } + if (unixpw_login_viewonly) { unixpw_client->viewOnly = TRUE; } diff --git a/x11vnc/unixpw.h b/x11vnc/unixpw.h index 976a4dd..25dd71d 100644 --- a/x11vnc/unixpw.h +++ b/x11vnc/unixpw.h @@ -7,12 +7,15 @@ extern void unixpw_screen(int init); extern void unixpw_keystroke(rfbBool down, rfbKeySym keysym, int init); extern void unixpw_accept(char *user); extern void unixpw_deny(void); -extern int su_verify(char *user, char *pass); +extern int su_verify(char *user, char *pass, char *cmd, char *rbuf, int *rbuf_size); extern int crypt_verify(char *user, char *pass); extern int unixpw_in_progress; extern int unixpw_login_viewonly; extern time_t unixpw_last_try_time; extern rfbClientPtr unixpw_client; +extern int keep_unixpw; +extern char *keep_unixpw_user; +extern char *keep_unixpw_pass; #endif /* _X11VNC_UNIXPW_H */ diff --git a/x11vnc/user.c b/x11vnc/user.c index 78eb6dd..90e791b 100644 --- a/x11vnc/user.c +++ b/x11vnc/user.c @@ -6,6 +6,8 @@ #include "scan.h" #include "screen.h" #include "unixpw.h" +#include "sslhelper.h" +#include "xwrappers.h" void check_switched_user(void); void lurk_loop(char *str); @@ -13,6 +15,7 @@ int switch_user(char *user, int fb_mode); int read_passwds(char *passfile); void install_passwds(void); void check_new_passwds(void); +int wait_for_client(int *argc, char** argv, int http); static void switch_user_task_dummy(void); @@ -574,9 +577,9 @@ static int try_user_and_display(uid_t uid, char *dpystr) { } fclose(stderr); - dpy2 = XOpenDisplay(dpystr); + dpy2 = XOpenDisplay_wr(dpystr); if (dpy2) { - XCloseDisplay(dpy2); + XCloseDisplay_wr(dpy2); exit(0); /* success */ } else { exit(2); /* fail */ @@ -940,4 +943,234 @@ void check_new_passwds(void) { } } +int wait_for_client(int *argc, char** argv, int http) { + static XImage ximage_struct; + XImage* fb_image; + int w = 640, h = 480, b = 32; + int w0, h0, i; + int chg_raw_fb = 0; + char *str, *q, *p; + char *cmd = NULL; + int db = 0; + + if (! use_dpy || strstr(use_dpy, "WAIT:") != use_dpy) { + return 0; + } + + rfbLog("into wait_for_client.\n"); + str = strdup(use_dpy); + str += strlen("WAIT:"); + q = strchr(str, ':'); + + /* get any leading geometry: */ + if (q) *q = '\0'; + if (sscanf(str, "%dx%d", &w0, &h0) == 2) { + w = w0; + h = h0; + } + if (q) *q = ':'; + + q = strchr(str, ':'); + if (! q) { + if (strstr(str, "cmd=") != str) { + str = strdup(":0"); + } + } else { + str = q; + } + if (db) fprintf(stderr, "str: %s\n", str); + + if (strstr(str, "cmd=") == str) { + cmd = str + strlen("cmd="); + if (db) fprintf(stderr, "cmd: %s\n", cmd); + + /* WAIT */ + if (no_external_cmds) { + rfbLog("wait_for_client external cmds not allowed:" + " %s\n", use_dpy); + clean_up_exit(1); + } + } + + if (fake_fb) { + free(fake_fb); + } + fake_fb = (char *) calloc(w*h*b/4, 1); + + fb_image = &ximage_struct; + fb_image->data = fake_fb; + fb_image->format = ZPixmap; + fb_image->width = w; + fb_image->height = h; + fb_image->bits_per_pixel = b; + fb_image->bytes_per_line = w*b/8; + fb_image->bitmap_unit = -1; + fb_image->depth = 24; + fb_image->red_mask = 0xff0000; + fb_image->green_mask = 0x00ff00; + fb_image->blue_mask = 0x0000ff; + + depth = fb_image->depth; + + dpy_x = wdpy_x = w; + dpy_y = wdpy_y = h; + off_x = 0; + off_y = 0; + + initialize_allowed_input(); + + initialize_screen(argc, argv, fb_image); + + if (http && check_httpdir()) { + http_connections(1); + } + + if (! raw_fb) { + chg_raw_fb = 1; + /* kludge to get RAWFB_RET with dpy == NULL guards */ + raw_fb = "null"; + } + + if (cmd && unixpw) { + keep_unixpw = 1; + } + + if (inetd && use_openssl) { + accept_openssl(OPENSSL_INETD); + } + + while (1) { + if (! use_threads) { + rfbPE(-1); + } + if (use_openssl) { + check_openssl(); + } + if (! screen || ! screen->clientHead) { + usleep(100 * 1000); + continue; + } + rfbLog("wait_for_client: got client\n"); + break; + } + + if (unixpw) { + if (! unixpw_in_progress) { + rfbLog("unixpw but no unixpw_in_progress\n"); + clean_up_exit(1); + } + while (1) { + if (! use_threads) { + rfbPE(-1); + } + if (unixpw_in_progress) { + usleep(20 * 1000); + continue; + } + rfbLog("wait_for_client: unixpw finished.\n"); + break; + } + } + + if (cmd) { + char line1[1024]; + char line2[16384]; + char *q; + int n; + + memset(line1, 0, 1024); + memset(line2, 0, 16384); + + if (unixpw) { + int res = 0, k, j; + char line[18000]; + + memset(line, 0, 18000); + + if (keep_unixpw_user && keep_unixpw_pass) { + n = 18000; + res = su_verify(keep_unixpw_user, keep_unixpw_pass, + cmd, line, &n); + strzero(keep_unixpw_user); + strzero(keep_unixpw_pass); + } + keep_unixpw = 0; + + if (! res) { + rfbLog("wait_for_client: cmd failed: %s\n", cmd); + clean_up_exit(1); + } + for (k = 0; k < 1024; k++) { + line1[k] = line[k]; + if (line[k] == '\n') { + k++; + break; + } + } + n -= k; + while (j < 16384) { + line2[j] = line[k+j]; + j++; + } + } else { + FILE *p = popen(cmd, "r"); + if (! p) { + rfbLog("wait_for_client: cmd failed: %s\n", cmd); + rfbLogPerror("popen"); + clean_up_exit(1); + } + if (fgets(line1, 1024, p) == NULL) { + rfbLog("wait_for_client: read failed: %s\n", cmd); + rfbLogPerror("fgets"); + clean_up_exit(1); + } + n = fread(line2, 1, 16384, p); + pclose(p); + } + + if (strstr(line1, "DISPLAY=") != line1) { + rfbLog("wait_for_client: bad reply %s\n", line1); + clean_up_exit(1); + } + + use_dpy = strdup(line1 + strlen("DISPLAY=")); + q = use_dpy; + while (*q != '\0') { + if (*q == '\n' || *q == '\r') *q = '\0'; + q++; + } +if (db) fprintf(stderr, "use_dpy: %s n: %d\n", use_dpy, n); +if (0) write(2, line2, n); + if (line2[0] != '\0') { + if (strstr(line2, "XAUTHORITY=") == line2) { + q = line2; + while (*q != '\0') { + if (*q == '\n' || *q == '\r') *q = '\0'; + q++; + } + if (auth_file) { + free(auth_file); + } + auth_file = strdup(line2 + strlen("XAUTHORITY=")); + + } else { + xauth_raw_data = (char *)malloc(n); + xauth_raw_len = n; + memcpy(xauth_raw_data, line2, n); +if (db) fprintf(stderr, "xauth_raw_len: %d\n", n); +if (0) { + write(2, xauth_raw_data, xauth_raw_len); + fprintf(stderr, "\n"); +} + } + } + } else { + use_dpy = strdup(str); + } + if (chg_raw_fb) { + raw_fb = NULL; + } + + return 1; +} diff --git a/x11vnc/user.h b/x11vnc/user.h index 1469c0f..9dcfe41 100644 --- a/x11vnc/user.h +++ b/x11vnc/user.h @@ -9,5 +9,6 @@ extern int switch_user(char *, int); extern int read_passwds(char *passfile); extern void install_passwds(void); extern void check_new_passwds(void); +extern int wait_for_client(int *argc, char** argv, int http); #endif /* _X11VNC_USER_H */ diff --git a/x11vnc/v4l.c b/x11vnc/v4l.c index 9722f38..7799354 100644 --- a/x11vnc/v4l.c +++ b/x11vnc/v4l.c @@ -1089,6 +1089,7 @@ static char *guess_via_v4l_info(char *dev, int *fd) { if (*fd) {} + /* v4l-info */ if (no_external_cmds) { rfbLog("guess_via_v4l_info: cannot run external " "command: v4l-info\n"); diff --git a/x11vnc/win_utils.c b/x11vnc/win_utils.c index 4ff3107..88c3987 100644 --- a/x11vnc/win_utils.c +++ b/x11vnc/win_utils.c @@ -304,6 +304,7 @@ int pick_windowid(unsigned long *num) { if (use_dpy) { set_env("DISPLAY", use_dpy); } + /* id */ if (no_external_cmds) { rfbLogEnable(1); rfbLog("cannot run external commands in -nocmds mode:\n"); diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index c8490bc..9dc9386 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "June 2006" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.8.1, lastmod: 2006-06-03 + version: 0.8.2, lastmod: 2006-06-08 .SH SYNOPSIS .B x11vnc [OPTION]... @@ -60,7 +60,8 @@ becomes a space character). X11 server display to connect to, usually :0. The X server process must be running on same machine and support MIT-SHM. Equivalent to setting the DISPLAY -environment variable to \fIdisp\fR. +environment variable to \fIdisp\fR. See the description +below of the "\fB-display\fR \fIWAIT:...\fR" extensions. .PP \fB-auth\fR \fIfile\fR .IP @@ -355,7 +356,7 @@ after startup. \fB-inetd\fR .IP Launched by -.IR inetd (1): +.IR inetd (8): stdio instead of listening socket. Note: if you are not redirecting stderr to a log file (via shell 2> or \fB-o\fR option) you MUST also specify the \fB-q\fR @@ -515,6 +516,755 @@ used to have viewonly passwords. (tip: make the 3rd and last line be "__BEGIN_VIEWONLY__" to have 2 full-access passwords) .PP +\fB-unixpw\fR \fI[list]\fR +.IP +Use Unix username and password authentication. x11vnc +uses the +.IR su (1) +program to verify the user's password. +[list] is an optional comma separated list of allowed +Unix usernames. See below for per-user options that +can be applied. +.IP +A familiar "login:" and "Password:" dialog is +presented to the user on a black screen inside the +vncviewer. The connection is dropped if the user fails +to supply the correct password in 3 tries or does not +send one before a 25 second timeout. Existing clients +are view-only during this period. +.IP +Since the detailed behavior of +.IR su (1) +can vary from +OS to OS and for local configurations, test the mode +carefully on your systems before using it in production. +Test different combinations of valid/invalid usernames +and valid/invalid passwords to see if it behaves as +expected. x11vnc will attempt to be conservative and +reject a login if anything abnormal occurs. +.IP +On FreeBSD and the other BSD's by default it is +impossible for the user running x11vnc to validate +his *own* password via +.IR su (1) +(evidently commenting out +the pam_self.so entry in /etc/pam.d/su eliminates this +problem). So the x11vnc login will always *fail* for +this case (even when the correct password is supplied). +.IP +A possible workaround for this would be to start +x11vnc as root with the "\fB-users\fR \fI+nobody\fR" option to +immediately switch to user nobody. Another source of +problems are PAM modules that prompt for extra info, +e.g. password aging modules. These logins will fail +as well even when the correct password is supplied. +.IP +**IMPORTANT**: to prevent the Unix password being sent +in *clear text* over the network, one of two schemes +will be enforced: 1) the \fB-ssl\fR builtin SSL mode, or 2) +require both \fB-localhost\fR and \fB-stunnel\fR be enabled. +.IP +Method 1) ensures the traffic is encrypted between +viewer and server. A PEM file will be required, see the +discussion under \fB-ssl\fR below (under some circumstances +a temporary one can be automatically generated). +.IP +Method 2) requires the viewer connection to appear +to come from the same machine x11vnc is running on +(e.g. from a ssh \fB-L\fR port redirection). And that the +\fB-stunnel\fR SSL mode be used for encryption over the +network.(see the description of \fB-stunnel\fR below). +.IP +Note: as a convenience, if you +.IR ssh (1) +in and start +x11vnc it will check if the environment variable +SSH_CONNECTION is set and appears reasonable. If it +does, then the \fB-ssl\fR or \fB-stunnel\fR requirement will be +dropped since it is assumed you are using ssh for the +encrypted tunnelling. \fB-localhost\fR is still enforced. +Use \fB-ssl\fR or \fB-stunnel\fR to force SSL usage even if +SSH_CONNECTION is set. +.IP +To override the above restrictions you can set +environment variables before starting x11vnc: +.IP +Set UNIXPW_DISABLE_SSL=1 to disable requiring either +\fB-ssl\fR or \fB-stunnel.\fR Evidently you will be using a +different method to encrypt the data between the +vncviewer and x11vnc: perhaps +.IR ssh (1) +or an IPSEC VPN. +.IP +Note that use of \fB-localhost\fR with +.IR ssh (1) +is roughly +the same as requiring a Unix user login (since a Unix +password or the user's public key authentication is +used by sshd on the machine where x11vnc runs and only +local connections from that machine are accepted) +.IP +Set UNIXPW_DISABLE_LOCALHOST=1 to disable the \fB-localhost\fR +requirement in Method 2). One should never do this +(i.e. allow the Unix passwords to be sniffed on the +network). +.IP +Regarding reverse connections (e.g. \fB-R\fR connect:host +and \fB-connect\fR host), when the \fB-localhost\fR constraint is +in effect then reverse connections can only be used +to connect to the same machine x11vnc is running on +(default port 5500). Please use a ssh or stunnel port +redirection to the viewer machine to tunnel the reverse +connection over an encrypted channel. Note that in \fB-ssl\fR +mode reverse connection are disabled (see below). +.IP +In \fB-inetd\fR mode the Method 1) will be enforced (not +Method 2). With \fB-ssl\fR in effect reverse connections +are disabled. If you override this via env. var, be +sure to also use encryption from the viewer to inetd. +Tip: you can also have your own stunnel spawn x11vnc +in \fB-inetd\fR mode (thereby bypassing inetd). See the FAQ +for details. +.IP +The user names in the comma separated [list] can have +per-user options after a ":", e.g. "fred:opts" +where "opts" is a "+" separated list of +"viewonly", "fullaccess", "input=XXXX", or +"deny", e.g. "karl,fred:viewonly,boss:input=M". +For "input=" it is the K,M,B,C described under \fB-input.\fR +.IP +If a user in the list is "*" that means those +options apply to all users. It also means all users +are allowed to log in after supplying a valid password. +Use "deny" to explicitly deny some users if you use +"*" to set a global option. +.IP +There are also some utilities for testing password +if [list] starts with the "%" character. See the +quick_pw() function in the source for details. +.PP +\fB-unixpw_nis\fR \fI[list]\fR +.IP +As \fB-unixpw\fR above, however do not use +.IR su (1) +but rather +use the traditional +.IR getpwnam (3) ++ +.IR crypt (3) +method to +verify passwords instead. This requires that the +encrypted passwords be readable. Passwords stored +in /etc/shadow will be inaccessible unless x11vnc +is run as root. +.IP +This is called "NIS" mode simply because in most +NIS setups the user encrypted passwords are accessible +(e.g. "ypcat passwd"). NIS is not required for this +mode to work (only that +.IR getpwnam (3) +return the encrypted +password is required), but it is unlikely it will work +for any other modern environment. All of the \fB-unixpw\fR +options and contraints apply. +.PP +\fB-display\fR \fIWAIT:...\fR +.IP +A special usage mode for the normal \fB-display\fR option. +Useful with \fB-unixpw,\fR but can be used independently +of it. If the display string begins with WAIT: then +x11vnc waits until a VNC client connects before opening +the X display (or \fB-rawfb\fR device). +.IP +This could be useful for delaying opening the display +for certain usage modes (say if x11vnc is started at +boot time and no X server is running or users logged +in yet). +.IP +If the string is, e.g. WAIT:0.0 or WAIT:1, i.e. "WAIT" +in front of a normal X display, then that indicated +display is used. A more interesting case is like this: +.IP +WAIT:cmd=/usr/local/bin/find_display +.IP +in which case the command after "cmd=" is run to +dynamically work out the DISPLAY and optionally the +XAUTHORITY data. The first line of the command output +must be of the form DISPLAY=<xdisplay>. Any remaining +output is taken as XAUTHORITY data. It can be either +of the form XAUTHORITY=<file> or raw xauthority data for +the display (e.g. "xauth extract - $DISPLAY" output). +.IP +In the case of \fB-unixpw,\fR then the above command is run +as the user who just authenticated via the login and +password prompt. +.IP +Thus the combination of \fB-display\fR WAIT:cmd=... and +\fB-unixpw\fR allows automatic pairing of an unix +authenticated VNC user with his desktop. This could +be very useful on SunRays and also any system where +multiple users share a given machine. The user does +not need to remember special ports or passwords set up +for his desktop and VNC. +.IP +A nice way to use WAIT:cmd=... is out of +.IR inetd (8) +(it automatically forks a new x11vnc for each user). +You can have the x11vnc inetd spawned process run as, +say, root or nobody. When run as root (for either +inetd or display manager), you can also supply the +option "\fB-users\fR \fIunixpw=\fR" to have the x11vnc process +switch to the user as well. Note: there will be a 2nd +SSL helper process that will not switch, but it is only +encoding and decoding the stream at that point. +.IP +As a special case, WAIT:cmd=FINDDISPLAY will run a +script that works on most Unixes to determine a user's +DISPLAY variable and xauthority data. this is TBD. +.IP +Finally, one can insert a geometry between colons, +e.g. WAIT:1280x1024:... to set the size of the display +the VNC client first attaches to since some VNC viewers +will not automatically adjust to a new framebuffer size. +.PP +\fB-ssl\fR \fI[pem]\fR +.IP +Use the openssl library (www.openssl.org) to provide a +built-in encrypted SSL tunnel between VNC viewers and +x11vnc. This requires libssl support to be compiled +into x11vnc at build time. If x11vnc is not built +with libssl support it will exit immediately when \fB-ssl\fR +is prescribed. +.IP +[pem] is optional, use "\fB-ssl\fR \fI/path/to/mycert.pem\fR" +to specify a PEM certificate file to use to identify +and provide a key for this server. See +.IR openssl (1) +for +more info about PEMs and the \fB-sslGenCert\fR option below. +.IP +The connecting VNC viewer SSL tunnel can optionally +authenticate this server if they have the public +key part of the certificate (or a common certificate +authority, CA, is a more sophisicated way to verify +this server's cert, see \fB-sslGenCA\fR below). This is +used to prevent man-in-the-middle attacks. Otherwise, +if the VNC viewer accepts this server's key without +verification, at least the traffic is protected +from passive sniffing on the network (but NOT from +man-in-the-middle attacks). +.IP +If [pem] is not supplied and the +.IR openssl (1) +utility +command exists in PATH, then a temporary, self-signed +certificate will be generated for this session (this +may take 5-30 seconds on slow machines). If +.IR openssl (1) +cannot be used to generate a temporary certificate +x11vnc exits immediately. +.IP +If successful in using +.IR openssl (1) +to generate a +temporary certificate, the public part of it will be +displayed to stderr (e.g. one could copy it to the +client-side to provide authentication of the server to +VNC viewers.) See following paragraphs for how to save +keys to reuse when x11vnc is restarted. +.IP +Set the env. var. X11VNC_SHOW_TMP_PEM=1 to have x11vnc +print out the entire certificate, including the PRIVATE +KEY part, to stderr. One could reuse this cert if saved +in a [pem] file. Similarly, set X11VNC_KEEP_TMP_PEM=1 +to not delete the temporary PEM file: the file name +will be printed to stderr (so one could move it to +a safe place for reuse). You will be prompted for a +passphrase for the private key. +.IP +If [pem] is "SAVE" then the certificate will be saved +to the file ~/.vnc/certs/server.pem, or if that file +exists it will be used directly. Similarly, if [pem] +is "SAVE_PROMPT" the server.pem certificate will be +made based on your answers to its prompts for info such +as OrganizationalName, CommonName, etc. +.IP +Use "SAVE-<string>" and "SAVE_PROMPT-<string>" +to refer to the file ~/.vnc/certs/server-<string>.pem +instead. E.g. "SAVE-charlie" will store to the file +~/.vnc/certs/server-charlie.pem +.IP +See \fB-ssldir\fR below to use a directory besides the +default ~/.vnc/certs +.IP +Example: x11vnc \fB-ssl\fR SAVE \fB-display\fR :0 ... +.IP +Reverse connections are disabled in \fB-ssl\fR mode because +there is no way to ensure that data channel will +be encrypted. Set X11VNC_SSL_ALLOW_REVERSE=1 to +override this. +.IP +Your VNC viewer will also need to be able to connect +via SSL. See the discussion below under \fB-stunnel\fR and +the FAQ (ssl_vncviewer script) for how this might be +achieved. E.g. on Unix it is easy to write a shell +script that starts up stunnel and then vncviewer. +Also in the x11vnc source a SSL enabled Java VNC Viewer +applet is provided in the classes/ssl directory. +.PP +\fB-ssldir\fR \fI[dir]\fR +.IP +Use [dir] as an alternate ssl certificate and key +management toplevel directory. The default is +~/.vnc/certs +.IP +This directory is used to store server and other +certificates and keys and also other materials. E.g. in +the simplest case, "\fB-ssl\fR \fISAVE\fR" will store the x11vnc +server cert in [dir]/server.pem +.IP +Use of alternate directories via \fB-ssldir\fR allows you to +manage multiple VNC Certificate Authority (CA) keys. +Another use is if ~/.vnc/cert is on an NFS share you +might want your certificates and keys to be on a local +filesystem to prevent network snooping (for example +\fB-ssldir\fR /var/lib/x11vnc-certs). +.IP +\fB-ssldir\fR affects nearly all of the other \fB-ssl*\fR options, +e.g. \fB-ssl\fR SAVE, \fB-sslGenCert,\fR etc.. +.PP +\fB-sslverify\fR \fI[path]\fR +.IP +For either of the \fB-ssl\fR or \fB-stunnel\fR modes, use [path] +to provide certificates to authenticate incoming VNC +*Client* connections (normally only the server is +authenticated in SSL.) This can be used as a method +to replace standard password authentication of clients. +.IP +If [path] is a directory it contains the client (or CA) +certificates in separate files. If [path] is a file, +it contains multiple certificates. See special tokens +below. These correspond to the "CApath = dir" and +"CAfile = file" stunnel options. See the +.IR stunnel (8) +manpage for details. +.IP +Examples: +x11vnc \fB-ssl\fR \fB-sslverify\fR ~/my.pem +x11vnc \fB-ssl\fR \fB-sslverify\fR ~/my_pem_dir/ +.IP +Note that if [path] is a directory, it must contain +the certs in separate files named like <HASH>.0, where +the value of <HASH> is found by running the command +"openssl x509 \fB-hash\fR \fB-noout\fR \fB-in\fR file.crt". Evidently +one uses <HASH>.1 if there is a collision... +.IP +The the key-management utility "\fB-sslCertInfo\fR \fIHASHON\fR" +and "\fB-sslCertInfo\fR \fIHASHOFF\fR" will create/delete these +hashes for you automatically (via symlink) in the HASH +subdirs it manages. Then you can point \fB-sslverify\fR to +the HASH subdir. +.IP +Special tokens: in \fB-ssl\fR mode, if [path] is not a file or +a directory, it is taken as a comma separated list of +tokens that are interpreted as follows: +.IP +If a token is "CA" that means load the CA/cacert.pem +file from the ssl directory. If a token is "clients" +then all the files clients/*.crt in the ssl directory +are loaded. Otherwise the file clients/token.crt +is attempted to be loaded. As a kludge, use a token +like ../server-foo to load a server cert if you find +that necessary. +.IP +Use \fB-ssldir\fR to use a directory different from the +~/.vnc/certs default. +.IP +Note that if the "CA" cert is loaded you do not need +to load any of the certs that have been signed by it. +You will need to load any additional self-signed certs +however. +.IP +Examples: +x11vnc \fB-ssl\fR \fB-sslverify\fR CA +x11vnc \fB-ssl\fR \fB-sslverify\fR self:fred,self:jim +x11vnc \fB-ssl\fR \fB-sslverify\fR CA,clients +.IP +Usually "\fB-sslverify\fR \fICA\fR" is the most effective. +See the \fB-sslGenCA\fR and \fB-sslGenCert\fR options below for +how to set up and manage the CA framework. +.IP +NOTE: the following utilities, \fB-sslGenCA,\fR \fB-sslGenCert,\fR +\fB-sslEncKey,\fR and \fB-sslCertInfo\fR are provided for +completeness, but for casual usage they are overkill. +.IP +They provide VNC Certificate Authority (CA) key creation +and server / client key generation and signing. So they +provide a basic Public Key management framework for +VNC-ing with x11vnc. (note that they require +.IR openssl (1) +be installed on the system) +.IP +However, the simplest usage mode (where x11vnc +automatically generates its own, self-signed, temporary +key and the VNC viewers always accept it, e.g. accepting +via a dialog box) is probably safe enough for most +scenarios. CA management is not needed. +.IP +To protect against Man-In-The-Middle attacks the +simplest mode can be improved by using "\fB-ssl\fR \fISAVE\fR" +to have x11vnc create a longer term self-signed +certificate, and then (safely) copy the corresponding +public key cert to the desired client machines (care +must be taken the private key part is not stolen; +you will be prompted for a passphrase). +.IP +So keep in mind no CA key creation or management +(-sslGenCA and \fB-sslGenCert)\fR is needed for either of +the above two common usage modes. +.IP +One might want to use \fB-sslGenCA\fR and \fB-sslGenCert\fR +if you had a large number of VNC client and server +workstations. That way the administrator could generate +a single CA key with \fB-sslGenCA\fR and distribute its +certificate part to all of the workstations. +.IP +Next, he could create signed VNC server keys +(-sslGenCert server ...) for each workstation or user +that then x11vnc would use to authenticate itself to +any VNC client that has the CA cert. +.IP +Optionally, the admin could also make it so the +VNC clients themselves are authenticated to x11vnc +(-sslGenCert client ...) For this \fB-sslverify\fR would be +pointed to the CA cert (and/or self-signed certs). +.IP +x11vnc will be able to use all of these cert and +key files. On the VNC client side, they will need to +be "imported" somehow. Web browsers have "Manage +Certificates" actions as does the Java applet plugin +Control Panel. stunnel can also use these files (see +the ssl_vncviewer example script in the FAQ.) +.PP +\fB-sslGenCA\fR \fI[dir]\fR +.IP +Generate your own Certificate Authority private key, +certificate, and other files in directory [dir]. +.IP +If [dir] is not supplied, a \fB-ssldir\fR setting is used, +or otherwise ~/.vnc/certs is used. +.IP +This command also creates directories where server and +client certs and keys will be stored. The +.IR openssl (1) +program must be installed on the system and available +in PATH. +.IP +After the CA files and directories are created the +command exits; the VNC server is not run. +.IP +You will be prompted for information to put into the CA +certificate. The info does not have to be accurate just +as long as clients accept the cert for VNC connections. +You will also need to supply a passphrase of at least +4 characters for the CA private key. +.IP +Once you have generated the CA you can distribute +its certificate part, [dir]/CA/cacert.pem, to other +workstations where VNC viewers will be run. One will +need to "import" this certicate in the applications, +e.g. Web browser, Java applet plugin, stunnel, etc. +Next, you can create and sign keys using the CA with +the \fB-sslGenCert\fR option below. +.IP +Examples: +x11vnc \fB-sslGenCA\fR +x11vnc \fB-sslGenCA\fR ~/myCAdir +x11vnc \fB-ssldir\fR ~/myCAdir \fB-sslGenCA\fR +.IP +(the last two lines are equivalent) +.PP +\fB-sslGenCert\fR \fItype\fR \fIname\fR +.IP +Generate a VNC server or client certificate and private +key pair signed by the CA created previously with +\fB-sslGenCA.\fR The +.IR openssl (1) +program must be installed +on the system and available in PATH. +.IP +After the Certificate is generated the command exits; +the VNC server is not run. +.IP +The type of key to be generated is the string \fItype\fR. +It is either "server" (i.e. for use by x11vnc) or +"client" (for a VNC viewer). Note that typically +only "server" is used: the VNC clients authenticate +themselves by a non-public-key method (e.g. VNC or +unix password). \fItype\fR is required. +.IP +An arbitrary default name you want to associate with +the key is supplied by the \fIname\fR string. You can +change it at the various prompts when creating the key. +\fIname\fR is optional. +.IP +If name is left blank for clients keys then "nobody" +is used. If left blank for server keys, then the +primary server key: "server.pem" is created (this +is the saved one referenced by "\fB-ssl\fR \fISAVE\fR" when the +server is started) +.IP +If \fIname\fR begins with the string "self:" then +a self-signed certificate is created instead of one +signed by your CA key. +.IP +If \fIname\fR begins with the string "req:" then only a +key (.key) and a certificate signing *request* (.req) +are generated. You can then send the .req file to +an external CA (even a professional one, e.g. Thawte) +and then combine the .key and the received cert into +the .pem file with the same basename. +.IP +The distinction between "server" and "client" is +simply the choice of output filenames and sub-directory. +This makes it so the \fB-ssl\fR SAVE-name option can easily +pick up the x11vnc PEM file this option generates. +And similarly makes it easy for the \fB-sslverify\fR option +to pick up your client certs. +.IP +There is nothing special about the filename or directory +location of either the "server" and "client" certs. +You can rename the files or move them to wherever +you like. +.IP +Precede this option with \fB-ssldir\fR [dir] to use a +directory other than the default ~/.vnc/certs You will +need to run \fB-sslGenCA\fR on that directory first before +doing any \fB-sslGenCert\fR key creation. +.IP +Note you cannot recreate a cert with exactly the same +distiguished name (DN) as an existing one. To do so, +you will need to edit the [dir]/CA/index.txt file to +delete the line. +.IP +Similar to \fB-sslGenCA,\fR you will be prompted to fill +in some information that will be recorded in the +certificate when it is created. Tip: if you know +the fully-quailified hostname other people will be +connecting to you can use that as the CommonName "CN" +to avoid some applications (e.g. web browsers and java +plugin) complaining it does not match the hostname. +.IP +You will also need to supply the CA private key +passphrase to unlock the private key created from +\fB-sslGenCA.\fR This private key is used to sign the server +or client certicate. +.IP +The "server" certs can be used by x11vnc directly by +pointing to them via the \fB-ssl\fR [pem] option. The default +file will be ~/.vnc/certs/server.pem. This one would +be used by simply typing \fB-ssl\fR SAVE. The pem file +contains both the certificate and the private key. +server.crt file contains the cert only. +.IP +The "client" cert + private key file will need +to be copied and imported into the VNC viewer +side applications (Web browser, Java plugin, +stunnel, etc.) Once that is done you can delete the +"client" private key file on this machine since +it is only needed on the VNC viewer side. The, +e.g. ~/.vnc/certs/clients/<name>.pem contains both +the cert and private key. The <name>.crt contains the +certificate only. +.IP +NOTE: It is very important to know one should always +generate new keys with a passphrase. Otherwise if an +untrusted user steals the key file he could use it to +masquerade as the x11vnc server (or VNC viewer client). +You will be prompted whether to encrypt the key with +a passphrase or not. It is recommended that you do. +One inconvenience to a passphrase is that it must +be suppled every time x11vnc or the client app is +started up. +.IP +Examples: +.IP +x11vnc \fB-sslGenCert\fR server +x11vnc \fB-ssl\fR SAVE \fB-display\fR :0 ... +.IP +and then on viewer using ssl_vncviewer stunnel wrapper +(see the FAQ): +ssl_vncviewer \fB-verify\fR ./cacert.crt hostname:0 +.IP +(this assumes the cacert.crt cert from \fB-sslGenCA\fR +was safely copied to the VNC viewer machine where +ssl_vncviewer is run) +.IP +Example using a name: +.IP +x11vnc \fB-sslGenCert\fR server charlie +x11vnc \fB-ssl\fR SAVE-charlie \fB-display\fR :0 ... +.IP +Example for a client certificate (rarely used): +.IP +x11vnc \fB-sslGenCert\fR client roger +scp ~/.vnc/certs/clients/roger.pem somehost:. +rm ~/.vnc/certs/clients/roger.pem +.IP +x11vnc is then started with the the option \fB-sslverify\fR +~/.vnc/certs/clients/roger.crt (or simply \fB-sslverify\fR +roger), and on the viewer user on somehost could do +for example: +.IP +ssl_vncviewer \fB-mycert\fR ./roger.pem hostname:0 +.PP +\fB-sslEncKey\fR \fI[pem]\fR +.IP +Utility to encrypt an existing PEM file with a +passphrase you supply when prompted. For that key to be +used (e.g. by x11vnc) the passphrase must be supplied +each time. +.IP +The "SAVE" notation described under \fB-ssl\fR applies as +well. (precede this option with \fB-ssldir\fR [dir] to refer +a directory besides the default ~/.vnc/certs) +.IP +The +.IR openssl (1) +program must be installed on the system +and available in PATH. After the Key file is encrypted +the command exits; the VNC server is not run. +.IP +Examples: +x11vnc \fB-sslEncKey\fR /path/to/foo.pem +x11vnc \fB-sslEncKey\fR SAVE +x11vnc \fB-sslEncKey\fR SAVE-charlie +.PP +\fB-sslCertInfo\fR \fI[pem]\fR +.IP +Prints out information about an existing PEM file. +In addition the public certificate is also printed. +The +.IR openssl (1) +program must be in PATH. Basically the +command "openssl x509 \fB-text"\fR is run on the pem. +.IP +The "SAVE" notation described under \fB-ssl\fR applies +as well. +.IP +Using "LIST" will give a list of all certs being +managed (in the ~/.vnc/certs dir, use \fB-ssldir\fR to refer +to another dir). "ALL" will print out the info for +every managed key (this can be very long). Giving a +client or server cert shortname will also try a lookup +(e.g. \fB-sslCertInfo\fR charlie). Use "LISTL" or "LL" +for a long (ls \fB-l\fR style) listing. +.IP +Using "HASHON" will create subdirs [dir]/HASH and +[dir]/HASH with OpenSSL hash filenames (e.g. 0d5fbbf1.0) +symlinks pointing up to the corresponding *.crt file. +([dir] is ~/.vnc/certs or one given by \fB-ssldir.)\fR +This is a useful way for other OpenSSL applications +(e.g. stunnel) to access all of the certs without +having to concatenate them. x11vnc will not use them +unless you specifically reference them. "HASHOFF" +removes these HASH subdirs. +.IP +The LIST, LISTL, LL, ALL, HASHON, HASHOFF words can +also be lowercase, e.g. "list". +.PP +\fB-sslDelCert\fR \fI[pem]\fR +.IP +Prompts you to delete all .crt .pem .key .req files +associated with [pem]. "SAVE" and lookups as in +\fB-sslCertInfo\fR apply as well. +.PP +\fB-stunnel\fR \fI[pem]\fR +.IP +Use the +.IR stunnel (8) +(www.stunnel.org) to provide an +encrypted SSL tunnel between viewers and x11vnc. +.IP +This external tunnel method was implemented prior to the +integrated \fB-ssl\fR encryption described above. It still +works well. This requires stunnel to be installed +on the system and available via PATH (n.b. stunnel is +often installed in sbin directories). Version 4.x of +stunnel is assumed (but see \fB-stunnel3\fR below.) +.IP +[pem] is optional, use "\fB-stunnel\fR \fI/path/to/stunnel.pem\fR" +to specify a PEM certificate file to pass to stunnel. +Whether one is needed or not depends on your stunnel +configuration. stunnel often generates one at install +time. See the stunnel documentation for details. +.IP +stunnel is started up as a child process of x11vnc and +any SSL connections stunnel receives are decrypted and +sent to x11vnc over a local socket. The strings +"The SSL VNC desktop is ..." and "SSLPORT=..." +are printed out at startup to indicate this. +.IP +The \fB-localhost\fR option is enforced by default +to avoid people routing around the SSL channel. +Set STUNNEL_DISABLE_LOCALHOST=1 before starting x11vnc +to disable the requirement. +.IP +Your VNC viewer will also need to be able to connect via +SSL. Unfortunately not too many do this. UltraVNC has +an encryption plugin but it does not seem to be SSL. +.IP +Also, in the x11vnc distribution, a patched TightVNC +Java applet is provided in classes/ssl that does SSL +connections (only). +.IP +It is also not too difficult to set up an stunnel or +other SSL tunnel on the viewer side. A simple example +on Unix using stunnel 3.x is: +.IP +% stunnel \fB-c\fR \fB-d\fR localhost:5901 \fB-r\fR remotehost:5900 +% vncviewer localhost:1 +.IP +For Windows, stunnel has been ported to it and there +are probably other such tools available. See the FAQ +for more examples. +.PP +\fB-stunnel3\fR \fI[pem]\fR +.IP +Use version 3.x stunnel command line syntax instead of +version 4.x +.PP +\fB-https\fR \fI[port]\fR +.IP +Choose a separate HTTPS port (-ssl mode only). +.IP +In \fB-ssl\fR mode, it turns out you can use the +single VNC port (e.g. 5900) for both VNC and HTTPS +connections. (HTTPS is used to retrieve a SSL-aware +VncViewer.jar applet that is provided with x11vnc). +Since both use SSL the implementation was extended to +detect if HTTP traffic (i.e. GET) is taking place and +handle it accordingly. The URL would be, e.g.: +.IP +https://mymachine.org:5900/ +.IP +This is convenient for firewalls, etc, because only one +port needs to be allowed in. However, this heuristic +adds a few seconds delay to each connection and can be +unreliable (especially if the user takes much time to +ponder the Certificate dialogs in his browser, Java VM, +or VNC Viewer applet. That's right 3 separate "Are +you sure you want to connect" dialogs!) +.IP +So use the \fB-https\fR option to provide a separate, more +reliable HTTPS port that x11vnc will listen on. If +[port] is not provided (or is 0), one is autoselected. +The URL to use is printed out at startup. +.IP +The SSL Java applet directory is specified via the +\fB-httpdir\fR option. If not supplied it will try to guess +the directory as though the \fB-http\fR option was supplied. +.PP \fB-usepw\fR .IP If no other password method was supplied on the command @@ -524,6 +1274,9 @@ use it with \fB-passwdfile;\fR otherwise, prompt the user for a password to create ~/.vnc/passwd and use it with the \fB-rfbauth\fR option. If none of these succeed x11vnc exits immediately. +.IP +Note: \fB-unixpw\fR currently does not count as a password +method by this option. .PP \fB-storepasswd\fR \fIpass\fR \fIfile\fR .IP @@ -556,7 +1309,7 @@ otherwise the client is rejected. See below for an extension to accept a client view-only. .IP If x11vnc is running as root (say from -.IR inetd (1) +.IR inetd (8) or from display managers .IR xdm (1) @@ -642,7 +1395,7 @@ interpreted by x11vnc. Example: \fB-gone\fR 'xlock &' \fB-users\fR \fIlist\fR .IP If x11vnc is started as root (say from -.IR inetd (1) +.IR inetd (8) or from display managers .IR xdm (1) @@ -660,38 +1413,47 @@ perform its primary functions. The option was added to make some of the *external* utility commands x11vnc occasionally runs work properly. In particular under GNOME and KDE to implement the "\fB-solid\fR \fIcolor\fR" feature -external commands (gconftool-2 and dcop) must be run -as the user owning the desktop session. Since this -option switches userid it also affects the userid used -to run the processes for the \fB-accept\fR and \fB-gone\fR options. -It also affects the ability to read files for options -such as \fB-connect,\fR \fB-allow,\fR and \fB-remap.\fR Note that the -\fB-connect\fR file is also sometimes written to. -.IP -So be careful with this option since in many situations +external commands (gconftool-2 and dcop) unfortunately +must be run as the user owning the desktop session. +Since this option switches userid it also affects the +userid used to run the processes for the \fB-accept\fR and +\fB-gone\fR options. It also affects the ability to read +files for options such as \fB-connect,\fR \fB-allow,\fR and \fB-remap.\fR +Note that the \fB-connect\fR file is also sometimes written +to. +.IP +So be careful with this option since in some situations its use can decrease security. .IP -The switch to a user will only take place if the -display can still be successfully opened as that user -(this is primarily to try to guess the actual owner +In general the switch to a user will only take place +if the display can still be successfully opened as that +user (this is primarily to try to guess the actual owner of the session). Example: "\fB-users\fR \fIfred,wilma,betty\fR". Note that a malicious user "barney" by quickly using -"xhost +" when logging in may get x11vnc to switch -to user "fred". What happens next? +"xhost +" when logging in may possibly get the x11vnc +process to switch to user "fred". What happens next? .IP Under display managers it may be a long time before -the switch succeeds (i.e. a user logs in). To make -it switch immediately regardless if the display +the switch succeeds (i.e. a user logs in). To instead +make it switch immediately regardless if the display can be reopened prefix the username with the "+" character. E.g. "\fB-users\fR \fI+bob\fR" or "\fB-users\fR \fI+nobody\fR". +.IP The latter (i.e. switching immediately to user "nobody") is probably the only use of this option that increases security. .IP +In \fB-unixpw\fR mode, if "\fB-users\fR \fIunixpw=\fR" is supplied +then after a user authenticates himself via the +\fB-unixpw\fR mechanism, x11vnc will try to switch to that +user as though "\fB-users\fR \fI+username\fR" had been supplied. +If you want to limit which users this will be done for, +provide them as a comma separated list after "unixpw=" +.IP To immediately switch to a user *before* connections to the X display are made or any files opened use the "=" character: "\fB-users\fR \fI=bob\fR". That user needs to -be able to open the X display of course. +be able to open the X display and any files of course. .IP The special user "guess=" means to examine the utmpx database (see @@ -701,18 +1463,18 @@ the display number (from DISPLAY or \fB-display\fR option) and try him/her. To limit the list of guesses, use: "\fB-users\fR \fIguess=bob,betty\fR". .IP -Even more sinister is the special user "lurk=" that -means to try to guess the DISPLAY from the utmpx login -database as well. So it "lurks" waiting for anyone -to log into an X session and then connects to it. -Specify a list of users after the = to limit which -users will be tried. To enable a different searching -mode, if the first user in the list is something like -":0" or ":0-2" that indicates a range of DISPLAY -numbers that will be tried (regardless of whether -they are in the utmpx database) for all users that -are logged in. Examples: "\fB-users\fR \fIlurk=\fR" and also -"\fB-users\fR \fIlurk=:0-1,bob,mary\fR" +Even more sinister is the special user "lurk=" +that means to try to guess the DISPLAY from the utmpx +login database as well. So it "lurks" waiting for +anyone to log into an X session and then connects to it. +Specify a list of users after the = to limit which users +will be tried. To enable a different searching mode, if +the first user in the list is something like ":0" or +":0-2" that indicates a range of DISPLAY numbers that +will be tried (regardless of whether they are in the +utmpx database) for all users that are logged in. Also +see the "\fB-display\fR \fIWAIT:...\fR" functionality. Examples: +"\fB-users\fR \fIlurk=\fR" and also "\fB-users\fR \fIlurk=:0-1,bob,mary\fR" .IP Be especially careful using the "guess=" and "lurk=" modes. They are not recommended for use on machines @@ -752,7 +1514,7 @@ commands are run for GNOME and KDE respectively. Other desktops won't work, e.g. Xfce (send us the corresponding commands if you find them). If x11vnc is running as root ( -.IR inetd (1) +.IR inetd (8) or .IR gdm (1) ), the \fB-users\fR option @@ -2025,7 +2787,7 @@ for a video camera that delivers the pixel data as mode if the bpp is 24. .IP video4linux: on Linux some attempt is made to handle -video devices (webcams or tv tuners) automatically. +video devices (webcams or TV tuners) automatically. The idea is the WxHxB will be extracted from the device itself. So if you do not supply "@WxHxB... parameters x11vnc will try to determine them. It first @@ -2074,7 +2836,7 @@ RGB555, RGB565, RGB24, and RGB32 (with bpp 8, 8, 16, 16, 24, and 32 respectively). See http://www.linuxtv.org for more info (V4L api). .IP -For tv/rf tuner cards one can set the tuning mode +For TV/rf tuner cards one can set the tuning mode via tun=XXX where XXX can be one of PAL, NTSC, SECAM, or AUTO. .IP @@ -2897,7 +3659,8 @@ http_url auth xauth users rootshift clipshift scale_str scaled_x scaled_y scale_numer scale_denom scale_fac scaling_blend scaling_nomult4 scaling_pad scaling_interpolate inetd privremote unsafe safer nocmds -passwdfile usepw using_shm +passwdfile unixpw unixpw_nis unixpw_list ssl ssl_pem +sslverify stunnel stunnel_pem https usepw using_shm logfile o flag rc norc h help V version lastmod bg sigpipe threads readrate netrate netlatency pipeinput clients client_count pid ext_xtest ext_xtrap ext_xrecord diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index e4069a2..88bd697 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -960,7 +960,7 @@ static void quick_pw(char *str) { } fprintf(stdout, "password: "); - /* no_external_cmds does not apply */ + /* test mode: no_external_cmds does not apply */ system("stty -echo"); if(fgets(tmp, 128, stdin) == NULL) { fprintf(stdout, "\n"); @@ -1003,7 +1003,7 @@ static void quick_pw(char *str) { exit(1); } } else { - if (su_verify(p, q+1)) { + if (su_verify(p, q+1, NULL, NULL, NULL)) { fprintf(stdout, "Y %s\n", p); exit(0); } else { @@ -1254,7 +1254,7 @@ static void check_loop_mode(int argc, char* argv[]) { perror("fork"); exit(1); } else { - /* no_external_cmds does not apply */ + /* loop mode: no_external_cmds does not apply */ execvp(argv[0], argv2); exit(1); } @@ -1283,6 +1283,7 @@ static void store_homedir_passwd(char *file) { str1[0] = '\0'; str2[0] = '\0'; + /* storepasswd */ if (no_external_cmds) { fprintf(stderr, "-nocmds cannot be used with -storepasswd\n"); exit(1); @@ -1388,6 +1389,7 @@ int main(int argc, char* argv[]) { int dt = 0, bg = 0; int got_rfbwait = 0; int got_httpdir = 0, try_http = 0; + int waited_for_client = 0; XImage *fb0 = NULL; /* used to pass args we do not know about to rfbGetScreen(): */ @@ -2728,20 +2730,33 @@ int main(int argc, char* argv[]) { use_xkb_modtweak = 0; #endif +#ifdef LIBVNCSERVER_WITH_TIGHTVNC_FILETRANSFER + if (filexfer) { + rfbRegisterTightVNCFileTransferExtension(); + } else { + rfbUnregisterTightVNCFileTransferExtension(); + } +#endif + + initialize_allowed_input(); + if (users_list && strstr(users_list, "lurk=")) { if (use_dpy) { rfbLog("warning: -display does not make sense in " "\"lurk=\" mode...\n"); } lurk_loop(users_list); + } else if (use_dpy && strstr(use_dpy, "WAIT:") == use_dpy) { + waited_for_client = wait_for_client(&argc_vnc, argv_vnc, + try_http && ! got_httpdir); } if (use_dpy) { - dpy = XOpenDisplay(use_dpy); + dpy = XOpenDisplay_wr(use_dpy); } else if ( (use_dpy = getenv("DISPLAY")) ) { - dpy = XOpenDisplay(use_dpy); + dpy = XOpenDisplay_wr(use_dpy); } else { - dpy = XOpenDisplay(""); + dpy = XOpenDisplay_wr(""); } if (! dpy && raw_fb_str) { @@ -2764,7 +2779,7 @@ int main(int argc, char* argv[]) { } fprintf(stderr, "\n"); use_dpy = ":0"; - dpy = XOpenDisplay(use_dpy); + dpy = XOpenDisplay_wr(use_dpy); if (dpy) { rfbLog("*** XOpenDisplay of \":0\" successful.\n"); } @@ -2803,7 +2818,7 @@ int main(int argc, char* argv[]) { fflush(stderr); fflush(stdout); usleep(30 * 1000); /* still needed? */ - XCloseDisplay(dpy); + XCloseDisplay_wr(dpy); exit(rc); } @@ -3133,13 +3148,6 @@ int main(int argc, char* argv[]) { raw_fb_pass_go_and_collect_200_dollars: -#ifdef LIBVNCSERVER_WITH_TIGHTVNC_FILETRANSFER - if (filexfer) { - rfbRegisterTightVNCFileTransferExtension(); - } else { - rfbUnregisterTightVNCFileTransferExtension(); - } -#endif if (! dt) { static char str[] = "-desktop"; argv_vnc[argc_vnc++] = str; @@ -3162,8 +3170,15 @@ int main(int argc, char* argv[]) { initialize_screen(&argc_vnc, argv_vnc, fb0); - if (try_http && ! got_httpdir && check_httpdir()) { - http_connections(1); + if (waited_for_client && fake_fb) { + free(fake_fb); + fake_fb = NULL; + } + + if (! waited_for_client) { + if (try_http && ! got_httpdir && check_httpdir()) { + http_connections(1); + } } initialize_tiles(); @@ -3180,10 +3195,10 @@ int main(int argc, char* argv[]) { initialize_keyboard_and_pointer(); - initialize_allowed_input(); - if (inetd && use_openssl) { - accept_openssl(OPENSSL_INETD); + if (! waited_for_client) { + accept_openssl(OPENSSL_INETD); + } } if (! inetd && ! use_openssl) { if (! screen->port || screen->listenSock < 0) { diff --git a/x11vnc/x11vnc.h b/x11vnc/x11vnc.h index c5ff32a..eb5f916 100644 --- a/x11vnc/x11vnc.h +++ b/x11vnc/x11vnc.h @@ -114,7 +114,7 @@ #define PASSWD_UNLESS_NOPW 0 #endif -#define REL81 +#define noREL81 /* * Beginning of support for small binary footprint build for embedded @@ -320,6 +320,8 @@ extern char lastmod[]; extern Display *dpy; /* the single display screen we connect to */ extern int scr; +extern char *xauth_raw_data; +extern int xauth_raw_len; extern Window window, rootwin; /* polled window, root window (usu. same) */ extern Visual *default_visual; /* the default visual (unless -visual) */ extern int bpp, depth; diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c index cfbbfb8..c316955 100644 --- a/x11vnc/x11vnc_defs.c +++ b/x11vnc/x11vnc_defs.c @@ -15,12 +15,14 @@ int xtrap_base_event_type = 0; int xdamage_base_event_type = 0; /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.8.1 lastmod: 2006-06-03"; +char lastmod[] = "0.8.2 lastmod: 2006-06-08"; /* X display info */ Display *dpy = NULL; /* the single display screen we connect to */ int scr = 0; +char *xauth_raw_data = NULL; +int xauth_raw_len = 0; Window window = None, rootwin = None; /* polled window, root window (usu. same) */ Visual *default_visual = NULL; /* the default visual (unless -visual) */ int bpp = 0, depth = 0; diff --git a/x11vnc/xevents.c b/x11vnc/xevents.c index 25d9cd4..ab49f0b 100644 --- a/x11vnc/xevents.c +++ b/x11vnc/xevents.c @@ -454,7 +454,7 @@ static void grab_buster_watch(int parent, char *dstr) { } /* overwrite original dpy, we let orig connection sit unused. */ - dpy = XOpenDisplay(dstr); + dpy = XOpenDisplay_wr(dstr); if (!dpy) { fprintf(stderr, "grab_buster_watch: could not reopen: %s\n", dstr); @@ -518,7 +518,7 @@ void spawn_grab_buster(void) { RAWFB_RET_VOID - XCloseDisplay(dpy); + XCloseDisplay_wr(dpy); dpy = NULL; if ((pid = fork()) > 0) { @@ -539,7 +539,7 @@ void spawn_grab_buster(void) { exit(0); } - dpy = XOpenDisplay(dstr); + dpy = XOpenDisplay_wr(dstr); if (!dpy) { rfbLog("failed to reopen display %s in spawn_grab_buster\n", dstr); diff --git a/x11vnc/xkb_bell.c b/x11vnc/xkb_bell.c index 1c01f7e..0ac0ceb 100644 --- a/x11vnc/xkb_bell.c +++ b/x11vnc/xkb_bell.c @@ -40,6 +40,10 @@ void initialize_xkb(void) { return; } + if (! xauth_raw(1)) { + return; + } + if (! XkbOpenDisplay(DisplayString(dpy), &xkb_base_event_type, &ir, NULL, NULL, &reason) ) { if (! quiet) { @@ -49,6 +53,7 @@ void initialize_xkb(void) { xkb_base_event_type = 0; xkb_present = 0; } + xauth_raw(0); } void initialize_watch_bell(void) { diff --git a/x11vnc/xrecord.c b/x11vnc/xrecord.c index ed087b5..b7bcbe5 100644 --- a/x11vnc/xrecord.c +++ b/x11vnc/xrecord.c @@ -118,8 +118,8 @@ static void xrecord_grabserver(int start) { XSync(gdpy_ctrl, True); if (! rc_grab || trapped_record_xerror) { - XCloseDisplay(gdpy_ctrl); - XCloseDisplay(gdpy_data); + XCloseDisplay_wr(gdpy_ctrl); + XCloseDisplay_wr(gdpy_data); gdpy_ctrl = NULL; gdpy_data = NULL; XSetErrorHandler(old_handler); @@ -127,8 +127,8 @@ static void xrecord_grabserver(int start) { } rc = XRecordEnableContextAsync(gdpy_data, rc_grab, record_grab, NULL); if (!rc || trapped_record_xerror) { - XCloseDisplay(gdpy_ctrl); - XCloseDisplay(gdpy_data); + XCloseDisplay_wr(gdpy_ctrl); + XCloseDisplay_wr(gdpy_data); gdpy_ctrl = NULL; gdpy_data = NULL; XSetErrorHandler(old_handler); @@ -179,18 +179,18 @@ void initialize_xrecord(void) { X_LOCK; /* open a 2nd control connection to DISPLAY: */ if (rdpy_data) { - XCloseDisplay(rdpy_data); + XCloseDisplay_wr(rdpy_data); rdpy_data = NULL; } if (rdpy_ctrl) { - XCloseDisplay(rdpy_ctrl); + XCloseDisplay_wr(rdpy_ctrl); rdpy_ctrl = NULL; } - rdpy_ctrl = XOpenDisplay(DisplayString(dpy)); + rdpy_ctrl = XOpenDisplay_wr(DisplayString(dpy)); XSync(dpy, True); XSync(rdpy_ctrl, True); /* open datalink connection to DISPLAY: */ - rdpy_data = XOpenDisplay(DisplayString(dpy)); + rdpy_data = XOpenDisplay_wr(DisplayString(dpy)); if (!rdpy_ctrl || ! rdpy_data) { X_UNLOCK; return; @@ -206,19 +206,19 @@ void initialize_xrecord(void) { * in place, why? Not sure, so we manually watch for grabs... */ if (gdpy_data) { - XCloseDisplay(gdpy_data); + XCloseDisplay_wr(gdpy_data); gdpy_data = NULL; } if (gdpy_ctrl) { - XCloseDisplay(gdpy_ctrl); + XCloseDisplay_wr(gdpy_ctrl); gdpy_ctrl = NULL; } xserver_grabbed = 0; - gdpy_ctrl = XOpenDisplay(DisplayString(dpy)); + gdpy_ctrl = XOpenDisplay_wr(DisplayString(dpy)); XSync(dpy, True); XSync(gdpy_ctrl, True); - gdpy_data = XOpenDisplay(DisplayString(dpy)); + gdpy_data = XOpenDisplay_wr(DisplayString(dpy)); if (gdpy_ctrl && gdpy_data) { disable_grabserver(gdpy_ctrl, 0); disable_grabserver(gdpy_data, 0); @@ -260,19 +260,19 @@ void shutdown_xrecord(void) { } if (rdpy_data) { - XCloseDisplay(rdpy_data); + XCloseDisplay_wr(rdpy_data); rdpy_data = NULL; } if (rdpy_ctrl) { - XCloseDisplay(rdpy_ctrl); + XCloseDisplay_wr(rdpy_ctrl); rdpy_ctrl = NULL; } if (gdpy_data) { - XCloseDisplay(gdpy_data); + XCloseDisplay_wr(gdpy_data); gdpy_data = NULL; } if (gdpy_ctrl) { - XCloseDisplay(gdpy_ctrl); + XCloseDisplay_wr(gdpy_ctrl); gdpy_ctrl = NULL; } xserver_grabbed = 0; @@ -1367,16 +1367,16 @@ static void shutdown_record_context(XRecordContext rc, int bequiet, int reopen) if (debug_scroll) { rfbLog("closing RECORD data connection.\n"); } - XCloseDisplay(rdpy_data); + XCloseDisplay_wr(rdpy_data); rdpy_data = NULL; if (debug_scroll) { rfbLog("closing RECORD control connection.\n"); } - XCloseDisplay(rdpy_ctrl); + XCloseDisplay_wr(rdpy_ctrl); rdpy_ctrl = NULL; - rdpy_ctrl = XOpenDisplay(dpystr); + rdpy_ctrl = XOpenDisplay_wr(dpystr); if (! rdpy_ctrl) { rfbLog("Failed to reopen RECORD control connection:" @@ -1390,13 +1390,13 @@ static void shutdown_record_context(XRecordContext rc, int bequiet, int reopen) disable_grabserver(rdpy_ctrl, 0); XSync(rdpy_ctrl, True); - rdpy_data = XOpenDisplay(dpystr); + rdpy_data = XOpenDisplay_wr(dpystr); if (! rdpy_data) { rfbLog("Failed to reopen RECORD data connection:" "%s\n", dpystr); rfbLog(" disabling RECORD scroll detection.\n"); - XCloseDisplay(rdpy_ctrl); + XCloseDisplay_wr(rdpy_ctrl); rdpy_ctrl = NULL; use_xrecord = 0; return; diff --git a/x11vnc/xwrappers.c b/x11vnc/xwrappers.c index 14c63dd..88413b6 100644 --- a/x11vnc/xwrappers.c +++ b/x11vnc/xwrappers.c @@ -68,6 +68,10 @@ void disable_grabserver(Display *in_dpy, int change); Bool XRecordQueryVersion_wr(Display *dpy, int *maj, int *min); +int xauth_raw(int on); +Display *XOpenDisplay_wr(char *display_name); +int XCloseDisplay_wr(Display *display); + void copy_raw_fb(XImage *dest, int x, int y, unsigned int w, unsigned int h); static void upup_downdown_warning(KeyCode key, Bool down); @@ -879,4 +883,74 @@ Bool XRecordQueryVersion_wr(Display *dpy, int *maj, int *min) { #endif } +int xauth_raw(int on) { + char tmp[] = "/tmp/x11vnc-xauth.XXXXXX"; + int tmp_fd = -1; + static char *old_xauthority = NULL; + static char *old_tmp = NULL; + int db = 0; + + if (on) { + if (old_xauthority) { + free(old_xauthority); + old_xauthority = NULL; + } + if (old_tmp) { + free(old_tmp); + old_tmp = NULL; + } + if (xauth_raw_data) { + tmp_fd = mkstemp(tmp); + if (tmp_fd < 0) { + rfbLog("could not create tmp xauth file: %s\n", tmp); + return 0; + } + if (db) fprintf(stderr, "tmp: %s\n", tmp); + write(tmp_fd, xauth_raw_data, xauth_raw_len); + close(tmp_fd); + if (getenv("XAUTHORITY")) { + old_xauthority = strdup(getenv("XAUTHORITY")); + } else { + old_xauthority = strdup(""); + } + set_env("XAUTHORITY", tmp); + old_tmp = strdup(tmp); + } + return 1; + } else { + if (old_xauthority) { + set_env("XAUTHORITY", old_xauthority); + free(old_xauthority); + old_xauthority = NULL; + } + if (old_tmp) { + unlink(old_tmp); + free(old_tmp); + old_tmp = NULL; + } + return 1; + } +} + +Display *XOpenDisplay_wr(char *display_name) { + Display *d; + int db = 0; + + if (! xauth_raw(1)) { + return NULL; + } + + d = XOpenDisplay(display_name); + if (db) fprintf(stderr, "XOpenDisplay_wr: %s 0x%x\n", display_name, d); + + xauth_raw(0); + + return d; +} + +int XCloseDisplay_wr(Display *display) { + int db = 0; + if (db) fprintf(stderr, "XCloseDisplay_wr: 0x%x\n", display); + return XCloseDisplay(display); +} diff --git a/x11vnc/xwrappers.h b/x11vnc/xwrappers.h index e464636..38bb72b 100644 --- a/x11vnc/xwrappers.h +++ b/x11vnc/xwrappers.h @@ -68,4 +68,8 @@ extern void disable_grabserver(Display *in_dpy, int change); extern Bool XRecordQueryVersion_wr(Display *dpy, int *maj, int *min); +extern int xauth_raw(int on); +extern Display *XOpenDisplay_wr(char *display_name); +extern int XCloseDisplay_wr(Display *display); + #endif /* _X11VNC_XWRAPPERS_H */ |