From: David Dombrowsky <6thstreetradio@gmail.com>
To: cygwin@cygwin.com
Subject: pinentry-tty, gpg-agent, and no way to enter password
Date: Tue, 16 Apr 2019 16:30:00 -0000 [thread overview]
Message-ID: <fe858701-3b25-1610-b04b-2662c10c94e5@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1324 bytes --]
Back in 2018, I mentioned that there was reliable way to enter a gpg
password on the cygwin console:
http://cygwin.1069669.n5.nabble.com/pinentry-curses-not-available-td143121.html
From there I was able to cobble together a solution using a locally
patched version of pinentry-curses. Somewhere along the line, that
stopped working.
I am now back where I started.
Does anyone have a solution for the following:
1. ssh into a windows box running cygwin sshd
2. run `echo hello | gpg -sab`
This worked until recently. Now I get:
gpg: using "01D5A625A30C0E6A" as default secret key for signing
gpg: signing failed: Invalid IPC response
gpg: signing failed: Invalid IPC response
checking the output of gpg-agent, I see:
gpg-agent[2261]: gpg-agent (GnuPG) 2.2.13-unknown started
gpg-agent[2261]: handler 0x200549e0 for fd 7 started
gpg-agent[2261]: starting a new PIN Entry
cbreak failure, exiting
gpg-agent[2261]: failed to unprotect the secret key: Operation cancelled
pinentry-w32 works, but it pops up a GUI window and thus requires an RDP
session. Does anyone have a working solution that doesn't require
access to the windows console?
--
David Dombrowsky, Software Engineer
davek@6thstreetradio.org | 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2019-04-16 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 16:30 David Dombrowsky [this message]
2019-04-17 15:07 ` 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=fe858701-3b25-1610-b04b-2662c10c94e5@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).