mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2963] Apparmor integration, most applications crash. #1854
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#1854
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 @Netanel-M on GitHub (Sep 15, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2963
Running Ubuntu 18.04 I've installed firejail, along with apparmor from the official repositories. I used
aa-enforce firejail-defaultto enable the apparmor profile, then proceeded to run a few programs withfirejail --apparmor <program name>. almost all of them crash, except for chromium-browser, seems to work. Here is the output offirejail --debug --apparmor kateI assume firefox fails for similar reasons, but I opted for kate because it's a much simpler software.
@chiraag-nataraj commented on GitHub (Sep 15, 2019):
Hmm, I've been running with apparmor enabled on Debian for a while now with no issues whatsoever (Firefox included). Does disabling the apparmor integration prevent the program from crashing?
@Netanel-M commented on GitHub (Sep 16, 2019):
Hi, yes when moving the
firejail-defaultprofile tocomplainmode firefox and kate do work.Also a correction, firefox doesn't actually crash, but it doesn't work. it keeps asking to restart, and won't go to any url.
I installed a fresh Ubuntu 18.04 image on a virtual machine and confirmed this all happens there too, so it's not just my machine.
@Vincent43 commented on GitHub (Sep 16, 2019):
Proper way for enabling firejail AppArmor profile after install is
apparmor_parser -r /etc/apparmor.d/firejail-defaultas documented in manpage.You may check output of
journalctl -b |grep DENIED. I'm unable to reproduce crashes in Ubuntu 18.04. You may try installing latest version from PPA@Netanel-M commented on GitHub (Sep 16, 2019):
Thank you for the response, here is the output of
journalctl -b | grep DENIEDI'm not sure why you weren't able to replicate the issue. To replicate it in a vm all I had to do was install ubuntu, boot with
security=apparmorandapparmor=1kernel parameters, update the sources and upgrade the system, install firejail and enable the apparmor profile.@Vincent43 commented on GitHub (Sep 17, 2019):
Did you tried with latest version from PPA? firejail AppArmor profile doesn't block dbus access for some time.
@Netanel-M commented on GitHub (Sep 18, 2019):
Hi, thank you very much for the suggestion. Installing firejail from PPA indeed solved the problem so I'm closing the issue, thank you again for the support.