Sudo chmod u+s /Applications/OpenSource/VirtualBox.app/Contents/MacOS/VBoxNetDHCPĪnother requirement of hardening is that every path component of the parent directory of VirtualBox.app/ is owned by root and not world writable. Sudo chmod u+s /Applications/OpenSource/VirtualBox.app/Contents/MacOS/VBoxNetAdpCtl Sudo chmod u+s /Applications/OpenSource/VirtualBox.app/Contents/MacOS/VBoxHeadless Sudo chmod u+s /Applications/OpenSource/VirtualBox.app/Contents/MacOS/VirtualBoxVM Sudo chmod u+s /Applications/OpenSource/VirtualBox.app/Contents/MacOS/VirtualBox Sudo chown -R root:admin /Applications/OpenSource/VirtualBox.app/ Now make sure that the setuid stubs have the correct permissions: There isn't any support for installing VirtualBox into a target directory.
#Mac os for virtualbox image install#
Next rebuild VirtualBox and install it into /Applications/OpenSource/. You can prevent that by adding the following to LocalConfig.kmk: Starting with VirtualBox 4.1, extra debug symbols are created. It may also make sense to disable some of the development only stuff, like test cases. VBOX_PATH_APP_DOCS = "/Applications/OpenSource/VirtualBox.app/Contents/MacOS" VBOX_PATH_SHARED_LIBS = "/Applications/OpenSource/VirtualBox.app/Contents/MacOS" VBOX_PATH_APP_PRIVATE_ARCH = "/Applications/OpenSource/VirtualBox.app/Contents/MacOS" VBOX_PATH_APP_PRIVATE = "/Applications/OpenSource/VirtualBox.app/Contents/MacOS" If you like to change that, say into /Applications/OpenSource/VirtualBox.app/, you need to add the following to the LocalConfig.kmk: The default install directory of VirtualBox is /Applications/VirtualBox.app/. Hardening needs some additional configuration and post-build steps. Never disable hardening (see previous section) when creating packages for redistribution.
This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten). Also, it will create an environment setup script called env.sh. If it finds everything it needs, it will create a file called !AutoConfig.kmk containing paths to the various tools on your system. You can manually set the target architecture with -target-arch=x86 or amd64, if some architecture related problems occur.
#Mac os for virtualbox image mac os x#
Xcode matching your Mac OS X version ( ).