top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

VBox: protecting VDI images and iSCSI raw devices

0 votes
449 views

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?

posted Sep 1, 2014 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

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

answer Sep 1, 2014 by Anderson
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?
commented Sep 1, 2014 by anonymous
Similar Questions
+2 votes
Fedora 23 and VirtualBox: VBox Guest Additions not working properly

I have just upgraded to 23 from 22 in a virtual machine using dnf as described in the Fedora Wiki, which went rather smoothly for me.

After manually installing the Guest Additions, the features "seemless windows" and "automatic resize of the guest desktop" don't work (the respective options in the views menu are greyed out).

The VBox kernel modules are built ok, but I get a warning saying: "unsupported pre-release version of X.Org server installed. Not
installing the X.Org drivers."

The X log says that there is X.Org X Server 1.17.99.902 installed, which is a pre-release. I guess downgrading might cure the problem, but how?

Any advice?

0 votes
VirtualBox and the USB flash drive

VirtualBox defaults to using the CDROM/DVD drive which is pretty worthless unless you have a supply of blanks, I don't have many on hand presently. I have been trying to make the USB function work without much success.

Googling suggests group/user problems, I have myself and root listed as vboxusers. The GUI has a USB menu which is always grayed, where I can create a filter, it recognizes the Sandisk flash drive when entered, I click on OK and nothing is saved apparently.

Now I've run across something in google that suggests an entry in fstab may be required? Has any one worked through this maze who can suggest how to make it work?

0 votes
Centos 6.4 and Virtualbox

I'm trying to install Centos 6.4 under Virtualbox on a Mac running Lion. I downloaded the 2 iso DVD files and set Virtualbox to boot from DVD 1

When I start the vm it puts out a lot of messages then asks me what kind of install I want to do. I select the basic install and it tells me it found the media ( the iso DVD file I downloaded) puts out a message about the anaconda ( I think) install starting then goes to a screen with the Centos 6 logo and appears to do nothing. No more messages appear.

Should I be using the minimal iso install file?

I have installed Windows XP, 7 and 8 under Virtualbox and they all work. I also installed Ubuntu but didn't like it so I removed it and thought I would try Centos

Does anyone know what might be going on and how to get it working?

0 votes
FSL in VMware workstation play on windows 10.

FSL in VMware workstation play on windows 10. I am not able to open 80 MB or its compressed form 27 Mb file of .nii extension while 18Mb file is opening in FSLeyes.

...