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 upVM names should not allow keywords #2857
Comments
andrewdavidwong
added
C: core
C: qubes-manager
enhancement
labels
Jun 19, 2017
andrewdavidwong
added this to the Release 3.2 updates milestone
Jun 19, 2017
marmarta
referenced this issue
in QubesOS/qubes-core-admin
Nov 4, 2017
Merged
Disallow 'default' as VM name #162
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Fixed in QubesOS/updates-status#293 |
marmarek
closed this
Nov 5, 2017
svenssonaxel
referenced this issue
Dec 9, 2017
Open
(design improvement) Split domain name space #3385
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
svenssonaxel commentedJun 18, 2017
Qubes OS version (e.g.,
R3.2):R3.2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):N/A
Steps to reproduce the behavior:
Use the VM Manager to create a new NetVM with the name "default".
Expected behavior:
The operation fails, similarly to the names "none", "true" and "false".
Actual behavior:
The NetVM is created. This leads to an ambiguity in the following command:
qvm-prefs -s my-new-vm netvm default
General notes:
To avoid similar mistakes in the future, maybe keywords should be uniformly distinguished from VM names, e.g. begin with _ or $, similarly to the current policy file format that uses $any and $dispvm. This would also provide backward compatibility with backups if new keywords are introduced in the future.
Related issues: