devzero@xxxxxx wrote:
You can use the '-nolisten tcp' option suppress listening on tcp
completely in your case.
ok - thanks - but how should anything connect then to a listening socket, if it isn`t able to talk
to the xserver via bsd socket or whatever other method(i don`t know)?
-nolisten tcp only disables tcp sockets - you can still connect to :0
using the Unix domain socket, and then let ssh forwarding take care of
all remote connections.
i`m system administrator and most "well designed" server-apps support a configure option to bind to specific interfaces. apache, mysql, samba - i can let them all run on specific interface:port ..... so should X, IMHO
if this feature isn`t already "inside" X - hasn`t this been a feature request already?
i think, it`s an essential feature!
You can get similar effects via the above mentioned -nolisten/ssh combo,
or with a firewall, so it's not been high enough priority for anyone to
write the code to do that. (I did actually put code like this in xdm for
controlling which interfaces to listen on for XDMCP connections
when I was doing the IPv6 work, but that only deals with XDMCP protocol
connections, not the X protocol itself.)
Also, most of the apps that support this are designed to run on machines
that connect to both internal and external networks, and those machines
often don't run X.
--
-Alan Coopersmith- alan.coopersmith@xxxxxxx
Sun Microsystems, Inc. - Sun Software Group
User Experience Engineering: G11N: X Window System
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86
