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
Date: Wed, 11 May 2005 12:20:49 -0400
From: Chip Olson <ceo AT thsi DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Permissions problem mounting NFS shares from Cygwin sshd
Message-ID: <20050511162049.GB14391@thsi.org>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20050510190317 DOT GB27244 AT thsi DOT org> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050510155711 DOT 09ccf2e8 AT pop DOT prospeed DOT net> <20050510214311 DOT GC27244 AT thsi DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0505110446000 DOT 12861 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.61.0505110446000.12861@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4i
X-IsSubscribed: yes

Quoth Igor Pechtchanski:

> Read the above page again, please.  If I understood your statement
> correctly, you've edited /etc/passwd and /etc/group directly.  This is not
> *supposed* to have any effect, unless you use the appropriate Windows
> tools to adjust group memberships.

From the NT Security document:

	Unfortunately, workstations and servers outside of domains
	are not able to set primary groups! In these cases, where
	there is no correlation of users to primary groups, NT returns 513
	(None) as primary group, regardless of the membership to existing
	local groups.

	When using mkpasswd -l -g on such systems, you have to change
	the primary group by hand if `None' as primary group is not what you
	want (and I'm sure, it's not what you want!)

This machine is not in a domain. I understood the above to mean I
needed to generate the password file with mkpasswd and edit it to
change those group IDs. Am I understanding incorrectly?

> The usual place to look for the actual errors when starting sshd is the
> Windows event log.

OK, this is interesting:

sshd : PID 1364 : starting service `sshd' failed: execve: 1, Operation
not permitted.

Which tells me Administrator doesn't have the privileges to start
sshd. Following the tried-and-true troubleshooting methodology of
"dunno, maybe it'll work", I changed /usr/sbin/sshd's ownership from
Administrator:Users to Administrator:Administrators. Its group ID
changed from 545 to 544, as I would expect, but the change had no
effect.

-- 
-Chip Olson | ceo AT thsi DOT org | "And the sands will roll out a carpet of 
gold / For your weary toes to be a-touchin' / And the ship's wise men 
will remind you once again / The whole wide world is watchin'"  
                                 -Bob Dylan, "When The Ship Comes In"

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