firejail
zap
firejail | zap | |
---|---|---|
139 | 17 | |
5,482 | 487 | |
- | - | |
9.7 | 4.1 | |
3 days ago | 9 months ago | |
C | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
firejail
-
Sandboxing All the Things with Flatpak and BubbleBox
bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.
Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.
If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail
-
Ask HN: What are some unpopular technologies you wish people knew more about?
Firejail is cool: https://github.com/netblue30/firejail
Linux namespaces/cgroups but nowhere near as heavy as Docker.
I use it when I want to limit the memory of a Python script:
```
-
Toolship: A (More) Secure Workstation
Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/
Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case
-
Firejail: Light, featureful and zero-dependency security sandbox for Linux
Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.
This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...
TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.
Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.
-
Bubblewrap – Low-level unprivileged sandboxing tool used by Flatpak
Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).
Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":
- Firejail: Light featureful and zero-dependency security sandbox for Linux
-
Do, or do not. There is no try
Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc
-
Strange times make for strange friends...
What do you mean by a Firefox container? Do you mean FireJail?
zap
- Working on an app to "install" and manage AppImages
-
Why doesn't appimage have this?
Integrate zap with that repo and make it official. It will automatically download the appimages inside a directory 'Appimage'. You can move them anywhere else ONLY if it has a directory named 'Appimage'. In this case it is moved to an external usb.
- Lamenting What AppImage Could Have Been
-
Install snap vs deb (ppa) for Ubuntu 22.04?
Personally, on a debian based distribution I would either use the AppImage (you could even use something like zap to manage its version). Or, the solution I would and have personally used is to compile it from source. I am a developer, so I am biased, but the instructions are very simple and clear so it should be pretty easy to do.
- Zap: The delightful package manager for AppImages
-
appimage-builder 1.0.0 was released, a tool for packing applications along with all of its dependencies using the system package manager to obtain binaries and resolve dependencies.
That said, there is Zap.
-
Bread, It's History & Minor Patch v0.7.2
Tho bread is github focused which is a big drawback as many software aren't on github, i discovered this program Zap Which was a appimage package manager like AM or bread but it's far much better than mine.
-
Interesting Benchmarks of Flatpak vs. Snap vs. AppImage
If you can download and install software from the web (which you also can do with debs and rpms btw), you can create a package manager to automate that from the terminal. You either trust a project or you don't, and if your don't the package format makes no difference.
-
It's time to fork some good projects
NOTE: I don't know when and if to add new AppImages from the main catalog, also because a part of them is mostly broken and out of control. The AppImage packages compiled and managed by "AM"/AppMan are new AppImages that use scripts that also allow constant updating and recompilation from scratch, as if they were installed from AUR, using more reliable sources (official repositories for Debian and derivatives) . If you are interested more to the applications made available officially from the official AppImage.GitHub.io catalog, I suggest you to use Zap, Bread or the aforementioned Appimagedl. All these amazing utilities can be quickly installed via "AM" or AppMan.
- AppImage and centralized repositories: my point of view
What are some alternatives?
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
AppImageUpdate - AppImageUpdate lets you update AppImages in a decentral way using information embedded in the AppImage itself.
flatpak - Linux application sandboxing and distribution framework
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
bubblejail - Bubblewrap based sandboxing for desktop applications
AppMan - Manage 1900+ AppImage packages and official standalone apps for GNU/Linux without root privileges using the extensible and ever-growing AUR-inspired database of "AM Application Manager". Easy to use like APT and powerful like PacMan.
Flatseal - Manage Flatpak permissions
appimagepool - A simple, modern AppImageHub Client, powered by flutter.
yabai - A tiling window manager for macOS based on binary space partitioning
gvm - Go Version Manager (gvm) enables seamless installing and swapping between Go versions with a single command. This tool manages a Go environment for the user by allowing a user to specify which Go version they wish to use and handling all of the steps to install and configure that Go version. GVM also supports installing Go from the official Golang master branch so that you can easily try the next version of Go without waiting for a pre release build.
podman - Podman: A tool for managing OCI containers and pods.
GIMP-64bit-and-32bit.AppImage - GNU Image Manipulation Program, cross-platform image and photo editor, AppImages for x86 and x64 architectures built from the more recent PPA (supports GLIBC 2.27 or later). [Moved to: https://github.com/ivan-hc/GIMP-AppImage]