Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WAff9-0005a3-NA for bitcoin-development@lists.sourceforge.net; Tue, 04 Feb 2014 13:03:39 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.96 as permitted sender) client-ip=62.13.148.96; envelope-from=pete@petertodd.org; helo=outmail148096.authsmtp.net; Received: from outmail148096.authsmtp.net ([62.13.148.96]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WAff8-0003vI-5I for bitcoin-development@lists.sourceforge.net; Tue, 04 Feb 2014 13:03:39 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s14D3Vcn056142; Tue, 4 Feb 2014 13:03:31 GMT Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s14D3QXJ008092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 4 Feb 2014 13:03:28 GMT Date: Tue, 4 Feb 2014 08:03:13 -0500 From: Peter Todd To: Mike Hearn Message-ID: <20140204130312.GA23538@savin> References: <1D8E0828-D07F-46EF-9F9F-5CA83AA9DB59@plan99.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <1D8E0828-D07F-46EF-9F9F-5CA83AA9DB59@plan99.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: be0876dd-8d9c-11e3-94fa-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdgYUHlAWAgsB AmIbWldeUF57W2o7 bAxPbAVDY01GQQRq WVdMSlVNFUsrABh1 BX92KBlyfwVPejBx ZUVqWD4JCURyckAp FlNcQWRVeGZhPWMC WUQOJh5UcAFPdx8U a1N6AHBDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4BHyI3 QBEEH313WxRcDz8+ KxEvMVMQWA4OM1ky eUN7QlJcexUTElYP fQlEBiMRP1AQQict EUtCR0kCFzZaRW9H HwUwJQVUagAA X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.109/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record 0.0 T_FRT_LOLITA1 BODY: ReplaceTags: Lolita (1) X-Headers-End: 1WAff8-0003vI-5I Cc: bitcoin-development@lists.sourceforge.net 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:03:39 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 04, 2014 at 01:01:12PM +0100, Mike Hearn wrote: > Hello, >=20 > I'm pleased to announce the release of bitcoinj 0.11, a library for writi= ng Bitcoin applications that run on the JVM. BitcoinJ is widely used across= the Bitcoin community; some users include Bitcoin Wallet for Android, Mult= iBit, Hive, blockchain.info, the biteasy.com block explorer (written in Lis= p!), Circle, Neo/Bee (Cypriot payment network), bitpos.me, Bitcoin Touch, B= lueMatt's relay network and DNS crawler, academic advanced contracts resear= ch and more. >=20 > The release-0.11 git tag is signed by Andreas Schildbach's GPG key. The c= ommit hash is 410d4547a7dd. This paragraph is signed by the same Bitcoin ke= y as with previous releases (check their release announcements to establish= continuity). Additionally, this email is signed using DKIM and for the fir= st time, a key that was ID verified by the Swiss government. >=20 > Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m > Signature for last paragraph: H3DvWBqFHPxKW/cdYUdZ6OHjbq6ZtC5PHK4ebpeiE+F= qTHyRLJ58BItbC0R2vo77h+DthpQigdEZ0V8ivSM7VIg=3D 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 h= ard-forking rule change which bans malleable signatures. Soft-forking rule change. --=20 'peter'[:-1]@petertodd.org 000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0 --gKMricLos+KVdGMg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iQGrBAEBCACVBQJS8OUQXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDA3NTgyOWY2MTY5Yzc5ZDdkNWFhYTIwYmZhOGRhNmU5ZWRi MjM5M2M0Zjg2NjJiYTAvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftMTgf9FRzNQ3Zv7/P2XlnEwZ9mkeQ4 qJFW1mOTTaS2sGGJ2UmckJj9SPU7lX+XtazFrTMYwMXxI7JlSuTa6zsmXqHyM4XT xrB3y6F7yW/jNi8e31GKsmeUhesTgx+JVwJHr47N1wee/2nR6VwyNCHDZBUsy8zk EqapYnBGvHu+bjbGbG3p+1czAZwHbVeDKagHU8w2Bkr9dTrjXPiaqcpWrNZQ1iKr 7CKT9H28yAyTEwNfx+3Q1irQMTXmnbTUS0VJIgjvwLTsR5PhkAhOXrEWuUZ072Wb jcmWxmbBYDlY/WlNpsmj9pGoghM9pCvUx1I17Y6K29zHo/NsM+tsLQZ2UHd9lQ== =Qcxt -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--