Software:Qubes OS

From HandWiki
Short description: Security-focused Linux-based operating system
Qubes OS
Qubes OS Logo.svg
Qubes OS ws 4-1-2.png
Qubes OS 4.1.2 with its default Xfce DE running Fedora 37, Debian 11 and Whonix 16 virtualizations.
DeveloperThe Qubes OS Project
OS familyLinux (Unix-like)
Working stateCurrent
Source modelOpen source with proprietary blobs,[1][2]
Initial releaseSeptember 3, 2012; 11 years ago (2012-09-03)[3]
|Final preview|Latest preview}}4.2.0-rc5[4] / November 26, 2023; 7 months ago (2023-11-26)
Available inMultilingual
Update methodDNF (PackageKit)
Package managerRPM Package Manager
Platformsx86-64
Kernel typeMicrokernel (Xen Hypervisor running minimal Linux-based OSes and others)
UserlandGNU[note 1]
Default user interfaceXfce
LicenseFree software licenses
(mainly GPL v2[5])
Official websitequbes-os.org

Qubes OS is a security-focused desktop operating system that aims to provide security through isolation.[6] Isolation is provided through the use of virtualization technology. This allows the segmentation of applications into secure virtual machines called qubes. Virtualization services in Qubes OS are provided by the Xen hypervisor.

The runtimes of individual qubes are generally based on a unique system of underlying operating system templates. Templates provide a single, immutable root file system which can be shared by multiple qubes. This approach has two major benefits. First, updates to a given template are automatically "inherited" by all qubes based on it. Second, shared templates can dramatically reduce storage requirements compared to separate VMs with a full operating install per secure domain.

The base installation of Qubes OS provides a number of officially supported templates based on the Fedora and Debian Linux distributions. Alternative community-supported templates include Whonix, Ubuntu, Arch Linux, CentOS, or Gentoo.[7] Users may also create their own templates.

Operating Systems like Qubes OS are referred to in academia as Converged Multi-Level Secure (MLS) Systems.[8] Other proposals of similar systems have surfaced[9][10] and SecureView and VMware vSphere are commercial competitors.[citation needed]

Security goals

Security domains scheme

Qubes implements a Security by Isolation approach.[11] 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 of a machine.[12][13]

To secure a desktop using Qubes OS, the 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.[14]

In Qubes OS, 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 divided into security domains with different levels of trust.

For instance: work domain (most trusted), shopping domain, random domain (less trusted).[15] Each of these domains is run in a separate qube.

The qubes have passwordless root access (e.g. passwordless sudo) by default.[16] UEFI Secure Boot is not supported out of the box, but this is not considered a major security issue.[17] Qubes is not a multiuser system.[18]

Installation and System Requirements

As a desktop-focused operating system, Qubes OS targets personal computer hardware. This market is dominated by laptops running Intel and AMD processors and chipsets.

