Date: Wed, 21 Mar 2001 17:54:57 +0000 From: David Pick <D.M.Pick@qmw.ac.uk> To: security@freebsd.org Subject: Re: Disabling xhost(1) Access Control Message-ID: <E14fmoz-0001CG-00@xi.css.qmw.ac.uk> In-Reply-To: Your message of "Wed, 21 Mar 2001 19:14:54 %2B0300." <Pine.BSF.4.21.0103211909180.3763-100000@astro.ioffe.rssi.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> I also think about disabling xhost and wonder which solution have you > chosen -- modifying Xserver source offered later in the thread? Actually, > "-nolisten tcp" is a nice idea, but I would like X to run from the server > on all "Xterminals", and of course "X -query" fails that way... I actually run two copies of "xdm": one (with "-nolisten tcp") for the local display which also has the XDMCP port set to zero to disable remore X displays using XDMCP; and the other copy of "xdm" with no X servers at all, just listening for XDMCP on port 177. Makes it much easier to control the availability of XMDCP without editing files as such. I use this on a laptop which wants just the local display in most connections, but I want to allow the use of an X terminal when I'm at home with a trusted desktop and 17" monitor. -- David Pick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E14fmoz-0001CG-00>