[apparmor] [Bug 732837] Re: AF_TIPC not supported by parser when it is in the kernel
john.johansen at canonical.com
Thu Mar 10 21:04:56 UTC 2011
There were several families being screened out because they caused build
failures under previous releases. This is no longer the case and I have
attached a proposed patch
** Patch added: "aa.patch"
You received this bug notification because you are a member of AppArmor
Developers, which is the registrant for AppArmor.
AF_TIPC not supported by parser when it is in the kernel
Status in AppArmor Linux application security framework:
If in python I do something like:
s = socket.socket(socket.AF_TIPC, socket.SOCK_RDM, 0)
I see this in the audit log:
type=AVC msg=audit(1299788719.107:159859): apparmor="DENIED" operation="create" parent=17142 profile="/home/jamie/tmp/test-net.py" pid=17143 comm="test-net.py" family="tipc" sock_type="rdm" protocol=0
If I then try to add rules for this in my profile:
$ sudo apparmor_parser -r -T -W /etc/apparmor.d/home.jamie.tmp.test-net.py
AppArmor parser error for /etc/apparmor.d/home.jamie.tmp.test-net.py in /etc/apparmor.d/home.jamie.tmp.test-net.py at line 39: Invalid network entry.
Leaving out the 'network tipc,' rule, but leaving 'rdm', the parser is ok, but I still get denials:
type=AVC msg=audit(1299789277.284:159863): apparmor="DENIED" operation="create" parent=17339 profile="/home/jamie/tmp/test-net.py" pid=17340 comm="test-net.py" family="tipc" sock_type="rdm" protocol=0
More information about the AppArmor