I think this bug needs to state clearly what was the old behavior with apparmor 4, then we have the current parser error with the same rule, and what the new beavior will be after this patch.
And by behavior, I don't mean just "before it was parsed, now it isn't, and with the patch it will be parsed again". What needs to be shown is: - how was it parsed before with apparmor 4? What was the end result of that rule with this syntax, was it a bogus rule? Undefined behavior? What did it match against exactly? - how is that same rule going to be parsed after the patch? In the exact same (perhaps even broken) way? What will it match against exactly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126450 Title: AppArmor Unix socket rules need to be able to support addr=@{a,b} variable usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2126450/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
