From mike@boobaz.net Thu Nov 9 15:29:44 2000 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA85930 for ; Thu, 9 Nov 2000 15:29:43 -0800 Received: from boobaz.net (c1056043-a.sttln1.wa.home.com [24.19.193.36]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA17187 for ; Thu, 9 Nov 2000 15:29:42 -0800 Received: from c1056043-a (c1056043-a [24.19.193.36]) by boobaz.net (8.9.3/8.9.3) with ESMTP id PAA10149 for ; Thu, 9 Nov 2000 15:29:41 -0800 Date: Thu, 9 Nov 2000 15:29:41 -0800 (PST) From: Mike X-Sender: mike@c1056043-a.sttln1.wa.home.com To: UW Linux Group Subject: Re: [OT] XConfused In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 9 Nov 2000 at 14:35, William Rowden wrote: |AFAIK, MI/X does not have access control. For WeirdX, I inserted |this into config/props: | | xhost +localhost | |I assumed the port forwarding for X would work like the port |forwarding for other protocols (e.g., localhost works for an http, |nntp, pop3 or smtp server in Netscape), i.e., that the connection |would appear to come from localhost. I think you're mistaken about what this does. Using 'xhost' (in Linux at least) allows you to specify which *remote* hosts can connect to your *local* X server. For example, in order to run the X application "baz" on host "foo" from my workstation "bar" I would: 1) Fire up X on bar (startx in Linux) 2) Run 'xhost +inet:foo' on bar 3) ssh to host foo and make sure $DISPLAY is set to "bar:0" 4) run X application "baz" on host "foo" --------------------------- -=<(| mike@boobaz.net |)>=- .