From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id BD26A40B for ; Thu, 23 Jul 2015 12:23:47 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CDE5D16F for ; Thu, 23 Jul 2015 12:23:46 +0000 (UTC) Received: by lbbzr7 with SMTP id zr7so156472357lbb.1 for ; Thu, 23 Jul 2015 05:23:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=xye9odZM837w/sgAMqlNtlxfIM883nRHwyA1nSjS+EQ=; b=eCajxBsZ+ANYf//hQVBBbHTW6/Tz3rVB3Ksru5wsLLDKcrcphSy6CcXeur1KiTUk/0 TmAeXKwdGtz/BvvF4EpCwiANglxZ8W5ZVCH4/lDKMaXmqZOgWSm41GT6B2cLuJPMd/o2 bYXB944Zibhf+C0uRPjDAzGSJ48tHVSNV1cRU/vbAWQOo6cBtsZA/VIQW65+KwpufGwE BjLoaexvuzPW53k6i/hG3siAV9VG4B1ongNsmYZ62jvwdloiE6WcZQpeSQnFqIhFcymH 4DFX9Is3cEkp6AaABPTcnkJFvRnKhisuJvEOO4P2Lgta/iXupUccgpSC6+1admES/JCN MG3A== X-Received: by 10.152.43.16 with SMTP id s16mr7598333lal.101.1437654224875; Thu, 23 Jul 2015 05:23:44 -0700 (PDT) MIME-Version: 1.0 References: <55AFBBE6.3060702@electrum.org> <1437606706.2688.0.camel@yahoo.com> <114b2a76-ebc7-461a-b4bc-10873574d6c4@HUB2.rwth-ad.de> In-Reply-To: <114b2a76-ebc7-461a-b4bc-10873574d6c4@HUB2.rwth-ad.de> From: Stefan Richter Date: Thu, 23 Jul 2015 12:23:35 +0000 Message-ID: To: Eric Voskuil , gb , Thomas Voegtlin Content-Type: multipart/alternative; boundary=001a11c3674c623639051b89f5d3 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Making Electrum more anonymous X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 12:23:47 -0000 --001a11c3674c623639051b89f5d3 Content-Type: text/plain; charset=UTF-8 This looks like a prime application for this PIR library: http://percy.sourceforge.net/apidocs/index.html Eric Voskuil via bitcoin-dev schrieb am Do., 23. Juli 2015 um 02:07 Uhr: > This is a good point. I didn't delve into the specifics of > implementation due to the larger issues that I raised. Libbitcoin Server > uses CurveZMQ, an implementation of CurveCP. > > http://curvecp.org > http://curvezmq.org > https://en.bitcoin.it/wiki/Libbitcoin_Server > > e > > On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote: > > Why RSA? > > > >> > >> Here is an idea, inspired by TOR, on which I would like to have some > >> feedback: We create an anonymous routing layer between Electrum servers > >> and clients. > >> > >> * Each server S publishes a RSA public key, KS > >> * Each client receives a list of available servers and their pubkeys > >> * For each wallet address, addr_i, a client chooses a server S_i, and a > >> RSA keypair (K_addr_i, k_addr_i) > >> * The client creates a list of encrypted requests. Each request contains > >> addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i > >> * The client chooses a main server M, and sends the list of encrypted > >> requests to M > >> * M dispatches the client's requests to the corresponding servers S_i > >> (without the client's IP address.) > >> * Each server decrypts the requests it receives, performs the request, > >> and encrypts the result with K_addr_i > >> * M receives encrypted responses, and forwards them to the client. > >> * The client decrypts the encrypted response with k_addr_i > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --001a11c3674c623639051b89f5d3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This looks like a prime application for this PIR library:= =C2=A0http://pe= rcy.sourceforge.net/apidocs/index.html

This is a good point. I didn't delve into the spec= ifics of
implementation due to the larger issues that I raised. Libbitcoin Server uses CurveZMQ, an implementation of CurveCP.

http://= curvecp.org
http:/= /curvezmq.org
https://en.bitcoin.it/wiki/Libbitcoin_Server

e

On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote:
> Why RSA?
>
>>
>> Here is an idea, inspired by TOR, on which I would like to have so= me
>> feedback: We create an anonymous routing layer between Electrum se= rvers
>> and clients.
>>
>> * Each server S publishes a RSA public key, KS
>> * Each client receives a list of available servers and their pubke= ys
>> * For each wallet address, addr_i, a client chooses a server S_i, = and a
>> RSA keypair (K_addr_i, k_addr_i)
>> * The client creates a list of encrypted requests. Each request co= ntains
>> addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i<= br> >> * The client chooses a main server M, and sends the list of encryp= ted
>> requests to M
>> * M dispatches the client's requests to the corresponding serv= ers S_i
>> (without the client's IP address.)
>> * Each server decrypts the requests it receives, performs the requ= est,
>> and encrypts the result with K_addr_i
>> * M receives encrypted responses, and forwards them to the client.=
>> * The client decrypts the encrypted response with k_addr_i

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--001a11c3674c623639051b89f5d3--