git-config gpg.program - more flexibility needed ?

git-config gpg.program - more flexibility needed ?

[Laura Smith]

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

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.

[-- Attachment #2: publickey - n5d9xq3ti233xiyif2vp@protonmail.ch - 0x94FAF468.asc --]
[-- Type: application/pgp-keys, Size: 703 bytes --]

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

[brian m. carlson]

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

On 2022-06-06 at 11:37:18, Laura Smith wrote:
> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]