Qubes
(Redirected from Qubes-Whonix)
Overview[edit]
Qubes-Whonix ™ is the seamless combination of Qubes OS and Whonix ™ for advanced security and anonymity.
In this configuration Whonix ™ runs on top of Qubes inside virtual machines (VMs), just like any other OS on the same platform (Fedora, Debian, Arch Linux and so on).
The Qubes bare-metal hypervisor is based on Xen and Fedora. Via hardware support like VT-x, VT-d and TXT, Qubes has implemented a strict security-by-isolation architecture. Hardware controllers and multiple user domains (qubes) are isolated using separate VMs that are explicitly assigned different levels of trust, yet the desktop experience is user-friendly and well-integrated.
Whonix ™ is based on Debian and Tor. The design provides a two-VM, split security architecture: an isolated Whonix-Gateway ™ (ProxyVM; sys-whonix) for complete routing of traffic over Tor; and Whonix-Workstation ™ (AppVM; anon-whonix) for all desktop applications, which serves as a tailored OS environment for Tor-based privacy/anonymity.
To use Qubes-Whonix ™, Qubes must first be installed as a hypervisor on the physical host computer, followed by installation of the two separate Whonix ™ TemplateVMs -- whonix-gw-14 and whonix-ws-14 -- on top of Qubes. From this point, the Whonix ™ TemplateVMs can be used for customization and creation of multiple Whonix-Gateway ™ ProxyVMs and Whonix-Workstation ™ AppVMs, enabling enhanced compartmentalization of user activities for better privacy. [1]
For a more in-depth consideration of Qubes-Whonix ™ advantages, see: Why use Qubes over other Virtualizers?
Guides[edit]
For major TemplateVM and AppVM operations, refer to the following guides:
- Install Qubes-Whonix ™
- Update Qubes-Whonix ™
- Update Tor Browser
- Reinstall Qubes-Whonix ™ TemplateVMs
- Uninstall Qubes-Whonix ™ TemplateVMs
- Install and update software in dom0
- Backup, restore and migrate VMs
For improved security and anonymity after installing Qubes-Whonix ™, refer to the following guides:
- Post-installation security advice
- AppArmor
- How to use Tor Bridges
- Multiple Whonix-Workstation ™
- DisposableVMs
- Qubes-Whonix ™ Security
Advanced:
Support[edit]
Before seeking personal support, please first search for the issue and a possible, documented solution. In many cases the issue can be solved by inspecting the phabricator issues tracker, reading Whonix ™ guides/documentation, conducting web searches, and examining past support requests.
If a search yields no results, support requests should be directed to the most appropriate forum:
- Qubes: Qubes Support
- Qubes-Whonix ™-specific: Whonix ™ Qubes Forum
- Whonix ™, Debian and Tor: Whonix ™ Support
Footnotes[edit]
- ↑ The only limitation on the number of possible VMs is available disk space.
No user support in comments. See Support.
Comments will be deleted after some time. Specifically after comments have been addressed in form of wiki enhancements. See Wiki Comments Policy.
Did you know that Whonix could provide protection against backdoors? See Verifiable Builds. Help is wanted and welcomed.
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.
Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee of the Open Invention Network. 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. Debian is a registered trademark owned by Software in the Public Interest, Inc.
Whonix ™ is produced independently from the Tor® anonymity software and carries no guarantee from The Tor Project 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.
Enable comment auto-refresher