Version: (using KDE KDE 3.5.3) Installed from: Debian testing/unstable Packages (Note: I tried with Debian testing, backport to Debian stable, and some SuSE packages, the problem is not Debian specific. Also, it seems 3.5.0 has the same behaviour.) When copying files around, konqueror has a bit annoying behaviour when the target directory has default acl set: * when the source file has no acl, the default acl of the target directory are applied to the newly created file. * when the source file does have acl, those are copied to the new file. The default acl of the target directory is not applied to the new file. Some older KDE version (not sure - 3.4.x or 3.3.x) did not have this problem - probably because it just didn't care about acls. In my view, this behaviour is inconsistant (when I view unix permissions + acl as the set of applicable permissions - the users don't really care that unix permissions and acl have different historical background), and also defeats the idea of having default acl on directories. Just FYI - why did we notice: Our usecase where we relied on the old behaviour is that we use shared directories as mailslots - publish files by copying them to directories with appropriate default acl so that the files become readable by the target audience.
I can confirm this above descibed bug is still there in kde 3.5.5 and is really annoying. This might also be a security leak, as the acl's and permissions are used to limit access to the given files.
*** This bug has been confirmed by popular vote. ***
Still present in 3.5.7, anybody yet tested 3.5.8?
Btw, my "solution" is to just leave acl handling to the kernel, see patch. Not sure if this is the correct solution.
Created attachment 22053 [details] kernel knows best.
Till? This appears to be your code.
Just a quick note: I'm not working in an environment that uses acls anymore, and this bug dates back to KDE 3.x. I guess if KDE 4 still misbehaves, somebody can just open a new bug, there's nothing of value in here.