Subject: Re: RM disregards file level permissions and uses directory
permissions instead.
Eric Blake wrote:
> According to James J. Perry on 4/16/2008 4:25 PM:
> | We are in the cutover process and one of the DBAs found this
behavior.
> | If testfile1 is owned by usera:group1 in a parent
Eric Blake wrote:
> According to James J. Perry on 4/16/2008 4:25 PM:
> | We are in the cutover process and one of the DBAs found this behavior.
> | If testfile1 is owned by usera:group1 in a parent directory with
> | permissions 777 owned by usera:group1, userb:group2 can delete testfile1
> | even
Eric Blake wrote:
In particular, the EACCES errors on unlink() mention that without the
sticky bit, all you need is write access to the directory (and your
directory is world writable); with the sticky bit set, you must also own
the directory and file.
^^^
To stave off confusion.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to James J. Perry on 4/16/2008 4:25 PM:
| We are in the cutover process and one of the DBAs found this behavior.
| If testfile1 is owned by usera:group1 in a parent directory with
| permissions 777 owned by usera:group1, userb:group2 can del
We are in the cutover process and one of the DBAs found this behavior.
If testfile1 is owned by usera:group1 in a parent directory with
permissions 777 owned by usera:group1, userb:group2 can delete testfile1
even if testfile1 has permissions 600. Conversely if the same parent
directory has permis
