From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: pinentry-curses not available?
Date: Fri, 02 Nov 2018 20:21:00 -0000 [thread overview]
Message-ID: <a7b21966-a616-c5ae-fd6b-0e3b8ad92055@gmail.com> (raw)
In-Reply-To: <CAHdnY6Pk62_ciujMvz319pUd6=Y7mQBj0POwnYgYh_sm1Lccwg@mail.gmail.com>
On 11/2/2018 3:47 PM, David Dombrowsky wrote:
> I don't see a way to download `pinentry-curses` or `pinentry-tty` for
> use with `gpg-agent` (using gnupg v2). Are these not maintained? Or
> am I just looking at the wrong sources?
>
> In any case, I got pinentry-1.1.0 to compile against a cygwin-supplied
> version of ncurses, and it mostly works (you still need to tell it to
> not detach from the tty, not sure what's up with that). This is very
> useful when signing git commits, and removing the need for a graphical
> console just to input my gpg passphrase.
I see from [1] that pinentry-w32 exists which is a replacement for
pinentry-curses which was in [2]. Now both of these are version 1.0.0.
Based on [3] Marco Atzeri can give or point to reasoning.
[1]
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpinentry%2Fpinentry-1.0.0-2&grep=pinentry
[2]
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpinentry%2Fpinentry-1.0.0-1&grep=pinentry
[3] https://cygwin.com/cygwin-pkg-maint
--
cyg Simple
--
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:[~2018-11-02 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 19:47 David Dombrowsky
2018-11-02 20:21 ` cyg Simple [this message]
2018-11-02 20:47 ` David Dombrowsky
2018-11-03 18:23 ` Marco Atzeri
2018-11-05 16:06 ` David Dombrowsky
2019-01-22 14:36 ` David Dombrowsky
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=a7b21966-a616-c5ae-fd6b-0e3b8ad92055@gmail.com \
--to=cygsimple@gmail.com \
--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).