AIUI Flatpak attempts to sandbox everything as much as possible. I'm no flatpak dev, nor am I intimately familiar with its implementation. But with little eff

AIUI Flatpak attempts to sandbox everything as much as possible. I'm no flatpak dev, nor am I intimately familiar with its implementation. But with little effort glancing at the code one can confirm there's clearly effort to even sandbox triggers: https://github.com/flatpak/flatpak/blob/1.15.3/common/flatpak-dir.c#L7124 https://github.com/flatpak/flatpak/blob/1.15.3/common/flatpa... Note that flatpak builds upon bubblewrap, which descends from linux-user-chroot, a project specifically focused on preventing things like host contamination during package builds over tools like jhbuild. The devs are aware of these issues and aspire to address them. I doubt it's perfect though, and I'm sure there are insecure modes for flatpaks where everything just occurs in the host namespace. But hopefully that's made clear to the end-user before proceeding. I recall there being some brouhaha over flathub misrepresenting some apps as totally secure/sandboxed which shouldn't have been, because they were still running in the host namespace or something like that. I believe that got fixed though.