From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-config gpg.program - more flexibility needed ?
Date: Mon, 6 Jun 2022 22:51:43 +0000 [thread overview]
Message-ID: <Yp6E/1ye2Wi1mn0f@camp.crustytoothpaste.net> (raw)
In-Reply-To: <cVbMAjbLsxZPKlRxZe1zSKBcPx60ss_U_7r5ew78Dv3TVnCTMoisvnDgQXAh-2i4Li41Id6TAsO-rpc4DBIN41lMMIzhGIYxcQcfJ2eBM8Q=@protonmail.ch>
[-- 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 --]
prev parent reply other threads:[~2022-06-06 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 11:37 git-config gpg.program - more flexibility needed ? Laura Smith
2022-06-06 22:51 ` brian m. carlson [this message]
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=Yp6E/1ye2Wi1mn0f@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=n5d9xq3ti233xiyif2vp@protonmail.ch \
/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).