DEP8: Invalid capability setuid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apparmor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Excuses is showing apparmor failing dep8 tests when they are triggered by another package.
last time apparmor was uploaded was on May 14th, and this is the package under test:
https:/
The errors are like this:
FAIL: test_profile_
-------
Traceback (most recent call last):
File "/tmp/tmp.
return unittest_func(self)
File "./caching.py", line 448, in test_profile_
self.
File "./caching.py", line 257, in _generate_
self.
File "/tmp/tmp.
self.
AssertionError: 1 != 0 : Got return code 1, expected 0
Command run: ../apparmor_parser --config-
Output: AppArmor parser error for /tmp/aa-
tags: | added: update-excuses |
tags: | added: update-excuse |
I think the problem might be an unnecessary backslash in common/Make.rules:
CAPABILITIES= $(shell echo "\#include <linux/ capability. h>" | cpp -dM | LC_ALL=C sed -n -e '/CAP_EMPTY_SET/d' -e 's/^\#define[ \t]\+CAP_ \([A-Z0- 9_]\+\) [ \t]\+\( [0-9xa- f]\+\)\ (.*\)$$ /CAP_\1/ p' | LC_ALL=C sort)
I wrote a dummy makefile to test this and $(CAPABILITIES) was empty. Changing to this:
CAPABILITIES= $(shell echo "#include <linux/ capability. h>" | cpp -dM | LC_ALL=C sed -n -e '/CAP_EMPTY_SET/d' -e 's/^\#define[ \t]\+CAP_ \([A-Z0- 9_]\+\) [ \t]\+\( [0-9xa- f]\+\)\ (.*\)$$ /CAP_\1/ p' | LC_ALL=C sort)
gives what I think is the expected output.