On 08/14/2017 12:47 PM, James Moe wrote:
On 08/14/2017 02:45 AM, Klaus Espenlaub wrote:
[ error message ]
Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10)
Please try reinstalling VirtualBox.
where: SUPR3HardenedMain what: 2 VERR_PERMISSION_DENIED (-10) -
On 08/14/2017 02:45 AM, Klaus Espenlaub wrote:
>>
>> [ error message ]
>> Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10)
>> Please try reinstalling VirtualBox.
>> where: SUPR3HardenedMain what: 2 VERR_PERMISSION_DENIED (-10) -
>> Permission denied.
>
> That error
On 08/14/2017 04:45 AM, Klaus Espenlaub wrote:
That error message means that the VirtualBox executable isn't installed suid
root (which the hardening expects and complains about by pointing at the user id
information for the running process).
Our spec file does not install /usr/bin/VirtualBox
Hi Hans,
the other platforms also have KPIs or similar constructs for figuring
out whether the client process issuing the I/O controls is a 32-bit or
64-bit one. However, using the VBOXGUEST_IOCTL_FLAG set to 0 or 0x80 if
32-bit or 64-bit was a less complex (+faster(+safer)) way of deal with
That error message means that the VirtualBox executable isn't installed
suid root (which the hardening expects and complains about by pointing
at the user id information for the running process).
On 14.08.2017 01:37, James Moe wrote:
On 08/11/2017 08:52 AM, Larry Finger wrote:
Just for my
On 14-08-17 09:27, Hans de Goede wrote:
Note to linux-kernel readers: This Cc-ed to linux-kernel because it is
relevant for the "[RFC 0/2] Add Virtual Box vboxguest and vboxsf guest
drivers to the mainline kernel" thread.
Hi Michael, Knut,
My first submission of the vboxguest driver for
On some operating-systems the driver can tell whether an ioctl is a
32bit compat callback or not without looking at the ioctl-nr, at a flag
argument to pass this info along and use it for Linux to not need
separate ioctl codes for 32 and 64 bit.
Signed-off-by: Hans de Goede