-
-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request]: setting to block non-freedom Flatpaks by default; setting to block unverified Flatpaks by default; --allow-nonfreedom
, --allow-unverified
#5654
Comments
This is already implemented: https://docs.flathub.org/docs/for-users/installation/#subsets |
Nice. But that only shows the Configuration file format in:
The following configuration snippet works for Flathub upstream default repository (not using any subsets): File
How to enable the subset using such a configuration file? That seems to be undocumented. Appending to that file:
does not work. Is this possible? |
Appending
seems to work. That is documented here: Under It's confusing that the internal config file |
Checklist
Suggestion
Issue:
For a Linux distribution (Kicksecure) (and Whonix), we are considering to enable Flathub by default. But there's 2 major concerns.
Software that is considered both under FLOSS licenses and verified is considered much more trustworthy.
Suggested Distribution Settings File:
The distribution could drop a configuration snippet in the yet to be invented
/usr/lib/flatpak/settings.d
folder.File
/usr/lib/flatpak/settings.d/30_kicksecure.conf
:This is just a default setting suitable for some Linux distributions. The user should have the freedom to easily undo this.
Suggested User Override Settings File:
File
/etc/flatpak/settings.d/50_user.conf
:Suggested User Command Line Overrides:
For overrides on the command line case by case:
--allow-nonfreedom
--allow-unverified
Suggested
flatpak
command line output output:The text was updated successfully, but these errors were encountered: