From: Jeffrey Walton <noloader@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: Re: Commit signing and pinentry problems
Date: Mon, 2 Mar 2020 09:09:42 -0500 [thread overview]
Message-ID: <CAH8yC8km9k3sWKpjuj=69Y8SC=VHcDkBk=8O9RuCDOGtWGyqQQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8n+ta4BSAE4rEfhKxe3T9poVdc94HvSk=6PEA4YbmwVyA@mail.gmail.com>
On Wed, Nov 20, 2019 at 7:41 AM Jeffrey Walton <noloader@gmail.com> wrote:
>
> I'm having an annoying problem that I can't figure out. I hope Git has
> a setting to fix it.
>
> I have a desktop workstation where I sit at the keyboard about 1/3 of
> the time. Git signing works as expected. About 2/3 of the time I SSH
> into the machine. Git signing does not work when SSH'd in.
>
> When Git signing fails over SSH an error looks like:
>
> $ git commit -S log.h -m "Remove unneeded header"
> error: gpg failed to sign the data
> fatal: failed to write commit object
>
> I just noticed this today (but it makes sense)...
>
> - Go to desktop workstation, log in
> - Go to remote machine, log in
> - Sign at remote machine over SSH
> - Desktop workstation will open GUI password prompt
> - Remote machine sign operation will hang until GUI prompt times-out
>
> The problem was reported to Ubuntu but no activity:
> https://bugs.launchpad.net/ubuntu/+source/pinentry/+bug/1852696 .
>
> Does anyone know how to use Git to work around pinentry brain-dead-ness?
This fellow's answer fixed this problem: https://stackoverflow.com/a/53641081
Jeff
prev parent reply other threads:[~2020-03-02 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 12:41 Commit signing and pinentry problems Jeffrey Walton
2019-11-20 15:15 ` Randall S. Becker
2019-11-21 0:48 ` brian m. carlson
2020-03-02 14:09 ` Jeffrey Walton [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8km9k3sWKpjuj=69Y8SC=VHcDkBk=8O9RuCDOGtWGyqQQ@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).