16 ms·
Response to Flatkill.org
- chunkyks 6y ago"Flatpak fixes that issue by providing consistent builds for every distribution" - aka https://xkcd.com/927/ https://xkcd.com/927/ "Standards" I get the point of flatpak and I see its value. Personally I just don't need yet another channel through which I need to get stuff. Ubuntu has already obnoxiously fragmented [1], this is just another fragmentation I don't want [1] chunky@mills:~$ erl Command 'erl' not found, but can be installed with: sudo snap install erlang # version 22.3.4.1, or sudo apt install erlang-base # version 1:22.2.7+dfsg-1
- tannhaeuser 6y agoAlso there's this annoying gem: $ sudo apt install cpufreq No apt package "cpufreq", but there is a snap with that name. Try "snap install cpufreq" Can't say I'm getting the point of either snap or flatpak when the whole point of using a distro is that's a trusted/curated set of software. Moreover, snaps frequently just don't seem to work for me whereas the regular .deb does.
- airhead969 6y agoI don't use Ubuntu anymore because it's turned into a garbage heap. Debian, Arch, or Qubes. (Fedora-Cent-RHEL are boned. Cent-RHEL has/had an awesome stable kernel due to enterprise-scale bug fixes but that's likely to end. Debian is a good substitute.) If I need the latest-greatest on a stable release OS, I use habitat.
- mroche 6y ago> Fedora-Cent-RHEL are boned. Care to elaborate on that? Curious where your position on this is coming from.
- airhead969 6y agoYou may not be aware of what's happened: IBM buys RHEL and immediately messes with its products and culture. https://www.cnbc.com/2019/07/09/ibm-closes-its-34-billion-acquisition-of-red-hat.html https://www.cnbc.com/2019/07/09/ibm-closes-its-34-billion-ac... https://itsfoss.com/centos-stream-fiasco/ https://itsfoss.com/centos-stream-fiasco/ CentOS is no longer basically functionally-equivalent to RHEL. https://www.theregister.com/2020/12/09/centos_red_hat/ https://www.theregister.com/2020/12/09/centos_red_hat/ IBM (through Red Hat) runs the Fedora project's board of directors, so there is no real independence from IBM.
- dralley 6y agoFedora is great, I've been using it daily for 5 years.
- airhead969 6y agoHow is Fedora going to sustain itself long-term? http://techrights.org/2020/12/26/fedora-2020-and-ibm-vision/ http://techrights.org/2020/12/26/fedora-2020-and-ibm-vision/
- dralley 6y agoWhat is up with everyone posting techrights all of a sudden? It's a conspiracy blog, and most websites actually paying attention to FOSS news have ignored them for years. https://www.reddit.com/r/linux/comments/4541p6/can_we_not_post_links_to_techrights_please/ https://www.reddit.com/r/linux/comments/4541p6/can_we_not_po... Disclaimer: I work for Red Hat. TechRights claimed that there were massive layoffs last year, which is total BS. They literally just make stuff up. The other day they claimed that "Fedora is being outsourced to Microsoft and to AWS" on the basis that some Fedora repos are on Github, and some build infrastructure uses AWS. And mind you the claim was not "Fedora project infrastructure is being outsourced" but actually "Fedora is being outsourced". And that has been the general way they approach "reporting" for years, as you can see from the /r/linux thread. Then when I and others pointed out how ridiculous this line of reasoning was, and the post got flagged by admins, they made an entire new post claiming they were being censored by HN.
- Shared404 6y agoI've personally had better luck with flatpack than snap[0] I still prefer to install from the OS repos where possible, but I like having choices. I'd rather be able to install something untrusted through a package manager where I can then at least have it installed in a standardized manner than download a binary and trust myself to remember what I did with it, but that may just be because I'm stupid :) . [0] Also, it not creating a bunch of loop devices is nice.
- airhead969 6y agoEmperor's new clothes. Something for someone to say is "better" while ensuring their job security. In reality it creates too many choices, duplication of effort, too much fragmentation, abandoning standards, and complexifying security, auditing, and configuration management. If you want isolated software, use something like Qubes (Xen with virtualized containers), not Docker and not flatpak, snap, or anything similar. Inventing "new" things rather than fixing what already exists is rarely ever a good solution.
- cycloptic 6y agoI don't see what you mean. Qubes is great, but it is not the same thing as Docker, flatpak, or snap. Are you saying Qubes should somehow be changed so that it works similar to Docker? And if so, why wouldn't you just use Docker?
- airhead969 6y agoThen you need to understand how they work differently and their contrasting limitations. Qubes (based on Xen) is great for desktop users to segregate applications. Xen standalone is similarly great for general server containerization. Docker doesn't work anything remotely like a hypervisor. It doesn't provide the much greater assurance of security, scalability, isolation, resource metering, accounting, or flexibility that a hypervisor does. Docker is a security disaster and it only runs Linux. Xen/Qubes runs Windows, BSDs, or any other OS. Docker seems "easy" but with many subtle costs that come later at scale. You can't live migrate a Docker container from one host to another, where you usually can with Xen using shared storage. There are many other gotchas in the lifecycle of Docker containers that are eliminated or mitigated by using hypervisor guests instead. flatpak and snap are basically filesystem overlays. They're gross, poorly-managed, incompatible duplications of package management.
- cycloptic 6y agoI am not sure I see what the significant difference is, I've heard of security escapes happening in both Docker and in various hypervisors. Either way there is a risk of some privilege escalation bug that allows access to the full RAM. I think if you want isolation, both of them lose out to having a separate firewalled off machine. Also I think the companies running heavy Linux workloads on Docker are probably not interested in the ability of Qubes to run Windows or Mac, just my read on the situation from talking to some of them. I don't know about snap but from what I have seen of flatpak, it allows for different versions of the same package to be installed, not many package managers are supporting that currently. (Nix and Guix being some notable exceptions, and those should be able to re-use some of the sandboxing bits from flatpak if they need to) Of course, that is one of the main benefits to building this on top of filesystem overlays, and why it requires a different approach from a traditional package manager, i.e. it's not just a duplication. Edit: Live migration actually does work for containers, take a look at CRIU. (I don't know the current status of this being integrated in Docker) I never even saw this as being opposing technology anyway, for example if you need to you could migrate a container in or out of a VM.
- danieldk 6y agoI get the point of flatpak and I see its value. Personally I just don't need yet another channel through which I need to get stuff. IMO Flatpak solves several real problems: 1.) allowing third parties distribute applications in a distro-agnostic manner; 2.) allowing easy installation of packages as a user (rather than requiring root); 3.) a way to install applications on top of an immutable base OS; 4.) sandboxing of applications, or at least packaging applications such that they can move to proper sandboxing over time. Unfortunately, the development of application bundles follow the prototypical path that we are oh so familiar with as Linux users. Rather than sitting together and making one standard, Canonical (Snap) and Red Hat (Flatpak) made their own application bundle formats, in addition to an already existing format (AppImage). And now vendors have to build bundles in three different formats, like they had to build for at least two package managers before. So, the problem actually got worse. To Red Hat's credit, Flatpak was initially developed as part of freedesktop.org (initially as xdg-app). We can always hope that Canonical will give up on Snaps for desktop applications I guess (like they dropped Unity and Upstart).
- Avamander 6y agoIt's weird that flatkill.org picked Flatpak instead of all container systems or statically linked software.
- yellowapple 6y agoWell that's the thing: not all of these container systems advertise themselves as having sandboxing built in. Neither do people statically linking. The AppImage philosophy seems to be much more robust here (and not coincidentally more in-line with the Unix philosophy): focus strictly on the packaging/distribution aspect and defer the sandboxing to separate tools (e.g. Firejail).
- Avamander 6y agoThey don't advertise, but they have the same issues, which should be dealt with. I don't think it's fine to just say "security doesn't concern us" in the year 2021.
- yellowapple 6y ago> They don't advertise, but they have the same issues, which should be dealt with. Which is possible, specifically by deferring to something like Firejail that can handle any application rather than expecting every application format to bake in its own subtly-different mechanism. That is: > I don't think it's fine to just say "security doesn't concern us" in the year 2021. That ain't what's being said. What these folks are actually saying is that security and packaging are separate concerns, and that said security should be enforced in one place in a way that's applicable to all programs, no matter their packaging.
- tremon 6y agosecurity should be enforced in one place in a way that's applicable to all programs, no matter their packaging. How do you do that without placing contraints on said packaging, though? Will you just blanket-restrict all packages to the strictest security measures? i.e. no network, no access to persistent storage, w^x on all pages? Or will you only provide token security because all features are useful to some apps, and you can't know beforehand what features the app actually needs?
- nickysielicki 6y agoI've contributed to flathub, so I might be biased, but what I never got about the "flatkill" rant (which was first posted like 3-4 years ago) is that flatpak has never claimed to be a security panacea. They didn't invent flatpak for the sake of security. Flatpak is fundamentally a distro-agnostic packaging mechanism and build environment with some clever abstractions to avoid static linking and encourage code reuse. Theoretically, it's also got the potential to make things more secure, but it wasn't ever billed as the main idea. My dad was always a windows guy, but recently I got him using linux mint for some of his ham radio stuff. Flatpak and flathub are perfect for people like him. And that's good enough.
- pydry 6y agoI got the same impression. Flatpak seemed much more like 21st century static linking with some slowly evolving security features bolted on top. The other thing I didn't get about the flatkill rant was why it didn't put flatpak in context. It makes much more sense compare the security of flatpak to that of appimage and snap than to look at flatpak as an isolated thing.
- stuaxo 6y agoYep - perfect is the enemy of good. For me the advantage of flatpak is that it makes things a lot easier to install, abstracting away all the detail between different Linux distros. The layering is good + because of immutability, you have a system that is a lot closer to the one the devs actually used. There is a little more security, which is a bonus too, but that's not the main draw.
- lrvick 6y agoTo be fair the default software supply chain integrity story and sandboxing of docker, snap, and appimage are also terrible. They all solve the same "problem". Without dedicated parties to maintain updates... like a distro, most of the packages distributed with these tools just make Linux less secure even if the tools themselves are useful in right context. The docs and authors of these tools are trying to bring to Linux the "go on the internet and get a random .exe" model of Windows which is a proven security nightmare.
- Denvercoder9 6y ago> A few months ago, I submitted an issue in the Gitg issue tracker. The maintainer replied to me: “Reviewing ssh feature, it is not even touched on gitg or libgit2-glib, just a dependency on libgit2, […]“.(Source) > Although it comes with an unpatched libssh2, Gitg does not use the part that contains the vulnerability. This conclusion is plain false. The maintainer comment he quotes only says that gitg doesn't directly use libssh2 (so they can't enforce a version constraint on it), not that it doesn't use it all. It's very likely that gitg does actually use the vulnerable libssh2 if you use it to clone a repository over SSH (which it can do).
- sushiburps 6y agoWhile discussing applications that are advertised by Flatpak's application metadata as sandboxed: "Allowing access to the host file system does not give the application full reign over your system." The Flatpak documentation he then links to contradicts his rather controversial idea that a sandboxed application have access to the host file system. "With Flatpak, each application is built and run in an isolated environment, which is called the ‘sandbox’. Each sandbox contains an application and its runtime. By default, the application can only access the contents of its sandbox. Access to user files, network, graphics sockets, subsystems on the bus and devices have to be explicitly granted. Access to other things, such as other processes, is deliberately not possible."
- offtop5 6y agoThe author sounds extremely defensive, either ship a decent product or don't. If it becomes something where getting exceptions for sandboxing are so absolutely difficult most people skip it all together and ask for full access, you might as well just install directly from apt. I also hate snaps, apt get install whatever you need, and be done with it.
- nickysielicki 6y agoAnd what about when apt doesn't have a package for the thing you want? You can install Spotify, Steam, Discord, Microsoft Edge, Zoom, and Minecraft with flatpak.
- throwawayffffas 6y agoUsually their developers will have ppas.
- banger180 6y agoAnd what if i do not use a debian based distro for which the ppa works? Maintaining one package that works on all distros is a lot easier.
- maeln 6y agoppas doesn't work if you don't use ubuntu/debian. And not everybody was willing to go through the trouble of making a ppa, an AUR package, a custom .rpm, etc, etc.
- boring_twenties 6y agoYou can install Spotify and Zoom with apt.
- jeltz 6y agoAnd Discord and Steam.
- 6y ago
- IshKebab 6y agoSo basically Flatkill was right. It's weird to see so much written about an issue that could be fixed in like 5 minutes. Just change it so instead of "Sandboxed" it says "Limited Sandbox (?)". The thing about updating SSH doesn't really feel like a flaw in Flatpak to me. It's just a trade-off. Lying about sandboxing is inexcusable though.
- throwawayffffas 6y agoWhile I kind of get the problem flathub is trying to solve. I have to ask how often have you guys found yourself unable find a package (in your distributions package manager) for the software you want. I personally use debian (now in qubes os). And for all the software I want there is either a package in the debian repositories, or there is a ppa, or a single sad package on the devs site.
- bkor 6y ago> I have to ask how often have you guys found yourself unable find a package Often enough if you don't use Debian/Ubuntu/Fedora. Similarly, the package might be out of date. That eventually more of the software can be sandboxed is nice as well.
- jraph 6y agoDebian kind of spoils you in this regard though. Go out of Debian and Ubuntu, and you are probably going to miss some package at some point. On Debian, Flatpak can still be useful to get the latest version of some apps too. I'm not a big fan however. At work, I'm using the Kate Flatpak package on Debian Buster (to have syntax highlighting for the programming language I use), but the open and save dialogs are a bit buggy and you cannot open another file in a new tab from the terminal or the file manager (it will open a new window). Integration is not great, I often just use the native Kate and do without the syntax highlight.
- maeln 6y ago> I have to ask how often have you guys found yourself unable find a package (in your distributions package manager) for the software you want. Very often. Or I just want a updated version. There is a lot of small/obscure open-source tool available on github (for example) to do X or Y. Most of them don't have a package, and if they have, it is often not really maintained and very outdated. The same apply if you need to use closed-source / not entirely open-source software. I remember all the time I had to figure out what kind of build system the app was using, running cmake/make/some weird build sys, only to figure out that I was missing some lib, and that the repo version was not compatible so I had to also deal with dependency manually, and then figure out the different build option, ...
- deleted 6y ago[deleted]
- thih9 6y agoRecent discussion as part of another submission: https://news.ycombinator.com/item?id=26528805 https://news.ycombinator.com/item?id=26528805
- remram 6y ago> While punching holes in the sandbox is not the most secure implementation in the world, it is only a temporary solution. It is better than not sandboxing at all. Is it though? My point of view is that it is the worst of both worlds. On one side application developers have to deal with changing Flatpak features like portals and the complexities of making their app work sandboxed, and on the other side users get no actual security whatsoever since there are still giant holes like bashrc. It would probably be better to disable security features entirely, so that apps can be packaged easily, until they provide actual security for the users. Since app developers will have to re-package anyway, make them do it then. In the meantime everyone is just alpha-testing features that don't provide value.
- haolez 6y agoFrom TFA regarding security updates on libraries and dependencies: "A valid point. Since the Flatpak developers were fully aware of this problem, they came up with an acceptable and easy solution: flatpak-external-data-checker (f-e-d-c). f-e-d-c is a tool that automatically checks for external sources, such as dependencies and binaries. When an update is found, flathubbot automatically submits a merge request. Here are some concrete examples: [1] [2]." At this point, it's getting more complex and harder to deploy than dynamically linked binaries, is it not?
- Decabytes 6y agoI think criticism of open source projects is valid, so I'm in no way saying we shouldn't, but it's so frustrating to see people just crapping on a project for not doing things the way the person wants. I can't remember where this quote is from, or who said it, but it gos along the lines of As a critic, I'm in the privileged position of being able to critique someone's lifes work And I think that sentiment could be felt more often. It's so easy to be on the outside looking in and critique everything that is wrong with something. But making things is hard, and trying to fix things that weren't necessarily a priority during a projects inceptions is even harder. I just wish more people would support each other when they share their projects to the world