From: David Dombrowsky <6thstreetradio@gmail.com>
To: cygwin@cygwin.com
Subject: Re: pinentry-curses not available?
Date: Fri, 02 Nov 2018 20:47:00 -0000 [thread overview]
Message-ID: <CAHdnY6P5W37VcEZ3b6=qHk+V_PAR=z08Q_o7syvTqO7fowkciA@mail.gmail.com> (raw)
In-Reply-To: <a7b21966-a616-c5ae-fd6b-0e3b8ad92055@gmail.com>
> I see from [1] that pinentry-w32 exists which is a replacement for
> pinentry-curses which was in [2].
pinentry-w32 works great, but it requires you to be logged in to the
GUI, and _then_ invoke gpg-agent, in order for things to work. And
you need to do this every time the pin times out. Obviously not the
end of the world, but having a console one is much nicer, because it
works over an ssh connection.
On Fri, Nov 2, 2018 at 4:21 PM cyg Simple <cygsimple@gmail.com> wrote:
>
> 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
>
--
David Dombrowsky, Senior Software Engineer
email: davek@6thstreetradio.org
Cell: 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415
http://6thstreetradio.org/
--
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:47 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
2018-11-02 20:47 ` David Dombrowsky [this message]
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='CAHdnY6P5W37VcEZ3b6=qHk+V_PAR=z08Q_o7syvTqO7fowkciA@mail.gmail.com' \
--to=6thstreetradio@gmail.com \
--cc=cygwin@cygwin.com \
--cc=davek@6thstreetradio.org \
/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).