-
Notifications
You must be signed in to change notification settings - Fork 25
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
Failed to decrypt with gnupg 2.2.4 #10
Comments
This will quickly become a more common issue as the latest Fedora and Ubuntu will likely be using these newer versions, though perhaps it will get patched on the gnupg side soon. |
This appears to have a potential fix in a newer libgcrypt versions, but I'm not sure how those interact with the pass/gopass implementations. |
This is weird, I'm on Debian sid with gpg 2.2.8 and I don't have any issue... |
@sherzberg Tried to enable auto expand of secmem?
|
I seem to be having this problem on a regular basis. I am running Fedora 28 with the following versions: gnupg2 2.2.8 @wsandin, I have tried the auto expand, but it does not seem to make any difference. Thank you for the suggestion. |
@wsandin sorry for the delay. I'm back on this now since I have just move to a new laptop. The suggestion you gave did not seem to help. Any other suggestions? |
I don't think this is an issue with this terraform provider, but I opened a ticket here first because it is easily reproducible with a simple terraform config. Mainly wanted to drop it here to see if anyone else has run into this issue.
Given a sufficiently large set of pass secrets to refresh, we get
failed to decrypt
errors on plans. This only seems to happen on > 2.1 gnupg. We have tried several version of terraform and gnupg, but our testing seems to point to gnupg > 2.1.Here is some terraform that will replicate the behavior.
We consisitently get something like this:
Software versions:
The text was updated successfully, but these errors were encountered: