This is more of a bug in firefox and evinve. They are relying on
trunc("/some/path") working after the file has been deleted, instead
they should be using trunc(fd). There use of trunc is incorrect even
though it has traditionally worked because it may not get the file
pointed to by the fd. If a new file is created at /some/path while fd
is open (but deleted) the trunc will apply to the new file, not the open
fd as is intended by their use. Further more if the parent (gp, ..)
directory is moved the trunc will also fail.
Unfortunately this behavior does need to be fixed in AppArmor because it
can break applications with no potential work around except to disable
AppArmor mediation of the application.
--
apparmor disallows truncate of deleted file
https://bugs.launchpad.net/bugs/451375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
