Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-06-26 07:30:46 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update attachment paths

Browse source
This commit is contained in:
Andrew David Wong 2021-06-18 05:02:02 -07:00
parent ba376404e0
commit e5a21f7488
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
30 changed files with 107 additions and 107 deletions
Download patch file Download diff file Expand all files Collapse all files

2
developer/services/admin-api.md
View file

@ -37,7 +37,7 @@ TBD
## Components
![Admin API Architecture](/attachment/wiki/AdminAPI/admin-api-architecture.svg)
![Admin API Architecture](/attachment/doc/admin-api-architecture.svg)
A central entity in the Qubes Admin API system is a `qubesd` daemon, which
holds information about all domains in the system and mediates all actions (like

6
developer/services/qrexec-internals.md
View file

@ -117,7 +117,7 @@ Details of all possible use cases and the messages involved are described below.
### dom0: request execution of `cmd` in domX
![qrexec internals diagram dom0-vm](/attachment/wiki/qrexec3/qrexec-dom0-vm.png)
![qrexec internals diagram dom0-vm](/attachment/doc/qrexec-dom0-vm.png)
- **dom0**: `qrexec-client` is invoked in **dom0** as follows:
@ -145,7 +145,7 @@ Details of all possible use cases and the messages involved are described below.
### domX: request execution of service `admin.Service` in dom0
![qrexec internals diagram vm-dom0](/attachment/wiki/qrexec3/qrexec-vm-dom0.png)
![qrexec internals diagram vm-dom0](/attachment/doc/qrexec-vm-dom0.png)
- **domX**: `qrexec-client-vm` is invoked as follows:
@ -191,7 +191,7 @@ Details of all possible use cases and the messages involved are described below.
### domX: invoke execution of qubes service `qubes.Service` in domY
![qrexec internals diagram vm-vm](/attachment/wiki/qrexec3/qrexec-vm-vm.png)
![qrexec internals diagram vm-vm](/attachment/doc/qrexec-vm-vm.png)
- **domX**: `qrexec-client-vm` is invoked as follows:

2
developer/services/qrexec.md
View file

@ -38,7 +38,7 @@ Typically, the first thing that a `qrexec-client` instance does is to send a req
`qrexec-client` starts a vchan server, which `qrexec-agent` then connects to.
Once this channel is established, stdin/stdout/stderr from the VMprocess is passed between `qrexec-agent` and the `qrexec-client` process.
![qrexec basics diagram](/attachment/wiki/qrexec3/qrexec3-basics.png)
![qrexec basics diagram](/attachment/doc/qrexec3-basics.png)
The `qrexec-client` command is used to make connections to VMs from dom0.
For example, the following command creates an empty file called `hello-world.txt` in the home folder of `someVM`:

2
developer/services/qrexec2.md
View file

@ -300,7 +300,7 @@ significantly differs from what is described in this section.
The VM-VM channels in Qubes R2 are made via "gluing" two VM-Dom0 and Dom0-VM
vchan connections:
![qrexec2-internals.png](/attachment/wiki/Qrexec2Implementation/qrexec2-internals.png)
![qrexec2-internals.png](/attachment/doc/qrexec2-internals.png)
Note that Dom0 never examines the actual data flowing in neither of the two
vchan connections.