On 01/09/14 13:03, jdd wrote: > Le 01/09/2014 11:03, Daniel Pocock a écrit : >> 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? > why don't you run it as vbox user, and keep this user private? > > access to the virtual machine have no relation with the user running the box
How does that work in practice though? Is there a recommended way to set this up? Do you mean running the VirtualBox GUI as user vbox with sudo? ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
