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?
On Friday, March 24, 2023 at 8:41:54 AM UTC-7 Boryeu Mao wrote:
> Yes, 'qvm-copy' alone would ensure the security of
Yes, 'qvm-copy' alone would ensure the security of copying/moving files
between AppVM's. Thanks.
On Fri, Mar 24, 2023 at 5:43 AM unman wrote:
> qvm-copy-to-vm is deprecated and will be removed.
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
qvm-copy-to-vm is deprecated and will be removed.
--
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+unsubscr...@googlegroups.com.
To view this
Ah that makes sense. Thanks much, Glen. (Scripting is precisely what I
was going for -- I can still have everything else automated.) Boryeu
On Thu, Mar 23, 2023 at 5:20 PM Glen Larwill wrote:
> Security?
>
> Forces ANY file movement between VMs to be under the control of a human
> behind a
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 wrote:
> I'd expected 'qvm-copy-to-vm' to accept the
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
