Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-11-28 07:30:44 -05:00
Code Issues Projects Releases Packages Wiki Activity

Trying to fix my mistakes ...

Browse source
This commit is contained in:
parulin 2025-08-16 14:28:31 -04:00
parent e3e699fa5e
commit 5281f045dc
No known key found for this signature in database
GPG key ID: 65099A5B0E31336C
10 changed files with 300 additions and 1527 deletions
Download patch file Download diff file Expand all files Collapse all files

33
developer/services/admin-api.rst
View file

@ -75,7 +75,7 @@ it easy to set the policy using current mechanism.
- `-`
- `-`
- ``<class>\n``
-
-
* - ``admin.vm.List``
- ``dom0|<vm>``
- `-`
@ -130,7 +130,7 @@ it easy to set the policy using current mechanism.
- `-`
- ``<label-index>``
-
* - ``admin.label.Remove``
* - ``admin.label.Remove``
- ``dom0``
- label
- `-`
@ -187,10 +187,10 @@ it easy to set the policy using current mechanism.
* - ``admin.vm.property.List``
- vm
- `-`
- `-`
- `-`
- ``<property>\n``
-
* - ``admin.vm.property.Get``
* - ``admin.vm.property.Get``
- vm
- property
- `-`
@ -223,7 +223,7 @@ it easy to set the policy using current mechanism.
* - ``admin.vm.property.Reset``
- vm
- property
- `-`
- `-`
- `-`
-
* - ``admin.vm.property.Set``
@ -262,7 +262,7 @@ it easy to set the policy using current mechanism.
- `-`
- value
-
* - ``admin.vm.feature.CheckWithTemplateAndAdminVM``
* - ``admin.vm.feature.CheckWithTemplateAndAdminVM``
- vm
- feature
- `-`
@ -297,7 +297,7 @@ it easy to set the policy using current mechanism.
- `-`
- `-`
- ``<tag>\n``
-
-
* - ``admin.vm.tag.Get``
- vm
- tag
@ -318,7 +318,7 @@ it easy to set the policy using current mechanism.
-
* - ``admin.vm.firewall.Get``
- vm
- `-`
- `-`
- `-`
- ``<rule>\n``
- rules syntax as in :doc:`firewall interface </developer/debugging/vm-interface>` (Firewall Rules in 4x) with addition of ``expire=`` and ``comment=`` options; ``comment=`` (if present) must be the last option
@ -363,11 +363,11 @@ it easy to set the policy using current mechanism.
- device
- `-`
- `-`
- ``device`` is in form ``<backend-name>+<device-ident>``
- ``device`` is in form ``<backend-name>+<device-ident>``
* - ``admin.vm.device.<class>.Set.required``
- vm
- device
- ``True|False``
- ``True|False``
- `-`
- ``device`` is in form ``<backend-name>+<device-ident>``
* - ``admin.vm.deviceclass.List``
@ -430,7 +430,7 @@ it easy to set the policy using current mechanism.
- `-`
- `-`
-
* - ``admin.pool.volume.List``
* - ``admin.pool.volume.List``
- ``dom0``
- pool
- `-`
@ -483,12 +483,12 @@ it easy to set the policy using current mechanism.
- pool
- vid
- token, to be used in ``admin.pool.volume.CloneTo``
- obtain a token to copy volume ``vid`` in ``pool``; the token is one time use only, it's invalidated by ``admin.pool.volume.CloneTo``, even if the operation fails
- obtain a token to copy volume ``vid`` in ``pool``; the token is one time use only, it's invalidated by ``admin.pool.volume.CloneTo``, even if the operation fails
* - ``admin.pool.volume.CloneTo``
- ``dom0``
- pool
- ``<vid> <token>``
- `-`
- `-`
- copy volume pointed by a token to volume ``vid`` in ``pool``
* - ``admin.vm.volume.List``
- vm
@ -498,7 +498,7 @@ it easy to set the policy using current mechanism.
- ``<volume>`` is per-VM volume name (``root``, ``private``, etc), ``<vid>`` is pool-unique volume id
* - ``admin.vm.volume.Info``
- vm
- volume
- volume
- `-`
- ``<property>=<value>\n``
-
@ -608,7 +608,7 @@ it easy to set the policy using current mechanism.
- ``dom0``
- config id
- `-`
- backup info
- backup info
- info what would be included in the backup
* - ``admin.backup.Cancel``
- ``dom0``
@ -921,6 +921,3 @@ TODO
- maybe some generator for ``.desktop`` for appmenus, which would wrap
calls in ``qrexec-client-vm``
.. raw:: html
<!-- vim: set ts=4 sts=4 sw=4 et : -->

5
developer/services/qrexec.rst
View file

@ -111,7 +111,10 @@ Answering an RPC call
^^^^^^^^^^^^^^^^^^^^^
In other for a RPC call to be answered in the target VM, a file in either of the following locations must exist, containing the file name of the program that will be invoked, or being that program itself – in which case it must have executable permission set (``chmod +x``): - ``/etc/qubes-rpc/RPC_ACTION_NAME`` when you make it in the template qube; - ``/usr/local/etc/qubes-rpc/RPC_ACTION_NAME`` for making it only in an app qube.
In other for a RPC call to be answered in the target VM, a file in either of the following locations must exist, containing the file name of the program that will be invoked, or being that program itself – in which case it must have executable permission set (``chmod +x``):
- ``/etc/qubes-rpc/RPC_ACTION_NAME`` when you make it in the template qube;
- ``/usr/local/etc/qubes-rpc/RPC_ACTION_NAME`` for making it only in an app qube.
The source VM name can then be accessed in the server process via ``QREXEC_REMOTE_DOMAIN`` environment variable. (Note the source VM has *no* control over the name provided in this variable–the name of the VM is provided by dom0, and so is trusted.)