Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd $adminvm policy keyword #2872
Comments
marmarek
added
C: core
enhancement
P: major
labels
Jun 27, 2017
marmarek
added this to the Release 4.0 milestone
Jun 27, 2017
marmarek
self-assigned this
Jun 27, 2017
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Jun 27, 2017
marmarek
referenced this issue
in QubesOS/qubes-core-admin
Jun 27, 2017
Merged
Policy related changes for Qubes 4.0 #121
marmarek
closed this
in
marmarek/qubes-core-admin@26ea836
Jul 4, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
qubesos-bot
Jul 4, 2017
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
qubesos-bot
commented
Jul 4, 2017
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Jul 4, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Jul 4, 2017
Closed
core-admin v4.0.1 (r4.0) #100
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedJun 27, 2017
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
$anyvmnot matching$adminvmmore 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
dom0and$adminvm.Cc @rootkovska