mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-05-02 06:46:11 -04:00
Merge branch 'md-refactoring-links' of https://github.com/tokideveloper/qubes-doc into tokideveloper-md-refactoring-links
This commit is contained in:
Andrew David Wong
commit
d2fa42c1e9
72 changed files with 733 additions and 1481 deletions
|
|
@ -97,7 +97,7 @@ Default compiled-in device cipher parameters:
|
|||
|
||||
This means that, by default, Qubes inherits these upstream defaults:
|
||||
|
||||
- AES-128 [[1]][cryptsetup-faq][[2]][dm-crypt][[3]][tomb-238]
|
||||
- AES-128 [[1]](https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions)[[2]](https://wiki.archlinux.org/index.php/dm-crypt/Device_encryption)[[3]](https://github.com/dyne/Tomb/issues/238)
|
||||
- SHA-256
|
||||
- `/dev/urandom`
|
||||
- probably an `iter-time` of one second
|
||||
|
|
@ -162,6 +162,3 @@ Boot into the Qubes installer, then press `ctrl`+`alt`+`F2` to get a virtual con
|
|||
The default file systems are ext4 for `/boot` and `/`, and swap for `swap`.
|
||||
When you are finished, the Unknown list should go away, and all three mount points should be assigned. Proceed normally with the installation from there.
|
||||
|
||||
[cryptsetup-faq]: https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions
|
||||
[dm-crypt]: https://wiki.archlinux.org/index.php/dm-crypt/Device_encryption
|
||||
[tomb-238]: https://github.com/dyne/Tomb/issues/238
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Qubes Download Mirrors
|
|||
List of Download Mirrors
|
||||
------------------------
|
||||
|
||||
The full list of known Qubes download mirrors is available [here][mirror-list].
|
||||
The full list of known Qubes download mirrors is available [here](/downloads/#mirrors).
|
||||
|
||||
Instructions for Mirror Operators
|
||||
---------------------------------
|
||||
|
|
@ -24,10 +24,6 @@ helpful in streamlining the process.
|
|||
* We are happy to provide rsync or HTTP master.
|
||||
* Our preferred frequency is **once every 24 hours**, but anything up to once
|
||||
every 6-8 hours is fine.
|
||||
* For technical accommodations, please contact [Wojtek] or [Marek].
|
||||
* For website updates and fixes, please contact [Andrew].
|
||||
* For technical accommodations, please contact [Wojtek](/team/#wojtek-porczyk) or [Marek](/team/#marek-marczykowski-górecki).
|
||||
* For website updates and fixes, please contact [Andrew](/team/#andrew-david-wong).
|
||||
|
||||
[mirror-list]: /downloads/#mirrors
|
||||
[Wojtek]: /team/#wojtek-porczyk
|
||||
[Marek]: /team/#marek-marczykowski-górecki
|
||||
[Andrew]: /team/#andrew-david-wong
|
||||
|
|
|
|||
|
|
@ -19,18 +19,18 @@ There are several security matters to consider before and during the Qubes insta
|
|||
No operating system, not even Qubes, can help you if you're installing it on hardware that is already compromised.
|
||||
This includes CPUs, GPUs, SSDs, HDDs, the motherboard, BIOS/EFI/UEFI, and all relevant firmware.
|
||||
Unfortunately, in today's world of undetectable supply chain attacks, there are no easy solutions.
|
||||
(Tools like [Anti Evil Maid (AEM)][AEM] can help with *maintaining* the trustworthiness of your hardware, but not with establishing it in the first place.)
|
||||
Some users have chosen to use tools like [Coreboot], [Heads], and [Skulls].
|
||||
(Tools like [Anti Evil Maid (AEM)](/doc/anti-evil-maid/) can help with *maintaining* the trustworthiness of your hardware, but not with establishing it in the first place.)
|
||||
Some users have chosen to use tools like [Coreboot](https://www.coreboot.org/), [Heads](http://osresearch.net/), and [Skulls](https://github.com/merge/skulls).
|
||||
|
||||
## Verifying the Qubes ISO
|
||||
|
||||
You should [verify] the PGP signature on your Qubes ISO before you install from it.
|
||||
You should [verify](/security/verifying-signatures/) the PGP signature on your Qubes ISO before you install from it.
|
||||
However, if the machine on which you attempt the verification process is already compromised, it could falsely claim that a malicious ISO has a good signature.
|
||||
Therefore, in order to be certain that your Qubes ISO is trustworthy, you require a trustworthy machine.
|
||||
But how can you be certain *that* machine is trustworthy?
|
||||
Only by using another trusted machine, and so forth.
|
||||
This is a [classic problem].
|
||||
While various [solutions] have been proposed, the point is that each user must ultimately make a choice about whether to trust that a file is non-malicious.
|
||||
This is a [classic problem](https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf).
|
||||
While various [solutions](https://www.dwheeler.com/trusting-trust/) have been proposed, the point is that each user must ultimately make a choice about whether to trust that a file is non-malicious.
|
||||
|
||||
## Choosing an installation medium
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ From a Qubes-specific security perspective, each has certain pros and cons.
|
|||
|
||||
Pros:
|
||||
|
||||
* Works via USB, including with a [USB qube].
|
||||
* Works via USB, including with a [USB qube](/doc/usb-qubes/#creating-and-using-a-usb-qube).
|
||||
* Non-fixed capacity.
|
||||
(Easy to find one on which the ISO can fit.)
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Cons:
|
|||
(If the drive is mounted to a compromised machine, the ISO could be maliciously altered after it has been written to the drive.)
|
||||
* Untrustworthy firmware.
|
||||
(Firmware can be malicious even if the drive is new.
|
||||
Plugging a drive with rewritable firmware into a compromised machine can also [compromise the drive][BadUSB].
|
||||
Plugging a drive with rewritable firmware into a compromised machine can also [compromise the drive](https://srlabs.de/badusb/).
|
||||
Installing from a compromised drive could compromise even a brand new Qubes installation.)
|
||||
|
||||
### Optical discs
|
||||
|
|
@ -79,12 +79,3 @@ Cons:
|
|||
|
||||
Considering the pros and cons of each, perhaps a USB drive with non-rewritable (or at least cryptographically-signed) firmware and a physical write-protect switch might be the best option.
|
||||
|
||||
[AEM]: /doc/anti-evil-maid/
|
||||
[verify]: /security/verifying-signatures/
|
||||
[classic problem]: https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf
|
||||
[solutions]: https://www.dwheeler.com/trusting-trust/
|
||||
[USB qube]: /doc/usb-qubes/#creating-and-using-a-usb-qube
|
||||
[BadUSB]: https://srlabs.de/badusb/
|
||||
[Coreboot]: https://www.coreboot.org/
|
||||
[Heads]: http://osresearch.net/
|
||||
[Skulls]: https://github.com/merge/skulls
|
||||
|
|
|
|||
|
|
@ -37,16 +37,16 @@ Please read it carefully and thoroughly, as it contains important information fo
|
|||
See <a href="/doc/install-security/">installation security</a> for more information.
|
||||
</div>
|
||||
|
||||
Qubes OS has very specific [system requirements].
|
||||
To ensure compatibility, we strongly recommend using [Qubes-certified hardware].
|
||||
Qubes OS has very specific [system requirements](/doc/system-requirements/).
|
||||
To ensure compatibility, we strongly recommend using [Qubes-certified hardware](/doc/certified-hardware/).
|
||||
Other hardware may require you to perform significant troubleshooting.
|
||||
You may also find it helpful to consult the [Hardware Compatibility List].
|
||||
You may also find it helpful to consult the [Hardware Compatibility List](/hcl/).
|
||||
|
||||
Even on supported hardware, you must ensure that [IOMMU-based virtualization] is activated in the BIOS.
|
||||
Even on supported hardware, you must ensure that [IOMMU-based virtualization](https://en.wikipedia.org/wiki/Input%E2%80%93output_memory_management_unit#Virtualization) is activated in the BIOS.
|
||||
Without it, Qubes OS won't be able to enforce isolation.
|
||||
For Intel-based boards, this setting is called Intel Virtualization for Directed I/O (**Intel VT-d**) and for AMD-based boards, it is called AMD I/O Virtualization Technology (or simply **AMD-Vi**).
|
||||
This parameter should be activated in your computer's BIOS, alongside the standard Virtualization (**Intel VT-x**) and AMD Virtualization (**AMD-V**) extensions.
|
||||
This [external guide][intel-guide] made for Intel-based boards can help you figure out how to enter your BIOS to locate and activate those settings.
|
||||
This [external guide](https://web.archive.org/web/20200112220913/https://www.intel.in/content/www/in/en/support/articles/000007139/server-products.html) made for Intel-based boards can help you figure out how to enter your BIOS to locate and activate those settings.
|
||||
If those settings are not nested under the Advanced tab, you might find them under the Security tab.
|
||||
|
||||
<div class="alert alert-warning" role="alert">
|
||||
|
|
@ -58,7 +58,7 @@ If those settings are not nested under the Advanced tab, you might find them und
|
|||
|
||||
### Copying the ISO onto the installation medium
|
||||
|
||||
Start by [downloading][downloads] a Qubes ISO.
|
||||
Start by [downloading](/downloads/) a Qubes ISO.
|
||||
|
||||
<div class="alert alert-danger" role="alert">
|
||||
<i class="fa fa-exclamation-triangle"></i>
|
||||
|
|
@ -68,7 +68,7 @@ Start by [downloading][downloads] a Qubes ISO.
|
|||
</div>
|
||||
|
||||
Once the ISO has been verified as authentic, you should copy it onto the installation medium of your choice, such as a dual-layer DVD, a Blu-ray disc, or a USB drive.
|
||||
The size of each Qubes ISO is available on the [downloads] page by hovering over the download button.
|
||||
The size of each Qubes ISO is available on the [downloads](/downloads/) page by hovering over the download button.
|
||||
|
||||
<div class="alert alert-warning" role="alert">
|
||||
<i class="fa fa-exclamation-circle"></i>
|
||||
|
|
@ -90,7 +90,7 @@ $ sudo dd if=Qubes-RX-x86_64.iso of=/dev/sdY status=progress bs=1048576 && sync
|
|||
Change `Qubes-RX-x86_64.iso` to the filename of the version you're installing, and change `/dev/sdY` to the correct target device e.g., `/dev/sdc`).
|
||||
Make sure to write to the entire device (e.g., `/dev/sdc`) rather than just a single partition (e.g., `/dev/sdc1`).
|
||||
|
||||
On Windows, you can use the [Rufus] tool to write the ISO to a USB key.
|
||||
On Windows, you can use the [Rufus](https://rufus.akeo.ie/) tool to write the ISO to a USB key.
|
||||
MediaTest is not recommended.
|
||||
Be sure to select "DD image" mode (*after* selecting the Qubes ISO):
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ Be sure to select "DD image" mode (*after* selecting the Qubes ISO):
|
|||
|
||||
|
||||
|
||||
If you are an advanced user, and you would like to customize your installation, please see [custom installation].
|
||||
If you are an advanced user, and you would like to customize your installation, please see [custom installation](/doc/custom-install/).
|
||||
Otherwise, follow the instructions below.
|
||||
|
||||
## Installation
|
||||
|
|
@ -139,7 +139,7 @@ First, try rebooting your computer.
|
|||
If it still loads your currently installed operating system or does not detect your installation medium, make sure the boot order is set up appropriately.
|
||||
The process to change the boot order varies depending on the currently installed system and the motherboard manufacturer.
|
||||
If **Windows 10** is installed on your machine, you may need to follow specific instructions to change the boot order.
|
||||
This may require an [advanced reboot].
|
||||
This may require an [advanced reboot](https://support.microsoft.com/en-us/help/4026206/windows-10-find-safe-mode-and-other-startup-settings).
|
||||
|
||||
After the POST, you may have a chance to choose a boot device.
|
||||
You may wish to select the USB drive or DVD drive as a temporary boot option so that the next time you boot, your internal storage device will be selected first.
|
||||
|
|
@ -160,7 +160,7 @@ If the test fails, a window will pop up.
|
|||
|
||||
Do not panic.
|
||||
It may simply indicate that IOMMU-virtualization hasn't been activated in the BIOS.
|
||||
Return to the [hardware requirements] section to learn how to activate it.
|
||||
Return to the [hardware requirements](#hardware-requirements) section to learn how to activate it.
|
||||
If the setting is not configured correctly, it means that your hardware won't be able to leverage some Qubes security features, such as a strict isolation of the networking and USB hardware.
|
||||
|
||||
If the test passes, you will reach the installation summary screen.
|
||||
|
|
@ -211,18 +211,18 @@ Don't forget to select your time and date by clicking on the Time & Date entry.
|
|||
On the software selection tab, you can choose which software to install in Qubes OS.
|
||||
Two options are available:
|
||||
|
||||
* **Debian:** Select this option if you would like to use [Debian] qubes in addition to the default Fedora qubes.
|
||||
* **Whonix:** Select this option if you would like to use [Whonix] qubes.
|
||||
Whonix allows you to use [Tor] securely within Qubes.
|
||||
* **Debian:** Select this option if you would like to use [Debian](/doc/templates/debian/) qubes in addition to the default Fedora qubes.
|
||||
* **Whonix:** Select this option if you would like to use [Whonix](/doc/whonix/) qubes.
|
||||
Whonix allows you to use [Tor](https://www.torproject.org/) securely within Qubes.
|
||||
|
||||
Whonix lets you route some or all of your network traffic through Tor for greater privacy.
|
||||
Depending on your threat model, you may need to install Whonix templates right away.
|
||||
|
||||
Regardless of your choices on this screen, you will always be able to install these and other [TemplateVMs] later.
|
||||
Regardless of your choices on this screen, you will always be able to install these and other [TemplateVMs](/doc/templates/) later.
|
||||
If you're short on disk space, you may wish to deselect these options.
|
||||
|
||||
By default, Qubes OS comes preinstalled with the lightweight Xfce4 desktop environment.
|
||||
Other desktop environments will be available to you after the installation is completed, though they may not be officially supported (see [advanced configuration]).
|
||||
Other desktop environments will be available to you after the installation is completed, though they may not be officially supported (see [advanced configuration](/doc/#advanced-configuration)).
|
||||
|
||||
Press **Done** to go back to the installation summary screen.
|
||||
|
||||
|
|
@ -352,7 +352,7 @@ Congratulations, you are now ready to use Qubes OS!
|
|||
|
||||
### Updating
|
||||
|
||||
Next, [update] your installation to ensure you have the latest security updates.
|
||||
Next, [update](/doc/updating-qubes-os/) your installation to ensure you have the latest security updates.
|
||||
Frequently updating is one of the best ways to remain secure against new threats.
|
||||
|
||||
### Security
|
||||
|
|
@ -372,56 +372,26 @@ For more information about Qubes OS Project security, please see the [security c
|
|||
### Backups
|
||||
|
||||
It is extremely important to make regular backups so that you don't lose your data unexpectedly.
|
||||
The [Qubes backup system] allows you to do this securely and easily.
|
||||
The [Qubes backup system](/doc/backup-restore/) allows you to do this securely and easily.
|
||||
|
||||
### Submit your HCL report
|
||||
|
||||
Consider giving back to the Qubes community and helping other users by [generating and submitting a Hardware Compatibility List (HCL) report][hcl-howto].
|
||||
Consider giving back to the Qubes community and helping other users by [generating and submitting a Hardware Compatibility List (HCL) report](/doc/hcl/#generating-and-submitting-new-reports).
|
||||
|
||||
### Get Started
|
||||
|
||||
[Get Started] with Qubes, and read more about [Common Tasks] and [Managing Operating Systems within Qubes].
|
||||
[Get Started](/getting-started/) with Qubes, and read more about [Common Tasks](/doc/#common-tasks) and [Managing Operating Systems within Qubes](/doc/#managing-operating-systems-within-qubes).
|
||||
|
||||
## Getting help
|
||||
|
||||
* We work very hard to make the [documentation] accurate, comprehensive useful and user friendly.
|
||||
* We work very hard to make the [documentation](/doc/) accurate, comprehensive useful and user friendly.
|
||||
We urge you to read it! It may very well contain the answers to your questions.
|
||||
(Since the documentation is a community effort, we'd also greatly appreciate your help in [improving] it!)
|
||||
(Since the documentation is a community effort, we'd also greatly appreciate your help in [improving](/doc/doc-guidelines/) it!)
|
||||
|
||||
* If issues arise during installation, see the [Installation Troubleshooting](/doc/installation-troubleshooting) guide.
|
||||
|
||||
* If you don't find your answer in the documentation, please see [Help, Support, Mailing Lists, and Forum] for places to ask.
|
||||
* If you don't find your answer in the documentation, please see [Help, Support, Mailing Lists, and Forum](/support/) for places to ask.
|
||||
|
||||
* Please do **not** email individual members of the Qubes team with questions about installation or other problems.
|
||||
Instead, please see [Help, Support, Mailing Lists, and Forum] for appropriate places to ask questions.
|
||||
Instead, please see [Help, Support, Mailing Lists, and Forum](/support/) for appropriate places to ask questions.
|
||||
|
||||
[QSB #46]: /news/2019/01/23/qsb-46/
|
||||
[system requirements]: /doc/system-requirements/
|
||||
[Qubes-certified hardware]: /doc/certified-hardware/
|
||||
[Hardware Compatibility List]: /hcl/
|
||||
[live USB]: /doc/live-usb/
|
||||
[downloads]: /downloads/
|
||||
[verifying signatures]: /security/verifying-signatures/
|
||||
[security considerations]: /doc/install-security/
|
||||
[Custom Installation]: /doc/custom-install/
|
||||
[Upgrade Guides]: /doc/upgrade/
|
||||
[Rufus]: https://rufus.akeo.ie/
|
||||
[documentation]: /doc/
|
||||
[improving]: /doc/doc-guidelines/
|
||||
[Help, Support, Mailing Lists, and Forum]: /support/
|
||||
[update]: /doc/updating-qubes-os/
|
||||
[Qubes backup system]: /doc/backup-restore/
|
||||
[Common Tasks]: /doc/#common-tasks
|
||||
[Managing Operating Systems within Qubes]: /doc/#managing-operating-systems-within-qubes
|
||||
[installation security]: /doc/install-security/
|
||||
[IOMMU-based virtualization]: https://en.wikipedia.org/wiki/Input%E2%80%93output_memory_management_unit#Virtualization
|
||||
[intel-guide]: https://web.archive.org/web/20200112220913/https://www.intel.in/content/www/in/en/support/articles/000007139/server-products.html
|
||||
[advanced reboot]: https://support.microsoft.com/en-us/help/4026206/windows-10-find-safe-mode-and-other-startup-settings
|
||||
[hardware requirements]: #hardware-requirements
|
||||
[Debian]: /doc/templates/debian/
|
||||
[Whonix]: /doc/whonix/
|
||||
[Tor]: https://www.torproject.org/
|
||||
[TemplateVMs]: /doc/templates/
|
||||
[advanced configuration]: /doc/#advanced-configuration
|
||||
[hcl-howto]: /doc/hcl/#generating-and-submitting-new-reports
|
||||
[Get Started]: /getting-started/
|
||||
|
|
|
|||
|
|
@ -13,9 +13,9 @@ This page details the level and period of support for versions of operating syst
|
|||
## Qubes OS
|
||||
|
||||
Qubes OS releases are supported for **six months** after each subsequent major
|
||||
or minor release (see [Version Scheme]). The current release and past major
|
||||
releases are always available on the [Downloads] page, while all ISOs, including
|
||||
past minor releases, are available from our [download mirrors].
|
||||
or minor release (see [Version Scheme](/doc/version-scheme/)). The current release and past major
|
||||
releases are always available on the [Downloads](/downloads/) page, while all ISOs, including
|
||||
past minor releases, are available from our [download mirrors](/downloads/#mirrors).
|
||||
|
||||
| Qubes OS | Start Date | End Date | Status |
|
||||
| ----------- | ---------- | ---------- | --------------------- |
|
||||
|
|
@ -25,7 +25,7 @@ past minor releases, are available from our [download mirrors].
|
|||
| Release 3.1 | 2016-03-09 | 2017-03-29 | Unsupported |
|
||||
| Release 3.2 | 2016-09-29 | 2019-03-28 | Unsupported |
|
||||
| Release 4.0 | 2018-03-28 | TBA | Supported |
|
||||
| Release 4.1 | TBA | TBA | [In development][4.1] |
|
||||
| Release 4.1 | TBA | TBA | [In development](https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22Release+4.1%22+) |
|
||||
|
||||
### Note on point releases
|
||||
|
||||
|
|
@ -51,18 +51,18 @@ The table below shows the OS used for dom0 in each Qubes OS release.
|
|||
### Note on dom0 and EOL
|
||||
|
||||
Dom0 is isolated from domUs. DomUs can access only a few interfaces, such as Xen, device backends (in the dom0 kernel and in other VMs, such as the NetVM), and Qubes tools (gui-daemon, qrexec-daemon, etc.).
|
||||
These components are [security-critical], and we provide updates for all of them (when necessary), regardless of the support status of the base distribution.
|
||||
These components are [security-critical](/doc/security-critical-code/), and we provide updates for all of them (when necessary), regardless of the support status of the base distribution.
|
||||
For this reason, we consider it safe to continue using a given base distribution in dom0 even after it has reached end-of-life (EOL).
|
||||
|
||||
## TemplateVMs
|
||||
|
||||
The following table shows select [TemplateVM] versions that are currently supported.
|
||||
Currently, only [Fedora] and [Debian] TemplateVMs are officially supported by the Qubes OS Project.
|
||||
[Whonix] TemplateVMs are supported by our partner, the [Whonix Project].
|
||||
The following table shows select [TemplateVM](/doc/templates/) versions that are currently supported.
|
||||
Currently, only [Fedora](/doc/templates/fedora/) and [Debian](/doc/templates/debian/) TemplateVMs are officially supported by the Qubes OS Project.
|
||||
[Whonix](/doc/whonix/) TemplateVMs are supported by our partner, the [Whonix Project](https://www.whonix.org/).
|
||||
Qubes support for each TemplateVM ends when that upstream release reaches end-of-life (EOL), unless otherwise noted.
|
||||
In the case of Debian, support ends at regular EOL, not [LTS][Debian-LTS] EOL, unless otherwise noted.
|
||||
In the case of Debian, support ends at regular EOL, not [LTS](https://wiki.debian.org/LTS) EOL, unless otherwise noted.
|
||||
See [below](#note-on-whonix-support) for Whonix support details.
|
||||
For upstream EOL information, see [Fedora EOL][fedora-eol] and [Debian EOL][debian-eol].
|
||||
For upstream EOL information, see [Fedora EOL](https://fedoraproject.org/wiki/End_of_life) and [Debian EOL](https://wiki.debian.org/DebianReleases).
|
||||
|
||||
| Qubes OS | Fedora | Debian | Whonix |
|
||||
| ----------- | ------ | ---------------------------- | ------ |
|
||||
|
|
@ -73,7 +73,7 @@ For upstream EOL information, see [Fedora EOL][fedora-eol] and [Debian EOL][debi
|
|||
|
||||
### Note on Whonix support
|
||||
|
||||
[Whonix] TemplateVMs are supported by our partner, the [Whonix Project].
|
||||
[Whonix](/doc/whonix/) TemplateVMs are supported by our partner, the [Whonix Project](https://www.whonix.org/).
|
||||
The Whonix Project has set its own support policy for Whonix TemplateVMs in Qubes.
|
||||
|
||||
This policy requires Whonix TemplateVM users to stay reasonably close to the cutting edge by upgrading to new stable versions of Qubes OS and Whonix TemplateVMs within a month of their respective releases.
|
||||
|
|
@ -87,17 +87,3 @@ To be precise:
|
|||
|
||||
We aim to announce both types of events one month in advance in order to remind users to upgrade.
|
||||
|
||||
[Version Scheme]: /doc/version-scheme/
|
||||
[Downloads]: /downloads/
|
||||
[download mirrors]: /downloads/#mirrors
|
||||
[security-critical]: /doc/security-critical-code/
|
||||
[TemplateVM]: /doc/templates/
|
||||
[extended support]: /news/2018/03/28/qubes-40/#the-past-and-the-future
|
||||
[4.1]: https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22Release+4.1%22+
|
||||
[Fedora]: /doc/templates/fedora/
|
||||
[Debian]: /doc/templates/debian/
|
||||
[fedora-eol]: https://fedoraproject.org/wiki/End_of_life
|
||||
[debian-eol]: https://wiki.debian.org/DebianReleases
|
||||
[Whonix]: /doc/whonix/
|
||||
[Whonix Project]: https://www.whonix.org/
|
||||
[Debian-LTS]: https://wiki.debian.org/LTS
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ title: Testing New Releases and Updates
|
|||
Testing New Releases and Updates
|
||||
================================
|
||||
|
||||
Testing new Qubes OS releases and updates is one of the most helpful ways in which you can [contribute] to the Qubes OS Project.
|
||||
Testing new Qubes OS releases and updates is one of the most helpful ways in which you can [contribute](/doc/contributing/) to the Qubes OS Project.
|
||||
However, you should only attempt to do this if you know what you're doing.
|
||||
Never rely on code that is in testing for critical work!
|
||||
|
||||
|
|
@ -18,26 +18,26 @@ Releases
|
|||
|
||||
How to test upcoming Qubes OS releases:
|
||||
|
||||
* Use [qubes-builder] to build the latest release.
|
||||
* Use [qubes-builder](/doc/qubes-builder/) to build the latest release.
|
||||
* Test the latest release candidate (RC), if any is currently available.
|
||||
* (No support) Experiment with devel alpha ISOs found from time to time at [Qubes OpenQA](https://openqa.qubes-os.org/).
|
||||
|
||||
See [Version Scheme] for details about release versions and schedules.
|
||||
See [Release Checklist] for details about the RC process.
|
||||
See [Version Scheme](/doc/version-scheme/) for details about release versions and schedules.
|
||||
See [Release Checklist](/doc/releases/todo/) for details about the RC process.
|
||||
|
||||
Updates
|
||||
-------
|
||||
|
||||
How to test updates:
|
||||
|
||||
* Enable [dom0 testing repositories].
|
||||
* Enable [TemplateVM testing repositories].
|
||||
* Enable [dom0 testing repositories](/doc/software-update-dom0/#testing-repositories).
|
||||
* Enable [TemplateVM testing repositories](/doc/software-update-domu/#testing-repositories).
|
||||
|
||||
Every new update is first uploaded to the `security-testing` repository if it is a security update or `current-testing` if it is a normal update.
|
||||
The update remains in `security-testing` or `current-testing` for a minimum of one week.
|
||||
On occasion, an exception is made for a particularly critical security update, which is immediately pushed to the `current` stable repository.
|
||||
In general, however, security updates remain in `security-testing` for two weeks before migrating to `current`.
|
||||
Normal updates generally remain in `current-testing` until they have been sufficiently tested by the community, which can weeks or even months, depending on the amount of feedback received (see [Providing Feedback]).
|
||||
Normal updates generally remain in `current-testing` until they have been sufficiently tested by the community, which can weeks or even months, depending on the amount of feedback received (see [Providing Feedback](#providing-feedback)).
|
||||
"Sufficient testing" is, in practice, a fluid term that is up the developers' judgment. In general, it means either that no negative feedback and at least one piece of positive feedback has been received or that the package has been in `current-testing` for long enough, depending on the component and the complexity of the changes.
|
||||
|
||||
A limitation of the current testing setup is that it is only possible to migrate the *most recent version* of a package from `current-testing` to `current`.
|
||||
|
|
@ -49,19 +49,9 @@ Providing Feedback
|
|||
|
||||
If you're testing new releases or updates, we would be grateful for your feedback.
|
||||
|
||||
We use an [automated build process].
|
||||
For every package that is uploaded to a testing repository, a GitHub issue is created in the [updates-status] repository for tracking purposes.
|
||||
We use an [automated build process](https://github.com/QubesOS/qubes-infrastructure/blob/master/README.md).
|
||||
For every package that is uploaded to a testing repository, a GitHub issue is created in the [updates-status](https://github.com/QubesOS/updates-status/issues) repository for tracking purposes.
|
||||
We welcome any kind of feedback on any package in any testing repository.
|
||||
Even a simple <span class="fa fa-thumbs-up" title="Thumbs Up"></span> or <span class="fa fa-thumbs-down" title="Thumbs Down"></span> on the package's associated issue would help us to decide whether the package is ready to be migrated to a stable repository.
|
||||
If you [report a bug] in a package that is in a testing repository, please reference the appropriate issue in [updates-status].
|
||||
If you [report a bug](/doc/reporting-bugs/) in a package that is in a testing repository, please reference the appropriate issue in [updates-status](https://github.com/QubesOS/updates-status/issues).
|
||||
|
||||
[contribute]: /doc/contributing/
|
||||
[qubes-builder]: /doc/qubes-builder/
|
||||
[Version Scheme]: /doc/version-scheme/
|
||||
[Release Checklist]: /doc/releases/todo/
|
||||
[dom0 testing repositories]: /doc/software-update-dom0/#testing-repositories
|
||||
[TemplateVM testing repositories]: /doc/software-update-domu/#testing-repositories
|
||||
[automated build process]: https://github.com/QubesOS/qubes-infrastructure/blob/master/README.md
|
||||
[updates-status]: https://github.com/QubesOS/updates-status/issues
|
||||
[report a bug]: /doc/reporting-bugs/
|
||||
[Providing Feedback]: #providing-feedback
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Backup R3.2
|
|||
|
||||
7. If your backup verifies successfully, proceed to the next section.
|
||||
If it does not, **stop**.
|
||||
Go back and repeat the backup steps, review the documentation, and ask for [help].
|
||||
Go back and repeat the backup steps, review the documentation, and ask for [help](/support/).
|
||||
|
||||
Install R4.0
|
||||
------------
|
||||
|
|
@ -61,7 +61,7 @@ For further details, please see the [installation guide](/doc/installation-guide
|
|||
If you did not successfully verify your backup in the previous section, cancel the installation, and go back to do that now.
|
||||
|
||||
3. Complete the R4.0 installation.
|
||||
Ask for [help] if you run into trouble.
|
||||
Ask for [help](/support/) if you run into trouble.
|
||||
|
||||
4. If you are unable to successfully install R4.0 on your system, all is not lost.
|
||||
Use the R3.2 installer to reinstall R3.2, then restore from your backup.
|
||||
|
|
@ -119,4 +119,3 @@ Please see [Supported Versions](/doc/supported-versions/) for information on sup
|
|||
* [Upgrading Debian TemplateVMs](/doc/templates/debian/#upgrading)
|
||||
* [Updating Whonix TemplateVMs](https://www.whonix.org/wiki/Qubes/Update)
|
||||
|
||||
[help]: /support/
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Qubes OS Upgrade Guides
|
|||
=======================
|
||||
|
||||
These guides are for upgrading from one version of Qubes to another.
|
||||
If you're just looking to update your system while staying on the same version, see [Updating Qubes OS].
|
||||
If you're just looking to update your system while staying on the same version, see [Updating Qubes OS](/doc/updating-qubes-os/).
|
||||
|
||||
* [Upgrading from R1 to R2 Beta 1](/doc/upgrade-to-r2b1/)
|
||||
* [Upgrading from R1 to R2 Beta 2](/doc/upgrade-to-r2b2/)
|
||||
|
|
@ -21,4 +21,3 @@ If you're just looking to update your system while staying on the same version,
|
|||
* [Upgrading from R3.1 to R3.2](/doc/upgrade-to-r3.2/)
|
||||
* [Upgrading from R3.2 to R4.0](/doc/upgrade-to-r4.0/)
|
||||
|
||||
[Updating Qubes OS]: /doc/updating-qubes-os/
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ When enough development has been made, we announce the first stable version,
|
|||
like e.g. `3.0.0` (i.e. without `-rc`). This version is considered stable and
|
||||
we support it for some period. Core components are branched at this moment and
|
||||
bugfixes are backported from master branch. Please see [Help, Support, Mailing
|
||||
Lists, and Forum] for places to ask questions about stable releases. No major
|
||||
Lists, and Forum](/support/) for places to ask questions about stable releases. No major
|
||||
features and interface incompatibilities are to be included in this release. We
|
||||
release bugfixes as `3.0.1`, `3.0.2` and so on, while new features come into the
|
||||
next release e.g. `3.1-rcX`.
|
||||
|
|
@ -158,4 +158,3 @@ Check installed version
|
|||
If you want to know which version you are running, for example to report
|
||||
an issue, you can either check in the Qubes Manager menu under About / Qubes OS or in the file /etc/qubes-release in dom0. For the latter you can use a command like `cat /etc/qubes-release` in a dom0 terminal.
|
||||
|
||||
[Help, Support, Mailing Lists, and Forum]: /support/
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue