mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2140] Allow --appimage to accept a path to the appimage file. #1452
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#1452
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 @crass on GitHub (Oct 5, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2140
Currently there's an issue where its not possible to successfully jail processes that attempt to run appimage binaries. One trivial example is when there's a wrapper script that executes the appimage binary. A harder example to work around is when running an X11 appimage binary via openbox's
--startupoption.I propose that firejail be modified to optionally accept a path to an appimage binary (perhaps multiple paths?). When firejail is given this path it does the normal setup for appimage binaries, but it does not execute the appimage's
AppRunas it normally would. Instead it creates a symlink toAppRunat the given appimage path. Then it continues setting up and executing the givien program to be jails.Ideally, this should allow the jailed program to spawn an appimage process transparently. The command might look something like this:
This seems overly verbose having to repeat the appimage path, but it allows for the case where the specified program to jail is configured/prompted to execute an appimage by some means other than the commandline.
@matu3ba commented on GitHub (Feb 27, 2020):
@crass Why would you not move the file to a predefined folder for your appimages and start it from there with firejail?
openbox seems very specific to me.
One could argue, if firecfg should setup /usr/bin to link to an appimage folder.
However this would need special handling and hence might not be worth the effort yet.