mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1667] Running unjailed programs from within jail #1125
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#1125
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 @metasyntacticQuux on GitHub (Dec 2, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1667
Is there a way to have a jailed program execute unjailed programs with full permissions? I've intentionally jailed my Firefox in such a way that it cannot access my personal documents. I've created a program to handle downloading files, and it works perfectly without firejail. I need it to run outside of the jail when Firefox launches it from within the jail.
@SkewedZeppelin commented on GitHub (Dec 2, 2017):
That would allow the jailed program to easily escape. So no. I'm sure there is an issue that describes it some more, but I cannot find one right now.
@metasyntacticQuux commented on GitHub (Dec 3, 2017):
Sorry, I meant whitelisting which programs can be run outside of the jail. Obviously if you can run any program you can do anything.
@reinerh commented on GitHub (Dec 3, 2017):
It's not possible. Once the seccomp filters and other restrictions are in place, they affect all the forked programs.