mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2905] Potential leakage in quiet option #1814
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#1814
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 @ghost on GitHub (Aug 13, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2905
Commit
7b37c90240triggered my curiosity because it introduced thequietoption twice in gzip archiver redirect profiles and I assumed it might break stuff. But to my surprise it didn't. After some more testing, this is what I'm observing with firejail from git master.Placement is (still) important and might leak output:
quietin bunzip2.profile (included gzip.profile still has it)quietin bunzip2.profile (included gzip.profile still has it)This validates the double include of the
quietoption in7b37c90240, which doesn't seem to have any/much negative impact. It also suggests we could close any potential output leakage of thequietoption in other (mainly archiver redirect) profiles in similar manner. Are there any objections, observations, comments on this?