Remove extra newlines at the beginning/end of files
Those are redundant, and yaml parser strips them in fact. By removing them, loading and saving yaml file without any change indeed produce the same output. This is useful for prepare_for_translation.py script (which adds lang and ref tags) - to produce only change that indeed was made.
This commit is contained in:
Marek Marczykowski-Górecki
parent
4851518719
commit
3806ecf338
|
|
@ -10,7 +10,6 @@ ref: 66
|
|||
title: Development Workflow
|
||||
---
|
||||
|
||||
|
||||
A workflow for developing Qubes OS+
|
||||
|
||||
First things first, setup [QubesBuilder](/doc/qubes-builder/). This guide
|
||||
|
|
@ -537,4 +536,3 @@ Usage: add this line to `/etc/apt/sources.list` on test machine (adjust host and
|
|||
~~~
|
||||
deb http://local-test.lan/linux-deb/r3.1 jessie-unstable main
|
||||
~~~
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 65
|
|||
title: Qubes Builder Details
|
||||
---
|
||||
|
||||
|
||||
Components Makefile.builder file
|
||||
--------------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 63
|
|||
title: Qubes ISO Building
|
||||
---
|
||||
|
||||
|
||||
Build Environment
|
||||
-----------------
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 51
|
|||
title: Code Signing
|
||||
---
|
||||
|
||||
|
||||
All contributions to the Qubes OS [source code](/doc/source-code/) must be cryptographically signed by the author's PGP key.
|
||||
|
||||
## Generating a Key
|
||||
|
|
@ -202,4 +201,3 @@ Please upload it.
|
|||
If you're submitting a patch by emailing the [developer mailing list](/support/#qubes-devel), simply sign your email with your PGP key.
|
||||
One good way to do this is with a program like [Enigmail](https://www.enigmail.net/).
|
||||
Enigmail is a security addon for the Mozilla Thunderbird email client that allows you to easily digitally encrypt and sign your emails.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 53
|
|||
title: Coding Style
|
||||
---
|
||||
|
||||
|
||||
Rationale
|
||||
---------
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 52
|
|||
title: Software License
|
||||
---
|
||||
|
||||
|
||||
Qubes is a compilation of software packages, each under its own license. The compilation is made available under the GNU General Public License version 2.
|
||||
|
||||
The full text of the GPL v2 license can be found [here](https://www.gnu.org/licenses/gpl-2.0.html).
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 54
|
|||
title: Source Code
|
||||
---
|
||||
|
||||
|
||||
All the Qubes code is kept in Git repositories. We have divided the project into
|
||||
several components, each of which has its own separate repository, for example:
|
||||
|
||||
|
|
@ -81,4 +80,3 @@ method you choose, you must [sign your code](/doc/code-signing/) before it can b
|
|||
name and email, so that *your* name will be used as a commit's author.
|
||||
5. Send your patch to `qubes-devel`. Start the message subject with
|
||||
`[PATCH]`.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 45
|
|||
title: Automated Tests
|
||||
---
|
||||
|
||||
|
||||
## Unit and Integration Tests
|
||||
|
||||
Starting with Qubes R3 we use [python unittest](https://docs.python.org/3/library/unittest.html) to perform automatic tests of Qubes OS.
|
||||
|
|
@ -260,4 +259,3 @@ In practice, however, either Xen or QEMU crashes when this is attempted.
|
|||
Nonetheless, PV works well, which is sufficient for automated installation testing.
|
||||
|
||||
Thanks to an anonymous donor, our openQA system is hosted in a datacenter on hardware that meets these requirements.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 46
|
|||
title: How to Mount LVM Images
|
||||
---
|
||||
|
||||
|
||||
You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0).
|
||||
|
||||
1: make the image available for qubesdb.
|
||||
|
|
@ -53,4 +52,3 @@ From the GUI, or from the command line:
|
|||
# References
|
||||
|
||||
Please consult this issue's [comment](https://github.com/QubesOS/qubes-issues/issues/4687#issuecomment-451626625).
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 48
|
|||
title: Python Profiling
|
||||
---
|
||||
|
||||
|
||||
This is a python profiling primer.
|
||||
|
||||
For the purpose of this document, `qubes-dev` is name of the domain used for postprocessing profiling stats.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 49
|
|||
title: Safe Remote Dom0 Terminals
|
||||
---
|
||||
|
||||
|
||||
If you do not have working graphics in Dom0, then using a terminal can be quite annoying!
|
||||
This was the case for the author while trying to debug PCI-passthrough of a machine's primary (only) GPU.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 44
|
|||
title: How to Set Up a Test Bench
|
||||
---
|
||||
|
||||
|
||||
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.
|
||||
|
||||
We will set up a spare machine (bare metal, not a virtual) that will be hosting our experimental Dom0. We will communicate with it via Ethernet and SSH. This tutorial assumes you are familiar with [QubesBuilder](/doc/qubes-builder/) and you have it set up and running flawlessly.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 47
|
|||
title: VM Configuration Interface
|
||||
---
|
||||
|
||||
|
||||
Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes:
|
||||
|
||||
- QubesDB
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 50
|
|||
title: Windows Debugging
|
||||
---
|
||||
|
||||
|
||||
Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs.
|
||||
|
||||
User-mode debugging is usually straightforward if it can be done on one machine. Just duplicate your normal debugging environment in the VM.
|
||||
|
|
|
|||
|
|
@ -561,4 +561,3 @@ Here's an example that follows the indentation rules:
|
|||
|
||||
Please try to write good commit messages, according to the [instructions in our
|
||||
coding style guidelines](/doc/coding-style/#commit-message-guidelines).
|
||||
|
||||
|
|
|
|||
|
|
@ -586,4 +586,3 @@ would override all the user changes there). More details:
|
|||
----
|
||||
|
||||
We adapted some of the language here about GSoC from the [KDE GSoC page](https://community.kde.org/GSoC).
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 242
|
|||
title: 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).
|
||||
|
||||
## 2021 Project Idea
|
||||
|
|
@ -145,4 +144,3 @@ Fixing this last point may require very close cooperation with developers, as th
|
|||
- [Markdown](https://daringfireball.net/projects/markdown/)
|
||||
|
||||
**Mentor**: [Marek Marczykowski-Górecki](/team/)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 29
|
|||
title: Package Contributions
|
||||
---
|
||||
|
||||
|
||||
_This page is for developers who wish to contribute packages.
|
||||
If you want to install contributed packages, please see [installing contributed packages](/doc/installing-contributed-packages/)._
|
||||
|
||||
|
|
@ -101,4 +100,3 @@ As the maintainer of the package, it is your privilege and responsibility to:
|
|||
|
||||
If you do not wish to be the maintainer of your package, please let us know.
|
||||
If you do not act on your maintainer duties for a given package for an extended period of time and after at least one reminder, we will assume that you no longer wish to be the maintainer for that package.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 31
|
|||
title: 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!
|
||||
|
||||
We ask anyone developing for Qubes OS to please read through this guide to better understand the user experience we strive to achieve. We also ask them to review [our style guide](/doc/style-guide/) for other design related information.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 18
|
|||
title: Qubes R1.0 Release Notes
|
||||
---
|
||||
|
||||
|
||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html).
|
||||
|
||||
## Known issues
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 25
|
|||
title: 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)
|
||||
|
||||
## New features since 1.0
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 20
|
|||
title: Qubes R3.0 Release Schedule
|
||||
---
|
||||
|
||||
|
||||
| Date | Stage |
|
||||
| -----------:| ------------------------------------- |
|
||||
| 5 Sep 2015 | current-testing freeze before 3.0-rc3 |
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 16
|
|||
title: Qubes R3.1 release notes
|
||||
---
|
||||
|
||||
|
||||
## New features since 3.0
|
||||
|
||||
* Management Stack based of Salt Stack in dom0 - [documentation](/doc/salt/)
|
||||
|
|
@ -64,4 +63,3 @@ for migrating of all of the user VMs.
|
|||
Alternatively you can [upgrade to R3.0
|
||||
using](/doc/releases/3.0/release-notes/#upgrading) first, then follow the
|
||||
instructions above. This will be time consuming process.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 17
|
|||
title: Qubes R3.1 Release Schedule
|
||||
---
|
||||
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 21
|
|||
title: Qubes R3.2 release notes
|
||||
---
|
||||
|
||||
|
||||
## New features since 3.1
|
||||
|
||||
* Management Stack extended to support in-VM configuration - [documentation](/doc/salt/)
|
||||
|
|
@ -60,4 +59,3 @@ for migrating of all of the user VMs.
|
|||
|
||||
Alternatively you can [upgrade to R3.1 using](/doc/releases/3.1/release-notes/#upgrading) first, then follow
|
||||
the instructions above. This will be time consuming process.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 22
|
|||
title: Qubes R3.2 Release Schedule
|
||||
---
|
||||
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 23
|
|||
title: Qubes R4.0 release notes
|
||||
---
|
||||
|
||||
|
||||
New features since 3.2
|
||||
----------------------
|
||||
|
||||
|
|
@ -106,4 +105,3 @@ There is no in-place upgrade path from earlier Qubes versions. The only
|
|||
supported option to upgrade to Qubes R4.0 is to install it from scratch and use
|
||||
[qubes backup and restore tools](/doc/backup-restore/) for migrating of all of the user VMs.
|
||||
We also provide [detailed instruction](/doc/upgrade-to-r4.0/) for this procedure.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 24
|
|||
title: Qubes R4.0 Release Schedule
|
||||
---
|
||||
|
||||
|
||||
This schedule is based on [Version Scheme](/doc/version-scheme/#release-schedule).
|
||||
|
||||
| Date | Stage |
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 13
|
|||
title: Release Notes
|
||||
---
|
||||
|
||||
|
||||
* [Qubes R1.0 release notes](/doc/releases/1.0/release-notes/)
|
||||
* [Qubes R2.0 release notes](/doc/releases/2.0/release-notes/)
|
||||
* [Qubes R3.0 release notes](/doc/releases/3.0/release-notes/)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 15
|
|||
title: Release Schedules
|
||||
---
|
||||
|
||||
|
||||
* [Qubes R3.0 release schedule](/doc/releases/3.0/schedule/)
|
||||
* [Qubes R3.1 release schedule](/doc/releases/3.1/schedule/)
|
||||
* [Qubes R3.2 release schedule](/doc/releases/3.2/schedule/)
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 14
|
|||
title: Release Checklist
|
||||
---
|
||||
|
||||
|
||||
*the checklist is probably unfinished*
|
||||
|
||||
On -rc1
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 151
|
|||
title: Version Scheme
|
||||
---
|
||||
|
||||
|
||||
Beginning with R3 release, we change (and formalise) the versioning scheme.
|
||||
From now on, it will be as follows.
|
||||
|
||||
|
|
@ -155,4 +154,3 @@ Check installed version
|
|||
|
||||
If you want to know which version you are running, for example to report
|
||||
an issue, you can either check in the Qubes Manager menu under About / Qubes OS or in the file /etc/qubes-release in dom0. For the latter you can use a command like `cat /etc/qubes-release` in a dom0 terminal.
|
||||
|
||||
|
|
|
|||
|
|
@ -274,4 +274,3 @@ In addition, there is a mechanism to prevent concurrent modifications of the pol
|
|||
`qrexec-client-vm`
|
||||
|
||||
<!-- vim: set ts=4 sts=4 sw=4 et : -->
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 43
|
|||
title: Dom0 Secure Updates
|
||||
---
|
||||
|
||||
|
||||
Reasons for Dom0 updates
|
||||
------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 39
|
|||
title: 'Qrexec: Qubes RPC Internals'
|
||||
---
|
||||
|
||||
|
||||
(*This page details the current implementation of qrexec (qrexec3).
|
||||
A [general introduction](/doc/qrexec/) to qrexec is also available.
|
||||
For the implementation of qrexec2, see [here](/doc/qrexec2/#qubes-rpc-internals).*)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 42
|
|||
title: '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.*
|
||||
|
||||
As of Qubes 4.1, qrexec allows implementing services not only as executable files, but also as Unix sockets.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 60
|
|||
title: Audio Virtualization
|
||||
---
|
||||
|
||||
|
||||
VMs on Qubes OS have access to virtualized audio through the PulseAudio module.
|
||||
It consists of two parts:
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 59
|
|||
title: Networking
|
||||
---
|
||||
|
||||
|
||||
## Overall description
|
||||
|
||||
In Qubes, the standard Xen networking is used, based on backend driver in the driver domain and frontend drivers in VMs. In order to eliminate layer 2 attacks originating from a compromised VM, routed networking is used instead of the default bridging of `vif` devices and NAT is applied at each network hop. The default *vif-route* script had some deficiencies (requires `eth0` device to be up, and sets some redundant iptables rules), therefore the custom *vif-route-qubes* script is used.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 55
|
|||
title: Security-critical Code
|
||||
---
|
||||
|
||||
|
||||
Below is a list of security-critical (i.e., trusted) code components in Qubes OS.
|
||||
A successful attack against any of these components could compromise the system's security.
|
||||
This code can be thought of as the Trusted Computing Base (TCB) of Qubes OS.
|
||||
|
|
@ -69,4 +68,3 @@ This means that we must trust at least some of the vendors that supply the code
|
|||
(We don't have to trust *all* of them, but we at least have to trust the few that provide the apps we use in the most critical domains.)
|
||||
In practice, we trust the software provided by the [Fedora Project](https://getfedora.org/).
|
||||
This software is signed by Fedora distribution keys, so it is also critical that the tools used in domains for software updates (`dnf` and `rpm`) are trustworthy.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 210
|
|||
title: 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 also provides features that make it easy and convenient to run these multiple domains, such as seamless GUI integration into one common desktop, secure clipboard copy and paste between domains, secure file transfer between domains, disposable VMs, and much more. Qubes also provides an advanced networking infrastructure that allows for the creation of multiple network VMs which isolate all the world-facing networking stacks and proxy VMs which can be used for advanced VPN configurations and tunneling over untrusted connections.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 57
|
|||
title: Storage Pools
|
||||
---
|
||||
|
||||
|
||||
Qubes OS R3.2 introduced the concept of storage drivers and pools. This feature
|
||||
was a first step towards a saner storage API, which is heavily rewritten in R4.
|
||||
See [here](https://dev.qubes-os.org/projects/core-admin/en/latest/qubes-storage.html)
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 58
|
|||
title: Template Implementation
|
||||
---
|
||||
|
||||
|
||||
Every VM has 4 block devices connected:
|
||||
|
||||
- **xvda** – base root device (/) – details described below
|
||||
|
|
|
|||
|
|
@ -114,4 +114,3 @@ The initial published version of this Code of Conduct was adapted from the
|
|||
[Contributor Covenant, version
|
||||
1.4](https://contributor-covenant.org/version/1/4) and the [Rust Code of
|
||||
Conduct](https://www.rust-lang.org/en-US/conduct.html).
|
||||
|
||||
|
|
|
|||
|
|
@ -58,4 +58,3 @@ time, like implementing a new feature, it's always good to contact us first,
|
|||
preferably via the [qubes-devel](/support/#qubes-devel) mailing list. Once
|
||||
we've worked out the details, we'll be grateful to [receive your
|
||||
patch](/doc/source-code/#how-to-send-patches).
|
||||
|
||||
|
|
|
|||
|
|
@ -694,4 +694,3 @@ If you need to support not-fully-updated systems, check for the existence of `/u
|
|||
Yes, Qubes natively supports automation via [Salt (SaltStack)](/doc/salt/).
|
||||
There is also the unofficial [ansible-qubes toolkit](https://github.com/Rudd-O/ansible-qubes).
|
||||
(**Warning:** Since this is an external project that has not been reviewed or endorsed by the Qubes team, [allowing it to manage dom0 may be a security risk](https://github.com/Qubes-Community/Contents/blob/master/docs/security/security-guidelines.md#dom0-precautions).)
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 123
|
|||
title: Screenshots
|
||||
---
|
||||
|
||||
|
||||
[](/attachment/doc/r4.0-xfce-desktop.png)
|
||||
|
||||
The default desktop environment is Xfce4.
|
||||
|
|
|
|||
|
|
@ -59,4 +59,3 @@ The raw data is available [here](https://tools.qubes-os.org/counter/stats.json).
|
|||
(This does not include any personally-identifying user data.)
|
||||
Please note that the format of this data is not documented and may change any time if the developers feel the need to include something else.
|
||||
The source code is available [here](https://github.com/woju/qubes-stats).
|
||||
|
||||
|
|
|
|||
|
|
@ -270,4 +270,3 @@ Qubes binaries :/
|
|||
implement multiple signature scheme for distributed binaries.
|
||||
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -87,4 +87,3 @@ about how to authenticate these keys.
|
|||
- [Marek Marczykowski-Górecki](/team/#marek-marczykowski-górecki)
|
||||
- [Simon Gaiser (aka HW42)](/team/#simon-gaiser-aka-hw42)
|
||||
- [Joanna Rutkowska](/team/#joanna-rutkowska) ([emeritus, canaries only](/news/2018/11/05/qubes-security-team-update/))
|
||||
|
||||
|
|
|
|||
|
|
@ -664,4 +664,3 @@ If your question is about GPG, please see the [GPG
|
|||
documentation](https://www.gnupg.org/documentation/). Still have question?
|
||||
Please see [Help, Support, Mailing Lists, and Forum](/support/) for places
|
||||
where you can ask!
|
||||
|
||||
|
|
|
|||
|
|
@ -40,4 +40,3 @@ or **No**.
|
|||
completeness, but they are excluded from the [Statistics](#statistics)
|
||||
section for the sake of accuracy.
|
||||
* All dates are in UTC.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 179
|
|||
title: AwesomeWM (window manager)
|
||||
---
|
||||
|
||||
|
||||
## Qubes-specific features
|
||||
|
||||
* support for the Qubes OS window colors
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 186
|
|||
title: How to Make Any File Persistent (bind-dirs)
|
||||
---
|
||||
|
||||
|
||||
## What are bind-dirs? ##
|
||||
|
||||
With [bind-dirs](https://github.com/QubesOS/qubes-core-agent-linux/blob/master/vm-systemd/bind-dirs.sh)
|
||||
|
|
@ -103,4 +102,3 @@ binds=( "${binds[@]/'/var/lib/tor'}" )
|
|||
## Discussion ##
|
||||
|
||||
[app qubes: make selected files and folders located in the root image persistent- review bind-dirs.sh](https://groups.google.com/forum/#!topic/qubes-devel/tcYQ4eV-XX4/discussion)
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 180
|
|||
title: Config Files
|
||||
---
|
||||
|
||||
|
||||
Qubes-specific VM config files
|
||||
------------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,6 @@ ref: 174
|
|||
title: Disposable Customization
|
||||
---
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
A [disposable](/doc/disposable/) can be based on any [app qube](/doc/glossary/#app-qube).
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 184
|
|||
title: GUI Configuration
|
||||
---
|
||||
|
||||
|
||||
## Video RAM adjustment for high-resolution displays
|
||||
|
||||
When a qube starts, a fixed amount of RAM is allocated to the graphics buffer called video RAM.
|
||||
|
|
|
|||
|
|
@ -246,4 +246,3 @@ sys-whonix.
|
|||
```
|
||||
Qubes VM Manager -> System -> Global Settings -> UpdateVM -> sys-whonix
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 183
|
|||
title: i3 (window manager)
|
||||
---
|
||||
|
||||
|
||||
i3 is part of the stable repository (as of Qubes R3.1) and can be installed by
|
||||
using the [dom0 update mechanism](/doc/how-to-install-software-in-dom0/). To install the i3
|
||||
window manager and the its Qubes specific configuration:
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 225
|
|||
title: Installing 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/)._
|
||||
|
||||
|
|
@ -55,4 +54,3 @@ sudo qubes-dom0-update --clean qvm-screenshot-tool
|
|||
```
|
||||
|
||||
Please see the package's README for specific installation and setup instructions.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 176
|
|||
title: KDE (desktop environment)
|
||||
---
|
||||
|
||||
|
||||
Installation
|
||||
------------
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 173
|
|||
title: Managing VM Kernels
|
||||
---
|
||||
|
||||
|
||||
By default, VMs kernels are provided by dom0.
|
||||
(See [here](/doc/how-to-install-software-in-dom0/#kernel-upgrade) for information about upgrading kernels in dom0.)
|
||||
This means that:
|
||||
|
|
@ -362,4 +361,3 @@ update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
|
|||
#### Troubleshooting
|
||||
|
||||
In case of problems, visit the [VM Troubleshooting guide](/doc/vm-troubleshooting/#vm-kernel-troubleshooting) to learn how to access the VM console, view logs and fix a VM kernel installation.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 175
|
|||
title: How to Mount a Qubes Partition from Another OS
|
||||
---
|
||||
|
||||
|
||||
When a Qubes OS install is unbootable or booting it is otherwise undesirable, this process allows for the recovery of files stored within the system.
|
||||
|
||||
These functions are manual and do not require any Qubes specific tools. All steps assume the default Qubes install with the following components:
|
||||
|
|
|
|||
|
|
@ -107,4 +107,3 @@ sudo lvresize --size 1024M /dev/qubes_dom0/vm-qube1-private
|
|||
```
|
||||
|
||||
If you have a SSD see [here](/doc/disk-trim) for information on using fstrim.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 178
|
|||
title: RPC Policies
|
||||
---
|
||||
|
||||
|
||||
This document explains the basics of RPC policies in Qubes.
|
||||
For more information, see [Qrexec: command execution in VMs](/doc/qrexec3/).
|
||||
|
||||
|
|
@ -67,4 +66,3 @@ Further details about how this system works can be found in [Qrexec: command exe
|
|||
|
||||
(***Note**: the `$` character is deprecated in qrexec keywords -- please use `@` instead (e.g. `@anyvm`).
|
||||
For more information, see the bulletin [here](https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-038-2018.txt).*)
|
||||
|
||||
|
|
|
|||
|
|
@ -608,4 +608,3 @@ install template and shutdown updateVM:
|
|||
- [Jinja templates](http://jinja.pocoo.org/)
|
||||
- [Qubes specific modules](https://github.com/QubesOS/qubes-mgmt-salt-dom0-qvm/blob/master/README.rst)
|
||||
- [Formulas for default Qubes VMs](https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/tree/master/qvm)
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 187
|
|||
title: Secondary Storage
|
||||
---
|
||||
|
||||
|
||||
Suppose you have a fast but small primary SSD and a large but slow secondary HDD.
|
||||
You want to store a subset of your app qubes on the HDD.
|
||||
|
||||
|
|
@ -112,4 +111,3 @@ By default VMs will be created on the main Qubes disk (i.e. a small SSD), to cre
|
|||
```
|
||||
qvm-create -P poolhd0_qubes --label red unstrusted-hdd
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 181
|
|||
title: 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.
|
||||
|
||||
**Caution:** If you want to use a USB-keyboard, please beware of the possibility to lock yourself out! To avoid this problem [enable your keyboard for login](#enable-a-usb-keyboard-for-login)!
|
||||
|
|
@ -201,4 +200,3 @@ The procedure to hide all USB controllers from dom0 is as follows:
|
|||
5. If `rd.qubes.hide_all_usb` appears anywhere in those lines, remove it.
|
||||
6. Save and close the file.
|
||||
7. Reboot.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 206
|
|||
title: Volume Backup and Revert
|
||||
---
|
||||
|
||||
|
||||
With Qubes, it is possible to revert one of a VM's storage volumes to a previous
|
||||
state using the automatic snapshot that is normally saved every time a VM is
|
||||
shutdown. (Note that this is a different, lower level activity than the
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 129
|
|||
title: Windows VMs
|
||||
---
|
||||
|
||||
|
||||
Like any other unmodified OSes, Windows can be installed in Qubes as an [HVM](/doc/standalone-and-hvm/) domain.
|
||||
|
||||
Qubes Windows Tools are then usually installed to provide integration with the rest of the Qubes system; they also include Xen's paravirtualized (PV) drivers to increase performance compared to qemu emulated devices. Alternatively, only Xen's PV drivers can be installed if integration with Qubes isn't required or if the tools aren't supported on a give version of Windows. In the latter case, one would have to [enable inter-VM networking](/doc/firewall/#enabling-networking-between-two-qubes) to be able to exchange files with HVMs.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ advanced: true
|
|||
title: Custom Installation
|
||||
---
|
||||
|
||||
|
||||
In the present context, "custom installation" refers to things like manual partitioning, setting up LVM and RAID, and manual LUKS encryption configuration.
|
||||
|
||||
## Installer Defaults
|
||||
|
|
@ -161,4 +160,3 @@ Boot into the Qubes installer, then press `ctrl`+`alt`+`F2` to get a virtual con
|
|||
Repeat the process for `sda1` and `qubes_dom0-swap`. Those should be assigned to `/boot` and `swap` respectively.
|
||||
The default file systems are ext4 for `/boot` and `/`, and swap for `swap`.
|
||||
When you are finished, the Unknown list should go away, and all three mount points should be assigned. Proceed normally with the installation from there.
|
||||
|
||||
|
|
|
|||
|
|
@ -25,4 +25,3 @@ helpful in streamlining the process.
|
|||
every 6-8 hours is fine.
|
||||
* For technical accommodations, please contact [Wojtek](/team/#wojtek-porczyk) or [Marek](/team/#marek-marczykowski-górecki).
|
||||
* For website updates and fixes, please contact [Andrew](/team/#andrew-david-wong).
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 149
|
|||
title: Installation security
|
||||
---
|
||||
|
||||
|
||||
There are several security matters to consider before and during the Qubes installation process.
|
||||
|
||||
## Trusting your hardware
|
||||
|
|
@ -77,4 +76,3 @@ Cons:
|
|||
(Option 3 violates the Qubes security model since it entails transferring an untrusted ISO to dom0 in order to burn it to disc, which leaves only the other two options.)
|
||||
|
||||
Considering the pros and cons of each, perhaps a USB drive with non-rewritable (or at least cryptographically-signed) firmware and a physical write-protect switch might be the best option.
|
||||
|
||||
|
|
|
|||
|
|
@ -472,4 +472,3 @@ the other [How-to Guides](/doc/#how-to-guides), and learn about
|
|||
* Please do **not** email individual members of the Qubes team with questions
|
||||
about installation or other problems. Instead, please see [Help, Support,
|
||||
Mailing Lists, and Forum](/support/) for appropriate places to ask questions.
|
||||
|
||||
|
|
|
|||
|
|
@ -129,4 +129,3 @@ templates within a month of their respective releases. To be precise:
|
|||
|
||||
We aim to announce both types of events one month in advance in order to remind
|
||||
users to upgrade.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 156
|
|||
title: Upgrading to R2
|
||||
---
|
||||
|
||||
|
||||
Current Qubes R2 Beta 3 (R2B3) systems can be upgraded in-place to the latest R2 (R2) release by following the procedure below.
|
||||
|
||||
**Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users back up the system by using the built-in [backup tool](/doc/backup-restore/).**
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 163
|
|||
title: Upgrading to R2B1
|
||||
---
|
||||
|
||||
|
||||
**Note: Qubes R2 Beta 1 is no longer supported! Please install or upgrade to a newer Qubes R2.**
|
||||
|
||||
**Note: This page is kept for historical reasons only! Do not follow the instructions below'''**
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 160
|
|||
title: Upgrading to R2B2
|
||||
---
|
||||
|
||||
|
||||
Existing users of Qubes R1 (but not R1 betas!) can upgrade their systems to the latest R2 beta release by following the procedure below. As usual, it is advisable to backup the system before proceeding with the upgrade. While it is possible to upgrade the system **it is strongly recommended to reinstall it**. You will preserve all your data and settings thanks to [backup and restore tools](/doc/backup-restore/).
|
||||
|
||||
Upgrade all Template and Standalone VM(s)
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 157
|
|||
title: Upgrading to R2B3
|
||||
---
|
||||
|
||||
|
||||
Current Qubes R2 Beta 2 (R2B2) systems can be upgraded in-place to the latest R2 Beta 3 (R2B3) release by following the procedure below. However, upgrading in-place is riskier than performing a clean installation, since there are more things which can go wrong. For this reason, **we strongly recommended that users perform a [clean installation](/doc/installation-guide/) of Qubes R2 Beta 3**.
|
||||
|
||||
**Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users back up the system by using the built-in [backup tool](/doc/backup-restore/).**
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 159
|
|||
title: Upgrading 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!**
|
||||
|
||||
Current Qubes R3.0 (R3.0) systems can be upgraded in-place to the latest R3.0 by following the procedure below. However, upgrading in-place is riskier than performing a clean installation, since there are more things which can go wrong. For this reason, **we strongly recommended that users perform a [clean installation](/doc/installation-guide/) of Qubes R3.0**.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 155
|
|||
title: Upgrading to R3.1
|
||||
---
|
||||
|
||||
|
||||
**Before attempting either an in-place upgrade or a clean installation, we
|
||||
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 161
|
|||
title: Upgrading to R3.2
|
||||
---
|
||||
|
||||
|
||||
**Before attempting either an in-place upgrade or a clean installation, we
|
||||
strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 162
|
|||
title: Upgrading to R4.0
|
||||
---
|
||||
|
||||
|
||||
**Before attempting either an in-place upgrade or a clean installation, we strongly recommend that users [back up their systems](/doc/backup-restore/).**
|
||||
|
||||
Current Qubes R3.2 systems cannot be upgraded in-place to R4.0.
|
||||
|
|
@ -116,4 +115,3 @@ Please see [Supported Versions](/doc/supported-versions/) for information on sup
|
|||
* [Upgrading Fedora templates](/doc/templates/fedora/#upgrading)
|
||||
* [Upgrading Debian templates](/doc/templates/debian/#upgrading)
|
||||
* [Updating Whonix templates](https://www.whonix.org/wiki/Qubes/Update)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 158
|
|||
title: Upgrade Guides
|
||||
---
|
||||
|
||||
|
||||
These guides are for upgrading from one version of Qubes to another.
|
||||
If you're just looking to update your system while staying on the same version,
|
||||
see [How to Update](/doc/how-to-update/).
|
||||
|
|
@ -19,4 +18,3 @@ see [How to Update](/doc/how-to-update/).
|
|||
* [Upgrading from R3.0 to R3.1](/doc/upgrade-to-r3.1/)
|
||||
* [Upgrading from R3.1 to R3.2](/doc/upgrade-to-r3.2/)
|
||||
* [Upgrading from R3.2 to R4.0](/doc/upgrade-to-r4.0/)
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 144
|
|||
title: 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.
|
||||
We aim for these vendors to be as diverse as possible in terms of geography, cost, and availability.
|
||||
|
||||
|
|
@ -105,4 +104,3 @@ This could be done by consulting the [Hardware Compatibility List](/hcl/) or try
|
|||
While we are willing to troubleshoot simple issues, we will need to charge a consulting fee for more in-depth work.
|
||||
|
||||
If you are interested in having your hardware certified, please [contact us](mailto:business@qubes-os.org).
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ ref: 145
|
|||
title: Hardware Testing
|
||||
---
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
|
@ -38,4 +37,3 @@ If anyone is willing to lend or donate these models to us, we would be happy to
|
|||
- Dell Latitude with Intel 8th Gen CPU and integrated graphics
|
||||
|
||||
Note: The Lenovo X and T series are similar enough to assume similar compatibility of the matching model from the other series.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 146
|
|||
title: Hardware Compatibility List (HCL)
|
||||
---
|
||||
|
||||
|
||||
The [HCL](/hcl) is a compilation of reports generated and submitted by users across various Qubes versions about their hardware's compatibility with Qubes.
|
||||
|
||||
**Note:**
|
||||
|
|
@ -46,4 +45,3 @@ Please consider sending the **HCL Support Files** `.cpio.gz` file as well. To ge
|
|||
|
||||
**Please note:**
|
||||
The **HCL Support Files** may contain numerous hardware details, including serial numbers. If, for privacy or security reasons, you do not wish to make this information public, please **do not** send the `.cpio.gz` file to the public mailing list.
|
||||
|
||||
|
|
|
|||
|
|
@ -84,4 +84,3 @@ title: System Requirements
|
|||
notebook](https://groups.google.com/d/msg/qubes-users/Sz0Nuhi4N0o/ZtpJdoc0OY8J).
|
||||
- You can check whether an Intel processor has VT-x and VT-d on
|
||||
[ark.intel.com](https://ark.intel.com/content/www/us/en/ark.html#@Processors).
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 207
|
|||
title: Emergency Backup Recovery (v2)
|
||||
---
|
||||
|
||||
|
||||
This page describes how to perform emergency restore of backup created on Qubes
|
||||
R2 Beta3 or earlier (which uses backup format 2).
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 201
|
|||
title: Emergency Backup Recovery (v3)
|
||||
---
|
||||
|
||||
|
||||
This page describes how to perform an emergency restore of a backup created on
|
||||
Qubes R2 or later (which uses backup format version 3).
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 192
|
|||
title: Emergency Backup Recovery (v4)
|
||||
---
|
||||
|
||||
|
||||
This page describes how to perform an emergency restore of a backup created on
|
||||
Qubes R4.X (which uses backup format version 4).
|
||||
|
||||
|
|
@ -179,4 +178,3 @@ Emergency Recovery Instructions
|
|||
repository:
|
||||
|
||||
https://github.com/QubesOS/qubes-doc.git
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 191
|
|||
title: How to Copy and Move Files
|
||||
---
|
||||
|
||||
|
||||
*This page is about copying and moving files.
|
||||
If you wish to simply copy and paste text, that can be done more easily using the inter-qube clipboard.
|
||||
See [copying and pasting text between qubes](/doc/how-to-copy-and-paste-text/).
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 196
|
|||
title: How to Copy and Paste Text
|
||||
---
|
||||
|
||||
|
||||
*This page is about copying and pasting plain text.
|
||||
If you wish to copy more complex data, such as rich text or images, see [copying and moving files between qubes](/doc/how-to-copy-and-move-files/).
|
||||
For dom0, see [copying from (and to) dom0](/doc/how-to-copy-from-dom0/).*
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 198
|
|||
title: How to Copy from Dom0
|
||||
---
|
||||
|
||||
|
||||
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/how-to-copy-and-paste-text/) and [copying and moving files between qubes](/doc/how-to-copy-and-move-files/).
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 205
|
|||
title: How to Enter Fullscreen Mode
|
||||
---
|
||||
|
||||
|
||||
What is fullscreen mode?
|
||||
-------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 193
|
|||
title: How to Use Block Storage Devices
|
||||
---
|
||||
|
||||
|
||||
*This page is part of [device handling in qubes](/doc/how-to-use-devices/).*
|
||||
|
||||
If you don't know what a "block device" is, just think of it as a fancy way to say "something that stores data".
|
||||
|
|
@ -255,4 +254,3 @@ qvm-block a work sys-usb:sda1 -o devtype=cdrom
|
|||
```
|
||||
|
||||
This option accepts `cdrom` and `disk`, default is `disk`.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 188
|
|||
title: How to Use Devices
|
||||
---
|
||||
|
||||
|
||||
This is an overview of device handling in Qubes OS.
|
||||
For specific devices ([block](/doc/how-to-use-block-storage-devices/), [USB](/doc/how-to-use-usb-devices/) and [PCI](/doc/how-to-use-pci-devices/) devices), please visit their respective pages.
|
||||
|
||||
|
|
@ -157,4 +156,3 @@ If no specific `sourceVM:deviceID` combination is given, *all devices of that DE
|
|||
|
||||
**SYNOPSIS**
|
||||
`qvm-device DEVICE_CLASS {detach|dt|d} targetVM [sourceVM:deviceID]`
|
||||
|
||||
|
|
|
|||
|
|
@ -188,4 +188,3 @@ More information about RPC policies for disposables can be found [here](/doc/qre
|
|||
You can change the template used to generate the disposables, and change settings used in the disposable savefile.
|
||||
These changes will be reflected in every new disposable based on that template.
|
||||
Full instructions can be found [here](/doc/disposable-customization/).
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 204
|
|||
title: How to Use Optical Discs
|
||||
---
|
||||
|
||||
|
||||
Passthrough reading and recording (a.k.a., "burning") are not supported by Xen.
|
||||
Currently, the only options for reading and recording optical discs (e.g., CDs, DVDs, BRDs) in Qubes are:
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ ref: 197
|
|||
title: How to Use PCI Devices
|
||||
---
|
||||
|
||||
|
||||
*This page is part of [device handling in qubes](/doc/how-to-use-devices/).*
|
||||
|
||||
**Warning:** Only dom0 exposes PCI devices.
|
||||
|
|
@ -142,4 +141,3 @@ or
|
|||
```
|
||||
|
||||
It is **strongly discouraged to reattach PCI devices to dom0**, especially if they don't support resetting!
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 195
|
|||
title: How to Use USB Devices
|
||||
---
|
||||
|
||||
|
||||
*This page is part of [device handling in qubes](/doc/how-to-use-devices/).*
|
||||
|
||||
If you are looking to handle USB *storage* devices (thumbdrives or USB-drives), please have a look at the [block device](/doc/how-to-use-block-storage-devices/) page.
|
||||
|
|
@ -155,4 +154,3 @@ Now you see the path and the text between `/pci0000:00/0000:` and `/usb3` i.e. `
|
|||
For example, On R 4.0 the command would look something like
|
||||
|
||||
`qvm-pci attach --persistent personal dom0:00_1a.0`
|
||||
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue