From: Schittli Thomas Date: Sat, 19 Apr 2014 18:24:39 GMT Subject: AW: Git: Please allow to use gpgsm to support X.509 certificates Message-ID: <87FCFF58480C9949AF1110DED8AC48E4E9A0DFCF@BASMX001.akros.ch> In-Reply-To: <20140419151913.GA29656@serenity.lan> Hi John, > Have you tried `git config gpg.program gpgsm`? wau, thanks a lot for this hint!, it works :-) I think a "seamless" integration for all certificate-types would be better, but I try to motivate GnuPG to merge the function of gpgsm.exe into gpg.exe. This would give a great benefit for all applications using GnuPG. Thanks a lot, kind regards, Tom ________________________________________ Von: git-owner@vger.kernel.org [git-owner@vger.kernel.org]" im Auftrag von "John Keeping [john@keeping.me.uk] Gesendet: Samstag, 19. April 2014 17:19 An: Schittli Thomas Cc: git@vger.kernel.org Betreff: Re: Git: Please allow to use gpgsm to support X.509 certificates On Sat, Apr 19, 2014 at 11:03:07AM +0000, Schittli Thomas wrote: > last night, brian m. Carlson explained, that "Git wants a key that can > be used by GnuPG" and therefore X.509 certificates are not supported. > > As you probably know, since 3 years gpg supports X.509 - > unfortunately, gpg does not automatically detect X.509 certificates > and we have to use gpgsm instead of gpg. > The good thing: for identical functions, the command line arguments are identical :-) > > Therefore: please allow to configure git, so that it can use gpg or gpgsm. > Or even better: if gpg fails, then please automatically try gpgsm :-) Have you tried `git config gpg.program gpgsm`?