I've had problems with this too. My workaround what I use now is instead of starting Xwindows with startx from the console, I use the following script. On Tue, 20 Jan 2004, Lindomar Santos wrote:
To: david
From: Lindomar Santos Subject: Re: [suse-security] closing port 6000 Hi David,
You have to edit /etc/opt/kde3/share/config/kdm/Xservers
:0 local /usr/X11R6/bin/X :0 vt07 -nolisten tcp
ps: In suse box 8.2
__|__ By Lindomar, o---*--(*)--*---o http://wecanstopspam.org
On Tue, 20 Jan 2004, david wrote:
I dont want to filter the port, I want to close it i dont understand why i easly can close port 6000 on slackware and mandrake but suse just cant
On Tuesday 20 January 2004 9:03 am, Philippe Vogel wrote:
david wrote:
is there another configuration file to close this port ?
/etc/opt/kde3/share/config/kdm
This may/should be a link (or /opt/... should be)
With yast you can configure there is no remote access to X.
If you want to have ports not closed but in steath mode you will have to patch iptables with the grsecurity iptables-patch (you will need kernel sources as well). This patch implements steathmode for filtering (afaik this will even not work with ack-packets scans).
Philippe
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here