mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-05-02 23:05:19 -04:00
Remove redundant h1 titles using # syntax
https://github.com/QubesOS/qubes-issues/issues/6701#issuecomment-862060759
This commit is contained in:
Andrew David Wong
parent
a4cbb51092
commit
4ff7430960
80 changed files with 0 additions and 80 deletions
|
|
@ -10,7 +10,6 @@ ref: 66
|
||||||
title: Development Workflow
|
title: Development Workflow
|
||||||
---
|
---
|
||||||
|
|
||||||
# Development Workflow
|
|
||||||
|
|
||||||
A workflow for developing Qubes OS+
|
A workflow for developing Qubes OS+
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ title: Qubes Builder
|
||||||
|
|
||||||
**Note: See [ISO building instructions](/doc/qubes-iso-building/) for a streamlined overview on how to use the build system.**
|
**Note: See [ISO building instructions](/doc/qubes-iso-building/) for a streamlined overview on how to use the build system.**
|
||||||
|
|
||||||
# Building Qubes from scratch
|
|
||||||
|
|
||||||
We have a fully automated build system for Qubes, that downloads, builds and
|
We have a fully automated build system for Qubes, that downloads, builds and
|
||||||
packages all the Qubes components, and finally should spit out a ready-to-use
|
packages all the Qubes components, and finally should spit out a ready-to-use
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 51
|
||||||
title: Code Signing
|
title: Code Signing
|
||||||
---
|
---
|
||||||
|
|
||||||
# Code Signing
|
|
||||||
|
|
||||||
All contributions to the Qubes OS [source code](/doc/source-code/) must be cryptographically signed by the author's PGP key.
|
All contributions to the Qubes OS [source code](/doc/source-code/) must be cryptographically signed by the author's PGP key.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -9,7 +9,6 @@ ref: 45
|
||||||
title: Automated Tests
|
title: Automated Tests
|
||||||
---
|
---
|
||||||
|
|
||||||
# Automated Tests
|
|
||||||
|
|
||||||
## Unit and Integration Tests
|
## Unit and Integration Tests
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 46
|
||||||
title: Mount LVM image
|
title: Mount LVM image
|
||||||
---
|
---
|
||||||
|
|
||||||
# How to mount LVM image
|
|
||||||
|
|
||||||
You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0).
|
You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 48
|
||||||
title: Profiling
|
title: Profiling
|
||||||
---
|
---
|
||||||
|
|
||||||
# Profiling
|
|
||||||
|
|
||||||
This is a python profiling primer.
|
This is a python profiling primer.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 44
|
||||||
title: Test Bench
|
title: Test Bench
|
||||||
---
|
---
|
||||||
|
|
||||||
# Test bench for Dom0
|
|
||||||
|
|
||||||
This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
|
This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 47
|
||||||
title: VM Configuration Interface
|
title: VM Configuration Interface
|
||||||
---
|
---
|
||||||
|
|
||||||
# VM Configuration Interface
|
|
||||||
|
|
||||||
Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes:
|
Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 50
|
||||||
title: Windows Debugging
|
title: Windows Debugging
|
||||||
---
|
---
|
||||||
|
|
||||||
# Debugging Windows HVMs
|
|
||||||
|
|
||||||
Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs.
|
Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 30
|
||||||
title: Documentation Guidelines
|
title: Documentation Guidelines
|
||||||
---
|
---
|
||||||
|
|
||||||
# Documentation guidelines
|
|
||||||
|
|
||||||
All Qubes OS documentation pages are stored as plain text files in the dedicated [qubes-doc](https://github.com/QubesOS/qubes-doc) repository.
|
All Qubes OS documentation pages are stored as plain text files in the dedicated [qubes-doc](https://github.com/QubesOS/qubes-doc) repository.
|
||||||
By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the web.
|
By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the web.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 242
|
||||||
title: Google Season of Docs
|
title: Google Season of Docs
|
||||||
---
|
---
|
||||||
|
|
||||||
# 2021 Google Season of Docs
|
|
||||||
|
|
||||||
Thank you for your interest in participating in the [2021 Google Season of Docs](https://developers.google.com/season-of-docs/) program with the [Qubes OS team](/team/). You can read more about the Google Season of Docs in the official [guides](https://developers.google.com/season-of-docs/docs/) and [FAQ](https://developers.google.com/season-of-docs/docs/faq).
|
Thank you for your interest in participating in the [2021 Google Season of Docs](https://developers.google.com/season-of-docs/) program with the [Qubes OS team](/team/). You can read more about the Google Season of Docs in the official [guides](https://developers.google.com/season-of-docs/docs/) and [FAQ](https://developers.google.com/season-of-docs/docs/faq).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 31
|
||||||
title: Usability & UX
|
title: Usability & UX
|
||||||
---
|
---
|
||||||
|
|
||||||
# Usability & UX
|
|
||||||
|
|
||||||
Software that is too complicated to use, is often unused. Because we want as many people as possible to benefit from its unique security properties, the usability and user experience of Qubes OS is an utmost priority!
|
Software that is too complicated to use, is often unused. Because we want as many people as possible to benefit from its unique security properties, the usability and user experience of Qubes OS is an utmost priority!
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 18
|
||||||
title: Qubes R1.0 Release Notes
|
title: Qubes R1.0 Release Notes
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes R1.0 Release Notes
|
|
||||||
|
|
||||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html).
|
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 25
|
||||||
title: Qubes R2.0 Release Notes
|
title: Qubes R2.0 Release Notes
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes R2.0 Release Notes
|
|
||||||
|
|
||||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html)
|
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html)
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 16
|
||||||
title: Qubes R3.1 release notes
|
title: Qubes R3.1 release notes
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes R3.1 release notes
|
|
||||||
|
|
||||||
## New features since 3.0
|
## New features since 3.0
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 21
|
||||||
title: Qubes R3.2 release notes
|
title: Qubes R3.2 release notes
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes R3.2 release notes
|
|
||||||
|
|
||||||
## New features since 3.1
|
## New features since 3.1
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 36
|
||||||
title: Admin API
|
title: Admin API
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes OS Admin API
|
|
||||||
|
|
||||||
## Goals
|
## Goals
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 39
|
||||||
title: 'Qrexec: Qubes RPC internals'
|
title: 'Qrexec: Qubes RPC internals'
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes RPC internals
|
|
||||||
|
|
||||||
(*This page details the current implementation of qrexec (qrexec3).
|
(*This page details the current implementation of qrexec (qrexec3).
|
||||||
A [general introduction](/doc/qrexec/) to qrexec is also available.
|
A [general introduction](/doc/qrexec/) to qrexec is also available.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 42
|
||||||
title: 'Qrexec: Socket-based services'
|
title: 'Qrexec: Socket-based services'
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qrexec: Socket-based services
|
|
||||||
|
|
||||||
*This page describes how to implement and use new socket-backed services for qrexec. See [qrexec](/doc/qrexec/) for general overview of the qrexec framework.*
|
*This page describes how to implement and use new socket-backed services for qrexec. See [qrexec](/doc/qrexec/) for general overview of the qrexec framework.*
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 38
|
||||||
title: Qrexec2
|
title: Qrexec2
|
||||||
---
|
---
|
||||||
|
|
||||||
# Command execution in VMs #
|
|
||||||
|
|
||||||
(*This page is about qrexec v2. For qrexec v3, see [here](/doc/qrexec3/).*)
|
(*This page is about qrexec v2. For qrexec v3, see [here](/doc/qrexec3/).*)
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 59
|
||||||
title: Networking
|
title: Networking
|
||||||
---
|
---
|
||||||
|
|
||||||
# VM network in Qubes
|
|
||||||
|
|
||||||
## Overall description
|
## Overall description
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 58
|
||||||
title: Template Implementation
|
title: Template Implementation
|
||||||
---
|
---
|
||||||
|
|
||||||
# Overview of VM block devices
|
|
||||||
|
|
||||||
Every VM has 4 block devices connected:
|
Every VM has 4 block devices connected:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 208
|
||||||
title: Canaries
|
title: Canaries
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes Canaries
|
|
||||||
|
|
||||||
A **Qubes Canary** is a security announcement periodically issued by the [Qubes Security Team](/security/#the-qubes-security-team) through the [Qubes Security Pack](/security/pack/) consisting of several statements to the effect that the signers of the canary have not been compromised.
|
A **Qubes Canary** is a security announcement periodically issued by the [Qubes Security Team](/security/#the-qubes-security-team) through the [Qubes Security Pack](/security/pack/) consisting of several statements to the effect that the signers of the canary have not been compromised.
|
||||||
The idea is that, as long as signed canaries including such statements continue to be published, all is well.
|
The idea is that, as long as signed canaries including such statements continue to be published, all is well.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 216
|
||||||
title: Canary Checklist
|
title: Canary Checklist
|
||||||
---
|
---
|
||||||
|
|
||||||
# Canary Checklist
|
|
||||||
|
|
||||||
## Preparation
|
## Preparation
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 215
|
||||||
title: Security Bulletin Checklist
|
title: Security Bulletin Checklist
|
||||||
---
|
---
|
||||||
|
|
||||||
# Security Bulletin Checklist
|
|
||||||
|
|
||||||
## Preparation
|
## Preparation
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 218
|
||||||
title: Qubes Security Bulletins (QSBs)
|
title: Qubes Security Bulletins (QSBs)
|
||||||
---
|
---
|
||||||
|
|
||||||
# Qubes Security Bulletins (QSBs)
|
|
||||||
|
|
||||||
A **Qubes Security Bulletin (QSB)** is a security announcement issued by the [Qubes Security Team](/security/#the-qubes-security-team) through the [Qubes Security Pack](/security/pack/).
|
A **Qubes Security Bulletin (QSB)** is a security announcement issued by the [Qubes Security Team](/security/#the-qubes-security-team) through the [Qubes Security Pack](/security/pack/).
|
||||||
A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them.
|
A QSB typically provides a summary and impact analysis of one or more recently-discovered software vulnerabilities, including details about patching to address them.
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 210
|
||||||
title: Security Goals
|
title: Security Goals
|
||||||
---
|
---
|
||||||
|
|
||||||
# Security design goals
|
|
||||||
|
|
||||||
Qubes OS implements a security-by-isolation (or security-by-compartmentalization) approach by providing the ability to easily create many security domains. These domains are implemented as lightweight Virtual Machines (VMs) running under the Xen hypervisor. Qubes' main objective is to provide strong isolation between these domains, so that even if an attacker compromises one of the domains, the others are still safe. Qubes, however, does not attempt to provide any security isolation for applications running within the same domain. For example, a buggy web browser running in a Qubes domain could still be compromised just as easily as on a regular Linux distribution. The difference that Qubes makes is that now the attacker doesn't have access to all the software running in the other domains.
|
Qubes OS implements a security-by-isolation (or security-by-compartmentalization) approach by providing the ability to easily create many security domains. These domains are implemented as lightweight Virtual Machines (VMs) running under the Xen hypervisor. Qubes' main objective is to provide strong isolation between these domains, so that even if an attacker compromises one of the domains, the others are still safe. Qubes, however, does not attempt to provide any security isolation for applications running within the same domain. For example, a buggy web browser running in a Qubes domain could still be compromised just as easily as on a regular Linux distribution. The difference that Qubes makes is that now the attacker doesn't have access to all the software running in the other domains.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 211
|
||||||
title: Verifying Signatures
|
title: Verifying Signatures
|
||||||
---
|
---
|
||||||
|
|
||||||
# On Digital Signatures and Key Verification
|
|
||||||
|
|
||||||
## What Digital Signatures Can and Cannot Prove
|
## What Digital Signatures Can and Cannot Prove
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 179
|
||||||
title: awesome
|
title: awesome
|
||||||
---
|
---
|
||||||
|
|
||||||
# Using awesome in dom0
|
|
||||||
|
|
||||||
## Qubes-specific features
|
## Qubes-specific features
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 186
|
||||||
title: How to make any file in a TemplateBasedVM persistent using bind-dirs
|
title: How to make any file in a TemplateBasedVM persistent using bind-dirs
|
||||||
---
|
---
|
||||||
|
|
||||||
# How to make any file in a TemplateBasedVM persistent using bind-dirs #
|
|
||||||
|
|
||||||
## What are bind-dirs? ##
|
## What are bind-dirs? ##
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 174
|
||||||
title: DisposableVM Customization
|
title: DisposableVM Customization
|
||||||
---
|
---
|
||||||
|
|
||||||
# DisposableVM Customization
|
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 184
|
||||||
title: GUI Configuration
|
title: GUI Configuration
|
||||||
---
|
---
|
||||||
|
|
||||||
# GUI Configuration
|
|
||||||
|
|
||||||
## Video RAM adjustment for high-resolution displays
|
## Video RAM adjustment for high-resolution displays
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 183
|
||||||
title: i3
|
title: i3
|
||||||
---
|
---
|
||||||
|
|
||||||
# i3 installation in dom0
|
|
||||||
|
|
||||||
i3 is part of the stable repository (as of Qubes R3.1) and can be installed by
|
i3 is part of the stable repository (as of Qubes R3.1) and can be installed by
|
||||||
using the [dom0 update mechanism](/doc/software-update-dom0/). To install the i3
|
using the [dom0 update mechanism](/doc/software-update-dom0/). To install the i3
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 225
|
||||||
title: Installing contributed packages
|
title: Installing contributed packages
|
||||||
---
|
---
|
||||||
|
|
||||||
# Installing contributed packages
|
|
||||||
|
|
||||||
_This page is for users who wish to install contributed packages.
|
_This page is for users who wish to install contributed packages.
|
||||||
If you want to contribute a package, please see [package contributions](/doc/package-contributions/)._
|
If you want to contribute a package, please see [package contributions](/doc/package-contributions/)._
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 173
|
||||||
title: Managing VM kernel
|
title: Managing VM kernel
|
||||||
---
|
---
|
||||||
|
|
||||||
# VM kernel managed by dom0
|
|
||||||
|
|
||||||
By default, VMs kernels are provided by dom0.
|
By default, VMs kernels are provided by dom0.
|
||||||
(See [here](/doc/software-update-dom0/#kernel-upgrade) for information about upgrading kernels in dom0.)
|
(See [here](/doc/software-update-dom0/#kernel-upgrade) for information about upgrading kernels in dom0.)
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 185
|
||||||
title: Management stack
|
title: Management stack
|
||||||
---
|
---
|
||||||
|
|
||||||
# Management Infrastructure
|
|
||||||
|
|
||||||
Since the Qubes R3.1 release we have included the Salt (also called SaltStack)
|
Since the Qubes R3.1 release we have included the Salt (also called SaltStack)
|
||||||
management engine in dom0 as default (with some states already configured).
|
management engine in dom0 as default (with some states already configured).
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 187
|
||||||
title: Secondary Storage
|
title: Secondary Storage
|
||||||
---
|
---
|
||||||
|
|
||||||
# Storing AppVMs on Secondary Drives
|
|
||||||
|
|
||||||
Suppose you have a fast but small primary SSD and a large but slow secondary HDD.
|
Suppose you have a fast but small primary SSD and a large but slow secondary HDD.
|
||||||
You want to store a subset of your AppVMs on the HDD.
|
You want to store a subset of your AppVMs on the HDD.
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 181
|
||||||
title: USB Qubes
|
title: USB Qubes
|
||||||
---
|
---
|
||||||
|
|
||||||
# USB Qubes #
|
|
||||||
|
|
||||||
If during installation you enabled the creation of a USB-qube, your system should be setup already and none of the mentioned steps here should be necessary. (Unless you want to [remove your USB-qube](#removing-a-usb-qube).) If for any reason no USB-qube was created during installation, this guide will show you how to do so.
|
If during installation you enabled the creation of a USB-qube, your system should be setup already and none of the mentioned steps here should be necessary. (Unless you want to [remove your USB-qube](#removing-a-usb-qube).) If for any reason no USB-qube was created during installation, this guide will show you how to do so.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 193
|
||||||
title: Block (Storage) Devices
|
title: Block (Storage) Devices
|
||||||
---
|
---
|
||||||
|
|
||||||
# Block (Storage) Devices
|
|
||||||
|
|
||||||
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 198
|
||||||
title: Copying from (and to) dom0
|
title: Copying from (and to) dom0
|
||||||
---
|
---
|
||||||
|
|
||||||
# Copying from (and to) dom0
|
|
||||||
|
|
||||||
This page covers copying files and clipboard text between [dom0](/doc/glossary/#dom0) and [domUs](/doc/glossary/#domu).
|
This page covers copying files and clipboard text between [dom0](/doc/glossary/#dom0) and [domUs](/doc/glossary/#domu).
|
||||||
Since dom0 is special, the processes are different from [copying and pasting text between qubes](/doc/copy-paste/) and [copying and moving files between qubes](/doc/copying-files/).
|
Since dom0 is special, the processes are different from [copying and pasting text between qubes](/doc/copy-paste/) and [copying and moving files between qubes](/doc/copying-files/).
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 188
|
||||||
title: Device Handling
|
title: Device Handling
|
||||||
---
|
---
|
||||||
|
|
||||||
# Device Handling
|
|
||||||
|
|
||||||
This is an overview of device handling in Qubes OS.
|
This is an overview of device handling in Qubes OS.
|
||||||
For specific devices ([block](/doc/block-devices/), [USB](/doc/usb-devices/) and [PCI](/doc/pci-devices/) devices), please visit their respective pages.
|
For specific devices ([block](/doc/block-devices/), [USB](/doc/usb-devices/) and [PCI](/doc/pci-devices/) devices), please visit their respective pages.
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 203
|
||||||
title: DisposableVMs
|
title: DisposableVMs
|
||||||
---
|
---
|
||||||
|
|
||||||
# DisposableVMs
|
|
||||||
|
|
||||||
A DisposableVM (previously known as a "DispVM") is a lightweight VM that can be created quickly and will disappear when closed.
|
A DisposableVM (previously known as a "DispVM") is a lightweight VM that can be created quickly and will disappear when closed.
|
||||||
DisposableVMs are usually created in order to host a single application, like a viewer, editor, or web browser.
|
DisposableVMs are usually created in order to host a single application, like a viewer, editor, or web browser.
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ redirect_from:
|
||||||
ref: 190
|
ref: 190
|
||||||
---
|
---
|
||||||
|
|
||||||
# Get started
|
|
||||||
|
|
||||||
After [downloading](/downloads/) and [installing](/doc/installation-guide/) Qubes OS, let's cover some basic concepts.
|
After [downloading](/downloads/) and [installing](/doc/installation-guide/) Qubes OS, let's cover some basic concepts.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 197
|
||||||
title: PCI Devices
|
title: PCI Devices
|
||||||
---
|
---
|
||||||
|
|
||||||
# PCI Devices
|
|
||||||
|
|
||||||
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 194
|
||||||
title: Installing and updating software in dom0
|
title: Installing and updating software in dom0
|
||||||
---
|
---
|
||||||
|
|
||||||
# Installing and updating software in dom0
|
|
||||||
|
|
||||||
Updating [dom0](/doc/glossary/#dom0) is one of the main steps in [Updating Qubes OS](/doc/updating-qubes-os/).
|
Updating [dom0](/doc/glossary/#dom0) is one of the main steps in [Updating Qubes OS](/doc/updating-qubes-os/).
|
||||||
It is very important to keep dom0 up-to-date with the latest [security](/security/) updates.
|
It is very important to keep dom0 up-to-date with the latest [security](/security/) updates.
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 189
|
||||||
title: Installing and updating software in domUs
|
title: Installing and updating software in domUs
|
||||||
---
|
---
|
||||||
|
|
||||||
# Installing and updating software in domUs
|
|
||||||
|
|
||||||
Updating [domUs](/doc/glossary/#domu), especially [TemplateVMs](/doc/templates/) and [StandaloneVMs](/doc/standalone-and-hvm/) are important steps in [Updating Qubes OS](/doc/updating-qubes-os/).
|
Updating [domUs](/doc/glossary/#domu), especially [TemplateVMs](/doc/templates/) and [StandaloneVMs](/doc/standalone-and-hvm/) are important steps in [Updating Qubes OS](/doc/updating-qubes-os/).
|
||||||
It is very import to keep domUs up-to-date with the latest [security](/security/) updates.
|
It is very import to keep domUs up-to-date with the latest [security](/security/) updates.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 200
|
||||||
title: Updating Qubes OS
|
title: Updating Qubes OS
|
||||||
---
|
---
|
||||||
|
|
||||||
# Updating Qubes OS
|
|
||||||
|
|
||||||
*This page is about updating your system while staying on the same [supported version of Qubes OS](/doc/supported-versions/#qubes-os).
|
*This page is about updating your system while staying on the same [supported version of Qubes OS](/doc/supported-versions/#qubes-os).
|
||||||
If you're instead looking to upgrade from your current version of Qubes OS to a newer version, see the [Upgrade Guides](/doc/upgrade/).*
|
If you're instead looking to upgrade from your current version of Qubes OS to a newer version, see the [Upgrade Guides](/doc/upgrade/).*
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 195
|
||||||
title: USB Devices
|
title: USB Devices
|
||||||
---
|
---
|
||||||
|
|
||||||
# USB Devices
|
|
||||||
|
|
||||||
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
*This page is part of [device handling in qubes](/doc/device-handling/).*
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 152
|
||||||
title: Custom Installation
|
title: Custom Installation
|
||||||
---
|
---
|
||||||
|
|
||||||
# Custom Installation
|
|
||||||
|
|
||||||
In the present context, "custom installation" refers to things like manual partitioning, setting up LVM and RAID, and manual LUKS encryption configuration.
|
In the present context, "custom installation" refers to things like manual partitioning, setting up LVM and RAID, and manual LUKS encryption configuration.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 149
|
||||||
title: Installation security
|
title: Installation security
|
||||||
---
|
---
|
||||||
|
|
||||||
# Installation security
|
|
||||||
|
|
||||||
There are several security matters to consider before and during the Qubes installation process.
|
There are several security matters to consider before and during the Qubes installation process.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 154
|
||||||
title: Supported Versions
|
title: Supported Versions
|
||||||
---
|
---
|
||||||
|
|
||||||
# Supported Versions
|
|
||||||
|
|
||||||
This page details the level and period of support for versions of operating systems in the Qubes ecosystem.
|
This page details the level and period of support for versions of operating systems in the Qubes ecosystem.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 159
|
||||||
title: Upgrading to R3.0
|
title: Upgrading to R3.0
|
||||||
---
|
---
|
||||||
|
|
||||||
# Upgrading Qubes R2 to R3.0
|
|
||||||
|
|
||||||
**This instruction is highly experimental, the official way to upgrade from R2 is to backup the data and reinstall the system. Use at your own risk!**
|
**This instruction is highly experimental, the official way to upgrade from R2 is to backup the data and reinstall the system. Use at your own risk!**
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 155
|
||||||
title: Upgrading to R3.1
|
title: Upgrading to R3.1
|
||||||
---
|
---
|
||||||
|
|
||||||
# Upgrading Qubes R3.0 to R3.1
|
|
||||||
|
|
||||||
**Before attempting either an in-place upgrade or a clean installation, we
|
**Before attempting either an in-place upgrade or a clean installation, we
|
||||||
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 161
|
||||||
title: Upgrading to R3.2
|
title: Upgrading to R3.2
|
||||||
---
|
---
|
||||||
|
|
||||||
# Upgrading Qubes R3.1 to R3.2
|
|
||||||
|
|
||||||
**Before attempting either an in-place upgrade or a clean installation, we
|
**Before attempting either an in-place upgrade or a clean installation, we
|
||||||
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,6 @@ ref: 144
|
||||||
title: Certified Hardware
|
title: Certified Hardware
|
||||||
---
|
---
|
||||||
|
|
||||||
# Certified Hardware
|
|
||||||
|
|
||||||
The Qubes OS Project aims to partner with a select few computer vendors to ensure that Qubes users have reliable hardware purchasing options.
|
The Qubes OS Project aims to partner with a select few computer vendors to ensure that Qubes users have reliable hardware purchasing options.
|
||||||
We aim for these vendors to be as diverse as possible in terms of geography, cost, and availability.
|
We aim for these vendors to be as diverse as possible in terms of geography, cost, and availability.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 145
|
||||||
title: Hardware Testing
|
title: Hardware Testing
|
||||||
---
|
---
|
||||||
|
|
||||||
# Hardware Testing
|
|
||||||
|
|
||||||
The Qubes developers test Qubes OS on certain hardware models.
|
The Qubes developers test Qubes OS on certain hardware models.
|
||||||
The tested hardware described on this page differs from [Qubes Certified Hardware](/doc/certified-hardware/) in a few key ways:
|
The tested hardware described on this page differs from [Qubes Certified Hardware](/doc/certified-hardware/) in a few key ways:
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 142
|
||||||
title: System Requirements
|
title: System Requirements
|
||||||
---
|
---
|
||||||
|
|
||||||
# System Requirements
|
|
||||||
|
|
||||||
<div class="alert alert-warning" role="alert">
|
<div class="alert alert-warning" role="alert">
|
||||||
<i class="fa fa-exclamation-triangle"></i>
|
<i class="fa fa-exclamation-triangle"></i>
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 133
|
||||||
title: In-place upgrade of Debian TemplateVMs
|
title: In-place upgrade of Debian TemplateVMs
|
||||||
---
|
---
|
||||||
|
|
||||||
# Upgrading Debian TemplateVMs
|
|
||||||
|
|
||||||
<div class="alert alert-danger" role="alert">
|
<div class="alert alert-danger" role="alert">
|
||||||
<i class="fa fa-exclamation-triangle"></i>
|
<i class="fa fa-exclamation-triangle"></i>
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 134
|
||||||
title: The Debian TemplateVM
|
title: The Debian TemplateVM
|
||||||
---
|
---
|
||||||
|
|
||||||
# The Debian TemplateVM
|
|
||||||
|
|
||||||
The Debian [TemplateVM](/doc/templates/) is an officially [supported](/doc/supported-versions/#templatevms) TemplateVM in Qubes OS.
|
The Debian [TemplateVM](/doc/templates/) is an officially [supported](/doc/supported-versions/#templatevms) TemplateVM in Qubes OS.
|
||||||
This page is about the standard (or "full") Debian TemplateVM.
|
This page is about the standard (or "full") Debian TemplateVM.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 136
|
||||||
title: The Fedora TemplateVM
|
title: The Fedora TemplateVM
|
||||||
---
|
---
|
||||||
|
|
||||||
# The Fedora TemplateVM
|
|
||||||
|
|
||||||
The Fedora [TemplateVM](/doc/templates/) is the default TemplateVM in Qubes OS. This page is about the standard (or "full") Fedora TemplateVM. For the minimal and Xfce versions, please see the [Minimal TemplateVMs](/doc/templates/minimal/) and [Xfce TemplateVMs](/doc/templates/xfce/) pages.
|
The Fedora [TemplateVM](/doc/templates/) is the default TemplateVM in Qubes OS. This page is about the standard (or "full") Fedora TemplateVM. For the minimal and Xfce versions, please see the [Minimal TemplateVMs](/doc/templates/minimal/) and [Xfce TemplateVMs](/doc/templates/xfce/) pages.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -12,7 +12,6 @@ ref: 130
|
||||||
title: StandaloneVMs and HVMs
|
title: StandaloneVMs and HVMs
|
||||||
---
|
---
|
||||||
|
|
||||||
# StandaloneVMs and HVMs
|
|
||||||
|
|
||||||
A [StandaloneVM](/doc/glossary/#standalonevm) is a type of VM in Qubes that is created by cloning a [TemplateVM](/doc/templates/).
|
A [StandaloneVM](/doc/glossary/#standalonevm) is a type of VM in Qubes that is created by cloning a [TemplateVM](/doc/templates/).
|
||||||
Unlike TemplateVMs, however, StandaloneVMs do not supply their root filesystems to other VMs.
|
Unlike TemplateVMs, however, StandaloneVMs do not supply their root filesystems to other VMs.
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 131
|
||||||
title: TemplateVMs
|
title: TemplateVMs
|
||||||
---
|
---
|
||||||
|
|
||||||
# TemplateVMs
|
|
||||||
|
|
||||||
In [Getting Started](/getting-started/), we covered the distinction in Qubes OS between where you *install* your software and where you *run* your software.
|
In [Getting Started](/getting-started/), we covered the distinction in Qubes OS between where you *install* your software and where you *run* your software.
|
||||||
Your software is installed in [TemplateVMs](/doc/glossary/#templatevm) (or "templates" for short).
|
Your software is installed in [TemplateVMs](/doc/glossary/#templatevm) (or "templates" for short).
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 222
|
||||||
title: Xfce TemplateVMs
|
title: Xfce TemplateVMs
|
||||||
---
|
---
|
||||||
|
|
||||||
# Xfce TemplateVMs
|
|
||||||
|
|
||||||
If you would like to use Xfce (more lightweight compared to GNOME desktop environment) Linux distribution in your qubes,
|
If you would like to use Xfce (more lightweight compared to GNOME desktop environment) Linux distribution in your qubes,
|
||||||
you can install one of the available Xfce templates for [Fedora](/doc/templates/fedora/), [CentOS](/doc/templates/centos/) or [Gentoo](/doc/templates/gentoo/).
|
you can install one of the available Xfce templates for [Fedora](/doc/templates/fedora/), [CentOS](/doc/templates/centos/) or [Gentoo](/doc/templates/gentoo/).
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 170
|
||||||
title: Device Handling Security
|
title: Device Handling Security
|
||||||
---
|
---
|
||||||
|
|
||||||
# Device Handling Security
|
|
||||||
|
|
||||||
Any additional ability a VM gains is additional attack surface.
|
Any additional ability a VM gains is additional attack surface.
|
||||||
It's a good idea to always attach the minimum entity required in a VM.
|
It's a good idea to always attach the minimum entity required in a VM.
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 167
|
||||||
title: The Qubes U2F Proxy
|
title: The Qubes U2F Proxy
|
||||||
---
|
---
|
||||||
|
|
||||||
# The Qubes U2F Proxy
|
|
||||||
|
|
||||||
The [Qubes U2F Proxy](https://github.com/QubesOS/qubes-app-u2f) is a secure proxy intended to make use of U2F two-factor authentication devices with web browsers without exposing the browser to the full USB stack, not unlike the [USB keyboard and mouse proxies](/doc/usb/) implemented in Qubes.
|
The [Qubes U2F Proxy](https://github.com/QubesOS/qubes-app-u2f) is a secure proxy intended to make use of U2F two-factor authentication devices with web browsers without exposing the browser to the full USB stack, not unlike the [USB keyboard and mouse proxies](/doc/usb/) implemented in Qubes.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -9,7 +9,6 @@ ref: 169
|
||||||
title: YubiKey in Qubes
|
title: YubiKey in Qubes
|
||||||
---
|
---
|
||||||
|
|
||||||
# Using YubiKey to Qubes authentication
|
|
||||||
|
|
||||||
You can use a YubiKey to enhance Qubes user authentication, for example to mitigate risk of someone snooping the password.
|
You can use a YubiKey to enhance Qubes user authentication, for example to mitigate risk of someone snooping the password.
|
||||||
This can also slightly improve security when you have a [USB keyboard](/doc/device-handling-security/#security-warning-on-usb-input-devices).
|
This can also slightly improve security when you have a [USB keyboard](/doc/device-handling-security/#security-warning-on-usb-input-devices).
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,6 @@ ref: 231
|
||||||
title: Disk Troubleshooting
|
title: Disk Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Disk Troubleshooting Guide #
|
|
||||||
|
|
||||||
## "Out of disk space" error ##
|
## "Out of disk space" error ##
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 233
|
||||||
title: GUI Troubleshooting
|
title: GUI Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# GUI Troubleshooting
|
|
||||||
|
|
||||||
## Can't click on anything after connecting 4k external display
|
## Can't click on anything after connecting 4k external display
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 97
|
||||||
title: Hardware Troubleshooting
|
title: Hardware Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Troubleshooting hardware-related issues
|
|
||||||
|
|
||||||
## Audio doesn't work / Troubleshooting newer hardware
|
## Audio doesn't work / Troubleshooting newer hardware
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 232
|
||||||
title: HVM Troubleshooting
|
title: HVM Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# HVM Troubleshooting
|
|
||||||
|
|
||||||
## HVM pauses on boot, followed by kernel error
|
## HVM pauses on boot, followed by kernel error
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 224
|
||||||
title: Installation Troubleshooting
|
title: Installation Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Installation Troubleshooting
|
|
||||||
|
|
||||||
## "An unknown error has occurred" error during installation
|
## "An unknown error has occurred" error during installation
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 235
|
||||||
title: Media Troubleshooting
|
title: Media Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Video and Audio Troubleshooting
|
|
||||||
|
|
||||||
## Can't play media videos in a VM due to missing codecs
|
## Can't play media videos in a VM due to missing codecs
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 230
|
||||||
title: PCI Troubleshooting
|
title: PCI Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# PCI troubleshooting
|
|
||||||
|
|
||||||
## DMA errors
|
## DMA errors
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -9,7 +9,6 @@ ref: 94
|
||||||
title: Suspend/Resume Troubleshooting
|
title: Suspend/Resume Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Troubleshooting problems relating to suspend/resume
|
|
||||||
|
|
||||||
## Network-Manager says “Device not ready” on suspend/resume
|
## Network-Manager says “Device not ready” on suspend/resume
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 177
|
||||||
title: UEFI Troubleshooting
|
title: UEFI Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Troubleshooting UEFI related problems
|
|
||||||
|
|
||||||
## Successfully installed in legacy mode, but had to change some kernel parameters
|
## Successfully installed in legacy mode, but had to change some kernel parameters
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 239
|
||||||
title: Update Troubleshooting
|
title: Update Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Fixing issues that arise during updating
|
|
||||||
|
|
||||||
## “Failed to synchronize cache for repo” errors when updating Fedora templates
|
## “Failed to synchronize cache for repo” errors when updating Fedora templates
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 98
|
||||||
title: Updating Debian and Whonix
|
title: Updating Debian and Whonix
|
||||||
---
|
---
|
||||||
|
|
||||||
# Updating Debian and Whonix
|
|
||||||
|
|
||||||
Despite Qubes shipping with [Debian Templates](/doc/templates/debian/), most of Qubes core components run on Fedora and thus our documentation has better coverage for Fedora. However, Qubes has been working closely with the [Whonix](https://whonix.org) project which is based on Debian.
|
Despite Qubes shipping with [Debian Templates](/doc/templates/debian/), most of Qubes core components run on Fedora and thus our documentation has better coverage for Fedora. However, Qubes has been working closely with the [Whonix](https://whonix.org) project which is based on Debian.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 234
|
||||||
title: USB Troubleshooting
|
title: USB Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# USB troubleshooting
|
|
||||||
|
|
||||||
## disp-sys-usb does not start
|
## disp-sys-usb does not start
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -8,7 +8,6 @@ ref: 223
|
||||||
title: VM Troubleshooting
|
title: VM Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# VM troubleshooting
|
|
||||||
|
|
||||||
## VM Kernel troubleshooting
|
## VM Kernel troubleshooting
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7,7 +7,6 @@ ref: 240
|
||||||
title: VPN Troubleshooting
|
title: VPN Troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# VPN Troubleshooting Guide
|
|
||||||
|
|
||||||
## Tips
|
## Tips
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue