Qubes OS

Template:Redirect Template:Short description Template:Use mdy dates Template:Infobox OS

Qubes OS is a security-focused desktop operating system that aims to provide security through isolation.^[1] Virtualization is performed by Xen, and user environments can be based on Fedora, Debian, Whonix, and Microsoft Windows, among other operating systems.^[2]^[3]

Systems like Qubes are referred to in academia as Converged Multi-Level Secure (MLS) Systems.^[4] Other proposals of similar systems have surfaced^[5]^[6] and SecureView^[7] is a commercial competitor. Qubes OS is however the only system of the kind actively being developed under a FOSS license.

Security goals

File:Qubes security domains.png

Security domains scheme

Qubes implements a Security by Isolation approach.^[8] The assumption is that there can be no perfect, bug-free desktop environment: such an environment counts millions of lines of code and billions of software/hardware interactions. One critical bug in any of these interactions may be enough for malicious software to take control over a machine.^[9]^[10]

To secure a desktop a Qubes user takes care to isolate various environments, so that if one of the components gets compromised, the malicious software would get access to only the data inside that environment.^[11]

In Qubes, the isolation is provided in two dimensions: hardware controllers can be isolated into functional domains (e.g. network domains, USB controller domains), whereas the user's digital life is decided in domains with different levels of trust. For instance: work domain (most trusted), shopping domain, random domain (less trusted).^[12] Each of those domains is run in a separate virtual machine.

In a (slightly controversial) design decision, Qubes virtual machines, by default, have passwordless root access (e.g. passwordless sudo).^[13] UEFI Secure Boot is not supported out of the box, but this is not considered a major security issue.^[14] Qubes is not a multiuser system.^[15]

Installation and requirements

Qubes was not intended to be run as part of a multi-boot system because if an attacker were to take control of one of the other operating systems then they'd likely be able to compromise Qubes (e.g. before Qubes boots).^[16] However, it is still possible to use Qubes as part of a multi-boot system and even to use grub2 as the boot loader/boot manager.^[16] A standard Qubes installation takes all space on the storage medium (e.g. hard drive, USB flash drive) to which it is installed (not just all available free space) and it uses LUKS/dm-crypt full disk encryption.^[14] It is possible (although not trivial) to customize much of the Qubes OS installation but for security reasons, this is discouraged for users that are not intimately familiar with Qubes. Qubes 4.x needs at least 32 GiB of disk space and 4 GB of RAM.^[17] However, in practice it typically needs upwards of 6-8 GB of RAM since although it is possible to run it with only 4 GB of RAM, users will likely be limited to running no more than about three Qubes at a time.^[14]

Since 2013, Qubes has not had support for 32-bit x86 architectures and now requires a 64-bit processor.^[14] Qubes uses Intel VT-d/AMD's AMD-Vi, which is only available on 64-bit architectures, to isolate devices and drivers. The 64-bit architecture also provides a little more protection against some classes of attacks.^[14] Since Qubes 4.x, Qubes requires either an Intel processor with support for VT-x with EPT and Intel VT-d virtualization technology or an AMD processor with support for AMD-V with RVI (SLAT) and AMD-Vi (aka AMD IOMMU) virtualization technology.^[14] Qubes targets the desktop market. This market is dominated by laptops running Intel processors and chipsets and consequently, Qubes developers focus on Intel's VT-x/VT-d technologies.^[18] This is not a major issue for AMD processors since AMD IOMMU is functionally identical to Intel's VT-d.^[18]

User experience

The users interact with Qubes OS very much the same way they would interact with a regular desktop operating system. But there are some key differences:

Each security domain (Qube) is identified by a different colored window border
Opening an application for the first time in that session for a particular security domain will take around 30s (depending on hardware)
Copying files^[19] and clipboard^[20] is a little different since domains don't share clipboard or filesystem
The user can create and manage security compartments

System architecture overview

Xen hypervisor and administrative domain (Dom0)

The hypervisor provides isolation between different virtual machines. The administrative domain, also referred to as Dom0 (a term inherited from Xen), has direct access to all the hardware by default. Dom0 hosts the GUI domain and controls the graphics device, as well as input devices, such as the keyboard and mouse. The GUI domain runs the X server, which displays the user desktop, and the window manager, which allows the user to start and stop the applications and manipulate their windows.

