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-backup requires an option to specify a password through stdin / cmdline #1523

Closed
Rudd-O opened this Issue Dec 18, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@Rudd-O

Rudd-O commented Dec 18, 2015

I just spent the better part of two hours trying to automate qvm-backup with no success at all.

Please add a command line option --stdin that lets qvm-backup override getpass.getpass(...) and also skip the confirmation [y/N] such that the password can be specified through standard input.

It should not be difficult -- you just need a code block that skips the confirmation if --stdin is specified, and another code block that skips the getpass.getpass() call if the aforementioned parameter has been specified.

All of this can be implemented in qvm-backup very easily.

Perhaps, even, there could be a --file option, which could have - as a parameter, meaning /dev/stdin. That way, it need not be the case that --stdin exists, or hardcodes the password input to standard input. Maybe the input can be a file in /dev/shm. Certainly, this can be used to do integration tests of qvm-backup, especially without having to include pty cobwebs in the code.

Thanks.

@marmarek marmarek added this to the Release 3.2 milestone Jan 6, 2016

@marmarek marmarek added the help wanted label Jan 6, 2016

andrewdavidwong added a commit that referenced this issue Jun 7, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 16, 2016

Member

There is qvm-backup --passphrase-file=- for it.

Member

marmarek commented Jul 16, 2016

There is qvm-backup --passphrase-file=- for it.

@marmarek marmarek closed this Jul 16, 2016

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