mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #666] --trace breaks tar unpacking #454
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#454
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 @thomasjfox on GitHub (Jul 30, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/666
when you run tar with the new tar.profile, tar won't extract any file if --trace is given.
This might be an easy reproducer to debug this issue,
may be #561 is related to this.
@thomasjfox commented on GitHub (Jul 30, 2016):
plain tar archives seem fine, the trouble starts when a compressor like bzip2 is used (=forked).
@thomasjfox commented on GitHub (Jul 30, 2016):
hmm, during my testing --tracelog was broken but now it works.
--trace probably messes up the stdout <-> stdin pipe tar uses for the compressor subprocesses.