Bugs related to reused VMIDs

[joebaires]

Hello,

This is my first message in this forum and I would like to discuss an issue I find problematic on Proxmox.

In brief: VMIDs should be auto-incremental, like in a database.

Currently, when you remove a VM/CT, the ID becomes available again, and the next time you create a virtual machine It will be used (proxmox will suggest the least available ID).

One of the severe consequences of this, is that the new machine will inherit access privileges of the previous VM, as Proxmox doesn't drop privileges when removing the VM, and they are referenced using the VMID.

I just had to learn this the hard way, with a customer complaining somebody was accessing his console.

I also think that in the same way stale privileges remain in the system, there might be similar issues with other parts of the Proxmox system.

Would like to hear your opinions. Thank you

-J

 

[m.ardito]

the new machine will inherit access privileges of the previous VM, as Proxmox doesn't drop privileges when removing the VM, and they are referenced using the VMID.

Hi,
maybe it will be more clear if you detail a bit which "privileges" you are specifically referring to...

if you created a user which can access pve web interface to use a VMID, someone could answer that if you remove the VMID then is your duty to make sure your permissions are always updated.

nobody else can know if you recreate the same VMID and give it to the ANOTHER customer, or if you recreate the same VMID and give it to the SAME customer (then if pve destroyed your previous permissions, your customer would complain that he's no more able to access the same VMID...)

I agree that pve could at least WARN you if some resource (permissions, pools I don't know what is left, I don't have external customers) related to the VMID will be left untouched (or not), so for you to know and act accordingly.

Marco