mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3987] cannot confine using apparmor on Arch linux LTS kernel #2494
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2494
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @virgilhem on GitHub (Feb 13, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3987
Since a recent kernel update I got the error "Warning: Cannot confine the application using AppArmor" when using the "--apparmor" flag"
The verification performed in src/firejail/sandbox.c failed with the error EINVAL:
test.c:
#include <sys/apparmor.h>
#include <stdio.h>
int main() {
if(aa_change_onexec("firejail-default")<0) { perror(NULL); }
}
$ gcc -lapparmor test.c
$ ./a.out
Invalid argument
Still the "aa-status" command shows that the firejail-default profile is correctly loaded in the kernel.
Don't know if this is a distro specfic issue.
@ghost commented on GitHub (Feb 16, 2021):
I can confirm your observations on Arch Linux with linux-lts
5.4.98.Luckily linux-lts5.10.16is in testing so I tried that as well and that works as expected (no output from your test.c). Looks like a kernel issue IMO.@virgilhem commented on GitHub (Mar 2, 2021):
FYI the issue has been reported upstream:
https://gitlab.com/apparmor/apparmor/-/issues/150
@rusty-snake commented on GitHub (Aug 4, 2021):
FYI https://gitlab.com/apparmor/apparmor/-/issues/150 was closed last week.