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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Fri, 26 Sep 2003 21:48:06 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	"Pierre A. Humblet" <pierre AT phumblet DOT no-ip DOT org>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Installed, Admin can run, other account can't...
In-Reply-To:	<3.0.5.32.20030926212951.00822b50@incoming.verizon.net>
Message-ID:	<Pine.GSO.4.56.0309262143440.3193@slinky.cs.nyu.edu>
References:	<3F745893 DOT 42F40E25 AT npc DOT net> <3F7360C6 DOT 53FB260C AT npc DOT net>
	<Pine DOT GSO DOT 4 DOT 56 DOT 0309251803540 DOT 3193 AT slinky DOT cs DOT nyu DOT edu> <3F745893 DOT 42F40E25 AT npc DOT net>
	<3 DOT 0 DOT 5 DOT 32 DOT 20030926212951 DOT 00822b50 AT incoming DOT verizon DOT net>
Importance:	Normal
MIME-Version:	1.0

On Fri, 26 Sep 2003, Pierre A. Humblet wrote:

> At 11:31 AM 9/26/2003 -0400, Igor Pechtchanski wrote:
> >
> >The "real" fix would be to make setup create the directories with the
> >right permissions from the start.  I'm not sure this is possible.
> >Perhaps people with more knowledge of ACLs (Pierre, Corinna, CGF?) will
> >chime in and offer their opinions...
>
> Sure, but what are the right permissions? Some people objet to giving
> access to Everybody. The group name and whether the group should have
> write access are matters of local preference.
>
> So setup uses the default inheritable acl of the directory under which
> cygwin is installed. It works just fine in most cases. I don't know why
> in this case group Users got no rights. This is not a typical factory
> default, it was most probably set that way for some local reason.
>
> Perhaps the exit message of setup should be to remind the installer
> to verify the permissions (PTC).
> Or perhaps that's another test that could be added into /etc/profile,
> nagging the user "are you sure this is really what you want".
>
> Pierre

Hmm, I guess it would make sense for setup to check the permissions on the
Cygwin root directory *before* installing any files in it, especially if
it's a new install and it's creating the root directory (I suppose it
would inherit from c:\ in that case, right?).  This way, if setup
determines that the root directory *it just created* has very restrictive
permissions, it could warn the user, or even open a Windows security
dialog for c:\cygwin (or whatever the root is) and let the user fix the
permissions before creating more directories or installing files.  Again,
this is all PTC, and I just wanted to get this into the archives for now.
	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!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

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

- Raw text -