From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-pull and tag objects
Date: Sat, 10 Feb 2007 22:32:05 +0100 [thread overview]
Message-ID: <eqldhe$h7i$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0702100938540.8424@woody.linux-foundation.org
Linus Torvalds wrote:
> On Sat, 10 Feb 2007, Theodore Tso wrote:
>> 3) The git-tag man page talks about GPG signing tags, but it doesn't
>> talk about how a GPG-signed tag is validated. Does this happen
>> manually or automatically?
>
> Use "git verify-tag X" to see something like this:
>
> [torvalds@woody linux]$ git-verify-tag v2.6.17
> gpg: Signature made Sat 17 Jun 2006 06:49:59 PM PDT using DSA key ID 76E21CBB
> gpg: Good signature from "Linus Torvalds (tag signing key) <torvalds@osdl.org>"
>
> but you obviously need to have the public key in question available to
> you.
One of the solutions, used in git.git repository, is to put public key
as a out-of-tree blob using git-hash-object, then tag it using singed tag
with instruction about how to extract key in the tag message (tag comment).
$ git cat-file -p junio-gpg-pub
object 0246401b5d117e01717149c413aa2f8702a83d4f
type blob
tag junio-gpg-pub
tagger Junio C Hamano <junkio@cox.net> Tue Dec 13 16:33:29 2005 -0800
GPG key to sign git.git archive.
This blob object contains the GPG public key I use to sign git.git
archive.
To use it to verify tags I signed, do:
$ git-cat-file blob junio-gpg-pub | gpg --import
to import it into your keyring, and then
$ git-verify-tag $tag_to_be_verified
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-10 21:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 11:16 git-pull and tag objects Alex Bennee
2007-02-09 9:33 ` Alex Riesen
2007-02-09 23:19 ` Junio C Hamano
2007-02-10 0:14 ` [PATCH] git-fetch: document automatic tag following Junio C Hamano
2007-02-10 14:23 ` git-pull and tag objects Theodore Tso
2007-02-10 17:56 ` Linus Torvalds
2007-02-10 21:32 ` Jakub Narebski [this message]
2007-02-10 21:58 ` Linus Torvalds
2007-02-11 21:55 ` Junio C Hamano
2007-02-12 0:40 ` Jakub Narebski
2007-02-11 0:25 ` Theodore Tso
2007-02-11 3:21 ` Linus Torvalds
2007-02-11 5:52 ` Junio C Hamano
2007-02-11 17:49 ` Linus Torvalds
2007-02-11 19:17 ` Junio C Hamano
2007-02-11 19:21 ` Junio C Hamano
2007-02-11 19:25 ` Linus Torvalds
2007-02-11 21:41 ` Junio C Hamano
2007-02-12 16:27 ` Theodore Tso
2007-02-13 6:17 ` Junio C Hamano
2007-02-14 6:38 ` Linus Torvalds
2007-02-14 7:22 ` Junio C Hamano
2007-02-14 11:18 ` Johannes Schindelin
2007-02-14 16:35 ` Linus Torvalds
2007-02-15 1:21 ` Jakub Narebski
2007-02-15 1:34 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='eqldhe$h7i$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.