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.

Sign up for GitHub

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

Jump to bottom

Add $adminvm policy keyword #2872

Closed
marmarek opened this issue Jun 27, 2017 · 1 comment
Closed

Add $adminvm policy keyword #2872

marmarek opened this issue Jun 27, 2017 · 1 comment
Assignees
@marmarek
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. r4.0-dom0-cur-test T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Milestone
Release 4.0

Comments

@marmarek
Copy link
Member

Since dom0 is special, it's better to refer to it by special policy keyword, instead of name like any other VM. For example this will make $anyvm not matching $adminvm more logical.
Also, dom0 name is Xen specific, so we will need some flexibility here when porting Qubes to other hypervisor anyway.

For Qubes 4.0, policy will recognize both dom0 and $adminvm.

Cc @rootkovska
@marmarek marmarek added C: core T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. P: major Priority: major. Between "default" and "critical" in severity. labels Jun 27, 2017
@marmarek marmarek added this to the Release 4.0 milestone Jun 27, 2017
@marmarek marmarek self-assigned this Jun 27, 2017
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Jun 27, 2017
@marmarek
qubespolicy: add $adminvm keyword for specifying dom0 aka AdminVM
259724b 
Fixes QubesOS/qubes-issues#2872
@marmarek marmarek mentioned this issue Jun 27, 2017
Merged
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-core-dom0-4.0.1-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 qubesos-bot mentioned this issue Jul 4, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marmarek marmarek

Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. r4.0-dom0-cur-test T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Milestone
Release 4.0
Development

No branches or pull requests
2 participants
@marmarek @qubesos-bot