On Aug 28 21:00, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> >> > It's what "acl" means on Cygwin.  "acl" means that Windowsd ACLs are used
> >> > and permissions are handled and converted to and from POSIX permissions.
> >> > "noacl" means, Cygwin ignores all ACLs and fakes ownership and POSIX
> >> > permissions only based only on filetype and DOS R/O attribute, as it has
> >> > to on filesystems not supporting ACLs, like FAT/FAT32.
> >> 
> >> Got it.
> >> It seems, Cygwin need a middle groung between these two for cases, where FS
> >> support access control, but don't want to be mangled.
> 
> > I'm certainly not going to introduce another mount mode.
> 
> I didn't said it has to be mount mode... besides, it doesn't make sense to
> implement YA mode to do what is already done, just a little different.
> 
> > What Cygwin could do is to perform ACL-based access checks independently of
> > the "acl"/"noacl" mount mode on FSes supporting ACLs.  However, if you want
> > ACLs, why not use the "acl" mount mode in the first place?
> 
> ACL inheritance, mostly. POSIX'ized permissions break inheritance on newly
> created files, at times making these files inaccessible to native
> applications, even though inheritance rules would allow it otherwise.
> 
> > Still, it *might* makes sense in some scenarios, even if the results of
> > stat(2)/acl(2) may differ surprisingly from what access(2) returns.
> 
> > We can also simply try it out.  A patch to enable this behaviour is
> > dead-simple.
> 
> > Here's the prerequisite:
> 
> >   Would more than one person want that *and* be willing to give this a
> >   *thorough* testing?
> 
> I'd like to hear out expected behavior from this patch first.

Same output from stat(2), different output from access(2).  Access(2)
would only take the actual Windows ACL into account and let Windows
functions decide about granting or denying the requested access.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpHtJIogdk1V.pgp
Description: PGP signature

Reply via email to