chmod: creator owner victimized? ... (1.7.35-0.4)

Corinna Vinschen corinna-cygwin@cygwin.com
Thu Feb 26 00:12:00 GMT 2015


On Feb 25 22:04, Houder wrote:
> > Hi Henri,
> >
> > On Feb 25 20:23, Houder wrote:
> >> Hi Corinna,
> >>
> >> Ref: https://cygwin.com/ml/cygwin/2015-02/msg00798.html
> >>  - [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.4
> >>
> >> Something for your list of things to think about ... and do later ;-)
> >>
> >> For a directory, the 'creator owner' should have sufficient permissions. That is, at least 'full control
> >> minus delete'; full control is good. (yes, as far as I can tell)
> >
> > Yeah, I noticed that problem myself a few hours ago and applied a fix in
> > the meantime.  In CVS, the chmod workaround does not touch the CREATOR
> > OWNER, CREATOR GROUP and Everyone default ACEs anymore.  I'll create a
> > snapshot and another test release soon.
> 
> Good ...
> 
> For the record: in addition to RX, W and DC, at least take ownership should
> be present, I believe.
> 
> Otherwise, chown will bark. (the example below uses setfacl)

It won't complain in this case, afaics, but having all standard access
rights for the default owner entry was the desired result nevertheless.
I fixed that in CVS.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20150226/8d9be4dc/attachment.sig>


More information about the Cygwin mailing list