-
-
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
Mechanism for advertising supported qubes-services #4402
Comments
Support 'supported-service.*' features requests coming from VMs. Set such features directly (allow only value '1') and remove any not reported in given call. This way uninstalling package providing given service will automatically remove related 'supported-service...' feature. Fixes QubesOS/qubes-issues#4402
List everything that can be enabled/disabled with qvm-service. QubesOS/qubes-issues#4402
List everything that can be enabled/disabled with qvm-service. QubesOS/qubes-issues#4402
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Qubes OS version:
R4.0
Description
Right now there is no mechanism for register supported services. One can enable/disable service with
qvm-service
(or GUI VM settings) with arbitrary name. If that name is recognized by the VM's scripts, it will act upon it. If not - it will be silently ignored. This means for example typos are impossible to detect at service setting stage.It would be useful to have some mechanism VM could use to advertise support for a service. This would help UI to detect common mistakes, but also to present appropriate settings (for example disable settings not supported in given VM). We have
qubes-firewall
feature to advertisequbes-firewall
service support, but more generic mechanism is needed.Proposed solution: introduce
supported-service.*
features and allow VMs to request enabling/disabling them.It should still be possible to set arbitrary service, but tools could warn if such service is not advertised as supported.
Related: #3948
The text was updated successfully, but these errors were encountered: