Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WAfoV-00064L-Gx for bitcoin-development@lists.sourceforge.net; Tue, 04 Feb 2014 13:13:19 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.52 as permitted sender) client-ip=209.85.219.52; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f52.google.com; Received: from mail-oa0-f52.google.com ([209.85.219.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WAfoT-0001NS-QG for bitcoin-development@lists.sourceforge.net; Tue, 04 Feb 2014 13:13:19 +0000 Received: by mail-oa0-f52.google.com with SMTP id i4so9821060oah.11 for ; Tue, 04 Feb 2014 05:13:12 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.138.228 with SMTP id qt4mr11134714oeb.38.1391519592198; Tue, 04 Feb 2014 05:13:12 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Tue, 4 Feb 2014 05:13:12 -0800 (PST) In-Reply-To: <20140204130312.GA23538@savin> References: <1D8E0828-D07F-46EF-9F9F-5CA83AA9DB59@plan99.net> <20140204130312.GA23538@savin> Date: Tue, 4 Feb 2014 14:13:12 +0100 X-Google-Sender-Auth: 4tzgINiV8rB_xXjlrJCCkUjEyiQ Message-ID: From: Mike Hearn To: Peter Todd Content-Type: multipart/alternative; boundary=047d7b342c96fdb84104f19466e4 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 T_FRT_LOLITA1 BODY: ReplaceTags: Lolita (1) 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WAfoT-0001NS-QG Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] bitcoinj 0.11 released, with p2sh, bip39 and payment protocol support X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 13:13:19 -0000 --047d7b342c96fdb84104f19466e4 Content-Type: text/plain; charset=UTF-8 Hah, good point. If nobody completes the homework, I'll post a fixed version tomorrow :) On Tue, Feb 4, 2014 at 2:03 PM, Peter Todd wrote: > On Tue, Feb 04, 2014 at 01:01:12PM +0100, Mike Hearn wrote: > > Hello, > > > > I'm pleased to announce the release of bitcoinj 0.11, a library for > writing Bitcoin applications that run on the JVM. BitcoinJ is widely used > across the Bitcoin community; some users include Bitcoin Wallet for > Android, MultiBit, Hive, blockchain.info, the biteasy.com block explorer > (written in Lisp!), Circle, Neo/Bee (Cypriot payment network), bitpos.me, > Bitcoin Touch, BlueMatt's relay network and DNS crawler, academic advanced > contracts research and more. > > > > The release-0.11 git tag is signed by Andreas Schildbach's GPG key. The > commit hash is 410d4547a7dd. This paragraph is signed by the same Bitcoin > key as with previous releases (check their release announcements to > establish continuity). Additionally, this email is signed using DKIM and > for the first time, a key that was ID verified by the Swiss government. > > > > Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m > > Signature for last paragraph: > H3DvWBqFHPxKW/cdYUdZ6OHjbq6ZtC5PHK4ebpeiE+FqTHyRLJ58BItbC0R2vo77h+DthpQigdEZ0V8ivSM7VIg= > > The above makes for a great homework problem for budding cryptographers: > Why did the three forms of signature, DKIM, long-lived bitcoin address, > and Official Swiss Government Identity fail to let you actually verify > you have the right code? (but make for great security theater) > > Bonus question: Who has the smallest work-factor for such an attack? > > Two rewards of 25mBTC for correct responses to each question from a > crypto newbie. > > > Thanks to Mike Belshe, the wallet can now send to P2SH addresses. > > Thanks > > > Generated signatures now use canonical S values. This will aid a future > hard-forking rule change which bans malleable signatures. > > Soft-forking rule change. > > -- > 'peter'[:-1]@petertodd.org > 000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0 > --047d7b342c96fdb84104f19466e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hah, good point. If nobody completes the homework, I'l= l post a fixed version tomorrow :)


=
On Tue, Feb 4, 2014 at 2:03 PM, Peter Todd <pe= te@petertodd.org> wrote:
On Tue, Feb 04, 2014 at 01= :01:12PM +0100, Mike Hearn wrote:
> Hello,
>
> I'm pleased to announce the release of bitcoinj 0.11, a library fo= r writing Bitcoin applications that run on the JVM. BitcoinJ is widely used= across the Bitcoin community; some users include Bitcoin Wallet for Androi= d, MultiBit, Hive, blo= ckchain.info, the bite= asy.com block explorer (written in Lisp!), Circle, Neo/Bee (Cypriot pay= ment network), bitpos.me= , Bitcoin Touch, BlueMatt's relay network and DNS crawler, academic adv= anced contracts research and more.
>
> The release-0.11 git tag is signed by Andreas Schildbach's GPG key= . The commit hash is 410d4547a7dd. This paragraph is signed by the same Bit= coin key as with previous releases (check their release announcements to es= tablish continuity). Additionally, this email is signed using DKIM and for = the first time, a key that was ID verified by the Swiss government.
>
> Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m
> Signature for last paragraph: H3DvWBqFHPxKW/cdYUdZ6OHjbq6ZtC5PHK4ebpei= E+FqTHyRLJ58BItbC0R2vo77h+DthpQigdEZ0V8ivSM7VIg=3D

The above makes for a great homework problem for budding cryptographe= rs:
Why did the three forms of signature, DKIM, long-lived bitcoin address,
and Official Swiss Government Identity fail to let you actually verify
you have the right code? (but make for great security theater)

Bonus question: Who has the smallest work-factor for such an attack?

Two rewards of 25mBTC for correct responses to each question from a
crypto newbie.

> Thanks to Mike Belshe, the wallet can now send to P2SH addresses.

Thanks

> Generated signatures now use canonical S value= s. This will aid a future hard-forking rule change which bans malleable sig= natures.

Soft-forking rule change.

--
'peter'[:-1]@pet= ertodd.org
000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0

--047d7b342c96fdb84104f19466e4--