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
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
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 <rme@i-rme.es>) id 1XJl4u-0007at-FE
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 15:12:04 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of i-rme.es
designates 209.85.213.180 as permitted sender)
client-ip=209.85.213.180; envelope-from=rme@i-rme.es;
helo=mail-ig0-f180.google.com;
Received: from mail-ig0-f180.google.com ([209.85.213.180])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XJl4t-0002ab-6y
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 15:12:04 +0000
Received: by mail-ig0-f180.google.com with SMTP id l13so9775828iga.7
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Aug 2014 08:11:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=gMk7AxLUVTsg0fLNrMnwJVWEJ16fzfnkHYtoFbSpPA4=;
b=lEajIPcLa68qcrSnVmXvcLcXypllBD8/H6RPB/0ivwsJLgIkgT8XICD7S8YjpJlbgu
1lCWs2guY7KTNn1eKLdMUgDE/l2tHR0meFdht7+ALcttdlCbwizEKskQRvEjyNVcb9ZH
BIsSFFwh6D/kQ/K+yFlKAHBz8EMvX2HjnsrPEeeMrENUSSwmGkhO74uvO1VTgwtpiRhQ
7aNiVZiocWyfriLwq16PMhHcIkYVDXMdCJda6UpcrXuJL5KRWrm7+BkSS4jSlc2Q+/9O
BLa6FcArUikafcRfp+H4o3moK+UtVSzx0TqbIS2GX9mOvmFp89sDbTiwy0drMITZ0sQd
FJEA==
X-Gm-Message-State: ALoCoQnp9kS0cIlVx5I/NlHbc6cgW+ljZTsQeOfPCI6mAeOx3tkHEoq/o7Tyv6CArNQaU1aBL0r4
MIME-Version: 1.0
X-Received: by 10.50.43.193 with SMTP id y1mr6420353igl.32.1408461117544; Tue,
19 Aug 2014 08:11:57 -0700 (PDT)
Received: by 10.107.25.15 with HTTP; Tue, 19 Aug 2014 08:11:57 -0700 (PDT)
X-Originating-IP: [85.251.84.81]
Received: by 10.107.25.15 with HTTP; Tue, 19 Aug 2014 08:11:57 -0700 (PDT)
In-Reply-To: <0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com>
References: <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
<CA+8=xuKRyO1=bu7cgNGHvtAeqgKBxjTH2uUkb61GdCuEQWEu5A@mail.gmail.com>
<0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com>
Date: Tue, 19 Aug 2014 17:11:57 +0200
Message-ID: <CA+8=xu+KWSF6XYgH-_t87na6M6UOD0CM1su8sizxn5a4b0_Xrw@mail.gmail.com>
From: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= <rme@i-rme.es>
To: Richard Moore <me@ricmoo.com>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0111d1be9774a30500fce82c
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 SPF_PASS SPF: sender matches SPF record
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: 1XJl4t-0002ab-6y
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: Tue, 19 Aug 2014 15:12:04 -0000
--089e0111d1be9774a30500fce82c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Only messages between peers are encrypted, only during transit.
Before sending a transaction to Node B you use his public key, so Node B
has the key
El 19/08/2014 17:05, "Richard Moore" <me@ricmoo.com> escribi=C3=B3:
> If you encrypt all messages with an asymmetric cipher, how would each nod=
e
> make use of the blockchain in an encrypted form? Each node would be able =
to
> encrypt the data, but only the Bitcoin Core Dev could decrypt it?
>
>
> On Aug 19, 2014, at 5:49 AM, Ra=C3=BAl Mart=C3=ADnez <rme@i-rme.es> wrote=
:
>
> Hi,
> I believe that all comunications should be encrypted by default, no matte=
r
> that is public information (tx info), the only exception I would make wou=
ld
> be block packets (to avoid increasing propagation time).
>
> I suggest that Bitcoin Core should generate a public/private key pair and
> share the public one with peers.
>
> This could provide privacy and integrity but not autentication.
>
> This way you can impersonate a bitcoin node (active mitm) but you cant
> just be passive and record all transactions send or recieved by an IP
> address.
>
> Today you can just watch for incoming/outgoing transactions to determine
> what tx are created in the Node, when you find one you can see the Bitcoi=
n
> address inputs and outputs and track that person's bitcoins.
>
> As an example, SSH provides this kind of encryption, althogh Bitcoin Core
> should ignore fingerprint changes (caused due to reinstalls).
>
> Please feel free to disqus why this is not needed or why you like this
> idea.
>
> -------------------------------------------------------------------------=
-----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> .=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=
=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA>
>
> Richard Moore ~ Founder
> Genetic Mistakes Software inc.
> phone: (778) 882-6125
> email: ricmoo@geneticmistakes.com
> www: http://GeneticMistakes.com
>
>
--089e0111d1be9774a30500fce82c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">Only messages between peers are encrypted, only during trans=
it.</p>
<p dir=3D"ltr">Before sending a transaction to Node B you use his public ke=
y, so Node B has the key</p>
<div class=3D"gmail_quote">El 19/08/2014 17:05, "Richard Moore" &=
lt;<a href=3D"mailto:me@ricmoo.com">me@ricmoo.com</a>> escribi=C3=B3:<br=
type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">If you encrypt all messages with an asy=
mmetric cipher, how would each node make use of the blockchain in an encryp=
ted form? Each node would be able to encrypt the data, but only the Bitcoin=
Core Dev could decrypt it?<div>
<br></div><div><br><div><div>On Aug 19, 2014, at 5:49 AM, Ra=C3=BAl Mart=C3=
=ADnez <<a href=3D"mailto:rme@i-rme.es" target=3D"_blank">rme@i-rme.es</=
a>> wrote:</div><br><blockquote type=3D"cite"><p dir=3D"ltr">Hi,<br>
I believe that all comunications should be encrypted by default, no matter =
that is public information (tx info), the only exception I would make would=
be block packets (to avoid increasing propagation time).</p><p dir=3D"ltr"=
>
I suggest that Bitcoin Core should generate a public/private key pair and s=
hare the public one with peers.</p><p dir=3D"ltr">This could provide privac=
y and integrity but not autentication.</p><p dir=3D"ltr">This way you can i=
mpersonate a bitcoin node (active mitm) but you cant just be passive and re=
cord all transactions send or recieved by an IP address.</p>
<p dir=3D"ltr">Today you can just watch for incoming/outgoing transactions =
to determine what tx are created in the Node, when you find one you can see=
the Bitcoin address inputs and outputs and track that person's bitcoin=
s.<br>
</p><p dir=3D"ltr">As an example, SSH provides this kind of encryption, alt=
hogh Bitcoin Core should ignore fingerprint changes (caused due to reinstal=
ls).</p><p dir=3D"ltr">Please feel free to disqus why this is not needed or=
why you like this idea.</p>
---------------------------------------------------------------------------=
---<br>_______________________________________________<br>Bitcoin-developme=
nt mailing list<br><a href=3D"mailto:Bitcoin-development@lists.sourceforge.=
net" target=3D"_blank">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br></blockquote></div><br><div>
<span style=3D"border-collapse:separate;color:rgb(0,0,0);font-family:Helvet=
ica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing=
:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px">.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=
=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=
=C2=B8><(((=C2=BA><br>
<br>Richard Moore ~ Founder<br>Genetic Mistakes Software inc.<br>phone: (77=
8) 882-6125<br>email:=C2=A0<a href=3D"mailto:ricmoo@geneticmistakes.com" ta=
rget=3D"_blank">ricmoo@geneticmistakes.com</a><br>www:=C2=A0<a href=3D"http=
://GeneticMistakes.com/" target=3D"_blank">http://GeneticMistakes.com</a></=
span>
</div>
<br></div></div></blockquote></div>
--089e0111d1be9774a30500fce82c--
|
