public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Louden <chris.louden@gmail.com>
To: cygwin@cygwin.com
Subject: Re: xauth issue (remote X w/putty via Cygwin/XWin)
Date: Tue, 22 Sep 2015 16:04:00 -0000	[thread overview]
Message-ID: <CAJGdTOAG6sESn1JySSkhBbiR1F9i2rF9pSGHWZzY62r7KMXWgw@mail.gmail.com> (raw)
In-Reply-To: <56017838.1050408@dronecode.org.uk>

I did attempt to use the Cygwin version of Putty but encountered
several errors. I ended adding a post-install script that makes the
following changes in /bin/startxwin and /bin/startx

defaultserverargs="-multiwindow -listen tcp"'
enable_xauth=0

This seems to allow functionality with our external (to Cygwin)
version of Putty however I am still testing.

-Chris


On Tue, Sep 22, 2015 at 9:48 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> On 15/09/2015 16:56, Chris Louden wrote:
>>
>> Following up on this post:
>>
>> https://cygwin.com/ml/cygwin-xfree/2015-02/msg00075.html
>>
>> Is there any news regarding the getting "listen tcp" issue with xauth
>> resolved. The workaround mentioned works but isn't ideal in the
>> environment I have.
>
>
> No progress, but a couple more suggestions:
>
> cygwin now has an X11 PuTTY client package.  I haven't tested that, but I
> guess that should be able to find the X display and authority file without
> any special configuration.
>
> Alternatively, you could patch xinit to use a deterministic name for the
> authority file e.g. ~/.serverauth.hostname.display rather than
> ~/.serverauth.pid.
>
> (If you write such a patch, please submit it, as that would probably be
> acceptable in our package and maybe upstream.  Using just the pid seems
> wrong, as there potentially could be collisions in a shared home directory)
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2015-09-22 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 15:56 Chris Louden
2015-09-22 15:48 ` Jon TURNEY
2015-09-22 16:04   ` Chris Louden [this message]

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=CAJGdTOAG6sESn1JySSkhBbiR1F9i2rF9pSGHWZzY62r7KMXWgw@mail.gmail.com \
    --to=chris.louden@gmail.com \
    --cc=chrislouden@gmail.com \
    --cc=cygwin@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).