In the default deployment of a VDI, the VDI (or equivalent file) is readable and writeable by the UNIX user running VirtualBox
For people using iSCSI, the iSCSI credentials are stored in a configuration file that is readable by the UNIX user who runs VirtualBox In both cases, this means that the UNIX user can modify the raw VDI filesystem contents, possibly modifying scripts that would run with root privileges or just breaking the VDI in some way that requires extra support effort. Is there any way to have the VDI file or settings owned by a system user (e.g. a user called vbox) such that they would only be accessible to the hypervisor and the user can only interact with the VM through the GUI? ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
