Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Virtualbox oracle-cert expired #90

Closed
NoumanSaleem opened this issue Jan 24, 2017 · 3 comments
Closed

Virtualbox oracle-cert expired #90

NoumanSaleem opened this issue Jan 24, 2017 · 3 comments

Comments

@NoumanSaleem
Copy link

The oracle-cert included with this repo is expired, causing the installation of virtualbox guest-additions to fail.
@bflad
Copy link

bflad commented Jan 30, 2017

In my local setup I was able to overwrite floppy/oracle-cert.cer with cert/vbox-sha1.cer from the VirtualBox 5.1.14 Guest Additions ISO (found at /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso on OS X) and have the Guest Additions install correctly running make virtualbox/eval-win7x64-enterprise. I'm not sure if that's the correct way to handle this situation (we might want to use the built-in ISO cert/VBoxCertUtil.exe available since VirtualBox 4.2), but thought I'd share.

barkingfoodog pushed a commit to barkingfoodog/windows that referenced this issue Jan 30, 2017
@omnis-jedi
Updating oracle cert per boxcutter#90
71008b0
@dbroeglin dbroeglin mentioned this issue Feb 2, 2017
Merged
exospheredata pushed a commit to exospheredata/boxcutter_windows that referenced this issue Mar 22, 2017
@goodrum
FIX: Remove hard dependency on the repo copy of the Virtualbox tools …
7346b6a 
…and include steps in script/vmtool.bat to handle the dynamic import of the certificate from the ISO. This solution resolves boxcutter#90 while not introducing any pattern changes or dependencies.
@tas50
Copy link
Contributor

tas50 commented May 3, 2017

Resolved in #100 until 2019 although I think exospheredata@7346b6a is probably a better long term solution

@tas50
Copy link
Contributor

tas50 commented May 6, 2017

I've fixed this on master until sometime in 2019, which gives us some time to better pull the cert right from the ISO

@tas50 tas50 closed this as completed May 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bflad @NoumanSaleem @tas50