Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up`qrexec-client-vm '$dispvm:<anything>'` always fails with "Request refused" #3137
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 1, 2017
Member
Note that by default ask action ignore destination you provided to qrexec-client-vm command. So, you may also put empty string there and choose $dispvm:work from confirmation dialog.
But what you've found is a bug of course...
|
Note that by default |
marmarek
added
bug
C: core
P: major
labels
Oct 1, 2017
marmarek
added this to the Release 4.0 milestone
Oct 1, 2017
marmarek
closed this
in
marmarek/qubes-core-admin-linux@54d5c7b
Oct 1, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 7, 2017
Automated announcement from builder-github
The package qubes-core-dom0-linux-4.0.6-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubesos-bot
commented
Oct 7, 2017
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Oct 7, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Oct 7, 2017
Closed
core-admin-linux v4.0.6 (r4.0) #248
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Oct 17, 2017
Automated announcement from builder-github
The package qubes-core-dom0-linux-4.0.6-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:
sudo qubes-dom0-update
Or update dom0 via Qubes Manager.
qubesos-bot
commented
Oct 17, 2017
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
joshuathayer commentedSep 30, 2017
•
edited
Edited 1 time
-
joshuathayer
edited Sep 30, 2017 (most recent)
Qubes OS version (e.g.,
R3.2):4.0, up to date with
current-testingviaSteps to reproduce the behavior:
From an AppVM:
Expected behavior:
Since the default policy in
/etc/qubes-rpc/policy/qubes.OpenInVMisask, I'd expect a confirmation dialog to appear.Then, I'd expect the same behavior as
qrexec-client-vm '$dispvm' qubes.OpenInVM "/usr/lib/qubes/qopen-in-vm" ./hello.txt: a new dispVM should start and ageditwindow should open with the contenthello world.Actual behavior:
An immediate
Request refusederror appears.Note that this happens regardless of "template" VM- the following exhibits the same behavior:
General notes:
I spent some time debugging and found that the colon in the target VM name is getting munged into an underscore at some point before
qrexec-policyis run ondom0, which seems to keep any policy from matching the target VM.Thanks!