git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Fabian Stelzer <fs@gigacodes.de>
Cc: git@vger.kernel.org
Subject: Re: Git SSH/GPG signing flags and config
Date: Sun, 28 Nov 2021 15:20:37 -0800	[thread overview]
Message-ID: <xmqqzgpn50l6.fsf@gitster.g> (raw)
In-Reply-To: <20211128125704.4twinfd3wriwdntz@fs> (Fabian Stelzer's message of "Sun, 28 Nov 2021 13:57:04 +0100")

Fabian Stelzer <fs@gigacodes.de> writes:

> Hi everyone,
> the `signing git objects with ssh` series was released with 2.34 and
> i'd like to thank everyone for your support and the good reviews!
> I think it would be beneficial now to adjust some of the wording in
> flags and the config. Currently everything is configured via gpg.* and
> all the `please sign this` flags are named --(no-?)gpg-sign.
> I would be in favor of a more generic flag independent of the signing
> mechanism. Adding something like `--ssh-sign` would suggest that you'd
> be able to switch signing format with it which i think would not be
> terribly useful. If you need to use multiple signing mechanism those
> would usually be configured per repository and can easily be done with
> an `includeif gitdir:` in your config.
> Therefore i would suggest just adding a generic `--(no-?)sign` to all
> the commands that support gpg-sign right now. The only problem i see
> is a conflict with `--signoff` so i'm open to other naming ideas. The
> same goes for the config. `sign.` as an alias to `gpg.` would work
> well with the current settings.
> Let me know what you think and i could prepare a first patch for one
> command to see what the alias / config / docs change could look like.

I do share your worry about --sign to be confused with the sign-off
procedure, and that was why the original used --gpg-sign.  We are
extending "gpg" part because "gpg" is not the only cryptographic
signing protocol we support, so perhaps --crypto-sign would still be
in the orginal spirit of "This is different from the sign-off, but
is a cryptographic signature, but it is a mouthful.


  reply	other threads:[~2021-11-28 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 12:57 Git SSH/GPG signing flags and config Fabian Stelzer
2021-11-28 23:20 ` Junio C Hamano [this message]
2021-12-05 11:36   ` Fabian Stelzer

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=xmqqzgpn50l6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=fs@gigacodes.de \
    --cc=git@vger.kernel.org \
    /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).