Actions

Kicksecure ™ for VirtualBox with XFCE

From Whonix

< Kicksecure



Kicksecure ™: A Security-hardened, Non-anonymous Linux Distribution.

Ambox warning pn.svg.png Testers only!

warning Note:

  • Do not use these instructions inside Whonix ™ [archive].
  • These instructions are only for use outside of Whonix; for example, browsing the internet non-anonymously.

1. Download Kicksecure ™ XFCE for Windows Windows logo - 2012.svg.png, MacOS Rsz osx.png and Linux Tux.png FREE


Ambox warning pn.svg.png By downloading, you acknowledge that you have read, understood and agreed to our Terms of Service and License Agreement.

Version: 15.0.1.3.4

Kicksecure ™
 		Download Security
without Verification 		Download Security
with Verification
Https long.png

Download

Medium High [1]
Button sig.png

OpenPGP Signature ( sha512 , sig )

- -
Crypto key.png Verify images using this Signing Key -


Verify the Kicksecure ™ Images Whonix ™ virtual machine images are cryptographically signed by Whonix developer Patrick Schleizer using OpenPGP. [2]

notice Digital signatures can increase security but this requires knowledge. Learn more about digital software signature verification.

If you know how to use an OpenPGP key, download the Whonix ™ Signing Key and the Whonix ™ signatures straight away.

Otherwise, use the following instructions:

Download Kicksecure ™ XFCE

2. Install VirtualBox Virtualbox logo.png

  • Linux Tux.png: please press expand on the right side.

Hosts using a non-Debian OS:

Install VirtualBox as per the normal mechanism for your Linux distribution.

Debian hosts:

These instructions are for Debian buster, which is recommended. Other Debian releases might work, but this is untested. In that case, replace buster with the actual codename your release.

Note: this applies to Kicksecure ™ 15. Later Kicksecure ™ versions may use a codename different to buster.

Package virtualbox [archive] should be installed from Debian unstable (codename: sid). This is non-ideal but required since VirtualBox in unavailable in Debian buster / buster-backports at the time of writing. It has risks such as bricking the apt package manager. Therefore users should make sure to have their backup and restore process functional. Alternativly you could install from Oracle Repository but this comes with different risks.

1. On the host.

Open a terminal.

2. Add Debian stable codename buster to the apt-conf default-release. 

sudo su -c "echo -e 'APT::Default-Release buster;' > /etc/apt/apt.conf.d/70defaultrelease"

3. Add Debian sid to Debian apt sources.

[3] 

sudo su -c "echo -e 'deb http://http.debian.net/debian sid main contrib non-free' > /etc/apt/sources.list.d/unstable.list"

4. Update the package lists. 

sudo apt-get update

5. Install the selected software. 

sudo apt-get install virtualbox/sid linux-headers-$(uname -r)

The procedure is now complete.

6. Undo.

On occasion it is necessary to undo this configuration, for example when upgrading from Debian buster to bullseye. [4] To proceed, run. 

sudo rm /etc/apt/sources.list.d/unstable.list

3. Import Kicksecure ™ into VirtualBox Virtualbox logo.png

For Kicksecure ™ VirtualBox import instructions, please press on expand on the right.

Start VirtualBox
Open The virtualbox1.png

Click on File then choose Import Appliance...
Select Import Applience2.png

Navigate and select Kicksecure ™ image and press next
Select whonix image and press next3.png

Do NOT change anything! Just click on Import
Press import4.png

Then press Agree
Press agree5.png

Wait until Whonix-Gateway.ova has been imported
Wait for importing6.png

Now start Kicksecure ™.
Start both of them8.png

Miscellaneous

There are also Video Tutorials.

If you still need help, please check the Support page.

For command line import instructions, see footnote. [5]

4. Start Kicksecure ™

Starting Kicksecure ™ is simple.

Start VirtualBox → Double-click the Kicksecure ™.

5. VirtualBox Screen Resolution Bug

VirtualBox Screen Resolution Bug.

If the display presents like the image on the right-hand side, then you are affected by a screen resolution bug which only occurs in VirtualBox.

To correct the resolution, first apply the General VirtualBox Troubleshooting Steps.

If the issue still persists, to correct resolution, try the following workarounds.

VirtualBox Virtual Screen Menu Workaround

  1. Power off the VM.
  2. Restart the VM.
  3. Maximize the VM window after start of the VM as soon as possible.
  4. VirtualBox VM Window → View → Virtual Screen 1 → Choose any, resize to another resolution
  5. VirtualBox VM Window → View → Auto-resize Guest Display
Normal presentation.

Desktop Resolution Settings Workaround

If the method above did not work, another option is the following. Inside the virtual machine:

XFCE Start Menu → Settings → Display → Resolution: → Choose a higher resolution resolution → Apply

VirtualBox VMSVGA Graphics Controller Setting Workaround

If it still does not work, a final option is the following.

Inside the virtual machine [6]:

On the host:

  1. Power off the VM.
  2. VirtualBox → click a VM → Settings → Display → Graphics Controller → VMSVGA → OK (This is already the case in newer Whonix ™ versions.)
  3. VirtualBox → click a VM → Settings → Display → Graphics Controller → increase slider for Video Memory to 128 → OK (This is already the case in newer Whonix ™ versions.)
  4. Restart the VM.
  5. Maximize the VM window after start of the VM as soon as possible.
  6. If necessary, try again one of above workarounds.

VirtualBox Guest Additions Bugs Reporting

Occasionally screen resolution problems might still persist, see: VirtualBox Guest Additions Bugs Reporting.

Whonix / Kicksecure default admin password is: changeme default username: user
default password: changeme

Footnotes and Experimental Spectre / Meltdown Defenses

Please press on expand on the right.

Kicksecure Stable Version | Kicksecure Testers Only Version

Testers only! For more information please press on expand on the right.

These experimental [archive] Spectre/Meltdown defenses are related to issues outlined in Firmware Security and Updates. Due to the huge performance penalty and unclear security benefits of applying these changes, it may not be worth the effort. The reason is VirtualBox is still likely vulnerable, even after:

  1. A host microcode upgrade.
  2. A host kernel upgrade.
  3. A VM kernel upgrade.
  4. A "not vulnerable" result from spectre-meltdown-checker run on the host.
  5. Installation of the latest VirtualBox version. [7]
  6. All Spectre/Meltdown-related VirtualBox settings are tuned for better security as documented below.

To learn more, see: VirtualBox 5.2.18 vulnerable to spectre/meltdown despite microcode being installed [archive] and the associated VirtualBox forum discussion [archive]. [8] Users must patiently wait for VirtualBox developers to fix this bug.

On the host. [9] [10] [11] [12] [13] [14] [15]

VBoxManage modifyvm "Whonix-Gateway" --ibpb-on-vm-entry o VBoxManage modifyvm "Whonix-Gateway" --ibpb-on-vm-exit on VBoxManage modifyvm "Whonix-Gateway" --l1d-flush-on-vm-entry on VBoxManage modifyvm "Whonix-Gateway" --l1d-flush-on-sched on VBoxManage modifyvm "Whonix-Gateway" --spec-ctrl on VBoxManage modifyvm "Whonix-Gateway" --nestedpaging off VBoxManage modifyvm "Whonix-Gateway" --mds-clear-on-vm-entry on VBoxManage modifyvm "Whonix-Gateway" --mds-clear-on-sched on

VBoxManage modifyvm "Whonix-Workstation" --ibpb-on-vm-entry on VBoxManage modifyvm "Whonix-Workstation" --ibpb-on-vm-exit on VBoxManage modifyvm "Whonix-Workstation" --l1d-flush-on-vm-entry on VBoxManage modifyvm "Whonix-Workstation" --l1d-flush-on-sched on VBoxManage modifyvm "Whonix-Workstation" --spec-ctrl on VBoxManage modifyvm "Whonix-Workstation" --nestedpaging off VBoxManage modifyvm "Whonix-Workstation" --mds-clear-on-vm-entry on VBoxManage modifyvm "Whonix-Workstation" --mds-clear-on-sched on

Info These steps must be repeated for every Whonix or non-Whonix VirtualBox VM, including multiple and custom VMs.

The above instructions only apply to the default VM names Whonix-Gateway ™ and Whonix-Workstation ™. Therefore, if Multiple Whonix-Workstation ™s and/or Multiple Whonix-Gateway ™s are configured, then repeat these instructions using the relevant name/s.


Footnotes[edit]

  1. ↑ It does not matter if the bulk download is done over an insecure channel if OpenPGP verification is used at the end.
  2. ↑ OpenPGP is a standard for data encryption that provides cryptographic privacy and authentication through the use of keys owned by its users.
  3. ↑ Or alternatively use the .onion mirror. 
    sudo su -c "echo -e 'deb tor+http://vwakviie2ienjx6t.onion/debian sid main contrib non-free' > /etc/apt/sources.list.d/unstable.list"

  4. ↑ Most often this step applies before attempting major Kicksecure ™ upgrades; upgrade instructions are also made available at that time (see stay tuned).
  5. ↑ For Linux: Read License Agreement. 
    vboxmanage import Kicksecure-XFCE-15.0.0.0.6.ova --vsys 0 --eula show --vsys 1 --eula show

    vboxmanage import Kicksecure-XFCE-15.0.0.0.6.ova --vsys 0 --eula accept --vsys 1 --eula accept

  6. ↑ VirtualBox VMSVGA graphics controller is based on the VMware graphics controller.
  7. ↑ VirtualBox version 5.2.18 or above is required since only that version comes with Spectre/Meltdown defenses. See https://forums.whonix.org/t/whonix-vulerable-due-to-missing-processor-microcode-packages/5739/22 [archive].
  8. ↑ Also see the following Whonix forum discussion: Whonix vulerable due to missing processor microcode packages? spectre / meltdown / retpoline / L1 Terminal Fault (L1TF) [archive]
  9. ↑

    --ibpb-on-vm-[enter|exit] on|off: Enables flushing of the indirect branch prediction buffers on every VM enter or exit respectively. This could be enabled by users overly worried about possible spectre attacks by the VM. Please note that these options may have sever impact on performance.
    https://www.virtualbox.org/manual/ch08.html [archive]

    There is a mistake in the VirtualBox manual stating enter which does not work. It is actually entry.

  10. ↑ https://www.virtualbox.org/manual/ch08.html [archive]

    --l1d-flush-on-vm-enter on|off: Enables flushing of the level 1 data cache on VM enter. See Section 13.4.1, “CVE-2018-3646”.

  11. ↑

    --l1d-flush-on-sched on|off: Enables flushing of the level 1 data cache on scheduling EMT for guest execution. See Section 13.4.1, “CVE-2018-3646 [archive]”.
    https://www.virtualbox.org/manual/ch08.html [archive]

  12. ↑ https://www.virtualbox.org/manual/ch13.html#sec-rec-cve-2018-3646 [archive]

    For users not concerned by this security issue, the default mitigation can be disabled using

    VBoxManage modifyvm name --l1d-flush-on-sched off

    Since we want to enable the security feature we set --l1d-flush-on-sched on.

  13. ↑

    --spec-ctrl on|off: This setting enables/disables exposing speculation control interfaces to the guest, provided they are available on the host. Depending on the host CPU and workload, enabling speculation control may significantly reduce performance.
    https://www.virtualbox.org/manual/ch08.html [archive]

  14. ↑ According to this VirtualBox ticket [archive] --spec-ctrl should be set to on.
  15. ↑

    --nestedpaging on|off: If hardware virtualization is enabled, this additional setting enables or disables the use of the nested paging feature in the processor of your host system; see Section 10.7, “Nested paging and VPIDs” and Section 13.4.1, “CVE-2018-3646”.

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier

Follow: Twitter.png Facebook.png 1280px-Gab text logo.svg.png Iconfinder news 18421.png Rss.png Matrix logo.svg.png 1024px-Telegram 2019 Logo.svg.png Discourse logo.svg Reddit.jpg Diaspora.png Gnusocial.png Mewe.png 500px-Tumblr Wordmark.svg.png Iconfinder youtube 317714.png 200px-Minds logo.svg.png 200px-Mastodon Logotype (Simple).svg.png 200px-LinkedIn Logo 2013.svg.png

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate whonix.png United Federation of Planets 1000px.png

Share: Twitter | Facebook

https link onion link

This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation. Policy of Whonix Website and Whonix Chat applies.

Copyright (C) 2012 - 2020 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)

Whonix ™ is a derivative of and not affiliated with Debian [archive]. Debian is a registered trademark [archive] owned by Software in the Public Interest, Inc [archive].

Whonix ™ is produced independently from the Tor® [archive] anonymity software and carries no guarantee from The Tor Project [archive] about quality, suitability or anything else.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. Whonix ™ is provided by ENCRYPTED SUPPORT LP. See Imprint, Contact.

Retrieved from "https://www.whonix.org/w/index.php?title=Kicksecure/XFCE&oldid=57983"