aa-disable

Disable AppArmor security profiles

TLDR

Disable a profile

$ sudo aa-disable [path/to/profile]

Disable multiple profiles

$ sudo aa-disable [path/to/profile1] [path/to/profile2]

Disable profiles in a directory

$ sudo aa-disable --dir [path/to/profiles]

Disable a profile without reloading the policy

$ sudo aa-disable --no-reload [path/to/profile]

SYNOPSIS

aa-disable executable [executable ...] [-d /path/to/profiles] [--no-reload]

aa-disable is used to disable one or more AppArmor profiles. This command will unload the profile from the kernel and prevent the profile from being loaded on AppArmor startup.A symbolic link to the profile is created in /etc/apparmor.d/disable/, which keeps the profile from being loaded automatically when AppArmor is restarted. The profile file itself remains in /etc/apparmor.d but is not active. Use aa-enforce or aa-complain to re-enable a disabled profile.

PARAMETERS

-d, --dir /path/to/profiles

Specifies the directory containing AppArmor profiles; defaults to /etc/apparmor.d

--no-reload

Do not reload the profile after modifying it

INSTALL

sudo apk add apparmor-utils

sudo zypper install apparmor-utils

nix profile install nixpkgs#apparmor-utils

CAVEATS

Disabling a profile removes security protections for the associated application. The application will run without AppArmor confinement until the profile is re-enabled.