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; 
MIME-Version: 1.0
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
Subject: [Bitcoin-development] Proposal: Encrypt bitcoin messages
Precedence: list

--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&#39;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--