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
|
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 <mh.in.england@gmail.com>) id 1UPrrB-0004f9-Ah
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Apr 2013 10:02:21 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.174 as permitted sender)
client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f174.google.com;
Received: from mail-ob0-f174.google.com ([209.85.214.174])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UPrr5-00072C-8h
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Apr 2013 10:02:21 +0000
Received: by mail-ob0-f174.google.com with SMTP id wm15so242825obc.5
for <bitcoin-development@lists.sourceforge.net>;
Wed, 10 Apr 2013 03:02:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.60.136 with SMTP id h8mr479752obr.47.1365588129862; Wed,
10 Apr 2013 03:02:09 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.167.169 with HTTP; Wed, 10 Apr 2013 03:02:09 -0700 (PDT)
In-Reply-To: <201304100958.51054.andyparkins@gmail.com>
References: <CANEZrP1Y0JwQU-xSY1KdKrLnGDA4PhDwo9LtGkMaoCGw9=sZKA@mail.gmail.com>
<201304100958.51054.andyparkins@gmail.com>
Date: Wed, 10 Apr 2013 12:02:09 +0200
X-Google-Sender-Auth: Y83A8RQ_GbqCmGdrWFoz8u8ekGg
Message-ID: <CANEZrP226ADAaAr5qTdOoTNcBzfDF6pipGDXSNEGqq_kXsVa5w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1c42063d9f804d9fec32a
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
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: 1UPrr5-00072C-8h
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoinj 0.8
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: Wed, 10 Apr 2013 10:02:21 -0000
--001a11c1c42063d9f804d9fec32a
Content-Type: text/plain; charset=UTF-8
The key in the message was used in my last announcement, so that
establishes continuity there.
But regardless, all mails I send are signed automatically by Gmail using
either the gmail.com consumer key (for my posts to this list) or the
google.com corporate key (for my posts to the bitcoinj lists), see
dkim.orgfor more details on this. Whilst this is not signing in the
GPG web of
trust sense, realistically the Gmail DKIM keys are much safer than any key
I could create/maintain, and my ability to sign mail as hearn@google.com is
controlled by hardware second factors and various other rather intense
security systems I can't discuss.
I've considered just not having the additional Bitcoin-key based signatures
at all, but it would help keep continuity in the case that I leave Google
or if there's a DKIM key rotation.
On Wed, Apr 10, 2013 at 10:58 AM, Andy Parkins <andyparkins@gmail.com>wrote:
> On Tuesday 09 April 2013 22:03:35 Mike Hearn wrote:
>
> > To get bitcoinj 0.8, check out our source from git and then run *git
> fetch
> > --all; git checkout **cbbb1a2bf4d1*. This will place you on the 0.8
> release
> > in a secure manner. This message was written on Tuesday 9th April 2013
> and
>
> Not quite secure yet, because you didn't sign your email.
>
>
> Andy
>
> --
> Dr Andy Parkins
> andyparkins@gmail.com
>
--001a11c1c42063d9f804d9fec32a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style>The key in the message was used in my last anno=
uncement, so that establishes continuity there.=C2=A0</div><div style><br><=
/div><div style>But regardless, all mails I send are signed automatically b=
y Gmail using either the <a href=3D"http://gmail.com">gmail.com</a> consume=
r key (for my posts to this list) or the <a href=3D"http://google.com">goog=
le.com</a> corporate key (for my posts to the bitcoinj lists), see <a href=
=3D"http://dkim.org">dkim.org</a> for more details on this. Whilst this is =
not signing in the GPG web of trust sense, realistically the Gmail DKIM key=
s are much safer than any key I could create/maintain, and my ability to si=
gn mail as <a href=3D"mailto:hearn@google.com">hearn@google.com</a> is cont=
rolled by hardware second factors and various other rather intense security=
systems I can't discuss.</div>
<div style><br></div><div style>I've considered just not having the add=
itional Bitcoin-key based signatures at all, but it would help keep continu=
ity in the case that I leave Google or if there's a DKIM key rotation.<=
/div>
<div style><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Wed, Apr 10, 2013 at 10:58 AM, Andy Parkins <span dir=3D"l=
tr"><<a href=3D"mailto:andyparkins@gmail.com" target=3D"_blank">andypark=
ins@gmail.com</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">On Tuesday 09 April 2013 22:03:35 Mike Hearn=
wrote:<br>
<br>
> To get bitcoinj 0.8, check out our source from git and then run *git f=
etch<br>
> --all; git checkout **cbbb1a2bf4d1*. This will place you on the 0.8 re=
lease<br>
<div class=3D"im">> in a secure manner. This message was written on Tues=
day 9th April 2013 and<br>
<br>
</div>Not quite secure yet, because you didn't sign your email.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Andy<br>
<br>
--<br>
Dr Andy Parkins<br>
<a href=3D"mailto:andyparkins@gmail.com">andyparkins@gmail.com</a><br>
</font></span></blockquote></div><br></div>
--001a11c1c42063d9f804d9fec32a--
|
