2 ms·
I dislike unfair bashing of projects which the domain name sort of implies, but I can’t help but question the reason for Flatpak and snap to exist. They are no
by kaba0 5y ago
I dislike unfair bashing of projects which the domain name sort of implies, but I can’t help but question the reason for Flatpak and snap to exist.
They are not great as sandboxes (something very dearly needed for linux, correct me if I’m wrong but firejail is suid so it actually can make a potential zero day into a root escalation), and the biggest problem: they suck as a packaging solution. It is the same way as Docker, making it someone else’s problem. I don’t understand why should linux distros badly copy that model when we have Nix, that actually solve dependency management properly. It should be pushed for.
- foxpurple 5y agoFlatpak is a good sandbox. It’s just they have to add a bunch of permissions in so that traditional style desktop apps can still function. You can crank the security to max if you want but it isn’t very useful if gimp can’t open files. So flapak let’s you say that gimp should have file system access or access to specific folders. But the blog author takes the existence of these permissions as flatpak being critically insecure.
- kaba0 5y agoI’m not sure - file access is but one (glaring) hole of linux security. How well does it work with eg. network, audio/video, etc?
- foxpurple 5y agoThere are permissions for both. You can disable network entirely and disable access to X11/Wayland. You can use flatpak to lock down things to the point you can’t do anything anymore.