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

qvm-copy-to-vm unexpressive error message if argument are inverted #3086

Open
Mayeu opened this Issue Sep 8, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@Mayeu

Mayeu commented Sep 8, 2017

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

R4-rc1

Affected TemplateVMs (e.g., fedora-23, if applicable):

Not sure if applicable, but all my test happened in AppVM using fedora-25


Expected behavior:

When running qvm-copy-to-vm with the wrong argument, eg. qvm-copy-to-vm $file $toVM instead of qvm-copy-to-vm $toVM $file, the tool should error out saying something like:

Error: no file or directory named $toVM found
usage: qvm-copy-to-vm [--without-progess] dest_vmname file [file...]

Actual behavior:

The only error showned is:

Request refused

The result is that you end-up digging into your policy to understand why on earth you can't send something from this VM when the policy clearly state $any $any ask :)

Steps to reproduce the behavior:

  1. Invert the argument in qvm-copy-to-vm

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Sep 9, 2017

@cartman4

This comment has been minimized.

Show comment
Hide comment
@cartman4

cartman4 Mar 15, 2018

I cant copy or move any files to other VMs since the last update (tried current-testing which seams to be RC-5 now and a the dom0-current repo of RC-4) i only get Request refused message when trying from terminal or nothing happens if i try it using the GUI

I cant copy or move any files to other VMs since the last update (tried current-testing which seams to be RC-5 now and a the dom0-current repo of RC-4) i only get Request refused message when trying from terminal or nothing happens if i try it using the GUI

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Mar 15, 2018

Member
Member

unman commented Mar 15, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 15, 2018

Member

@cartman4 Are you sure you have installed updates in both dom0 and template? There should be qubes-core-dom0 4.0.24 (dom0) and qubes-core-agent 4.0.24 (template). And restarted VMs?
In some cases (depending on previous version) system restart might be required.

BTW This is different than original issue. I believe original issue is resolved by introducing qvm-copy/qvm-move tools, which do not have VM name argument at all.

Member

marmarek commented Mar 15, 2018

@cartman4 Are you sure you have installed updates in both dom0 and template? There should be qubes-core-dom0 4.0.24 (dom0) and qubes-core-agent 4.0.24 (template). And restarted VMs?
In some cases (depending on previous version) system restart might be required.

BTW This is different than original issue. I believe original issue is resolved by introducing qvm-copy/qvm-move tools, which do not have VM name argument at all.

@cartman4

This comment has been minimized.

Show comment
Hide comment
@cartman4

cartman4 Mar 15, 2018

thanks marmarek. missed updating templates to same version.

thanks marmarek. missed updating templates to same version.

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