q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Katherine Johnson — Mathematics to the Moon

Katherine Johnson’s mathematical calculations helped guide some of America’s most important early space missions while she confronted the racial and gender barriers faced by Black women in twentieth-century America.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Qubes OS

Qubes OS
Qubes OS 4.1.2 with its default Xfce DE running Fedora 37, Debian 11 and Whonix 16 virtualizations.
DeveloperThe Qubes OS Project

Invisible Things Labs

Joanna Rutkowska
OS familyLinux (Unix-like)
Working stateCurrent
Source modelOpen source with proprietary blobs,[1][2]
Initial releaseSeptember 3, 2012; 14 years ago (2012-09-03)[3]
Latest release4.3.2[4] Edit this on Wikidata / 2 October 2026; 14 days ago (2 October 2026)
Marketing targetsecurity by compartmentalization, desktop, laptop
Available inMultilingual
Update methodDNF (PackageKit)
Package managerRPM Package Manager
Supported platformsx86-64
Kernel typeMicrokernel (Xen Hypervisor running minimal Linux-based OSes and others)
UserlandGNU[a]
Default
user interface
Xfce
LicenseFree software licenses
(mainly GPL v2[7])
Official website
TaglineA Reasonably Secure Operating System

Qubes OS is a security-focused desktop operating system that aims to provide security through compartmentalization.[9] Compartmentalization 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, and Gentoo.[10] Users may also create their own templates.

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

Security goals

[edit]
Security domains scheme

Qubes implements a Security by Isolation approach.[14] 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.[15][16]

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

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).[18] Each of these domains is run in a separate qube.

The qubes have passwordless root access (e.g. passwordless sudo) by default.[19] UEFI Secure Boot is not supported out of the box. The Qubes OS team does not consider this a major security issue.[20] Qubes is not a multiuser system.[21]

Installation and System Requirements

[edit]

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 minimum base system requirements[22] for Qubes OS are:

  • 64-bit Intel or AMD processor with virtualization extensions[b]
  • 6 GB of RAM
  • 32 GB of disk space

User experience

[edit]

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[24] and clipboard paste buffers[25] 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

[edit]

Xen hypervisor and domains

[edit]

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

[edit]

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.[26][27]

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

[edit]

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

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

[edit]

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).[29]

Reception

[edit]

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

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

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:[32]

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

See also

[edit]

Notes

[edit]
  1. ^ The base (dom0) operating system in Qubes OS 4.2 is Fedora 37,[5] which uses the GNU coreutils.[6]
  2. ^ Since 2013, Qubes OS only supports 64-bit processors.[20] 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).[23] This is not a major issue for AMD processors since AMD IOMMU is functionally identical to Intel's VT-d.[23]

References

