X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Message-ID: <4A7859F2.5030704@dronecode.org.uk>
Date: Tue, 04 Aug 2009 16:55:30 +0100
From: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: $DISPLAY variable empty after SSHing
References: <24800981 DOT post AT talk DOT nabble DOT com> <4A77AFF8 DOT 5030406 AT cygwin DOT com> <24802076 DOT post AT talk DOT nabble DOT com> <h58dbj$3ea$1 AT ger DOT gmane DOT org>
In-Reply-To: <h58dbj$3ea$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 04/08/2009 05:27, Andrew DeFaria wrote:
> mcoughlin wrote:
>> Well it is good to know that it is doable.
>>
>> My computer is running Windows Vista, the middle computer runs Red Hat
>> 3, and the work computer runs Red Hat 4.
>>
>>>> ssh -X computer #2
>>>>
>>>> Warning: untrusted X11 forwarding setup failed: xauth key data not
>>>> generated
>>>> Warning: No xauth data; using fake authentication data for X11
>>>> forwarding.
> These warnings are significant. Why don't you resolve them first then
> see if the problem persists.

I doubt very much that these warnings are significant.

The OP says he tried with ssh -Y (which is the way to 'resolve' these 
warnings), as well as ssh -X.

Not having X11 forwarding on the server as suggested elsewhere seems a far 
more likely cause. Adding '-v' to the ssh command line is usually helpful in 
debugging ssh problems.

> Note I have not totally figured out what causes this and what the proper
> solution is. It does involve using xauth and adding the proper auth key.
> My internet research on this has yielded hazy results. I also noticed
> that this tends to happen when you are not yourself. By that I mean that
> I've seen this happen when I su as somebody else then do an ssh to
> another machine. IOW somethings screwy in the authentication of the user
> thuse ssh/X considers it unsafe and perhaps is not passing along the
> proper DISPLAY because of this.

A very clear explanation can be found in point 3 in this email [1]

This is pointed to by the Cygwin/X FAQ and these issues discussed there, 
although I agree the language there could use some clarifications.

[1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00154.html

--
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