Hi ! > 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)? 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! regards roland xfree86@xxxxxxxxxxx schrieb am 16.11.03 20:51:49: > > On 16 Nov 2003, at 20:06, roland@webde wrote: > > > Hi ! > > since i use X only on localhost and open remote x-windows only via > > ssh-tunneling, > > i wonder why my xserver is listening on 0.0.0.0:6000. > > an interface binding to 127.0.0.1:6000 would be sufficient and more > > secure. > > lets say i have 2 network interfaces - one connected to the internet > > and one to > > the localnet. how can i configure X that it binds to > > localnet-interface only? > > You can use the '-nolisten tcp' option suppress listening on tcp > completely in your > case. > If you're using xdm, you can add the option to /etc/X11/xdm/Xserver. If > you're using > startx to start the server, you can use 'startx -- -nolisten tcp' or > create a ~/.xserverrc > file to specify the option. See the Xserver(1) and xinit(1) manual > pages for more details. > > _______________________________________________ > XFree86 mailing list > XFree86@xxxxxxxxxxx > http://XFree86.Org/mailman/listinfo/xfree86 ______________________________________________________________________________ WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130 _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
