public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Cc: Vitalik Buterin <vbuterin@gmail.com>,
	Michael Gooden <me@michaelgooden.net>,
	bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoinj 0.11 released, with p2sh, bip39 and payment protocol support
Date: Fri, 7 Feb 2014 11:48:17 +0100	[thread overview]
Message-ID: <B652BED9-6DAB-40D2-9164-206787F5DDEF@plan99.net> (raw)
In-Reply-To: <20140207092141.GA3532@savin>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

Here’s a new release announcement with full ID’s this time:

The v0.11 tag is signed by Andreas Schildbach’s GPG key (fingerprint E944 AE66 7CF9 60B1 004B C32F CA66 2BE1 8B87 7A60). The commit hash is 410d4547a7dd20745f637313ed54d04d08d28687.

Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m
Signature: IFXzt4ZdWFEpLrAXRDnQS6ZKJYGmyHDHtyAgeg/2/EaTvg41jSsUQW8rq19evT2UNp+eP0+OWgWM7iDKrTv11DY=

It’s worth noting that this problem crops up in other contexts too. For instance, it’s very common for people to identify PGP keys by a short identifier.

As it happens I do have a PGP key, fingerprint C85A AB0F 7A1C CCA3 2BFC EECC F2E4 861C 9988 816F, and I just signed Andreas’ key with it. However, as I’m not myself well connected in the web of trust, that doesn’t add a whole lot. But now that my key is effectively signed out of band by SwissSign so if people wanted to manually trace a trust path across systems, they could. I am skeptical anyone will :-)

Note that thanks to Gary Rowe, there is a Maven dependency checker plugin that verifies the (full) hashes of library dependencies. It could be better integrated but it provides another backstop.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7453 bytes --]

      reply	other threads:[~2014-02-07 11:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 12:01 [Bitcoin-development] bitcoinj 0.11 released, with p2sh, bip39 and payment protocol support Mike Hearn
2014-02-04 13:03 ` Peter Todd
2014-02-04 13:13   ` Mike Hearn
2014-02-04 13:17     ` Peter Todd
2014-02-04 14:43       ` Jeff Garzik
2014-02-04 14:46         ` Peter Todd
2014-02-04 15:17       ` Natanael
2014-02-04 16:04         ` Peter Todd
2014-02-05  7:57           ` Jeremy Spilman
2014-02-05 15:09           ` Brooks Boyd
2014-02-07  9:21   ` Peter Todd
2014-02-07 10:48     ` Mike Hearn [this message]

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=B652BED9-6DAB-40D2-9164-206787F5DDEF@plan99.net \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=me@michaelgooden.net \
    --cc=pete@petertodd.org \
    --cc=vbuterin@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox