Install Newer Versions of VirtualBox

From Kicksecure
Jump to navigation Jump to search

This wiki page documents how to install different versions of VirtualBox from sources other than the default repositories, such as Debian unstable or directly from the developers of VirtualBox.

Security Considerations[edit]

If using Kicksecure inside a virtual machine (VM), the virtualization platform is an essential component of a secure Kicksecure system. A vulnerable virtualizer may provide opportunities for attackers to perform a breakout from a virtual machine in order to undo the security by isolation features that Kicksecure provides. The decision to install an alternative virtualizer should not be taken lightly.

The two methods described below to install VirtualBox are safer than downloading, verifying, and installing binaries manually.

See also recommended VirtualBox version.

Newer VirtualBox Version[edit]

Install VirtualBox from Debian Unstable[edit]

Discouraged: Use the recommended VirtualBox version instead.

Unknown if currently possible. [1]

Install from Repository[edit]

Discouraged: Use the recommended VirtualBox version instead.

Warning: this procedure will install a foreign software source.

Info: The Self Support First Policy applies to this procedure.

The latest Oracle VirtualBox package information can be found

Optional: To find out which version is available from the APT Repository, please press expand on the right side.

1. Adding the APT repository.

Choose either: A OR B.

A: Use extrepo to add APT Repository

Step 1

Install package(s) extrepo. Follow steps A to D.

A. Platform specific notice.

B. Update the package lists and upgrade the system The Web Archive Onion Version .

sudo apt update && sudo apt full-upgrade

C. Install the extrepo package(s).

Using apt command line --no-install-recommends The Web Archive Onion Version is in most cases optional.

sudo apt install --no-install-recommends extrepo

D. Platform specific notice.

E. Done.

The procedure of installing package(s) extrepo is complete.

Step 2 Open file /etc/extrepo/config.yaml in an editor with root rights.


This box uses sudoedit for better security.

sudoedit /etc/extrepo/config.yaml

Kicksecure for Qubes


sudoedit /etc/extrepo/config.yaml

  • After applying this change, shutdown the Template.
  • All App Qubes based on the Template need to be restarted if they were already running.
  • This is a general procedure required for Qubes and unspecific to Kicksecure for Qubes.

Others and Alternatives

  • This is just an example. Other tools could achieve the same goal.
  • If this example does not work for you or if you are not using Kicksecure, please refer to this link.

sudoedit /etc/extrepo/config.yaml

Step 3 Paste at the end.

- contrib - non-free


Step 4 Save and exit.

Step 5 Use extrepo to enable the APT repository.

sudo extrepo enable virtualbox

If everything goes well, extrepo will just print some empty lines.

Step 6 Done.

Adding the APT repository has been completed.

B: Manually add APT Repository

Step A Add the Oracle apt sources list.

Make sure to change bookworm to the current name of your stable distribution.

echo "deb [signed-by=/usr/share/keyrings/virtualbox-archive-keyring.asc] $(lsb_release -sc) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list

Step B Add Oracle's signing key to APT keyring.

Step 1 Securely download the key.

curl --tlsv1.3 --remote-name --tlsv1.2

Step 2 Display the key's fingerprint.

gpg --keyid-format long --import --import-options show-only --with-fingerprint oracle_vbox_2016.asc

Step 3 Verify the fingerprint.

The most important check is confirming the key fingerprint exactly matches the output below.

Key fingerprint = B9F8 D658 297A F3EF C18D 5CDF A2F6 83C5 2980 AECF


Do not continue if the fingerprint does not match -- this risks using infected or erroneous files! The whole point of verification is to confirm file integrity.

Step 4 Add the signing key.

sudo cp oracle_vbox_2016.asc /usr/share/keyrings/virtualbox-archive-keyring.asc

Step 5 Done.

The key has been added to the keyring.

2. Update and Install VirtualBox.

A. Update the package lists.

sudo apt update

B. Install VirtualBox and Linux Kernel Headers, which are a dependency.

sudo apt install virtualbox-7.0 linux-headers-$(uname -r)

C. Update VirtualBox guest additions.

Note: After upgrading the VirtualBox host version, this might cause issues with the guest VMs such as broken VM size adjustment (full screen) [3] unless the VirtualBox guest additions are also upgraded inside your virtual machine.

This is currently not the case at time of writing in August 2023. If this happens, then you could try Migration to Oracle Style VirtualBox Guest Additions.

D. Done.

Installation of VirtualBox from Repository has been completed.


  1. Was not possible as of Debian buster. Dependencies such as for package glibc were too new. This meant a host of updated dependencies from Debian unstable wer pulled and mixed with Debian stable, often leading to many issues including system instability.
  2. The following comments in that file...
    # - contrib
    # - non-free

    ...could be deleted but that is completely optional.

  3. Problems after upgrading Kicksecure - cannot full size Kicksecure

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!