From: David Dombrowsky <davek@6thstreetradio.org>
To: cygwin@cygwin.com
Subject: more notes pinentry
Date: Wed, 5 Aug 2020 11:53:29 -0400 [thread overview]
Message-ID: <5b3aacdc-d663-c933-b6a5-cbead7d0637b@6thstreetradio.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1391 bytes --]
I've had an ongoing saga of trying to get gpg2's pinentry to work on the
console, via an SSH session, without requiring a console window.
I just tried rebuilding and testing from the latest git repo, and I
still receive the same error:
$ echo test | gpg -sab
gpg: using "01D5A625A30C0E6A" as default secret key for signing
gpg: signing failed: Operation cancelled
gpg: signing failed: Operation cancelled
The "Operation cancelled" comes from some command it's sending to the
tty and that's failing. I haven't looked into it more than that. It
isn't a system limitation, as `ssh-add` can prompt for a password all day.
As an admittedly insecure work-around, I've forked the code and added
something that will read the password from a file in the home directory.
This is obviously sub-optimal, but it works. Since I sign every git
commit and I'm the only user of this machine, it's a reasonable risk to
take to allow me to conveniently sign my commits.
The fork is here, in case anyone cares:
https://github.com/ddombrowsky/pinentry/commits/secretfile
If anyone has any opinions as to the real root cause, I'd be willing to
look into it more.
--
David Dombrowsky | Chief Software Engineer
6th Street Radio LLC | 6thstreetradio.org | 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415
V2VkIEF1ZyAgNSAwMjoxMzowMiBFRFQgMjAyMAo=
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2020-08-05 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5b3aacdc-d663-c933-b6a5-cbead7d0637b@6thstreetradio.org \
--to=davek@6thstreetradio.org \
--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).