qvm-copy-to-vm question

[Todd Lasman]

I'm not sure if I'm doing this correctly.

According to the usage, the syntax is:
qvm-copy-to-vm destination_qube_name FILE

When I do this, I get a dialog that asks me which qube I want to copy my
file to. Why have this, if I already specified it in the command line?
Is there a way to suppress the dialog? And if not, what's the purpose of
having the destination_qube_name in the command line in the first place?

I'm told that some use qvm-copy instead of qvm-copy-to-vm. Whenever I
use the qvm-copy command (with the destination qube and the file to
copy) I always get the error message "Can't stat destination_qube. File
or directory doesn't exist (or something like that)"

All I want to do is copy a file from one qube to the next without
hassle. Suggestions?

Thanks!

Todd

[awokd]

Todd Lasman wrote on 2/13/19 1:58 AM:

> I'm not sure if I'm doing this correctly.
>
> According to the usage, the syntax is:
> qvm-copy-to-vm destination_qube_name FILE

This is for copies from dom0 only.

> When I do this, I get a dialog that asks me which qube I want to copy my
> file to. Why have this, if I already specified it in the command line?
> Is there a way to suppress the dialog? And if not, what's the purpose of
> having the destination_qube_name in the command line in the first place?

3.2 used to permit the destination_qube_name in there, but 4.0+ doesn't.

> I'm told that some use qvm-copy instead of qvm-copy-to-vm. Whenever I
> use the qvm-copy command (with the destination qube and the file to
> copy) I always get the error message "Can't stat destination_qube. File
> or directory doesn't exist (or something like that)"
>
> All I want to do is copy a file from one qube to the next without
> hassle. Suggestions?

From a terminal session inside the source qube, use "qvm-copy
[filename]". It will then prompt for the destination qube.

[Todd Lasman]

Ok. Thanks for the explanation. Still doesn't seem right to me, though.
I think I should be able to do the whole copy/move with one command,
rather than two.

Todd

[awokd]

Todd Lasman wrote on 2/14/19 4:12 AM:

I think it was done for security reasons- having dom0 prompt for the
destination is safer than allowing any qube to copy any data to any
other qube automatically.

[unman]

On Wed, Feb 13, 2019 at 08:12:42PM -0800, Todd Lasman wrote:
>
> On 2/13/19 3:18 PM, 'awokd' via qubes-users wrote:
> > Todd Lasman wrote on 2/13/19 1:58 AM:
> > > I'm not sure if I'm doing this correctly.
> > >
> > > According to the usage, the syntax is:
> > > qvm-copy-to-vm destination_qube_name FILE
> >

> > > All I want to do is copy a file from one qube to the next without
> > > hassle. Suggestions?

You can suppress the prompt by setting rules in
/etc/qubes-rpc/policy/qubes.Filecopy
So if you have in that file:
qube1 qube2 allow
In qube1 you can use qvm-move-to-vm qube2 foo and no prompt will appear.

The prompt appears because either you have not specified a target qube
or you have not given appropriate permissions.

unman

[Todd Lasman]

On 2/14/19 7:12 AM, unman wrote:
> On Wed, Feb 13, 2019 at 08:12:42PM -0800, Todd Lasman wrote:
>> On 2/13/19 3:18 PM, 'awokd' via qubes-users wrote:
>>> Todd Lasman wrote on 2/13/19 1:58 AM:
>>>> I'm not sure if I'm doing this correctly.

>>>> O

>>>> qvm-copy-to-vm destination_qube_name FILE
>>>> All I want to do is copy a file from one qube to the next without
>>>> hassle. Suggestions?
> You can suppress the prompt by setting rules in
> /etc/qubes-rpc/policy/qubes.Filecopy
> So if you have in that file:
> qube1 qube2 allow
> In qube1 you can use qvm-move-to-vm qube2 foo and no prompt will appear.
>
> The prompt appears because either you have not specified a target qube
> or you have not given appropriate permissions.
>
> unman
>

I understand. Thanks all, for the explanation (security), and the
potential for setting rules.

Todd