Open roddhjav opened 1 week ago
The plan is to uses
attach_disconnect.path
by default and automatically on all profiles with theattach_disconnect
flag. The attached path is set to a@{att}
, a new dynamically generated variable set at build time in the preamble of all profile to be:* `@{att}=/att/<profile_name>` for profile with `attach_disconnect` flag. * `@{att}=/` for other profiles
This is what I don't understand. @{att}=/att/<profile_name>
is for profiles with the attach_disconnect
flag - okay. But @{att}=/
for other profiles, i.e. without the attach_disconnect
flag? Why should this be needed for such profiles at all? That sounds to me like a oxymoron :)
As @{att}
can be used in abstraction, profile without the attach_disconnect
flag need to have the variable defined. It is mostly a safety measure to ensure the profiles compile.
Ah, understood! Thanks!
As
@{att}
can be used in abstraction, profile without theattach_disconnect
flag need to have the variable defined. It is mostly a safety measure to ensure the profiles compile.
Why not @{att}=/giekxhayfnjdhaeb
?
For more context, see https://apparmor.pujol.io/development/internal/#re-attached-path
AppAmor 4.0 provides the
attach_disconnect.path
flag allowing to reattach this path to a prefix that is not/
. When used it provides an important security improvement from AppArmor 3.0.The plan is to uses
attach_disconnect.path
by default and automatically on all profiles with theattach_disconnect
flag. The attached path is set to a@{att}
, a new dynamically generated variable set at build time in the preamble of all profile to be:@{att}=/att/<profile_name>
for profile withattach_disconnect
flag.@{att}=/
for other profiles@{att}=/
Internal
abstractions/attached/base
abstractionabstractions/attached/consoles
abstractionattach
build tasks:attach_disconnected.path
flag on all profile with theattach_disconnected
flagattached/base
abstraction in the profile@{att}=/
Tasks
attach_disconnect
have been updated to use@{att}
when required.558
557
555