Closed davidbarratt closed 6 years ago
Thanks for giving it a try. 🙂 To help, I'll need more info.
As a potential quick fix, I recommend using GPG2 v2.1.11 or greater. This is available in WSL using sudo apt install gnupg2
. All my dev and testing was with this version of GPG2.
I just now pushed an update to clarify more and add troubleshooting. I recommend you read the updated README and download the newest code. This commit includes toast notification (on by default) if passwords are pulled from Windows Credential Manager. How to enable/disable is in the updated docs.
If the updated docs don't assist in fixing it...
With the default GPG2 setup, not using this repo's code/config...
Can you use GPG agent successfully using GPG keys with passwords ?
Try a test. gpg2 --clearsign myfile.zip
. Your entire console window should clear and present you an isolated password entry field in a crudely drawn box. Type in your key's password and it should return to your normal console with no error. And you should see the newly signed myfile.zip.asc
file.
If that standard GPG2 setup doesn't work like that, particularly the full screen password prompt with the crude box, I recommend you first focus on getting your default setup working before moving to this custom pinentry.
If all works with this default GPG2 agent setup, then I need more info, please.
winver.exe
and WSL uname -a
asdasdcat /etc/lsb-release
and the DISTRIB_RELEASE valuegpg --version
and/or GPG2 gpg2 --version
gpg-agent --version
powershell -command "echo $PSVersionTable"
and the PSVersion valueno reply from original poster. closing issue.
I follow the standard instructions, but I can't get the dialog to popup... gpg just hangs waiting for the password.
Am I doing something wrong?