Hello, Am Montag, 2. Oktober 2017, 17:17:53 CEST schrieb Vincas Dargis: > On 2017.10.02 02:19, John Johansen wrote: > > I believe it was a deliberate decision by the author to not support > > the confusing syntax of mixed characters.
Right, that's an (intended) side effect of rewriting the file rule handling in 2.11, and IIRC this is the first time someone actually had a problem with this decision. > > The parser's support is > > much older and has not been patched to conform with the above > > mentioned decision, ideally it should be reporting that the syntax > > is deprecated I'm not sure if this is worth the effort - I'd have to extend the regex to allow the deprecated rules, add checks for the deprecated variants etc. Handling file rules is already complex enough ;-) If more people run into this, well, maybe. But with only one report of a "mixed case" fallback exec rule, it's easier to handle by doing manual user support ;-) BTW: I just updated the wiki page and added a deprecation notice for "mixed case" fallback exec rules. > I guess I could create bug / feature request against apparmor_parser, > about emitting warning when `Pux` is used in profile. Yes, please do. Regards, Christian Boltz -- Bugzilla beißt nicht und ist viel, viel netter als ich. ;) [Lars Müller in opensuse-de]
signature.asc
Description: This is a digitally signed message part.
-- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
