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:03:00 -0000	[thread overview]
Message-ID: <20040102180352.GB5079@areti.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0401021824060.12132@odoaker.hrz.tu-chemnitz.de>

On Fri, Jan 02, 2004 at 06:27:42PM +0100, Alexander Gottwald wrote:
> On Fri, 2 Jan 2004, Chris Green wrote:
> 
> > The "start /B xhost 127.0.0.1" and the "start /B xwinclip" both fail
> > because they haven't got permission to access display 127.0.0.1:0.0.
> > 
> > How on earth can one set this permission if xhost can't be run?
> 
> create a file /etc/X0.hosts and add all hosts which should have access
> to the xserver.
> 
Ah, now that seems a good idea, thanks!

> > The xterm one is running in has permission to display so why can't
> > xhost and xwinterm display there too?
> 
> Which xterm? The one from linux has permission because you started it 
> from the xdm session. The one from windows has no permission because
> someone might have logged on the the windows host and started it from
> there. This is a simple security issue.
> 
The xterm that one runs by clicking on the cygwin icon, the standard
cygwin (not cygwin/X) terminal window.  It's there that I'm trying to
start my session from (well, actually it's a batch file, but I'm
running it from that window).

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


  reply	other threads:[~2004-01-02 18:03 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 [this message]
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
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=20040102180352.GB5079@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).