1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP2NyvRKwSEZORjAOq6G7UqLv=F3FjxmGNTPMT10yWGxzw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
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 <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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <pete@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 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
<div dir=3D"ltr">Hah, good point. If nobody completes the homework, I'l=
l post a fixed version tomorrow :)</div><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Tue, Feb 4, 2014 at 2:03 PM, Peter Todd <span=
dir=3D"ltr"><<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pe=
te@petertodd.org</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tue, Feb 04, 2014 at 01=
:01:12PM +0100, Mike Hearn wrote:<br>
> Hello,<br>
><br>
> 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, <a href=3D"http://blockchain.info" target=3D"_blank">blo=
ckchain.info</a>, the <a href=3D"http://biteasy.com" target=3D"_blank">bite=
asy.com</a> block explorer (written in Lisp!), Circle, Neo/Bee (Cypriot pay=
ment network), <a href=3D"http://bitpos.me" target=3D"_blank">bitpos.me</a>=
, Bitcoin Touch, BlueMatt's relay network and DNS crawler, academic adv=
anced contracts research and more.<br>
><br>
> 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.<br>
><br>
> Key: 16vSNFP5Acsa6RBbjEA7QYCCRDRGXRFH4m<br>
> Signature for last paragraph: H3DvWBqFHPxKW/cdYUdZ6OHjbq6ZtC5PHK4ebpei=
E+FqTHyRLJ58BItbC0R2vo77h+DthpQigdEZ0V8ivSM7VIg=3D<br>
<br>
</div>The above makes for a great homework problem for budding cryptographe=
rs:<br>
Why did the three forms of signature, DKIM, long-lived bitcoin address,<br>
and Official Swiss Government Identity fail to let you actually verify<br>
you have the right code? (but make for great security theater)<br>
<br>
Bonus question: Who has the smallest work-factor for such an attack?<br>
<br>
Two rewards of 25mBTC for correct responses to each question from a<br>
crypto newbie.<br>
<div class=3D"im"><br>
> Thanks to Mike Belshe, the wallet can now send to P2SH addresses.<br>
<br>
Thanks<br>
<br>
</div><div class=3D"im">> Generated signatures now use canonical S value=
s. This will aid a future hard-forking rule change which bans malleable sig=
natures.<br>
<br>
</div>Soft-forking rule change.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
'peter'[:-1]@<a href=3D"http://petertodd.org" target=3D"_blank">pet=
ertodd.org</a><br>
000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0<br>
</font></span></blockquote></div><br></div>
--047d7b342c96fdb84104f19466e4--
|
