New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

`qrexec-client-vm '$dispvm:<anything>'` always fails with "Request refused" #3137

Closed
joshuathayer opened this Issue Sep 30, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@joshuathayer

joshuathayer commented Sep 30, 2017

Qubes OS version (e.g., R3.2):

4.0, up to date with current-testing via

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Steps to reproduce the behavior:

From an AppVM:

$ echo "hello world" > hello.txt
$ qrexec-client-vm '$dispvm:fedora-25-dvm' qubes.OpenInVM "/usr/lib/qubes/qopen-in-vm" ./hello.txt

Expected behavior:

Since the default policy in /etc/qubes-rpc/policy/qubes.OpenInVM is ask, 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 a gedit window should open with the content hello world.

Actual behavior:

An immediate Request refused error appears.

Note that this happens regardless of "template" VM- the following exhibits the same behavior:

$ qrexec-client-vm '$dispvm:work' qubes.OpenInVM "/usr/lib/qubes/qopen-in-vm" ./hello.txt

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-policy is run on dom0, which seems to keep any policy from matching the target VM.

Thanks!

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

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...

Member

marmarek commented Oct 1, 2017

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...

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

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

Changes included in this update

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

Changes included in this update

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Oct 7, 2017

Closed

core-admin-linux v4.0.6 (r4.0) #248

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

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.

Changes included in this update

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.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment