Apache OpenOffice (AOO) Bugzilla – Issue 31890
file system ACLs are ignored when opening files
Last modified: 2013-02-07 22:42:39 UTC
Our company uses file system ACLs on a XFS file system and over NFS with the appropriate nfs-acl patches. However, OpenOffice.org ignores the ACLs when opening files and only looks at the traditional Unix file permissions to figure out if a file can only be opened in read-only mode. Here's an example: 0 mbunkus@ls-bs-ws6:~$ ls -l helloworld.sxw -rw-rw-r--+ 1 root root 5127 Jul 22 09:44 helloworld.sxw 0 mbunkus@ls-bs-ws6:~$ getfacl helloworld.sxw # file: helloworld.sxw # owner: root # group: root user::rw- user:mbunkus:rw- group::rw- mask::rw- other::r-- This file is opened in read-only mode although the user mbunkus has write access. This can be verified with a simple 'echo 1 > helloworld.sxw' (after making a backup, of course). Using 'chmod o+w' on the file causes OpenOffice.org to open it in read/write mode. This issue severly limits OOo's usability in multi user environments.
Confirmed.
TM->BH: Due to the fact that OOo isn´t (and has never been) able to handle ACL´s correctly, I changed this to enhancement. Please have a look, thanks !
I'm sorry, but I disagree. The point is not that OOo should be able to _handle_ ACLs. The point is that OOo _thinks_ that it may not write a file and enters read only mode while it actually _may_ write it. If it would just try to open th e file for writing it would see that this is indeed possible. We users using ACLs would be happy, OOo wouldn't have to handle ACLs.
I think this is the same problem as in Bug #96918 and this is a major issue.
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".