Defining a profile name/path via the @{exec_path} variable
Some time ago I asked about a problem that happened after an AppArmor update (2.13.1 => 2.13.2). It was about the following AA profile snippet which is used in all of my profiles:
#include <tunables/global>
@{exec_path} = /{usr/,}bin/app
profile app @{exec_path} {
@{exec_path} mr,
#include if exists <local/app>
}
I even forgot about this since I have the apparmor-utils
and python3-apparmor
packages in version 2.13.1-3+b1
(in the hold state). But recently my friend asked me why my profiles don't work in his system, and he said the problem was the @{exec_path}
variable.
Is there any progress on this subject?
Edited by Mikhail Morfikov