mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3257] stackable wrappers convention proposal #2043
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#2043
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 @adrelanos on GitHub (Feb 29, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3257
Could you please provide feedback for this stackable wrappers proposal?
Related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822693
@netblue30 commented on GitHub (Mar 17, 2020):
/etc/wrapper.d and wrappers in /usr/lib/firejail/ are fine. On our side is not too much to do, we can generate the wrappers easily. And once they are implemented in debian we can install the wrappers in /usr/lib/firejail from our source code archive. So, I would say go for it!