public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Subject: Re: Possible to use clipboard with remote/xdm connection? Date: Fri, 02 Jan 2004 19:20:00 -0000 [thread overview] Message-ID: <3FF5C45A.3090406@msu.edu> (raw) In-Reply-To: <20040102185023.GA5256@areti.co.uk> Chris Green wrote: > On Fri, Jan 02, 2004 at 01:28:22PM -0500, Harold L Hunt II wrote: > >>>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. >> >>Sure, one wants to, but there is not a way to do it. Patches are welcome. >> > > So are we now saying that what I want to do is impossible? Umm... I'm not sure what you want to do. It is not currently possible to pre-authenticate xwinclip via xhost from a script run on your Windows machine, but it is possible to use the X hosts file like Alexander suggested, or to run xhost on the remote machine after logging in. So, if you want to do the first item, then you would need to try to design a change to the X security system and provide a patch that implements it. It would be difficult to design such a change without opening up security holes that do not currently exist; or, it may not be possible. > I thought people were initially saying that although the '-clipboard' > parameter to Xwin wouldn't work when using xdmcp the separate xwinclip > executable should work OK. However it would now seem that it's > actually impossible to execute xwinclip in the situation where one has > am xdmcp connection to a remote computer. No, it is not impossible. Alexander told you how to use xwinclip (run xhost on the remote machine once you have logged in), but you did not believe him that it worked so you didn't try it. Remember who is asking for help here and who is helping... we are telling you how to do it, you just need to try it. > I'm not complaining (much!), but I am rather confused. :-) It's okay. You'll figure it out. Harold
next prev parent reply other threads:[~2004-01-02 19:20 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 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 [this message] 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=3FF5C45A.3090406@msu.edu \ --to=huntharo@msu.edu \ --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: linkBe 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).