Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42795B97.FFEBA771@dessent.net> Date: Wed, 04 May 2005 16:32:39 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: CYGWIN sshd service could not be started References: <000601c54f44$479cdc80$6c01a8c0@dell5100> <427678F2.EA496694@dessent.net> <42768CA6.6485FF51@dessent.net> <20050503085400.GA25050@calimero.vinschen.de> <20050503090504.GC25050@calimero.vinschen.de> <20050504090655.GG31567@calimero.vinschen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.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 ? ;-) > 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/