git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: "Bernhard E. Reiter" <bernhard.reiter@intevation.de>
To: git@vger.kernel.org
Cc: gnupg-devel@gnupg.org
Subject: Stable GnuPG interface, git should use GPGME
Date: Fri, 10 Mar 2017 11:00:07 +0100
Message-ID: <201703101100.15214.bernhard.reiter@intevation.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

Dear Git-Devs,

git uses an pipe-and-exec approach to running a GnuPG binary 
as writen in the documentation [1]:

    gpg.program
           Use this custom program instead of "gpg" found on $PATH when making
           or verifying a PGP signature. The program must support the same
           command-line interface as GPG

please consider using libgpgme interfacing to GnuPG, because the gpg 
command-line interface is not considered an official API to GnuPG by the 
GnuPG-devs and thus potentially unstable. 

== Details

I'm involved in GnuPG development. For most applications using libgpgme is the 
way what GnuPG-devs would recommend, also see 

  https://wiki.gnupg.org/APIs .

GnuPG devs are making a good effort of trying to keep the command-line 
interface stable, though it is not for sure. Git is only using a small part 
of the interface, so the risk when keeping the current way is small. 
Still I believe git's stability and usability would profit when moving to 
libgpgme, especially with the coming move to GnuPG 2.2, better diagnosing 
messages and for cross-plattform usage.

== Usability problem with `gpg2` vs `gpg`

My use case today was signing and git by default found the `gpg` binary by 
default and the command failed. The reason is that I have `gpg2` installed 
and most applications use it right away. So git failed signing because 
the .gnupg configuration of the user was not ready for the old `gpg` which is 
still installed on Debian GNU/Linux for purposes of the operating system. If 
git would have used libgpgme, gpgme would have choosen the most uptodate 
version of `gpg` available (or configured) without me intervening via 
gpg.program. Now because of this problem you could adding a check for `gpg2` 
and fallback to `gpg`, but even better would be to move to libgpgme. >:)

Best Regards and thanks for maintaining Git as Free Software,
Bernhard

== how to respond

ps: Please copy me on replies as I am not on git@vger.kernel.org. 
pps: I've copied gnupg-devel@ so they can see I've send this report, you don't 
have to.


[1] 
https://github.com/git/git/blob/3bc53220cb2dcf709f7a027a3f526befd021d858/Documentation/config.txt
search for 'gpg.program'.

-- 
www.intevation.de/~bernhard (CEO)     +49 541 33 508 3-3
Intevation GmbH, Osnabrück, Germany; Amtsgericht Osnabrück, HRB 18998
Owned and run by Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply index

Thread overview: 19+ messages in thread (expand / mbox.gz / Atom feed / [top])
2017-03-10 10:00 Bernhard E. Reiter [this message]
2017-03-10 14:23 ` Ævar Arnfjörð Bjarmason
2017-03-13 10:14   ` Michael J Gruber
2017-03-13 12:49     ` Bernhard E. Reiter
2017-03-14 10:39       ` Michael J Gruber
2017-03-17  9:56         ` Bernhard E. Reiter
2017-03-22 17:15           ` Werner Koch
2017-03-22 18:46             ` Peter Lebbing
2017-03-23  6:52               ` Werner Koch
2017-03-23  7:29             ` Bernhard E. Reiter
2017-03-23 10:56               ` Werner Koch
2017-03-13 10:30   ` Bernhard Reiter
2017-03-10 18:54 ` Linus Torvalds
2017-03-10 20:26   ` Theodore Ts'o
2017-03-13 11:14   ` Bernhard E. Reiter
2017-03-13 12:53     ` Jeff King
2017-03-11  0:10 ` brian m. carlson
2017-03-13 12:29   ` Bernhard E. Reiter
2017-03-13 19:48   ` Christian Neukirchen

Reply instructions:

You may reply publically 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 to all the recipients using the --to, --cc,
  and --in-reply-to switches of git-send-email(1):

  git send-email \
    --in-reply-to=201703101100.15214.bernhard.reiter@intevation.de \
    --to=bernhard.reiter@intevation.de \
    --cc=git@vger.kernel.org \
    --cc=gnupg-devel@gnupg.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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox