Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot confine using apparmor on Arch linux LTS kernel #3987

Closed
virgilhem opened this issue Feb 13, 2021 · 3 comments
Closed

cannot confine using apparmor on Arch linux LTS kernel #3987

virgilhem opened this issue Feb 13, 2021 · 3 comments
Labels
notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail

Comments

@virgilhem
Copy link

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.

@glitsj16
Copy link
Collaborator

Don't know if this is a distro specfic issue.

I can confirm your observations on Arch Linux with linux-lts 5.4.98. Luckily linux-lts 5.10.16 is 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
Copy link
Author

FYI the issue has been reported upstream:
https://gitlab.com/apparmor/apparmor/-/issues/150

@rusty-snake
Copy link
Collaborator

rusty-snake commented Aug 4, 2021

FYI https://gitlab.com/apparmor/apparmor/-/issues/150 was closed last week.

@kmk3 kmk3 added the notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail label Feb 7, 2024
@kmk3 kmk3 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notourbug The issue is valid, but it isn't directly caused by (or cannot be fixed by) firejail
Projects
None yet
Development

No branches or pull requests

4 participants