git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH] gpg: add support for gpgsm

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 31, 2016, 15:49 UTC
Message-ID
<xmqq60w2r6kq.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160331142200.GB31116@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> But maybe we could pull this out to a separate config option, like
> "commit.defaultSignatureType", which could be either "gpg", "gpgsm", or
> "auto" to enable the behavior you have here.  Then savvy users can pick
> the type they plan to use.

Yes, I think the topic should start without "auto" guessing mode to get the basics right; guessing mode can come after we are comfortable with the solidness of the resulting codebase.

> And regardless of the default type for creating signatures, we'd still
> automatically verify signatures from either type.

Again, true, as long as we can tell which program to use to verify, there is no guesswork involved, and this can and should be in the early part of the topic.

Thanks.
Previous: Carlos Martín NietoNext: Junio C Hamano
Message 4 of 8 in “gpg: add support for gpgsm”
  1. gpg: add support for gpgsmCarlos Martín Nieto, Mar 31, 2016
  2. Jeff KingMar 31, 2016
  3. Carlos Martín NietoMar 31, 2016
  4. Junio C HamanoMar 31, 2016
  5. Junio C HamanoMar 31, 2016
  6. Jeff KingMar 31, 2016
  7. Carlos Martín NietoMar 31, 2016
  8. Jeff KingMar 31, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.