From 8085719b1cee36c5191d371b16ed7d1bfeaf8c7f Mon Sep 17 00:00:00 2001 From: qubedmaiska Date: Sat, 18 Jan 2025 15:21:06 -0500 Subject: [PATCH] small formatting issues --- developer/services/qrexec.md | 1 + user/advanced-topics/gui-configuration.md | 2 +- user/advanced-topics/rpc-policy.md | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/developer/services/qrexec.md b/developer/services/qrexec.md index 4ee41d98..d95e952d 100644 --- a/developer/services/qrexec.md +++ b/developer/services/qrexec.md @@ -109,6 +109,7 @@ Note that if the request is redirected (`target=` parameter), policy action rema If no policy rule is matched, the action is denied. 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. diff --git a/user/advanced-topics/gui-configuration.md b/user/advanced-topics/gui-configuration.md index b622ac99..56a06227 100644 --- a/user/advanced-topics/gui-configuration.md +++ b/user/advanced-topics/gui-configuration.md @@ -21,7 +21,7 @@ qvm-features dom0 gui-videoram-min $(($WIDTH * $HEIGHT * 4 / 1024)) qvm-features dom0 gui-videoram-overhead 0 ``` -Where `$WIDTH`×`$HEIGHT` is the maximum desktop size that you anticipate needing. +Where `$WIDTH` × `$HEIGHT` is the maximum desktop size that you anticipate needing. For example, if you expect to use a 1080p display and a 4k display side-by-side, that is `(1920 + 3840) × 2160 × 4 / 1024 = 48600`, or slightly more than 48 MiB per qube. After making these adjustments, the qubes need to be restarted. diff --git a/user/advanced-topics/rpc-policy.md b/user/advanced-topics/rpc-policy.md index 53cf01e4..bd2aa168 100644 --- a/user/advanced-topics/rpc-policy.md +++ b/user/advanced-topics/rpc-policy.md @@ -43,7 +43,7 @@ This is how we create a policy that says: "VMs tagged with 'work' are allowed to When an operation is initiated with a specific target, e.g. `qvm-copy-to-vm other_work_vm some_file` the policy mechanism looks for a row matching `source_work_vm other_work_vm PERMISSION`. In this case, assuming both VMs have the `work` tag, the second row would match, and -the operation would be `allow`ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`, +the operation would be `allow`-ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`, the policy mechanism looks for a row matching `source_work_vm @default PERMISSION`. In this case, the first row indicates that the user should be prompted for the destination. The list of destination VMs in the prompt is filtered to only include VMs that are valid as per the policy (so in this example, only other work VMs would be listed). If the first row was commented out, the second row would not match