From: Stefan Beller <sbeller@google.com>
To: tom@oxix.org, Matthieu Moy <Matthieu.Moy@imag.fr>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: [Request for Documentation] Differentiate signed (commits/tags/pushes)
Date: Mon, 6 Mar 2017 11:59:24 -0800 [thread overview]
Message-ID: <CAGZ79kYxD9B_+3vBgO+Z-wh2GMg_REazA-xpTSAqe3_64VMV3w@mail.gmail.com> (raw)
When discussing migrating to a new hashing function, I tried to learn
about the subtleties of the different things that can be gpg-signed in
Git.
What is the difference between signed commits and tags?
(Not from a technical perspective, but for the end user)
Both of them certify that a given tree is the desired
content for your repository, but git-tag seems to be designed for
conveying a trusted state to collaborators, whereas git-commit
is primarily designed to just record a state.
So in which case would I want to use a signed commit?
(which then overlaps with signed pushes)
A signed push can certify that a given payload (consisting
of multiple commits on possibly multiple branches) was transmitted
to a remote, which can be recorded by the remote as e.g. a proof
of work.
The man page of git-commit doesn't discuss gpg signing at all,
git-tag has some discussion on how to properly use tags. Maybe
there we could have a discussion on when not to use tags, but
rather signed commits?
Off list I was told gpg-signed commits are a "checkbox feature",
i.e. no real world workflow would actually use it. (That's a bold
statement, someone has to use it as there was enough interest
to implement it, no?)
Thanks,
Stefan
next reply other threads:[~2017-03-06 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:59 Stefan Beller [this message]
2017-03-06 22:13 ` [Request for Documentation] Differentiate signed (commits/tags/pushes) Junio C Hamano
2017-03-06 22:52 ` Stefan Beller
2017-03-07 0:08 ` Junio C Hamano
2017-03-07 0:58 ` Stefan Beller
2017-03-06 23:03 ` Junio C Hamano
2017-03-06 23:59 ` Jakub Narębski
2017-03-07 0:16 ` Junio C Hamano
2017-03-07 7:16 ` Matthieu Moy
2017-03-07 9:23 ` Jeff King
2017-03-07 9:45 ` Tom Jones
2017-03-07 22:19 ` Stefan Beller
2017-03-08 5:41 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kYxD9B_+3vBgO+Z-wh2GMg_REazA-xpTSAqe3_64VMV3w@mail.gmail.com \
--to=sbeller@google.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tom@oxix.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).