I dont think that there is a way to keep X from listening on port 6000 (or some port) since it is a server running on your machine. It has to bind to a port and then the client connects to that port. That is why you can have multiple X sessions, running on different ports. If you dont want anything running on port 6000, dont run X. If you just dont want anyone else but yourself to connect to it, do ipchains -A input -s ! 127.0.0.1 -p tcp --dport 6000 -j REJECT On Wed, 11 Jul 2001, [ISO-8859-1] Martin K�hling wrote:
On Wed, 11 Jul 2001, Roman Drahtmueller wrote:
On my SuSE 7.1 box it doesn't work either (yes, I *did* restart the X server!).
You're not supposed to restart the X-server. Restart xdm! This will nuke the X-Server as well, of course...
I should have written: "I *did* restart X".
Netstat -pnl still shows the process "X" listening on port 6000:
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 17043/X
Martin
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Chad Whitten Network/Systems Administrator Nexband Communications chadwick@nexband.com