mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #861] Support AppImage type 2 image format #584
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#584
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 @probonopd on GitHub (Oct 16, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/861
Please support the AppImage type 2 image format. This is the next-generation format that is using squashfs instead of ISO9660, and enables features such as embedded GPG signatures and other new functionality.
It should be pretty straightforward to use type 2 images, loop-mount them using the kernel with
-o,offset=xxxxx. The offset is the length of the ELF file in bytes. Appended to the ELF is the squashfs image.Tools to work with type 2 images:
https://github.com/probonopd/appimagetool
Example type 2 image:
https://bintray.com/probono/AppImages/download_file?file_path=Leafpad-0.8.18.1.glibc2.4-x86_64.AppImage
@netblue30 commented on GitHub (Oct 16, 2016):
Will do!
@netblue30 commented on GitHub (Oct 23, 2016):
Looks pretty cool, you basically cut the size of the image in half! I have the support in, it will autodetect the type and mount iso or squashfs accordingly:
For now use --private or a --profile command. I'll bring in support to pick up a profile automatically based on the application name.
@probonopd commented on GitHub (Oct 23, 2016):
Cool, thanks, will test asap.
@probonopd commented on GitHub (Oct 23, 2016):
Isn't it dangerous that the user can launch the app directly from
/run/firejail/appimage/appimage-...?@probonopd commented on GitHub (Oct 23, 2016):
Do we really need that many processes around?
@netblue30 commented on GitHub (Oct 23, 2016):
You can get rid of 24127 if you use --shell=none. I don't know what that [loop6] process is.
The idea is to mount it under /run instead of /tmp because in /tmp everybody has write access, while in /run only root can write.
@probonopd commented on GitHub (Oct 23, 2016):
How can we avoid the artefact that file managers show a new disk for a fraction of a second during mounting and unmounting?
Similarly, can it be that Firejail interferes (i.e., breaks) Startup Notifications? Note the two icons instead of one.
This is the relevant desktop file:
In case you wonder, these entries were generated by the
appimageddaemon which now uses firejail if it is installed.@probonopd commented on GitHub (Oct 23, 2016):
firejail --noprofile --shell=none --appimage ...results inError: --shell=none configured, but no program specified@netblue30 commented on GitHub (Oct 23, 2016):
Done, grab the latest from git. I'll look into --shell=none, it looks like a bug on my side.
@probonopd commented on GitHub (Oct 23, 2016):
Actually my mistake, having the mountpoint start with "." does not fix this. I currently don't know how to do this properly.
@netblue30 commented on GitHub (Oct 23, 2016):
No problem.