From 2af81d9e7d4272db6b86f2b7ca04daea7111a98b Mon Sep 17 00:00:00 2001
From: straussmaus <44516603+straussmaus@users.noreply.github.com>
Date: Wed, 31 Oct 2018 03:51:06 +0000
Subject: [PATCH] Specified that /etc/qubes-rpc/policy/qubes.UpdatesProxy is on
 dom0

Modified "Technical Details (R4.0) to specify that /etc/qubes-rpc/policy/qubes.UpdatesProxy is on dom0 not the TemplateVM
---
 common-tasks/software-update-vm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common-tasks/software-update-vm.md b/common-tasks/software-update-vm.md
index 4197bcf5..cffba2f1 100644
--- a/common-tasks/software-update-vm.md
+++ b/common-tasks/software-update-vm.md
@@ -267,7 +267,7 @@ And in both cases defaults listed above are applied if the service is not explic
 ### Technical details (R4.0)
 
 Instead of using a network connection like in R3.2, R4.0 uses RPC/qrexec.
-The proxy is configured in qrexec policy: `/etc/qubes-rpc/policy/qubes.UpdatesProxy`.
+The proxy is configured in qrexec policy on dom0: `/etc/qubes-rpc/policy/qubes.UpdatesProxy`.
 By default this is set to sys-net and/or sys-whonix, depending on firstboot choices.
 This new design allows for templates to be updated even when they are not connected to any netvm.