5 ms·
note that the response partially agrees with the points raised, it looks like a constructive discussion overall.
by ekianjo 6y ago
note that the response partially agrees with the points raised, it looks like a constructive discussion overall.
- nextlevelwizard 6y agoIt is hard to guess at motives when author is unknown. Or when neither of the CVE links go anywhere. Maybe I've understood how Flatpaks work incorrectly (please correct me if so), but the applications are ran in containers. So how would an attacker exploit CVE-2019-17498 on a Gitg? Its not like Gitg has a port open for listening incoming messages. With ffmpeg I don't know if things like Chromium are actually using the flatpak ffmpeg or if they ship with their own libs.
- eis 6y agoWhich is good as one should discuss the merits of the arguments brought forth when discussing the pros and cons of a technology rather than who who said it or what motives they might have. Edit: when I wrote this comment only the first sentence of the parent existed.
- necovek 6y agoYou've misunderstood "how Flatpaks work": they are using the same system calls that containers use for containerization but in a different way, look at https://en.wikipedia.org/wiki/Linux_namespaces https://en.wikipedia.org/wiki/Linux_namespaces (Snaps use AppArmor too if that's a more familiar technology). They are not containers in themselves: if you feel this is pedantic, the way namespaces are used can make all the difference (eg. why you should not be running stuff in docker containers as root which can easily be used to get root on the host).
- foobar33333 6y agoThe criticism and response typically boils down to "Yes, but its actually not any worse than what we have now" If you manually install a rpm, deb or add a new repo, your system is completely owned by the person who built that package or repo. The biggest problem is that flatpak advertises sandboxing when some apps disable it but I imagine in the future we will get better UI around showing the user exactly what gets exposed as well as less permissions being given to packages.
- eeZah7Ux 6y ago> If you manually install a rpm, deb or add a new repo, your system is completely owned by the person who built that package or repo True, and the same is true for flatpak given that the author of the package controls the sandboxing. The only solution is to have 1 or 2 trusted packagers to review the package, including its code - which is what some Linux distributions do. Furthermore, Debian does a long release freeze for the stable release and a lot of users test it. A malicious package might well be spotted. Contrast it with the very lightweight vetting that is done by others.
- foobar33333 6y agoFlathub actually does review submissions reasonably well. You have to give a justification for each permission you request and why it couldn't be done in any other way.
- necovek 6y agoThe thing is that messaging is the important bit here. If I have Debian apt archives in my sources.list, I understand the risks, just like a pure Windows user does: other than bugs, you might be affected if someone hacks Debian/Microsoft and that's it (or, of course, someone internal to them decides to do it). Flatpaks/snaps are designed to be built by less-trusted parties and promise things they know they can't deliver on. Now I am suddenly asked to trust these external developers that they will be as adamant with security fixes, be non-malicious, etc. And flatpak/snap are trying to convince me how that's a non-issue "because sandboxing". Sure, we here understand the underlying technologies so we can make our own educated guesses, but majority of the people who this is aimed at don't. Since you also mentioned "add a new repo", there are some repos you can trust even if they are not the official ones. PPAs on Launchpad build from source packages, so you can always get the source first ("apt-get source package" after adding the repo). If someone is just bundling binaries and the build is a no-op, you can drop the repo right away. Sure, it requires some effort and you won't be checking every repo, but for sufficiently popular repos, somebody would be doing that. It'd be ideal if apr grew support for limiting packages that can come out of a repo, so you'd have to whitelist when something new pops up ("hey, this repo has now introduced libc version X, and your libc is coming from repo main: do you want to allow upgrades from non-main repo to libc? [only once] [yes] [no]").
- mands 6y agoAgreed, as far as constructive discussion can be had with a post from a domain called flatkill.org :)