Integration of the different virtual machines is provided by the Application Viewer, which provides an illusion for the user that applications execute natively on the desktop, while in fact they are hosted (and isolated) in different virtual machines. Qubes integrates all these virtual machines onto one common desktop environment.

Because Dom0 is security-sensitive, it is isolated from the network. It tends to have as little interface and communication with other domains as possible in order to minimize the possibility of an attack originating from an infected virtual machine.^[21]^[22]

The Dom0 domain manages the virtual disks of the other VMs, which are actually stored as files on the dom0 filesystem(s). Disk space is saved by virtue of various virtual machines (VM) sharing the same root file system in a read-only mode. Separate disk storage is only used for userʼs directory and per-VM settings. This allows software installation and updates to be centralized. It is also possible to install software only on a specific VM, by installing it as the non-root user, or by installing it in the non-standard, Qubes-specific /rw hierarchy.

Network domain

The network mechanism is the most exposed to security attacks. To circumvent this it is isolated in a separate, unprivileged virtual machine, called the Network Domain.

An additional firewall virtual machine is used to house the Linux-kernel-based firewall, so that even if the network domain is compromised due to a device driver bug, the firewall is still isolated and protected (as it is running in a separate Linux kernel in a separate VM).^[23]

Application Virtual Machines (AppVM)

AppVMs are the virtual machines used for hosting user applications, such as a web browser, an e-mail client or a text editor. For security purposes, these applications can be grouped in different domains, such as "personal", "work", "shopping", "bank", etc. The security domains are implemented as separate, Virtual Machines (VMs), thus being isolated from each other as if they were executing on different machines.

Some documents or applications can be run in disposable VMs through an action available in the file manager. The mechanism follows the idea of sandboxes: after viewing the document or application, then the whole Disposable VM will be destroyed.^[24]

Each security domain is labelled by a color, and each window is marked by the color of the domain it belongs to. So it is always clearly visible to which domain a given window belongs.

Template:Clear

Reception

Security and privacy experts such as Edward Snowden, Daniel J. Bernstein, and Christopher Soghoian have publicly praised the project.^[25]

Jesse Smith wrote review of Qubes OS 3.1 for DistroWatch Weekly:^[26] Template:Quote Kyle Rankin from Linux Journal reviewed Qubes OS in 2016:^[27] Template:Quote In 2014, Qubes was selected as a finalist of Access Innovation Prize 2014 for Endpoint Security, run by the international human rights organization Access Now.^[28]

References

1 }}

     | references-column-width 
     | references-column-count references-column-count-{{#if:1|30em}} }}
   | {{#if: 
     | references-column-width }} }}" style="{{#if: 30em
   | {{#iferror: {{#ifexpr: 30em > 1 }}
     | Template:Column-width
     | Template:Column-count }}
   | {{#if: 
     | Template:Column-width }} }} list-style-type: {{#switch: 
   | upper-alpha
   | upper-roman
   | lower-alpha
   | lower-greek
   | lower-roman = {{{group}}}
   | #default = decimal}};">

External links

Template:Commons category

Template:RedHatFedora-distro Template:Linux-distro Template:Virtualization products Template:FLOSS

[1] Template:Cite web

[2] Template:Cite web

[3] Template:Cite web

[4] Template:Cite conference

[5] Template:Cite conference

[6] Template:Cite journal

[7] Template:Cite web

[8] Template:Cite web

[9] Template:Cite web

[10] Template:Cite web

[11] Template:Cite web

[12] Template:Cite web

[QubesPasswordlessRootAccessInVMs-13] Passwordless Root Access in VMs

[QubesFAQ-14] 14.0 ^14.1 ^14.2 ^14.3 ^14.4 ^14.5 Qubes faq

[15] Template:Cite web

[QubesMultiboot-16] 16.0 ^16.1 Multibooting Qubes

[QubesSystemRequirements-17] Qubes system requirements

[WhyIntelVT-d-18] 18.0 ^18.1 Why Intel VT-d ?

[19] Template:Cite web

[20] Template:Cite web

[21] Template:Cite web

[22] Template:Cite web

[23] Template:Cite web

[24] Template:Cite web

[25] Template:Cite web

[26] DistroWatch Weekly, Issue 656, 11 April 2016

[27] Secure Desktops with Qubes: Introduction | Linux Journal

[28] Template:Cite web

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

[26]

[27]

[28]