From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: "Pierre A. Humblet" <pierre@phumblet.no-ip.org>
Cc: cygwin@cygwin.com
Subject: Re: Installed, Admin can run, other account can't...
Date: Sat, 27 Sep 2003 02:11:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309262143440.3193@slinky.cs.nyu.edu> (raw)
In-Reply-To: <3.0.5.32.20030926212951.00822b50@incoming.verizon.net>
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@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.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/
next prev parent reply other threads:[~2003-09-27 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 22:07 Marco Mason
2003-09-25 22:25 ` Igor Pechtchanski
2003-09-26 15:26 ` Marco Mason
2003-09-26 15:32 ` Igor Pechtchanski
2003-09-26 20:19 ` Marco Mason
2003-09-27 1:48 ` Pierre A. Humblet
2003-09-27 2:11 ` Igor Pechtchanski [this message]
2003-09-26 12:01 ` Jason Tishler
2003-09-26 12:20 ` Jason Tishler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0309262143440.3193@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin@cygwin.com \
--cc=pierre@phumblet.no-ip.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).