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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rme@i-rme.es>) id 1XJgO5-0001Fl-PP
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 10:11:33 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of i-rme.es
designates 209.85.223.182 as permitted sender)
client-ip=209.85.223.182; envelope-from=rme@i-rme.es;
helo=mail-ie0-f182.google.com;
Received: from mail-ie0-f182.google.com ([209.85.223.182])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XJgO5-0005NE-0B
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Aug 2014 10:11:33 +0000
Received: by mail-ie0-f182.google.com with SMTP id y20so800855ier.27
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Aug 2014 03:11:27 -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:cc:content-type;
bh=ZACOTno0Ke+5sUM3yTPorpV6rqPdn/Q2somBdoJ8u0U=;
b=ELYgLLWbWAEKzoGX557Ww+Nc1R/SgpqJBVnRyFLJ9fnlVwFjEgv9gk46b+GCoIeOv2
d7J9z+pDFs/6ABcERaKNR/OVLTkGSqoJ2TSGmYN2PkuMbM29v/GI3qc0g3x62OEvcSk3
eHp3gKA6i0YKHX+wvK2faqZSd/PUloc0Qe8XVkivb+k95E70pImL/0nNqqyuprMczLWN
jdsNRqeYhVHlpinJXMYonFvgDuDC2gAQUK+NSnge/mhG/tD7ULKb8bWMSwxWqNYzpGsm
x3pDl4Cg/MrR0OBustR7SX7Q8ksTUSW/YNaQaXB+aB2jkTenvu8Pegll34SjUzWuUdes
Vrxg==
X-Gm-Message-State: ALoCoQnC9YlWNm02wi5IWm90CWP6beiN1vEIcs0PyT0MqihiGXb0yzQePi844PYTFeS8CQhL8Mbk
MIME-Version: 1.0
X-Received: by 10.50.152.9 with SMTP id uu9mr4536484igb.32.1408441782230; Tue,
19 Aug 2014 02:49:42 -0700 (PDT)
Received: by 10.107.25.15 with HTTP; Tue, 19 Aug 2014 02:49:41 -0700 (PDT)
X-Originating-IP: [85.251.84.81]
Received: by 10.107.25.15 with HTTP; Tue, 19 Aug 2014 02:49:41 -0700 (PDT)
In-Reply-To: <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
References: <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
Date: Tue, 19 Aug 2014 11:49:41 +0200
Message-ID: <CA+8=xuKRyO1=bu7cgNGHvtAeqgKBxjTH2uUkb61GdCuEQWEu5A@mail.gmail.com>
From: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= <rme@i-rme.es>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013c67c41df76f0500f868fd
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.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: 1XJgO5-0005NE-0B
Subject: [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 10:11:33 -0000
--089e013c67c41df76f0500f868fd
Content-Type: text/plain; charset=UTF-8
Hi,
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).
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 Bitcoin
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.
--089e013c67c41df76f0500f868fd
Content-Type: text/html; charset=UTF-8
<p dir="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="ltr">I suggest that Bitcoin Core should generate a public/private key pair and share the public one with peers.</p>
<p dir="ltr">This could provide privacy and integrity but not autentication.</p>
<p dir="ltr">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.</p>
<p dir="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 bitcoins.<br>
</p>
<p dir="ltr">As an example, SSH provides this kind of encryption, althogh Bitcoin Core should ignore fingerprint changes (caused due to reinstalls).</p>
<p dir="ltr">Please feel free to disqus why this is not needed or why you like this idea.</p>
--089e013c67c41df76f0500f868fd--
|
