From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Commit signing and pinentry problems
Date: Thu, 21 Nov 2019 00:48:31 +0000 [thread overview]
Message-ID: <20191121004831.GB6430@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAH8yC8n+ta4BSAE4rEfhKxe3T9poVdc94HvSk=6PEA4YbmwVyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On 2019-11-20 at 12:41:23, Jeffrey Walton wrote:
> Hi Everyone,
>
> 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
This isn't really a Git problem, so much as a GnuPG one.
You probably want to use the curses pinentry input instead of the GUI
one. If you're using Ubuntu, you can set "pinentry-program
/usr/bin/pinentry-curses" in ~/.gnupg/gpg-agent.conf, kill all of the
gpg-agent processes, and then attempt to sign again.
You may also need to set GPG_TTY and/or kill the gpg-agent process when
logging in remotely. See gpg-agent(1) for details on configuration and
use.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-11-21 0:48 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 [this message]
2020-03-02 14:09 ` Jeffrey Walton
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=20191121004831.GB6430@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.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 NNTP newsgroup(s).