Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <415A7D9E.DA312AB5@dessent.net>
Date: Wed, 29 Sep 2004 02:17:18 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SSH Environment
References: <1936 DOT 217 DOT 162 DOT 71 DOT 141 DOT 1096446340 DOT squirrel AT 217 DOT 162 DOT 71 DOT 141>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

"David E. Meier" wrote:

> I try the running ssh client with only the required dll's from a .net
> application and without a full cygwin installation. Basically that works
> fine.

SSH looks in /etc/passwd for the user's home directory, I believe.  It
uses the mount table to know where /etc is actually located, as with any
Cygwin application.

> Then I tried setting the HOME-variable to different values when starting
> the ssh-process from my .net application using 

Insert here the usual reminder that if you distribute a Cygwin binary
such as ssh you must also arrange means to distribute the full source
code required to build that binary, which includes the source to the
Cygwin DLL.  Pointing users to cygwin.com for source code is not
allowed.

Brain

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/