** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628286
Title:
[utils] DBus rules enforce stricter ordering of dbus attributes
To
Committed as r3634
** Changed in: apparmor
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628286
Title:
[utils] DBus rules enforce stricter ordering of
** Branch linked: lp:apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628286
Title:
[utils] DBus rules enforce stricter ordering of dbus attributes
To manage notifications about this bug go
I submitted my patch to the list:
https://lists.ubuntu.com/archives/apparmor/2017-February/010537.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628286
Title:
[utils] DBus rules enforce
Feel free to send out what you have now (with a "just FYI, WIP" note) -
maybe I can help in some details.
For "my" invalid rule: Well, I managed to pick an example that is "more
invalid" than yours ;-)
What I wanted to know is - if there's another parameter between two bus=...
parameters, will
On 01/27/2017 12:05 PM, Christian Boltz wrote:
> FYI: FileRule accepts the permissions in any order, so maybe you could
> look at how it's done there. (Needless to say that having a list of
> possible permissions is easier to handle, but maybe it helps
> nevertheless.)
I'll have a look at that.
> It is too bad that all of the
> profiles have to be fully parsed just to use basic utilities that don't
> necessarily care about the rules inside of a profile.
The main problem is that we allow "random" filenames for the profiles,
so we need to check all files for the to-be-changed profile -
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: apparmor
Status: Triaged => In Progress
** Changed in: apparmor
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Assignee:
On 01/24/2017 06:13 AM, Christian Boltz wrote:
> 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
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
I'm bumping the importance of the upstream AppArmor task to high. I
think this regression is going to affect a considerable number of users
since there has never been a restriction on the ordering of dbus rule
components.
** Changed in: apparmor
Importance: Medium => High
--
You received
Adding an apparmor-easyprof-ubuntu task because the Python utilities in
AppArmor 2.11.0 can't handle some of the dbus rules that it generates.
I'm hoping that we can work around this regression in the Python utils
in the meantime. This bug renders the Python utils useless when certain
packages
** Also affects: apparmor-easyprof-ubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628286
Title:
[utils] DBus rules enforce stricter
13 matches
Mail list logo
