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

Re: Cross-signing commits

From
SLSoni L. <fakedme+git@gmail.com>
Date
Mar 5, 2021, 21:53 UTC
Message-ID
<537258e7-fcf4-814c-c7c1-95c8d525f34a@gmail.com>
In-Reply-To
<YEKmVWHJchUhxZmn@camp.crustytoothpaste.net>
On 2021-03-05 6:44 p.m., brian m. carlson wrote:
Show 8 quoted lines
> On 2021-03-05 at 16:47:14, Soni L. wrote:
> > We have a somewhat unusual use-case where we need to cross-sign commits. Is
> > there any way to do this in git? As far as one can tell, attempting to
> > cross-sign a commit would cause its hash to change, and creating a signed
> > child commit would break fast-forward merges. So these are a no-go.
>
> 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.

Previous: brian m. carlsonNext: brian m. carlson
Message 3 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.