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

Re: Preventing unsigned commit/merge/tag

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 31, 2013, 19:27 UTC
Message-ID
<20131231192736.GI451338@vauxhall.crustytoothpaste.net>
In-Reply-To
<CAH_OBicyrd=H1uG+_5-Jz=gK0fLsPbKKhkypWDG5yNb0umnhiw@mail.gmail.com>
On Tue, Dec 31, 2013 at 12:49:01PM -0500, shawn wilson wrote:
Show 5 quoted lines
> What's the best way of doing this? I'd prefer this be a pre hook on
> the server that rejects and the user has to rebase and fix their
> stuff. Though, if there's some way to make it easier for users not to
> mess up (other than an alias for everything which I'll probably do
> anyway) that would be useful. Any ideas?

I don't believe the sign-on-rebase stuff ever got picked up, so at the moment this wouldn't be a good idea, since each and every commit would have to be manually amended. It seems it never made it from the list into Junio's queue whatsoever. And the always-sign code is only in pu at the moment.

But if you wanted to anyway, you could simply use a pre-receive hook and walk the tree, verifying the signatures of each commit against some canonical list of approved keys.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: shawn wilson
Message 2 of 2 in “Preventing unsigned commit/merge/tag”
  1. shawn wilsonDec 31, 2013
  2. brian m. carlsonDec 31, 2013

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.