-
Notifications
You must be signed in to change notification settings - Fork 10
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: signing failed: Bad passphrase #9
Comments
🤷 Have you tried skipping using this tool and verifying that the passphrase stored in the GPG key entry exactly matches? Otherwise I'm not sure how it would send the wrong passphrase. |
yup just did it again copy/pasting the field just to be sure and it worked. may be the sending an empty string? or str encoding error. |
You could try editing files in here: https://github.com/djherbis/keepass-pinentry/tree/master/KeepassPinentry to log what's going on and try to debug. Its working for me so I don't really know what's different on your machine. |
what is the |
|
I noticed that if I don't but the The version of keepass in your repo is 2.35 which is quite a distance from the current 2.52 (64-bit), may be that's why? |
Ah, yeah the code basically just does a "Search" for
The version in the repo is only in there because ya need some version to build an extension, my local keepass version is much newer. |
I'm getting the 2 notifications saying that
TLSKEY
thenGPG
entries were read.but I'm met with the error gpg:
signing failed: Bad passphrase
GPG entry is empty expect for the password field which hold the GPG password that I want Keepass do type for me when I do
git commit -S
any hint?
The text was updated successfully, but these errors were encountered: