X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.7 required=5.0	tests=BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
connect(): No such file or directory
From: jaynnas AT us DOT ibm DOT com
Subject: Re: Different user environment for key vs password authentication
Date: Thu, 3 Jun 2010 18:56:49 +0000 (UTC)
Lines: 13
Message-ID: <hu8tth$e6r$1@dough.gmane.org>
References: <COL112-W26010F7BDD060C68A6687EDCD00 AT phx DOT gbl> <4C06DC4D DOT 7040005 AT cygwin DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-IsSubscribed: yes
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

To make sure I'm understanding the implication of your response, let me 
summarize...

According to the link you sent, the different user environment is 
resulting not because of something that the ssh server (or cygwin) is 
doing/configured to do but because of how Windows handles remote log-ins 
with password or key authentication.  In order to deal with this fact 
regarding key authentication, I must consider to use some of the 
approaches suggested in the document to switch the user context.   Is this 
an accurate summary? 

Thanks,
Jaynna


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