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: <42795B97.FFEBA771@dessent.net>
Date: Wed, 04 May 2005 16:32:39 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: CYGWIN sshd service could not be started
References: <000601c54f44$479cdc80$6c01a8c0 AT dell5100> <427678F2 DOT EA496694 AT dessent DOT net> <42768CA6 DOT 6485FF51 AT dessent DOT net> <20050503085400 DOT GA25050 AT calimero DOT vinschen DOT de> <20050503090504 DOT GC25050 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 61 DOT 0505031553390 DOT 1454 AT slinky DOT cs DOT nyu DOT edu> <20050504090655 DOT GG31567 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 61 DOT 0505040933420 DOT 1454 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Igor Pechtchanski wrote:

> > > In the future versions, we should also check for user mounts for the
> > > SYSTEM user -- unlikely, but very nasty and hard to detect.  I also
> > > wonder if the above test should go into configurations for all
> > > services, or perhaps even added to cygrunsrv in some form...
> >
> > Well, you know the acronym for this... ;-)
> 
> Oh, you mean <http://cygwin.com/acronyms/#BWAM>? ;-)
> I know someone will have to do that, just wanted to put that one in the
> archives.

Maybe cygpath needs another option, "check path as user."  E.g.

cygpath -c SYSTEM /usr/bin  # return true if SYSTEM user can access
/usr/bin

It would consider all the mounts, check the permissions on the
directory, do traverse checking if that's enabled, and anything else
relevent.  For files it would check the ability to read, for paths the
ability to execute/traverse.

This could be used for troubleshooting various problems reported on the
mailing list relating to permissions.  It seems to come up in various
forms often.

Although I fully admit that SHTDI applies here too.

Brian

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