virtualbox.org

The problem is that VirtualBox is not exposing SSBD flag (and of course, potentially also the relevant instructions, I cannot confirm the latter).

As I already explained, the guest is executing random untrusted code (in user mode). I do not wish that this user mode code is able to escalate itself to root level or even further to the host level. I am really confused by your last question... Of course the security hole needs to be patched and mi...

Just for the clarification: my problem is not solved since I am not using Windows 10 guest (for which the problem did solve), but instead mainly CentOS guest, and sometimes also Ubuntu guest.

Thanks. I was not aware of this option. I turned it on. The results are: In Windows 10 VM both of the Spectre mitigations are successfully enabled (after turning on the above mentioned option). Unfortunately, in Ubuntu VM nothing has changed, installed all updates and rebooted, no improvement. And i...

Thanks for the clarification! Do you know, is anybody working on the Spectre microcode compatibility update for VirtualBox? When could it be ready for testing? Also, it still would be interesting to know - is there any way to replace VirtualBox dll-s with custom signed ones? Is the only way forward ...

Thanks for trying the situation! I am sorry, the last log file must have been overwritten before I managed to zip it. I am sending a new correct one where the error is visible (this is with just one possible certificate and signing mode I had used, I also used different certificates and signing mode...

Thanks for the suggestion! Is it certain that VirtualBox will load the test-signed dll when testsigning is turned on? I turned testsigning on, rebooted. Tried signing either with my self-generated certificates (sha1 and sha256), or alternatively, with a test signing certificate automatically generat...

My intention is modifying the bytes that store the CPU microcode revision number returned to VM.

I need to modify a few bytes in VBoxVMM.dll. Unfortunately, VirtualBox refuses to start the VM with the modified dll. My procedure was the following: 0. Closed VirtualBox and also killed VBoxSvc.exe 1. Modify the dll. 2. makecert -r -ss myPrivateCert1 -n "CN=My Company Inc." testCert1.cer ...