-
-
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
Do not allow to rename VMs directly #2868
Comments
Are the initial and final system states as a result of "rename" vs. "clone & remove" different? How? Are mgmt/admin VMs somehow restricted from performing the latter? I believe I understand the underlying security motivation, but I do not see what is gained by only disallowing vm name change while clone & rm is still possible. |
Yes, Mgmt VM needs permission to manage both "old" and "new" VMs. If it's limited only to set few properties, it can't perform full clone. For example if you don't allow it to add new tags to a VM, the new VM will not have those tags set (it's up to Mgmt VM what to do - either ignore the error, or abort operation). Also, renaming VM have a lot of corner cases (technically-wise) - for example tracking VM rename over Admin API is tricky. New VM have new UUID, so it's easy to detect remove & create. |
Since VM name in immutable now, drop rename-related methods. QubesOS/qubes-issues#2868
Since VM name is immutable, rename method can be dropped from storage API. QubesOS/qubes-issues#2868
Since VM name in immutable now, drop rename-related methods. QubesOS/qubes-issues#2868
Since VM name is immutable, rename method can be dropped from storage API. QubesOS/qubes-issues#2868
Automated announcement from builder-github The package
|
In Qubes 4.0 we want to forbid changing VM
name
property. This is mostly because VM name is used in Qubes RPC policy as identifier, so renaming VM can have severe security consequences. This is especially important when such operation could be performed by semi-trusted Management VM (through Admin API).In practice changing VM name will still be possible, in two steps:
The text was updated successfully, but these errors were encountered: