[apparmor] [patch] make parser's definition of allowed var names consistent

Christian Boltz apparmor at cboltz.de
Mon Mar 28 11:24:51 UTC 2011


Am Montag, 28. März 2011 schrieb Steve Beattie:
> [This patch is nominated for trunk and 2.6.2.]
> The parser's lexer supports variables defined matching the regex
> '[[:alpha:]][[:alnum:]_]*' (i.e. a single alpha followed by any
> number of alphanumerics or underscores). Unfortunately, the code
> that expends variables inside a profile does not match this, it
> incorrectly matched '([[:alpha:]]|_)+' (one or more alphas or
> underscores). This patch corrects the [...]
> apparmor.vim syntax file.

Applied to apparmor.vim.in so that it doesn't get lost with the next 
generation of apparmor.vim.

That said: "Hiding" apparmor.vim patches in a big mail is a bit risky - 
if I overlook them, my next version of apparmor.vim will not contain the 

(Which brings us back to the question if I should move apparmor.vim and 
the files to generate it in some public version control system...)


Christian Boltz
> Äh - stehe ich auf dem Schlauch? Sehe ich das Problem eigentlich
> nicht?  ImageMagick mit "system" aufrufen und schlicht und einfach
> den Return-Code auswerten?
Das ruft IM über die Shell auf. Mit der Methode wird die Kiste noch
bis zur nächsten Eiszeit rechnen. :-)
[> Stefan Hundhammer und Ratti in suse-programming]

More information about the AppArmor mailing list