I am well aware of it. It is an example of the traditional distribution workflow preventing a backdoor from landing into Debian Stable and other security-focused distributions.
Of course the backdoor could have been spotted sooner, but also much later, given its sophistication.
In the specific case of xz, "Jia Tan" had to spend years of efforts in gaining trust and then to very carefully conceal the backdoor (and still failed to reach Debian Stable and other distributions).
Why so much effort? Because many simpler backdoors or vulnerabilities have been spotted sooner.
Also many less popular FOSS projects from unknown or untrusted upstream authors are simply not packaged.
Contrast that with distributing large "blobs", be it containers from docker hub or flatpak, snap etc, or statically linked binaries or pulling dependencies straight from upstream repositories (e.g. npm install): any vulnerability or backdoor can reach end users quickly and potentially stay unnoticed for years, as it happened many times.
They have to watch hundreds to thousands of packages so having them do security checks for each package is simply not feasible.
That is what we do and yes, it takes effort, but it is still working better than the alternatives. Making attacks difficult and time consuming is good security.
If there is anything to learn from the xz attack is that both package maintainers and end users should be less lenient in accepting blobs of any kind.
They do now have a verified tick in Flathub to show if a Flatpak is official
Jia Tan liked your comment
Without the traditional distribution workflow what prevents flatpaks to be full of security issues?
Unfortunately sandboxing cannot protect the data you put in the application.
I would love a text based ActivityPub client focused on meaningful discussions: threaded view, ability to follow threads or branches, highlight posts based on keywords.
You are better off with an encrypted password store and a 2FA on a phone. You can back up both, easily, and they are both protected with fingerprints and/or global passwords.
People panic about face scan while the ongoing massive privacy breaches exist around online services and electronic devices. The amount of personal data that people pour into smartphones is enormous compared to using that vending machine. We need more GDPR.
I would come along a question that I was well educated on, and the top voted responses were all very clearly wrong, but sounded correct to someone who didn’t know better.
This can be said to https://news.ycombinator.com/ as well. I wonder how much of this is due to sock puppets and bots.
Github is designed to centralize git (as the word "hub" suggests). You can still migrate away code, issues and wikis, but contributors, followers, wiki editors, issue subscribers, visibility in general and github stars are locked in. Discoverability matters to projects trying to attract contributors.
You can use firejail or other sandoxes with any application packaged in any distribution.