88
Are packages from flathub always safe?
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jul 2023
88 points (97.8% liked)
Linux
48335 readers
497 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I'd recommend that you stop using Flatpak immediately, it's a horrific security nightmare.
https://flatkill.org
The fact that the website hasn't been updated since 2020 and still has an open CVE shines the light on Flatpak's attention to security.
Regarding point 3, if that's true, then why are all of the most-dowloaded packages on Flathub mislabelled as 'sandboxed' when they have full write access to a user's home directory? That isn't a sandbox.
Flatpak currently has a 7.2 vulnerability that has gone unaddressed since 2017. The maximum vulnerability rating is a 9, so this is quite major.
https://www.cvedetails.com/vulnerability-list.php?vendor_id=16613&product_id=&version_id=&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=3&cvssscoremax=0&year=0&month=0&cweid=0&order=1&trc=9&sha=14fe55bfe41eaaaaca8e742bde18bc6938f88a3e
Maybe you should have read the entries in the link you posted
Text about the 7.2 vulnerability from 2017:
That version was tagged in git on July 20th, 2017