This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problem with gnupg2 not prompting for passphrase

On 7/11/2017 11:10 AM, Garber, Dave (GE Oil & Gas, Non-GE) wrote:
>> -----Original Message-----
>> From: [] On
>> Behalf Of jeff
>> Sent: Tuesday, July 11, 2017 1:56 PM
>> To:
>> Subject: EXT: Re: problem with gnupg2 not prompting for passphrase
>> On 7/11/2017 10:51 AM, Brian Inglis wrote:
>>> On 2017-07-10 23:07, Thomas Wolff wrote:
>>>> Am 11.07.2017 um 00:38 schrieb jeff:
>>>>> On 7/10/2017 1:21 PM, Achim Gratz wrote:
>>>>>> jeff writes:
>>>>>>> jeff_xeon:/cygdrive/u:503: gpg2 --output fred.good --decrypt
>>>>>>> fred.gpg
>>>>>>> gpg: encrypted with 4096-bit RSA key, ID A3791E7DD935A424, created
>>>>>>> 2013-03-21
>>>>>>>        "Jeff Deifik <>"
>>>>>>> gpg: public key decryption failed: No such device or address
>>>>>>> gpg: decryption failed: No secret key
>>>>>>> I have uninstalled the standalone version of gnupg2 before I did this.
>>>>>>> It seems most likely that the version of gpg2 being invoked is a
>>>>>>> cygwin version.
>>>>>> It fails to find your private key, so it is quite obviously not in
>>>>>> a place where gpg2 expects to find it.
>>>>> I have my keys stored in $HOME/.gnupg which is where gnupg v1
>> expects them.
>>> gnupg2 uses the same --homedir paths, $GNUPGHOME env var, native
>>> Windows reg key, and native Windows portable apps homedir as gnupg1.
>>>> Just guessing: Some software does not look in $HOME for config files (e.g.
>>>> openssh) but expects them in /home/...
>>> OpenSSH expects user config files in ~/.ssh/ where ~ is $HOME, or the
>>> home directory from "getent passwd $LOGNAME", which defaults to /.
>>> They'd better expect $HOME, not /home/$LOGNAME, as $HOME could
>> also be
>>> /u/$LOGNAME, /mnt/nfs/OrkeyDorkey, or /mnt/Network\ Users/Orkey\
>>> Dorkey! ;^>
>> The problem almost certainly lies with pinentry. It seems to be a new feature
> See for the solution.

That did fix the issue. No doubt pinentry needs to be fixed to call
pinentry-w32 when appropriate.

I can now use gpg2 via bash as well as via thunderbird / engmail.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]