However, Windows 7 can apply Server 2008 r2's Microsoft update to get SHA256 signature capability, see viewtopic.php?f=6&t=103731&p=505523#p505520 Windows 7 is no longer a supported host OS with 6.1, so I'd bet the devs would no longer consider it a requirement to get 6.1's executables to have a Windows 7-compatible certificate. I can't speak to the devs' intentions on signing certificates, or to what they're actually able to do nowadays with what certificates they can get. Robpats wrote:I wonder if this is the intended way of signing for compatibility or there are some bugs in the signing procedures.
ox-extpack (link on Downloads page is now also updated). Reverted to VirtualBox 6.1.34 (and matching Extension Pack) and working again. Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib: code signature invalid for '/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'
Failed to install the Extension Pack /Users//Downloads/Software Updates/Oracle_VM_VirtualBox_Extension_Pack-6.1.36.vbox-extpack.įailed to load the main module ('/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'): VERR_FILE_NOT_FOUND - dlopen(/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib, 6): no suitable image found.
0 kommentar(er)
