public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Larry W. Virden" <lvirden@gmail.com> To: cygwin-xfree@cygwin.com Subject: struggling with xauth vs xhost Date: Tue, 30 Apr 2013 14:21:00 -0000 [thread overview] Message-ID: <CAPRVdgRW8Q=2i2irK0ej3VkD-8s_wdwtjZ304avsbvbrmgaCyQ@mail.gmail.com> (raw) While in the process of moving from a commercial X server to the cygwin Xfree server, we seem to have run into a peculiar behavior. The previous environment made heavy use of xhost. I proposed that in cygwin xfree we move to xauth as a more secure environment. That has for the most part worked out. The environment is that the x applications are running on a Solaris 10 sparc machine, displaying back to Win7 desktops with cygwin 1.7.x running on them. When a user chooses the single X window method of opening a local window which ssh's over to the Unix machines, things seem to work okay. When they choose the "full screen" approach, where the entire window takes over the desktop, and the window manager and everything else is running remotely, an xhost is being executed. This causes some applications to fail because the language used considers that to be a security risk. When we look in both local start up files as well as remote start up files, we do not see where the xhost is being performed. Is there a way for us to track down where that is occurring so that we can see about commenting that out? Thanks! -- Tcl - The glue of a new generation. http://wiki.tcl.tk/ Larry W. Virden http://www.facebook.com/lvirden/ Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next reply other threads:[~2013-04-30 14:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-30 14:21 Larry W. Virden [this message] 2013-05-01 13:46 ` Jon TURNEY
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='CAPRVdgRW8Q=2i2irK0ej3VkD-8s_wdwtjZ304avsbvbrmgaCyQ@mail.gmail.com' \ --to=lvirden@gmail.com \ --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).