diff --git a/developer/releases/3.2/release-notes.md b/developer/releases/3.2/release-notes.md index f7b66dee..3fc0ef02 100644 --- a/developer/releases/3.2/release-notes.md +++ b/developer/releases/3.2/release-notes.md @@ -73,5 +73,5 @@ the instructions above. This will be time consuming process. [upgrade-r3.1]: /doc/releases/3.1/release-notes/#upgrading [backup]: /doc/backup-restore/ [qrexec-argument]: https://github.com/QubesOS/qubes-issues/issues/1876 -[qrexec-doc]: /doc/qrexec3/#service-argument-in-policy +[qrexec-doc]: /doc/qrexec/#service-argument-in-policy [github-release-notes]: https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed diff --git a/developer/releases/4.0/release-notes.md b/developer/releases/4.0/release-notes.md index 38a47501..30336924 100644 --- a/developer/releases/4.0/release-notes.md +++ b/developer/releases/4.0/release-notes.md @@ -115,7 +115,7 @@ We also provide [detailed instruction][upgrade-to-r4.0] for this procedure. [qrexec-proxy]: https://github.com/QubesOS/qubes-issues/issues/1854 [qrexec-policy-keywords]: https://github.com/QubesOS/qubes-issues/issues/865 [qrexec-confirm]: https://github.com/QubesOS/qubes-issues/issues/910 -[qrexec-doc]: /doc/qrexec3/#extra-keywords-available-in-qubes-40-and-later +[qrexec-doc]: /doc/qrexec/#specifying-vms-tags-types-targets-etc [storage]: https://github.com/QubesOS/qubes-issues/issues/1842 [vm-interface]: /doc/vm-interface/ [admin-api]: /news/2017/06/27/qubes-admin-api/ diff --git a/developer/services/qrexec2.md b/developer/services/qrexec2.md index 79ea7d14..1f5f3c48 100644 --- a/developer/services/qrexec2.md +++ b/developer/services/qrexec2.md @@ -231,7 +231,7 @@ surfaces that are exposed to untrusted or less trusted VMs in that case. # Qubes RPC internals # (*This is about the implementation of qrexec v2. For the implementation of -qrexec v3, see [here](/doc/qrexec3/#qubes-rpc-internals). Note that the user +qrexec v3, see [here](/doc/qrexec-internals/). Note that the user API in v3 is backward compatible: qrexec apps written for Qubes R2 should run without modification on Qubes R3.*) diff --git a/user/advanced-configuration/disposablevm-customization.md b/user/advanced-configuration/disposablevm-customization.md index 581da8b3..b4e9596b 100644 --- a/user/advanced-configuration/disposablevm-customization.md +++ b/user/advanced-configuration/disposablevm-customization.md @@ -48,7 +48,7 @@ Additionally you may want to set it as default DisposableVM Template: [user@dom0 ~]$ qubes-prefs default_dispvm custom-disposablevm-template -The above default is used whenever a qube request starting a new DisposableVM and do not specify which one (for example `qvm-open-in-dvm` tool). This can be also set in qube settings and will affect service calls from that qube. See [qrexec documentation](/doc/qrexec3/#extra-keywords-available-in-qubes-40-and-later) for details. +The above default is used whenever a qube request starting a new DisposableVM and do not specify which one (for example `qvm-open-in-dvm` tool). This can be also set in qube settings and will affect service calls from that qube. See [qrexec documentation](/doc/qrexec/#specifying-vms-tags-types-targets-etc) for details. If you wish to use the `fedora-minimal` template as a DisposableVM Template, see the "DisposableVM Template" use case under [fedora-minimal customization](/doc/templates/fedora-minimal/#customization). diff --git a/user/common-tasks/copying-files.md b/user/common-tasks/copying-files.md index ea8ddb49..21688795 100644 --- a/user/common-tasks/copying-files.md +++ b/user/common-tasks/copying-files.md @@ -57,6 +57,3 @@ It even applies to the scenario of copying files between air-gapped machines. So, you should always copy data only from *more trusted* to *less trusted* qubes. See also [this article](https://blog.invisiblethings.org/2011/03/13/partitioning-my-digital-life-into.html) for more information on this topic, and some ideas of how we might solve this problem in some future version of Qubes. - -You may also want to read how to [revoke "Yes to All" authorization](/doc/qrexec3/#revoking-yes-to-all-authorization) - diff --git a/user/common-tasks/disposablevm.md b/user/common-tasks/disposablevm.md index 981144f5..4e211367 100644 --- a/user/common-tasks/disposablevm.md +++ b/user/common-tasks/disposablevm.md @@ -168,7 +168,7 @@ This line means: In other words, any VM will be allowed to create a new DisposableVM based on `online-dvm-template` and open a URL inside of that DisposableVM. -More information about RPC policies for DisposableVMs can be found [here][qrexec3-4.0]. +More information about RPC policies for DisposableVMs can be found [here][qrexec]. ## Customizing DisposableVMs ## @@ -179,4 +179,4 @@ Full instructions can be found [here](/doc/disposablevm-customization/). [DisposableVM Template]: /doc/glossary/#disposablevm-template -[qrexec3-4.0]: /doc/qrexec3/#extra-keywords-available-in-qubes-40-and-later +[qrexec]: /doc/qrexec/#qubes-rpc-administration