public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: Andrew DeFaria <Andrew@DeFaria.com>, cygwin@cygwin.com
Subject: Re: X11Forward and xauth problems
Date: Tue, 24 Mar 2015 13:35:00 -0000	[thread overview]
Message-ID: <55115B29.8000904@dronecode.org.uk> (raw)
In-Reply-To: <meq0g3$hob$1@ger.gmane.org>

On 23/03/2015 21:27, Andrew DeFaria wrote:
> On 3/23/2015 2:06 PM, Jon TURNEY wrote:
>> On 23/03/2015 20:48, Andrew DeFaria wrote:
>>> Normally I just turn on -X (or put X11Forward yes in ~/.ssh/config) but
>>> that usually results in a noticeable delay in logging in and the
>>> following error:
>>>
>>> Warning: untrusted X11 forwarding setup failed: xauth key data not
>>> generated
>>> Warning: No xauth data; using fake authentication data for X11
>>> forwarding.
>>
>> Firstly, if you don't want these warnings, use ssh -Y.
>>
>> (By using ssh -X, you are asking for something which the X server can't
>> give you, hence the warnings.  See
>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trusted-untrusted-x11-forwarding
>>
>> for more details)
>
> Yeah but -Y gives me the same thing:

This is similar, but it is not the same.

> Adefaria-lt:ssh -Y cm-app-ldev01
> Warning: No xauth data; using fake authentication data for X11 forwarding.
> /usr/bin/xauth:  unable to link authority file
> /home/adefaria/.Xauthority, use /home/adefaria/.Xauthority-n
> Cm-app-ldev01:

I think this last message here is unusual, and is coming from xauth 
running on the remote server.  Can you you give a few more details on 
what OS that is running?

If you connect using ssh -vv -Y, you should be able to see the xauth 
commands that sshd is running, and if those, or some other step in the 
connection, is the cause of the delay.

You might also try running those xauth commands in the terminal to 
investigate further.

>>> Adefaria-lt:xhost +
>>> access control disabled, clients can connect from any host
>>> Adefaria-lt:ssh cm-app-ldev01
>>> Cm-app-ldev01:export DISPLAY=adefaria-lt:0
>>> Cm-app-ldev01:xclock
>>> Error: Can't open display: adefaria-lt:0
>>> Cm-app-ldev01:
>>
>> If you want this to work, you will now (since X server 1.17) need to
>> start the server with the option '-listen tcp'.
>
> Restarted Xwin with -multimonitor and -listen tcp. Now I get:

Sorry for any ambiguity, but you have misunderstood what I wrote.

If you want explicitly setting DISPLAY and allowing access using xhost 
to work, you must start the server with the option '-listen tcp'.

-- 
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-03-24 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 21:06 Andrew DeFaria
2015-03-23 21:26 ` Jon TURNEY
2015-03-23 22:03   ` Andrew DeFaria
2015-03-24 13:35     ` Jon TURNEY [this message]
2015-03-25 22:11       ` Andrew DeFaria
2015-03-26 20:39         ` Jon TURNEY
2015-03-26 22:17           ` Andrew DeFaria
2015-03-27  3:12             ` Andrew DeFaria
2015-03-30 13:40             ` 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=55115B29.8000904@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Andrew@DeFaria.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).