Well, up to 2.10 dbus rule handling in the tools was simply matching for "dbus.*," and writing the line back to the profile without any changes. I'm not sure if I'd call full support for dbus rules (including handling of log events) a regression ;-) but I understand that it's annoying.
Writing a "real" parser in the python code would be quite some work, so - how difficult would it be to make apparmor_parser's code to parse dbus rules available via libapparmor? (Or a separate libapparmor_parser or libapparmor_private if you worry about including too much in libapparmor.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1628286 Title: [utils] DBus rules enforce stricter ordering of dbus attributes Status in AppArmor: Triaged Status in apparmor-easyprof-ubuntu package in Ubuntu: In Progress Bug description: The DBus rules data strutures added recently (after the 2.10.95 beta 1 release) include a more strcit interpretation of dbus attribute ordering than before and is more strict than the parser: [parser]$ cat /tmp/aa-test-dir/test.profile profile t /t { dbus (receive, send) path=/com/canonical/UbuntuAppLaunch/* bus=session, } [parser]$ ./apparmor_parser -QK -d /tmp/aa-test-dir/test.profile ----- Debugging built structures ----- Name: t Profile Mode: Enforce dbus ( send receive ) bus="session" path="/com/canonical/UbuntuAppLaunch/*", [parser]$ ./apparmor_parser --version AppArmor parser version 2.10.95 Copyright (C) 1999-2008 Novell Inc. Copyright 2009-2012 Canonical Ltd. [parser]$ cd ../utils/ [utils]$ PYTHONPATH=. python3 ./aa-logprof -d /tmp/aa-test-dir Reading log entries from /var/log/syslog. Updating AppArmor profiles in /tmp/aa-test-dir. ERROR: Invalid or unknown keywords in 'dbus (receive, send) path=/com/canonical/UbuntuAppLaunch/* bus=session To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1628286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp