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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <will.yager@gmail.com>) id 1XLFxd-00038S-B8
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Aug 2014 18:22:45 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.53 as permitted sender)
client-ip=209.85.216.53; envelope-from=will.yager@gmail.com;
helo=mail-qa0-f53.google.com;
Received: from mail-qa0-f53.google.com ([209.85.216.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XLFxT-0006ZF-73
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Aug 2014 18:22:45 +0000
Received: by mail-qa0-f53.google.com with SMTP id v10so10687979qac.40
for <bitcoin-development@lists.sourceforge.net>;
Sat, 23 Aug 2014 11:22:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.140.33.230 with SMTP id j93mr18424838qgj.64.1408818147724;
Sat, 23 Aug 2014 11:22:27 -0700 (PDT)
Received: by 10.140.51.37 with HTTP; Sat, 23 Aug 2014 11:22:27 -0700 (PDT)
In-Reply-To: <20140823175038.GU22640@nl.grid.coop>
References: <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
<53F3DFF7.9070709@jrn.me.uk>
<CAJHLa0ORxgQrkc4oiqSa3NdNHLU-0pmZDLjXUSpBKWBsBWTgcQ@mail.gmail.com>
<1569765.oHsHtFYAhh@1337h4x0r> <53F8C656.6010200@riseup.net>
<20140823175038.GU22640@nl.grid.coop>
Date: Sat, 23 Aug 2014 13:22:27 -0500
Message-ID: <CAG8oi1O0RzEmnPg+t1GONnpmmEFucB_Ux35Ca8Y6g0TZf6CiCQ@mail.gmail.com>
From: William Yager <will.yager@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a113a75ce3f93400501500973
X-Spam-Score: 0.6 (/)
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
(will.yager[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1XLFxT-0006ZF-73
Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages
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: Sat, 23 Aug 2014 18:22:45 -0000
--001a113a75ce3f93400501500973
Content-Type: text/plain; charset=UTF-8
On Sat, Aug 23, 2014 at 12:50 PM, Troy Benjegerdes <hozer@hozed.org> wrote:
> they can hire a hacker who will
> find a misplaced (} in your crypto code, and all the work you did to
> encrypt wire protocols becomes silently worthless.
>
Not to mention encrypting basically non-sensitive inter-node traffic is
almost completely worthless in providing anonymity anyway...
Seriously, I have not heard a strong justification for this proposal yet. I
have heard some people talking about Tor-ifying communications, but that is
a completely different issue and should not be confused with just
"encrypting bitcoin messages".
--001a113a75ce3f93400501500973
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Sat, Aug 23, 2014 at 12:50 PM, Troy Benjegerdes <span d=
ir=3D"ltr"><<a href=3D"mailto:hozer@hozed.org" target=3D"_blank">hozer@h=
ozed.org</a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=C2=A0they can hire a hacker who will<br>
find a misplaced (} in your crypto code, and all the work you did to<br>
encrypt wire protocols becomes silently worthless.<br></blockquote><div><br=
></div><div>Not to mention encrypting basically non-sensitive inter-node tr=
affic is almost completely worthless in providing anonymity anyway...=C2=A0=
</div>
<div><br></div><div>Seriously, I have not heard a strong justification for =
this proposal yet. I have heard some people talking about Tor-ifying commun=
ications, but that is a completely different issue and should not be confus=
ed with just "encrypting bitcoin messages".</div>
</div></div></div>
--001a113a75ce3f93400501500973--
|