[edit]
  1. ^ "Will Qubes seek to get certified under the GNU Free System Distribution Guidelines (GNU FSDG)?".
  2. ^ "Qubes OS License".
  3. ^ "Introducing Qubes 1.0!". September 3, 2012.
  4. ^ "Qubes OS 4.3.2 has been released!". October 2, 2026. Retrieved October 4, 2026.
  5. ^ "Supported releases § Dom0". Archived from the original on February 24, 2025.
  6. ^ "Fedora CoreOS Release Notes § 37.20230401.3.0".
  7. ^ "License Qubes OS". www.qubes-os.org.
  8. ^ "Privacy policy". Qubes OS.
  9. ^ "Qubes OS bakes in virty system-level security". The Register. September 5, 2012.
  10. ^ "Qubes OS Templates".
  11. ^ Issa, Abdullah; Murray, Toby; Ernst, Gidon (December 4, 2018). "In search of perfect users: towards understanding the usability of converged multi-level secure user interfaces". Proceedings of the 30th Australian Conference on Computer-Human Interaction. OzCHI '18: 30th Australian Computer-Human Interaction Conference. Melbourne Australia: Association for Computing Machinery (ACM). p. 572576. doi:10.1145/3292147.3292231. ISBN 978-1-4503-6188-0. Retrieved November 1, 2020.
  12. ^ Beaumont, Mark; McCarthy, Jim; Murray, Toby (December 5, 2016). "The cross domain desktop compositor: using hardware-based video compositing for a multi-level secure user interface". Proceedings of the 32nd Annual Conference on Computer Security Applications. ACSAC '16: 2016 Annual Computer Security Applications Conference. Los Angeles California USA: Association for Computing Machinery (ACM). p. 533545. doi:10.1145/2991079.2991087. ISBN 978-1-4503-4771-6. Retrieved November 1, 2020.
  13. ^ Filyanov, Atanas; Nas, Aysegül; Volkamer, Melanie (July 1, 2013). "Poster: On the Usability of Secure GUIs" (PDF). p. 11. S2CID 17605611.
  14. ^ "The three approaches to computer security". Joanna Rutkowska. September 2, 2008.
  15. ^ "Qubes OS: An Operating System Designed For Security". Tom's hardware. August 30, 2011.
  16. ^ "A digital fortress?". The Economist. March 28, 2014.
  17. ^ "How Splitting a Computer Into Multiple Realities Can Protect You From Hackers". Wired. November 20, 2014.
  18. ^ "Partitioning my digital life into security domains". Joanna Rutkowska. March 13, 2011.
  19. ^ Passwordless Root Access in VMs
  20. ^ a b "Qubes FAQ". Retrieved August 5, 2025.
  21. ^ Rutkowska, Joanna (May 3, 2010). "Google Groups - Qubes as a multi-user system". Google Groups.
  22. ^ "Qubes system requirements". Archived from the original on January 30, 2025.
  23. ^ a b Why Intel VT-d ?
  24. ^ "Copying Files between qubes". Qubes OS. Retrieved June 5, 2020.
  25. ^ "Copy and Paste". Qubes OS. Retrieved June 5, 2020.
  26. ^ "(Un)Trusting your GUI Subsystem". Joanna Rutkowska. September 9, 2010.
  27. ^ "The Linux Security Circus: On GUI isolation". Joanna Rutkowska. April 23, 2011.
  28. ^ "Qubes To Implement Disposable Virtual Machines". OSnews. June 3, 2010.
  29. ^ "Playing with Qubes Networking for Fun and Profit". Joanna Rutkowska. September 28, 2011.
  30. ^ "Endpoint Security Prize Finalists Announced!".
  31. ^ DistroWatch Weekly, Issue 656, 11 April 2016
  32. ^ Secure Desktops with Qubes: Introduction |Linux Journal
  33. ^ "Endpoint Security Prize Finalists Announced!". Michael Carbone. February 13, 2014.
[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

Wikipedia

Qubes OS

Qubes OS is a security-focused desktop operating system that aims to provide security through compartmentalization. Compartmentalization 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, and Gentoo. Users may also create their own templates. Operating Systems like Qubes OS are referred to in academia as Converged Multi-Level Secure (MLS) Systems. Other proposals of similar systems have surfaced and SecureView and VMware vSphere are commercial competitors.

MORE →
Wikipedia

Anaconda (installer)

Anaconda is a free and open-source system installer for Linux distributions. Anaconda is used by Red Hat Enterprise Linux, Oracle Linux, Scientific Linux, Rocky Linux, AlmaLinux, CentOS, MIRACLE LINUX, Qubes OS, Fedora, Sabayon Linux, Bazzite Linux and BLAG Linux and GNU, also in some less known and discontinued distros like Progeny Componentized Linux, Asianux, Foresight Linux, Rpath Linux and VidaLinux.

MORE →
Wikipedia

Joanna Rutkowska

Joanna Rutkowska (born 1981) is a Polish computer security researcher, primarily known for her research on low-level security and stealth malware, and as founder of the Qubes OS security-focused desktop operating system.

MORE →
No preview image
Wikipedia

CLIP OS

CLIP OS is a Linux-based operating system created by ANSSI, the National Cybersecurity Agency of France. The aim is to produce a hardened operating system to secure sensitive information which meets the needs of the French Administration.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Who was the first African-American woman millionaire in the United States?

Madam C.J. Walker