9 ms·
Relative to running the same application without flatpak: - You'd expect the application to run as your user and have full access to the home directory. Many a
by jillesvangurp 6y ago
Relative to running the same application without flatpak:
- You'd expect the application to run as your user and have full access to the home directory. Many applications expect to have this access. This is what it means to have user space applications. Flatpak is not about fixing or changing this.
- You'd expect individual applications might have out of date dependencies. Depending on the application this might be completely fine. This is not a security risk of flatpak but of the application. Developers are responsible for releasing updates, not flatpak.
So, works as advertised and intended. If your flatpak install has security bugs, update it. If you use a linux distribution that ships an out of date flatpak with fixed security issues, consider using a different one or update it yourself. If you use flatpak apps from developers that can't be bothered to release updates or fix bugs, consider using something else.
Basically, flatpak not being a middlemen between you and the application developers kind of is the whole point. They don't mention sandboxing on their frontpage, at all. This is not a goal. Instead, providing a cross distribution consistent installation experience is the main goal. They are not trying to be more secure than manually installing packages on your system.
So, these are not security bugs as far as I can see. It's not a security nightmare. It's fine. Actually looks interesting and might give it a try if/when I get rid of my mac.
- vibrant_mclean 6y ago> This is not a security risk of flatpak but of the application. Developers are responsible for releasing updates, not flatpak If it was a regular application installed by a linux package manager, the dependencies will be automatically updated to fix security issues(At least in most cases).
- gridlockd 6y ago> They don't mention sandboxing on their frontpage, at all. This is not a goal. ...and without this "fake sandboxing" strawman, flatkill.org is left without a convincing argument. The security trade-offs that come with flatpak are the same tradeoffs that desktop operating systems like MacOS and Windows have made since their inception. Considering that these are successful desktop operating systems, whereas Linux is not, one might conclude that these are the right tradeoffs, all things considered. Sure, it's "a security nightmare", but we've been living through it for decades. The alternatives clearly aren't good enough to bring everyone to move over.
- haolez 6y agoExcept that with "old school" package managers you get security updates without the application or the developer having to act on it. I don't know if it's "a nightmare", but it's worse security comparing against the previous solution.
- danShumway 6y agoNobody should be relying on dynamic linking as the primary way they keep their home computer secure. Enough applications statically link their libraries that this is not a reliable strategy. If you can't trust a library author to keep their code up to date, it's probably also a mistake to trust them to use your system libraries in a way that minimizes their attack surface. I also have problems with Flatpak's security model, particularly with their UX around permissions. We already learned from Android/iOS that allowing highly permissive manifests out of the box was a bad idea. But at least Flatpak is trying to do something, and that something seems like a tangible improvement to me. The idea that our systems will be secure because we dynamically link everything needs to die; it's not a viable security model. Even if the only thing that Flatpak does is kill the "dynamic libraries make me secure" perspective, that on its own will be worthwhile.
- hapless 6y agoStatic linking is dead. Most applications cannot be built statically, at all. Solaris-style RPath is still an option on Linux, but it is rarely used. As far as “security,” dynamic linking is not an attempt to contain applications, but rather to fix as many things as possible with as few updates as possible. Flatpak actively encourages upstream developers not to participate in the wider picture, and as it turns out, upstream developers can’t be trusted to fix security holes in a timely manner. This was a widely foreseen issue that was pooh-poohed in the early days of flatpak, but, well, look how it turned out.
- otterley 6y ago> Most applications cannot be built statically, at all. That’s a pretty bold claim. Can you identify a specific C program that cannot be built statically, no matter how hard you try?
- sergeykish 6y ago> Developers are responsible for releasing updates, not flatpak. That's what distribution maintainers do. > They are not trying to be more secure than manually installing packages on your system. That's downgrade from distribution experience.
- eikenberry 6y agoThe primary reason I have when considering using a flatpak or appimage is for software either not commonly included in distros (eg. proprietary software like games) or that are updated more often than the distro cares to manage (eg. browsers). It fills the gaps in distros.
- sergeykish 6y agoYou do not have to abandon distribution model. I've just installed Nix on Arch Linux [1]. It ships all required dependencies - glibc etc - version specific. Works on Ubuntu/Debian [2]. [1] https://wiki.archlinux.org/index.php/Nix https://wiki.archlinux.org/index.php/Nix [2] https://ariya.io/2020/05/nix-package-manager-on-ubuntu-or-debian https://ariya.io/2020/05/nix-package-manager-on-ubuntu-or-de...
- solarkraft 6y agoSo wait ... It's in my way for no reason? /snark I get the idea of Flatpak. I want some kind of app sandboxing. Ideally with a good UX and shared libraries, however.
- smileybarry 6y ago> They don't mention sandboxing on their frontpage, at all. But the apps themselves still show "Sandboxed" when they aren't[1]. It's trivial for the flatpak "store" to just hide "sandboxed" if the flatpak requires access in its manifest. The Microsoft/Windows Store does this. UWP apps are sandboxed and permission-managed, but if a store app requires full access, the permissions section[2] says: > This app can > Access all your files, peripheral devices, apps, programs and registry [1] See first screenshot in OP article. [2] https://www.microsoft.com/en-us/p/microsoft-flight-simulator-standard/9nxn8gf8n9ht#activetab=pivot:overviewtab https://www.microsoft.com/en-us/p/microsoft-flight-simulator...
- grey_earthling 6y agoThat screenshot is of GNOME Software, not of a Flatpak app. GNOME Software decides how it describes apps. The GNOME designers are working on a redesign of this area: https://gitlab.gnome.org/Teams/Design/software-mockups/-/blob/master/app-pages.png https://gitlab.gnome.org/Teams/Design/software-mockups/-/blo... There are other software installers that can install Flatpak apps, e.g. KDE Discover. So this is a valid criticism of GNOME Software, but not of Flatpak.
- smileybarry 6y agoYou're right, I checked Plasma (Kubuntu) and it doesn't show the same "Sandboxed" indicator for Flathub. This is more of a GNOME issue, even a serious one if it existed for an whole 2 years.
- knocte 6y agoGreat, let's create the bug report, otherwise GNOME devs may not know about this defect.
- cheph 6y ago> But the apps themselves still show "Sandboxed" when they aren't Redefining the term and then claiming that what someone else meant by it is not in line with what you meant with it is ... well it is messed up. They are sandboxed, but rightly Gimp has access to your whole filesystem because that is what people who install it expect. Of the 30 apps I have installed via flatpak only 6 have access to the whole FS or my entire home directory (Zotero=home, Krita=host, KolorPaint=host, Inkscape=host, Gimp=host, Geeqie=host), and of those 6 only 1 (Zotero) of them seems like it may be fine without it. Having access to the host FS in no way mean to me that Geeqie is not "sandboxed". It just means that what I would expect is the case. If you want to change it, go open up flatseal and change it.
- waheoo 6y ago> Instead, providing a cross distribution consistent installation experience is the main goal. Who is asking this exactly? As an arch user and technically a fedora, Gentoo, slackware, Ubuntu, debian user, I'm not asking for this. I like how I install packages. Installing garbage from a webpage like some windows pleb or having to eject weird desktop download things after drag and dropping things on a Mac is not something I want. Please stop pushing this idea about flatpak being better, its not for a lot of users and for me, security doesn't even enter the equation. But the idea that random flatpak maintainer has better security processes I place than the sec team for many distros is laughable at best. You can wrangle the argument all you like about ideal world scenarios but the fact of the matter remains that suboptimal ideal still works out as more effective in the real world. Tragedy of the commons problems generally do require sub optimal solutions in the small to solve in the large.
- TehCorwiz 6y agoThere’s a lot of good software that isn’t in package repos. This isn’t a failure in the developers part. It takes knowledge and time and effort to package for a repo, let alone all the different repos on each distro. Flat pack gives a single way to distribute something and on that merit alone it’s valuable.
- waheoo 6y agoAgain, to whom? Arch has aur, arch can sideload rpm/Deb's, Mac has home brew, who needs this? The only people I see using flatpak is the 50 odd Linux users we have at work, they constantly have dramas trying to make things work around home directory sandboxing, permissions, updating and more > Single way Why is this valuable? Just saying it doesn't make it true. Why do we need a single way to install? I'm not saying it's a bad thing, but giving up home dirs and a bunch of other platform specific benefits is a cost I'm not willing to pay for some made up ideal that gives me a worse experience.
- santoshalper 6y agoDid you know, and this may shock you, that there are other people with other interests. Also, and this one is really going to blow your mind, these other "people" (plebes if you will), may value different things and want products that are of no interest to you. Flatpak sounds like a shitshow, but the not because it doesn't meet your specific requirements.
- mschuster91 6y ago> You'd expect the application to run as your user and have full access to the home directory. Many applications expect to have this access. This is what it means to have user space applications. Flatpak is not about fixing or changing this. I as an user could at least expect a sandbox that protects a rogue application from modifying or even reading critical files without user consent: .config of other applications, .ssh/, shell configs (profile, rc). A web browser may require create-write access to ~/Downloads but not arbitrary read or write access anywhere else with the exception of save-as/upload explicitly requested by the user*, and that could be done by the OS file selection dialog giving back the filename + a token. And so on. Perhaps it could even be abstracted to a common "profile" for application classes, and go even further than that and have stuff like raw USB/Bluetooth not authorized by the browser but by the OS/sandbox layer (to prevent attackers exploiting a browser bug).
- boomlinde 6y ago> You'd expect individual applications might have out of date dependencies. Depending on the application this might be completely fine. This is not a security risk of flatpak but of the application. Developers are responsible for releasing updates, not flatpak. Not so much in a system that links executable dynamically to system provided libraries (e.g. Debian), or provides system wide maintenance updates to statically linked binaries when their dependencies receive important updates (e.g. Alpine). ...which really covers every sane, actively maintained *nix system with a package manager, so in that sense Flatpak is definitely a step down. Instead of trusting, say, the Debian or OpenBSD maintainers to provide timely security updates, you have to trust each individual vendor of your flatpaks. The only advantage I can see for them is in providing closed source software, which OS maintainers simply can't maintain and update. A developer advantage may be that the standard of inclusion is much lower than for Debian or OpenBSD, but that's IMO a user disadvantage.
- mixedCase 6y ago> Instead of trusting, say, the Debian or OpenBSD maintainers to provide timely security updates, you have to trust each individual vendor of your flatpaks. Well, yes, and it's the most obvious approach. You're trusting the person producing the product for producing a good product. The distro approach is great, but it doesn't scale well for obvious reasons and it makes software development harder due to downstream issues often going reported as upstream issues. I appreciate and enjoy the distro approach for what it gives me, but there should always be a way for developers to provide packaging that works everywhere and then distro maintainers can feel free to recompile/repackage as they please.
- boomlinde 6y ago> You're trusting the person producing the product for producing a good product. That's a generalization. Specifically, I'm trusting the person producing the product to do something that e.g. Debian has a proven track record of doing quite well: maintaining dependencies so that I have a secure (and consistent) system altogether...so well that I'd rather trust them to do it over any existing flatpak vendor, and definitely more than trusting n vendors for the n flatpaks I have installed. > The distro approach is great, but it doesn't scale well for obvious reasons Regarding what aspect doesn't it achieve the scale necessary? It's not obvious to me what you mean at all. > and it makes software development harder due to downstream issues often going reported as upstream issues. A cost of system-scale software maintenance, for sure. > I appreciate and enjoy the distro approach for what it gives me, but there should always be a way for developers to provide packaging that works everywhere and then distro maintainers can feel free to recompile/repackage as they please. I don't fundamentally disagree. My point is that I think it's a security risk to leave it to every developer to maintain their dependencies as they see fit, and that this is a problem that flatpaks create that a well maintained distro software repo doesn't have. It's better to acknowledge this risk and consider it to grow as you install more flatpaks than to ignore it, expecting that every flatpak vendor will respond in a timely manner to dependency CVEs; the trust I place in Debian—by necessity very high—now has to be multiplied for each individual flatpak.