Make direct links to internals sections (QubesOS/qubes-issues#1392)

This commit is contained in:
Axon 2015-11-09 00:20:01 +00:00
parent 3fe2f6e6aa
commit bffa21f613
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
2 changed files with 4 additions and 4 deletions

View File

@ -232,9 +232,9 @@ surfaces that are exposed to untrusted or less trusted VMs in that case.
## Qubes RPC internals ## ## Qubes RPC internals ##
(*This is about the implementation of qrexec v2. For the implementation of (*This is about the implementation of qrexec v2. For the implementation of
qrexec v3, see [here](/doc/qrexec3/). Note that the user API in v3 is backward qrexec v3, see [here](/doc/qrexec3/#qubes-rpc-internals). Note that the user
compatible: qrexec apps written for Qubes R2 should run without modification API in v3 is backward compatible: qrexec apps written for Qubes R2 should
on Qubes R3.*) run without modification on Qubes R3.*)
### Dom0 tools implementation ### ### Dom0 tools implementation ###

View File

@ -206,7 +206,7 @@ and we should get "3" as answer, after dom0 allows it.
## Qubes RPC internals ## ## Qubes RPC internals ##
(*This is about the implementation of qrexec v3. For the implementation of (*This is about the implementation of qrexec v3. For the implementation of
qrexec v2, see [here](/doc/qrexec2/).*) qrexec v2, see [here](/doc/qrexec2/#qubes-rpc-internals).*)
Qrexec framework consists of a number of processes communicating with each Qrexec framework consists of a number of processes communicating with each
other using common IPC protocol (described in detail below). Components other using common IPC protocol (described in detail below). Components