From 793928e7b1144b885c39434f843722a5a93660c9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Sat, 8 Dec 2018 22:37:44 +0100 Subject: [PATCH] qrexec: clarify when pipes and when vchan is used, add note about loopback vchan QubesOS/qubes-issues#4583 --- services/qrexec3.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/services/qrexec3.md b/services/qrexec3.md index b0495299..edccd982 100644 --- a/services/qrexec3.md +++ b/services/qrexec3.md @@ -361,8 +361,9 @@ qrexec v2, see [here](/doc/qrexec2/#qubes-rpc-internals).*) Qrexec framework consists of a number of processes communicating with each other using common IPC protocol (described in detail below). Components -residing in the same domain use pipes as the underlying transport medium, -while components in separate domains use vchan link. +residing in the same domain (`qrexec-client-vm` to `qrexec-agent`, `qrexec-client` to `qrexec-daemon`) use pipes as the underlying transport medium, +while components in separate domains (`qrexec-daemon` to `qrexec-agent`, data channel between `qrexec-agent`s) use vchan link. +Because of [vchan limitation](https://github.com/qubesos/qubes-issues/issues/951), it is not possible to establish qrexec connection back to the source domain. ## Dom0 tools implementation ##