Skip to content
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

Closed
marmarek opened this issue Oct 18, 2018 · 2 comments · Fixed by QubesOS/qubes-core-admin#238
Closed

Mechanism for advertising supported qubes-services #4402

marmarek opened this issue Oct 18, 2018 · 2 comments · Fixed by QubesOS/qubes-core-admin#238
Labels
C: core P: minor Priority: minor. The lowest priority, below "default." r4.0-dom0-stable T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@marmarek
Copy link
Member

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 advertise qubes-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

@marmarek marmarek added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: core P: minor Priority: minor. The lowest priority, below "default." labels Oct 18, 2018
@marmarek marmarek added this to the Release 4.0 updates milestone Oct 18, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 21, 2018
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
marmarek added a commit to marmarek/qubes-core-agent-linux that referenced this issue Oct 22, 2018
List everything that can be enabled/disabled with qvm-service.

QubesOS/qubes-issues#4402
marmarek added a commit to marmarek/qubes-core-agent-linux that referenced this issue Oct 23, 2018
List everything that can be enabled/disabled with qvm-service.

QubesOS/qubes-issues#4402
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-core-dom0-4.0.33-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-core-dom0-4.0.37-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core P: minor Priority: minor. The lowest priority, below "default." r4.0-dom0-stable T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants