Difference between revisions of "Whonix"

From RCS Wiki
Jump to navigation Jump to search
(→‎Known Issues: Link to Kicksecure.)
(Import recent updates from Kicksecure page)
Line 39: Line 39:
 
  sudo apt-get update
 
  sudo apt-get update
  
Note: As of 2021 September 10, there are bugs in the <code>security-misc</code> package in the Whonix <code>bullseye</code> suite, which break ppc64el supportThese bugs were fixed by <code>security-misc</code> version <code>3:22.7-1</code>.  Until the fixes make their way to the <code>bullseye</code> suite, you can get the fixes early by substituting <code>bullseye-developers</code> for <code>bullseye</code> in the <code>derivative.list</code> line above.
+
Upgrade Linux to 5.14 or higher; a bug was fixed between Linux 5.10 and Linux 5.14 that broke ppc64le support in Whonix.  This means using the Debian Bullseye-Backports suite:
  
Upgrade Linux to 5.14 or higher; a bug was fixed between Linux 5.10 and Linux 5.14 that broke ppc64le support in Whonix.  As of 2021 September 10, this means using the Debian Experimental suite ([http://jvgypgbnfyvfopg5msp6nwr2sl2fd6xmnguq35n7rfkw3yungjn2i4yd.onion/ source]) ([https://onion.debian.org/ clearnet]):
+
  <nowiki>echo "deb tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bullseye-backports main" | sudo tee /etc/apt/sources.list.d/backports.list</nowiki>
 
 
  <nowiki>echo "deb tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian experimental main" | sudo tee /etc/apt/sources.list.d/experimental.list</nowiki>
 
 
  sudo apt-get update
 
  sudo apt-get update
  sudo apt-get -t experimental install linux-image-powerpc64le
+
  sudo apt-get -t bullseye-backports install linux-image-powerpc64le
  
== Whonix-Gateway ==
+
Then, run one of the following, depending on whether you want Whonix to use XFCE or CLI-only, and whether you are installing Whonix-Gateway or Whonix-Workstation:
  
Run one of the following, depending on whether you want the Whonix-Gateway to use XFCE or CLI-only:
+
sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-xfce
  
  sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-xfce
+
  sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-xfce
  
 
  sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-cli
 
  sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-cli
 +
 +
sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-cli
  
 
If you get a package conflict error that mentions <code>console-common</code>, run the following and then try again:
 
If you get a package conflict error that mentions <code>console-common</code>, run the following and then try again:
Line 59: Line 59:
 
  sudo apt-get install --no-install-recommends console-common
 
  sudo apt-get install --no-install-recommends console-common
  
If you get prompted with questions during package installation, you can choose the defaults.
+
If you get prompted about choosing the default display manager during package installation, choose <code>gdm3</code> ([http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Stable_Release#Whonix_™_16.0.2.7 source]) ([https://www.whonix.org/wiki/Stable_Release#Whonix_™_16.0.2.7 clearnet]).
 +
 
 +
If you get prompted with other questions during package installation, you can choose the defaults.
  
 
The Whonix packages will install their own <code>sources.list</code> data in <code>/etc/apt/sources.list.d/debian.list</code>, which means you should delete the <code>sources.list</code> that Debian came with (in order to avoid warnings from <code>apt-get</code> about duplicated repos):
 
The Whonix packages will install their own <code>sources.list</code> data in <code>/etc/apt/sources.list.d/debian.list</code>, which means you should delete the <code>sources.list</code> that Debian came with (in order to avoid warnings from <code>apt-get</code> about duplicated repos):
  
 
  sudo rm /etc/apt/sources.list
 
  sudo rm /etc/apt/sources.list
 +
sudo rm /etc/apt/sources.list.d/backports.list
  
Shut off the VM.
+
Run the following to work around a bug that breaks subsequent package updates ([http://forums.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/t/dist-base-files-postinst-aborted-on-ppc64el/13381/2 source]) ([https://forums.whonix.org/t/dist-base-files-postinst-aborted-on-ppc64el/13381/2 clearnet]):
  
Set the VM's NIC to use the <code>Whonix-External</code> Network source.
+
sudo mkdir -p /etc/dist-base-files.d/
 +
echo "set +e" | sudo tee /etc/dist-base-files.d/50_user.conf
  
Add a 2nd NIC to the VM, and set it to use the <code>Whonix-Internal</code> Network source.
+
Run the following to work around a bug in the <code>security-misc</code> package that breaks non-x86 architectures ([https://github.com/torvalds/linux/blob/master/arch/powerpc/Kconfig source], grep for <code>config ARCH_MMAP_RND_BITS_MAX</code> and <code>config COMPAT</code>):
  
Launch the VM again; Whonix-Gateway should be running.
+
sudo sed -i 's/vm.mmap_rnd_bits=32/vm.mmap_rnd_bits=29/' /etc/sysctl.d/30_security-misc.conf
 +
sudo sed -i 's/vm.mmap_rnd_compat_bits=16//' /etc/sysctl.d/30_security-misc.conf
  
If you get errors about the Tor service failing to start, this is probably an AppArmor issue. You can fix it by running the following:
+
Shut off the VM.
 
 
sudo touch /etc/apparmor.d/local/system_tor.anondist
 
  
Restart the VM again and Tor should work.
+
If you're installing Whonix-Gateway, set the VM's NIC to use the <code>Whonix-External</code> Network source.  Then add a 2nd NIC to the VM, and set it to use the <code>Whonix-Internal</code> Network source.
  
== Whonix-Workstation ==
+
If you're installing Whonix-Workstation, set the VM's NIC to use the <code>Whonix-Internal</code> Network source.
  
Run one of the following, depending on whether you want the Whonix-Workstation to use XFCE or CLI-only:
+
Launch the VM again; Whonix should be running.
  
sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-xfce
+
If you get errors in Whonix-Gateway about the Tor service failing to start, this is probably an AppArmor issue.  You can fix it by running the following:
  
  sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-cli
+
  sudo touch /etc/apparmor.d/local/system_tor.anondist
 
 
If you get a package conflict error that mentions <code>console-common</code>, run the following and then try again:
 
 
 
sudo apt-get install --no-install-recommends console-common
 
 
 
If you get prompted with questions during package installation, you can choose the defaults.
 
 
 
The Whonix packages will install their own <code>sources.list</code> data in <code>/etc/apt/sources.list.d/debian.list</code>, which means you should delete the <code>sources.list</code> that Debian came with (in order to avoid warnings from <code>apt-get</code> about duplicated repos):
 
 
 
sudo rm /etc/apt/sources.list
 
 
 
Shut off the VM.
 
 
 
Set the VM's NIC to use the <code>Whonix-Internal</code> Network source.
 
  
Launch the VM again; Whonix-Workstation should be running.
+
Restart Whonix-Gateway again and Tor should work.
  
 
== Known Issues ==
 
== Known Issues ==

Revision as of 02:42, 27 March 2022

Whonix (clearnet link) can be installed on POWER using KVM. These instructions were tested with Whonix 16.

Both Whonix-Gateway and Whonix-Workstation

Download Whonix from the Whonix KVM download page (clearnet link).

Extract it:

tar -xvf Whonix*.libvirt.xz

Install the Whonix virtual networks:

sudo virsh -c qemu:///system net-define Whonix_external*.xml
sudo virsh -c qemu:///system net-define Whonix_internal*.xml
sudo virsh -c qemu:///system net-autostart Whonix-External
sudo virsh -c qemu:///system net-start Whonix-External
sudo virsh -c qemu:///system net-autostart Whonix-Internal
sudo virsh -c qemu:///system net-start Whonix-Internal

Then, create two Debian Bullseye ppc64el VM's. When installing Debian, do not create a separate root password, name the user user, and for desktop environment either pick XFCE or do not install one. Launch a shell in each VM, and follow the below instructions for each VM.

Import the Whonix/Kicksecure signing key (source) (clearnet):

sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install --no-install-recommends curl gpg gpg-agent
curl --tlsv1.3 --proto =https --max-time 180 --output ~/patrick.asc https://www.whonix.org/patrick.asc
sudo cp ~/patrick.asc /etc/apt/trusted.gpg.d/derivative.asc

Initialize the console group (source) (clearnet):

sudo addgroup --system console
sudo adduser user console

Add the Whonix/Kicksecure package repository (source) (clearnet):

sudo apt-get install apt-transport-tor
echo "deb tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion bullseye main" | sudo tee /etc/apt/sources.list.d/derivative.list
sudo apt-get update

Upgrade Linux to 5.14 or higher; a bug was fixed between Linux 5.10 and Linux 5.14 that broke ppc64le support in Whonix. This means using the Debian Bullseye-Backports suite:

echo "deb tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bullseye-backports main" | sudo tee /etc/apt/sources.list.d/backports.list
sudo apt-get update
sudo apt-get -t bullseye-backports install linux-image-powerpc64le

Then, run one of the following, depending on whether you want Whonix to use XFCE or CLI-only, and whether you are installing Whonix-Gateway or Whonix-Workstation:

sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-xfce
sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-xfce
sudo apt-get install --no-install-recommends non-qubes-whonix-gateway-cli
sudo apt-get install --no-install-recommends non-qubes-whonix-workstation-cli

If you get a package conflict error that mentions console-common, run the following and then try again:

sudo apt-get install --no-install-recommends console-common

If you get prompted about choosing the default display manager during package installation, choose gdm3 (source) (clearnet).

If you get prompted with other questions during package installation, you can choose the defaults.

The Whonix packages will install their own sources.list data in /etc/apt/sources.list.d/debian.list, which means you should delete the sources.list that Debian came with (in order to avoid warnings from apt-get about duplicated repos):

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

Run the following to work around a bug that breaks subsequent package updates (source) (clearnet):

sudo mkdir -p /etc/dist-base-files.d/
echo "set +e" | sudo tee /etc/dist-base-files.d/50_user.conf

Run the following to work around a bug in the security-misc package that breaks non-x86 architectures (source, grep for config ARCH_MMAP_RND_BITS_MAX and config COMPAT):

sudo sed -i 's/vm.mmap_rnd_bits=32/vm.mmap_rnd_bits=29/' /etc/sysctl.d/30_security-misc.conf
sudo sed -i 's/vm.mmap_rnd_compat_bits=16//' /etc/sysctl.d/30_security-misc.conf

Shut off the VM.

If you're installing Whonix-Gateway, set the VM's NIC to use the Whonix-External Network source. Then add a 2nd NIC to the VM, and set it to use the Whonix-Internal Network source.

If you're installing Whonix-Workstation, set the VM's NIC to use the Whonix-Internal Network source.

Launch the VM again; Whonix should be running.

If you get errors in Whonix-Gateway about the Tor service failing to start, this is probably an AppArmor issue. You can fix it by running the following:

sudo touch /etc/apparmor.d/local/system_tor.anondist

Restart Whonix-Gateway again and Tor should work.

Known Issues

See Kicksecure known issues.

No Whonix-specific known issues.