summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--ChangeLog6
-rw-r--r--libvncclient/sockets.c4
-rw-r--r--libvncserver/cargs.c12
-rwxr-xr-xlibvncserver/httpd.c3
-rw-r--r--libvncserver/main.c2
-rwxr-xr-xlibvncserver/sockets.c42
-rw-r--r--rfb/rfb.h6
-rw-r--r--x11vnc/ChangeLog5
-rw-r--r--x11vnc/README1287
-rwxr-xr-xx11vnc/tkx11vnc6
-rw-r--r--x11vnc/tkx11vnc.h6
-rw-r--r--x11vnc/x11vnc.129
-rw-r--r--x11vnc/x11vnc.c258
13 files changed, 1008 insertions, 658 deletions
diff --git a/ChangeLog b/ChangeLog
index 4a8482b..b769313 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2005-03-04 Karl Runge <runge@karlrunge.com>
+ * libvncserver/{cargs.c,sockets.c}: add -listen option and
+ rfbScreen member listenInterface.
+ * rfb/rfb.h: rfbListenOnTCPPort() and rfbListenOnUDPPort()
+ function prototypes changed to include network interface.
+
2005-02-14 Karl Runge <runge@karlrunge.com>
* x11vnc: -users lurk=, -solid for cde, -gui ez,.. beginner mode.
diff --git a/libvncclient/sockets.c b/libvncclient/sockets.c
index efe7eb9..21047fb 100644
--- a/libvncclient/sockets.c
+++ b/libvncclient/sockets.c
@@ -305,7 +305,7 @@ FindFreeTcpPort(void)
struct sockaddr_in addr;
addr.sin_family = AF_INET;
- addr.sin_addr.s_addr = INADDR_ANY;
+ addr.sin_addr.s_addr = htonl(INADDR_ANY);
sock = socket(AF_INET, SOCK_STREAM, 0);
if (sock < 0) {
@@ -339,7 +339,7 @@ ListenAtTcpPort(int port)
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
- addr.sin_addr.s_addr = INADDR_ANY;
+ addr.sin_addr.s_addr = htonl(INADDR_ANY);
sock = socket(AF_INET, SOCK_STREAM, 0);
if (sock < 0) {
diff --git a/libvncserver/cargs.c b/libvncserver/cargs.c
index 254f2ce..fbd3cc9 100644
--- a/libvncserver/cargs.c
+++ b/libvncserver/cargs.c
@@ -14,6 +14,8 @@
#include <rfb/rfb.h>
+extern rfbStringToAddr(char *str, in_addr_t *iface);
+
void
rfbUsage(void)
{
@@ -36,6 +38,8 @@ rfbUsage(void)
fprintf(stderr, "-httpport portnum use portnum for http connection\n");
fprintf(stderr, "-enablehttpproxy enable http proxy support\n");
fprintf(stderr, "-progressive height enable progressive updating for slow links\n");
+ fprintf(stderr, "-listen ipaddr listen for connections only on network interface with\n");
+ fprintf(stderr, " addr ipaddr. '-listen localhost' and hostname work too.\n");
}
/* purges COUNT arguments from ARGV at POSITION and decrements ARGC.
@@ -125,6 +129,14 @@ rfbProcessArguments(rfbScreenInfoPtr rfbScreen,int* argc, char *argv[])
return FALSE;
}
rfbScreen->progressiveSliceHeight = atoi(argv[++i]);
+ } else if (strcmp(argv[i], "-listen") == 0) { /* -listen ipaddr */
+ if (i + 1 >= *argc) {
+ rfbUsage();
+ return FALSE;
+ }
+ if (! rfbStringToAddr(argv[++i], &(rfbScreen->listenInterface))) {
+ return FALSE;
+ }
} else {
i++;
i1=i;
diff --git a/libvncserver/httpd.c b/libvncserver/httpd.c
index e169c30..b973bb6 100755
--- a/libvncserver/httpd.c
+++ b/libvncserver/httpd.c
@@ -102,7 +102,8 @@ rfbHttpInitSockets(rfbScreenInfoPtr rfbScreen)
rfbLog(" URL http://%s:%d\n",rfbScreen->thisHost,rfbScreen->httpPort);
- if ((rfbScreen->httpListenSock = rfbListenOnTCPPort(rfbScreen->httpPort)) < 0) {
+ if ((rfbScreen->httpListenSock =
+ rfbListenOnTCPPort(rfbScreen->httpPort, rfbScreen->listenInterface)) < 0) {
rfbLogPerror("ListenOnTCPPort");
return;
}
diff --git a/libvncserver/main.c b/libvncserver/main.c
index 0f68ee1..9447bf0 100644
--- a/libvncserver/main.c
+++ b/libvncserver/main.c
@@ -579,6 +579,8 @@ rfbScreenInfoPtr rfbGetScreen(int* argc,char** argv,
/* disable progressive updating per default */
screen->progressiveSliceHeight = 0;
+ screen->listenInterface = htonl(INADDR_ANY);
+
if(!rfbProcessArguments(screen,argc,argv)) {
free(screen);
return 0;
diff --git a/libvncserver/sockets.c b/libvncserver/sockets.c
index 0937097..0aba2dc 100755
--- a/libvncserver/sockets.c
+++ b/libvncserver/sockets.c
@@ -102,6 +102,8 @@ int rfbMaxClientWait = 20000; /* time (ms) after which we decide client has
void
rfbInitSockets(rfbScreenInfoPtr rfbScreen)
{
+ in_addr_t iface = rfbScreen->listenInterface;
+
if (rfbScreen->socketInitDone)
return;
@@ -132,9 +134,8 @@ rfbInitSockets(rfbScreenInfoPtr rfbScreen)
if(rfbScreen->autoPort) {
int i;
rfbLog("Autoprobing TCP port \n");
-
for (i = 5900; i < 6000; i++) {
- if ((rfbScreen->listenSock = rfbListenOnTCPPort(i)) >= 0) {
+ if ((rfbScreen->listenSock = rfbListenOnTCPPort(i, iface)) >= 0) {
rfbScreen->port = i;
break;
}
@@ -153,7 +154,7 @@ rfbInitSockets(rfbScreenInfoPtr rfbScreen)
else if(rfbScreen->port>0) {
rfbLog("Listening for VNC connections on TCP port %d\n", rfbScreen->port);
- if ((rfbScreen->listenSock = rfbListenOnTCPPort(rfbScreen->port)) < 0) {
+ if ((rfbScreen->listenSock = rfbListenOnTCPPort(rfbScreen->port, iface)) < 0) {
rfbLogPerror("ListenOnTCPPort");
return;
}
@@ -166,7 +167,7 @@ rfbInitSockets(rfbScreenInfoPtr rfbScreen)
if (rfbScreen->udpPort != 0) {
rfbLog("rfbInitSockets: listening for input on UDP port %d\n",rfbScreen->udpPort);
- if ((rfbScreen->udpSock = rfbListenOnUDPPort(rfbScreen->udpPort)) < 0) {
+ if ((rfbScreen->udpSock = rfbListenOnUDPPort(rfbScreen->udpPort, iface)) < 0) {
rfbLogPerror("ListenOnUDPPort");
return;
}
@@ -527,9 +528,29 @@ rfbWriteExact(cl, buf, len)
return 1;
}
+/* currently private, called by rfbProcessArguments() */
+int
+rfbStringToAddr(char *str, in_addr_t *addr) {
+ if (str == NULL || *str == '\0' || strcmp(str, "any") == 0) {
+ *addr = htonl(INADDR_ANY);
+ } else if (strcmp(str, "localhost") == 0) {
+ *addr = htonl(INADDR_LOOPBACK);
+ } else {
+ struct hostent *hp;
+ if ((*addr = inet_addr(str)) == htonl(INADDR_NONE)) {
+ if (!(hp = gethostbyname(str))) {
+ return 0;
+ }
+ *addr = *(unsigned long *)hp->h_addr;
+ }
+ }
+ return 1;
+}
+
int
-rfbListenOnTCPPort(port)
+rfbListenOnTCPPort(port, iface)
int port;
+ in_addr_t iface;
{
struct sockaddr_in addr;
int sock;
@@ -538,8 +559,7 @@ rfbListenOnTCPPort(port)
memset(&addr, 0, sizeof(addr));
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
- /* addr.sin_addr.s_addr = interface.s_addr; */
- addr.sin_addr.s_addr = INADDR_ANY;
+ addr.sin_addr.s_addr = iface;
if ((sock = socket(AF_INET, SOCK_STREAM, 0)) < 0) {
return -1;
@@ -574,7 +594,7 @@ rfbConnectToTcpAddr(host, port)
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
- if ((addr.sin_addr.s_addr = inet_addr(host)) == INADDR_NONE)
+ if ((addr.sin_addr.s_addr = inet_addr(host)) == htonl(INADDR_NONE))
{
if (!(hp = gethostbyname(host))) {
errno = EINVAL;
@@ -596,8 +616,9 @@ rfbConnectToTcpAddr(host, port)
}
int
-rfbListenOnUDPPort(port)
+rfbListenOnUDPPort(port, iface)
int port;
+ in_addr_t iface;
{
struct sockaddr_in addr;
int sock;
@@ -606,8 +627,7 @@ rfbListenOnUDPPort(port)
memset(&addr, 0, sizeof(addr));
addr.sin_family = AF_INET;
addr.sin_port = htons(port);
- /* addr.sin_addr.s_addr = interface.s_addr; */
- addr.sin_addr.s_addr = INADDR_ANY;
+ addr.sin_addr.s_addr = iface;
if ((sock = socket(AF_INET, SOCK_DGRAM, 0)) < 0) {
return -1;
diff --git a/rfb/rfb.h b/rfb/rfb.h
index bdff995..660baab 100644
--- a/rfb/rfb.h
+++ b/rfb/rfb.h
@@ -257,6 +257,8 @@ typedef struct _rfbScreenInfo
/* if LibVNCServer doesn't know the normal message, it calls this
* hook. If the hook handles the message, it returns TRUE. */
rfbProcessCustomClientMessageProcPtr processCustomClientMessage;
+
+ in_addr_t listenInterface;
} rfbScreenInfo, *rfbScreenInfoPtr;
@@ -506,8 +508,8 @@ extern int rfbWriteExact(rfbClientPtr cl, const char *buf, int len);
extern void rfbCheckFds(rfbScreenInfoPtr rfbScreen,long usec);
extern int rfbConnect(rfbScreenInfoPtr rfbScreen, char* host, int port);
extern int rfbConnectToTcpAddr(char* host, int port);
-extern int rfbListenOnTCPPort(int port);
-extern int rfbListenOnUDPPort(int port);
+extern int rfbListenOnTCPPort(int port, in_addr_t iface);
+extern int rfbListenOnUDPPort(int port, in_addr_t iface);
/* rfbserver.c */
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog
index dbeb8b7..751c5ff 100644
--- a/x11vnc/ChangeLog
+++ b/x11vnc/ChangeLog
@@ -1,3 +1,8 @@
+2005-03-04 Karl Runge <runge@karlrunge.com>
+ * add changes to couple with -listen option, in particular
+ the behavior of -localhost and remote control cmds.
+ * workarounds for old trees.
+
2005-02-23 Karl Runge <runge@karlrunge.com>
* final changes for 0.7.1 release.
diff --git a/x11vnc/README b/x11vnc/README
index 2ee2b8c..86fdc67 100644
--- a/x11vnc/README
+++ b/x11vnc/README
@@ -1,5 +1,5 @@
-x11vnc README file Date: Wed Feb 23 12:59:36 EST 2005
+x11vnc README file Date: Fri Mar 4 20:24:54 EST 2005
The following information is taken from these URLs:
@@ -296,8 +296,8 @@ 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 Dec 2004, the [33]x11vnc-0.7.tar.gz source package is
- released (recommended download) . The [34]x11vnc 0.7 release notes.
+ link. As of Feb 2005, the [33]x11vnc-0.7.1.tar.gz source package is
+ released (recommended download) . The [34]x11vnc 0.7.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,
@@ -333,13 +333,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.7 release of x11vnc: replace
- with the version you downloaded):
+ build as follows (example given for the 0.7.1 release of x11vnc:
+ replace with the version you downloaded):
(un-tar the x11vnc+libvncserver tarball)
-# gzip -dc x11vnc-0.7.tar.gz | tar -xvf -
+# gzip -dc x11vnc-0.7.1.tar.gz | tar -xvf -
(cd to the source directory)
-# cd x11vnc-0.7
+# cd x11vnc-0.7.1
(run configure and then run make)
# ./configure
@@ -370,7 +370,7 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer.
makes a noticeable difference over a fast LAN.
- Shortcut: On Solaris 10 you can pick up everything just by insuring
+ Shortcuts: On Solaris 10 you can pick up everything just by insuring
that your PATH has /usr/sfw/bin (for gcc) and /usr/ccs/bin (for other
build tools), e.g.:
env PATH=/usr/sfw/bin:/usr/ccs/bin:$PATH sh -c './configure; make'
@@ -397,7 +397,8 @@ r/sfw; make'
[45]http://www.gzip.org/zlib/. See also
[46]http://www.sunfreeware.com/ for Solaris binary packages of these
libraries as well as for gcc. Normally they will install into
- /usr/local.
+ /usr/local but you can install them anywhere with the
+ --prefix=/path/to/anywhere, etc.
Here is a build script that indicates one way to pass the library
@@ -469,12 +470,13 @@ ls -l ./x11vnc/x11vnc
Building on HP-UX: For jpeg and zlib you will need to do the same
sort of thing as described above for Solaris. You set CPPFLAGS and
- LDFLAGS to find them. You do not need to do any of the above
- /usr/openwin stuff. Also, HP-UX does not seem to support -R, so get
- rid of the -R items in LDFLAGS. Because of this, at runtime you may
- need to set LD_LIBRARY_PATH to indicate the directory paths so the
- libraries can be found. Starting with the 0.7.1 x11vnc release the
- configure --with-jpeg=DIR --with-zlib=DIR options are handy.
+ LDFLAGS to find them (see below for an example). You do not need to do
+ any of the above /usr/openwin stuff. Also, HP-UX does not seem to
+ support -R, so get rid of the -R items in LDFLAGS. Because of this, at
+ runtime you may need to set LD_LIBRARY_PATH or SHLIB_PATH to indicate
+ the directory paths so the libraries can be found. It is a good idea
+ to have static archives, e.g. libz.a and libjpeg.a for the nonstandard
+ libraries so that they get bolted into the x11vnc binary.
Finally, there seems to be a bug with gcc on HP-UX 11.xx: something
fails (in the gcc private header files?) and it thinks it cannot find
@@ -482,6 +484,15 @@ ls -l ./x11vnc/x11vnc
-DLIBVNCSERVER_HAVE_GETTIMEOFDAY=1. You may get some warnings but we
have verified that this generates working x11vnc binaries on HP-UX
hppa and ia64.
+
+ Here is what we recently did to build x11vnc 0.7.1 on HP-UX 11.11
+env CPPFLAGS="-DLIBVNCSERVER_HAVE_GETTIMEOFDAY=1 -I $HOME/hpux/jpeg/include -I
+$HOME/hpux/zlib/include" LDFLAGS="-L $HOME/hpux/jpeg/lib -L $HOME/hpux/zlib/lib
+" ./configure
+make
+
+ Where we had static archives (libjpeg.a, libz.a) only in the
+ $HOME/hpux/... directories.
_________________________________________________________________
Some Notes:
@@ -653,6 +664,8 @@ ls -l ./x11vnc/x11vnc
Please feel free to [61]contact me if you have any questions,
problems, or comments about x11vnc, etc.
+ Also, some people ask if they can make a donation, see [62]this link
+ for that.
_________________________________________________________________
x11vnc FAQ:
@@ -660,42 +673,42 @@ ls -l ./x11vnc/x11vnc
[Building and Starting]
- [62]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed
+ [63]Q-1: I can't get x11vnc to start up. It says "XOpenDisplay failed
(null)" or "Xlib: connection to ":0.0" refused by server" and then
exits. What do I need to do?
- [63]Q-2: I can't get x11vnc and/or libvncserver to compile.
+ [64]Q-2: I can't get x11vnc and/or libvncserver to compile.
- [64]Q-3: Help, I need to run x11vnc on Solaris 2.5.1 and it doesn't
+ [65]Q-3: Help, I need to run x11vnc on Solaris 2.5.1 and it doesn't
compile!
- [65]Q-4: Where can I get a precompiled x11vnc binary for my Operating
+ [66]Q-4: Where can I get a precompiled x11vnc binary for my Operating
System?
- [66]Q-5: Where can I get a VNC Viewer binary (or source code) for the
+ [67]Q-5: Where can I get a VNC Viewer binary (or source code) for the
Operating System I will be viewing from?
- [67]Q-6: How can I see all of x11vnc's command line options and
+ [68]Q-6: How can I see all of x11vnc's command line options and
documentation on how to use them?
- [68]Q-7: I don't like typing arcane command line options every time I
+ [69]Q-7: 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?
- [69]Q-8: Can I make x11vnc more quiet and also go into the background
+ [70]Q-8: Can I make x11vnc more quiet and also go into the background
after starting up?
- [70]Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies
+ [71]Q-9: 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.
[Win2VNC Related]
- [71]Q-10: I have two separate machine displays in front of me, one
+ [72]Q-10: 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?
- [72]Q-11: I am running Win2VNC on my Windows machine and I'm trying to
+ [73]Q-11: I am running Win2VNC on my Windows machine and I'm trying to
create a dual-screen mode with my second display monitor by running
"x11vnc -nofb". Whenever I initiate the connection Win2VNC quickly
disconnects and x11vnc says something like:
@@ -703,208 +716,216 @@ ls -l ./x11vnc/x11vnc
[Color Issues]
- [73]Q-12: The X display I run x11vnc on is only 8 bits per pixel (bpp)
+ [74]Q-12: 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 the colors are incorrect in certain
windows.
- [74]Q-13: Color problems: Why are the colors for some windows messed
+ [75]Q-13: Color problems: Why are the colors for some windows messed
up in x11vnc? BTW, I have an X display that 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.
- [75]Q-14: How do I figure out the window id to supply to the -id
+ [76]Q-14: How do I figure out the window id to supply to the -id
windowid option?
- [76]Q-15: Why don't menus or other transient windows come up when I am
+ [77]Q-15: Why don't menus or other transient windows come up when I am
using the -id windowid option to view a single application window?
- [77]Q-16: My X display is depth 24 at 24bpp (instead of the normal
+ [78]Q-16: 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 vncviewer. What's up?
+ x11vnc and/or vncviewer. What's up?
[Xterminals]
- [78]Q-17: Can I use x11vnc to view and interact with an Xterminal
+ [79]Q-17: 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?
- [79]Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for
+ [80]Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for
a Unix/Linux machine acting as an Xterminal?
[Remote Control]
- [80]Q-19: How do I stop x11vnc once it is running in the background?
+ [81]Q-19: How do I stop x11vnc once it is running in the background?
- [81]Q-20: Can I change settings in x11vnc without having to restart
+ [82]Q-20: Can I change settings in x11vnc without having to restart
it? I.e., is there a way to remote control it?
[Security and Permissions]
- [82]Q-21: How do I create a VNC password for use with x11vnc?
+ [83]Q-21: How do I create a VNC password for use with x11vnc?
- [83]Q-22: Can I have two passwords for VNC viewers, one for full
+ [84]Q-22: Can I have two passwords for VNC viewers, one for full
access and the other for view-only access to the display?
- [84]Q-23: Can I fine tune what types of user input are allowed? E.g.
+ [85]Q-23: 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?
- [85]Q-24: Why does x11vnc exit as soon as the VNC viewer disconnects?
+ [86]Q-24: 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?
- [86]Q-25: Can I limit which machines incoming VNC clients can connect
+ [87]Q-25: Can I limit which machines incoming VNC clients can connect
from?
- [87]Q-26: How do I build x11vnc/libvncserver with libwrap
+ [88]Q-26: How do I build x11vnc/libvncserver with libwrap
(tcp_wrappers) support?
- [88]Q-27: How can I tunnel my connection to x11vnc via an encrypted
+ [89]Q-27: 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?
+
+ [90]Q-28: Now that -localhost implies listening only on the loopback
+ interface, how I can occasionally allow in a non-local host via the
+ allowonce remote control command?
+
+ [91]Q-29: How can I tunnel my connection to x11vnc via an encrypted
SSH channel between two Unix machines?
- [89]Q-28: How can I tunnel my connection to x11vnc via an encrypted
+ [92]Q-30: How can I tunnel my connection to x11vnc via an encrypted
SSH channel from Windows using an SSH client like Putty?
- [90]Q-29: Can I prompt the user at the local X display whether the
+ [93]Q-31: 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?
- [91]Q-30: Does x11vnc support Unix usernames and passwords? Can I
+ [94]Q-32: Does x11vnc support Unix usernames and passwords? Can I
further limit the set of Unix usernames who can connect to the VNC
desktop?
- [92]Q-31: I start x11vnc as root because it is launched via inetd(1)
+ [95]Q-33: I start x11vnc as root because it is launched via inetd(1)
or a display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- [93]Q-32: I use a screen-lock when I leave my workstation (e.g.
+ [96]Q-34: 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?
- [94]Q-33: Can I have x11vnc automatically lock the screen when I
+ [97]Q-35: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
[Display Managers and Services]
- [95]Q-34: How can I run x11vnc as a "service" that is always
+ [98]Q-36: How can I run x11vnc as a "service" that is always
available?
- [96]Q-35: How can I use x11vnc to connect to an X login screen like
+ [99]Q-37: 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).
- [97]Q-36: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
+ [100]Q-38: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
- [98]Q-37: How do I make x11vnc work with the Java VNC viewer applet in
- a web browser?
+ [101]Q-39: How do I make x11vnc work with the Java VNC viewer applet
+ in a web browser?
- [99]Q-38: Are reverse connections (i.e. the VNC server connecting to
+ [102]Q-40: Are reverse connections (i.e. the VNC server connecting to
the VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
[Resource Usage and Performance]
- [100]Q-39: I have lots of memory, but why does x11vnc fail with
+ [103]Q-41: 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)?
- [101]Q-40: How can I make x11vnc use less system resources?
+ [104]Q-42: How can I make x11vnc use less system resources?
- [102]Q-41: How can I make x11vnc use MORE system resources?
+ [105]Q-43: How can I make x11vnc use MORE system resources?
- [103]Q-42: I use x11vnc over a slow link with high latency (e.g.
+ [106]Q-44: I use x11vnc over a slow link with high latency (e.g.
dialup modem), is there anything I can do to speed things up?
- [104]Q-43: When I drag windows around with the mouse or scroll up and
+ [107]Q-45: 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?
[Mouse Cursor Shapes]
- [105]Q-44: Why isn't the mouse cursor shape (the little icon shape
+ [108]Q-46: Why isn't the mouse cursor shape (the little icon shape
where the mouse pointer is) correct as I move from window to window?
- [106]Q-45: When using XFIXES cursorshape mode, some of the cursors
+ [109]Q-47: 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?
- [107]Q-46: In XFIXES mode, are there any hacks to handle cursor
+ [110]Q-48: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
[Mouse Pointer]
- [108]Q-47: Why does the mouse arrow just stay in one corner in my
+ [111]Q-49: Why does the mouse arrow just stay in one corner in my
vncviewer, whereas my cursor (that does move) is just a dot?
- [109]Q-48: Can I take advantage of the TightVNC extension to the VNC
+ [112]Q-50: 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)?
- [110]Q-49: Is it possible to swap the mouse buttons (e.g. left-handed
+ [113]Q-51: 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]
- [111]Q-50: How can I get my AltGr and Shift modifiers to work between
+ [114]Q-52: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- [112]Q-51: When I try to type a "<" (i.e. less than) instead I get ">"
+ [115]Q-53: When I try to type a "<" (i.e. less than) instead I get ">"
(i.e. greater than)! Strangely, typing ">" works OK!!
- [113]Q-52: I'm using an "international" keyboard (e.g. German "de", or
+ [116]Q-54: 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?
- [114]Q-53: When typing I sometimes get double, triple, or more of my
+ [117]Q-55: 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?
- [115]Q-54: The x11vnc -norepeat mode is in effect, but I still get
+ [118]Q-56: The x11vnc -norepeat mode is in effect, but I still get
repeated keystrokes!!
- [116]Q-55: The machine where I run x11vnc has an AltGr key, but the
+ [119]Q-57: 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?
- [117]Q-56: I have a Sun machine I run x11vnc on. Its Sun keyboard has
+ [120]Q-58: 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)
- [118]Q-57: Can I map a keystroke to a mouse button click on the remote
+ [121]Q-59: Can I map a keystroke to a mouse button click on the remote
machine?
[Screen Related Issues and Features]
- [119]Q-58: The remote display is larger (in number of pixels) than the
+ [122]Q-60: 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?
- [120]Q-59: Does x11vnc support server-side framebuffer scaling? (E.g.
+ [123]Q-61: Does x11vnc support server-side framebuffer scaling? (E.g.
to make the desktop smaller).
- [121]Q-60: Does x11vnc work with Xinerama? (i.e. multiple monitors
+ [124]Q-62: Does x11vnc work with Xinerama? (i.e. multiple monitors
joined together to form one big, single screen).
- [122]Q-61: Can I use x11vnc on a multi-headed display that is not
+ [125]Q-63: Can I use x11vnc on a multi-headed display that is not
Xinerama (i.e. separate screens :0.0, :0.1, ... for each monitor)?
- [123]Q-62: Does x11vnc support the XRANDR (X Resize, Rotate and
+ [126]Q-64: Does x11vnc support the XRANDR (X Resize, Rotate and
Reflection) extension? Whenever I rotate or resize the screen x11vnc
just seems to crash.
- [124]Q-63: Why is the view in my VNC viewer completely black? Or why
+ [127]Q-65: Why is the view in my VNC viewer completely black? Or why
is everything flashing around randomly?
- [125]Q-64: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+ [128]Q-66: 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
@@ -912,7 +933,7 @@ ls -l ./x11vnc/x11vnc
otherwise all messed up unless the X session x11vnc is attached to is
in the active VC?
- [126]Q-65: I am using x11vnc where my local machine has "popup/hidden
+ [129]Q-67: 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
@@ -920,13 +941,13 @@ ls -l ./x11vnc/x11vnc
[Misc: Clipboard, Beeps, Thanks, etc.]
- [127]Q-66: Does the Clipboard/Selection get transferred between the
+ [130]Q-68: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
- [128]Q-67: Why don't I hear the "Beeps" in my X session (e.g. when
+ [131]Q-69: Why don't I hear the "Beeps" in my X session (e.g. when
typing tput bel in an xterm)?
- [129]Q-68: Thanks for your program and for your help! Can I make a
+ [132]Q-70: Thanks for your program and for your help! Can I make a
donation?
_________________________________________________________________
@@ -939,13 +960,13 @@ ls -l ./x11vnc/x11vnc
For the former error, you need to specify the X display to connect to
(it also needs to be on the same machine x11vnc is to run on). Set
- your DISPLAY environment variable or use the [130]-display option to
+ your DISPLAY environment variable or use the [133]-display option to
specify it. Nearly always the correct value will be ":0"
For the latter error, you need to set up the X11 permissions
correctly. See the xauth(1), Xsecurity(7), and xhost(1) man pages for
much info. For example, you may need to set your XAUTHORITY
- environment variable or use the [131]-auth option to point to the
+ environment variable or use the [134]-auth option to point to the
correct cookie file (e.g. /home/joe/.Xauthority or /var/gdm/:0.Xauth),
or simply be sure you run x11vnc as the correct user (i.e. the user
who owns the X session you wish to view). Running x11vnc as root is
@@ -959,11 +980,11 @@ ls -l ./x11vnc/x11vnc
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 [132]-users option).
+ documentation on the [135]-users option).
Some Linux distributions or display managers may set XAUTHORITY to a
random local filename. You need to dig out where they have hidden the
- MIT-MAGIC-COOKIE file (and set XAUTHORITY to it or use the [133]-auth
+ MIT-MAGIC-COOKIE file (and set XAUTHORITY to it or use the [136]-auth
option). This command is often useful to find non-standard settings
for XAUTHORITY:
ps wwwweaux | tr ' ' '\n' | grep XAUTHORITY | sort -u
@@ -1033,18 +1054,16 @@ ls -l ./x11vnc/x11vnc
earlier and perhaps non-Solaris):
First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the
- above [134]Solaris build script to run the configure command. That
+ above [137]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
lines:
-#ifndef usleep
struct timeval _tmp_usleep_tv;
#define usleep(x) \
_tmp_usleep_tv.tv_sec = (x) / 1000000; \
_tmp_usleep_tv.tv_usec = (x) % 1000000; \
select(0, NULL, NULL, NULL, &_tmp_usleep_tv);
-#endif
int gethostname(char *name, int namelen);
long random();
int srandom(unsigned int seed);
@@ -1055,9 +1074,7 @@ int srandom(unsigned int seed);
#ifndef in_addr_t
typedef unsigned int in_addr_t;
#endif
-#ifndef snprintf
#define snprintf(a, n, args...) sprintf((a), ## args)
-#endif
Then run make with the Solaris build script environment, everything
should compile without problems, and the resulting x11vnc binary
@@ -1067,7 +1084,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
- [135]SunOS 4.x
+ [138]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
@@ -1076,19 +1093,19 @@ typedef unsigned int in_addr_t;
Q-4: Where can I get a precompiled x11vnc binary for my Operating
System?
- Hopefully the [136]build steps above and [137]FAQ provide enough info
+ Hopefully the [139]build steps above and [140]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) [138]http://packages.debian.org/x11vnc
+ Debian: (.deb) [141]http://packages.debian.org/x11vnc
- Slackware: (.tgz) [139]http://www.linuxpackages.net/ Redhat/Fedora:
- (.rpm) [140]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg)
- [141]http://www.sunfreeware.com/ wwexptools: (.tgz)
- [142]http://www.bell-labs.com/project/wwexptools/packages.html The
+ Slackware: (.tgz) [142]http://www.linuxpackages.net/ Redhat/Fedora:
+ (.rpm) [143]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg)
+ [144]http://www.sunfreeware.com/ wwexptools: (.tgz)
+ [145]http://www.bell-labs.com/project/wwexptools/packages.html The
last one, wwexptools, provides a variety of Unix binaries (Linux,
Solaris, HP-UX, IRIX, ...) with the intent of being compatible on a
wide range of OS releases. Find x11vnc near the bottom of that page
@@ -1100,14 +1117,14 @@ typedef unsigned int in_addr_t;
this by looking at the x11vnc output and if it says the encoding for a
client is "hextile" then likely the fast compression encodings are
missing. If you want optimal performance on your OS, you should see
- the [143]build notes above for where to download libz and libjpeg, and
+ the [146]build notes above for where to download libz and libjpeg, and
then build everything with gcc. For Solaris, the
http://www.sunfreeware.com/ packages are built with libz and libjpeg.
If the above binaries don't work and building x11vnc on your OS fails
(and all else fails!) you can try one of my motley collection of
- [144]test binaries. Some may be old, some may have extra debugging
- output, etc. They may work on your OS.
+ [147]test binaries. Some may be old, some may have extra debugging
+ output, etc. One of them may work on your OS...
As a general note, the x11vnc program is simple enough you don't
really need to install a package: the binary will in most cases work
@@ -1126,16 +1143,16 @@ typedef unsigned int in_addr_t;
To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix)
try here:
- * [145]http://www.tightvnc.com/download.html
- * [146]http://www.realvnc.com/download-free.html
- * [147]http://sourceforge.net/projects/cotvnc/
+ * [148]http://www.tightvnc.com/download.html
+ * [149]http://www.realvnc.com/download-free.html
+ * [150]http://sourceforge.net/projects/cotvnc/
Q-6: How can I see all of x11vnc's command line options and
documentation on how to use them?
Run: x11vnc -opts to list just the option names or run: x11vnc
-help for long descriptions about each option. The output is listed
- [148]here as well.
+ [151]here as well.
Q-7: 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?
@@ -1167,18 +1184,18 @@ display :0
GUI based on the remote-control functionality that was added. It's 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
- [149]-gui option for more info. Examples: "x11vnc ... -gui" and
+ [152]-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.
Q-8: Can I make x11vnc more quiet and also go into the background
after starting up?
- Use the [150]-q and [151]-bg options, respectively. (also: -quiet is
+ Use the [153]-q and [154]-bg options, respectively. (also: -quiet is
an alias for -q)
Note that under -bg the stderr messages will be lost unless you use
- the "[152]-o logfile" option.
+ the "[155]-o logfile" option.
Q-9: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with
the error message like: "Broken pipe". I'm using the -forever mode and
@@ -1190,7 +1207,7 @@ display :0
Up until of Apr/2004 the above fix only works for BSD signal systems
(Linux, FreeBSD, ...) For SYSV systems there is a workaround in my
- [153]x11vnc.c file. It also has an [154]option -sigpipe exit to have
+ [156]x11vnc.c file. It also has an [157]option -sigpipe exit to have
x11vnc clean up and exit upon receiving SIGPIPE.
[Win2VNC Related]
@@ -1200,21 +1217,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 "[155]-nofb" option
+ Yes, for best response start up x11vnc with the "[158]-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 [156]x2vnc, however you would
+ This will also work X11 to X11 using [159]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:
- * [157]Original Win2VNC
- * [158]Enhanced Win2VNC and [159]sourceforge link
- * [160]x2vnc
- * [161]x2x also [162]here
- * [163]zvnc (MorphOS)
+ * [160]Original Win2VNC
+ * [161]Enhanced Win2VNC and [162]sourceforge link
+ * [163]x2vnc
+ * [164]x2x also [165]here
+ * [166]zvnc (MorphOS)
All of them will work with x11vnc (except x2x where it is not needed).
@@ -1234,7 +1251,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, in the
- libvncserver CVS, x11vnc has the [164]-visual option to allow you to
+ libvncserver CVS, x11vnc has the [167]-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:
@@ -1250,7 +1267,7 @@ display :0
start out OK, but after a while the colors are incorrect in certain
windows.
- Use the [165]-flashcmap option to have x11vnc watch for changes in the
+ Use the [168]-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
@@ -1259,7 +1276,7 @@ display :0
example of this. Consider reconfiguring the system to 16 bpp or depth
24 TrueColor if at all possible.
- Also note that in some rare cases the [166]-notruecolor option has
+ Also note that in some rare cases the [169]-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.
@@ -1269,10 +1286,10 @@ display :0
visuals of different color depths: e.g. there are both depth 8 and 24
visuals available at the same time.
- You may want to review the [167]previous question regarding 8 bpp
+ You may want to review the [170]previous question regarding 8 bpp
PseudoColor.
- On some hardware (Sun/SPARC, Sgi), the [168]-overlay option discussed
+ On some hardware (Sun/SPARC, Sgi), the [171]-overlay option discussed
a couple paragraphs down may solve this for you (you may want to skip
to it directly).
@@ -1297,25 +1314,27 @@ TrueColor defdepth 24
in /etc/dt/config/Xservers (copy /usr/dt/config/Xservers). Also look
at the fbconfig(1) and related manpages (e.g. ffbconfig, m64config,
pgxconfig, SUNWjfb_config, etc ...) for hardware framebuffer settings
- that may achieve the same effect. In general for non-Sun machines,
- look at the "-cc class" and related options in your X server manpage
- (perhaps Xserver(1)), it may allow modifying the default visual (e.g.
- "-cc 4", see <X11/X.h> for the visual class numbers). On XFree86 some
- video card drivers (e.g. Matrox mga) have settings like Option
- "Overlay" "24,8" to support multi-depth overlays. For these, use the
- "-cc 4" X server command line option to get a depth 24 default visual.
+ that may achieve the same effect.
+
+ In general for non-Sun machines, look at the "-cc class" and related
+ options in your X server manpage (perhaps Xserver(1)), it may allow
+ modifying the default visual (e.g. "-cc 4", see <X11/X.h> for the
+ visual class numbers). On XFree86 some video card drivers (e.g. Matrox
+ mga) have settings like Option "Overlay" "24,8" to support multi-depth
+ overlays. For these, use the "-cc 4" X server command line option to
+ get a depth 24 default visual.
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 [169]-overlay x11vnc option (Aug/2004) to have x11vnc use the
+ use the [172]-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
Cadence CAD apps are mentioned by x11vnc users) that require the
- default depth be 8bpp, or will use a 8bpp visual even if depth 24
- visuals are available, and so the default depth workaround described
- in the previous paragraph is not sufficient for these apps.
+ default depth be 8bpp, or the app will use a 8bpp visual even if depth
+ 24 visuals are available, and so the default depth workaround
+ described in the previous paragraph is not sufficient for these apps.
Misc. notes on -overlay mode: An amusing by-product of -overlay mode
is that mouse cursor shape is correct. The -overlay mode may be
@@ -1327,18 +1346,18 @@ TrueColor defdepth 24
/etc/dt/config/Xservers file).
- Still not working? Run xwininfo on the application with the messed up
- 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 [170]-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).
+ Colors still not working correctly? Run xwininfo on the application
+ with the messed up 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 [173]-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. Fortunately the
- [171]-overlay option works for Solaris machines with overlay visuals
+ [174]-overlay option works for Solaris machines with overlay visuals
where most of this problem occurs.
Q-14: How do I figure out the window id to supply to the -id windowid
@@ -1348,13 +1367,13 @@ 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 [172]problems.
+ debugging x11vnc [175]problems.
When using -id windowid, note that some VNC viewers will have problems
rendering screens that have a width that is not a multiple of 4. Try
to manually adjust the window width before starting x11vnc -id ....
- Also, as of Dec/2004 libvncserver CVS you can use "[173]-id pick" to
+ Also, as of Dec/2004 libvncserver CVS you can use "[176]-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.
@@ -1371,14 +1390,14 @@ TrueColor defdepth 24
be able to see these transient windows.
If things are not working and you still want to do the single window
- polling, try the [174]-sid windowid option ("shifted" windowid).
+ polling, try the [177]-sid windowid option ("shifted" windowid).
x11vnc is known to crash under both -id and -sid, so both modes are
still experimental. Please report any reproducible bugs.
Q-16: 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 vncviewer. What's up?
+ and/or vncviewer. What's up?
First off, depth 24 at 24bpp (bpp=bits-per-pixel) is fairly uncommon
and can cause problems in general. It also can be slower than depth 24
@@ -1423,15 +1442,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 [175]-display option to point the display to that of
+ machine. Use the [178]-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 [176]-noshm option (this enables the polling over
+ and also supply the [179]-noshm option (this enables the polling over
the network).
The response will likely be sluggish. 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
- [177]-flipbyteorder if the colors get messed up due to endian byte
+ [180]-flipbyteorder if the colors get messed up due to endian byte
order differences.
Q-18: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a
@@ -1445,9 +1464,9 @@ TrueColor defdepth 24
the MIT-MAGIC-COOKIE auth file data must be copied to the Xterminal.
If $HOME/.Xauthority is exported via NFS (this is insecure of course),
then x11vnc can simply pick it up via NFS (you may need to use the
- [178]-auth option to point to the correct file). Other options include
+ [181]-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 -
+ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
and then perhaps ssh from central-server to xterm123 to start x11vnc.
You can use "xauth -f /path/to/cookie-file list" to examine the
@@ -1455,16 +1474,17 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
xauth(1) manpage for more details.
If the display name needs to be changed between the two hosts, see
- [179]this note on the xauth add ... command.
+ [182]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 to allow cookie-free local access for x11vnc.
+ You can run "xhost -127.0.0.1" after x11vnc connects if you want.
If the Xterminal is really stripped down and doesn't have any user
accounts, NFS, etc. you'll need to contact your system administrator
to set something up. It can be done!
- Not recommended, but as a last resort, you could have x11vnc [180]poll
+ Not recommended, but as a last resort, you could have x11vnc [183]poll
the Xterminal over the network.
Note: use of Display Manager (gdm, kdm, ...) auth cookie files (i.e.
@@ -1481,17 +1501,17 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
As of Dec/2004 in the libvncserver CVS there is a remote control
feature. It can change a huge amount of things on the fly: see the
- [181]-remote and [182]-query options. To shut down the running x11vnc
+ [184]-remote and [185]-query options. To shut down the running x11vnc
server just type "x11vnc -R stop". To disconnect all clients do
"x11vnc -R disconnect:all", etc.
- For older versions: If the [183]-forever option has not been supplied,
+ For older versions: If the [186]-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 [184]-bg option
+ If you have not put x11vnc in the background via the [187]-bg option
or shell & operator, then simply press Ctrl-C in the shell where
x11vnc is running to stop it. Potential Gotcha: If somehow your
Keypress of Ctrl-C went through x11vnc to the Xserver that then
@@ -1500,13 +1520,13 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
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 [185]-clear_mods option and [186]-clear_keys
+ Alt. Alternatively, the [188]-clear_mods option and [189]-clear_keys
option can be used to release pressed keys at startup and exit.
Q-20: Can I change settings in x11vnc without having to restart it?
I.e., is there a way to remote control it?
- Look at the [187]-remote (same as -R) and [188]-query (same as -Q)
+ Look at the [190]-remote (same as -R) and [191]-query (same as -Q)
options added in the Dec/2004 libvncserver CVS. They allow nearly
everything to be changed dynamically and settings to be queried.
Examples: "x11vnc -R shared", "x11vnc -R forever", "x11vnc -R
@@ -1518,7 +1538,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
be possible.
There is also a simple tcl/tk gui based on this remote control
- mechanism. See the [189]-gui option for more info.
+ mechanism. See the [192]-gui option for more info.
[Security and Permissions]
@@ -1530,12 +1550,12 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
vncpasswd(1) program from those packages. The libvncserver package
also comes with a simple program: storepasswd in the examples
directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports
- the -storepasswd "pass" "file" [190]option, which is the the same
+ the -storepasswd "pass" "file" [193]option, which is the 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: [191]-rfbauth
+ You then use the password via the x11vnc option: [194]-rfbauth
$HOME/myvncpasswd
Compared to vncpasswd(1) the latter two methods are a somewhat unsafe
@@ -1544,7 +1564,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
out for the command winding up in your shell's history file (history
-c is often a way to clear it).
- x11vnc also has the [192]-passwdfile and -passwd/-viewpasswd plain
+ x11vnc also has the [195]-passwdfile and -passwd/-viewpasswd plain
text (i.e. not obscured like the -rfbauth VNC passwords) password
options.
@@ -1552,13 +1572,13 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
and the other for view-only access to the display?
Yes, as of May/2004 in the libvncserver CVS there is the
- [193]-viewpasswd option to supply the view-only password. Note the
- full-access password option [194]-passwd must be supplied at the same
+ [196]-viewpasswd option to supply the view-only password. Note the
+ full-access password option [197]-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
- [195]-passwdfile option to specify a file containing plain text
+ [198]-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
@@ -1566,7 +1586,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
it is taken as the view-only password. (use "__EMPTY__" to supply an
empty one).
- View-only passwords currently do not work for the [196]-rfbauth
+ View-only passwords currently do not work for the [199]-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
@@ -1579,7 +1599,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
some users just be able to move the mouse, but not click or type
anything?
- As of Feb/2005, the [197]-input option allows you to do this. "K",
+ As of Feb/2005, the [200]-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
@@ -1594,22 +1614,22 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
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 [198]-forever option (aka -many) to have
+ periods of time. Use the [201]-forever option (aka -many) to have
x11vnc wait for more connections after the first client disconnects.
- Use the [199]-shared option to have x11vnc allow multiple clients to
+ Use the [202]-shared option to have x11vnc allow multiple clients to
connect simultaneously.
- Recommended additional safety measures include using ssh ([200]see
+ Recommended additional safety measures include using ssh ([203]see
above), stunnel, or a VPN to authenticate and encrypt the viewer
- connections or to at least use the -rfbauth passwd-file [201]option to
- use VNC password protection (or [202]-passwdfile) It is up to you to
+ connections or to at least use the -rfbauth passwd-file [204]option to
+ use VNC password protection (or [205]-passwdfile) It is up to you to
apply these security measures, they will not be done for you
automatically.
Q-25: Can I limit which machines incoming VNC clients can connect
from?
- Yes, look at the [203]-allow and [204]-localhost options to limit
+ Yes, look at the [206]-allow and [207]-localhost options to limit
connections by hostname or IP address. E.g.
x11vnc -allow 192.168.0.1,192.168.0.2
@@ -1621,7 +1641,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
Note that -localhost is the same as "-allow 127.0.0.1"
For more control, build libvncserver with libwrap support
- [205](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
+ [208](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5)
for complete details.
Q-26: How do I build x11vnc/libvncserver with libwrap (tcp_wrappers)
@@ -1640,24 +1660,57 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
is "vnc", e.g.:
vnc: 192.168.100.3 .example.com
- Note that if you run x11vnc out of [206]inetd you do not need to build
+ Note that if you run x11vnc out of [209]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.
- Q-27: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-27: 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?
+
+ As of Mar/2005 in the libvncserver CVS, there is the "[210]-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 "[211]-allow host1,..." option to allow only specific hosts
+ in.
+
+ This option is useful if you want insure that no one can even begin a
+ dialog with x11vnc from untrusted network interfaces (e.g. ppp0). The
+ option [212]-localhost now implies "-listen localhost" since that is
+ what most people expect it to do.
+
+ Q-28: Now that -localhost implies listening only on the loopback
+ interface, how I can occasionally allow in a non-local host via the
+ allowonce remote control command?
+
+ To do this specify "[213]-allow localhost". Unlike [214]-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
+ ([215]-listen option) via remote control or gui, you may need to also
+ manually adjust the [216]-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 [217]-localhost on
+ and off x11vnc should see to it that you never get into such a state.
+
+ Q-29: 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 [207]how to tunnel VNC via
+ See the description earlier on this page on [218]how to tunnel VNC via
SSH from Unix to Unix. A number of ways are described along with some
issues you may encounter.
Other secure encrypted methods exists, e.g. stunnel, IPSEC, various
VPNs, etc.
- Q-28: How can I tunnel my connection to x11vnc via an encrypted SSH
+ Q-30: How can I tunnel my connection to x11vnc via an encrypted SSH
channel from Windows using an SSH client like Putty?
- [208]Above we described how to tunnel VNC via SSH from Unix to Unix,
+ [219]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
@@ -1680,8 +1733,8 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
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 [209]-localhost
- and [210]-rfbauth/[211]-passwdfile options.
+ For extra protection feel free to run x11vnc with the [220]-localhost
+ and [221]-rfbauth/[222]-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
@@ -1690,19 +1743,19 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
you'll need to do a second login (ssh or rsh) to the workstation
machine 'otherhost' and then start up x11vnc on it.
- As discussed [212]above another option is to first start the VNC
+ As discussed [223]above another option is to first start the VNC
viewer in "listen" mode, and then launch x11vnc with the
- "[213]-connect localhost" option to establish the reverse connection.
+ "[224]-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).
- Q-29: Can I prompt the user at the local X display whether the
+ Q-31: 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?
- Yes, look at the "[214]-accept command" option, it allows you to
+ Yes, look at the "[225]-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
@@ -1721,7 +1774,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
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 [215]-viewonly option has been
+ mouse on the "View" button. If the [226]-viewonly option has been
supplied, the "View" action will not be present: the whole display is
view only in that case.
@@ -1737,7 +1790,7 @@ central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge -
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 [216]ftp://ftp.x.org/
+ is available at [227]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
@@ -1776,23 +1829,22 @@ elif [ $rc = 4 ]; then
fi
exit 1
- Stefan Radman has written a nice dtksh script [217]dtVncPopup for use
+ Stefan Radman has written a nice dtksh script [228]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.
Note that in all cases x11vnc will block while the external command or
popup is being run, so attached clients will not receive screen
- updates, etc during this period. (use of -threads may or may not alter
- this behavior).
+ updates, etc during this period.
- To run a command when a client disconnects, use the "[218]-gone
+ To run a command when a client disconnects, use the "[229]-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-30: Does x11vnc support Unix usernames and passwords? Can I further
+ Q-32: Does x11vnc support Unix usernames and passwords? Can I further
limit the set of Unix usernames who can connect to the VNC desktop?
Until the VNC protocol and libvncserver support this things will be
@@ -1800,13 +1852,13 @@ exit 1
such support.
One approximate method involves starting x11vnc with the
- [219]-localhost option. This basically requires the viewer user to log
+ [230]-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 username
-L 5900:localhost:5900 hostname ... See the ssh wrapper scripts
- mentioned [220]elsewhere on this page. Of course a malicious user
+ mentioned [231]elsewhere on this page. 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 watch out for is a
malicious user on the viewer side (where ssh is running) trying to
@@ -1815,7 +1867,7 @@ exit 1
Regarding limiting the set of Unix usernames who can connect, the
traditional way would be to further require a VNC password to supplied
(-rfbauth, -passwd, etc). A scheme that avoids a second password
- involves using the [221]-accept option that runs a program to examine
+ involves using the [232]-accept option that runs a program to examine
the connection information to determine which user is connecting from
the local machine. For example, the program could use the ident
service on the local machine (normally ident should not be trusted
@@ -1843,18 +1895,18 @@ exit 1 # reject it
For this to work with ssh port redirection, the ssh option
UsePrivilegeSeparation must be enabled.
- Q-31: I start x11vnc as root because it is launched via inetd(1) or a
+ Q-33: I start x11vnc as root because it is launched via inetd(1) or a
display manager like gdm(1). Can I have x11vnc later switch to a
different user?
- As of Feb/2005 x11vnc has the [222]-users option that allows things
+ As of Feb/2005 x11vnc has the [233]-users option that allows things
like this. Please read the documentation on it (in the x11vnc -help
output) carefully for features and caveats. It's use can often
decrease security unless care is taken. A nice use of it is "-users
+nobody" that switches to the Unix user nobody right after connections
to the X display are established.
- Q-32: I use a screen-lock when I leave my workstation (e.g.
+ Q-34: 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
@@ -1867,7 +1919,7 @@ exit 1 # reject it
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 [223]blockdpy.c The idea behind it is simple (but
+ source for it is [234]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
@@ -1883,15 +1935,15 @@ exit 1 # reject it
bulletproof. A really robust solution would likely require X server
and perhaps even video hardware support.
- The blockdpy utility is launched by the [224]-accept option and told
- to exit via the [225]-gone option (the vnc client user should
+ The blockdpy utility is launched by the [235]-accept option and told
+ to exit via the [236]-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.
- Q-33: Can I have x11vnc automatically lock the screen when I
+ Q-35: Can I have x11vnc automatically lock the screen when I
disconnect the VNC viewer?
- Yes, a user mentions he uses the [226]-gone option under CDE to run a
+ Yes, a user mentions he uses the [237]-gone option under CDE to run a
screen lock program:
x11vnc -display :0 -forever -gone 'dtaction LockDisplay'
@@ -1903,7 +1955,7 @@ exit 1 # reject it
[Display Managers and Services]
- Q-34: How can I run x11vnc as a "service" that is always available?
+ Q-36: How can I run x11vnc as a "service" that is always available?
There are a number of ways to do this. The primary thing you need to
decide is whether you want x11vnc to connect to the X session on the
@@ -1914,11 +1966,11 @@ exit 1 # reject it
permissions to connect to the X display.
Here are some ideas:
- * Use the description under "Continuously" in the [227]FAQ on x11vnc
+ * Use the description under "Continuously" in the [238]FAQ on x11vnc
and Display Managers
- * Use the description in the [228]FAQ on x11vnc and inetd(1)
+ * Use the description in the [239]FAQ on x11vnc and inetd(1)
* Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc)
- * Although less reliable, see the [229]x11vnc_loop rc.local hack
+ * Although less reliable, see the [240]x11vnc_loop rc.local hack
below.
The display manager scheme will not be specific to which user has the
@@ -1936,7 +1988,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
plus any other options you desire.
- Q-35: How can I use x11vnc to connect to an X login screen like xdm,
+ Q-37: 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).
@@ -1948,7 +2000,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 [230]-auth option sets XAUTHORITY). There will be a similar thing
+ (the [241]-auth option sets XAUTHORITY). There will be a similar thing
for xdm using however a different auth directory path (perhaps
something like /var/lib/xdm/authdir/authfiles/A:0-XQvaJk for xdm or
/var/lib/kdm/A:0-crWk72 for kdm, where the random characters in
@@ -1968,7 +2020,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
For dtlogin in addition to the above sort of trick (BTW, the auth file
should be in /var/dt), you'll also need to add something like
Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig
- or /usr/dt/config/Xconfig on Solaris, see [231]the example at the end
+ or /usr/dt/config/Xconfig on Solaris, see [242]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.
@@ -2007,7 +2059,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
debugging. In that case replace the -bg above with something like:
1>> /var/tmp/x11vnc.log 2>&1 &
- (or use the "[232]-o logfile" option).
+ (or use the "[243]-o logfile" option).
_________________________________________________________________
Fedora/gdm: Here is an example of what we did on a vanilla install of
@@ -2022,7 +2074,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
Then restart: /usr/sbin/gdm-restart (or reboot). The
KillInitClients=false setting is important: without it x11vnc will be
- killed immediately after the user logs in. Here are [233]full details
+ killed immediately after the user logs in. Here are [244]full details
on how to configure gdm
_________________________________________________________________
@@ -2056,22 +2108,22 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
If you do not want to deal with any display manager startup scripts,
here is a kludgey script that can be run manually or out of a boot
- file like rc.local: [234]x11vnc_loop It will need some local
+ file like rc.local: [245]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 above is
preferred.
If the machine is a traditional Xterminal you may want to read
- [235]this FAQ.
+ [246]this FAQ.
- Q-36: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
+ Q-38: Can I run x11vnc out of inetd(1)? How about xinetd(1)?
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 [236]-inetd
+ where the shell script /usr/local/bin/x11vnc_sh uses the [247]-inetd
option and looks something like (you'll need to customize to your
settings).
#!/bin/sh
@@ -2083,13 +2135,13 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg
also goes to the VNC vncviewer, and that confuses it greatly). If you
do not use a wrapper script as above but rather call x11vnc directly
in /etc/inetd.conf and do not redirect stderr, then you must specify
- the -q (aka [237]-quiet) option: /usr/local/bin/x11vnc -q -inetd ...
+ the -q (aka [248]-quiet) option: /usr/local/bin/x11vnc -q -inetd ...
or use -o logfile to collect the output in a file. The wrapper script
with stderr redirection to a log file is the recommended method
because the errors and warnings printed out are very useful in
troubleshooting problems.
- Note also the need to set XAUTHORITY via [238]-auth to point to the
+ Note also the need to set XAUTHORITY via [249]-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
@@ -2132,11 +2184,11 @@ service x11vncservice
With the contents of /usr/local/bin/x11vnc_sh similar to the example
given above.
- Q-37: How do I make x11vnc work with the Java VNC viewer applet in a
+ Q-39: 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 [239]option:
+ that connect to it, run x11vnc with this [250]option:
-httpdir /path/to/the/java/classes/dir
(this directory will contain the files index.vnc and, for example,
@@ -2159,20 +2211,21 @@ service x11vncservice
entirely from the viewer-side by having the jar file there and using
either the java or appletviewer commands to run the program.
- Q-38: Are reverse connections (i.e. the VNC server connecting to the
+ Q-40: Are reverse connections (i.e. the VNC server connecting to the
VNC viewer) using "vncviewer -listen" and vncconnect(1) supported?
As of Mar/2004 in the libvncserver CVS x11vnc supports reverse
connections. On Unix one starts the VNC viewer in listen mode:
- vncviewer -listen, and then starts up x11vnc with the [240]-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). If a file is specified
- instead: -connect /path/to/some/file then that file is checked
- periodically (about once a second) for new hosts to connect to.
+ vncviewer -listen (see your documentation for Windows, etc), and then
+ starts up x11vnc with the [251]-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). If a file is specified instead: -connect /path/to/some/file
+ then that file is checked periodically (about once a second) for new
+ hosts to connect to.
To use the vncconnect(1) program (from the core VNC package at
- www.realvnc.com) specify the [241]-vncconnect option to x11vnc (Note:
+ www.realvnc.com) specify the [252]-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
@@ -2188,7 +2241,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1"
[Resource Usage and Performance]
- Q-39: I have lots of memory, but why does x11vnc fail with shmget:
+ Q-41: 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)?
@@ -2206,7 +2259,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$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 [242]shm_clear to list and prompt for removal
+ Here is a shell script [253]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,
@@ -2240,36 +2293,36 @@ ied)
in /etc/system. See the next paragraph for more workarounds.
To minimize the number of shm segments used by x11vnc try using the
- [243]-onetile option (corresponds to only 3 shm segments used, and
+ [254]-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
- [244]-noshm option. Performance will be somewhat degraded but when
+ [255]-noshm option. Performance will be somewhat degraded but when
done over local machine sockets it should be acceptable (see an
- [245]earlier question discussing -noshm).
+ [256]earlier question discussing -noshm).
- Q-40: How can I make x11vnc use less system resources?
+ Q-42: How can I make x11vnc use less system resources?
- The [246]-nap and "[247]-wait n" (where n is the sleep between polls
+ The [257]-nap and "[258]-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. Using the
- [248]-onetile option will use less memory and use fewer shared memory
- slots (add [249]-fs 1.0 for one less slot).
+ [259]-onetile option will use less memory and use fewer shared memory
+ slots (add [260]-fs 1.0 for one less slot).
- Q-41: How can I make x11vnc use MORE system resources?
+ Q-43: How can I make x11vnc use MORE system resources?
- You can try [250]-threads and dial down the wait time (e.g. -wait 1)
- and possibly dial down [251]-defer as well. Note that if you try to
+ You can try [261]-threads and dial down the wait time (e.g. -wait 1)
+ and possibly dial down [262]-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 [252]-id option) can be streamed over a LAN or wireless at
+ the x11vnc [263]-id option) can be streamed over a LAN or wireless at
a reasonable frame rate.
- Q-42: I use x11vnc over a slow link with high latency (e.g. dialup
+ Q-44: 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 (most of which will help
@@ -2281,7 +2334,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
- [253]-solid [color] option.
+ [264]-solid [color] option.
* Configure your window manager or desktop "theme" to not use fancy
images, shading, and gradients for the window decorations, etc.
Disable Opaque moves, resizes, and animations.
@@ -2294,7 +2347,7 @@ ied)
worth it, but could be of use in some situations.
VNC viewer parameters:
- * Use a [254]TightVNC enabled viewer!
+ * Use a [265]TightVNC enabled viewer!
* Make sure the tight encoding is being used (look at vncviewer and
x11vnc outputs)
* Request 8 bits per pixel using -bgr233 (up to 4X speedup over
@@ -2312,22 +2365,22 @@ ied)
vncviewer to be very slow)
x11vnc parameters:
- * Try using [255]-nodragging (no screen updates when dragging mouse,
+ * Try using [266]-nodragging (no screen updates when dragging mouse,
but sometimes you miss visual feedback)
- * Try the [256]-progressive pixelheight mode with the block
+ * Try the [267]-progressive pixelheight mode with the block
pixelheight 100 or so (delays sending vertical blocks since they
may change while viewer is receiving earlier ones)
- * Set [257]-fs 1.0 (disables fullscreen updates)
- * Try increasing [258]-wait or [259]-defer (reduces the maximum
+ * Set [268]-fs 1.0 (disables fullscreen updates)
+ * Try increasing [269]-wait or [270]-defer (reduces the maximum
"frame rate", but won't help much for large screen changes)
- * If you just want to watch one (simple) window use [260]-id (cuts
+ * If you just want to watch one (simple) window use [271]-id (cuts
down extraneous polling and updates, but can be buggy or
insufficient)
- * Set [261]-nosel (disables all clipboard selection exchange)
- * Use [262]-nocursor and [263]-nocursorpos (repainting the remote
+ * Set [272]-nosel (disables all clipboard selection exchange)
+ * Use [273]-nocursor and [274]-nocursorpos (repainting the remote
cursor position and shape takes resources and round trips)
- Q-43: When I drag windows around with the mouse or scroll up and down
+ Q-45: 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?
@@ -2335,21 +2388,21 @@ ied)
tree. The 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 "[264]-pointer_mode 1" option.
+ way via the "[275]-pointer_mode 1" option.
- Also added was the [265]-nodragging option that disables all screen
+ Also added was the [276]-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 in the libvncserver CVS the [266]-pointer_mode n option
+ As of Dec/2004 in the libvncserver CVS the [277]-pointer_mode n option
was introduced. n=1 is the original mose, n=2 and improvement, etc..
See the -pointer_mode n help for more info.
[Mouse Cursor Shapes]
- Q-44: Why isn't the mouse cursor shape (the little icon shape where
+ Q-46: 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
@@ -2363,16 +2416,16 @@ 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 "[267]-cursor X" option that
+ A simple kludge is provided by the "[278]-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 "[268]-cursor some" option for
+ work for those cases. Also see the "[279]-cursor some" option for
additional kludges.
Note that as of Aug/2004 in the libvncserver CVS, on Solaris using the
SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse
- cursor when the [269]-overlay option is supplied. See [270]this FAQ
+ cursor when the [280]-overlay option is supplied. See [281]this FAQ
for more info.
Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support
@@ -2380,7 +2433,7 @@ ied)
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 [271]Solaris 10.
+ distros and [282]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
@@ -2388,9 +2441,9 @@ ied)
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. [272]Details can be found here.
+ under 32bpp. [283]Details can be found here.
- Q-45: When using XFIXES cursorshape mode, some of the cursors look
+ Q-47: 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?
@@ -2420,24 +2473,24 @@ 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 "[273]-alphacut n" option lets
+ course!) some tunable parameters. The "[284]-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 "[274]-alphafrac f" option tries to correct individual
+ 240. The "[285]-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 [275]-alpharemove that is useful for
+ Finally, there is an option [286]-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
-alpharemove to brighten them by having x11vnc divide out the alpha
value.
- Q-46: In XFIXES mode, are there any hacks to handle cursor
+ Q-48: In XFIXES mode, are there any hacks to handle cursor
transparency ("alpha channel") exactly?
As of Jan/2005 in the CVS, libvncserver has been modified to allow an
@@ -2445,11 +2498,11 @@ ied)
send the 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 [276]-nocursorshape x11vnc option.
+ disabled for all clients with the [287]-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
- [277]-noalphablend option to disable this behavior (always approximate
+ [288]-noalphablend option to disable this behavior (always approximate
transparent cursors with opaque RGB values).
The CursorShapeUpdates VNC extension complicates matters because the
@@ -2474,12 +2527,12 @@ ied)
[Mouse Pointer]
- Q-47: Why does the mouse arrow just stay in one corner in my
+ Q-49: 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 [278]tightvnc extension
+ This default takes advantage of a [289]tightvnc extension
(CursorShapeUpdates) that allows specifying a cursor image shape for
- the local VNC viewer. You may disable it with the [279]-nocursor
+ the local VNC viewer. You may disable it with the [290]-nocursor
option to x11vnc if your viewer does not have this extension.
Note: as of Aug/2004 in the libvncserver CVS this should be fixed: the
@@ -2487,22 +2540,22 @@ ied)
CursorShapeUpdates) will be to draw the moving cursor into the x11vnc
framebuffer. This can also be disabled via -nocursor.
- Q-48: Can I take advantage of the TightVNC extension to the VNC
+ Q-50: 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 [280]-cursorpos option when starting x11vnc. A VNC viewer must
+ Use the [291]-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 in the
- libvncserver CVS -cursorpos is the default. See also [281]-nocursorpos
- and [282]-nocursorshape.
+ libvncserver CVS -cursorpos is the default. See also [292]-nocursorpos
+ and [293]-nocursorshape.
- Q-49: Is it possible to swap the mouse buttons (e.g. left-handed
+ Q-51: 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: [283]-buttonmap
+ You can remap the mouse buttons via something like: [294]-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.
@@ -2510,7 +2563,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 [284]-debug_pointer option prints out much info for
+ Note that the [295]-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
@@ -2532,7 +2585,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 [285]-buttonmap but rather configuring the X server
+ consider not using [296]-buttonmap but rather configuring the X server
to think it has a mouse with 5 buttons even though the physical mouse
does not.
@@ -2550,10 +2603,10 @@ ied)
(yes, this is getting a little silly).
[Keyboard Issues]
- Q-50: How can I get my AltGr and Shift modifiers to work between
+ Q-52: How can I get my AltGr and Shift modifiers to work between
keyboards for different languages?
- The option [286]-modtweak should be of some use for this. It is a mode
+ The option [297]-modtweak should be of some use for this. 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.
@@ -2562,20 +2615,20 @@ ied)
default (use -nomodtweak 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 [287]this FAQ
+ and ">" it. This key does not exist on the keyboard (see [298]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 [288]FAQ about the -xkb option for a more powerful method
+ Also see the [299]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
- [289]-debug_keyboard option prints out much info for every keystroke
+ [300]-debug_keyboard option prints out much info for every keystroke
and so can be useful debugging things.
- Q-51: When I try to type a "<" (i.e. less than) instead I get ">"
+ Q-53: 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
@@ -2622,20 +2675,20 @@ ied)
-remap less-comma
These are convenient in that they do not modify the actual X server
- settings. The former ([290]-modtweak) is a mode that monitors the
+ settings. The former ([301]-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 ([291]-remap less-comma) is an immediate remapping of the
+ The latter ([302]-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 [292]FAQ about the -xkb option as a possible workaround
+ See also the [303]FAQ about the -xkb option as a possible workaround
using the XKEYBOARD extension.
- Note that the [293]-debug_keyboard option prints out much info for
+ Note that the [304]-debug_keyboard option prints out much info for
every keystroke to aid debugging keyboard problems.
- Q-52: I'm using an "international" keyboard (e.g. German "de", or
+ Q-54: 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
@@ -2656,7 +2709,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 [294]-modtweak
+ This all worked fine with x11vnc running with the [305]-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
@@ -2674,7 +2727,7 @@ ied)
* there is a new option -xkb to use the XKEYBOARD extension API to
do the Modifier key tweaking.
- The [295]-xkb option seems to fix all of the missing keys: "@", "<",
+ The [306]-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
@@ -2692,7 +2745,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:
- [296]-skip_keycodes 93
+ [307]-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
@@ -2709,14 +2762,14 @@ 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 [297]-remap x11vnc option:
+ created using the [308]-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
- [298]-add_keysyms option in the next paragraph.
- * To complement the above workaround using the [299]-remap, an
- option [300]-add_keysyms was added. This option instructs x11vnc
+ [309]-add_keysyms option in the next paragraph.
+ * To complement the above workaround using the [310]-remap, an
+ option [311]-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
@@ -2724,7 +2777,7 @@ ied)
when the Keysym is received from a VNC viewer, and only after that
would -add_keysyms, or anything else, come into play.
- Q-53: When typing I sometimes get double, triple, or more of my
+ Q-55: 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
@@ -2732,7 +2785,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) [301]-norepeat x11vnc option. You will still
+ use the new (Jul/2004) [312]-norepeat x11vnc option. You will still
have autorepeating because that is taken care of on your VNC viewer
side. Update: as of Dec/2004 -norepeat is now the default. Use -repeat
to disable it.
@@ -2754,17 +2807,17 @@ 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 [302]-norepeat (which has since Dec/2004 been
+ needed, or to use the [313]-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-54: The x11vnc -norepeat mode is in effect, but I still get repeated
+ Q-56: 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
- [303]this FAQ) If so, x11vnc is starting before your session and it
+ [314]this FAQ) If so, x11vnc is starting before your session and it
disables autorepeat when you connect, and then your session startup
could be resetting the autorepeat to be on. Or it could be something
inside your desktop that decides to turn it back on. x11vnc in
@@ -2777,11 +2830,11 @@ ied)
utility. If something in your desktop is automatically turning it back
on you will have to disable that somehow.
- Q-55: The machine where I run x11vnc has an AltGr key, but the local
+ Q-57: 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 "[304]-remap Super_R-Mode_switch" x11vnc option may
+ Something like "[315]-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)).
@@ -2791,7 +2844,7 @@ ied)
Super_R-Mode_switch,Menu-Multi_key" or use "-remap filename" to
specify remappings from a file.
- Q-56: I have a Sun machine I run x11vnc on. Its Sun keyboard has just
+ Q-58: 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)
@@ -2803,17 +2856,17 @@ 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 [305]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones
+ the [316]-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.
- Q-57: Can I map a keystroke to a mouse button click on the remote
+ Q-59: 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 [306]-remap
+ have x11vnc do the remapping. This can be done via the [317]-remap
option using the fake "keysyms" Button1, Button2, etc. as the "to"
keys (i.e. the ones after the "-")
@@ -2821,7 +2874,7 @@ ied)
a touchpad with only two buttons. It is difficult to do a middle
button "paste" because (using XFree86 Emulate3Buttons) you have to
click both buttons on the touch pad at the same time. This remapping:
- [307]-remap Super_R-Button2
+ [318]-remap Super_R-Button2
maps the Super_R "flag" key press to the Button2 click, thereby making
X pasting a bit easier.
@@ -2832,7 +2885,7 @@ ied)
[Screen Related Issues and Features]
- Q-58: The remote display is larger (in number of pixels) than the
+ Q-60: 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?
@@ -2850,15 +2903,15 @@ ied)
There may also be scaling viewers out there (e.g. TightVNC on Windows)
that automatically shrink or expand the remote framebuffer to fit the
- local display. Especially for hand-held devices. See also [308]this
+ local display. Especially for hand-held devices. See also [319]this
FAQ on x11vnc scaling.
- Q-59: Does x11vnc support server-side framebuffer scaling? (E.g. to
+ Q-61: Does x11vnc support server-side framebuffer scaling? (E.g. to
make the desktop smaller).
As of Jun/2004 in the libvncserver CVS x11vnc provides basic
server-side scaling. It is a global scaling of the desktop, not a
- per-client setting. To enable it use the "[309]-scale fraction"
+ per-client setting. To enable it use the "[320]-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 expanded (not
@@ -2900,10 +2953,10 @@ 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 ([310]-rfbport option,
+ different scalings listening on separate ports ([321]-rfbport option,
etc.).
- Q-60: Does x11vnc work with Xinerama? (i.e. multiple monitors joined
+ Q-62: 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
@@ -2915,22 +2968,22 @@ ied)
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 [311]-blackout x11vnc option allows you
+ distracting to the viewer. The [322]-blackout x11vnc option allows you
to blacken-out rectangles by specifying their WxH+X+Y geometries. If
- your system has the libXinerama library, the [312]-xinerama x11vnc
+ your system has the libXinerama library, the [323]-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 [313]-xwarppointer
+ of the large display. If this happens try using the [324]-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-61: Can I use x11vnc on a multi-headed display that is not Xinerama
+ Q-63: 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
@@ -2948,17 +3001,17 @@ 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 [314]FAQ to increase the limit. It
- is probably also a good idea to run with the [315]-onetile option in
+ /etc/system as mentioned in another [325]FAQ to increase the limit. It
+ is probably also a good idea to run with the [326]-onetile option in
this case (to limit each x11vnc to 3 shm segments), or even
- [316]-noshm to use no shm segments.
+ [327]-noshm to use no shm segments.
- Q-62: Does x11vnc support the XRANDR (X Resize, Rotate and Reflection)
+ Q-64: 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 in the libvncserver CVS x11vnc supports XRANDR. You
- enable it with the [317]-xrandr option to make x11vnc monitor XRANDR
+ enable it with the [328]-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. If the
@@ -2967,7 +3020,7 @@ ied)
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
- [318]-padgeom option to make the region big enough to hold all resizes
+ [329]-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
@@ -2975,12 +3028,12 @@ ied)
specify "-xrandr exit" then all will be disconnected and x11vnc will
terminate.
- Q-63: Why is the view in my VNC viewer completely black? Or why is
+ Q-65: 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-64: I use Linux Virtual Consoles (VC's) to implement 'Fast User
+ Q-66: 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
@@ -3007,7 +3060,7 @@ ied)
x11vnc can poll it correctly), one can use the switchto(1) command,
e.g. "switchto 7" for VC #7.
- Q-65: I am using x11vnc where my local machine has "popup/hidden
+ Q-67: 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
@@ -3021,21 +3074,21 @@ ied)
[Misc: Clipboard, Beeps, Thanks, etc.]
- Q-66: Does the Clipboard/Selection get transferred between the
+ Q-68: Does the Clipboard/Selection get transferred between the
vncviewer and the X display?
As of Jan/2004 in the libvncserver CVS 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 [319]-nosel option. If you
+ the Clipboard/Selection exchanged use the [330]-nosel option. If you
don't want the PRIMARY selection to be polled for changes use the
- [320]-noprimary option.
+ [331]-noprimary 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-67: Why don't I hear the "Beeps" in my X session (e.g. when typing
+ Q-69: Why don't I hear the "Beeps" in my X session (e.g. when typing
tput bel in an xterm)?
As of Dec/2003 in the libvncserver CVS "Beep" XBell events are tracked
@@ -3043,18 +3096,18 @@ ied)
not on by default 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 [321]-nobell option. If
+ If you don't want to hear the beeps use the [332]-nobell option. If
you want to hear the audio from the remote applications, consider
trying a redirector such as esd.
- Q-68: Thanks for your program and for your help! Can I make a
+ Q-70: 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!
- Click on the PayPal button below.
+ Click on the PayPal button below for more info.
Also, in general I always enjoy hearing from x11vnc users, how they
use it, what new features they would like, etc. Please send me an
- [322]email.
+ [333]email!
[PayPal]
@@ -3092,8 +3145,8 @@ References
30. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
31. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
32. http://sourceforge.net/projects/libvncserver/
- 33. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=292078
- 34. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=292078
+ 33. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=307884
+ 34. http://sourceforge.net/project/shownotes.php?group_id=32584&release_id=307884
35. http://www.karlrunge.com/x11vnc/x11vnc.c
36. http://www.karlrunge.com/x11vnc/tkx11vnc.h
37. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
@@ -3121,267 +3174,278 @@ References
59. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
60. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
61. mailto:xvml@karlrunge.com
- 62. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
- 63. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 64. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
- 65. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
- 66. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
- 67. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
- 68. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
- 69. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
- 70. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
- 71. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
- 72. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
- 73. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 74. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
- 75. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
- 76. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
- 77. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
- 78. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 79. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 80. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
- 81. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
- 82. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 83. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 84. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
- 85. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
- 86. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
- 87. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 88. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
- 89. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
- 90. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
- 91. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
- 92. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
- 93. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
- 94. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
- 95. http://www.karlrunge.com/x11vnc/index.html#faq-service
- 96. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 97. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 98. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
- 99. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
- 100. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 101. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
- 102. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
- 103. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
- 104. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
- 105. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
- 106. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
- 107. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 108. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
- 109. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
- 110. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
- 111. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
- 112. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 113. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 114. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
- 115. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
- 116. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
- 117. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
- 118. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
- 119. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
- 120. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 121. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
- 122. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
- 123. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
- 124. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
- 125. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
- 126. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
- 127. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
- 128. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
- 129. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
- 130. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 131. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 132. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 134. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 135. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
- 136. http://www.karlrunge.com/x11vnc/index.html#building
- 137. http://www.karlrunge.com/x11vnc/index.html#faq-build
- 138. http://packages.debian.org/x11vnc
- 139. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
- 140. http://dag.wieers.com/packages/x11vnc/
- 141. http://www.sunfreeware.com/
- 142. http://www.bell-labs.com/project/wwexptools/packages.html
- 143. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
- 144. http://www.karlrunge.com/x11vnc/bins
- 145. http://www.tightvnc.com/download.html
- 146. http://www.realvnc.com/download-free.html
- 147. http://sourceforge.net/projects/cotvnc/
- 148. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
- 149. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 150. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 153. http://www.karlrunge.com/x11vnc/x11vnc.c
- 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe
- 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
- 156. http://fredrik.hubbe.net/x2vnc.html
- 157. http://www.hubbe.net/~hubbe/win2vnc.html
- 158. http://www.deboer.gmxhome.de/
- 159. http://sourceforge.net/projects/win2vnc/
- 160. http://fredrik.hubbe.net/x2vnc.html
- 161. http://freshmeat.net/projects/x2x/
- 162. http://ftp.digital.com/pub/Digital/SRC/x2x/
- 163. http://zapek.com/software/zvnc/
- 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
- 165. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
- 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
- 167. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
- 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 170. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 62. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 63. http://www.karlrunge.com/x11vnc/index.html#faq-xperms
+ 64. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 65. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build
+ 66. http://www.karlrunge.com/x11vnc/index.html#faq-binaries
+ 67. http://www.karlrunge.com/x11vnc/index.html#faq-viewer-download
+ 68. http://www.karlrunge.com/x11vnc/index.html#faq-cmdline-opts
+ 69. http://www.karlrunge.com/x11vnc/index.html#faq-config-file
+ 70. http://www.karlrunge.com/x11vnc/index.html#faq-quiet-bg
+ 71. http://www.karlrunge.com/x11vnc/index.html#faq-sigpipe
+ 72. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc
+ 73. http://www.karlrunge.com/x11vnc/index.html#faq-win2vnc-8bpp
+ 74. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
+ 75. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 76. http://www.karlrunge.com/x11vnc/index.html#faq-windowid
+ 77. http://www.karlrunge.com/x11vnc/index.html#faq-transients-id
+ 78. http://www.karlrunge.com/x11vnc/index.html#faq-24bpp
+ 79. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 80. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 81. http://www.karlrunge.com/x11vnc/index.html#faq-stop-bg
+ 82. http://www.karlrunge.com/x11vnc/index.html#faq-remote_control
+ 83. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 84. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 85. http://www.karlrunge.com/x11vnc/index.html#faq-input-opt
+ 86. http://www.karlrunge.com/x11vnc/index.html#faq-forever-shared
+ 87. http://www.karlrunge.com/x11vnc/index.html#faq-allow-opt
+ 88. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 89. http://www.karlrunge.com/x11vnc/index.html#faq-listen-interface
+ 90. http://www.karlrunge.com/x11vnc/index.html#faq-listen-localhost
+ 91. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-unix
+ 92. http://www.karlrunge.com/x11vnc/index.html#faq-ssh-putty
+ 93. http://www.karlrunge.com/x11vnc/index.html#faq-accept-opt
+ 94. http://www.karlrunge.com/x11vnc/index.html#faq-unix-passwords
+ 95. http://www.karlrunge.com/x11vnc/index.html#faq-users-opt
+ 96. http://www.karlrunge.com/x11vnc/index.html#faq-blockdpy
+ 97. http://www.karlrunge.com/x11vnc/index.html#faq-gone-lock
+ 98. http://www.karlrunge.com/x11vnc/index.html#faq-service
+ 99. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 100. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 101. http://www.karlrunge.com/x11vnc/index.html#faq-java-http
+ 102. http://www.karlrunge.com/x11vnc/index.html#faq-reverse-connect
+ 103. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 104. http://www.karlrunge.com/x11vnc/index.html#faq-less-resource
+ 105. http://www.karlrunge.com/x11vnc/index.html#faq-more-resource
+ 106. http://www.karlrunge.com/x11vnc/index.html#faq-slow-link
+ 107. http://www.karlrunge.com/x11vnc/index.html#faq-pointer-mode
+ 108. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-shape
+ 109. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha
+ 110. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 111. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-arrow
+ 112. http://www.karlrunge.com/x11vnc/index.html#faq-cursor-positions
+ 113. http://www.karlrunge.com/x11vnc/index.html#faq-buttonmap-opt
+ 114. http://www.karlrunge.com/x11vnc/index.html#faq-altgr
+ 115. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 116. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 117. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys
+ 118. http://www.karlrunge.com/x11vnc/index.html#faq-repeated-keys-still
+ 119. http://www.karlrunge.com/x11vnc/index.html#faq-remap-opt
+ 120. http://www.karlrunge.com/x11vnc/index.html#faq-sun-alt-meta
+ 121. http://www.karlrunge.com/x11vnc/index.html#faq-remap-button-click
+ 122. http://www.karlrunge.com/x11vnc/index.html#faq-scrollbars
+ 123. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 124. http://www.karlrunge.com/x11vnc/index.html#faq-xinerama
+ 125. http://www.karlrunge.com/x11vnc/index.html#faq-multi-screen
+ 126. http://www.karlrunge.com/x11vnc/index.html#faq-xrandr
+ 127. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen
+ 128. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc
+ 129. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars
+ 130. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard
+ 131. http://www.karlrunge.com/x11vnc/index.html#faq-beeps
+ 132. http://www.karlrunge.com/x11vnc/index.html#faq-thanks
+ 133. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 134. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 135. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 136. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 137. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 138. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html
+ 139. http://www.karlrunge.com/x11vnc/index.html#building
+ 140. http://www.karlrunge.com/x11vnc/index.html#faq-build
+ 141. http://packages.debian.org/x11vnc
+ 142. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc
+ 143. http://dag.wieers.com/packages/x11vnc/
+ 144. http://www.sunfreeware.com/
+ 145. http://www.bell-labs.com/project/wwexptools/packages.html
+ 146. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding
+ 147. http://www.karlrunge.com/x11vnc/bins
+ 148. http://www.tightvnc.com/download.html
+ 149. http://www.realvnc.com/download-free.html
+ 150. http://sourceforge.net/projects/cotvnc/
+ 151. http://www.karlrunge.com/x11vnc/x11vnc_opts.html
+ 152. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 153. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 154. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 155. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 156. http://www.karlrunge.com/x11vnc/x11vnc.c
+ 157. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe
+ 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb
+ 159. http://fredrik.hubbe.net/x2vnc.html
+ 160. http://www.hubbe.net/~hubbe/win2vnc.html
+ 161. http://www.deboer.gmxhome.de/
+ 162. http://sourceforge.net/projects/win2vnc/
+ 163. http://fredrik.hubbe.net/x2vnc.html
+ 164. http://freshmeat.net/projects/x2x/
+ 165. http://ftp.digital.com/pub/Digital/SRC/x2x/
+ 166. http://zapek.com/software/zvnc/
+ 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual
+ 168. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap
+ 169. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor
+ 170. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp
171. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 172. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 172. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
173. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
- 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
- 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
- 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 179. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
- 180. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
- 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
- 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
- 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
- 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
- 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
- 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
- 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 192. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
- 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
- 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
- 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
- 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
- 200. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 201. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
- 202. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
- 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
- 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 205. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
- 206. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 207. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 208. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
- 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
- 212. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
- 216. ftp://ftp.x.org/
- 217. http://www.karlrunge.com/x11vnc/dtVncPopup
- 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
- 220. http://www.karlrunge.com/x11vnc/index.html#tunnelling
- 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
- 223. http://www.karlrunge.com/x11vnc/blockdpy.c
- 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
- 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
- 227. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 228. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
- 229. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
- 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 231. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
- 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
- 233. http://www.jirka.org/gdm-documentation/x241.html
- 234. http://www.karlrunge.com/x11vnc/x11vnc_loop
- 235. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
- 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
- 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
- 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
- 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
- 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
- 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
- 242. http://www.karlrunge.com/x11vnc/shm_clear
- 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 245. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
- 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
- 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
- 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
- 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 253. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
- 254. http://www.tightvnc.com/
- 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
- 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 174. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 175. http://www.karlrunge.com/x11vnc/index.html#faq-overlays
+ 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid
+ 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display
+ 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder
+ 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 182. http://www.karlrunge.com/x11vnc/index.html#xauth_pain
+ 183. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg
+ 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods
+ 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys
+ 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote
+ 191. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query
+ 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui
+ 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd
+ 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 195. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd
+ 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd
+ 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input
+ 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever
+ 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared
+ 203. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 204. http://www.karlrunge.com/x11vnc/index.html#faq-passwd
+ 205. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile
+ 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 208. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers
+ 209. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 212. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 213. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen
+ 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow
+ 217. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 218. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 219. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth
+ 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile
+ 223. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly
+ 227. ftp://ftp.x.org/
+ 228. http://www.karlrunge.com/x11vnc/dtVncPopup
+ 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost
+ 231. http://www.karlrunge.com/x11vnc/index.html#tunnelling
+ 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users
+ 234. http://www.karlrunge.com/x11vnc/blockdpy.c
+ 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept
+ 236. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone
+ 238. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 239. http://www.karlrunge.com/x11vnc/index.html#faq-inetd
+ 240. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop
+ 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 242. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris
+ 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o
+ 244. http://www.jirka.org/gdm-documentation/x241.html
+ 245. http://www.karlrunge.com/x11vnc/x11vnc_loop
+ 246. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth
+ 247. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd
+ 248. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q
+ 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth
+ 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir
+ 251. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect
+ 252. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect
+ 253. http://www.karlrunge.com/x11vnc/shm_clear
+ 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 256. http://www.karlrunge.com/x11vnc/index.html#faq-noshm
+ 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap
258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
- 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
- 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
- 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
- 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
- 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
- 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
- 270. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
- 271. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
- 272. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
- 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
- 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
- 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
- 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
- 278. http://www.tightvnc.com/
- 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
- 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
- 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
- 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
- 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
- 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
- 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 287. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
- 288. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 292. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
- 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
- 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
- 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
- 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
- 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
- 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
- 303. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
- 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
- 308. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
- 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
- 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
- 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
- 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
- 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
- 314. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
- 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
- 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
- 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
- 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
- 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
- 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
- 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
- 322. mailto:xvml@karlrunge.com
+ 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads
+ 262. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid
+ 265. http://www.tightvnc.com/
+ 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive
+ 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs
+ 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait
+ 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer
+ 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id
+ 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging
+ 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode
+ 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor
+ 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay
+ 281. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode
+ 282. http://www.karlrunge.com/x11vnc/index.html#solaris10-build
+ 283. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks
+ 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut
+ 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac
+ 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove
+ 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend
+ 289. http://www.tightvnc.com/
+ 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor
+ 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos
+ 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos
+ 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape
+ 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 295. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer
+ 296. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap
+ 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 298. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless
+ 299. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 303. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak
+ 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard
+ 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak
+ 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb
+ 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes
+ 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms
+ 312. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat
+ 314. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager
+ 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap
+ 319. http://www.karlrunge.com/x11vnc/index.html#faq-scaling
+ 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale
+ 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport
+ 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout
+ 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama
+ 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer
+ 325. http://www.karlrunge.com/x11vnc/index.html#faq-solshm
+ 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile
+ 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm
+ 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr
+ 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom
+ 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel
+ 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary
+ 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell
+ 333. mailto:xvml@karlrunge.com
=======================================================================
@@ -3394,7 +3458,8 @@ 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.7.1 lastmod: 2005-02-23
+x11vnc: allow VNC connections to real X11 displays. 0.7.2pre lastmod: 2005-03-0
+4
x11vnc options:
-display disp -auth file
@@ -3464,12 +3529,15 @@ libvncserver options:
-httpport portnum use portnum for http connection
-enablehttpproxy enable http proxy support
-progressive height enable progressive updating for slow links
+-listen ipaddr listen for connections only on network interface with
+ addr ipaddr. '-listen localhost' and hostname work too.
% x11vnc -help
-x11vnc: allow VNC connections to real X11 displays. 0.7.1 lastmod: 2005-02-23
+x11vnc: allow VNC connections to real X11 displays. 0.7.2pre lastmod: 2005-03-0
+4
Typical usage is:
@@ -3635,7 +3703,19 @@ Options:
file containing addresses or prefixes that is re-read
each time a new client connects. Lines can be commented
out with the "#" character in the usual way.
--localhost Same as -allow 127.0.0.1
+-localhost Same as "-allow 127.0.0.1".
+
+ Note: if you want to restrict which network interface
+ x11vnc listens on, see the -listen option below.
+ E.g. "-listen localhost" or "-listen 192.168.3.21".
+ As a special case, the option "-localhost" implies
+ "-listen localhost".
+
+ For non-localhost -listen usage, if you use the remote
+ control mechanism (-R) to change the -listen interface
+ you may need to manually adjust the -allow list (and
+ vice versa) to avoid situations where no connections
+ (or too many) are allowed.
-input string Fine tuning of allowed user input. If "string" does
not contain a comma "," the tuning applies only to
@@ -3787,7 +3867,7 @@ Options:
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 difference searching
+ 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
@@ -4348,6 +4428,7 @@ Options:
use "-host" to delete a single host
localhost enable -localhost mode
nolocalhost disable -localhost mode
+ listen:str set -listen to str, empty to disable.
input:str set -input to "str", empty to disable.
client_input:str set the K, M, B -input on a per-client
basis. select which client as for
@@ -4515,7 +4596,7 @@ Options:
overlay_nocursor visual scale viewonly noviewonly
shared noshared forever noforever once timeout deny
lock nodeny unlock connect allowonce allow localhost
- nolocalhost accept gone shm noshm flipbyteorder
+ nolocalhost listen accept gone shm noshm flipbyteorder
noflipbyteorder onetile noonetile solid_color solid
nosolid blackout xinerama noxinerama xrandr noxrandr
xrandr_mode padgeom quiet q noquiet modtweak nomodtweak
@@ -4617,6 +4698,8 @@ These options are passed to libvncserver:
-httpport portnum use portnum for http connection
-enablehttpproxy enable http proxy support
-progressive height enable progressive updating for slow links
+-listen ipaddr listen for connections only on network interface with
+ addr ipaddr. '-listen localhost' and hostname work too.
Pretty wild huh? [1]Contact me if you have any questions or problems.
diff --git a/x11vnc/tkx11vnc b/x11vnc/tkx11vnc
index a592f5c..e43b73c 100755
--- a/x11vnc/tkx11vnc
+++ b/x11vnc/tkx11vnc
@@ -49,6 +49,7 @@ catch {rename send {}}
# be the same after the remote command)
# G means gui internal item
# F means can be set via file browse
+# D means for simple gui
# -C:val1,... means it will be a checkbox (radio button)
# the "-" means no other options follow
# 0 means to skip the item.
@@ -87,7 +88,7 @@ Clients
vncconnect
-- D
=D http
- =F httpdir:
+ httpdir:
httpport:
enablehttpproxy
@@ -185,8 +186,9 @@ Permissions
=SQA deny_all
--
=DFP allow:
- localhost
+ =D localhost
=RA allowonce:
+ listen:
-- D
=RA noremote
--
diff --git a/x11vnc/tkx11vnc.h b/x11vnc/tkx11vnc.h
index e758bf7..2ecfdbe 100644
--- a/x11vnc/tkx11vnc.h
+++ b/x11vnc/tkx11vnc.h
@@ -55,6 +55,7 @@
"# be the same after the remote command)\n"
"# G means gui internal item\n"
"# F means can be set via file browse\n"
+"# D means for simple gui\n"
"# -C:val1,... means it will be a checkbox (radio button)\n"
"# the \"-\" means no other options follow\n"
"# 0 means to skip the item.\n"
@@ -93,7 +94,7 @@
" vncconnect\n"
" -- D\n"
" =D http\n"
-" =F httpdir:\n"
+" httpdir:\n"
" httpport:\n"
" enablehttpproxy\n"
"\n"
@@ -191,8 +192,9 @@
" =SQA deny_all\n"
" --\n"
" =DFP allow:\n"
-" localhost\n"
+" =D localhost\n"
" =RA allowonce:\n"
+" listen:\n"
" -- D\n"
" =RA noremote\n"
" --\n"
diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1
index 8df6029..3c29d76 100644
--- a/x11vnc/x11vnc.1
+++ b/x11vnc/x11vnc.1
@@ -1,8 +1,8 @@
.\" This file was automatically generated from x11vnc -help output.
-.TH X11VNC "1" "February 2005" "x11vnc " "User Commands"
+.TH X11VNC "1" "March 2005" "x11vnc " "User Commands"
.SH NAME
x11vnc - allow VNC connections to real X11 displays
- version: 0.7.1, lastmod: 2005-02-23
+ version: 0.7.2pre, lastmod: 2005-03-04
.SH SYNOPSIS
.B x11vnc
[OPTION]...
@@ -248,7 +248,19 @@ out with the "#" character in the usual way.
.PP
\fB-localhost\fR
.IP
-Same as \fB-allow\fR 127.0.0.1
+Same as "\fB-allow\fR \fI127.0.0.1\fR".
+.IP
+Note: if you want to restrict which network interface
+x11vnc listens on, see the \fB-listen\fR option below.
+E.g. "\fB-listen\fR \fIlocalhost\fR" or "\fB-listen\fR \fI192.168.3.21\fR".
+As a special case, the option "\fB-localhost\fR" implies
+"\fB-listen\fR \fIlocalhost\fR".
+.IP
+For non-localhost \fB-listen\fR usage, if you use the remote
+control mechanism (-R) to change the \fB-listen\fR interface
+you may need to manually adjust the \fB-allow\fR list (and
+vice versa) to avoid situations where no connections
+(or too many) are allowed.
.PP
\fB-input\fR \fIstring\fR
.IP
@@ -438,7 +450,7 @@ 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 difference searching
+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
@@ -1202,6 +1214,8 @@ localhost enable \fB-localhost\fR mode
.IP
nolocalhost disable \fB-localhost\fR mode
.IP
+listen:str set \fB-listen\fR to str, empty to disable.
+.IP
input:str set \fB-input\fR to "str", empty to disable.
.IP
client_input:str set the K, M, B \fB-input\fR on a per-client
@@ -1484,7 +1498,7 @@ nooverlay_nocursor nooverlay_cursor nooverlay_yescursor
overlay_nocursor visual scale viewonly noviewonly
shared noshared forever noforever once timeout deny
lock nodeny unlock connect allowonce allow localhost
-nolocalhost accept gone shm noshm flipbyteorder
+nolocalhost listen accept gone shm noshm flipbyteorder
noflipbyteorder onetile noonetile solid_color solid
nosolid blackout xinerama noxinerama xrandr noxrandr
xrandr_mode padgeom quiet q noquiet modtweak nomodtweak
@@ -1634,6 +1648,11 @@ enable http proxy support
\fB-progressive\fR \fIheight\fR
.IP
enable progressive updating for slow links
+.PP
+\fB-listen\fR \fIipaddr\fR
+.IP
+listen for connections only on network interface with
+addr ipaddr. '-listen localhost' and hostname work too.
.SH "FILES"
.IR $HOME/.x11vncrc ,
.IR $HOME/.Xauthority
diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c
index 27148fc..f10b683 100644
--- a/x11vnc/x11vnc.c
+++ b/x11vnc/x11vnc.c
@@ -1,7 +1,7 @@
/*
* x11vnc.c: a VNC server for X displays.
*
- * Copyright (c) 2002-2004 Karl J. Runge <runge@karlrunge.com>
+ * Copyright (c) 2002-2005 Karl J. Runge <runge@karlrunge.com>
* All rights reserved.
*
* This is free software; you can redistribute it and/or modify
@@ -27,17 +27,22 @@
* krfb, the KDE desktopsharing project (Tim Jansen)
*
* The primary goal of this program is to create a portable and simple
- * command-line server utility that allows a VNC viewer to connect to an
- * actual X display (as the above do). The only non-standard dependency
- * of this program is the static library libvncserver.a (although in
- * some environments libjpeg.so may not be readily available and needs
- * to be installed, it may be found at ftp://ftp.uu.net/graphics/jpeg/).
- * To increase portability it is written in plain C.
+ * command-line server utility that allows a VNC viewer to connect
+ * to an actual X display (as the above do). The only non-standard
+ * dependency of this program is the static library libvncserver.a.
+ * Although in some environments libjpeg.so or libz.so may not be
+ * readily available and needs to be installed, they may be found
+ * at ftp://ftp.uu.net/graphics/jpeg/ and http://www.gzip.org/zlib/,
+ * respectively. To increase portability it is written in plain C.
*
- * The next goal is to improve performance and interactive response.
+ * Another goal is to improve performance and interactive response.
* The algorithm of x0rfbserver was used as a base. Additional heuristics
* are also applied (currently there are a bit too many of these...)
*
+ * Another goal is to add many features that enable and incourage creative
+ * Ausage and application of the tool. pologies for the large number
+ * Aof options!
+ *
* To build:
*
* Obtain the libvncserver package (http://libvncserver.sourceforge.net).
@@ -53,12 +58,13 @@
* Known shortcomings:
*
* The screen updates are good, but of course not perfect since the X
- * display must be continuously polled and read for changes (as opposed to
- * receiving a change callback from the X server, if that were generally
- * possible... (Update: this seems to be handled now with the X DAMAGE
- * extension, but unfortunately that doesn't seem to address the slow
- * read from the video h/w). So, e.g., opaque moves and similar window
- * activity can be very painful; one has to modify one's behavior a bit.
+ * display must be continuously polled and read for changes and this is
+ * slow for most hardware. This can be contrasted with receiving a change
+ * callback from the X server, if that were generally possible... (Update:
+ * this seems to be handled now with the X DAMAGE extension, but
+ * unfortunately that doesn't seem to address the slow read from the
+ * video h/w. So, e.g., opaque moves and similar window activity can
+ * be very painful; one has to modify one's behavior a bit.
*
* General audio at the remote display is lost unless one separately
* sets up some audio side-channel such as esd.
@@ -73,7 +79,10 @@
* the -cursor option. Further, if -cursorX or -X is used, a trick
* is done to at least show the root window cursor vs non-root cursor.
* (perhaps some heuristic can be done to further distinguish cases...,
- * currently -cursor some is a first hack at this)
+ * currently "-cursor some" is a first hack at this)
+ *
+ * Under XFIXES mode for showing the cursor shape, the cursor may be
+ * poorly approximated if it has transparency.
*
* Windows using visuals other than the default X visual may have
* their colors messed up. When using 8bpp indexed color, the colormap
@@ -83,9 +92,16 @@
* 24 visuals will incorrectly display windows using the non-default one.
* On Sun and Sgi hardware we can to work around this with -overlay.
*
- * Feature -id <windowid> can be picky: it can crash for things like the
- * window not sufficiently mapped into server memory, etc. SaveUnders
- * menus, popups, etc will not be seen.
+ * Feature -id <windowid> can be picky: it can crash for things like
+ * the window not sufficiently mapped into server memory, etc (Update:
+ * we now use the -xrandr mechanisms to trap errors for this mode).
+ * SaveUnders menus, popups, etc will not be seen.
+ *
+ * Under some situations the keysym unmapping is not correct, especially
+ * if the two keyboards correspond to different languages. The -modtweak
+ * option is the default and corrects most problems. One can use the
+ * -xkb option to try to use the XKEYBOARD extension to clear up any
+ * remaining problems.
*
* Occasionally, a few tile updates can be missed leaving a patch of
* color that needs to be refreshed. This may only be when threaded,
@@ -113,15 +129,23 @@
/*
* if you are inserting this file, x11vnc.c into an old CVS tree you
- * may need to set OLD_TREE to 1.
+ * may need to set OLD_TREE to 1. See below for LibVNCServer 0.7 tips.
*/
+
#define OLD_TREE 0
#if OLD_TREE
/*
- * if have a very old tree and get errors these may be needed as well:
+ * if you have a very old tree (LibVNCServer 0.6) and get errors these may
+ * be need to be uncommented. LibVNCServer <= 0.5 is no longer supported.
+ * note the maxRectsPerUpdate below is a hack that may break some usage.
#define oldCursorX cursorX
#define oldCursorY cursorY
+#define thisHost rfbThisHost
+#define framebufferUpdateMessagesSent rfbFramebufferUpdateMessagesSent
+#define bytesSent rfbBytesSent
+#define rawBytesEquivalent rfbRawBytesEquivalent
+#define progressiveSliceHeight maxRectsPerUpdate
*/
/*
@@ -189,8 +213,29 @@
#else
#define RFBUNDRAWCURSOR(s)
#endif
+/*
+ * To get a clean build in a LibVNCServer 0.7 source tree no need for
+ * OLD_TREE, you just need to either download the forgotten tkx11vnc.h
+ * file or run:
+ *
+ * echo 'char gui_code[] = "";' > tkx11vnc.h
+ *
+ * (this disables the gui) and uncomment this line:
+#define rfbSetCursor(a, b) rfbSetCursor((a), (b), FALSE)
+ */
+
+/*
+ * To get a clean build on LibVNCServer 0.7.1 no need for OLD_TREE,
+ * just uncomment this line (note the maxRectsPerUpdate below is a hack
+ * that may break some usage):
+ *
+#define listenInterface maxRectsPerUpdate
+ */
#if LIBVNCSERVER_HAVE_XSHM
+# if defined(__hpux) && defined(__ia64) /* something weird on hp/itanic */
+# undef _INCLUDE_HPUX_SOURCE
+# endif
#include <sys/ipc.h>
#include <sys/shm.h>
#include <X11/extensions/XShm.h>
@@ -290,7 +335,7 @@ static int xdamage_base_event_type;
#endif
/* date +'lastmod: %Y-%m-%d' */
-char lastmod[] = "0.7.1 lastmod: 2005-02-23";
+char lastmod[] = "0.7.2pre lastmod: 2005-03-04";
/* X display info */
@@ -579,6 +624,7 @@ int safe_remote_only = 0; /* -safer, -unsafe */
int started_as_root = 0;
char *users_list = NULL; /* -users */
char *allow_list = NULL; /* for -allow and -localhost */
+char *listen_str = NULL;
char *allow_once = NULL; /* one time -allow */
char *accept_cmd = NULL; /* for -accept */
char *gone_cmd = NULL; /* for -gone */
@@ -1688,7 +1734,7 @@ typedef unsigned int in_addr_t;
in_addr_t iaddr;
iaddr = inet_addr(ip);
- if (iaddr == INADDR_NONE) {
+ if (iaddr == htonl(INADDR_NONE)) {
return strdup("unknown");
}
@@ -7140,7 +7186,7 @@ void reset_httpport(int old, int new) {
close(screen->httpListenSock);
}
rfbLog("reset_httpport: setting httpport %d -> %d.\n",
- old, hp);
+ old == -1 ? hp : old, hp);
rfbHttpInitSockets(screen);
}
}
@@ -7171,7 +7217,7 @@ void reset_rfbport(int old, int new) {
}
rfbLog("reset_rfbport: setting rfbport %d -> %d.\n",
- old, rp);
+ old == -1 ? rp : old, rp);
rfbInitSockets(screen);
maxfd = screen->maxFd;
@@ -7731,7 +7777,9 @@ char *process_remote_cmd(char *cmd, int stringonly) {
char *before, *old;
if (query) {
int state = 0;
- if (allow_list && !strcmp(allow_list, "127.0.0.1")) {
+ char *s = allow_list;
+ if (s && (!strcmp(s, "127.0.0.1") ||
+ !strcmp(s, "localhost"))) {
state = 1;
}
snprintf(buf, bufn, "ans=%s:%d", p, state);
@@ -7753,11 +7801,26 @@ char *process_remote_cmd(char *cmd, int stringonly) {
}
if (old) free(old);
free(before);
+
+ if (listen_str) {
+ free(listen_str);
+ }
+ listen_str = strdup("localhost");
+
+ screen->listenInterface = htonl(INADDR_LOOPBACK);
+ rfbLog("listening on loopback network only.\n");
+ rfbLog("allow list is: '%s'\n", NONUL(allow_list));
+ reset_rfbport(-1, screen->port);
+ if (screen->httpListenSock > -1) {
+ reset_httpport(-1, screen->httpPort);
+ }
} else if (!strcmp(p, "nolocalhost")) {
char *before, *old;
if (query) {
int state = 0;
- if (allow_list && !strcmp(allow_list, "127.0.0.1")) {
+ char *s = allow_list;
+ if (s && (!strcmp(s, "127.0.0.1") ||
+ !strcmp(s, "localhost"))) {
state = 1;
}
snprintf(buf, bufn, "ans=%s:%d", p, !state);
@@ -7780,6 +7843,106 @@ char *process_remote_cmd(char *cmd, int stringonly) {
if (old) free(old);
free(before);
+ if (listen_str) {
+ free(listen_str);
+ }
+ listen_str = NULL;
+
+ screen->listenInterface = htonl(INADDR_ANY);
+ rfbLog("listening on ALL network interfaces.\n");
+ rfbLog("allow list is: '%s'\n", NONUL(allow_list));
+ reset_rfbport(-1, screen->port);
+ if (screen->httpListenSock > -1) {
+ reset_httpport(-1, screen->httpPort);
+ }
+
+ } else if (strstr(p, "listen") == p) {
+ char *before;
+ int ok, mod = 0;
+
+ COLON_CHECK("listen:")
+ if (query) {
+ snprintf(buf, bufn, "ans=%s%s%s", p, co,
+ NONUL(listen_str));
+ goto qry;
+ }
+ if (listen_str) {
+ before = strdup(listen_str);
+ } else {
+ before = strdup("");
+ }
+ p += strlen("listen:");
+
+ listen_str = strdup(p);
+
+ if (strcmp(before, listen_str)) {
+ rfbLog("process_remote_cmd: modified listen_str:\n");
+ rfbLog(" from: \"%s\"\n", before);
+ rfbLog(" to: \"%s\"\n", listen_str);
+ mod = 1;
+ }
+
+ ok = 1;
+ if (listen_str == NULL || *listen_str == '\0' ||
+ !strcmp(listen_str, "any")) {
+ screen->listenInterface = htonl(INADDR_ANY);
+ } else if (!strcmp(listen_str, "localhost")) {
+ screen->listenInterface = htonl(INADDR_LOOPBACK);
+ } else {
+ struct hostent *hp;
+ in_addr_t iface = inet_addr(listen_str);
+ if (iface == htonl(INADDR_NONE)) {
+ if (!(hp = gethostbyname(listen_str))) {
+ ok = 0;
+ } else {
+ iface = *(unsigned long *)hp->h_addr;
+ }
+ }
+ if (ok) {
+ screen->listenInterface = iface;
+ }
+ }
+
+ if (ok && mod) {
+ int is_loopback = 0;
+ in_addr_t iface = screen->listenInterface;
+
+ if (allow_list) {
+ if (!strcmp(allow_list, "127.0.0.1") ||
+ !strcmp(allow_list, "localhost")) {
+ is_loopback = 1;
+ }
+ }
+ if (iface != htonl(INADDR_LOOPBACK)) {
+ if (is_loopback) {
+ rfbLog("re-setting -allow list to all "
+ "hosts for non-loopback listening.\n");
+ free(allow_list);
+ allow_list = NULL;
+ }
+ } else {
+ if (!is_loopback) {
+ if (allow_list) {
+ free(allow_list);
+ }
+ rfbLog("setting -allow list to 127.0.0.1\n");
+ allow_list = strdup("127.0.0.1");
+ }
+ }
+ }
+ if (ok) {
+ rfbLog("allow list is: '%s'\n", NONUL(allow_list));
+ reset_rfbport(-1, screen->port);
+ if (screen->httpListenSock > -1) {
+ reset_httpport(-1, screen->httpPort);
+ }
+ free(before);
+ } else {
+ rfbLog("bad listen string: %s\n", listen_str);
+ free(listen_str);
+ listen_str = before;
+ }
+
} else if (strstr(p, "accept") == p) {
COLON_CHECK("accept:")
if (query) {
@@ -16079,7 +16242,7 @@ void initialize_speeds(void) {
s = strdup("6,4,200");
} else if (!strcmp(speeds_str, "dsl")) {
s = strdup("6,100,50");
- } else if (!strcmp(speeds_str, "modem")) {
+ } else if (!strcmp(speeds_str, "lan")) {
s = strdup("6,5000,1");
} else {
s = strdup(speeds_str);
@@ -16556,7 +16719,19 @@ static void print_help(int mode) {
" file containing addresses or prefixes that is re-read\n"
" each time a new client connects. Lines can be commented\n"
" out with the \"#\" character in the usual way.\n"
-"-localhost Same as -allow 127.0.0.1\n"
+"-localhost Same as \"-allow 127.0.0.1\".\n"
+"\n"
+" Note: if you want to restrict which network interface\n"
+" x11vnc listens on, see the -listen option below.\n"
+" E.g. \"-listen localhost\" or \"-listen 192.168.3.21\".\n"
+" As a special case, the option \"-localhost\" implies\n"
+" \"-listen localhost\".\n"
+"\n"
+" For non-localhost -listen usage, if you use the remote\n"
+" control mechanism (-R) to change the -listen interface\n"
+" you may need to manually adjust the -allow list (and\n"
+" vice versa) to avoid situations where no connections\n"
+" (or too many) are allowed.\n"
"\n"
"-input string Fine tuning of allowed user input. If \"string\" does\n"
" not contain a comma \",\" the tuning applies only to\n"
@@ -16708,7 +16883,7 @@ static void print_help(int mode) {
" 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 difference searching\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"
@@ -17286,6 +17461,7 @@ static void print_help(int mode) {
" use \"-host\" to delete a single host\n"
" localhost enable -localhost mode\n"
" nolocalhost disable -localhost mode\n"
+" listen:str set -listen to str, empty to disable.\n"
" input:str set -input to \"str\", empty to disable.\n"
" client_input:str set the K, M, B -input on a per-client\n"
" basis. select which client as for\n"
@@ -17456,7 +17632,7 @@ static void print_help(int mode) {
" overlay_nocursor visual scale viewonly noviewonly\n"
" shared noshared forever noforever once timeout deny\n"
" lock nodeny unlock connect allowonce allow localhost\n"
-" nolocalhost accept gone shm noshm flipbyteorder\n"
+" nolocalhost listen accept gone shm noshm flipbyteorder\n"
" noflipbyteorder onetile noonetile solid_color solid\n"
" nosolid blackout xinerama noxinerama xrandr noxrandr\n"
" xrandr_mode padgeom quiet q noquiet modtweak nomodtweak\n"
@@ -17606,6 +17782,11 @@ void set_vnc_desktop_name(void) {
if (screen->port) {
char *host = this_host();
int lport = screen->port;
+ char *iface = listen_str;
+
+ if (iface != NULL && *iface != '\0' && strcmp(iface, "any")) {
+ host = iface;
+ }
if (host != NULL) {
/* note that vncviewer special cases 5900-5999 */
if (inetd) {
@@ -18159,7 +18340,7 @@ int main(int argc, char* argv[]) {
} else if (!strcmp(arg, "-?") || !strcmp(arg, "-opts")) {
print_help(1);
} else if (!strcmp(arg, "-V") || !strcmp(arg, "-version")) {
- fprintf(stderr, "x11vnc: %s\n", lastmod);
+ fprintf(stdout, "x11vnc: %s\n", lastmod);
exit(0);
} else if (!strcmp(arg, "-q") || !strcmp(arg, "-quiet")) {
quiet = 1;
@@ -18377,6 +18558,9 @@ int main(int argc, char* argv[]) {
if (!strcmp(arg, "-nevershared")) {
got_nevershared = 1;
}
+ if (!strcmp(arg, "-listen") && i < argc-1) {
+ listen_str = strdup(argv[i+1]);
+ }
/* otherwise copy it for libvncserver use below. */
if (argc_vnc < 100) {
argv_vnc[argc_vnc++] = strdup(arg);
@@ -18615,6 +18799,18 @@ int main(int argc, char* argv[]) {
}
}
+ /* tie together cases of -localhost vs. -listen localhost */
+ if (! listen_str) {
+ if (allow_list && !strcmp(allow_list, "127.0.0.1")) {
+ listen_str = strdup("localhost");
+ argv_vnc[argc_vnc++] = strdup("-listen");
+ argv_vnc[argc_vnc++] = strdup(listen_str);
+ }
+ } else if (!strcmp(listen_str, "localhost") ||
+ !strcmp(listen_str, "127.0.0.1")) {
+ allow_list = strdup("127.0.0.1");
+ }
+
if (! quiet) {
fprintf(stderr, "\n");
fprintf(stderr, "Settings:\n");
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-24 16:17:00 +0000