Re: git-config gpg.program - more flexibility needed ?

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jun 6, 2022, 22:51 UTC
Message-ID: <Yp6E/1ye2Wi1mn0f@camp.crustytoothpaste.net>
In-Reply-To: <cVbMAjbLsxZPKlRxZe1zSKBcPx60ss_U_7r5ew78Dv3TVnCTMoisvnDgQXAh-2i4Li41Id6TAsO-rpc4DBIN41lMMIzhGIYxcQcfJ2eBM8Q=@protonmail.ch>

On 2022-06-06 at 11:37:18, Laura Smith wrote:

Show 5 quoted lines

> If my understanding is correct, gpg.program (https://git-scm.com/docs/git-config#Documentation/git-config.txt-gpgprogram) is a bit too hard-coded ?
> 
> There are excellent non-gpg CLI programs out there such as gosop, sequoia and sequoia-sop.
> 
> It would be great if instead of hard-coding the required flags that git requires, users were given the option to override the flags.

Unfortunately, it's a little hard to override the flags because different flags are passed in in different situations. For example, in some cases, we need the --status-fd output to properly determine whether the signature is trusted or not, and people can either pass in a key ID or not when signing. There isn't really a way to make things abstract in a useful way since there are so many possible permutations.

It should, however, be possible to write a wrapper around Sequoia or other programs that would provide the necessary behaviour if you'd like to use a different implementation.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA