Sharing a 'small' inconvenience I had to fix with #opensuse #slowroll (I suspect #tumbleweed is the same) - I couldn't launch snaps (spotify, bitwarden) after update - error was: ` cannot
❌ Ditto@fosstodon.org to 
@linux Sharing a 'small' inconvenience I had to fix with #opensuse #slowroll (I suspect #tumbleweed is the same) - I couldn't launch snaps (spotify, bitwarden) after update - error was: cannot determine seccomp compiler version in generateSystemKey fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory
The fix (I first tried re-installing, didn't work) was to:
a. locate snap-seccomp - was in /usr/libexec/snapd
b. symlink: ln -s /usr/libexec/snapd /usr/lib/snapd
You are viewing a single comment
@pastermil @linux the attack surface for something that isn't officially maintained by the developers, and that doesn't have more vetting (e.g. distribution packages) opens up room for malicious actors.
e.g. #arch / #aur recommends verifying scripts manually before installing, and malicious scripts have been found and removed.
There are actors like #jiatan out there. An unofficial #flatpak needs manual verification before install - that's why I just go with #snap if the flatpak isn't official
@thegreybeardofthetree @pastermil @linux
FYI FlatHub uses GitHub Actions, you can check how they build their apps and some of them support reproducible builds, just in case you want to verify GitHub isn't acting maliciously.
FlatHub and AUR can't really be compared in terms of security. Flatpak apps also don't modify the host OS, while AUR packages can.
Personally, I only trust distro packages and FlatHub.
Funny that Jia Tan was an official maintainer of xz until he was found to be problematic.
Speaking of verifying, you know you can't really verify anything on the snap server since they're proprietary, right? On the contrary everything on flathub is laid to bare for anyone to look at.
In the end, you're free to choose. Since you've kindly provided your argument, I've provided mine in hope you'd reconsider.