[GH-ISSUE #4393] BUG// apparmor protection failed #2648

Closed
opened 2026-05-05 09:18:37 -06:00 by gitea-mirror · 11 comments
Owner

Originally created by @osevan on GitHub (Jul 7, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4393

Running firejail 0.65 in kernel 5.11 rt

Buster and bullseye box

With Apparmor support enabled at compile time with configure flag.

I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile .
Example chrome and Firefox .

But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes.

Maybe Apparmor library not works inside firejail?

I tested on bullseye and buster.

Originally created by @osevan on GitHub (Jul 7, 2021). Original GitHub issue: https://github.com/netblue30/firejail/issues/4393 Running firejail 0.65 in kernel 5.11 rt Buster and bullseye box With Apparmor support enabled at compile time with configure flag. I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile . Example chrome and Firefox . But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes. Maybe Apparmor library not works inside firejail? I tested on bullseye and buster.
gitea-mirror 2026-05-05 09:18:37 -06:00
  • closed this issue
  • added the
    notabug
    label
Author
Owner

@rusty-snake commented on GitHub (Jul 8, 2021):

Running firejail 0.65

There is no 0.65 firejail release. Guess you mean 0.9.65, but this is out of date.
Latest release: 0.9.66
Latest git: 0.9.67
If you compile firejail from source, you need to regularly do this.

I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile .
Example chrome and Firefox .

But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes.

So running firejail --apparmor firefox & firejail --apparmor evince and then sudo aa-status shows only firefox, right?

<!-- gh-comment-id:876142353 --> @rusty-snake commented on GitHub (Jul 8, 2021): > Running firejail 0.65 There is no 0.65 firejail release. Guess you mean 0.9.65, but this is out of date. Latest release: 0.9.66 Latest git: 0.9.67 If you compile firejail from source, you need to regularly do this. > I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile . >Example chrome and Firefox . > >But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes. So running `firejail --apparmor firefox & firejail --apparmor evince` and then `sudo aa-status` shows only firefox, right?
Author
Owner

@osevan commented on GitHub (Jul 9, 2021):

Running firejail 0.65

There is no 0.65 firejail release. Guess you mean 0.9.65, but this is out of date.
Latest release: 0.9.66
Latest git: 0.9.67
If you compile firejail from source, you need to regularly do this.

I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile .
Example chrome and Firefox .
But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes.

So running firejail --apparmor firefox & firejail --apparmor evince and then sudo aa-status shows only firefox, right?

With apparmor in evince.profile not direct flag --apparmor

aa-status cant recognize firejail-default for evince

<!-- gh-comment-id:877021816 --> @osevan commented on GitHub (Jul 9, 2021): > > Running firejail 0.65 > > There is no 0.65 firejail release. Guess you mean 0.9.65, but this is out of date. > Latest release: 0.9.66 > Latest git: 0.9.67 > If you compile firejail from source, you need to regularly do this. > > > I can detect with sudo aa-status ,if firejail-default profile running for Apparmor , when apparmor flag is inside profile . > > Example chrome and Firefox . > > But I figured out with mupdf, evince and qpdfview with apparmor flag inside, sudo aa-status cant detect firejail-default for these sandboxes. > > So running `firejail --apparmor firefox & firejail --apparmor evince` and then `sudo aa-status` shows only firefox, right? With apparmor in evince.profile not direct flag --apparmor aa-status cant recognize firejail-default for evince
Author
Owner

@rusty-snake commented on GitHub (Jul 9, 2021):

With apparmor in evince.profile not direct flag --apparmor

So apparmor in evince.profile does not work but --apparmor works?

<!-- gh-comment-id:877085993 --> @rusty-snake commented on GitHub (Jul 9, 2021): > With apparmor in evince.profile not direct flag --apparmor So `apparmor` in evince.profile does not work but `--apparmor` works?
Author
Owner

@osevan commented on GitHub (Jul 9, 2021):

I have not tested --apparmor.

I can test at night.

But yes,apparmor inside profile placed, but, not triggered by aa-status

<!-- gh-comment-id:877150608 --> @osevan commented on GitHub (Jul 9, 2021): I have not tested --apparmor. I can test at night. But yes,apparmor inside profile placed, but, not triggered by aa-status
Author
Owner

@rusty-snake commented on GitHub (Jul 9, 2021):

Buster and bullseye box

This happen in Debian Buster and Debian Bullseye? Or do you mean a FrankenDebian?

Maybe Apparmor library not works inside firejail?

If it works for firefox ...

I have not tested --apparmor.
I can test at night.

Probably best to post the output of aa-status.

sudo aa-status cant detect firejail-default for these sandboxes.

Are they really running inside firejail (firejail --list)?

<!-- gh-comment-id:877242703 --> @rusty-snake commented on GitHub (Jul 9, 2021): > Buster and bullseye box This happen in Debian Buster and Debian Bullseye? Or do you mean a [FrankenDebian](https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian)? > Maybe Apparmor library not works inside firejail? If it works for firefox ... > I have not tested --apparmor. I can test at night. Probably best to post the output of `aa-status`. > sudo aa-status cant detect firejail-default for these sandboxes. Are they really running inside firejail (`firejail --list`)?
Author
Owner

@osevan commented on GitHub (Jul 10, 2021):

Buster and bullseye box

This happen in Debian Buster and Debian Bullseye? Or do you mean a FrankenDebian?

Maybe Apparmor library not works inside firejail?

If it works for firefox ...

I have not tested --apparmor.
I can test at night.

Probably best to post the output of aa-status.

sudo aa-status cant detect firejail-default for these sandboxes.

Are they really running inside firejail (firejail --list)?

Of course they run

<!-- gh-comment-id:877583824 --> @osevan commented on GitHub (Jul 10, 2021): > > Buster and bullseye box > > This happen in Debian Buster and Debian Bullseye? Or do you mean a [FrankenDebian](https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian)? > > > Maybe Apparmor library not works inside firejail? > > If it works for firefox ... > > > I have not tested --apparmor. > > I can test at night. > > Probably best to post the output of `aa-status`. > > > sudo aa-status cant detect firejail-default for these sandboxes. > > Are they really running inside firejail (`firejail --list`)? Of course they run
Author
Owner

@rusty-snake commented on GitHub (Jul 16, 2021):

Of course they run

The thing is that I can not explain what can cause apparmor to apply to firefox but not to evince except for evince not running in firejail.

<!-- gh-comment-id:881320695 --> @rusty-snake commented on GitHub (Jul 16, 2021): > Of course they run The thing is that I can not explain what can cause `apparmor` to apply to firefox but not to evince except for evince not running in firejail.
Author
Owner

@osevan commented on GitHub (Jul 19, 2021):

Today i did git pull and compiled firejail again.

Updated kernel to 5.13 rt

Even with firejail --apparmor dnscrypt-proxy ,apparmor cannot trigger firejail-default in aa-status, but, firejail --list shows everything running well

<!-- gh-comment-id:882927526 --> @osevan commented on GitHub (Jul 19, 2021): Today i did git pull and compiled firejail again. Updated kernel to 5.13 rt Even with firejail --apparmor dnscrypt-proxy ,apparmor cannot trigger firejail-default in aa-status, but, firejail --list shows everything running well
Author
Owner

@rusty-snake commented on GitHub (Jul 20, 2021):

Are chrome and firefox the only sandboxes where firejail-default is shown by aa-status?

<!-- gh-comment-id:883080340 --> @rusty-snake commented on GitHub (Jul 20, 2021): Are chrome and firefox the only sandboxes where firejail-default is shown by aa-status?
Author
Owner

@osevan commented on GitHub (Jul 21, 2021):

Are chrome and firefox the only sandboxes where firejail-default is shown by aa-status?

Plus libreoffice works well and aa-status trigger firejail-default with libreoffice inside.

I dont tested many apps only libreoffice browser Firefox and chrome and pdf apps.

<!-- gh-comment-id:884548479 --> @osevan commented on GitHub (Jul 21, 2021): > Are chrome and firefox the only sandboxes where firejail-default is shown by aa-status? Plus libreoffice works well and aa-status trigger firejail-default with libreoffice inside. I dont tested many apps only libreoffice browser Firefox and chrome and pdf apps.
Author
Owner

@osevan commented on GitHub (Jul 26, 2021):

I figured out what was wrong.

I have symbolic link in usr/local/bin, what points to /usr/bin/firejail <-- this is old firejail place 9.0.64.

New binary place is in /usr/local/bin/firejail.

Now my shell tried wrong firejail execution and apparmor couldn't start.

I deleted symbolic links and corrected path.

Now everything works like expected.

<!-- gh-comment-id:886946526 --> @osevan commented on GitHub (Jul 26, 2021): I figured out what was wrong. I have symbolic link in usr/local/bin, what points to /usr/bin/firejail <-- this is old firejail place 9.0.64. New binary place is in /usr/local/bin/firejail. Now my shell tried wrong firejail execution and apparmor couldn't start. I deleted symbolic links and corrected path. Now everything works like expected.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2648
No description provided.