gimp VS firejail

GIMP: C, not C++

GIMP - https://gitlab.gnome.org/GNOME/gimp

GIMP

How are they implement? https://gitlab.gnome.org/GNOME/gimp https://github.com/figma

As u/schumaml said already, we have an issue tracker: https://gitlab.gnome.org/GNOME/gimp/

The former might be something you want to report as an issue at https://gitlab.gnome.org/GNOME/gimp, with the XCF file used for your cover image - or a mockup exhibiting the same issue - attached.

As Gimp is open source, I already had a look in the source code but it's written in C, which is different enough from C++ or C# that I have a rather difficult time understanding it, at least in terms of project structure. I'm pretty sure I found the handling of the tool itself in gimpoperationcolorize.c but I don't know where to go from here.

> Gotta be real, Gimp's not that far off from just one guy (https://github.com/GNOME/gimp/graphs/contributors)

GitHub only shows people with an email address linked to a GitHub account in that chart; the last time I checked it was 4 or 5 people working on it regularly, which is still a very small team (none are working on it full-time) so your point still stands (it's a point I've made myself a few times before when people compare GIMP to Photoshop or the like).

Maybe not the best example. The one on github is just a mirror of this one.

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

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:

```

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, 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.

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 does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc

What do you mean by a Firefox container? Do you mean FireJail?