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.

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

Some of the VirtualBox base boxes are currently not working #140

Open
cliffe opened this issue Mar 25, 2019 · 5 comments
Open

Some of the VirtualBox base boxes are currently not working #140

cliffe opened this issue Mar 25, 2019 · 5 comments

Comments

@cliffe
Copy link
Owner

cliffe commented Mar 25, 2019

I think some of these are recent problems, but I hadn't used VirtualBox for quite a few months.

  • The wheezy server base has just started complaining of a package management certificate/authentication issue (we need to update the image with new certs, or maybe configure apt-get to not authenticate packages)
  • The stretch kde desktop image seems to be corrupted?
  • The stretch server image complained puppet wasn't installed
@cliffe
Copy link
Owner Author

cliffe commented Mar 25, 2019

`
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'debian_stretch' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'debian_stretch' (v0) for provider: virtualbox
default: Downloading: https://app.vagrantup.com/secgen/boxes/debian_stretch_server/versions/1.1/providers/virtualbox.box
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and that enough disk space
is available and then try again.
The output from attempting to unpackage (if any):

bsdtar: Ignoring malformed pax extended attribute
x ./box.ovf
bsdtar: Ignoring malformed pax extended attribute
x ./GNUSparseFile.0/box-disk001.vmdk
bsdtar: Ignoring malformed pax extended attribute
x ./Vagrantfile
bsdtar: Error exit delayed from previous errors.
`

@cliffe
Copy link
Owner Author

cliffe commented Mar 26, 2019

I've updated the Stretch server VM, to have puppet etc -- works, but needs some further testing. Working on re-creating the Stretch KDE base, and on the others.

cliffe added a commit that referenced this issue Mar 27, 2019
@cliffe cliffe closed this as completed in 880c0b3 Mar 27, 2019
@cliffe cliffe reopened this Mar 27, 2019
@cliffe
Copy link
Owner Author

cliffe commented Mar 27, 2019

Stretch bases are now sorted for VirtualBox.

Wheezy and Kali look to need repo certificate updates

@cliffe
Copy link
Owner Author

cliffe commented Apr 19, 2019

Wheezy has been retired from the main debian mirrors.

/etc/apt/sources.list:

deb http://archive.debian.org/debian wheezy main
deb http://archive.debian.org/debian-archive/debian-security wheezy/updates main

/etc/apt/apt.conf.d/99allow_unauth:

APT { Get { AllowUnauthenticated "1"; }; };
Acquire::Check-Valid-Until "false";

For reference:

curl --remote-name --location https://apt.puppetlabs.com/DEB-GPG-KEY-puppet
gpg --keyid-format 0xLONG --with-fingerprint ./DEB-GPG-KEY-puppet
apt-key add DEB-GPG-KEY-puppet

cliffe added a commit that referenced this issue Apr 20, 2019
@mahfuz10
Copy link

After adding two lines in /etc/apt/sources.list, I run sudo apt-get update in ubuntu 18.04. And I found this error:
W: GPG error: http://archive.debian.org/debian-archive/debian-security wheezy/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY


I solved with these commands:
$ sudo apt-get install dirmngr
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8B48AD6246925553
$ sudo apt-get update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants