public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Chris Green <chris@areti.co.uk>
To: cygwin-xfree@cygwin.com
Subject: Re: Possible to use clipboard with remote/xdm connection?
Date: Fri, 02 Jan 2004 18:00:00 -0000	[thread overview]
Message-ID: <20040102180025.GA5079@areti.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0401021702380.12132@odoaker.hrz.tu-chemnitz.de>

On Fri, Jan 02, 2004 at 05:10:57PM +0100, Alexander Gottwald wrote:
> 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. 
> 
... but I am "within the castle", I'm sitting running a script on the
win2k system and I can't see how to run xwinclip there because it
won't give me permission to display on the terminal that I'm already
using.

It's of little use to be able to allow xwinclip to run on the win2k
system by executing something on the Linux system.  One wants a means
to do it from the X startup script.

-- 
Chris Green (chris@areti.co.uk)


  reply	other threads:[~2004-01-02 18:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 23:21 Chris Green
     [not found] ` <3FF34EE3.9070300@msu.edu>
2004-01-01 15:37   ` Chris Green
2004-01-01 18:26     ` Alexander Gottwald
2004-01-02 14:04       ` Chris Green
2004-01-02 14:33         ` Alexander Gottwald
2004-01-02 14:44           ` Chris Green
2004-01-02 15:20             ` Chris Green
2004-01-02 17:27               ` Alexander Gottwald
2004-01-02 18:03                 ` Chris Green
2004-01-02 19:33                   ` Alexander Gottwald
2004-01-02 19:49                     ` Thomas Dickey
2004-01-02 20:15                       ` Alexander Gottwald
2004-01-02 20:56                         ` Thomas Dickey
2004-01-02 21:33                           ` Harold L Hunt II
2004-01-02 21:40                             ` Thomas Dickey
2004-01-02 21:44                               ` Harold L Hunt II
2004-01-02 22:50                     ` Chris Green
2004-01-02 23:50                       ` [OT] " Igor Pechtchanski
2004-01-03  0:07                         ` Thomas Dickey
2004-01-03 12:22                         ` Chris Green
2004-01-02 16:10             ` Alexander Gottwald
2004-01-02 18:00               ` Chris Green [this message]
2004-01-02 18:28                 ` Harold L Hunt II
2004-01-02 18:50                   ` Chris Green
2004-01-02 19:20                     ` Harold L Hunt II
2004-01-02 22:50                       ` Chris Green
2004-01-02 20:13                 ` Alexander Gottwald
2004-01-02 22:43                   ` Chris Green
2004-01-03 11:00                     ` Alexander Gottwald
2004-01-12 19:57 Kevin Markle
2004-01-12 20:00 ` Harold L Hunt II

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040102180025.GA5079@areti.co.uk \
    --to=chris@areti.co.uk \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).