mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
Change URIs from CamelCase to lowercase-hyphen-separated
This commit is contained in:
Axon
parent
bb5fb46527
commit
f3ee78f223
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: GettingStarted
|
||||
permalink: /doc/GettingStarted/
|
||||
redirect_from: /wiki/GettingStarted/
|
||||
permalink: /en/doc/getting-started/
|
||||
redirect_from:
|
||||
- /doc/GettingStarted/
|
||||
- /wiki/GettingStarted/
|
||||
---
|
||||
|
||||
Getting Started with Qubes OS
|
||||
@ -34,7 +36,7 @@ Qubes VM Manager and Command Line Tools
|
||||
|
||||
All aspects of the Qubes system can be controlled using command line tools run under a dom0 console. To open a console window in dom0, either go to Start-\>System Tools-\>Konsole or press Alt-F2 and type `konsole`.
|
||||
|
||||
Various command line tools are described as part of this guide, and the whole reference can be found [here](/doc/DomZeroTools/).
|
||||
Various command line tools are described as part of this guide, and the whole reference can be found [here](/en/doc/dom0-tools/).
|
||||
|
||||
|
||||
|
||||
@ -77,7 +79,7 @@ How Many Domains Do I Need?
|
||||
|
||||
That's a great question, but there's no one-size-fits-all answer. It depends on the structure of your digital life, and this is at least a little different for everyone. If you plan on using your system for work, then it also depends on what kind of job you do.
|
||||
|
||||
It's a good idea to start out with the three domains created automatically by the installer: work, personal, and untrusted. Then, if and when you start to feel that some activity just doesn't fit into any of your existing domains, you can easily create a new domain for it. You'll also be able to easily copy any files you need to the newly created domain, as explained [here](/doc/CopyingFiles/).
|
||||
It's a good idea to start out with the three domains created automatically by the installer: work, personal, and untrusted. Then, if and when you start to feel that some activity just doesn't fit into any of your existing domains, you can easily create a new domain for it. You'll also be able to easily copy any files you need to the newly created domain, as explained [here](/en/doc/copying-files/).
|
||||
|
||||
More paranoid people might find it worthwhile to read [this article](http://theinvisiblethings.blogspot.com/2011/03/partitioning-my-digital-life-into.html), which describes how one of the Qubes authors partitions her digital life into security domains.
|
||||
|
||||
@ -114,4 +116,4 @@ In order for the changes to take effect, restart the AppVM(s).
|
||||
|
||||
* * * * *
|
||||
|
||||
Now that you're familiar with the basics, feel free to have a look at other [Qubes User Guides](/doc/UserDoc/).
|
||||
Now that you're familiar with the basics, feel free to have a look at other [Qubes User Guides](/en/doc/).
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesLists
|
||||
permalink: /doc/QubesLists/
|
||||
redirect_from: /wiki/QubesLists/
|
||||
title: MailingLists
|
||||
permalink: /en/doc/mailing-lists/
|
||||
redirect_from:
|
||||
- /doc/QubesLists/
|
||||
- /wiki/QubesLists/
|
||||
---
|
||||
|
||||
Qubes Mailing Lists
|
||||
@ -45,8 +47,8 @@ This list is for helping users solve various daily problems with Qubes OS. Examp
|
||||
Please try searching both the Qubes website and the archives of the mailing lists before sending a question. In addition, please make sure that you have read and understood the following basic documentation prior to posting to the list:
|
||||
|
||||
- [Installation guides, System Requirements, and HCL](/doc/QubesDownloads/) \<-- for problems related to Qubes OS installation
|
||||
- [Qubes User FAQ](/doc/UserFaq/)
|
||||
- [Qubes User Guides](/doc/UserDoc/) \<-- for questions about how to use Qubes OS
|
||||
- [Qubes User FAQ](/en/doc/user-faq/)
|
||||
- [Qubes User Guides](/en/doc/) \<-- for questions about how to use Qubes OS
|
||||
|
||||
### How to Subscribe and Post
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UserFaq
|
||||
permalink: /doc/UserFaq/
|
||||
redirect_from: /wiki/UserFaq/
|
||||
permalink: /en/doc/user-faq/
|
||||
redirect_from:
|
||||
- /doc/UserFaq/
|
||||
- /wiki/UserFaq/
|
||||
---
|
||||
|
||||
Qubes Users' FAQ
|
||||
@ -133,7 +135,7 @@ Create an issue in [qubes-issues](https://github.com/QubesOS/qubes-issues/issues
|
||||
Installation & Hardware Compatibility
|
||||
-------------------------------------
|
||||
|
||||
(See also: [System Requirements](/doc/SystemRequirements/) and [Hardware Compatibility List](/hcl/).)
|
||||
(See also: [System Requirements](/en/doc/system-requirements/) and [Hardware Compatibility List](/hcl/).)
|
||||
|
||||
### How much disk space does each AppVM require?
|
||||
|
||||
@ -186,7 +188,7 @@ In your TemplateVMs, open a terminal and run `sudo yum upgrade`.
|
||||
|
||||
### How do I run a Windows HVM in non-seamless mode (i.e., as a single window)?
|
||||
|
||||
Enable "debug mode" in the AppVM's settings, either by checking the box labelled "Run in debug mode" in the Qubes VM Manager AppVM settings menu or by running the [qvm-prefs command](/doc/Dom0Tools/QvmPrefs/).)
|
||||
Enable "debug mode" in the AppVM's settings, either by checking the box labelled "Run in debug mode" in the Qubes VM Manager AppVM settings menu or by running the [qvm-prefs command](/en/doc/dom0-tools/qvm-prefs/).)
|
||||
|
||||
|
||||
### I created a usbVM and assigned usb controllers to it. Now the usbVM wont boot.
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Introduction
|
||||
permalink: /intro/
|
||||
permalink: /en/intro/
|
||||
redirect_from:
|
||||
- /intro/
|
||||
- "/doc/SimpleIntro/"
|
||||
- "/wiki/SimpleIntro/"
|
||||
---
|
||||
@ -72,8 +73,8 @@ More information
|
||||
|
||||
This page is just a brief sketch of what Qubes is all about, and many technical details have been omitted here for the sake of presentation.
|
||||
|
||||
- If you're a current or potential Qubes user, you may want to check out the [documentation](/doc/) and the [FAQ](/doc/UserFaq/).
|
||||
- If you're a developer, there's dedicated [documentation](/doc/SystemDoc/) and an [FAQ](/doc/DevelFaq/) just for you.
|
||||
- If you're a current or potential Qubes user, you may want to check out the [documentation](/en/doc/) and the [FAQ](/en/doc/user-faq/).
|
||||
- If you're a developer, there's dedicated [documentation](/en/doc/system-doc/) and an [FAQ](/en/doc/devel-faq/) just for you.
|
||||
- Ready to give Qubes a try? Head on over to the [downloads page](/downloads/).
|
||||
- Once you've installed Qubes, here's a guide on [getting started](/doc/GettingStarted/).
|
||||
- Once you've installed Qubes, here's a guide on [getting started](/en/doc/getting-started/).
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Emergency Backup Recovery - format version 2
|
||||
permalink: /doc/BackupEmergencyRestoreV2/
|
||||
permalink: /en/doc/backup-emergency-restore-v2/
|
||||
redirect_from: /doc/BackupEmergencyRestoreV2/
|
||||
---
|
||||
|
||||
Emergency Backup Recovery without Qubes - format version 2
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Emergency Backup Recovery - format version 3
|
||||
permalink: /doc/BackupEmergencyRestoreV3/
|
||||
permalink: /en/doc/backup-emergency-restore-v3/
|
||||
redirect_from: /doc/BackupEmergencyRestoreV3/
|
||||
---
|
||||
|
||||
Emergency Backup Recovery without Qubes - format version 3
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: BackupRestore
|
||||
permalink: /doc/BackupRestore/
|
||||
redirect_from: /wiki/BackupRestore/
|
||||
permalink: /en/doc/backup-restore/
|
||||
redirect_from:
|
||||
- /doc/BackupRestore/
|
||||
- /wiki/BackupRestore/
|
||||
---
|
||||
|
||||
Qubes Backup, Restoration, and Migration
|
||||
@ -17,7 +19,7 @@ Qubes Backup, Restoration, and Migration
|
||||
|
||||
With Qubes, it's easy to back up and restore your whole system, as well as to migrate between two physical machines.
|
||||
|
||||
As of Qubes R2B3, these functions are integrated into the Qubes VM Manager GUI. There are also two command-line tools available which perform the same functions: [qvm-backup](/doc/Dom0Tools/QvmBackup/) and [qvm-backup-restore](/doc/Dom0Tools/QvmBackupRestore/).
|
||||
As of Qubes R2B3, these functions are integrated into the Qubes VM Manager GUI. There are also two command-line tools available which perform the same functions: [qvm-backup](/en/doc/dom0-tools/qvm-backup/) and [qvm-backup-restore](/en/doc/dom0-tools/qvm-backup-restore/).
|
||||
|
||||
Creating a Backup
|
||||
-----------------
|
||||
@ -32,7 +34,7 @@ Creating a Backup
|
||||
|
||||
1. Select the destination for the backup:
|
||||
|
||||
- If you wish to send your backup to a [USB mass storage device](/doc/StickMounting/), select the device in the dropdown box next to **Device** (feature removed in R3, select appropriate **Target AppVM** and mount the stick with one click in file selection dialog).
|
||||
- If you wish to send your backup to a [USB mass storage device](/en/doc/stick-mounting/), select the device in the dropdown box next to **Device** (feature removed in R3, select appropriate **Target AppVM** and mount the stick with one click in file selection dialog).
|
||||
- If you wish to send your backup to a (currently running) AppVM, select the AppVM in the dropdown box next to **Target AppVM**.
|
||||
|
||||
You must also specify a directory on the device or in the AppVM, or a command to be executed in the AppVM as a destination for your backup. For example, if you wish to send your backup to the `~/backups` folder in the target AppVM, you would simply type `backups` in this field. This destination directory must already exist. If it does not exist, you must create it manually prior to backing up.
|
||||
@ -54,7 +56,7 @@ Restoring from a Backup
|
||||
|
||||
1. Select the source location of the backup to be restored:
|
||||
|
||||
- If your backup is located on a [USB mass storage device](/doc/StickMounting/), select the device in the dropdown box next to **Device**.
|
||||
- If your backup is located on a [USB mass storage device](/en/doc/stick-mounting/), select the device in the dropdown box next to **Device**.
|
||||
- If your backup is located in a (currently running) AppVM, select the AppVM in the dropdown box next to **AppVM**.
|
||||
|
||||
You must also specify the directory in which the backup resides (or a command to be executed in an AppVM). If you followed the instructions in the previous section, "Creating a Backup," then your backup is most likely in the location you chose as the destination in step 3. For example, if you had chosen the `~/backups` directory of an AppVM as your destination in step 3, you would now select the same AppVM and again type `backups` into the **Backup directory** field.
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: CopyPaste
|
||||
permalink: /doc/CopyPaste/
|
||||
redirect_from: /wiki/CopyPaste/
|
||||
permalink: /en/doc/copy-paste/
|
||||
redirect_from:
|
||||
- /doc/CopyPaste/
|
||||
- /wiki/CopyPaste/
|
||||
---
|
||||
|
||||
Copy and Paste between domains
|
||||
@ -44,7 +46,7 @@ You may now paste the log contents to any VM as you normally would (i.e., Ctrl-S
|
||||
|
||||
For data other than logs, there are two options:
|
||||
|
||||
1. [Copy it as a file.](/doc/CopyToDomZero/)
|
||||
1. [Copy it as a file.](/en/doc/copy-to-dom0/)
|
||||
2. Paste the data to `/var/run/qubes/qubes-clipboard.bin`, then write "dom0" to `/var/run/qubes/qubes-clipboard.bin.source`. Then use Ctrl-Shift-V to paste the data to the desired VM.
|
||||
|
||||
Clipboard automatic policy enforcement
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: CopyToDomZero
|
||||
permalink: /doc/CopyToDomZero/
|
||||
redirect_from: /wiki/CopyToDomZero/
|
||||
title: CopyToDom0
|
||||
permalink: /en/doc/copy-to-dom0/
|
||||
redirect_from:
|
||||
- /doc/CopyToDomZero/
|
||||
- /wiki/CopyToDomZero/
|
||||
---
|
||||
|
||||
Copying files to between VMs and Dom0
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: CopyingFiles
|
||||
permalink: /doc/CopyingFiles/
|
||||
redirect_from: /wiki/CopyingFiles/
|
||||
permalink: /en/doc/copying-files/
|
||||
redirect_from:
|
||||
- /doc/CopyingFiles/
|
||||
- /wiki/CopyingFiles/
|
||||
---
|
||||
|
||||
Copying files between domains
|
||||
@ -26,7 +28,7 @@ GUI
|
||||
CLI
|
||||
---
|
||||
|
||||
[qvm-copy-to-vm](/doc/VmTools/QvmCopyToVm/)
|
||||
[qvm-copy-to-vm](/en/doc/vm-tools/qvm-copy-to-vm/)
|
||||
|
||||
On inter-domain file copy security
|
||||
----------------------------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DisposableVMs
|
||||
permalink: /doc/DisposableVms/
|
||||
redirect_from: /wiki/DisposableVMs/
|
||||
permalink: /en/doc/dispvm/
|
||||
redirect_from:
|
||||
- /doc/DisposableVms/
|
||||
- /wiki/DisposableVMs/
|
||||
---
|
||||
|
||||
Disposable VMs (DispVMs)
|
||||
@ -71,7 +73,7 @@ Customizing Disposable VMs
|
||||
---------------------------------------------------------
|
||||
|
||||
You can change the template used to generate the Disposable VM, and change settings used in the Disposable VM savefile. These changes will be reflected in every new Disposable VM.
|
||||
Full instructions are [here](/doc/UserDoc/DispVMCustomization/)
|
||||
Full instructions are [here](/en/doc/disp-vm-customization/)
|
||||
|
||||
|
||||
Disposable VMs and Local Forensics
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: FullScreenMode
|
||||
permalink: /doc/FullScreenMode/
|
||||
redirect_from: /wiki/FullScreenMode/
|
||||
permalink: /en/doc/full-screen-mode/
|
||||
redirect_from:
|
||||
- /doc/FullScreenMode/
|
||||
- /wiki/FullScreenMode/
|
||||
---
|
||||
|
||||
Enabling Full Screen Mode for select VMs
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ManagingAppVmShortcuts
|
||||
permalink: /doc/ManagingAppVmShortcuts/
|
||||
redirect_from: /wiki/ManagingAppVmShortcuts/
|
||||
permalink: /en/doc/managing-appvm-shortcuts/
|
||||
redirect_from:
|
||||
- /doc/ManagingAppVmShortcuts/
|
||||
- /wiki/ManagingAppVmShortcuts/
|
||||
---
|
||||
|
||||
Managing shortcuts to applications in AppVMs
|
||||
@ -29,6 +31,6 @@ List of installed applications for each AppVM is stored in its template's `/var/
|
||||
|
||||
Actual command lines for the menu shortcuts involve `qvm-run` command which starts a process in another domain. Example: `qvm-run -q --tray -a w7s 'cmd.exe /c "C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\Accessories\\Calculator.lnk"'` or `qvm-run -q --tray -a untrusted 'firefox %u'`
|
||||
|
||||
`qvm-sync-appmenus` works by invoking *GetAppMenus* [Qubes service](/doc/Qrexec/) in the target domain. This service enumerates installed applications and sends formatted info back to the dom0 script (`/usr/libexec/qubes-appmenus/qubes-receive-appmenus`) which creates .desktop files in the AppVM/TemplateVM directory.
|
||||
`qvm-sync-appmenus` works by invoking *GetAppMenus* [Qubes service](/en/doc/qrexec/) in the target domain. This service enumerates installed applications and sends formatted info back to the dom0 script (`/usr/libexec/qubes-appmenus/qubes-receive-appmenus`) which creates .desktop files in the AppVM/TemplateVM directory.
|
||||
|
||||
For Linux VMs the service script is in `/etc/qubes-rpc/qubes.GetAppMenus`. In Windows it's a PowerShell script located in `c:\Program Files\Invisible Things Lab\Qubes OS Windows Tools\qubes-rpc-services\get-appmenus.ps1` by default.
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SoftwareUpdateDom0
|
||||
permalink: /doc/SoftwareUpdateDom0/
|
||||
redirect_from: /wiki/SoftwareUpdateDom0/
|
||||
permalink: /en/doc/software-update-dom0/
|
||||
redirect_from:
|
||||
- /doc/SoftwareUpdateDom0/
|
||||
- /wiki/SoftwareUpdateDom0/
|
||||
---
|
||||
|
||||
Updating software in dom0
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SoftwareUpdateVM
|
||||
permalink: /doc/SoftwareUpdateVM/
|
||||
redirect_from: /wiki/SoftwareUpdateVM/
|
||||
permalink: /en/doc/software-update-vm/
|
||||
redirect_from:
|
||||
- /doc/SoftwareUpdateVM/
|
||||
- /wiki/SoftwareUpdateVM/
|
||||
---
|
||||
|
||||
Installing and updating software in VMs
|
||||
@ -39,7 +41,7 @@ As the template VM is used for creating filesystems for other AppVMs, where you
|
||||
|
||||
There are several ways to deal with this problem:
|
||||
|
||||
- Only install packages from trusted sources -- e.g. from the pre-configured Fedora repositories. All those packages are signed by Fedora, and as we expect that at least the package's installation scripts are not malicious. This is enforced by default (at the [firewall VM level](/doc/QubesFirewall/)), by not allowing any networking connectivity in the default template VM, except for access to the Fedora repos.
|
||||
- Only install packages from trusted sources -- e.g. from the pre-configured Fedora repositories. All those packages are signed by Fedora, and as we expect that at least the package's installation scripts are not malicious. This is enforced by default (at the [firewall VM level](/en/doc/qubes-firewall/)), by not allowing any networking connectivity in the default template VM, except for access to the Fedora repos.
|
||||
|
||||
- Use *standalone VMs* (see below) for installation of untrusted software packages.
|
||||
|
||||
@ -49,7 +51,7 @@ Some popular questions:
|
||||
|
||||
- So, why should we actually trust Fedora repos -- it also contains large amount of 3rd party software that might buggy, right?
|
||||
|
||||
As long as template's compromise is considered, it doesn't really matter whether /usr/bin/firefox is buggy and can be exploited, or not. What matters is whether its *installation* scripts (such as %post in the rpm.spec) are benign or not. Template VM should be used only for installation of packages, and nothing more, so it should never get a chance to actually run the /usr/bin/firefox and got infected from it, in case it was compromised. Also, some of your more trusted AppVMs, would have networking restrictions enforced by the [firewall VM](/doc/QubesFirewall/), and again they should not fear this proverbial /usr/bin/firefox being potentially buggy and easy to compromise.
|
||||
As long as template's compromise is considered, it doesn't really matter whether /usr/bin/firefox is buggy and can be exploited, or not. What matters is whether its *installation* scripts (such as %post in the rpm.spec) are benign or not. Template VM should be used only for installation of packages, and nothing more, so it should never get a chance to actually run the /usr/bin/firefox and got infected from it, in case it was compromised. Also, some of your more trusted AppVMs, would have networking restrictions enforced by the [firewall VM](/en/doc/qubes-firewall/), and again they should not fear this proverbial /usr/bin/firefox being potentially buggy and easy to compromise.
|
||||
|
||||
- But why trusting Fedora?
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: StickMounting
|
||||
permalink: /doc/StickMounting/
|
||||
redirect_from: /wiki/StickMounting/
|
||||
permalink: /en/doc/stick-mounting/
|
||||
redirect_from:
|
||||
- /doc/StickMounting/
|
||||
- /wiki/StickMounting/
|
||||
---
|
||||
|
||||
How to Mount USB Sticks to AppVMs
|
||||
@ -10,7 +12,7 @@ How to Mount USB Sticks to AppVMs
|
||||
|
||||
(**Note:** In the present context, the term "USB stick" denotes any [USB mass storage device](https://en.wikipedia.org/wiki/USB_mass_storage_device_class). In addition to smaller flash memory sticks, this includes things like USB external hard drives.)
|
||||
|
||||
Qubes supports the ability to attach a USB stick (or just one or more of its partitions) to any AppVM easily, no matter which VM actually handles the USB controller. (The USB controller may be assigned on the **Devices** tab of an AppVM's settings page in Qubes VM Manager or by using the [qvm-pci command](/doc/AssigningDevices/).)
|
||||
Qubes supports the ability to attach a USB stick (or just one or more of its partitions) to any AppVM easily, no matter which VM actually handles the USB controller. (The USB controller may be assigned on the **Devices** tab of an AppVM's settings page in Qubes VM Manager or by using the [qvm-pci command](/en/doc/assigning-devices/).)
|
||||
|
||||
As of Qubes R2 Beta 3, USB stick mounting has been integrated into the Qubes VM Manager GUI. Simply insert your USB stick, right-click the desired AppVM in the Qubes VM Manager list, click **Attach/detach block devices**, and select your desired action and device. This, however, only works for the whole device.
|
||||
If you would like to attach individual partitions you must use the command-line tool (shown below). The reason for this is that when attaching a single partition, it used to be that Nautilus file manager would not see it and automatically mount it (see [this ticket](https://github.com/QubesOS/qubes-issues/issues/623)). This problem, however, seems to be resolved (see [this issue comment](https://github.com/QubesOS/qubes-issues/issues/1072#issuecomment-124270051)).
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: AssigningDevices
|
||||
permalink: /doc/AssigningDevices/
|
||||
redirect_from: /wiki/AssigningDevices/
|
||||
permalink: /en/doc/assigning-devices/
|
||||
redirect_from:
|
||||
- /doc/AssigningDevices/
|
||||
- /wiki/AssigningDevices/
|
||||
---
|
||||
|
||||
Assigning Devices to VMs
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ConfigFiles
|
||||
permalink: /doc/ConfigFiles/
|
||||
permalink: /en/doc/config-files/
|
||||
redirect_from:
|
||||
- /doc/ConfigFiles/
|
||||
- "/doc/UserDoc/ConfigFiles/"
|
||||
- "/wiki/UserDoc/ConfigFiles/"
|
||||
---
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DiskTRIM
|
||||
permalink: /doc/DiskTRIM/
|
||||
redirect_from: /wiki/DiskTRIM/
|
||||
permalink: /en/doc/disk-trim/
|
||||
redirect_from:
|
||||
- /doc/DiskTRIM/
|
||||
- /wiki/DiskTRIM/
|
||||
---
|
||||
|
||||
VMs have already TRIM enabled by default, but dom0 doesn't. There are some security implications (read for example [this article](http://asalor.blogspot.com/2011/08/trim-dm-crypt-problems.html)), but IMO not very serious.
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ExternalAudio
|
||||
permalink: /doc/ExternalAudio/
|
||||
redirect_from: /wiki/ExternalAudio/
|
||||
permalink: /en/doc/external-audio/
|
||||
redirect_from:
|
||||
- /doc/ExternalAudio/
|
||||
- /wiki/ExternalAudio/
|
||||
---
|
||||
|
||||
Using External Audio Devices
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ExternalDeviceMountPoint
|
||||
permalink: /doc/ExternalDeviceMountPoint/
|
||||
redirect_from: /wiki/ExternalDeviceMountPoint/
|
||||
permalink: /en/doc/external-device-mount-point/
|
||||
redirect_from:
|
||||
- /doc/ExternalDeviceMountPoint/
|
||||
- /wiki/ExternalDeviceMountPoint/
|
||||
---
|
||||
|
||||
All external storage devices connected to an AppVM using the Fedora template can be found under
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Fetchmail
|
||||
permalink: /doc/Fetchmail/
|
||||
redirect_from: /wiki/Fetchmail/
|
||||
permalink: /en/doc/fetchmail/
|
||||
redirect_from:
|
||||
- /doc/Fetchmail/
|
||||
- /wiki/Fetchmail/
|
||||
---
|
||||
|
||||
Fetchmail
|
||||
=========
|
||||
|
||||
Fetchmail is standalone MRA (Mail Retrieval Agent) aka "IMAP/POP3 client". Its sole purpose is to fetch your messages and store it locally or feed to local MTA (Message Transfer Agent). It cannot "read" messages — for that, use a MUA like Thunderbird or [Mutt](/doc/Mutt/).
|
||||
Fetchmail is standalone MRA (Mail Retrieval Agent) aka "IMAP/POP3 client". Its sole purpose is to fetch your messages and store it locally or feed to local MTA (Message Transfer Agent). It cannot "read" messages — for that, use a MUA like Thunderbird or [Mutt](/en/doc/mutt/).
|
||||
|
||||
Installation
|
||||
------------
|
||||
@ -20,7 +22,7 @@ Configuration
|
||||
|
||||
Assuming you have more than one account (safe assumption these days), you need to spawn multiple fetchmail instances, one for each IMAP/POP3 server (though one instance can watch over several accounts on one server). The easiest way is to create template systemd unit and start it several times. Fedora does not supply any, so we have to write one anyway.
|
||||
|
||||
**NOTE:** this assumes you use [Postfix](/doc/Postfix/) as your local MTA.
|
||||
**NOTE:** this assumes you use [Postfix](/en/doc/postfix/) as your local MTA.
|
||||
|
||||
In TemplateVM create `/etc/systemd/system/fetchmail@.service`:
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Mutt
|
||||
permalink: /doc/Mutt/
|
||||
redirect_from: /wiki/Mutt/
|
||||
permalink: /en/doc/mutt/
|
||||
redirect_from:
|
||||
- /doc/Mutt/
|
||||
- /wiki/Mutt/
|
||||
---
|
||||
|
||||
Mutt
|
||||
@ -13,8 +15,8 @@ Mutt is a fast, standards-compliant, efficient MUA (Mail User Agent). In some ar
|
||||
Mutt lacks true MTA (Message Transfer Agent aka "SMTP client") and MRA (Mail
|
||||
Retrieval Agent aka "IMAP/POP3 client"), thus there are some provisions
|
||||
built-in. In principle it is only mail reader and composer. You may install
|
||||
true MTA such as [Postfix](/doc/Postfix/) or Exim and MRA such as
|
||||
[Fetchmail](/doc/Fetchmail/). Alternatively you can synchronize your mailbox
|
||||
true MTA such as [Postfix](/en/doc/postfix/) or Exim and MRA such as
|
||||
[Fetchmail](/en/doc/fetchmail/). Alternatively you can synchronize your mailbox
|
||||
using [OfflineIMAP](https://github.com/OfflineIMAP/offlineimap) and just stick
|
||||
to integrated SMTP support. You can even use integrated IMAP client, but it is
|
||||
not very convenient.
|
||||
@ -27,7 +29,7 @@ Installation
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
Mutt generally works out of the box. This configuration guide discusses only Qubes-specific setup. In this example we will have one TemplateVM and several AppVMs. It also takes advantage of [SplitGPG](/doc/UserDoc/SplitGpg/), which is assumed to be already working.
|
||||
Mutt generally works out of the box. This configuration guide discusses only Qubes-specific setup. In this example we will have one TemplateVM and several AppVMs. It also takes advantage of [SplitGPG](/en/doc/split-gpg/), which is assumed to be already working.
|
||||
|
||||
**NOTE:** this requires `qubes-gpg-split >= 2.0.9`. 2.0.8 and earlier contains bug which causes this setup to hang in specific situations and does not allow to list keys.
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: NetworkBridgeSupport
|
||||
permalink: /doc/NetworkBridgeSupport/
|
||||
redirect_from: /wiki/NetworkBridgeSupport/
|
||||
permalink: /en/doc/network-bridge-support/
|
||||
redirect_from:
|
||||
- /doc/NetworkBridgeSupport/
|
||||
- /wiki/NetworkBridgeSupport/
|
||||
---
|
||||
|
||||
Network Bridge Support (EXPERIMENTAL and UNSUPPORTED)
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: NetworkPrinter
|
||||
permalink: /doc/NetworkPrinter/
|
||||
redirect_from: /wiki/NetworkPrinter/
|
||||
permalink: /en/doc/network-printer/
|
||||
redirect_from:
|
||||
- /doc/NetworkPrinter/
|
||||
- /wiki/NetworkPrinter/
|
||||
---
|
||||
|
||||
Configuring a network printer for Qubes AppVMs
|
||||
@ -20,7 +22,7 @@ Security considerations for network printers and drivers
|
||||
|
||||
Some printers require 3rd party drivers, typically downloadable from the vendor's website. Such drivers are typically distributed in a form of ready to install RPM packages. However, they are often unsigned, and additionally the downloads are available via HTTP connections only. As a result, installation of such 3rd party RPMs in a default template VM exposes a risk of compromise of this template VM, which, in turn, leads automatically to compromise of all the AppVMs based on the template. (Again, it's not buggy or malicious drivers that we fear here, but rather malicious installation scripts for those drivers).
|
||||
|
||||
In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/doc/DisposableVms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
|
||||
In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/en/doc/disposable-vms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
|
||||
|
||||
However, one should be aware that most (all?) network printing protocols are insecure, unencrypted protocols. This means, that an attacker who is able to sniff the local network, or who is controlling the (normally untrusted) Qubes NetVM, will likely to be able to see the documents being printed. This is a limitation of today's printers and printing protocols, something that cannot be solved by Qubes or any other OS.
|
||||
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Postfix
|
||||
permalink: /doc/Postfix/
|
||||
redirect_from: /wiki/Postfix/
|
||||
permalink: /en/doc/postfix/
|
||||
redirect_from:
|
||||
- /doc/Postfix/
|
||||
- /wiki/Postfix/
|
||||
---
|
||||
|
||||
Postfix
|
||||
=======
|
||||
|
||||
Postfix is full featured MTA (Message Transfer Agent). Here we will configure it in smarthost mode as part of common [Mutt](/doc/Mutt/)+Postfix+[Fetchmail](/doc/Fetchmail/) stack.
|
||||
Postfix is full featured MTA (Message Transfer Agent). Here we will configure it in smarthost mode as part of common [Mutt](/en/doc/mutt/)+Postfix+[Fetchmail](/en/doc/fetchmail/) stack.
|
||||
|
||||
Installation
|
||||
------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ResizeDiskImage
|
||||
permalink: /doc/ResizeDiskImage/
|
||||
redirect_from: /wiki/ResizeDiskImage/
|
||||
permalink: /en/doc/resize-disk-image/
|
||||
redirect_from:
|
||||
- /doc/ResizeDiskImage/
|
||||
- /wiki/ResizeDiskImage/
|
||||
---
|
||||
|
||||
Resizing Disk Image
|
||||
@ -15,7 +17,7 @@ There are several disk images which can be easily extended.
|
||||
|
||||
1048576 MB is the maximum size which can be assigned to a private storage through qubes-manager.
|
||||
|
||||
To grow the private disk image of a AppVM beyond this limit [qubes-grow-private](/doc/Dom0Tools/QvmGrowPrivate/) can be used:
|
||||
To grow the private disk image of a AppVM beyond this limit [qubes-grow-private](/en/doc/dom0-tools/qvm-grow-private/) can be used:
|
||||
|
||||
~~~
|
||||
qvm-grow-private <vm-name> <size>
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ResizeRootDiskImage
|
||||
permalink: /doc/ResizeRootDiskImage/
|
||||
redirect_from: /wiki/ResizeRootDiskImage/
|
||||
permalink: /en/doc/resize-root-disk-image/
|
||||
redirect_from:
|
||||
- /doc/ResizeRootDiskImage/
|
||||
- /wiki/ResizeRootDiskImage/
|
||||
---
|
||||
|
||||
Resizing \`root.img\` Size
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Rxvt
|
||||
permalink: /doc/Rxvt/
|
||||
redirect_from: /wiki/Rxvt/
|
||||
permalink: /en/doc/rxvt/
|
||||
redirect_from:
|
||||
- /doc/Rxvt/
|
||||
- /wiki/Rxvt/
|
||||
---
|
||||
|
||||
Rxvt
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SecondaryStorage
|
||||
permalink: /doc/SecondaryStorage/
|
||||
redirect_from: /wiki/SecondaryStorage/
|
||||
permalink: /en/doc/secondary-storage/
|
||||
redirect_from:
|
||||
- /doc/SecondaryStorage/
|
||||
- /wiki/SecondaryStorage/
|
||||
---
|
||||
|
||||
Storing AppVMs on Secondary Drives
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: TorVM
|
||||
permalink: /doc/TorVM/
|
||||
permalink: /en/doc/torvm/
|
||||
redirect_from:
|
||||
- /doc/TorVM/
|
||||
- "/doc/UserDoc/TorVM/"
|
||||
- "/wiki/UserDoc/TorVM/"
|
||||
---
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: VPN
|
||||
permalink: /doc/VPN/
|
||||
redirect_from: /wiki/VPN/
|
||||
permalink: /en/doc/vpn/
|
||||
redirect_from:
|
||||
- /doc/VPN/
|
||||
- /wiki/VPN/
|
||||
---
|
||||
|
||||
How To make a VPN Gateway in Qubes
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: ZFS
|
||||
permalink: /doc/ZFS/
|
||||
redirect_from: /wiki/ZFS/
|
||||
permalink: /en/doc/zfs/
|
||||
redirect_from:
|
||||
- /doc/ZFS/
|
||||
- /wiki/ZFS/
|
||||
---
|
||||
|
||||
ZFS in Qubes
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DispVMCustomization
|
||||
permalink: /doc/DispVMCustomization/
|
||||
permalink: /en/doc/dispvm-customization/
|
||||
redirect_from:
|
||||
- /doc/DispVMCustomization/
|
||||
- "/doc/UserDoc/DispVMCustomization/"
|
||||
- "/wiki/UserDoc/DispVMCustomization/"
|
||||
---
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: LanguageLocalization
|
||||
permalink: /doc/LanguageLocalization/
|
||||
redirect_from: /wiki/LanguageLocalization/
|
||||
permalink: /en/doc/language-localization/
|
||||
redirect_from:
|
||||
- /doc/LanguageLocalization/
|
||||
- /wiki/LanguageLocalization/
|
||||
---
|
||||
|
||||
For digiting with special alphabets, please see this [thread](https://groups.google.com/forum/#!searchin/qubes-users/languge/qubes-users/VcNPlhdgVQM/iF9PqSzayacJ)
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: XFCE
|
||||
permalink: /doc/XFCE/
|
||||
permalink: /en/doc/xfce/
|
||||
redirect_from:
|
||||
- /doc/XFCE/
|
||||
- "/doc/UserDoc/XFCE/"
|
||||
- "/wiki/UserDoc/XFCE/"
|
||||
---
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: CodingStyle
|
||||
permalink: /doc/CodingStyle/
|
||||
permalink: /en/doc/coding-style/
|
||||
redirect_from:
|
||||
- /doc/CodingStyle/
|
||||
- /wiki/CodingStyle/
|
||||
- /trac/wiki/CodingStyle/
|
||||
---
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DevelBooks
|
||||
permalink: /doc/DevelBooks/
|
||||
redirect_from: /wiki/DevelBooks/
|
||||
permalink: /en/doc/devel-books/
|
||||
redirect_from:
|
||||
- /doc/DevelBooks/
|
||||
- /wiki/DevelBooks/
|
||||
---
|
||||
|
||||
Below is a list of various books that might be useful in learning some basics needed for Qubes development.
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DevelFaq
|
||||
permalink: /doc/DevelFaq/
|
||||
redirect_from: /wiki/DevelFaq/
|
||||
permalink: /en/doc/devel-faq/
|
||||
redirect_from:
|
||||
- /doc/DevelFaq/
|
||||
- /wiki/DevelFaq/
|
||||
---
|
||||
|
||||
Qubes Developers FAQ
|
||||
@ -24,7 +26,7 @@ There are a few things that are KDE-specific, but generally it should not be a b
|
||||
|
||||
- Qubes requires KDM (KDE Login Manager), rather than GDM, for the very simple reason that GDM doesn't obey standards and start `/usr/bin/Xorg` instead of `/usr/bin/X`. This is important for Qubes, because we need to load a special "X wrapper" (to make it possible to use Linux usermode shared memory to access Xen shared memory pages in our App Viewers -- see the sources [here](https://github.com/QubesOS/qubes-gui-daemon/tree/master/shmoverride)). So, Qubes makes the `/usr/bin/X` to be a symlink to the Qubes X Wrapper, which, in turn, executes the `/usr/bin/Xorg`. This works well with KDM (and would probably also work with other X login managers), but not with GDM. If somebody succeeded in makeing GDM to execute `/usr/bin/X` instead of `/usr/bin/Xorg`, we would love to hear about it!
|
||||
|
||||
- We maintain a special [repository](/doc/KdeDom0/) for building packages specifically for Qubes Dom0.
|
||||
- We maintain a special [repository](/en/doc/kde-dom0/) for building packages specifically for Qubes Dom0.
|
||||
|
||||
- We've patched the KDE's Window Manager (specifically [one of the decoration plugins](https://github.com/QubesOS/qubes-desktop-linux-kde/tree/master/plastik-for-qubes)) to draw window decorations in the color of the specific AppVM's label.
|
||||
|
||||
@ -36,8 +38,8 @@ Any rpm-based, 64-bit. Preferred Fedora.
|
||||
|
||||
### Q: How to build Qubes from sources?
|
||||
|
||||
See [the instruction](/doc/QubesBuilder/)
|
||||
See [the instruction](/en/doc/qubes-builder/)
|
||||
|
||||
### Q: How do I submit a patch?
|
||||
|
||||
See [Qubes Source Code Repositories](/doc/SourceCode/).
|
||||
See [Qubes Source Code Repositories](/en/doc/source-code/).
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesResearch
|
||||
permalink: /doc/QubesResearch/
|
||||
redirect_from: /wiki/QubesResearch/
|
||||
permalink: /en/doc/qubes-research/
|
||||
redirect_from:
|
||||
- /doc/QubesResearch/
|
||||
- /wiki/QubesResearch/
|
||||
---
|
||||
|
||||
Here are some links to various papers/research projects that somehow relate to Qubes.
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SourceCode
|
||||
permalink: /doc/SourceCode/
|
||||
redirect_from: /wiki/SourceCode/
|
||||
permalink: /en/doc/source-code/
|
||||
redirect_from:
|
||||
- /doc/SourceCode/
|
||||
- /wiki/SourceCode/
|
||||
---
|
||||
|
||||
Qubes Source Code Repositories
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SystemDoc
|
||||
permalink: /doc/SystemDoc/
|
||||
redirect_from: /wiki/SystemDoc/
|
||||
permalink: /en/doc/system-doc/
|
||||
redirect_from:
|
||||
- /doc/SystemDoc/
|
||||
- /wiki/SystemDoc/
|
||||
---
|
||||
|
||||
System Documentation for Developers
|
||||
@ -10,42 +12,42 @@ System Documentation for Developers
|
||||
|
||||
Fundamentals
|
||||
------------
|
||||
* [Qubes OS Architecture Overview](/doc/QubesArchitecture/)
|
||||
* [Qubes OS Architecture Overview](/en/doc/qubes-architecture/)
|
||||
* [Qubes OS Architecture Spec v0.3 [PDF]](/attachment/wiki/QubesArchitecture/arch-spec-0.3.pdf) (The original 2009 document that started this all...)
|
||||
* [Security-critical elements of Qubes OS](/doc/SecurityCriticalCode/)
|
||||
* Qubes RPC: [`qrexec` v2](/doc/Qrexec/) ([R2 implementation](/doc/Qrexec2Implementation/))
|
||||
* Qubes RPC: [`qrexec` v3](/doc/Qrexec3/) ([R3 implementation](/doc/Qrexec3Implementation/)) (Odyssey)
|
||||
* [Security-critical elements of Qubes OS](/en/doc/security-critical-code/)
|
||||
* Qubes RPC: [`qrexec` v2](/en/doc/qrexec/) ([R2 implementation](/en/doc/qrexec2-implementation/))
|
||||
* Qubes RPC: [`qrexec` v3](/en/doc/qrexec3/) ([R3 implementation](/en/doc/qrexec3-implementation/)) (Odyssey)
|
||||
* [Example for writing a `qrexec` service in Qubes OS (blog post)](http://theinvisiblethings.blogspot.com/2013/02/converting-untrusted-pdfs-into-trusted.html)
|
||||
* [Qubes GUI virtualization protocol](/doc/GUIdocs/)
|
||||
* [Networking in Qubes](/doc/QubesNet/)
|
||||
* [Implementation of template sharing and updating](/doc/TemplateImplementation/)
|
||||
* [Qubes GUI virtualization protocol](/en/doc/gui-docs/)
|
||||
* [Networking in Qubes](/en/doc/qubes-net/)
|
||||
* [Implementation of template sharing and updating](/en/doc/template-implementation/)
|
||||
|
||||
Services
|
||||
--------
|
||||
* [Inter-domain file copying](/doc/Qfilecopy/) (deprecates [`qfileexchgd`](/doc/Qfileexchgd/))
|
||||
* [Dynamic memory management in Qubes](/doc/Qmemman/)
|
||||
* [Implementation of DisposableVMs](/doc/DVMimpl/)
|
||||
* [Inter-domain file copying](/en/doc/qfilecopy/) (deprecates [`qfileexchgd`](/en/doc/qfileexchgd/))
|
||||
* [Dynamic memory management in Qubes](/en/doc/qmemman/)
|
||||
* [Implementation of DisposableVMs](/en/doc/dvm-impl/)
|
||||
* [Article about disposable VMs](http://theinvisiblethings.blogspot.com/2010/06/disposable-vms.html)
|
||||
* [Dom0 secure update mechanism](/doc/Dom0SecureUpdates/)
|
||||
* [Dom0 secure update mechanism](/en/doc/dom0-secure-updates/)
|
||||
* VM secure update mechanism (forthcoming)
|
||||
|
||||
Debugging
|
||||
---------
|
||||
* [Profiling python code](/doc/Profiling/)
|
||||
* [Test environment in separate machine for automatic tests](/doc/TestBench/)
|
||||
* [Automated tests](/doc/AutomatedTests/)
|
||||
* [VM-dom0 internal configuration interface](/doc/VMInterface/)
|
||||
* [Debugging Windows VMs](/doc/WindowsDebugging/)
|
||||
* [Profiling python code](/en/doc/profiling/)
|
||||
* [Test environment in separate machine for automatic tests](/en/doc/test-bench/)
|
||||
* [Automated tests](/en/doc/automated-tests/)
|
||||
* [VM-dom0 internal configuration interface](/en/doc/vm-interface/)
|
||||
* [Debugging Windows VMs](/en/doc/windows-debugging/)
|
||||
|
||||
Building
|
||||
--------
|
||||
* [Building Qubes](/doc/QubesBuilder/) (["API" Details](/doc/QubesBuilderDetails/))
|
||||
* [Development Workflow](/doc/DevelopmentWorkflow/)
|
||||
* [KDE Dom0 packages for Qubes](/doc/KdeDom0/)
|
||||
* [How to build Qubes installation ISO](/doc/InstallationIsoBuilding/)
|
||||
* [Building Qubes OS 3.0 ISO](/doc/QubesR3Building/)
|
||||
* [Building USB passthrough support (experimental)](/doc/USBVM/)
|
||||
* [Building a TemplateVM based on a new OS (ArchLinux example)](/doc/BuildingNonFedoraTemplate/)
|
||||
* [Building the Archlinux Template](/doc/BuildingArchlinuxTemplate/)
|
||||
* [Building Qubes](/en/doc/qubes-builder/) (["API" Details](/en/doc/qubes-builder-details/))
|
||||
* [Development Workflow](/en/doc/development-workflow/)
|
||||
* [KDE Dom0 packages for Qubes](/en/doc/kde-dom0/)
|
||||
* [How to build Qubes installation ISO](/en/doc/installation-iso-building/)
|
||||
* [Building Qubes OS 3.0 ISO](/en/doc/qubes-r3-building/)
|
||||
* [Building USB passthrough support (experimental)](/en/doc/usbvm/)
|
||||
* [Building a TemplateVM based on a new OS (ArchLinux example)](/en/doc/building-non-fedora-template/)
|
||||
* [Building the Archlinux Template](/en/doc/building-archlinux-template/)
|
||||
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: VersionScheme
|
||||
permalink: /doc/VersionScheme/
|
||||
redirect_from: /wiki/VersionScheme/
|
||||
permalink: /en/doc/version-scheme/
|
||||
redirect_from:
|
||||
- /doc/VersionScheme/
|
||||
- /wiki/VersionScheme/
|
||||
---
|
||||
|
||||
Version Scheme
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: BuildingArchlinuxTemplate
|
||||
permalink: /doc/BuildingArchlinuxTemplate/
|
||||
redirect_from: /wiki/BuildingArchlinuxTemplate/
|
||||
permalink: /en/doc/building-archlinux-template/
|
||||
redirect_from:
|
||||
- /doc/BuildingArchlinuxTemplate/
|
||||
- /wiki/BuildingArchlinuxTemplate/
|
||||
---
|
||||
|
||||
Template building
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: BuildingNonFedoraTemplate
|
||||
permalink: /doc/BuildingNonFedoraTemplate/
|
||||
redirect_from: /wiki/BuildingNonFedoraTemplate/
|
||||
permalink: /en/doc/building-non-fedora-template/
|
||||
redirect_from:
|
||||
- /doc/BuildingNonFedoraTemplate/
|
||||
- /wiki/BuildingNonFedoraTemplate/
|
||||
---
|
||||
|
||||
Building a TemplateVM for ArchLinux (or another non fedora OS)
|
||||
@ -136,7 +138,7 @@ As soon as you manage to make qrexec and qubes-gui-agent working, it should be s
|
||||
|
||||
Several XEN libraries are required for Qubes to work correctly. In fact, you need to make xenstore commands working before anything else. For this, Qubes git can be used as several patches have been selected by Qubes developpers that could impact the activity inside a VM. Start be retrieving a recent git and identify how you can build a package from it: `git clone git://git.qubes-os.org/marmarek/xen`
|
||||
|
||||
Find the .spec file in the git repository (this is the file being used to build rpm packages), and try to adapt it to your OS in order to build a package similar to the target 'xen-vm'. For example, a PKGBUILD has been created for [ArchLinux](/doc/Templates/Archlinux/) and can be found on [http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD](http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD).
|
||||
Find the .spec file in the git repository (this is the file being used to build rpm packages), and try to adapt it to your OS in order to build a package similar to the target 'xen-vm'. For example, a PKGBUILD has been created for [ArchLinux](/en/doc/templates/archlinux/) and can be found on [http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD](http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD).
|
||||
|
||||
Don't be afraid with the complexity of the PKGBUILD, most of the code is almost a copy/paste of required sources and patches found in the .spec file provided in the git repository.
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DevelopmentWorkflow
|
||||
permalink: /doc/DevelopmentWorkflow/
|
||||
redirect_from: /wiki/DevelopmentWorkflow/
|
||||
permalink: /en/doc/development-workflow/
|
||||
redirect_from:
|
||||
- /doc/DevelopmentWorkflow/
|
||||
- /wiki/DevelopmentWorkflow/
|
||||
---
|
||||
|
||||
Development Workflow
|
||||
@ -10,7 +12,7 @@ Development Workflow
|
||||
|
||||
A workflow for developing Qubes OS+
|
||||
|
||||
First things first, setup [QubesBuilder](/doc/QubesBuilder/). This guide assumes you're using qubes-builder to build Qubes.
|
||||
First things first, setup [QubesBuilder](/en/doc/qubes-builder/). This guide assumes you're using qubes-builder to build Qubes.
|
||||
|
||||
Repositories and committing Code
|
||||
--------------------------------
|
||||
@ -128,7 +130,7 @@ RPMS will appear in qubes-src/kernel/rpm/x86\_64:
|
||||
-rw-rw-r-- 1 user user 54502117 Nov 17 05:37 kernel-qubes-vm-3.4.18-1debug20121117a.pvops.qubes.x86_64.rpm
|
||||
~~~
|
||||
|
||||
### Useful [QubesBuilder](/doc/QubesBuilder/) commands
|
||||
### Useful [QubesBuilder](/en/doc/qubes-builder/) commands
|
||||
|
||||
1. *make check* - will check if all the code was commited into repository and if all repository are tagged with signed tag.
|
||||
2. *make show-vtags* - show version of each component (based on git tags) - mostly useful just before building ISO. **Note:** this will not show version for components containing changes since last version tag
|
||||
@ -142,7 +144,7 @@ When developing it is convenient to be able to rapidly test changes. Assuming yo
|
||||
|
||||
Here are some handy scripts Marek has shared to facilitate this.
|
||||
|
||||
You may also like to run your [test environment on separate machine](/doc/TestBench/).
|
||||
You may also like to run your [test environment on separate machine](/en/doc/test-bench/).
|
||||
|
||||
### Syncing dom0 files
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: InstallationIsoBuilding
|
||||
permalink: /doc/InstallationIsoBuilding/
|
||||
redirect_from: /wiki/InstallationIsoBuilding/
|
||||
permalink: /en/doc/installation-iso-building/
|
||||
redirect_from:
|
||||
- /doc/InstallationIsoBuilding/
|
||||
- /wiki/InstallationIsoBuilding/
|
||||
---
|
||||
|
||||
How to build Qubes installation ISO
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: KdeDom0
|
||||
permalink: /doc/KdeDom0/
|
||||
redirect_from: /wiki/KdeDom0/
|
||||
permalink: /en/doc/kde-dom0/
|
||||
redirect_from:
|
||||
- /doc/KdeDom0/
|
||||
- /wiki/KdeDom0/
|
||||
---
|
||||
|
||||
Qubes-customized KDE packages for Dom0
|
||||
======================================
|
||||
|
||||
The Qubes kde-dom0 project (see [Source Code](/doc/SourceCode/)) contains the source code needed for building the customized KDE packages for use in Qubes Dom0 (the user desktop). The packages are based on Fedora 12 KDE packages, but are heavily slimmed down (Qubes doesn't need lots of KDE functionality in Dom0, such as most of the KDE apps). In the near future those KDE packages will also get some Qubes specific extensions, such as coloured titlebars/frames nicely integrated into the KDE Window Manager. And, of course, custom themes, e.g. for KDM :)
|
||||
The Qubes kde-dom0 project (see [Source Code](/en/doc/source-code/)) contains the source code needed for building the customized KDE packages for use in Qubes Dom0 (the user desktop). The packages are based on Fedora 12 KDE packages, but are heavily slimmed down (Qubes doesn't need lots of KDE functionality in Dom0, such as most of the KDE apps). In the near future those KDE packages will also get some Qubes specific extensions, such as coloured titlebars/frames nicely integrated into the KDE Window Manager. And, of course, custom themes, e.g. for KDM :)
|
||||
|
||||
Getting the sources
|
||||
-------------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesBuilder
|
||||
permalink: /doc/QubesBuilder/
|
||||
redirect_from: /wiki/QubesBuilder/
|
||||
permalink: /en/doc/qubes-builder/
|
||||
redirect_from:
|
||||
- /doc/QubesBuilder/
|
||||
- /wiki/QubesBuilder/
|
||||
---
|
||||
|
||||
Building Qubes from scratch
|
||||
@ -84,9 +86,9 @@ You can also build selected component separately. Eg. to compile only gui virtua
|
||||
make gui-daemon
|
||||
|
||||
Full list you can get from make help. For advanced use and preparing sources
|
||||
for use with [QubesBuilder](/doc/QubesBuilder/) take a look at [doc directory
|
||||
for use with [QubesBuilder](/en/doc/qubes-builder/) take a look at [doc directory
|
||||
in QubesBuilder](https://github.com/marmarek/qubes-builder/tree/master/doc) or
|
||||
[QubesBuilderDetails](/doc/QubesBuilderDetails/) page.
|
||||
[QubesBuilderDetails](/en/doc/qubes-builder-details/) page.
|
||||
|
||||
Making customized build
|
||||
-----------------------
|
||||
@ -122,7 +124,7 @@ If you want to somehow modify sources, you can also do it, here are some basic s
|
||||
Code verification keys management
|
||||
=================================
|
||||
|
||||
[QubesBuilder](/doc/QubesBuilder/) by default verifies signed tags on every downloaded code. Public keys used for that are stored in `keyrings/git`. By default Qubes developers' keys are imported automatically, but if you need some additional keys (for example your own), you can add them using:
|
||||
[QubesBuilder](/en/doc/qubes-builder/) by default verifies signed tags on every downloaded code. Public keys used for that are stored in `keyrings/git`. By default Qubes developers' keys are imported automatically, but if you need some additional keys (for example your own), you can add them using:
|
||||
|
||||
GNUPGHOME=$PWD/keyrings/git gpg --import /path/to/key.asc
|
||||
GNUPGHOME=$PWD/keyrings/git gpg --edit-key ID_OF_JUST_IMPORTED_KEY
|
||||
|
||||
@ -1,22 +1,24 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesBuilderDetails
|
||||
permalink: /doc/QubesBuilderDetails/
|
||||
redirect_from: /wiki/QubesBuilderDetails/
|
||||
permalink: /en/doc/qubes-builder-details/
|
||||
redirect_from:
|
||||
- /doc/QubesBuilderDetails/
|
||||
- /wiki/QubesBuilderDetails/
|
||||
---
|
||||
|
||||
[QubesBuilder](/doc/QubesBuilder/) "API"
|
||||
[QubesBuilder](/en/doc/qubes-builder/) "API"
|
||||
========================================
|
||||
|
||||
Components Makefile.builder file
|
||||
--------------------------------
|
||||
|
||||
[QubesBuilder](/doc/QubesBuilder/) expects that each component have *Makefile.builder* file in its root directory. This file specifies what should be done to build the package. As name suggests, this is normal makefile, which is included by builder as its configuration. Its main purpose is to set some variables. Generally all available variables/settings are described as comments at the beginning of Makefile.\* in [QubesBuilder](/doc/QubesBuilder/).
|
||||
[QubesBuilder](/en/doc/qubes-builder/) expects that each component have *Makefile.builder* file in its root directory. This file specifies what should be done to build the package. As name suggests, this is normal makefile, which is included by builder as its configuration. Its main purpose is to set some variables. Generally all available variables/settings are described as comments at the beginning of Makefile.\* in [QubesBuilder](/en/doc/qubes-builder/).
|
||||
|
||||
Variables for Linux build:
|
||||
|
||||
- `RPM_SPEC_FILES` List (space separated) of spec files for RPM package build. Path should be relative to component root directory. [QubesBuilder](/doc/QubesBuilder/) will install all BuildRequires (in chroot environment) before the build. In most Qubes components all spec files are kept in *rpm\_spec* directory. This is mainly used for Fedora packages build.
|
||||
- `ARCH_BUILD_DIRS` List (space separated) of directories with PKGBUILD files for Archlinux package build. Similar to RPM build, [QubesBuilder](/doc/QubesBuilder/) will install all makedepends, then build the package.
|
||||
- `RPM_SPEC_FILES` List (space separated) of spec files for RPM package build. Path should be relative to component root directory. [QubesBuilder](/en/doc/qubes-builder/) will install all BuildRequires (in chroot environment) before the build. In most Qubes components all spec files are kept in *rpm\_spec* directory. This is mainly used for Fedora packages build.
|
||||
- `ARCH_BUILD_DIRS` List (space separated) of directories with PKGBUILD files for Archlinux package build. Similar to RPM build, [QubesBuilder](/en/doc/qubes-builder/) will install all makedepends, then build the package.
|
||||
|
||||
Most components uses *archlinux* directory for this purpose, so its good to keep this style.
|
||||
|
||||
@ -35,8 +37,8 @@ Variables for Windows build:
|
||||
- `SIGNTOOL` Path to signtool
|
||||
- `WIN_PACKAGE_CMD` Command used to produce installation package (msi or msm). Default value is *wix.bat*, similar to above - use *true* if you don't want this command.
|
||||
- `WIN_OUTPUT_HEADERS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with public headers of the package - for use in other components.
|
||||
- `WIN_OUTPUT_LIBS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with libraries (both DLL and implib) of the package - for use in other components. Note that [QubesBuilder](/doc/QubesBuilder/) will copy files specified as *\$(WIN\_OUTPUT\_LIBS)/\*/\** to match WDK directory layout (*\<specified directory\>/\<arch directory\>/\<actual libraries\>*), so you in mingw build you need to place libraries in some additional subdirectory.
|
||||
- `WIN_BUILD_DEPS` List of components required to build this one. [QubesBuilder](/doc/QubesBuilder/) will copy files specified with `WIN_OUTPUT_HEADERS` and `WIN_OUTPUT_LIBS` of those components to some directory and provide its path with `QUBES_INCLUDES` and `QUBES_LIBS` variables. Use those variables in your build scripts (*sources* or *Makefile* - depending on selected compiler). You can assume that the variables are always set and directories always exists, even if empty.
|
||||
- `WIN_OUTPUT_LIBS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with libraries (both DLL and implib) of the package - for use in other components. Note that [QubesBuilder](/en/doc/qubes-builder/) will copy files specified as *\$(WIN\_OUTPUT\_LIBS)/\*/\** to match WDK directory layout (*\<specified directory\>/\<arch directory\>/\<actual libraries\>*), so you in mingw build you need to place libraries in some additional subdirectory.
|
||||
- `WIN_BUILD_DEPS` List of components required to build this one. [QubesBuilder](/en/doc/qubes-builder/) will copy files specified with `WIN_OUTPUT_HEADERS` and `WIN_OUTPUT_LIBS` of those components to some directory and provide its path with `QUBES_INCLUDES` and `QUBES_LIBS` variables. Use those variables in your build scripts (*sources* or *Makefile* - depending on selected compiler). You can assume that the variables are always set and directories always exists, even if empty.
|
||||
|
||||
builder.conf settings
|
||||
---------------------
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesR3Building
|
||||
permalink: /doc/QubesR3Building/
|
||||
redirect_from: /wiki/QubesR3Building/
|
||||
permalink: /en/doc/qubes-r3-building/
|
||||
redirect_from:
|
||||
- /doc/QubesR3Building/
|
||||
- /wiki/QubesR3Building/
|
||||
---
|
||||
|
||||
Building Qubes OS 3.0 ISO
|
||||
=========================
|
||||
|
||||
Ensure your system is rpm-based and that you have necessary dependencies installed (see [QubesBuilder](/doc/QubesBuilder/) for more info):
|
||||
Ensure your system is rpm-based and that you have necessary dependencies installed (see [QubesBuilder](/en/doc/qubes-builder/) for more info):
|
||||
|
||||
~~~
|
||||
sudo yum install git createrepo rpm-build make wget rpmdevtools pandoc
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: USBVM
|
||||
permalink: /doc/USBVM/
|
||||
redirect_from: /wiki/USBVM/
|
||||
permalink: /en/doc/usbvm/
|
||||
redirect_from:
|
||||
- /doc/USBVM/
|
||||
- /wiki/USBVM/
|
||||
---
|
||||
|
||||
USB Pass through: USBVM
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Contributing
|
||||
permalink: /doc/contributing/
|
||||
permalink: /en/doc/contributing/
|
||||
redirect_from:
|
||||
- /doc/contributing/
|
||||
- "/doc/ContributingHowto/"
|
||||
- "/wiki/ContributingHowto/"
|
||||
---
|
||||
@ -14,16 +15,16 @@ Ok, so you think Qubes Project is cool and you would like to contribute? You are
|
||||
|
||||
First you should decide what you are interested in (and good in). The Qubes project would welcome contributions in various areas:
|
||||
|
||||
- Testing and [bug reporting](/doc/BugReportingGuide/)
|
||||
- Testing and [bug reporting](/en/doc/reporting-bugs/)
|
||||
- Code audit (e.g. gui-daemon)
|
||||
- New features
|
||||
- Artwork (plymouth themes, KDM themes, installer themes, wallpapers, etc)
|
||||
|
||||
Perhaps the best starting point is to have a look at the [issues](https://github.com/QubesOS/qubes-issues/issues) to see what are the most urgent tasks to do.
|
||||
|
||||
Before you engage in some longer activity, e.g. implementing a new feature, it's always good to contact us first (preferably via the [qubes-devel](/doc/QubesLists/) list), to avoid a situation when two or more independent people would work on the same feature at the same time, doubling each others work. When you contact us and devote to a particular task, we will create a ticket for this task with info who is working on this feature and what is the expected date of some early code to be posted.
|
||||
Before you engage in some longer activity, e.g. implementing a new feature, it's always good to contact us first (preferably via the [qubes-devel](/en/doc/qubes-lists/) list), to avoid a situation when two or more independent people would work on the same feature at the same time, doubling each others work. When you contact us and devote to a particular task, we will create a ticket for this task with info who is working on this feature and what is the expected date of some early code to be posted.
|
||||
|
||||
When you are ready to start some work, read how to [access Qubes sources and send patches](/doc/SourceCode/).
|
||||
When you are ready to start some work, read how to [access Qubes sources and send patches](/en/doc/source-code/).
|
||||
|
||||
You can also contribute in other areas than coding and testing, e.g. by providing mirrors for Qubes rpm repositories, providing feedback about what features you would like to have in Qubes, or perhaps even preparing some cool You Tube videos that would demonstrate some Qubes' features. You are always encouraged to discuss your ideas on qubes-devel.
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Automated tests
|
||||
permalink: /doc/AutomatedTests/
|
||||
permalink: /en/doc/automated-tests/
|
||||
redirect_from: /doc/AutomatedTests/
|
||||
---
|
||||
|
||||
Automatic tests
|
||||
@ -103,7 +104,7 @@ Example test run:
|
||||
After you added a new unit test to [core-admin/tests](https://github.com/QubesOS/qubes-core-admin/tree/master/tests)
|
||||
you have to make sure of two things:
|
||||
|
||||
1. The test will be added to the RPM file created by [QubesBuilder](/doc/QubesBuilder/)
|
||||
1. The test will be added to the RPM file created by [QubesBuilder](/en/doc/qubes-builder/)
|
||||
For this you need to edit [core-admin/tests/Makefile](https://github.com/QubesOS/qubes-core-admin/tree/master/tests/Makefile)
|
||||
2. The test will be loaded by [core-admin/tests/\_\_init\_\_.py](https://github.com/QubesOS/qubes-core-admin/tree/master/tests/__init__.py)
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Profiling
|
||||
permalink: /doc/Profiling/
|
||||
redirect_from: /wiki/Profiling/
|
||||
permalink: /en/doc/profiling/
|
||||
redirect_from:
|
||||
- /doc/Profiling/
|
||||
- /wiki/Profiling/
|
||||
---
|
||||
|
||||
Profiling
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: TestBench
|
||||
permalink: /doc/TestBench/
|
||||
redirect_from: /wiki/TestBench/
|
||||
permalink: /en/doc/test-bench/
|
||||
redirect_from:
|
||||
- /doc/TestBench/
|
||||
- /wiki/TestBench/
|
||||
---
|
||||
|
||||
Test bench for Dom0
|
||||
@ -10,7 +12,7 @@ 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.
|
||||
|
||||
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/QubesBuilder/) and you have it set up and running flawlessly.
|
||||
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](/en/doc/qubes-builder/) and you have it set up and running flawlessly.
|
||||
|
||||
Setting up the machine
|
||||
----------------------
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: VMInterface
|
||||
permalink: /doc/VMInterface/
|
||||
permalink: /en/doc/vm-interface/
|
||||
redirect_from:
|
||||
- /doc/VMInterface/
|
||||
- "/doc/SystemDoc/VMInterface/"
|
||||
- "/wiki/SystemDoc/VMInterface/"
|
||||
---
|
||||
@ -82,16 +83,16 @@ Other Qrexec services installed by default:
|
||||
- `qubes.DetachPciDevice` - service called in reaction to `qvm-pci -d` call on
|
||||
running VM. The service receives one word - BDF of device to detach. When the
|
||||
service call ends, the device will be detached
|
||||
- `qubes.Filecopy` - receive some files from other VM. Files sent in [qfile format](/doc/Qfilecopy/)
|
||||
- `qubes.Filecopy` - receive some files from other VM. Files sent in [qfile format](/en/doc/qfilecopy/)
|
||||
- `qubes.OpenInVM` - open a file in called VM. Service receives a single file on stdin (in
|
||||
[qfile format](/doc/Qfilecopy/). After a file viewer/editor is terminated, if
|
||||
[qfile format](/en/doc/qfilecopy/). After a file viewer/editor is terminated, if
|
||||
the file was modified, can be sent back (just raw content, without any
|
||||
headers); otherwise service should just terminate without sending anything.
|
||||
This service is used by both `qvm-open-in-vm` and `qvm-open-in-dvm` tools. When
|
||||
called in DispVM, service termination will trigger DispVM cleanup.
|
||||
- `qubes.Restore` - retrieve Qubes backup. The service receives backup location
|
||||
entered by the user (one line, terminated by '\n'), then should output backup
|
||||
archive in [qfile format](/doc/Qfilecopy/) (core-agent-linux component contains
|
||||
archive in [qfile format](/en/doc/qfilecopy/) (core-agent-linux component contains
|
||||
`tar2qfile` utility to do the conversion
|
||||
- `qubes.SelectDirectory`, `qubes.SelectFile` - services which should show
|
||||
file/directory selection dialog and return (to stdout) a single line
|
||||
@ -117,7 +118,7 @@ abstraction. This will change in the future. Those tools are:
|
||||
- `nm-online -x` - called before `qubes.SyncNtpClock` service call by `qvm-sync-clock` tool
|
||||
- `resize2fs` - called to resize filesystem on /rw partition by `qvm-grow-private` tool
|
||||
- `gpk-update-viewer` - called by Qubes Manager to display available updates in a TemplateVM
|
||||
- `systemctl start qubes-update-check.timer` (and similarly stop) - called when enabling/disabling updates checking in given VM (`qubes-update-check` [qvm-service](/doc/QubesService/))
|
||||
- `systemctl start qubes-update-check.timer` (and similarly stop) - called when enabling/disabling updates checking in given VM (`qubes-update-check` [qvm-service](/en/doc/qubes-service/))
|
||||
|
||||
Additionally automatic tests extensively calls various commands directly in VMs. We do not plan to change that.
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: WindowsDebugging
|
||||
permalink: /doc/WindowsDebugging/
|
||||
redirect_from: /wiki/WindowsDebugging/
|
||||
permalink: /en/doc/windows-debugging/
|
||||
redirect_from:
|
||||
- /doc/WindowsDebugging/
|
||||
- /wiki/WindowsDebugging/
|
||||
---
|
||||
|
||||
Debugging Windows HVMs
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Documentation Guidelines
|
||||
permalink: /doc/doc-guidelines/
|
||||
permalink: /en/doc/doc-guidelines/
|
||||
redirect_from:
|
||||
- /doc/doc-guidelines/
|
||||
- "/wiki/DocStyle/"
|
||||
- "/doc/DocStyle/"
|
||||
---
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: GUIdocs
|
||||
permalink: /doc/GUIdocs/
|
||||
redirect_from: /wiki/GUIdocs/
|
||||
permalink: /en/doc/gui-docs/
|
||||
redirect_from:
|
||||
- /doc/GUIdocs/
|
||||
- /wiki/GUIdocs/
|
||||
---
|
||||
|
||||
Qubes GUI protocol
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesArchitecture
|
||||
permalink: /doc/QubesArchitecture/
|
||||
redirect_from: /wiki/QubesArchitecture/
|
||||
permalink: /en/doc/qubes-architecture/
|
||||
redirect_from:
|
||||
- /doc/QubesArchitecture/
|
||||
- /wiki/QubesArchitecture/
|
||||
---
|
||||
|
||||
Qubes Architecture Overview
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: QubesNet
|
||||
permalink: /doc/QubesNet/
|
||||
redirect_from: /wiki/QubesNet/
|
||||
permalink: /en/doc/qubes-net/
|
||||
redirect_from:
|
||||
- /doc/QubesNet/
|
||||
- /wiki/QubesNet/
|
||||
---
|
||||
|
||||
VM network in Qubes
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SecurityCriticalCode
|
||||
permalink: /doc/SecurityCriticalCode/
|
||||
permalink: /en/doc/security-critical-code/
|
||||
redirect_from:
|
||||
- /doc/SecurityCriticalCode/
|
||||
- /wiki/SecurityCriticalCode/
|
||||
- /trac/wiki/SecurityCriticalCode/
|
||||
---
|
||||
@ -12,7 +13,7 @@ Security-Critical Code in Qubes OS
|
||||
|
||||
Below is a list of security-critical (AKA trusted) code in Qubes OS. A successful attack against any of those might allow to compromise the Qubes OS security. This code can be thought of as of a Trusted Computing Base (TCB) of Qubes OS. The goal of the project has been to minimize the amount of this trusted code to an absolute minimum. The size of the current TCB is of an order of hundreds thousands of lines of C code, which is several orders of magnitude less than in other OSes, such as Windows, Linux or Mac, where it is of orders of tens of millions of lines of C code.
|
||||
|
||||
For more information about the security goals of Qubes OS, see [this page](/doc/SecurityGoals/).
|
||||
For more information about the security goals of Qubes OS, see [this page](/en/doc/security-goals/).
|
||||
|
||||
Security-Critical Qubes-Specific Components
|
||||
-------------------------------------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: TemplateImplementation
|
||||
permalink: /doc/TemplateImplementation/
|
||||
redirect_from: /wiki/TemplateImplementation/
|
||||
permalink: /en/doc/template-implementation/
|
||||
redirect_from:
|
||||
- /doc/TemplateImplementation/
|
||||
- /wiki/TemplateImplementation/
|
||||
---
|
||||
|
||||
Overview of VM block devices
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: License
|
||||
permalink: /doc/license/
|
||||
permalink: /en/doc/license/
|
||||
redirect_from:
|
||||
- /doc/license/
|
||||
- "/doc/QubesLicensing/"
|
||||
- "/wiki/QubesLicensing/"
|
||||
---
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Reporting Bugs
|
||||
permalink: /doc/reporting-bugs/
|
||||
permalink: /en/doc/reporting-bugs/
|
||||
redirect_from:
|
||||
- /doc/reporting-bugs/
|
||||
- "/doc/BugReportingGuide/"
|
||||
- "/wiki/BugReportingGuide/"
|
||||
---
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Dom0SecureUpdates
|
||||
permalink: /doc/Dom0SecureUpdates/
|
||||
redirect_from: /wiki/Dom0SecureUpdates/
|
||||
permalink: /en/doc/dom0-secure-updates/
|
||||
redirect_from:
|
||||
- /doc/Dom0SecureUpdates/
|
||||
- /wiki/Dom0SecureUpdates/
|
||||
---
|
||||
|
||||
Qubes Dom0 secure update procedure
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: DVMimpl
|
||||
permalink: /doc/DVMimpl/
|
||||
redirect_from: /wiki/DVMimpl/
|
||||
permalink: /en/doc/dvm-impl/
|
||||
redirect_from:
|
||||
- /doc/DVMimpl/
|
||||
- /wiki/DVMimpl/
|
||||
---
|
||||
|
||||
DisposableVM implementation in Qubes
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qfilecopy
|
||||
permalink: /doc/Qfilecopy/
|
||||
redirect_from: /wiki/Qfilecopy/
|
||||
permalink: /en/doc/qfilecopy/
|
||||
redirect_from:
|
||||
- /doc/Qfilecopy/
|
||||
- /wiki/Qfilecopy/
|
||||
---
|
||||
|
||||
InterVM file copy design
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qfileexchgd
|
||||
permalink: /doc/Qfileexchgd/
|
||||
redirect_from: /wiki/Qfileexchgd/
|
||||
permalink: /en/doc/qfileexchgd/
|
||||
redirect_from:
|
||||
- /doc/Qfileexchgd/
|
||||
- /wiki/Qfileexchgd/
|
||||
---
|
||||
|
||||
**This mechanism is obsolete as of Qubes Beta 1!**
|
||||
==================================================
|
||||
|
||||
Please see this [page](/doc/Qfilecopy/) instead.
|
||||
Please see this [page](/en/doc/qfilecopy/) instead.
|
||||
|
||||
qfilexchgd, the Qubes file exchange daemon
|
||||
==========================================
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qmemman
|
||||
permalink: /doc/Qmemman/
|
||||
redirect_from: /wiki/Qmemman/
|
||||
permalink: /en/doc/qmemman/
|
||||
redirect_from:
|
||||
- /doc/Qmemman/
|
||||
- /wiki/Qmemman/
|
||||
---
|
||||
|
||||
qmemman, Qubes memory manager
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qrexec
|
||||
permalink: /doc/Qrexec/
|
||||
redirect_from: /wiki/Qrexec/
|
||||
permalink: /en/doc/qrexec/
|
||||
redirect_from:
|
||||
- /doc/Qrexec/
|
||||
- /wiki/Qrexec/
|
||||
---
|
||||
|
||||
Command execution in VM (and Qubes RPC)
|
||||
@ -159,4 +161,4 @@ As previously noted, Qubes aims to provide mechanisms that are very simple and t
|
||||
Qubes RPC internals
|
||||
-------------------
|
||||
|
||||
The internal implementation of qrexec in Qubes R2 is described [here](/doc/Qrexec2Implementation/), and in Qubes R3 [here](/doc/Qrexec3Implementation/).
|
||||
The internal implementation of qrexec in Qubes R2 is described [here](/en/doc/qrexec2-implementation/), and in Qubes R3 [here](/en/doc/qrexec3-implementation/).
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qrexec2Implementation
|
||||
permalink: /doc/Qrexec2Implementation/
|
||||
redirect_from: /wiki/Qrexec2Implementation/
|
||||
permalink: /en/doc/qrexec2-implementation/
|
||||
redirect_from:
|
||||
- /doc/Qrexec2Implementation/
|
||||
- /wiki/Qrexec2Implementation/
|
||||
---
|
||||
|
||||
Implementation of qrexec in Qubes R2
|
||||
====================================
|
||||
|
||||
This page describes implementation of the [qrexec framework](/doc/Qrexec/) in Qubes OS R2. Note that the implementation has changed significantly in Qubes R3 (see [Qrexec3Implementation](/doc/Qrexec3Implementation/)), although the user API reminded backwards compatible (i.e. qrexec apps written for Qubes R2 should run without modifications on Qubes R3).
|
||||
This page describes implementation of the [qrexec framework](/en/doc/qrexec/) in Qubes OS R2. Note that the implementation has changed significantly in Qubes R3 (see [Qrexec3Implementation](/en/doc/qrexec3-implementation/)), although the user API reminded backwards compatible (i.e. qrexec apps written for Qubes R2 should run without modifications on Qubes R3).
|
||||
|
||||
Dom0 tools implementation
|
||||
-------------------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qrexec3
|
||||
permalink: /doc/Qrexec3/
|
||||
redirect_from: /wiki/Qrexec3/
|
||||
permalink: /en/doc/qrexec3/
|
||||
redirect_from:
|
||||
- /doc/Qrexec3/
|
||||
- /wiki/Qrexec3/
|
||||
---
|
||||
|
||||
Command execution in VM (and Qubes RPC)
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Qrexec3Implementation
|
||||
permalink: /doc/Qrexec3Implementation/
|
||||
redirect_from: /wiki/Qrexec3Implementation/
|
||||
permalink: /en/doc/qrexec3-implementation/
|
||||
redirect_from:
|
||||
- /doc/Qrexec3Implementation/
|
||||
- /wiki/Qrexec3Implementation/
|
||||
---
|
||||
|
||||
Implementation of qrexec in Qubes R3
|
||||
====================================
|
||||
|
||||
This page describes implementation of the [qrexec framework](/doc/Qrexec/) in Qubes OS R3.
|
||||
This page describes implementation of the [qrexec framework](/en/doc/qrexec/) in Qubes OS R3.
|
||||
|
||||
Qrexec framework consists of a number of processes communicating with each other using common IPC protocol (described in detail below). Components residing in the same domain use pipes as the underlying transport medium, while components in separate domains use vchan link.
|
||||
|
||||
|
||||
165
doc.md
165
doc.md
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Documentation
|
||||
permalink: /doc/
|
||||
permalink: /en/doc/
|
||||
redirect_from:
|
||||
- /doc/
|
||||
- "/doc/UserDoc/"
|
||||
- "/wiki/UserDoc/"
|
||||
- "/doc/QubesDocs/"
|
||||
@ -14,17 +15,17 @@ Qubes OS Documentation
|
||||
|
||||
The Basics
|
||||
----------
|
||||
* [A Simple Introduction to Qubes](/intro/)
|
||||
* [Getting Started](/doc/GettingStarted/)
|
||||
* [Users' FAQ](/doc/UserFaq/)
|
||||
* [Mailing Lists](/doc/QubesLists/)
|
||||
* [A Simple Introduction to Qubes](/en/intro/)
|
||||
* [Getting Started](/en/doc/getting-started/)
|
||||
* [Users' FAQ](/en/doc/user-faq/)
|
||||
* [Mailing Lists](/en/doc/mailing-lists/)
|
||||
* [Further reading: How is Qubes different from...?](http://blog.invisiblethings.org/2012/09/12/how-is-qubes-os-different-from.html)
|
||||
* [Further reading: Why Qubes is more than a collection of VMs](http://www.invisiblethingslab.com/resources/2014/Software_compartmentalization_vs_physical_separation.pdf)
|
||||
|
||||
|
||||
Choosing Your Hardware
|
||||
----------------------
|
||||
* [System Requirements](/doc/SystemRequirements/)
|
||||
* [System Requirements](/en/doc/system-requirements/)
|
||||
* [Hardware Compatibility List (HCL)](/hcl)
|
||||
* Qubes Certified Laptops ([coming soon!](https://twitter.com/Puri_sm/status/644963433293717504))
|
||||
|
||||
@ -32,120 +33,120 @@ Choosing Your Hardware
|
||||
Installing Qubes
|
||||
----------------
|
||||
* [Use Qubes without installing: Qubes Live USB (alpha)](https://groups.google.com/d/msg/qubes-users/IQdCEpkooto/iyMh3LuzCAAJ)
|
||||
* [How to Install Qubes](/doc/InstallationGuide/)
|
||||
* [How to Install Qubes](/en/doc/installation-guide/)
|
||||
* [Qubes Downloads](/downloads/)
|
||||
* [Why and How to Verify Signatures](/doc/VerifyingSignatures/)
|
||||
* [Security Considerations when Installing](/doc/InstallSecurity/)
|
||||
* [Why and How to Verify Signatures](/en/doc/verifying-signatures/)
|
||||
* [Security Considerations when Installing](/en/doc/install-security/)
|
||||
|
||||
|
||||
Common Tasks
|
||||
------------
|
||||
* [Copying and Pasting Text Between Domains](/doc/CopyPaste/)
|
||||
* [Copying and Moving Files Between Domains](/doc/CopyingFiles/)
|
||||
* [Copying Files to and from dom0](/doc/CopyToDomZero/)
|
||||
* [Mounting USB Drives to AppVMs](/doc/StickMounting/)
|
||||
* [Updating Software in dom0](/doc/SoftwareUpdateDom0/)
|
||||
* [Updating and Installing Software in VMs](/doc/SoftwareUpdateVM/)
|
||||
* [Backup, Restoration, and Migration](/doc/BackupRestore/)
|
||||
* [Disposable VMs](/doc/DisposableVms/)
|
||||
* [Managing Application Shortcuts](/doc/ManagingAppVmShortcuts/)
|
||||
* [Enabling Fullscreen Mode](/doc/FullScreenMode/)
|
||||
* [Copying and Pasting Text Between Domains](/en/doc/copy-paste/)
|
||||
* [Copying and Moving Files Between Domains](/en/doc/copying-files/)
|
||||
* [Copying Files to and from dom0](/en/doc/copy-to-dom0/)
|
||||
* [Mounting USB Drives to AppVMs](/en/doc/stick-mounting/)
|
||||
* [Updating Software in dom0](/en/doc/software-update-dom0/)
|
||||
* [Updating and Installing Software in VMs](/en/doc/software-update-vm/)
|
||||
* [Backup, Restoration, and Migration](/en/doc/backup-restore/)
|
||||
* [Disposable VMs](/en/doc/dispvm/)
|
||||
* [Managing Application Shortcuts](/en/doc/managing-appvm-shortcuts/)
|
||||
* [Enabling Fullscreen Mode](/en/doc/full-screen-mode/)
|
||||
|
||||
|
||||
Managing Operating Systems within Qubes
|
||||
---------------------------------------
|
||||
* [TemplateVMs](/doc/Templates/)
|
||||
* [Templates: Fedora - minimal](/doc/Templates/FedoraMinimal/)
|
||||
* [Templates: Debian](/doc/Templates/Debian/)
|
||||
* [Templates: Archlinux](/doc/Templates/Archlinux/)
|
||||
* [Templates: Ubuntu](/doc/Templates/Ubuntu/)
|
||||
* [Templates: Whonix](/doc/Templates/Whonix/)
|
||||
* [Installing and Using Windows-based AppVMs (Qubes R2 Beta 3 and later)](/doc/WindowsAppVms/)
|
||||
* [Creating and Using HVM and Windows Domains (Qubes R2+)](/doc/HvmCreate/)
|
||||
* [Advanced options and troubleshooting of Qubes Tools for Windows (R3)](/doc/WindowsTools3/)
|
||||
* [Advanced options and troubleshooting of Qubes Tools for Windows (R2)](/doc/WindowsTools2/)
|
||||
* [Uninstalling Qubes Tools for Windows 2.x](/doc/UninstallingWindowsTools2/)
|
||||
* [Upgrading the Fedora 20 Template](/doc/FedoraTemplateUpgrade20/)
|
||||
* [Upgrading the Fedora 18 Template](/doc/FedoraTemplateUpgrade18/)
|
||||
* [Tips for Using Linux in an HVM](/doc/LinuxHVMTips/)
|
||||
* [TemplateVMs](/en/doc/templates/)
|
||||
* [Templates: Fedora - minimal](/en/doc/templates/fedora-minimal/)
|
||||
* [Templates: Debian](/en/doc/templates/debian/)
|
||||
* [Templates: Archlinux](/en/doc/templates/archlinux/)
|
||||
* [Templates: Ubuntu](/en/doc/templates/ubuntu/)
|
||||
* [Templates: Whonix](/en/doc/templates/whonix/)
|
||||
* [Installing and Using Windows-based AppVMs (Qubes R2 Beta 3 and later)](/en/doc/windows-appvms/)
|
||||
* [Creating and Using HVM and Windows Domains (Qubes R2+)](/en/doc/hvm-create/)
|
||||
* [Advanced options and troubleshooting of Qubes Tools for Windows (R3)](/en/doc/windows-tools-3/)
|
||||
* [Advanced options and troubleshooting of Qubes Tools for Windows (R2)](/en/doc/windows-tools-2/)
|
||||
* [Uninstalling Qubes Tools for Windows 2.x](/en/doc/uninstalling-windows-tools-2/)
|
||||
* [Upgrading the Fedora 20 Template](/en/doc/fedora-template-upgrade-20/)
|
||||
* [Upgrading the Fedora 18 Template](/en/doc/fedora-template-upgrade-18/)
|
||||
* [Tips for Using Linux in an HVM](/en/doc/linux-hvm-tips/)
|
||||
* [Creating NetBSD VM](https://groups.google.com/group/qubes-devel/msg/4015c8900a813985)
|
||||
|
||||
|
||||
Security Guides
|
||||
---------------
|
||||
* [General Security Information](/doc/QubesSecurity/)
|
||||
* [Security Guidelines](/doc/SecurityGuidelines/)
|
||||
* [Understanding Qubes Firewall](/doc/QubesFirewall/)
|
||||
* [Understanding and Preventing Data Leaks](/doc/DataLeaks/)
|
||||
* [Installing Anti Evil Maid](/doc/AntiEvilMaid/)
|
||||
* [Using Multi-factor Authentication with Qubes](/doc/Multi-factorAuthentication/)
|
||||
* [Using GPG more securely in Qubes: Split GPG](/doc/SplitGpg/)
|
||||
* [Configuring YubiKey for user authentication](/doc/YubiKey/)
|
||||
* [Note regarding password-less root access in VM](/doc/VMSudo/)
|
||||
* [General Security Information](/en/doc/qubes-security/)
|
||||
* [Security Guidelines](/en/doc/security-guidelines/)
|
||||
* [Understanding Qubes Firewall](/en/doc/qubes-firewall/)
|
||||
* [Understanding and Preventing Data Leaks](/en/doc/data-leaks/)
|
||||
* [Installing Anti Evil Maid](/en/doc/anti-evil-maid/)
|
||||
* [Using Multi-factor Authentication with Qubes](/en/doc/multifactor-authentication/)
|
||||
* [Using GPG more securely in Qubes: Split GPG](/en/doc/split-gpg/)
|
||||
* [Configuring YubiKey for user authentication](/en/doc/yubi-key/)
|
||||
* [Note regarding password-less root access in VM](/en/doc/vm-sudo/)
|
||||
|
||||
|
||||
Configuration Guides
|
||||
--------------------
|
||||
* [Configuration Files](/doc/ConfigFiles/)
|
||||
* [How to Install a Transparent Tor ProxyVM (TorVM)](/doc/TorVM/)
|
||||
* [How to set up a ProxyVM as a VPN Gateway](/doc/VPN/)
|
||||
* [Storing AppVMs on Secondary Drives](/doc/SecondaryStorage/)
|
||||
* [Where are my external storage devices mounted?](/doc/ExternalDeviceMountPoint/)
|
||||
* [Resizing AppVM and HVM Disk Images](/doc/ResizeDiskImage/)
|
||||
* [Extending `root.img` Size](/doc/ResizeRootDiskImage/)
|
||||
* [Installing ZFS in Qubes](/doc/ZFS/)
|
||||
* [Mutt Guide](/doc/Mutt/)
|
||||
* [Postfix Guide](/doc/Postfix/)
|
||||
* [Fetchmail Guide](/doc/Fetchmail/)
|
||||
* [Configuration Files](/en/doc/config-files/)
|
||||
* [How to Install a Transparent Tor ProxyVM (TorVM)](/en/doc/torvm/)
|
||||
* [How to set up a ProxyVM as a VPN Gateway](/en/doc/vpn/)
|
||||
* [Storing AppVMs on Secondary Drives](/en/doc/secondary-storage/)
|
||||
* [Where are my external storage devices mounted?](/en/doc/external-device-mount-point/)
|
||||
* [Resizing AppVM and HVM Disk Images](/en/doc/resize-disk-image/)
|
||||
* [Extending `root.img` Size](/en/doc/resize-root-disk-image/)
|
||||
* [Installing ZFS in Qubes](/en/doc/zfs/)
|
||||
* [Mutt Guide](/en/doc/mutt/)
|
||||
* [Postfix Guide](/en/doc/postfix/)
|
||||
* [Fetchmail Guide](/en/doc/fetchmail/)
|
||||
* [Creating Custom NetVMs and ProxyVMs](http://theinvisiblethings.blogspot.com/2011/09/playing-with-qubes-networking-for-fun.html)
|
||||
* [How to make proxy for individual tcp connection from networkless VM](https://groups.google.com/group/qubes-devel/msg/4ca950ab6d7cd11a)
|
||||
* [HTTP filtering proxy in Qubes firewall VM](https://groups.google.com/group/qubes-devel/browse_thread/thread/5252bc3f6ed4b43e/d881deb5afaa2a6c#39c95d63fccca12b)
|
||||
* [Adding Bridge Support to the NetVM (EXPERIMENTAL)](/doc/NetworkBridgeSupport/)
|
||||
* [Assigning PCI Devices to AppVMs](/doc/AssigningDevices/)
|
||||
* [Enabling TRIM for SSD disks](/doc/DiskTRIM/)
|
||||
* [Configuring a Network Printer](/doc/NetworkPrinter/)
|
||||
* [Using External Audio Devices](/doc/ExternalAudio/)
|
||||
* [Adding Bridge Support to the NetVM (EXPERIMENTAL)](/en/doc/network-bridge-support/)
|
||||
* [Assigning PCI Devices to AppVMs](/en/doc/assigning-devices/)
|
||||
* [Enabling TRIM for SSD disks](/en/doc/disk-trim/)
|
||||
* [Configuring a Network Printer](/en/doc/network-printer/)
|
||||
* [Using External Audio Devices](/en/doc/external-audio/)
|
||||
* [Booting with GRUB2 and GPT](https://groups.google.com/group/qubes-devel/browse_thread/thread/e4ac093cabd37d2b/d5090c20d92c4128#d5090c20d92c4128)
|
||||
* [Rxvt Guide](/doc/Rxvt/)
|
||||
* [Rxvt Guide](/en/doc/rxvt/)
|
||||
|
||||
|
||||
Customization Guides
|
||||
--------------------
|
||||
* [DispVM Customization](/doc/DispVMCustomization/)
|
||||
* [XFCE Installation in dom0](/doc/XFCE/)
|
||||
* [DispVM Customization](/en/doc/dispvm-customization/)
|
||||
* [XFCE Installation in dom0](/en/doc/xfce/)
|
||||
* [Customizing the GUI experience with KDE](https://groups.google.com/d/topic/qubes-users/KhfzF19NG1s/discussion)
|
||||
* [Language Localization](/doc/LanguageLocalization/)
|
||||
* [Language Localization](/en/doc/language-localization/)
|
||||
|
||||
|
||||
Troubleshooting
|
||||
---------------
|
||||
* [Home directory is out of disk space error](/doc/OutOfmemory/)
|
||||
* [Home directory is out of disk space error](/en/doc/out-of-memory/)
|
||||
* [Installing on system with new AMD GPU (missing firmware problem)](https://groups.google.com/group/qubes-devel/browse_thread/thread/e27a57b0eda62f76)
|
||||
* [How to install an Nvidia driver in dom0](/doc/InstallNvidiaDriver/)
|
||||
* [How to install an Nvidia driver in dom0](/en/doc/install-nvidia-driver/)
|
||||
* [Solving problems with Macbook Air 2012](https://groups.google.com/group/qubes-devel/browse_thread/thread/b8b0d819d2a4fc39/d50a72449107ab21#8a9268c09d105e69)
|
||||
* [Getting Sony Vaio Z laptop to work with Qubes](/doc/SonyVaioTinkering/)
|
||||
* [Getting Lenovo 450 to work with Qubes](/doc/Lenovo450Tinkering/)
|
||||
* [Getting Sony Vaio Z laptop to work with Qubes](/en/doc/sony-vaio-tinkering/)
|
||||
* [Getting Lenovo 450 to work with Qubes](/en/doc/lenovo450-tinkering/)
|
||||
|
||||
|
||||
Reference Pages
|
||||
---------------
|
||||
* [Dom0 Command-Line Tools](/doc/DomZeroTools/)
|
||||
* [DomU Command-Line Tools](/doc/VmTools/)
|
||||
* [Glossary of Qubes Terminology](/doc/Glossary/)
|
||||
* [Qubes Service Framework](/doc/QubesService/)
|
||||
* [Command Execution in VMs (and Qubes RPC)](/doc/Qrexec/)
|
||||
* [Dom0 Command-Line Tools](/en/doc/dom0-tools/)
|
||||
* [DomU Command-Line Tools](/en/doc/vm-tools/)
|
||||
* [Glossary of Qubes Terminology](/en/doc/glossary/)
|
||||
* [Qubes Service Framework](/en/doc/qubes-service/)
|
||||
* [Command Execution in VMs (and Qubes RPC)](/en/doc/qrexec/)
|
||||
|
||||
|
||||
For Developers
|
||||
--------------
|
||||
* [System Documentation](/doc/SystemDoc/)
|
||||
* [Developers' FAQ](/doc/DevelFaq/)
|
||||
* [How to Contribute to the Qubes OS Project](/doc/contributing/)
|
||||
* [Bug Reporting Guide](/doc/reporting-bugs/)
|
||||
* [Source Code](/doc/SourceCode/)
|
||||
* [Qubes OS Version Scheme](/doc/VersionScheme/)
|
||||
* [Coding Guidelines](/doc/CodingStyle/)
|
||||
* [Documentation Guidelines](/doc/doc-guidelines/)
|
||||
* [Books for Developers](/doc/DevelBooks/)
|
||||
* [Research Papers](/doc/QubesResearch/)
|
||||
* [Licensing](/doc/license/)
|
||||
* [System Documentation](/en/doc/system-doc/)
|
||||
* [Developers' FAQ](/en/doc/devel-faq/)
|
||||
* [How to Contribute to the Qubes OS Project](/en/doc/contributing/)
|
||||
* [Bug Reporting Guide](/en/doc/reporting-bugs/)
|
||||
* [Source Code](/en/doc/source-code/)
|
||||
* [Qubes OS Version Scheme](/en/doc/version-scheme/)
|
||||
* [Coding Guidelines](/en/doc/coding-style/)
|
||||
* [Documentation Guidelines](/en/doc/doc-guidelines/)
|
||||
* [Books for Developers](/en/doc/devel-books/)
|
||||
* [Research Papers](/en/doc/qubes-research/)
|
||||
* [Licensing](/en/doc/license/)
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
---
|
||||
layout: doc
|
||||
title: HCL
|
||||
permalink: /doc/HCL/
|
||||
permalink: /en/doc/hcl/
|
||||
redirect_from:
|
||||
- /doc/HCL/
|
||||
- /wiki/HCL/
|
||||
- /wiki/HCLR1/
|
||||
- /wiki/HCL-R2B2/
|
||||
@ -15,7 +16,7 @@ The [HCL](/hcl) is a compilation of reports generated and submitted by users acr
|
||||
**Note:**
|
||||
Except in the case of developer-reported entries, the Qubes team has not independently verified the accuracy of these reports.
|
||||
Please first consult the data sheets (CPU, chipset, motherboard) prior to buying new hardware for Qubes.
|
||||
Meet the [SystemRequirements](/doc/SystemRequirements/) and search particular for support of:
|
||||
Meet the [SystemRequirements](/en/doc/system-requirements/) and search particular for support of:
|
||||
|
||||
- HVM ("AMD virtualization (AMD-V)", "Intel virtualization (VT-x)", "VIA virtualization (VIA VT)")
|
||||
- IOMMU ("AMD I/O Virtualization Technology (AMD-Vi)", "Intel Virtualization Technology for Directed I/O (VT-d)")
|
||||
@ -35,7 +36,7 @@ In order to generate a HCL report in Qubes, simply open a terminal in dom0 (KDE:
|
||||
(Note: If you are working with a new Qubes installation, you may need to update your system in order to download this script.)
|
||||
|
||||
You are encouraged to submit your HCL report for the benefit of further Qubes development and other users.
|
||||
If you would like to submit your HCL report, please send the **HCL Info** `.txt` file to [\`qubes-users@googlegroups.com\`](/doc/QubesLists/) with the subject `HCL - <your machine model name>`.
|
||||
If you would like to submit your HCL report, please send the **HCL Info** `.txt` file to [\`qubes-users@googlegroups.com\`](/en/doc/qubes-lists/) with the subject `HCL - <your machine model name>`.
|
||||
Please include any useful information about any Qubes features you may have tested (see the legend below), as well as general machine compatibility (video, networking, sleep, etc.).
|
||||
If you have problems with your hardware try a different kernel in the [Troubleshooting menu](/doc/InstallationGuideR2rc1/#troubleshooting-problems-with-the-installer).
|
||||
Please consider sending the **HCL Support Files** `.cpio.gz` file as well.
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: SystemRequirements
|
||||
permalink: /doc/SystemRequirements/
|
||||
redirect_from: /wiki/SystemRequirements/
|
||||
permalink: /en/doc/system-requirements/
|
||||
redirect_from:
|
||||
- /doc/SystemRequirements/
|
||||
- /wiki/SystemRequirements/
|
||||
---
|
||||
|
||||
System Requirements
|
||||
@ -21,7 +23,7 @@ Recommended
|
||||
|
||||
- Fast SSD (strongly recommended)
|
||||
- Intel GPU (strongly preferred)
|
||||
- Nvidia GPUs may require significant [troubleshooting](/doc/InstallNvidiaDriver/).
|
||||
- Nvidia GPUs may require significant [troubleshooting](/en/doc/install-nvidia-driver/).
|
||||
- ATI GPUs have not been formally tested (but see the [Hardware Compatibility List](/hcl/)).
|
||||
- Intel VT-x or AMD-v technology (required for running HVM domains, such as Windows-based AppVMs)
|
||||
- Intel VT-d or AMD IOMMU technology (required for effective isolation of network VMs)
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: InstallSecurity
|
||||
permalink: /doc/InstallSecurity/
|
||||
redirect_from: /wiki/InstallSecurity/
|
||||
permalink: /en/doc/install-security/
|
||||
redirect_from:
|
||||
- /doc/InstallSecurity/
|
||||
- /wiki/InstallSecurity/
|
||||
---
|
||||
|
||||
# Installation Security Considerations #
|
||||
|
||||
@ -1,16 +1,34 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Installation Guide
|
||||
permalink: /doc/InstallationGuide/
|
||||
redirect_from: /wiki/InstallationGuide/
|
||||
redirect_from: /doc/InstallationGuideR1/
|
||||
redirect_from: /doc/InstallationGuideR2B1/
|
||||
redirect_from: /doc/InstallationGuideR2B2/
|
||||
redirect_from: /doc/InstallationGuideR2B3/
|
||||
redirect_from: /doc/InstallationGuideR2rc1/
|
||||
redirect_from: /doc/InstallationGuideR2rc2/
|
||||
redirect_from: /doc/InstallationGuideR3.0rc1/
|
||||
redirect_from: /doc/InstallationGuideR3.0rc2/
|
||||
permalink: /en/doc/installation-guide/
|
||||
redirect_from:
|
||||
- /doc/InstallationGuide/
|
||||
- /wiki/InstallationGuide/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR1/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR2B1/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR2B2/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR2B3/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR2rc1/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR2rc2/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR3.0rc1/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/InstallationGuideR3.0rc2/
|
||||
---
|
||||
|
||||
Installation Guide
|
||||
@ -33,7 +51,7 @@ Note: We don't recommend installing Qubes in a virtual machine! It will likely n
|
||||
Download installer ISO
|
||||
----------------------
|
||||
|
||||
See [this page](/doc/QubesDownloads/) for ISO downloads. Remember, we have absolutely no control over those servers, and so you should be assuming that they might be compromised, or just be serving a compromised ISOs because their operators decided so, for whatever reason. Always verify the digital signature on the downloaded ISO. See this [page](/doc/VerifyingSignatures/) for more info about how to download and verify our GPG keys, and then verify the downloaded ISO:
|
||||
See [this page](/doc/QubesDownloads/) for ISO downloads. Remember, we have absolutely no control over those servers, and so you should be assuming that they might be compromised, or just be serving a compromised ISOs because their operators decided so, for whatever reason. Always verify the digital signature on the downloaded ISO. See this [page](/en/doc/verifying-signatures/) for more info about how to download and verify our GPG keys, and then verify the downloaded ISO:
|
||||
|
||||
gpg -v Qubes-R2-x86_64-DVD.iso.asc
|
||||
|
||||
@ -70,9 +88,9 @@ See [release notes](/doc/releases/) of appropriate version.
|
||||
Getting Help
|
||||
------------
|
||||
|
||||
- **User manuals are [here](/doc/UserDoc/).** (Strongly recommended!)
|
||||
- **User manuals are [here](/en/doc/).** (Strongly recommended!)
|
||||
|
||||
- Developers documentation (normally not needed by users) is [here](/doc/SystemDoc/)
|
||||
- Developers documentation (normally not needed by users) is [here](/en/doc/system-doc/)
|
||||
|
||||
- If you don't find answer in the sources given above, write to the *qubes-users* mailing list (you don't need to be subscribed to the list, just send email to the address given below):
|
||||
- [https://groups.google.com/group/qubes-users](https://groups.google.com/group/qubes-users)
|
||||
|
||||
@ -1,9 +1,13 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UpgradeToR2
|
||||
permalink: /doc/UpgradeToR2/
|
||||
redirect_from: /doc/UpgradeToR2rc1/
|
||||
redirect_from: /wiki/UpgradeToR2rc1/
|
||||
permalink: /en/doc/upgrade-to-r2/
|
||||
redirect_from:
|
||||
- /doc/UpgradeToR2/
|
||||
- /doc/UpgradeToR2rc1/
|
||||
redirect_from:
|
||||
-
|
||||
- /wiki/UpgradeToR2rc1/
|
||||
---
|
||||
|
||||
Upgrading Qubes R2 Beta 3 to R2
|
||||
@ -11,7 +15,7 @@ Upgrading Qubes R2 Beta 3 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/BackupRestore/).**
|
||||
**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](/en/doc/backup-restore/).**
|
||||
|
||||
Upgrade Template and Standalone VM(s)
|
||||
-------------------------------------
|
||||
@ -22,7 +26,7 @@ Upgrade Template and Standalone VM(s)
|
||||
|
||||
While technically it is possible to use old Fedora 18 template on R2, it is strongly recommended to upgrade all the Template VMs and Standalone VMs, because Fedora 18 no longer receive security updates.
|
||||
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. If more than one template and/or Standalone VMs are used, then it is recommended to upgrade/replace all of them. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/doc/SoftwareUpdateVM/).
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. If more than one template and/or Standalone VMs are used, then it is recommended to upgrade/replace all of them. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/en/doc/software-update-vm/).
|
||||
|
||||
Upgrading dom0
|
||||
--------------
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UpgradeToR2B1
|
||||
permalink: /doc/UpgradeToR2B1/
|
||||
redirect_from: /wiki/UpgradeToR2B1/
|
||||
permalink: /en/doc/upgrade-to-r2b1/
|
||||
redirect_from:
|
||||
- /doc/UpgradeToR2B1/
|
||||
- /wiki/UpgradeToR2B1/
|
||||
---
|
||||
|
||||
Upgrading Qubes R1 to R2 Beta 1
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UpgradeToR2B2
|
||||
permalink: /doc/UpgradeToR2B2/
|
||||
redirect_from: /wiki/UpgradeToR2B2/
|
||||
permalink: /en/doc/upgrade-to-r2b2/
|
||||
redirect_from:
|
||||
- /doc/UpgradeToR2B2/
|
||||
- /wiki/UpgradeToR2B2/
|
||||
---
|
||||
|
||||
Upgrading Qubes R1 to R2 (beta2)
|
||||
================================
|
||||
|
||||
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/BackupRestore/).
|
||||
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](/en/doc/backup-restore/).
|
||||
|
||||
Upgrade all Template and Standalone VM(s)
|
||||
-----------------------------------------
|
||||
@ -1,23 +1,25 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UpgradeToR2B3
|
||||
permalink: /doc/UpgradeToR2B3/
|
||||
redirect_from: /wiki/UpgradeToR2B3/
|
||||
permalink: /en/doc/upgrade-to-r2b3/
|
||||
redirect_from:
|
||||
- /doc/UpgradeToR2B3/
|
||||
- /wiki/UpgradeToR2B3/
|
||||
---
|
||||
|
||||
Upgrading Qubes R2 Beta 2 to R2 Beta 3
|
||||
======================================
|
||||
|
||||
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/InstallationGuideR2B3/) of Qubes R2 Beta 3**.
|
||||
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](/en/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/BackupRestore/).**
|
||||
**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](/en/doc/backup-restore/).**
|
||||
|
||||
Experienced users may be comfortable accepting the risks of upgrading in-place. Such users may wish to first attempt an in-place upgrade. If nothing goes wrong, then some time and effort will have been saved. If something does go wrong, then the user can simply perform a clean installation, and no significant loss will have occurred (as long as the user [backed up](/doc/BackupRestore/) correctly!).
|
||||
Experienced users may be comfortable accepting the risks of upgrading in-place. Such users may wish to first attempt an in-place upgrade. If nothing goes wrong, then some time and effort will have been saved. If something does go wrong, then the user can simply perform a clean installation, and no significant loss will have occurred (as long as the user [backed up](/en/doc/backup-restore/) correctly!).
|
||||
|
||||
Upgrade all Template and Standalone VM(s)
|
||||
-----------------------------------------
|
||||
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/doc/SoftwareUpdateVM/). The steps described in this section should be repeated in *all* user's Template and Standalone VMs.
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/en/doc/software-update-vm/). The steps described in this section should be repeated in *all* user's Template and Standalone VMs.
|
||||
|
||||
It is critical to complete this step **before** proceeding to dom0 upgrade. Otherwise you will most likely ends with unusable system.
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Upgrade to R3.0
|
||||
permalink: /doc/UpgradeToR3.0/
|
||||
redirect_from: /doc/UpgradeToR3.0rc1/
|
||||
permalink: /en/doc/upgrade-to-r3.0/
|
||||
redirect_from:
|
||||
- /doc/UpgradeToR3.0/
|
||||
- /doc/UpgradeToR3.0rc1/
|
||||
---
|
||||
|
||||
Upgrading Qubes R2 to R3.0
|
||||
@ -10,16 +12,16 @@ 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!**
|
||||
|
||||
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/InstallationGuide/) of Qubes R3.0**.
|
||||
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](/en/doc/installation-guide/) of Qubes R3.0**.
|
||||
|
||||
**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/BackupRestore/).**
|
||||
**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](/en/doc/backup-restore/).**
|
||||
|
||||
Experienced users may be comfortable accepting the risks of upgrading in-place. Such users may wish to first attempt an in-place upgrade. If nothing goes wrong, then some time and effort will have been saved. If something does go wrong, then the user can simply perform a clean installation, and no significant loss will have occurred (as long as the user [backed up](/doc/BackupRestore/) correctly!).
|
||||
Experienced users may be comfortable accepting the risks of upgrading in-place. Such users may wish to first attempt an in-place upgrade. If nothing goes wrong, then some time and effort will have been saved. If something does go wrong, then the user can simply perform a clean installation, and no significant loss will have occurred (as long as the user [backed up](/en/doc/backup-restore/) correctly!).
|
||||
|
||||
Upgrade all Template and Standalone VM(s)
|
||||
-----------------------------------------
|
||||
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/doc/SoftwareUpdateVM/). The steps described in this section should be repeated in **all** user's Template and Standalone VMs.
|
||||
By default, in Qubes R2, there is only one Template VM, however users are free to create more Template VMs for special purposes, as well as Standalone VMs. More information on using multiple Template VMs, as well as Standalone VMs, can be found [here](/en/doc/software-update-vm/). The steps described in this section should be repeated in **all** user's Template and Standalone VMs.
|
||||
|
||||
It is critical to complete this step **before** proceeding to dom0 upgrade. Otherwise you will most likely end with unusable system.
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: VerifyingSignatures
|
||||
permalink: /doc/VerifyingSignatures/
|
||||
redirect_from: /wiki/VerifyingSignatures/
|
||||
permalink: /en/doc/verifying-signatures/
|
||||
redirect_from:
|
||||
- /doc/VerifyingSignatures/
|
||||
- /wiki/VerifyingSignatures/
|
||||
---
|
||||
|
||||
On Digital Signatures and Key Verification
|
||||
@ -48,7 +50,7 @@ For additional security we also publish the fingerprint of the Qubes Master Sign
|
||||
Key fingerprint = 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494
|
||||
uid Qubes Master Signing Key
|
||||
|
||||
There should also be a copy of this key at the project's main website, in the [Qubes Security Pack](/doc/SecurityPack/), and in the archives of the project's [developer](https://groups.google.com/forum/#!msg/qubes-devel/RqR9WPxICwg/kaQwknZPDHkJ) and [user](https://groups.google.com/d/msg/qubes-users/CLnB5uFu_YQ/ZjObBpz0S9UJ) mailing lists.
|
||||
There should also be a copy of this key at the project's main website, in the [Qubes Security Pack](/en/doc/security-pack/), and in the archives of the project's [developer](https://groups.google.com/forum/#!msg/qubes-devel/RqR9WPxICwg/kaQwknZPDHkJ) and [user](https://groups.google.com/d/msg/qubes-users/CLnB5uFu_YQ/ZjObBpz0S9UJ) mailing lists.
|
||||
|
||||
Once you have obtained the Qubes Master Signing Key ([`0x36879494`](https://keys.qubes-os.org/keys/qubes-master-signing-key.asc)), you should verify the fingerprint of this key very carefully by obtaining copies of the fingerprint from trustworthy independent sources and comparing them to the downloaded key's fingerprint to ensure they match. Then set its trust level to "ultimate" (oh, well), so that it can be used to automatically verify all the keys signed by the Qubes Master Signing Key:
|
||||
|
||||
@ -106,7 +108,7 @@ For example: Qubes OS Release 2 Signing Key ([`0x0A40E458`](https://keys.qubes-o
|
||||
gpg: Total number processed: 1
|
||||
gpg: imported: 1 (RSA: 1)
|
||||
|
||||
You can also download all the currently used developers' signing keys and current and older release signing keys (and also a copy of the Qubes Master Signing Key) from the [keys directory on our server](https://keys.qubes-os.org/keys/) and from the [Qubes Security Pack](/doc/SecurityPack/).
|
||||
You can also download all the currently used developers' signing keys and current and older release signing keys (and also a copy of the Qubes Master Signing Key) from the [keys directory on our server](https://keys.qubes-os.org/keys/) and from the [Qubes Security Pack](/en/doc/security-pack/).
|
||||
|
||||
The developer signing keys are set to be valid for 1 year only, while the Qubes Master Signing Key ([`0x36879494`](https://keys.qubes-os.org/keys/qubes-master-signing-key.asc)) has no expiration date. This latter key was generated and is kept only within a dedicated, air-gapped "vault" machine, and the private portion will (hopefully) never leave this isolated machine.
|
||||
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
layout: doc
|
||||
title: FedoraTemplateUpgrade
|
||||
permalink: /doc/FedoraTemplateUpgrade18/
|
||||
redirect_from: /wiki/FedoraTemplateUpgrade/
|
||||
permalink: /en/doc/fedora-template-upgrade-18/
|
||||
redirect_from:
|
||||
- /doc/FedoraTemplateUpgrade18/
|
||||
- /wiki/FedoraTemplateUpgrade/
|
||||
---
|
||||
|
||||
Upgrade of Fedora template
|
||||
==========================
|
||||
|
||||
(**Note:** There is a [newer version of this page for upgrading from Fedora 20 to Fedora 21](/doc/FedoraTemplateUpgrade20/).)
|
||||
(**Note:** There is a [newer version of this page for upgrading from Fedora 20 to Fedora 21](/en/doc/fedora-template-upgrade-20/).)
|
||||
|
||||
This instruction in simplified version of [official Fedora instruction](https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum). Note that only "yum" method will work in Qubes template VM (if you are curious why: mostly because template VM does not have own bootloader).
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: FedoraTemplateUpgrade
|
||||
permalink: /doc/FedoraTemplateUpgrade20/
|
||||
redirect_from: /wiki/FedoraTemplateUpgrade20/
|
||||
permalink: /en/doc/fedora-template-upgrade-20/
|
||||
redirect_from:
|
||||
- /doc/FedoraTemplateUpgrade20/
|
||||
- /wiki/FedoraTemplateUpgrade20/
|
||||
---
|
||||
|
||||
How to Upgrade Fedora Templates
|
||||
@ -195,7 +197,7 @@ As mentioned above, you may encounter the following `yum` error:
|
||||
|
||||
In this case, you have several options:
|
||||
|
||||
1. [Increase the TemplateVM's disk image size](/doc/ResizeDiskImage/).
|
||||
1. [Increase the TemplateVM's disk image size](/en/doc/resize-disk-image/).
|
||||
This is the solution mentioned in the main instructions above.
|
||||
2. Delete files in order to free up space. One way to do this is by
|
||||
uninstalling packages. You may then reinstalling them again after you
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: HvmCreate
|
||||
permalink: /doc/HvmCreate/
|
||||
redirect_from: /wiki/HvmCreate/
|
||||
permalink: /en/doc/hvm-create/
|
||||
redirect_from:
|
||||
- /doc/HvmCreate/
|
||||
- /wiki/HvmCreate/
|
||||
---
|
||||
|
||||
Creating and using HVM (fully virtualized) domains in Qubes 2
|
||||
@ -193,12 +195,12 @@ In the near future we plan on introducing shared template also for HVM domains,
|
||||
~~Installing Qubes support tools in Windows 7 VMs~~ (only for R2 Beta 2)
|
||||
------------------------------------------------------------------------
|
||||
|
||||
Note: the R2 Beta 3 (which is coming soon) has automated most of the actions described below -- please see [this page instead](/doc/WindowsAppVms/).
|
||||
Note: the R2 Beta 3 (which is coming soon) has automated most of the actions described below -- please see [this page instead](/en/doc/windows-appvms/).
|
||||
|
||||
Qubes support tools for Windows VMs is a set of programs and drivers that provide integration of Windows VMs with the rest of the Qubes system. Currently the following features become available for Windows VMs after installation of those tools:
|
||||
|
||||
- Support for [secure clipboard copy/paste](/doc/CopyPaste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/doc/CopyingFiles/) between the Windows VM and other AppVMs
|
||||
- Support for [secure clipboard copy/paste](/en/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/en/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- Support for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
|
||||
- Xen PV drivers for Windows that increase performance compared to qemu emulated devices
|
||||
|
||||
@ -294,7 +296,7 @@ And the screenshot below illustrates the Send To entries in a Windows VM that ca
|
||||
Assigning PCI devices to HVM domains
|
||||
------------------------------------
|
||||
|
||||
HVM domains (including Windows VMs) can be [assigned PCI devices](/doc/AssigningDevices/) just like normal AppVMs. E.g. one can assign one of the USB controllers to the Windows VM and should be able to use various devices that require Windows software, such as phones, electronic devices that are configured via FTDI, etc.
|
||||
HVM domains (including Windows VMs) can be [assigned PCI devices](/en/doc/assigning-devices/) just like normal AppVMs. E.g. one can assign one of the USB controllers to the Windows VM and should be able to use various devices that require Windows software, such as phones, electronic devices that are configured via FTDI, etc.
|
||||
|
||||
Once problem, however, at the moment, is that after the whole system gets suspend into S3 sleep, and subsequently resumed, such attached devices stop working and should be restarted within the VM. Under Windows this can be achieved by opening the Device Manager, selecting the actual device, such as a USB controller, and then first 'Disabling', and then 'Enabling' the device again. This is illustrated on the screenshot below:
|
||||
|
||||
@ -305,5 +307,5 @@ Further reading
|
||||
|
||||
Other documents related to HVM:
|
||||
|
||||
- [LinuxHVMTips](/doc/LinuxHVMTips/)
|
||||
- [LinuxHVMTips](/en/doc/linux-hvm-tips/)
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: LinuxHVMTips
|
||||
permalink: /doc/LinuxHVMTips/
|
||||
redirect_from: /wiki/LinuxHVMTips/
|
||||
permalink: /en/doc/linux-hvm-tips/
|
||||
redirect_from:
|
||||
- /doc/LinuxHVMTips/
|
||||
- /wiki/LinuxHVMTips/
|
||||
---
|
||||
|
||||
Tips for Linux in HVM domain
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Templates
|
||||
permalink: /doc/Templates/
|
||||
redirect_from: /wiki/Templates/
|
||||
permalink: /en/doc/templates/
|
||||
redirect_from:
|
||||
- /doc/Templates/
|
||||
- /wiki/Templates/
|
||||
---
|
||||
|
||||
Templates
|
||||
@ -15,7 +17,7 @@ additional software installed by default. This concept is described
|
||||
[here](/doc/GettingStarted/#appvms-domains-and-templatevms).
|
||||
|
||||
Some templates are available in ready to use binary form, but some of them are
|
||||
only as a source code, which can be built using [Qubes Builder](/doc/QubesBuilder/).
|
||||
only as a source code, which can be built using [Qubes Builder](/en/doc/qubes-builder/).
|
||||
Especially some templates "flavors" are available in source code form only.
|
||||
Take a look at [Qubes Builder
|
||||
documentation](https://github.com/QubesOS/qubes-builder/blob/master/README.md)
|
||||
@ -30,7 +32,7 @@ the source code we publish.
|
||||
|
||||
- Fedora
|
||||
- [Fedora - Minimal](/doc/Templates/FedoraMinimal)
|
||||
- [Debian](/doc/Templates/Debian/)
|
||||
- [Debian](/en/doc/templates/debian/)
|
||||
|
||||
Community Supported templates
|
||||
-----------------------------
|
||||
@ -44,7 +46,7 @@ In short - by installing those templates, you trust not only ITL and
|
||||
distribution maintainers, but also the template maintainer. It can also happen
|
||||
that those templates are somehow less stable, because we do not test them.
|
||||
|
||||
- [Whonix](/doc/Templates/Whonix/)
|
||||
- [Ubuntu](/doc/Templates/Ubuntu/)
|
||||
- [Archlinux](/doc/Templates/Archlinux/)
|
||||
- [Whonix](/en/doc/templates/whonix/)
|
||||
- [Ubuntu](/en/doc/templates/ubuntu/)
|
||||
- [Archlinux](/en/doc/templates/archlinux/)
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Archlinux template
|
||||
permalink: /doc/Templates/Archlinux/
|
||||
redirect_from: /wiki/Templates/Archlinux/
|
||||
permalink: /en/doc/templates/archlinux/
|
||||
redirect_from:
|
||||
- /doc/Templates/Archlinux/
|
||||
- /wiki/Templates/Archlinux/
|
||||
---
|
||||
|
||||
Archlinux template
|
||||
@ -25,7 +27,7 @@ Install
|
||||
-------
|
||||
|
||||
Currently we do not ship ready to use binary package. It can be compiled using
|
||||
[this instructions](/doc/BuildingArchlinuxTemplate/).
|
||||
[this instructions](/en/doc/building-archlinux-template/).
|
||||
|
||||
Olivier provides binary package build by himself, you can get it for:
|
||||
* Qubes R2 [here](https://groups.google.com/d/msgid/qubes-devel/54CE3FB1.3050708%40yahoo.fr).
|
||||
@ -36,4 +38,4 @@ Olivier provides binary package build by himself, you can get it for:
|
||||
Known issues
|
||||
------------
|
||||
|
||||
If you want to help in improving the template, feel free to [contribute](/doc/ContributingHowto/).
|
||||
If you want to help in improving the template, feel free to [contribute](/en/doc/contributing/).
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Debian
|
||||
permalink: /doc/Templates/Debian/
|
||||
redirect_from: /wiki/Templates/Debian/
|
||||
permalink: /en/doc/templates/debian/
|
||||
redirect_from:
|
||||
- /doc/Templates/Debian/
|
||||
- /wiki/Templates/Debian/
|
||||
---
|
||||
|
||||
Debian template(s)
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: FedoraMinimal
|
||||
permalink: /doc/Templates/FedoraMinimal/
|
||||
redirect_from: /wiki/Templates/FedoraMinimal/
|
||||
permalink: /en/doc/templates/fedora-minimal/
|
||||
redirect_from:
|
||||
- /doc/Templates/FedoraMinimal/
|
||||
- /wiki/Templates/FedoraMinimal/
|
||||
---
|
||||
|
||||
Fedora - minimal
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Ubuntu
|
||||
permalink: /doc/Templates/Ubuntu/
|
||||
redirect_from: /wiki/Templates/Ubuntu/
|
||||
permalink: /en/doc/templates/ubuntu/
|
||||
redirect_from:
|
||||
- /doc/Templates/Ubuntu/
|
||||
- /wiki/Templates/Ubuntu/
|
||||
---
|
||||
|
||||
Ubuntu template(s)
|
||||
@ -18,7 +20,7 @@ to redistribute a modified Ubuntu. The redistribution is not allowed by their
|
||||
Install
|
||||
-------
|
||||
|
||||
It can built using [Qubes Builder](/doc/QubesBuilder/). You can also access its
|
||||
It can built using [Qubes Builder](/en/doc/qubes-builder/). You can also access its
|
||||
documentation in the [source code
|
||||
repository](https://github.com/QubesOS/qubes-builder/blob/master/README.md).
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: Whonix template
|
||||
permalink: /doc/Templates/Whonix/
|
||||
redirect_from: /wiki/Templates/Whonix/
|
||||
permalink: /en/doc/templates/whonix/
|
||||
redirect_from:
|
||||
- /doc/Templates/Whonix/
|
||||
- /wiki/Templates/Whonix/
|
||||
---
|
||||
|
||||
Whonix template(s)
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: UninstallingWindowsTools2
|
||||
permalink: /doc/UninstallingWindowsTools2/
|
||||
redirect_from: /wiki/UninstallingWindowsTools2/
|
||||
permalink: /en/doc/uninstalling-windows-tools-2/
|
||||
redirect_from:
|
||||
- /doc/UninstallingWindowsTools2/
|
||||
- /wiki/UninstallingWindowsTools2/
|
||||
---
|
||||
|
||||
Uninstalling Qubes Tools for Windows v2.x
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: WindowsAppVms
|
||||
permalink: /doc/WindowsAppVms/
|
||||
redirect_from: /wiki/WindowsAppVms/
|
||||
permalink: /en/doc/windows-appvms/
|
||||
redirect_from:
|
||||
- /doc/WindowsAppVms/
|
||||
- /wiki/WindowsAppVms/
|
||||
---
|
||||
|
||||
Installing and using Windows-based AppVMs
|
||||
@ -13,8 +15,8 @@ Qubes provides special support for running Windows-based AppVMs. This requires t
|
||||
Qubes support tools for Windows is a set of programs and drivers that provide integration of Windows AppVMs with the rest of the Qubes system. Currently the following features are available for Windows VMs after installation of those tools:
|
||||
|
||||
- Seamless GUI mode that integrates apps windows onto the common Qubes trusted desktop (available on Qubes R2 Beta 3 and later)
|
||||
- Support for [secure clipboard copy/paste](/doc/CopyPaste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/doc/CopyingFiles/) between the Windows VM and other AppVMs
|
||||
- Support for [secure clipboard copy/paste](/en/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- Support for [secure file exchange](/en/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- Support for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
|
||||
- Xen PV drivers for Windows that increase performance compared to qemu emulated devices
|
||||
|
||||
@ -25,7 +27,7 @@ NOTE: Currently only 64-bit versions of Windows 7 are support by Qubes Windows T
|
||||
Installing Windows OS in a Qubes VM
|
||||
-----------------------------------
|
||||
|
||||
Please refer to [this page](/doc/HvmCreate/) for instructions on how to install Windows in a Qubes VM.
|
||||
Please refer to [this page](/en/doc/hvm-create/) for instructions on how to install Windows in a Qubes VM.
|
||||
|
||||
Installing Qubes support tools in Windows 7 VMs
|
||||
-----------------------------------------------
|
||||
@ -101,7 +103,7 @@ Qubes allows HVM VMs to share a common root filesystem from a select Template VM
|
||||
qvm-create --hvm-template win7-x64-template -l green
|
||||
~~~
|
||||
|
||||
... and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see [this page](/doc/HvmCreate/) instructions. However, it would make lots of sense to store the `C:\Users` directory on the 2nd disk which is automatically exposed by Qubes to all HVMs. This 2nd disk is backed by the `private.img` file in the AppVMs' and is not reset upon AppVMs reboot, so the user's directories and profiles would survive the AppVMs reboot, unlike the "root" filesystem which will be reverted to the "golden image" from the Template VM automatically. To facilitate such separation of user profiles, Qubes Windows Tools provide an option to automatically move `C:\Users` directory to the 2nd disk backed by `private.img`. It's a selectable feature of the installer, enabled by default. If that feature is selected during installation, completion of the process requires two reboots:
|
||||
... and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see [this page](/en/doc/hvm-create/) instructions. However, it would make lots of sense to store the `C:\Users` directory on the 2nd disk which is automatically exposed by Qubes to all HVMs. This 2nd disk is backed by the `private.img` file in the AppVMs' and is not reset upon AppVMs reboot, so the user's directories and profiles would survive the AppVMs reboot, unlike the "root" filesystem which will be reverted to the "golden image" from the Template VM automatically. To facilitate such separation of user profiles, Qubes Windows Tools provide an option to automatically move `C:\Users` directory to the 2nd disk backed by `private.img`. It's a selectable feature of the installer, enabled by default. If that feature is selected during installation, completion of the process requires two reboots:
|
||||
|
||||
- The private disk is initialized and formatted on the first reboot after tools installation. It can't be done **during** the installation because Xen mass storage drivers are not yet active.
|
||||
- User profiles are moved to the private disk on the next reboot after the private disk is initialized. Reboot is required because the "mover utility" runs very early in the boot process so OS can't yet lock any files in there. This can take some time depending on the profiles' size and because the GUI agent is not yet active dom0/Qubes Manager may complain that the AppVM failed to boot. That's a false alarm (you can increase AppVM's default boot timeout using `qvm-prefs`), the VM should appear "green" in Qubes Manager shortly after.
|
||||
@ -1,8 +1,10 @@
|
||||
---
|
||||
layout: doc
|
||||
title: WindowsTools2
|
||||
permalink: /doc/WindowsTools2/
|
||||
redirect_from: /wiki/WindowsTools2/
|
||||
permalink: /en/doc/windows-tools-2/
|
||||
redirect_from:
|
||||
- /doc/WindowsTools2/
|
||||
- /wiki/WindowsTools2/
|
||||
---
|
||||
|
||||
Qubes Tools for Windows: advanced settings and troubleshooting
|
||||
@ -34,7 +36,7 @@ If the install process fails you can retry it using the command line below to ge
|
||||
Uninstalling
|
||||
------------
|
||||
|
||||
See [this page](/doc/UninstallingWindowsTools2/).
|
||||
See [this page](/en/doc/uninstalling-windows-tools-2/).
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
@ -1,9 +1,13 @@
|
||||
---
|
||||
layout: doc
|
||||
title: WindowsTools
|
||||
permalink: /doc/WindowsTools3/
|
||||
redirect_from: /wiki/WindowsTools/
|
||||
redirect_from: /doc/WindowsTools/
|
||||
permalink: /en/doc/windows-tools-3/
|
||||
redirect_from:
|
||||
- /doc/WindowsTools3/
|
||||
- /wiki/WindowsTools/
|
||||
redirect_from:
|
||||
-
|
||||
- /doc/WindowsTools/
|
||||
---
|
||||
|
||||
Qubes Tools for Windows: advanced settings and troubleshooting
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user