From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Can't sign with gpg2 using pinentry-curses
Date: Thu, 06 Jul 2017 21:23:00 -0000 [thread overview]
Message-ID: <a1eaa601-173d-4a43-200d-661b0378036d@cornell.edu> (raw)
In-Reply-To: <df11b983-7949-c74e-2d32-5ce7e314c6cb@cornell.edu>
On 7/6/2017 4:27 PM, Ken Brown wrote:
> When I try to sign a file using gpg2 in a mintty or xterm terminal
> (e.g., 'gpg2 -bs foo'), a dialogue box is drawn in the terminal, but I
> can't figure out how to enter my passphrase. Anything I type is just
> echoed at the bottom of the screen, regardless of what I do with the
> mouse. If I type Ctrl-C, the bash prompt returns but the
> pinentry-curses process keeps running for a while.
>
> If I install pinentry-gnome3, then 'gpg2 -bs' works fine when run from
> an xterm window; a dialogue box pops up and I can enter the passphrase.
For a solution outside of X11, it looks like pinentry-w32 will do the
job. But simply installing that package isn't enough, because the
script /usr/bin/pinentry never calls pinentry-w32.exe.
As a workaround, I moved /usr/bin/pinentry out of the way and created a
symlink
/usr/bin/pinentry -> pinentry-w32.exe
With this, gpg2 -bs works, although I still get the annoying message
gpg: selecting openpgp failed: No such device
Ken
--
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-06 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 20:27 Ken Brown
2017-07-06 21:23 ` Ken Brown [this message]
2017-07-06 21:31 ` Ken Brown
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=a1eaa601-173d-4a43-200d-661b0378036d@cornell.edu \
--to=kbrown@cornell.edu \
--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).