From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15027 invoked by alias); 2 Jan 2004 16:10:59 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 15019 invoked from network); 2 Jan 2004 16:10:58 -0000 Received: from unknown (HELO meg.hrz.tu-chemnitz.de) (134.109.132.57) by sources.redhat.com with SMTP; 2 Jan 2004 16:10:58 -0000 Received: from hedwig.hrz.tu-chemnitz.de ([134.109.132.173] helo=mailbox.hrz.tu-chemnitz.de) by meg.hrz.tu-chemnitz.de with esmtp (Exim 4.22) id 1AcRt3-0002H5-SU; Fri, 02 Jan 2004 17:10:57 +0100 Received: from odoaker.hrz.tu-chemnitz.de ([134.109.132.94] ident=[rs+Igogj9x8Tc121/t4WPuObgGHKrlvk]) by mailbox.hrz.tu-chemnitz.de with esmtp (Exim 4.22) id 1AcRt3-00087j-OX; Fri, 02 Jan 2004 17:10:57 +0100 Received: from localhost (goal@localhost) by odoaker.hrz.tu-chemnitz.de (8.11.6/8.11.6) with ESMTP id i02GAvt17190; Fri, 2 Jan 2004 17:10:57 +0100 X-Authentication-Warning: odoaker.hrz.tu-chemnitz.de: goal owned process doing -bs Date: Fri, 02 Jan 2004 16:10:00 -0000 From: Alexander Gottwald To: cygwin-xfree@cygwin.com, chris.green@isbd.co.uk Subject: Re: Possible to use clipboard with remote/xdm connection? In-Reply-To: <20040102144403.GA4596@areti.co.uk> Message-ID: References: <20031231221603.GA320@areti.co.uk> <3FF34EE3.9070300@msu.edu> <20040101153702.GB1971@areti.co.uk> <20040102140446.GA4425@areti.co.uk> <20040102144403.GA4596@areti.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Spam-Report: --- Start der SpamAssassin 2.61 Textanalyse (0.0 Punkte) Fragen an/questions to: Postmaster TU Chemnitz --- Ende der SpamAssassin Textanalyse X-Scan-Signature: cb5add96829c288e5da73fa3a8e2275c X-SW-Source: 2004-01/txt/msg00019.txt.bz2 List-Id: On Fri, 2 Jan 2004, Chris Green wrote: > But if I run xhost in that session I will be setting xhost permissions > on the Linux Slackware system which is most definitely not what is > required. No. It sets the permissions of the __xserver__ to which the session belongs. Try it! linux$ echo $DISPLAY win2k.local.net:0.0 linux$ xhost 127.0.0.1 127.0.0.1 being added to access control list linux$ xhost access control enabled, only authorized clients can connect INET:localhost linux$ DISPLAY=127.0.0.1:0.0 xhost xhost: unable to open display "127.0.0.1:0.0" win2k$ DISPLAY=127.0.0.1:0 xhost access control enabled, only authorized clients can connect INET:win2k > It seems very odd that xhost requires access to the local display in > order to work as you need xhost to set permission to acces the local > display - sort of catch 22. Same with the gates of a castle. To get in, you must open it from inside. This is the main principle of security. You can not allow those who have no access to change the permissions. bye ago -- Alexander.Gottwald@s1999.tu-chemnitz.de http://www.gotti.org ICQ: 126018723