Windows qrexec agent has special handling of nogui:
that cannot be achieved otherwise
#9198
Labels
affects-4.1
This issue affects Qubes OS 4.1.
affects-4.2
This issue affects Qubes OS 4.2.
C: windows-tools
diagnosed
Technical diagnosis has been performed (see issue comments).
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
How to file a helpful issue
Qubes OS release
git main but probably predates R4.1
Brief summary
The Windows qrexec agent handles qrexec commands of the form
USER:nogui:
specially. By design, it is not possible to include thenogui:
except via a call in dom0 toqrexec-client
orqvm-run --no-gui
. As per #9180 (comment) the solution to this is not to allownogui
to be specified in the policy file (NACKd by @marmarek in #9180), but rather to allow the same effect to be achieved within the guest.Steps to reproduce
See above.
Expected behavior
nogui:
doesn’t do anything that cannot be achieved by proper service configuration in the Windows guest.Actual behavior
nogui:
does something that cannot be achieved by proper service configuration in the Windows guest.The text was updated successfully, but these errors were encountered: