Il 2014-10-17 07:14 Iosif Peterfi ha scritto:
Greetings,
If someone 'malicious' has the permissions to delete
the HDD files, then he might as well shut down or kill the virtual
machines processes before deleting everything. And the HDD data is the
least important problem in this situation. Since you must have backups
for everything already and start the recovery. IMHO more important is
the question when and how the 'malicious' person acquired admin
privileges. This might give you a clue on which backup to recover.
Locking the disk file would do more bad than good since
it will prevent admins from doing simple administrative tasks as
resetting a password on the VM.
In any case you could delete the qcow file via rm cmdline...
The solution is only the backup as said from Iosif...
I think that even removing the qcow2 when the VM is stopped could
be a problem... no?
:-)
Diaolin
---
A volte la storia si sovrappone a te che la vivi per riannodare il tuo
cammino ad un filo costantemente teso tra ieri e domani, portandoti
a ripercorrere un tempo compagno dei tuoi passi per lunghi anni.
Poi, finalmente, il filo si spezza e riesci a comprendere il tuo oggi.
[Diaolin]
349 66 84 215
349 72 65 081
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
