From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: problem with gnupg2 not prompting for passphrase
Date: Mon, 10 Jul 2017 19:42:00 -0000 [thread overview]
Message-ID: <3e91fbf6-cf13-718f-5f0f-8e77cd57b169@towo.net> (raw)
In-Reply-To: <ddb4fd0f-8138-7cc5-ccf5-678fe6365afd@jeffunit.com>
Am 10.07.2017 um 16:29 schrieb jeff:
> I installed gnupg2 and several versions of pinentry.
> When I try to use it with engmail on thunderbird, I don't get prompted
> for a passphrase.
>
> My engmail setup works with a standalone version of gnupg2.
> it also used to work with cygwin gnupg1 (before engmail required gnupg2).
This suggests your gnupg2 is not a cygwin program. Unfortunately,
interoperability of non-cygwin programs with cygwin terminal I/O is
limited. You might want to use the winpty wrapper.
Thomas
> When I invoke gnupg2 from the command line:
> xeon:/cygdrive/u:502: gpg2 --output fred.good --decrypt fred.gpg
> gpg: encrypted with 4096-bit RSA key, ID A3791E7DD935A424, created
> 2013-03-21
> "Jeff Deifik <jeff@jeffunit.com>"
> gpg: public key decryption failed: No such device or address
> gpg: decryption failed: No secret key
>
>
> I should get something like:
>
> You need a passphrase to unlock the secret key for
> user: "Blake (Executioner) <blake@cyb.org>"
> 1024-bit ELG-E key, ID 5C8CBD41, created 1999-06-04 (main key ID 9E98BC16)
>
> Enter passphrase:
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-10 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 14:30 jeff
2017-07-10 19:42 ` Thomas Wolff [this message]
2017-07-10 19:55 ` jeff
2017-07-10 20:21 ` Achim Gratz
2017-07-10 22:38 ` jeff
2017-07-11 5:07 ` Thomas Wolff
2017-07-11 17:51 ` Brian Inglis
2017-07-11 17:56 ` jeff
2017-07-11 18:10 ` Garber, Dave (GE Oil & Gas, Non-GE)
2017-07-11 18:18 ` jeff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e91fbf6-cf13-718f-5f0f-8e77cd57b169@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).