[Bug 1226356] Re: explicit deny rules do not silence logging denials
Tyler Hicks
tyhicks at canonical.com
Tue Sep 24 20:59:08 UTC 2013
Hi John - I think I've got a handle on this bug (patches are about to go
out to the mailing list), but here's the output you requested:
$ echo "/t { deny dbus, }" | apparmor_parser -qQD expr-tree -D dfa-node-
map
DFA: Expression Tree
(\ ([^\0000])*\0000([^\0000])*<64>|\ ([^\0000])*\0000([^\0000])*\0000([^\0000])*\0000([^\0000])*\0000([^\0000])*\0000([^\0000])*((<2>|<4>)|<64>))
Mapping of States to expr nodes
State <= Nodes
-------------------
0 <= {0x22fca60,0}
1 <= {0x22fcdc0,0}
2 <= {0x22fcd60,0}
3 <= {0x22ffdc0,0x22ffc60}
4 <= {0x2300000,0}
5 <= {0x2300580,0}
6 <= {0x2300690,0}
7 <= {0x23007e0,0x23006b0}
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1226356
Title:
explicit deny rules do not silence logging denials in dbus and mount
rules
Status in “apparmor” package in Ubuntu:
Triaged
Status in “dbus” package in Ubuntu:
Invalid
Status in “apparmor” source package in Saucy:
Triaged
Status in “dbus” source package in Saucy:
Invalid
Bug description:
I have this rule in my profile:
# We want to explicitly deny access to NetworkManager
deny dbus (send)
bus=system
path=/org/freedesktop/NetworkManager,
but with this rule, I still see these denials:
Sep 17 01:03:02 ubuntu-phablet dbus[622]: apparmor="DENIED" operation="dbus_method_call" bus="system" name="org.freedesktop.NetworkManager" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" pid=3201 profile="net.launchpad.ubuntu-security.ubuntu-sdk-1310-api-demos_ubuntu-sdk-1310-api-demos_0.1" peer_pid=1154 peer_profile="unconfined"
Sep 17 01:03:02 ubuntu-phablet dbus[622]: apparmor="DENIED" operation="dbus_method_call" bus="system" name="org.freedesktop.NetworkManager" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="GetDevices" mask="send" pid=3201 profile="net.launchpad.ubuntu-security.ubuntu-sdk-1310-api-demos_ubuntu-sdk-1310-api-demos_0.1" peer_pid=1154 peer_profile="unconfined"
Another one is this deny rule:
deny dbus send bus=session
interface="org.gnome.GConf.Server",
with these denials:
Sep 16 17:37:58 localhost dbus[16510]: apparmor="DENIED" operation="dbus_method_call" bus="session" name="org.gnome.GConf" path="/org/gnome/GConf/Server" interface="org.gnome.GConf.Server" member="GetDefaultDatabase" mask="send" pid=15037 profile="net.launchpad.ubuntu-security.ubuntu-sdk-1310-api-demos_ubuntu-sdk-1310-api-demos_0.1" peer_pid=16736 peer_profile="unconfined"
While this isn't a 'high' priority because the accesses are still
being denied, it is a bug and the lack of silencing may cause
confusion for users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1226356/+subscriptions
More information about the foundations-bugs
mailing list