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 target selection via cli #3584

Open
m4lu opened this Issue Feb 14, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@m4lu

m4lu commented Feb 14, 2018

Qubes OS version:

R4.0 (rc4)

Affected TemplateVMs:

  • fedora-26
  • fedora-26-minimal
  • debian-9

Steps to reproduce the behavior:

Run qvm-copy file in any Qube based on the templates mentioned above.

Expected behavior:

There should be a way to provide the target Qube on the cli (without a GUI).

Actual behavior:

A GUI dialogue pops up.

General notes:

The documentation (https://www.qubes-os.org/doc/copying-files/) states that the old tools like qvm-copy-to-vm are deprecated in 4.x The provided user interface is an improvement over the old one on 3.2, but to be able to script certain tasks would yield advantages for me.


Related issues:

#3529 (might be considered related)

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Documentation/website Feb 14, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
Member

andrewdavidwong commented Feb 14, 2018

Related: #3251, #3141, #1839

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 14, 2018

Member

The provided user interface is an improvement over the old one on 3.2, but to be able to script certain tasks would yield advantages for me.

You should be able to script it by specifying the destination VM in the appropriate policy file. I think this issue should be about documenting that functionality.

CC: @marmarek

Member

andrewdavidwong commented Feb 14, 2018

The provided user interface is an improvement over the old one on 3.2, but to be able to script certain tasks would yield advantages for me.

You should be able to script it by specifying the destination VM in the appropriate policy file. I think this issue should be about documenting that functionality.

CC: @marmarek

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 14, 2018

Member

Alternatively, if it's actually available, try using qvm-copy-to-vm (instead of the qvm-copy wrapper), as mentioned in #3141 (if the way it's described there is how it actually ended up being implemented).

Member

andrewdavidwong commented Feb 14, 2018

Alternatively, if it's actually available, try using qvm-copy-to-vm (instead of the qvm-copy wrapper), as mentioned in #3141 (if the way it's described there is how it actually ended up being implemented).

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 14, 2018

Member

If policy define action ask, you need GUI anyway. But if you define allow (for some specific source and target), then qvm-copy-to-vm will work.

Member

marmarek commented Feb 14, 2018

If policy define action ask, you need GUI anyway. But if you define allow (for some specific source and target), then qvm-copy-to-vm will work.

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