This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Silly ACL problems [Was: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin]
- To: cygwin-developers at sources dot redhat dot com
- Subject: Re: Silly ACL problems [Was: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin]
- From: Corinna Vinschen <vinschen at redhat dot com>
- Date: Sun, 5 Aug 2001 21:52:33 +0200
- References: <3B63432E.6050309@ece.gatech.edu> <3B649305.2090302@ece.gatech.edu> <3B64C0A9.1080700@ece.gatech.edu> <3B64F567.6060304@ece.gatech.edu> <3B65835C.9000001@ece.gatech.edu> <3B65A2B8.90702@ece.gatech.edu> <3B66CC47.8040704@ece.gatech.edu> <3B6711C9.6050700@ece.gatech.edu> <3B6C3A4F.3070502@ece.gatech.edu> <3B6D9D32.1050600@ece.gatech.edu>
- Reply-To: cygdev <cygwin-developers at cygwin dot com>
On Sun, Aug 05, 2001 at 03:23:30PM -0400, Charles Wilson wrote:
> Well, it looks like the script below DOES cause some problems. I just
> installed the new ash and binutils packages using setup. However: I
> can't execute them.
>
> Here's the ACL for /bin (prior to running setup to install the new ash)
>
> # file: bin
> # owner: 500
> # group: 513
> user::rwx
> group::rwx
> mask::rwx
> other::r-x
> default::mask::---
>
> After installing ash (as Administrator), the ACL for sh.exe:
>
> # file: sh.exe
> # owner: 544
> # group: 513
> user::rwx
> group::---
> group:18:rwx
> mask::---
> other::---
>
> I can fix this (by hand, after logging BACK in as Administrator), but
> what went wrong?
Nothing, I think. Setup is a non-Cygwin tool so it has nothing
to do with ntsec. Since the ACL of /bin doesn't inherit it's
permissions, newly created files get a default DACL which is
identical to what you see above if your account has admin privs.
This reminds me that setting the default DACL could be a useful
extension to the create_token() code...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.