Install Newer Versions of VirtualBox
Donate
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, thereby undoing 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]
Choose the installation source: either Install from VirtualBox.org Repository or Install VirtualBox from Debian Unstable.
Install from VirtualBox.org Repository
Warning: This procedure will install a foreign software source.
Discouraged: Use the recommended VirtualBox version instead. [1]
Info: The Self Support First Policy applies to this procedure.
The latest Oracle VirtualBox package information can be found here
.
Optional: To find out which version is available from the VirtualBox.org APT Repository, please press expand on the right side.
The user could investigate the following links:
- It is useful to start investigation at the "base link": https://download.virtualbox.org/virtualbox/debian
- Other more specific "hot links" at the time of writing:
1. Adding the VirtualBox.org APT repository.
Choose either: A, B OR C.
A: Use VirtualBox Installer by Kicksecure Developers
2. Learn more about and acquire the VirtualBox Installer by Kicksecure Developers.
3. Run it with the option --oracle-repo.
This will result in the installation of VirtualBox from the Oracle (VirtualBox.org) repository.
bash ./virtualbox-installer --oracle-repo
4. Review the output of the VirtualBox Installer.
5. VirtualBox installation is complete.
6. Move on to step C below.
B: Use extrepo to add VirtualBox.org APT Repository
Install package(s) extrepo following these instructions
1 Platform specific notice.
- Kicksecure: No special notice.
- Kicksecure-Qubes: In Template.
2 Update the package lists and upgrade the system
.
sudo apt update && sudo apt full-upgrade
3 Install the extrepo package(s).
Using apt command line --no-install-recommends option is in most cases optional.
sudo apt install --no-install-recommends extrepo
4 Platform specific notice.
- Kicksecure: No special notice.
- Kicksecure-Qubes: Shut down Template and restart App Qubes based on it as per Qubes Template Modification.
5 Done.
The procedure of installing package(s) extrepo is complete.
Step 2 Open file /etc/extrepo/config.yaml in an editor with root rights.
Kicksecure
See Open File with Root Rights for detailed instructions on why to use sudoedit for better security and how to use it.
Note: Mousepad (or the chosen text editor) must be closed before running the sudoedit command.
sudoedit /etc/extrepo/config.yaml
Kicksecure for Qubes
NOTES:
- When using Kicksecure-Qubes, this needs to be done inside the Template.
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 VirtualBox.org APT repository.
sudo extrepo enable virtualbox
If everything goes well, extrepo will just print some empty lines.
Step 6 Done.
Adding the VirtualBox.org APT repository is complete.
C: Manually add VirtualBox.org 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] https://download.virtualbox.org/virtualbox/debian $(lsb_release -sc) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list
Step B Add Oracle's signing key to the APT keyring.
Step 1 Securely download the key.
curl --tlsv1.3 --remote-name --tlsv1.2 https://www.virtualbox.org/download/oracle_vbox_2016.asc
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.
Warning:
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.
Continue VirtualBox installation depending on the option chosen above.
- A: Do not press expand. Skip to Step C below.
- B and C: Needed. Press expand on the right side.
2. Update and Install VirtualBox.
A. Update the package lists.
sudo apt update
B. Install VirtualBox and Linux Kernel Headers, which are dependencies.
sudo apt install virtualbox-7.1 linux-headers-$(uname -r)
C. Update VirtualBox guest additions.
Note: After upgrading the VirtualBox host version, this might cause issues with guest VMs, such as broken VM size adjustment (full screen), [3] unless the VirtualBox guest additions are also upgraded inside your virtual machine.
As of August 2023, this issue has not been observed. However, if it occurs, you may try Migration to Oracle Style VirtualBox Guest Additions.
D. Done.
Installation of VirtualBox from the VirtualBox.org Repository is complete.
Install VirtualBox from Debian Unstable
Unknown if currently possible. [4]
Discouraged: Use the recommended VirtualBox version instead. [5]
Footnotes[edit]
- ↑
- Security: Because using a foreign software source.
- Usability: Can lead to different VirtualBox host virtualization software versions than the VirtualBox Guest Additions version, which can result in broken guest additions.
- Stability: Not packaged or tested by Debian. Not the same version that most other Kicksecure users are using.
- ↑
The following comments in that file...
# - contrib # - non-free
...could be deleted, but that is completely optional.
- ↑
Problems after upgrading Kicksecure - cannot full size Kicksecure screen
- ↑
As of Debian
buster, this was not possible due to dependencies such asglibcbeing too new. This caused numerous updated dependencies from Debian unstable to be pulled in and mixed with Debian stable, often leading to significant issues, including system instability. - ↑ This method is discouraged because its feasibility is unknown and it can cause system instability.
A secure by default operating system with the latest security research in place.
At
Kicksecure we value freedom and trust, supporting Open Source and Freedom Software
2012-
2025 ENCRYPTED SUPPORT LLC
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!