Opened 9 years ago
Closed 9 years ago
#15087 closed defect (worksforme)
VirtualBox not handling dll certificate properly - blocking startup of VMs
| Reported by: | zadarum | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.0.14 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
I am unable to start any VMs in VirtualBox 5.0.14 running on Windows 7. I have BeyondTrust's PowerBroker software installed, and the certificate date on one of its DLLs is expired. As this thread points out: https://forums.virtualbox.org/viewtopic.php?f=6&t=69580 VB is not handling expired certificates properly, since the consensus is that a certificate is still valid as long as it was valid at the time the code is signed. My VBHardening.log file is attached.[[]]
Attachments (1)
Change History (3)
by , 9 years ago
| Attachment: | VBoxHardening.log added |
|---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
No response, closing. Before you consider to reopen this ticket, please check VBox 5.0.16.
Note:
See TracTickets
for help on using tickets.
Do you have any evidence for your claim that VirtualBox rates expired certificates as invalid signatures? I'm very uncertain that the people in the forum know what they're talking about.
Makes no sense, as otherwise VirtualBox wouldn't work on most Windows installs out there. For example the "rsaenh.dll" on an up to date Windows 7 install was signed (and timestamped) in 2009, with a certificate which is valid from 2008 to 2010. Your VBoxHardening.log clearly shows that VirtualBox is successfully validating this signature.
That said, there apparently is some other issue which needs investigating.