Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Thu, 16 May 2002 00:19:11 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin & opensshd on .net enterprise server
Message-ID: <20020516041911.GC24615@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <IEEOIFENFHDKFJFILDAHKEEAEGAA DOT tony AT tndh DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <IEEOIFENFHDKFJFILDAHKEEAEGAA.tony@tndh.net>
User-Agent: Mutt/1.3.23.1i

On Wed, May 15, 2002 at 12:30:26PM -0700, Tony Hain wrote:
>I am looking for any clues on how to make cygwin & opensshd work on a
>.net enterprise server, and found nothing in the mail archive. I had
>been running Mark's opensshd specific environment on W2k server without
>trouble. When I installed a fresh build 3615, OpenSSH_3.1p1 failed, so I
>thought I would try the full cygwin. That is failing in the same way, so
>after a couple of days experimenting I am stuck.
>
>With the intent of sending Mark a trace, I followed his instructions for
>debugging by  using a scheduled task to get a system account command
>window (if it is of any use, I have put a copy of the debug trace at the
>end). What I found in the process is that there appears to be some
>permissions related problem, because I get logged in as any valid user
>over the ssh channel, but that immediately exits. Trying to figure that
>out I found that the only process/user that can run the shell is the
>system account. When I run sh, bash, or the cygwin.bat from any other
>account it just exits, but they appear to work fine in the system
>initiated command window. This is also true of many of the exe's in
>/bin, although some of them just hang with 100% cpu for the non-system
>user.
>
>One thing I found in the process is that the old passwd file is useless.
>The only way I could log in using ssh with either Mark's sshd subset, or
>the full cygwin was to use the mkpasswd & mkgroup process to build those
>files from scratch with the NT UIDs. What the log showed before I did
>that was 'Cygwin Process Id = 0xC78 : fatal: setuid 520: Not owner.'
>Simply changing that got me to the point of 'password accepted', but
>until the shell runs for all accounts, that does no good.
>
>I tried setting bash to W2k compatibility mode (actually all modes), and
>turning off  the 'protect my computer from unauthorized activity'
>checkbox in the run as ... option, but those made no difference. I also
>tried setting the file owner for the entire subdirectory tree to system,
>again no difference. cygrunsrv.exe and sshd.exe are running as system,
>but it appears they end up running the shell in user space.
>
>Any clues what to try next???

Why don't you ask "Mark"?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/