mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #358] Firejail discards exit code #255
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#255
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 @gnunicorn on GitHub (Mar 7, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/358
Hello,
we are using firejail to securely run a compiler and linter in the clippy-service. First off, I wanted to thank you for this great project and the work you've put in it. It works great for us and allowed us to quickly setup a sandbox to allow third-party access without security risks. Thank you very much!
Coming to our specific problem: firejail currently swallows the exit-code of the program it runs internally. As this gives us an indication whether the compiler exited successfully or whether there was a problem, this is a big problem for us.
I've identified that it would only require to keep the variable from the waitpid (instead of NULL) and forward that on process exit, but that is currently not done. Would you accept a Pull-Request implementing this behavior? And/or do you want this new behavior be hidden behind a command-line option (like
--preserve-exit-code)? I could prepare a PR about that but first wanted to make sure you'd want this, or maybe you had other good reasons to discard the exit code...Highly appreciate you looking at this and all the work you've put in this already.
Thanks for your time!
@netblue30 commented on GitHub (Mar 7, 2016):
Sure, if you send a patch I'll merge it, thanks!
@netblue30 commented on GitHub (Mar 31, 2016):
It is already in the master branch, a testing release will follow shortly.