mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3815] Question: AppImage trust #2408
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#2408
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 @mid-kid on GitHub (Dec 13, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3815
AppImages are essentially a binary with a disk image attached. The default way to unpack them is to just run and trust this "runtime" binary. This essentially puts trust into this binary to not do anything bad, and has a similar issue as running
lddto inspect a glibc binary.My question is mostly: What does firejail with the
--appimageoption do? Is this bootstrap/runtime binary ran at all, if so, is it ran sandboxed or unsandboxed? Or does firejail reimplement this?@smitsohu commented on GitHub (Dec 16, 2020):
Firejail doesn't use the AppImage runtime, it uses a simple reimplementation.
All AppImage code is executed in the sandbox, and that's the only possible way; everything else would defeat the very idea of a sandbox.
@mid-kid commented on GitHub (Dec 17, 2020):
Thanks, I was worried for a second, since everything about the format is really opaque.