mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[PR #3450] [MERGED] enable apparmor support by default in update_deb.sh #4767
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#4767
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?
📋 Pull Request Information
Original PR: https://github.com/netblue30/firejail/pull/3450
Author: @ghost
Created: 6/4/2020
Status: ✅ Merged
Merged: 6/12/2020
Merged by: @undefined
Base:
master← Head:update-deb📝 Commits (2)
e78aae3enable apparmor support by default in update_deb.sh5c99f3dAdd fix for Debian bug 916920📊 Changes
1 file changed (+10 additions, -2 deletions)
View changed files
📝
contrib/update_deb.sh(+10 -2)📄 Description
IMO enabling apparmor support by default here ensures a git installation that is compatible with the OS repository and PPA packages (see the firejail-from-git wiki page).
One thing I'm not sure of is how we can patch firejail.config to accomodate https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916920.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.