-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Phase out legacy qrexec policy files #8000
Comments
New policy should be placed in /etc/qubes/policy.d. But don't place any explicit defaults and rely on implicit deny by default. This way it's easier to integrate with custom policies and GUI tools. QubesOS/qubes-issues#8000
It doesn't make sense in qubes-core-dom0-linux package, which has nothing to do with appmenus (anymore). QubesOS/qubes-issues#8000
1. Convert qubes.ReceiveUpdates to 90-default-linux.policy 2. Move qubes.SyncAppMenus to 90-default.policy in core-admin 3. Drop qubes.repos.*, since those are "deny" by default anyway QubesOS/qubes-issues#8000
1. Convert qubes.ReceiveUpdates to 90-default-linux.policy 2. Move qubes.SyncAppMenus to 90-default.policy in core-admin 3. Drop qubes.repos.*, since those are "deny" by default anyway QubesOS/qubes-issues#8000
1. Convert qubes.ReceiveUpdates to 90-default-linux.policy 2. Move qubes.SyncAppMenus to 90-default.policy in core-admin 3. Drop qubes.repos.*, since those are "deny" by default anyway QubesOS/qubes-issues#8000
New policy editor / global config handles Split-GPG policy now, don't get in its way. QubesOS/qubes-issues#8000
1. Convert qubes.ReceiveUpdates to 90-default-linux.policy 2. Move qubes.SyncAppMenus to 90-default.policy in core-admin 3. Drop qubes.repos.*, since those are "deny" by default anyway QubesOS/qubes-issues#8000
The conversion tool should take care to not duplicate default rules, and should put user-defined rules into A stretch goal is to detect policy patterns supported by GUI tools and put those into appropriate 50- policy files (for example for input proxy or split-gpg). But this need to be done carefully, as GUI global config supports only some specific rule patterns, not arbitrary rules for every service. |
Make it add rules into /etc/qubes/policy.d/60-registered-arguments.policy, instead of legacy /etc/qubes-rpc/policy. Since the new format can have multiple rules in a single file, locking is necessary. Do it the same way as other policy.* services, so it's coordinated too. QubesOS/qubes-issues#8000
Automated announcement from builder-github The component
|
Do it when building R4.2 package only. QubesOS/qubes-issues#8000
Do it when building R4.2 package only. QubesOS/qubes-issues#8000
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
How to file a helpful issue
The problem you're addressing (if any)
Legacy qrexec policy files (those in /etc/qubes-rpc/policy) are incompatible with GUI tool for setting policy, and hard to maintain via other automation while still allowing user to modify them manually.
New policy format (in /etc/qubes/policy.d) solves those issues, but legacy files (generally, when present) take precedence, limiting its usefulness.
The solution you'd like
The value to a user, and who that user might be
More possible value from GUI tools and other automation for policy management.
The text was updated successfully, but these errors were encountered: