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

Managing signed git tags and expiring keys

From
Jonathan "Duke" Leto <jonathan@leto.net>
Date
Jan 6, 2012, 08:13 UTC
Message-ID
<CABQG1aSY53-Z73CiUf2kstfaKLJ8zBGzu51CFdWHGiVR16JJ7w@mail.gmail.com>
Howdy,

My question is about the Git workflow in a repository which has signed tags and uses expiring keys in a chain of trust.

When the key changes, all existing tags are signed with the previous key in the chain of trust.

Do people:
1) resign all the tags, causing people to overwrite their local tags
2) keep all versions of the keys in the chain of trust
3) something else more involved?
Is anybody doing this currently?
Thanks!
Duke
-- 
Jonathan "Duke" Leto <jonathan@leto.net>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.
Next: Junio C Hamano
Message 1 of 2 in “Managing signed git tags and expiring keys”
  1. Jonathan "Duke" LetoJan 6, 2012
  2. Junio C HamanoJan 6, 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.