x11vnc: fix keycode and other remote control actions under

        DIRECT: with an extra XFlush and other safety measures.
        fflush(stderr) much in su_verify.  Make the -unixpw env. vars
        UNIXPW_DISABLE_SSL and UNIXPW_DISABLE_LOCALHOST work correctly.
        Make -loopbg actually imply -bg.

1 files changed, 15 insertions, 11 deletions

diff --git a/x11vnc/help.c b/x11vnc/help.c
index 585da81..db690e4 100644
--- a/x11vnc/help.c
+++ b/x11vnc/help.c
@@ -913,20 +913,24 @@ void print_help(int mode) {
 "                       environment variables before starting x11vnc:\n"
 "\n"
 "                       Set UNIXPW_DISABLE_SSL=1 to disable requiring either\n"
-"                       -ssl or -stunnel.  Evidently you will be using a\n"
-"                       different method to encrypt the data between the\n"
-"                       vncviewer and x11vnc: perhaps ssh(1) or an IPSEC VPN.\n"
-"\n"
-"                       Note that use of -localhost with ssh(1) is roughly\n"
-"                       the same as requiring a Unix user login (since a Unix\n"
-"                       password or the user's public key authentication is\n"
-"                       used by sshd on the machine where x11vnc runs and only\n"
-"                       local connections from that machine are accepted).\n"
+"                       -ssl or -stunnel (as under SSH_CONNECTION.)  Evidently\n"
+"                       you will be using a different method to encrypt the\n"
+"                       data between the vncviewer and x11vnc: perhaps ssh(1)\n"
+"                       or an IPSEC VPN. -localhost is still enforced (however,\n"
+"                       see the next paragraph.)\n"
 "\n"
 "                       Set UNIXPW_DISABLE_LOCALHOST=1 to disable the -localhost\n"
-"                       requirement in Method 2).  One should never do this\n"
+"                       requirement in -unixpw modes.  One should never do this\n"
 "                       (i.e. allow the Unix passwords to be sniffed on the\n"
-"                       network.)\n"
+"                       network.)  This also disables the localhost requirement\n"
+"                       for reverse connections (see below.)\n"
+"\n"
+"                       Note that use of -localhost with ssh(1) (and no -unixpw)\n"
+"                       is roughly the same as requiring a Unix user login\n"
+"                       (since a Unix password or the user's public key\n"
+"                       authentication is used by sshd on the machine where\n"
+"                       x11vnc runs and only local connections from that machine\n"
+"                       are accepted).\n"
 "\n"
 "                       Regarding reverse connections (e.g. -R connect:host\n"
 "                       and -connect host), when the -localhost constraint is\n"