-
Notifications
You must be signed in to change notification settings - Fork 187
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
GPG 2.1 requires --pinentry-mode loopback to specify passphrase #145
Comments
Hi, thanks for reporting! Well since that's not the first time that adding options to GPG comes up as an issue, I'm thinking about adding a separate GPG_OPTIONS variable where users could add GPG-related options easily. Not sure yet how quoting issues will turn out. |
Hi, I've added a new variable |
Yes, I have removed the option from STATIC_OPTIONS and added using the suggested GPG_OPTIONS: GPG_OPTIONS="--no-show-photos --pinentry-mode loopback" It seems to be working well. Thanks for adding this. |
Just wanted to say that I am successfully using |
After upgrading gnupg to V2.1, my unattended duplicty-backup backups stopped working with the following error message:
The problem is that I was supplying the passphrase in the config file but gpg now needs the
--pinentry-mode loopback
option to be able to use that. This means adding--gpg-options "--pinentry-mode loopback"
to the duplicity command. Note that getting the correct quoting is error-prone if doing that using STATIC_OPTIONS.It would be nice if duplicity-backup automatically added
--gpg-options "--pinentry-mode loopback"
to the duplicity command if the PASSPHRASE is set.If that is not possible then, at the very least, please expand the PASSPHRASE comment in the example conf file to explain that
--gpg-options --pinentry-mode=loopback
must be included in STATIC_OPTIONS (that seems to be the best form to recommend to minimise quoting problems).The text was updated successfully, but these errors were encountered: