{"thread":{"id":"3077","subject":"what exactly is git-tag looking for when you try to sign a tag?","startedAt":"2006-01-15T19:32:05Z","lastAt":"2006-01-15T20:02:27Z","messageCount":2,"participants":["Alan Chandler","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14689","messageId":"200601151932.05342.alan@chandlerfamily.org.uk","threadId":"3077","inReplyTo":null,"subject":"what exactly is git-tag looking for when you try to sign a tag?","fromName":"Alan Chandler","fromEmail":"alan@chandlerfamily.org.uk","sentAt":"2006-01-15T19:32:05Z","receivedAt":"2006-01-15T19:32:05Z","isPatch":false,"sender":{"key":"alan@chandlerfamily.org.uk","avatar":"https://gravatar.com/avatar/1862247e5ea8eac114c842f9dc3a5db6253754e24ef7171757cf97eedce48b8c?d=mp&s=160"},"body":"Since I reached my first release of my software this morning, I though I would \ntry and get a bit more formal with things and attempted to sign the tag\n\nAlthough I had tried gpg several years ago, I didn't seem to have any keys in \nmy keyring, so I just generated a new one with \n\ngpg --gen-key\n\nYou can see a key listed with you check for secret keys\n\nwith gpg -K\n\nbut then I tried to generate a tag with \n\ngit-tag -s v1.0\n\nand it complained that I don't have any secret key available.\n\nWhat exactly is the process of making one available?\n-- \nAlan Chandler\nhttp://www.chandlerfamily.org.uk\nOpen Source. It's the difference between trust and antitrust.\n"},{"id":"14692","messageId":"Pine.LNX.4.64.0601151155520.13339@g5.osdl.org","threadId":"3077","inReplyTo":"200601151932.05342.alan@chandlerfamily.org.uk","subject":"Re: what exactly is git-tag looking for when you try to sign a tag?","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-01-15T20:02:27Z","receivedAt":"2006-01-15T20:02:27Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Sun, 15 Jan 2006, Alan Chandler wrote:\n> \n> git-tag -s v1.0\n> \n> and it complained that I don't have any secret key available.\n> \n> What exactly is the process of making one available?\n\nDo \n\n\tgpg --list-secret-keys\n\nto check what keys you have available to sign with.\n\nThen, use\n\n\tgit tag -u \"key user name\" v1.0\n\nbecause what has _probably_ happened is that if you just use \"-s\" it will \npick your \"committer name\" as the key identifier, and you probably made \nyour keys using your real email or other identifier.\n\nSo \"-u <username>\" means the same thing as \"-s\", but with additionally \nspecifying _which_ key it should use.\n\nAlternatively, you should be able to just use \"gpg --edit-key <keyname>\" \nand then using \"adduid\" to add your git committer ID as a user of the key. \nAt which point \"git tag -s <tagname>\" should just work, since gpg will be \nable to match up the keys automatically.\n\n\t\tLinus\n"}]}