Hmm, with the current approach a -nolisten to an alias has no effect anyway. A '-nolisten tcp' will have the same effect as a '-nolisten unix': None.
The reason is that a flag is set for the protocol however when the protocols are initialized the aliases aren't checked. Also tcp is aliased to IPv6. I don't know why this was done but I would expect that it violates the principle of least surprise: When connecting with 'display tcp/1.2.3.4:0' a IPv6 socket is created and the IPv4 connection is done over the IPv6 socket. This may not work on systems without IPv6 support. Egbert. Keith Packard writes: > Around 23 o'clock on Jul 23, Matthieu Herrb wrote: > > > Here's a patch to allow multiple '-nolisten' options on the command > > line. To disable both IPv4 and IPv6 transports, one needs to say: > > > > X -nolisten tcp -nolisten inet6 > > While supporting multiple -nolisten arguments is good, I suggest that the > current '-nolisten tcp' should include both inet4 and inet6 tcp options; > most people use '-nolisten tcp' to avoid exposing an open port to the X > server to the network. > > -nolisten inet4 don't listen for TCP/IPv4 connections > -nolisten inet6 don't listen for TCP/IPv6 connections > -nolisten tcp don't listen for any TCP connections > > -keith > > > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
