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

--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, &quot;Richard Moore&quot; &=
lt;<a href=3D"mailto:me@ricmoo.com">me@ricmoo.com</a>&gt; 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 &lt;<a href=3D"mailto:rme@i-rme.es" target=3D"_blank">rme@i-rme.es</=
a>&gt; 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&#39;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&gt;&lt;(((=C2=BA&gt;<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--