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

RE: Cross-signing commits

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Mar 5, 2021, 23:45 UTC
Message-ID
<022c01d71219$a18eed60$e4acc820$@nexbridge.com>
In-Reply-To
<YEKpoiy//SR5Nt3q@camp.crustytoothpaste.net>
On March 5, 2021 4:59 PM, brian m. carlson wrote:
Show 23 quoted lines
> On 2021-03-05 at 21:53:14, Soni L. wrote:
> > On 2021-03-05 6:44 p.m., brian m. carlson wrote:
> > > Can you explain what you mean by "cross-signing"?  Are you proposing
> > > a situation where two parties sign the same commit?
> >
> > Yep. See, the repos enforce signing, but they can also be forks. If
> > someone wants to track upstream in one of their branches they just
> > can't. Would be cool if they could just say they trust the commits by
> > signing the relevant commits with their own key instead - on the
> > assumption that they actually reviewed said commits.
> 
> Git doesn't natively support having multiple signatures in a commit, although
> it is of course possible to do, since OpenPGP supports it.
> However, as you noted, changing the signature changes the object ID, so if
> you re-sign a commit for any reason, that changes the commit ID.
> There isn't any way around this at all; that's just how it works.
> 
> So you can either re-sign or have an unchanged commit ID, but not both at
> the same time.
> 
> You can use additional empty signed commits or signed tags, or you can use
> some sort of external system that keeps track of additional signatures or
> approvals if you want.
If your workflow requires multiple signatures on the same commit, you have options:
1. Use signed tags. So you can put multiple OpenPGP signed tags on a commit, representing each person's individual sign-off. Tags would be my preference as they show up explicitly in the git log --decorate output. Of course you will need a naming standard for this class of tags.
2. Create empty child commits with the desired commit as parent, and each person can sign their own commit - not really a great idea as history gets messy and potentially confusing.

Regards, Randall

-- Brief whoami: NonStop developer since approximately 211288444200000000 UNIX developer since approximately 421664400 -- In my real life, I talk too much.

Previous: brian m. carlson
Message 5 of 5 in “Cross-signing commits”
  1. Soni L.Mar 5, 2021
  2. brian m. carlsonMar 5, 2021
  3. Soni L.Mar 5, 2021
  4. brian m. carlsonMar 5, 2021
  5. Randall S. BeckerMar 5, 2021

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.