Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 17:25:55 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Chip Olson cc: cygwin AT cygwin DOT com Subject: Re: Permissions problem mounting NFS shares from Cygwin sshd In-Reply-To: <20050511162049.GB14391@thsi.org> Message-ID: 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> <20050511162049 DOT GB14391 AT thsi DOT org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 11 May 2005, Chip Olson wrote: > 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? I believe so. I read the above as "one only needs to change /etc/passwd and /etc/group if the machine is part of a domain". Perhaps it could be reworded to make that clearer -- . > > 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. Your Administrator user is probably not seeing /usr/sbin, or the permissions on /usr/sbin are wrong. Hard to know without more information. > 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. I don't recall you attaching the output of "cygcheck -svr" as requested in . Please provide that information so that we know what you have on your Cygwin installation. Also, if you log in as Administrator, can you explicitly run /usr/sbin/sshd? If not, what is the error message? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/