public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: Andrew.DeFaria@tellabs.com
Subject: Re: Can't talk to X server through ssh tunnel after ~ 18 minutes
Date: Thu, 26 May 2011 15:38:00 -0000	[thread overview]
Message-ID: <4DDE743B.9060504@dronecode.org.uk> (raw)
In-Reply-To: <irk4eh$c8l$1@dough.gmane.org>

On 26/05/2011 00:47, Andrew DeFaria wrote:
> On 5/25/2011 11:01 AM, Tim Daneliuk wrote:
>> On 5/25/2011 12:43 PM, Andrew DeFaria said this:
>>> I ssh from my Cygwin box to a Linux machine (happens with Solaris machines
>>> too) and I can run X applications back to Cygwin/X without a problem.
>>> However, after a few minutes something happens to the tunnel and I can no
>>> longer put up any X windows:
>> What arguments are you using to start the ssh session?
> The only argument is -X. Like I said, I was able to put up X windows through
> the ssh tunnel. Then, after some, it stops working - consistently.

I'd guess this is something to do with an untrusted xauth cookie with a 20
minute timeout being generated, although exactly how that can happen if you
are using an X server without the SECURITY extension (as Cygwin/X servers have
been built for the past couple of years), I don't quite understand.

See 'ForwardX11Timeout' in 'man ssh_config'

Use 'ssh -Y'

--
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:[~2011-05-26 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 17:43 Andrew DeFaria
2011-05-25 18:02 ` Tim Daneliuk
2011-05-25 23:47   ` Andrew DeFaria
2011-05-26 15:38     ` Jon TURNEY [this message]
2011-05-27  5:10       ` Andrew DeFaria

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=4DDE743B.9060504@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Andrew.DeFaria@tellabs.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).