X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:  Re: $DISPLAY variable empty after SSHing
Date:  Mon, 03 Aug 2009 21:27:30 -0700
Lines: 29
Message-ID: <h58dbj$3ea$1@ger.gmane.org>
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>
Mime-Version:  1.0
Content-Type:  text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
In-Reply-To: <24802076.post@talk.nabble.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Note-from-DJ: This may be spam



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.

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.
-- 
Andrew DeFaria <http://defaria.com>
Give a man a fish and he'll eat for a day, teach a man to phish and 
he'll suck your bank account dry


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