buggy apparmor profile
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Fix Released
|
Medium
|
Olivier Tilloy |
Bug Description
Nibaldo González has reported that the LibreOffice AppArmor profile has mistakes in it:
https:/
> In this case, AppArmor grants write and read permissions to files with
> extension: '.#.txt', '.#All', '.the', '.format', '.#.xml', '.and',
> etc. Clearly, the profile must be fixed.
I've confirmed this via apparmor_parser -Qd output on a slightly modified
version of the source file:
$ apparmor_parser -Qd < foo | grep '#'
Warning from stdin (line 1): apparmor_parser: cannot use or update cache, disable, or force-complain via stdin
Mode: rwak: Name: ({/home/
The comments on the variable assignment lines are carried through to the
policy.
Thanks
Changed in libreoffice (Ubuntu): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in libreoffice-l10n (Ubuntu): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in libreoffice (Ubuntu): | |
assignee: | Olivier Tilloy (osomon) → nobody |
assignee: | nobody → Olivier Tilloy (osomon) |
status: | Confirmed → Fix Released |
no longer affects: | libreoffice-l10n (Ubuntu) |
And a corresponding bug in the AppArmor project in case we wish to handle it there instead:
https:/ /bugs.launchpad .net/apparmor/ +bug/1741584