AppArmor

aa-enforce|complain leaves temporary files after it fails

Bug #1785403 reported by Vincas Dargis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
New
Undecided
Unassigned

Bug Description

On Debian Sid with AppArmor 2.13, temporary files like `usr.lib.libreoffice.program.soffice.binzrz7ukcd~` are left after failure.

```
$ ls usr.lib.libreoffice.program.soffice.bin*
usr.lib.libreoffice.program.soffice.bin
$ sudo aa-enforce usr.lib.libreoffice.program.soffice.bin
Setting /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin to enforce mode.

ERROR: Path doesn't start with / or variable: gpg
$ ls usr.lib.libreoffice.program.soffice.bin*
usr.lib.libreoffice.program.soffice.bin usr.lib.libreoffice.program.soffice.binzrz7ukcd~
```

These files appear on every failed `aa-enforce` and `aa-complain` run.

Vincas Dargis (talkless)
summary: - aa-enforce leaves temporary files when it fails
+ aa-enforce|complain leaves temporary files when it fails
summary: - aa-enforce|complain leaves temporary files when it fails
+ aa-enforce|complain leaves temporary files after it fails
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.