[vbox-dev] (no subject)

[Austin English]

On Wed, Jan 27, 2016 at 1:56 AM, Frank Mehnert <frank.mehnert at oracle.com> wrote:
> Hi Austin,
>
> On Wednesday 27 January 2016 00:13:18 Austin English wrote:
>> Well, Virtualbox hadn't compiled, I was hitting
>> https://www.virtualbox.org/ticket/1499.
>>
>> Using a 32-bit kernel instead, I was able to get VirtualBox 4.3.32 to
>> build. The results:
>>
>> # hardened, no sudo
>> amnesia at amnesia:/media/amnesia/e3f702b9-64b4-40c2-96c3-ef6cf856e129/VirtualB
>> ox-4.3.32/out/linux.x86/release/bin$ ./VirtualBox
>> VirtualBox: Error -10 in SUPR3HardenedMain!
>> VirtualBox: Effective UID is not root (euid=1000 egid=1000 uid=1000
>> gid=1000)
>>
>> VirtualBox: Tip! It may help to reinstall VirtualBox.
>
> that will not work of course. Running a hardened build from the bin
> directory is not supported. A hardened build will only run if it's
> installed to /opt/VirtualBox and the stubs (VirtualBox, VBoxHeadless,
> VBoxSDL, VBoxNetDHCP, VBoxNetNAT) are installed as suid root.

Thanks for the tip. Is that documented somewhere?
https://www.virtualbox.org/wiki/Linux%20build%20instructions indicates
that a hardened build can from from the build dir if some symlinks are
made (which they were already for me by the build), and some files are
chmod'ed/chown'ed. There's no mention of installing to /opt.

>> # hardened, as sudo:
>> amnesia at amnesia:/media/amnesia/e3f702b9-64b4-40c2-96c3-ef6cf856e129/VirtualB
>> ox-4.3.32/out/linux.x86/release/bin$ sudo ./VirtualBox
>> [sudo] password for amnesia:
>> VirtualBox: supR3HardenedVerifyDir: Failed to open "/opt/VirtualBox":
>> No such file or directory (2)
>
> See above, wrong directory.
>
>> # non-hardened, no sudo:
>> Dialog Box: Kernel driver not accessible
>>
>> Failed to open a session for the virtual machine asdf.
>>
>> The virtual machine 'asdf' has terminated unexpectedly during startup
>> with exit code 1 (0x1).
>>
>> Result Code: NS_ERROR_FAILURE (0x80004005)
>> Component: Machine
>> Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
>
> This would work if you would adapt the permissions of the /dev/vboxdrv
> device to be readable+writable as normal user. This can be done using
> a proper udev rule.
>
>> # non-hardened, sudo:
>> starts up
>>
>>
>> tl;dr: only works with hardening disabled, as root.
>
> Kind regards,
>
> Frank
>
>> On Thu, Jan 21, 2016 at 5:29 PM, Alexey Eromenko <al4321 at gmail.com> wrote:
>> > find /vbox-src/ grep VirtualBox
>> > $ cd [PATH]
>> > $ ./VirtualBox
>> >
>> > On Fri, Jan 22, 2016 at 1:21 AM, Austin English <austinenglish at gmail.com>
>> >
>> > wrote:
>> >> How can Virtualbox be started from compile directory? There were a few
>> >> errors, so I'm not sure that it's usable.
>> >>
>> >> On Thu, Jan 21, 2016 at 5:19 PM, Alexey Eromenko <al4321 at gmail.com>
> wrote:
>> >> > VBox compiled, and even test units ran fine.
>> >> >
>> >> > But I see a linker error in last stage:
>> >> > kBuild: Linking VMMR0
>> >> > ...
>> >> > kmk: Target `all' not remade because of errors.
>> >> >
>> >> > But no idea what is this error.
>> >> > Check if kernel module compiled and works.
>> >> > Try to load it
>> >>
>> >> --
>> >> -Austin
>> >
>> > --
>> > -Alexey Eromenko "Technologov"
>
> --
> Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox
> ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany
>
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstraße 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
>
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev



-- 
-Austin