this post was submitted on 03 Nov 2023
189 points (94.4% liked)
Linux
48366 readers
1158 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Flatpaks are great. I do wish flatseal was part of the flatpak standard. I want an android style permissions menu
Well, Flatseal is using flatpak's standard way of managing permissions. Everything it does you can also do from the command line with flatpak. It's just a frontend.
I think KDE wants to add these options to it's settings as well. That will be great, when it's better integrated into the whole system.
KDE already does have the same thing in its settings
I'd like to see permission pop ups so I know it wanted permission to do something and didn't have them, having to ask me. Sometimes it is explained that certain stuff the app does are blocked by the sandbox by default for security, but you can enable it, which is alright. Sometimes you'll just have to find that out for yourself.
I wish it would be possible now but it probably won't happen until windows and mac will have similar features. The problem is that processes cannot just read a file, because in the container it doesn't exist. It's maybe due to permission. Maybe not. You cannot tell. Android apps are written in a way that they request access, while pc apps are just reading the files directly without requesting permission.
So the app has to be written for flatpak. However, afaik, this is the maintainers goal too. Btw, the file open dialog is a currently working example of the dynamic permission handling. It's just that the app should use these features which is not guaranteed.
That makes sense. Unfortunate that we won't have it anytime soon
Same. In addition to the prompt-based permissions that @Kusimulkku@lemm.ee brings up, I'd like to see more granular control of permissions. For example, a flatpak app's access to webcams, controllers, etc. are all controlled through just one permission:
--device=all(aka "Device Access" in KDE's Flatpak Permission Settings).