virtualbox.org

so ive noticed that

shell32.dll: Not signed
comdlg32.dll: Not signed

both have been customized , shell32.dll, the explorer back and forward buttons ive customized and comdlg32.dll , ive customized the file transfer windows colour , both seem to be the culprit in anything beyond VirtualBox-4.3.12-93733-Win , not running due to hardening

would there be an option of adding a dll whitelist option , so we can run the newer versions without issues? id appreciate it alot

i recon putting the unmodified files into the virtualbox folder wont make it work , right?

If they allow any unsigned DLL then any DLL could call itself e.g. shell32.dll and get loaded into the VBox execution space.

In any case shell32.dll is a core system DLL, as is comdlg32.dll. No way I'd accept either of those being hacked.

or as i said allow for adding the proper signed dlls to the virtualbox directory and have virtualbox use those to run instead of the systems dlls, that would as well take care of the issue without whitelisting, since simply signing the modified dlls i recon wont do the trick due to a different hash value output compared to the original signed dll