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

Re: signing commits with openssl/PKCS#11

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Oct 24, 2012, 09:46 UTC
Message-ID
<5087B8E7.8010306@drmicha.warpmail.net>
In-Reply-To
<1392235.RizYqAYdkC@off17>
Mat Arge venit, vidit, dixit 22.10.2012 15:38:
Show 10 quoted lines
> Hy!
> 
> I would like to sign each commit with a X.509 certificate and a private key 
> stored on a PKCS#11 token. I assume that that should be possible somehow using 
> a hook which calls openssl. Does somebody know a working implementation of 
> this?
> 
> cheers
> Mat
> 

In principle, we have an almost pluggable architecture. See for example the latter part of the 2nd post in

http://article.gmane.org/gmane.comp.version-control.git/175127

Unless you want to change git itself, you're probably better off storing your non-gpg signatures in a note (or a self-created signed tag). To sign the commit rev, you could sign the output of "git cat-file commit rev" (or of "git rev-parse rev") and store that signature in a note that commit. To verify, you verify the note against the commit.

Michael
Previous: Mat ArgeNext: Mat Arge
Message 2 of 5 in “signing commits with openssl/PKCS#11”
  1. Mat ArgeOct 22, 2012
  2. Michael J GruberOct 24, 2012
  3. Mat ArgeOct 25, 2012
  4. Brandon CaseyOct 25, 2012
  5. Mat ArgeOct 25, 2012

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.