The base system requirements for Qubes OS are:

  • 64-bit Intel or AMD processor with virtualization extensions (Since 2013, Qubes OS only supports 64-bit processors.[17] In addition, since release 4.x, Qubes OS requires either an Intel processor with support for VT-x with EPT and Intel VT-d or an AMD processor with support for AMD-V with RVI (SLAT) and AMD-Vi (aka AMD IOMMU). [19] This is not a major issue for AMD processors since AMD IOMMU is functionally identical to Intel's VT-d.[19])
  • 6 GB RAM minimum
  • 32 GB disk space minimum[20]

User experience

Users interact with Qubes OS in much the same manner that they interact with any standard graphical desktop operating systems with some key differences:

  • The creation of qubes (security domains) offers the means to create discrete, lean, secure application spaces by linking them to a complete root filesystem using shared templates.
  • Applications launched from their respective qubes are distinguished by a unique colored window border.
  • Opening an application for the first time in a given qube may incur a modest delay depending on system hardware.
  • Sharing files[21] and clipboard paste buffers[22] utilize a special mechanism, as qubes do not share a common clipboard or file system.
  • Users can create and manage as many qubes as desired to suit their specific requirements.

System architecture overview

Xen hypervisor and domains

The Xen hypervisor provides strong isolation between its hosted virtual machines, called domains in Xen terminology.

The first domain started by Xen is the privileged administrative domain referred to as domain zero or more commonly dom0.

The Administrative domain: dom0

As of Qubes OS 4.1.2, the operating system running in dom0 is Fedora Linux running a paravirtualized Linux kernel. It is the Linux kernel in dom0 that controls and brokers access to all the physical system hardware, via standard Linux kernel device drivers.

The operating system hosts the user's graphical desktop and controls most hardware devices. This includes the graphics device, USB ports, storage and input devices, such as the keyboard and mouse. The base graphical desktop is composed of the X server, the XFWM window manager and the XFCE desktop.

By design, dom0 has the least possible direct interaction with the qubes in order to minimize the possibility of an attack originating from there.[23][24]

Updates to the dom0 operating system and the included Template OS images are performed via a special mechanism which does not require dom0 operating system to connect directly to a network.

The User domains: qubes

An app qube (an instance of a qube) provides secure, compartmentalized execution of standard user applications such as a web browser, an email client or a text editor.

Operation of app qubes is controlled by the Qube Manager. It launches the discrete app qubes and presents their applications on the desktop of dom0 as normal process windows.

This mechanism follows the idea of a sandbox. After running the application, viewing the document, etc., the whole disposable will be destroyed on shutdown.[25]

Qubes OS integrates all of the app qubes into a single common desktop environment. The identity of each app qube for a given process is provided by an unforgeable, colored window border which is defined in the properties of the app qube.

Disk usage in dom0 is minimized by allowing multiple app qubes to share a common "template" root file system image maintained in read-only mode. Additional disk storage is only used for userʼs applications, data and per-VM settings.

Network domain

The network mechanism is the most exposed to security attacks. To circumvent this, it is isolated in a separate, unprivileged qube, named the net qube.

Another firewall Domain is used to house the Linux-kernel-based firewall, so that even if the network domain is compromised, the firewall is still isolated and protected (as it is running in a separate Linux kernel in a separate VM).[26]

Reception

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

Jesse Smith wrote a review of Qubes OS 3.1 for DistroWatch Weekly:[28]

I had a revelation though on the second day of my trial when I realized I had been using Qubes incorrectly. I had been treating Qubes as a security enhanced Linux distribution, as though it were a regular desktop operating system with some added security. This quickly frustrated me as it was difficult to share files between domains, take screen shots or even access the Internet from programs I had opened in Domain Zero. My experience was greatly improved when I started thinking of Qubes as being multiple, separate computers which all just happened to share a display screen. Once I began to look at each domain as its own island, cut off from all the others, Qubes made a lot more sense. Qubes brings domains together on one desktop in much the same way virtualization lets us run multiple operating systems on the same server.

Kyle Rankin from Linux Journal reviewed Qubes OS in 2016:[29]

I'm sure you already can see a number of areas where Qubes provides greater security than you would find in a regular Linux desktop.

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.[30]

See also

Notes

  1. ↑ The base (dom0) operating system used by Qubes OS is Fedora (source), Which (as of December 2022) uses the GNU coreutils.

References

  1. ↑ "Will Qubes seek to get certified under the GNU Free System Distribution Guidelines (GNU FSDG)?". https://www.qubes-os.org/faq/#will-qubes-seek-to-get-certified-under-the-gnu-free-system-distribution-guidelines-gnu-fsdg. 
  2. ↑ "Qubes OS License". https://www.qubes-os.org/doc/license/. 
  3. ↑ "Introducing Qubes 1.0!". September 3, 2012. http://theinvisiblethings.blogspot.com/2012/09/introducing-qubes-10.html. 
  4. ↑ "Qubes OS 4.2.0-rc5 is available for testing". www.qubes-os.org. 2023-11-26. https://www.qubes-os.org/news/2023/11/26/qubes-os-4-2-0-rc5-available-for-testing/. 
  5. ↑ "License Qubes OS". https://www.qubes-os.org/doc/QubesLicensing/. 
  6. ↑ "Qubes OS bakes in virty system-level security". The Register. September 5, 2012. https://www.theregister.co.uk/2012/09/05/qubes_secure_os_released/. 
  7. ↑ "Qubes OS Templates". https://www.qubes-os.org/doc/Templates/. 
  8. ↑ Issa, Abdullah; Murray, Toby; Ernst, Gidon (2018-12-04). "In search of perfect users: towards understanding the usability of converged multi-level secure user interfaces". OzCHI '18: 30th Australian Computer-Human Interaction Conference. Melbourne Australia: Association for Computing Machinery (ACM). pp. 572576. doi:10.1145/3292147.3292231. ISBN 978-1-4503-6188-0. https://dl.acm.org/doi/10.1145/3292147.3292231. Retrieved 2020-11-01. 
  9. ↑ Beaumont, Mark; McCarthy, Jim; Murray, Toby (2016-12-05). "The cross domain desktop compositor: using hardware-based video compositing for a multi-level secure user interface". ACSAC '16: 2016 Annual Computer Security Applications Conference. Los Angeles California USA: Association for Computing Machinery (ACM). pp. 533545. doi:10.1145/2991079.2991087. ISBN 978-1-4503-4771-6. https://dl.acm.org/doi/10.1145/2991079.2991087. Retrieved 2020-11-01. 
  10. ↑ Atanas Filyanov; Nas, Aysegül; Volkamer, Melanie (July 1, 2013). "Poster: On the Usability of Secure GUIs". pp. 11. 
  11. ↑ "The three approaches to computer security". Joanna Rutkowska. September 2, 2008. http://theinvisiblethings.blogspot.com/2008/09/three-approaches-to-computer-security.html. 
  12. ↑ "Qubes OS: An Operating System Designed For Security". Tom's hardware. August 30, 2011. http://www.tomshardware.com/reviews/qubes-os-joanna-rutkowska-windows,3009.html. 
  13. ↑ "A digital fortress?". The Economist. March 28, 2014. https://www.economist.com/blogs/babbage/2014/03/computer-security. 
  14. ↑ "How Splitting a Computer Into Multiple Realities Can Protect You From Hackers". Wired. November 20, 2014. https://www.wired.com/2014/11/protection-from-hackers. 
  15. ↑ "Partitioning my digital life into security domains". Joanna Rutkowska. March 13, 2011. http://theinvisiblethings.blogspot.com/2011/03/partitioning-my-digital-life-into.html. 
  16. ↑ Passwordless Root Access in VMs
  17. ↑ 17.0 17.1 Qubes FAQ
  18. ↑ Rutkowska, Joanna (May 3, 2010). "Google Groups - Qubes as a multi-user system". https://groups.google.com/forum/#!msg/qubes-devel/XnTly2JNfPw/BppN_D5vn4kJ. 
  19. ↑ 19.0 19.1 Why Intel VT-d ?
  20. ↑ Qubes system requirements
  21. ↑ "Copying Files between qubes". Qubes OS. https://www.qubes-os.org/doc/copying-files/. 
  22. ↑ "Copy and Paste". Qubes OS. https://www.qubes-os.org/doc/copy-paste/. 
  23. ↑ "(Un)Trusting your GUI Subsystem". Joanna Rutkowska. September 9, 2010. http://theinvisiblethings.blogspot.com/2010/09/untrusting-your-gui-subsystem.html. 
  24. ↑ "The Linux Security Circus: On GUI isolation". Joanna Rutkowska. April 23, 2011. http://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html. 
  25. ↑ "Qubes To Implement Disposable Virtual Machines". OSnews. June 3, 2010. http://www.osnews.com/story/23403/Qubes_To_Implement_Disposable_Virtual_Machines. 
  26. ↑ "Playing with Qubes Networking for Fun and Profit". Joanna Rutkowska. September 28, 2011. http://theinvisiblethings.blogspot.com/2011/09/playing-with-qubes-networking-for-fun.html. 
  27. ↑ "Endpoint Security Prize Finalists Announced!". https://www.qubes-os.org/experts/. 
  28. ↑ DistroWatch Weekly, Issue 656, 11 April 2016
  29. ↑ Secure Desktops with Qubes: Introduction |Linux Journal
  30. ↑ "Endpoint Security Prize Finalists Announced!". Michael Carbone. February 13, 2014. https://www.accessnow.org/blog/2014/02/13/endpoint-security-prize-finalists-announced. 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Qubes_OS&oldid=3460265"