> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > I posted the other day with regard to the -localhost option only > taking effect on the 58## and 59## ports, but not 60##. I'm not > running a firewall, and consider my machine secure (enough) because > the only open port is ssh. I was surprised when I found Xvnc > with -localhost had opened a port to the world. I didn't get a > response, and had no luck on the TightVNC list either, so I started > digging through the code and found that the 60## socket appears to be > bound by the underlying X server in Xtransam.c. This is pretty > unfamiliar territory for me, so I was wondering if there is anyone on > this list that is familiar with the workings here? In particular > would it be possible to modify the X code to utilize the -localhost > option? Any guidance would be most appreciated. >
As far as I know, the X11 part of Xvnc uses the X11 security. There is way to much to discuss on X11 security. You can start on that by looking at the manuals of xauth and xhost (`man xauth`, `man xhost`). See also the -ac option to Xvnc: That toggles between 'all open' and 'all closed' (similar to `xhost +` and `xhost -`. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
