I just read https://lwn.net/Articles/1020571/ in which is
One thing that has been a bit of a pain point, Wick said, is that nested sandboxing does not work in Flatpak. For instance, an application cannot use Bubblewrap inside Flatpak. Many applications, such as web browsers, make heavy use of sandboxing.
.
They really like to put their tabs into their own sandboxes because it turns out that if one of those tabs is running some code that manages to exploit and break out of the process there, at least it's contained and doesn't spread to the rest of the browser.
.
What Flatpak does instead, currently, is to have a kind of side sandbox that applications can call to and spawn another Flatpak instance that can be restricted even further. ""So, in that sense, that is a solution to the problem, but it is also kind of fragile"." There have been issues with this approach for quite a while, he said, but no one knows quite how to solve them.
Notwithstanding the rise & rise of numerous #atomic / #immutable distros, which thus rely heavily on flatpak usage by users, i still substantially prefer "traditional" mutable distros, & native pkgs.
After reading this article, & attempting to understand it [not my area of expertise at all], i feel even more motivated to keep avoiding running any browser as a flatpak version.
Thoughts pls, from others who would certainly have a better understanding than i?
#Flatpak #browsers #security #Linux