Related Documentation
Introduction
Firejail is an application sandboxing tool
AppArmor Integration
Firejail has integrated basic support for AppArmor policy.
Firejail uses a single apparmor profile (this is different than firejail profiles) for all jails.
and can apply the firejail apparmor profile if the jail is started with the --apparmor
command line flag.
firejail --apparmor --seccomp firefox
transitions to firejail-default
at exec (aa_change_onexec)
Modifying the firejail-default profile
???
Check if firejail is built with AppArmor support
???
Configure and Build firejail
To configure and build firejail with AppArmor support
...
Interactions with AppArmor
While the firejail sandboxing tool provides basic AppArmor integration it actually weakens AppArmor protections for application.
single profile
All applications run under filejail when using the integrated AppArmor support use the same profile, regardless of whether an AppArmor profile for the applications exists. This means AppArmor restrictions can not be tailored to each application. It also means any communication mediation based on the confinement label have to treat all firejailed applications the same.
mount namespaces
seccomp
nonewprivs
Alternate way to use firejail with AppArmor
Because of the ways that the firejail sandbox interacts with AppArmor policy using --apparmor
is not recommended.
AppArmor's profile attachment can be used instead.
How to use AppArmor profile attachment
create a firejail profile - to block firejail from using apparmor
Because of mount namespaces
- alternate profiles
setup profile transitions