Re: GPG signing for git commit?
- From
Robin H. Johnson <robbat2@gentoo.org>
- Date
- Apr 15, 2009, 18:55 UTC
- Message-ID
- <20090415185554.GG23644@curie-int>
- In-Reply-To
- <49D99BB2.2090906@vilain.net>
On Mon, Apr 06, 2009 at 06:05:38PM +1200, Sam Vilain wrote:
> This system allows for *pushes* to be signed and in general laying the > foundation for knowing that commits are authentic without the intrusion > into the refs/tags/* space that making lots of signed tags would imply.
I'm on the lookout for something similar, so that we can be sure who introduced some change into the central repo.
One of the spots that we're looking for in this, is a model something like what follows. Firstly, a "proxy maintainer" (PM) is a developer with commit rights to the central repo, that's willing to proxy commits by an outside source for some specific package. Think of them as the kernel subsystem maintainer, but many more of them. The PM is still expected to verify the work before passing it on the central repo.
So we have a commit with author+committer being the outside source, and now we want to record (in an easily reviewable fashion) that a specific changeset was introduced to the central tree by the PM.
Not sure of the best route to trace this data. Signing the SHA1 makes the most sense, but need to be able to do that without polluting the tag namespace.
If the changeset does not have an associated signature, we'd like to reject it at the central repo.
-- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : robbat2@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85