From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: <0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com> Date: Tue, 19 Aug 2014 17:11:57 +0200 Message-ID: From: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= To: Richard Moore , Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" 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 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

Only messages between peers are encrypted, only during trans= it.

Before sending a transaction to Node B you use his public ke= y, so Node B has the key

El 19/08/2014 17:05, "Richard Moore" &= lt;me@ricmoo.com> escribi=C3=B3:
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?


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 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 s= hare the public one with peers.

This could provide privac= y and integrity but not autentication.

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.

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.

As an example, SSH provides this kind of encryption, alt= hogh Bitcoin Core should ignore fingerprint changes (caused due to reinstal= ls).

Please feel free to disqus why this is not needed or= why you like this idea.

---------------------------------------------------------------------------= ---
_______________________________________________
Bitcoin-developme= nt mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

.=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: (77= 8) 882-6125
email:=C2=A0ricmoo@geneticmistakes.com
www:=C2=A0http://GeneticMistakes.com

--089e0111d1be9774a30500fce82c--