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

Enterprise wide Git commit signing

From
EREthan Rahn <erahn@arista.com>
Date
Sep 10, 2020, 19:16 UTC
Message-ID
<CAMk6QYPgC1ch_umvGvYRa8F97iY6ynO-ApYC8zHwGzPY3TauDg@mail.gmail.com>
Hello Git Users,

My name is Ethan Rahn and I lead Product Security at Arista Networks. I recently completed work on a project which I wanted to highlight for everyone on this list. This is a means for allowing an enterprise to centrally manage code signing keys for all engineers, enforce the signing of all git commits, and audit that the source code repository was not altered after signing. You can read the full blog post here: https://eos.arista.com/commit-signing-with-git-at-enterprise-scale/ . Part of what makes this so exciting to me is that I haven't seen commit signing done at this level before, especially not with having the repo be auditable after the fact. By having the repo be auditable the level of vulnerable infrastructure can be reduced to the code signing keystore; in other words the code repository can be validated at any time to ensure it was not tampered with.

I think that the work done here is very interesting because I have not seen it done elsewhere. Supply chain attacks through source code repositories are a real problem. The solution in most cases seems to be setting up a security perimeter around the repository and checking for unauthorized accesses. If an unauthorized access does occur, or credentials are stolen, it is hard to know the complete set of unauthorized changes made, especially if they are mixed with legitimate work of a number of users over a period of time.

Happy to answer any questions around this or take comments. The work around key management has been open sourced ( references in the blog post ) so that the open source community can benefit from this.

Cheers,
Ethan
Next: Christian Couder
Message 1 of 2 in “Enterprise wide Git commit signing”
  1. Ethan RahnSep 10, 2020
  2. Christian CouderSep 13, 2020

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.