'qvm-copy' and 'qvm-copy-to-vm' in AppVM

[Boryeu Mao]

I'd expected 'qvm-copy-to-vm' to accept the 1st argument as target-vm and get on with copying, but for me both commands request the target-vm in a pop-up window -- so what is the point of having 'qvm-copy-to-vm' at all, if I am not missing something really simple?

Thanks

[Glen Larwill]

Security?

Forces ANY file movement between VMs to be under the control of a human behind a keyboard/mouse. I ran into this as well, then realized the risk I was creating running this from a script.

GL

On Thu, Mar 23, 2023, 16:50 Boryeu Mao <borye...@gmail.com> wrote:

I'd expected 'qvm-copy-to-vm' to accept the 1st argument as target-vm and get on with copying, but for me both commands request the target-vm in a pop-up window -- so what is the point of having 'qvm-copy-to-vm' at all, if I am not missing something really simple?

Thanks

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/35eb7530-a5ca-4096-899c-c98c9f69f2b2n%40googlegroups.com.

[Boryeu Mao]

Ah that makes sense.  Thanks much, Glen.  (Scripting is precisely what I was going for -- I can still have everything else automated.)  Boryeu

[unman]

qvm-copy-to-vm is deprecated and will be removed.

[Boryeu Mao]

Yes, 'qvm-copy' alone would ensure the security of copying/moving files between AppVM's.  Thanks.

[Boryeu Mao]

Maybe the 'qvm-copy-to-vm' version could be made to place the 1st argument in the Target field of the pop-up window, such that only a CR is required to complete the operation?